灌溉梦想,记录脚步

一则关于SAN Switch奇怪的故障

SAN Switch设备型号:EMC DS-4700M
存储型号:HITACHI VSP
主机型号:HP SuperDome

故障描述:

按照端口进行zone划分后,存储端无法扫描到主机wwn,之后检查光纤交换机日志,无异常。

因为交换机端口速率为2Gb,存储端口为8Gb,推测在速率协商时出现问题,之后通过将端口模式从自协商改为固定速率,观察状况,仍无效。

之后尝试在存储端手动增加wwn进行磁盘Mapping,但是无效。

之后尝试通过wwn进行划分zone,生效。

总结:

基于端口划分zone是交换机的基本功能,很难解释。

HP-UX操作系统备份

make_tape_recovery命令的格式和简单说明

#/opt/ignite/bin/make_tape_recovery [ -AprvC] [-d destination] [-b boot_destination] –make_tape_recovery命令所在的位置

-A : 指定要备份整个root disk /

-p : 预览备份过程,并不创建 Bootable DDS Tape

a. 确认 /var/opt/ignite/recovery/mkrec.append 文件

b. 创建 /var/opt/ignite/recovery/arch.include 文件
继续阅读 »

LINKLOOP二层协议连通性测试

linkloop命令是HP-UX独有的命令,所以在使用的时候对方也一定要是HP-UX主机
该命令是用来测试第二层(网卡MAC地址)的连通性,该命令是向远程HP-UX主机发送一个测试包来测试MAC地址的连通性.
用法:
linkloop 0x00248177E460 #0x00248177E460为远程主机的MAC地址.
该命令要在root用户下才能执行.
-n 设置传输的桢数
-i 指定使用哪个PPA(physical poit of attachment ,指示网卡的唯一标志)默认使用它在内部数据结构中遇到的第一个PPA(lan0)
-t 以秒为单位,指定等到(超时)时间
-s 指定数据报的大小
-v 详细信息选项
继续阅读 »

关于VIP的奇怪故障一例

OS:HP-UX 11.31 DB:Oracle 10.0.2.5 RAC (2nodes)

问题描述:节点二在服务启动后,经过1分钟至3分钟会发生VIP导致的服务切换,切换后节点二VIP在节点一上启动,检查日志主要报错为:

1
Invalid parameters, or failed to bring up VIP (host=essrzc2)

经过检查,系统网关配置正常,响应速度正常,系统日志无异常。开启服务debug后收获如下日志:

1
2
3
4
5
6
7
8
2013-12-16 14:57:08.192: [    RACG][1] [21721][1][ora.essrzc2.vip]: Mon Dec 16 14:57:03 EAT 2013 [ 21730 ] Checking interface existance
Mon Dec 16 14:57:03 EAT 2013 [ 21730 ] Calling getifbyip
Mon Dec 16 14:57:03 EAT 2013 [ 21730 ] getifbyip:  started for 132.42.37.144
 
2013-12-16 14:57:08.192: [    RACG][1] [21721][1][ora.essrzc2.vip]: Mon Dec 16 14:57:03 EAT 2013 [ 21730 ] Completed getifbyip lan900:801
Mon Dec 16 14:57:03 EAT 2013 [ 21730 ] Completed with initial interface test
Mon Dec 16 14:57:03 EAT 2013 [ 21730 ] Broadcast = 132.42.37.255
 <a href="https://www.forzw.com/archives/707#more-707" class="more-link">继续阅读 &raquo;</a>

MySQL在ARM平台上的编译错误一例

由于ARM平台开发板CPU本身处理能力有限,这样在MySQL编译的时候过程非常漫长,更可恶的还出现了错误,如下:

1
2
3
4
5
6
7
8
9
10
[ 68%] Building C object libmysql/CMakeFiles/clientlib.dir/__/sql-common/client_plugin.c.o
/root/lnmp1.0-full/mysql-5.5.28/sql-common/client_plugin.c: In function ‘mysql_client_plugin_init’:
/root/lnmp1.0-full/mysql-5.5.28/sql-common/client_plugin.c:252:5: error: incompatible type for argument 5 of ‘add_plugin’
/root/lnmp1.0-full/mysql-5.5.28/sql-common/client_plugin.c:120:1: note: expected ‘va_list’ but argument is of type ‘int’
/root/lnmp1.0-full/mysql-5.5.28/sql-common/client_plugin.c: In function ‘mysql_client_register_plugin’:
/root/lnmp1.0-full/mysql-5.5.28/sql-common/client_plugin.c:310:5: error: incompatible type for argument 5 of ‘add_plugin’
/root/lnmp1.0-full/mysql-5.5.28/sql-common/client_plugin.c:120:1: note: expected ‘va_list’ but argument is of type ‘int’
make[2]: *** [libmysql/CMakeFiles/clientlib.dir/__/sql-common/client_plugin.c.o] Error 1
make[1]: *** [libmysql/CMakeFiles/clientlib.dir/all] Error 2
make: *** [all] Error 2

处理方法如下应用下面Patch,文件名arm_fix_client_plugin.patch,内容:
继续阅读 »

ORA-65086: cannot open/close the pluggable database

在Oracle 12C中执行卸载命令后,如果执行PDB的OPEN操作,将会提示错误,如下:

1
2
3
4
5
6
7
8
SQL> alter pluggable database pdb01 unplug into '/opt/oracle/pdb01.xml';
 
Pluggable database altered.
 
SQL> ALTER PLUGGABLE DATABASE pdb01 OPEN;
*
ERROR at line 1:
ORA-65086: cannot open/close the pluggable database

继续阅读 »

crs_stop 错误一列

grid 与 oracle 版本为11.2.0.4,为两节点RAC,在通过crs_stop -all命令关闭oracle服务时出现下面问题:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
[oracle@rac01 ~]$ crs_stat -t
Name           Type           Target    State     Host        
------------------------------------------------------------
ora.DATA.dg    ora....up.type OFFLINE   OFFLINE               
ora.FRA.dg     ora....up.type OFFLINE   OFFLINE               
ora....ER.lsnr ora....er.type OFFLINE   OFFLINE               
ora....N1.lsnr ora....er.type OFFLINE   OFFLINE               
ora.OCR.dg     ora....up.type OFFLINE   OFFLINE               
ora.asm        ora.asm.type   OFFLINE   ONLINE    rac02       
ora.cvu        ora.cvu.type   OFFLINE   OFFLINE               
ora.gsd        ora.gsd.type   OFFLINE   OFFLINE               
ora....network ora....rk.type OFFLINE   OFFLINE               
ora.oc4j       ora.oc4j.type  OFFLINE   OFFLINE               
ora.ons        ora.ons.type   OFFLINE   OFFLINE               
ora.rac.db     ora....se.type OFFLINE   OFFLINE               
ora....SM1.asm application    OFFLINE   ONLINE    rac01       
ora....01.lsnr application    OFFLINE   OFFLINE               
ora.rac01.gsd  application    OFFLINE   OFFLINE               
ora.rac01.ons  application    OFFLINE   OFFLINE               
ora.rac01.vip  ora....t1.type OFFLINE   OFFLINE               
ora....SM2.asm application    OFFLINE   ONLINE    rac02       
ora....02.lsnr application    OFFLINE   OFFLINE               
ora.rac02.gsd  application    OFFLINE   OFFLINE               
ora.rac02.ons  application    OFFLINE   OFFLINE               
ora.rac02.vip  ora....t1.type OFFLINE   OFFLINE               
ora....ry.acfs ora....fs.type OFFLINE   OFFLINE               
ora.scan1.vip  ora....ip.type OFFLINE   OFFLINE

继续阅读 »