山东移动

2008年4月29日 5182点热度 0人点赞 0条评论

200804---磁盘阵列裸设备的使用支持

vxedit set user=oracle group=dba volume_name

目前有两个盘阵可供使用,已经创建了大部分的逻辑分区。
其中40G做了cook file。
另外300多G做裸设备供oracle使用。
SQL> CREATE TABLESPACE ts_test DATAFILE '/dev/vx/rdsk/datadg/rawdata1-1' size 2047000k;
注:阵列空间建的是4194304个块,即2G,由于阵列空间使用时可能需要控制信息,建议保留几十k以避免意外,故建立空间时最多使用2097152k-2k
其他字符设备的使用请务必参照此说明确定size的大小!
关于字符设备的详细信息可以这样查看:
#vxprint -ht
结果中length的大小单位是块。

目前rawdata1-1~1-10是2G;
2-1~2-10,3-1~3-10是4G;

建立卷:vxassist -g datadg make rawdata4-01 4g datadg01
在datadg01这个磁盘上建立一个名为rawdata4-01的卷,大小为4G。

创建表空间时权限需要修改:
vxedit -g datadg set user=oracle group=dba mode=660 rawdata1-1

vxassist -g datadg make rawdata12-01 4g datadg01
sleep 2
vxassist -g datadg make rawdata12-02 4g datadg02
sleep 2
vxassist -g datadg make rawdata12-03 4g datadg01
sleep 2
vxassist -g datadg make rawdata12-04 4g datadg02
sleep 2
vxassist -g datadg make rawdata12-05 4g datadg01
sleep 2
vxassist -g datadg make rawdata12-06 4g datadg02
sleep 2
vxassist -g datadg make rawdata12-07 4g datadg01
sleep 2
vxassist -g datadg make rawdata12-08 4g datadg02
sleep 2
vxassist -g datadg make rawdata12-09 4g datadg01
sleep 2
vxassist -g datadg make rawdata12-10 4g datadg02
sleep 2

vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-01
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-02
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-03
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-04
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-05
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-06
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-07
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-08
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-09
vxedit -g datadg set user=oracle group=dba mode=660 rawdata12-10

root@sdwg9 # vxassist -g datadg make rawdata13-01 4g datadg01
root@sdwg9 # vxedit -g datadg set user=oracle group=dba mode=660 rawdata13-01

----------------------------------------------

200806---数据库升级

PM建议:先在hp4测试,再在hp2升级,稳定运行一段时间没有问题以后,再在hp1升级。

sdwghp4:/u1/informix>oninit
/usr/lib/pa20_64/dld.sl: Unable to find library 'libjvm.sl'.
Killed

./u1/informix/extend/krakatoa/jre/lib/PA_RISC/server/libjvm.sl
./u1/informix/extend/krakatoa/jre/lib/PA_RISC2.0/server/libjvm.sl
./u1/informix/extend/krakatoa/jre/lib/PA_RISC2.0W/server/libjvm.sl

./opt/java1.3/jre/lib/PA_RISC/classic/libjvm.sl
./opt/java1.3/jre/lib/PA_RISC/server/libjvm.sl
./opt/java1.3/jre/lib/PA_RISC2.0/classic/libjvm.sl
./opt/java1.3/jre/lib/PA_RISC2.0/server/libjvm.sl
./opt/java1.4/jre/lib/PA_RISC/server/libjvm.sl
./opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl
./opt/java1.4/jre/lib/PA_RISC2.0W/server/libjvm.sl
./opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl
./opt/java1.5/jre/lib/PA_RISC2.0W/server/libjvm.sl

cp: cannot access /u1/informix1110/etc/sqlhosts.std

Errors occurred during the installation.
- One or more errors occurred during the copying of files (servercorefiles) .
Please refer to the install log for additional information.
- One or more errors occurred during the copying of files (perfmonitorfiles) .
Please refer to the install log for additional information.

以上错误因为安装介质引起,重新下载、上传,ok。

------------------------------------------------------------------

2008-6-27,按照ibm网站给出的升级步骤,升级hp4数据库,ok。观察一个周末,2008-6-30周一上午检查log,一切正常。
实际升级、转换时间为:1分5秒

sdwghp2:/etc/cmcluster/ha_ids2>cat ids2start.sh
export INFORMIXDIR=/u1/informix/ids94ha2
export ONCONFIG=onconfig.sdwgdb2
export INFORMIXSERVER=sdwg1_db
export SHLIB_PATH=$INFORMIXDIR/lib
export PATH=$INFORMIXDIR/bin:.:$PATH
export INFORMIXSTACKSIZE=64
export KAIOON=1
export IFMX_HPKAIO_NUM_REQ=3000
su informix -c oninit
sdwghp2:/etc/cmcluster/ha_ids2>cat ids2stop.sh
export INFORMIXDIR=/u1/informix/ids94ha2
export ONCONFIG=onconfig.sdwgdb2
export INFORMIXSERVER=sdwg1_db
export LIBPATH=$INFORMIXDIR/lib
export PATH=$INFORMIXDIR/bin:.:$PATH
su informix -c "onmode -ky"

----------------------------------------

2008-6-30升级sdwghp2:

15:58:13  IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.

15:58:13  Physical Recovery Started at Page (1:72122).
15:58:13  Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
15:58:13  Logical Recovery Started.
15:58:13  10 recovery worker threads will be started.
15:58:13  HPUX Version B.11.11 -> Using flag/select style KAIO
15:58:13  HP KAIO concurrent requests changed from 1000 to 3000
15:58:13  HPUX KAIO Segment locked addr=0xe97000 size=512000000
15:58:13  HPUX KAIO Segment locked addr=0x88b69000 size=2421981184
15:58:17  Logical Recovery has reached the transaction cleanup phase.
15:58:17  Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks

15:58:18  Dataskip is now OFF for all dbspaces
15:58:18  Conv/rev: Started check phase of conversion for component RSAM
15:58:18  Conv/rev: Finished check phase of conversion for component RSAM
15:58:18  Conv/rev: Started check phase of conversion for component SQL
15:58:18  Quiescent Mode
15:58:18  Conv/rev: Finished check phase of conversion for component SQL
15:58:18  Conv/rev: Started check phase of conversion for component SMI
15:58:18  Conv/rev: Finished check phase of conversion for component SMI
15:58:18  Conv/rev: Started check phase of conversion for component BAR
15:58:18  Conv/rev: Finished check phase of conversion for component BAR
15:58:18  Conv/rev: Started check phase of conversion for component PLOAD
15:58:18  Conv/rev: Finished check phase of conversion for component PLOAD
15:58:18  Conv/rev: Started check phase of conversion for component RTREE
。。。。。
15:58:32  R-tree error message conversion completed successfully.
15:58:34  Conv/rev: Finished conversion for component RTREE
15:58:34  Conv/rev: Started conversion for component SECURE
15:58:35  'sysuser' conversion completed successfully.
15:58:37  Conv/rev: Finished conversion for component SECURE
15:58:37  Conv/rev: Started conversion for component SCHAPI
15:58:37  Conv/rev: Finished conversion for component SCHAPI
15:58:37  Conv/rev: Started conversion for component HA
15:58:37  Conv/rev: Finished conversion for component HA
15:58:37  Conversion Completed Successfully
15:58:37  Building 'sysadmin' database ...
15:58:38  Unloading Module <SPLNULL>
15:58:38  Loading Module <SPLNULL>
15:58:38  'sysadmin' database built successfully.
15:58:38  SCHAPI: Started dbScheduler thread.
15:58:38  SCHAPI: Started 2 dbWorker threads.
16:03:22  Checkpoint Completed:  duration was 0 seconds.
16:03:22  Mon Jun 30 - loguniq 27574, logpos 0x97c56d8, timestamp: 0xfc8322ab Interval: 3

16:03:22  Maximum server connections 103
16:03:22  Checkpoint Statistics - Avg. Txn Block Time 0.132, # Txns blocked 25, Plog used 59761,
Llog used 38980

4h以后报错:
20:12:00  Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem
20:12:00  IBM Informix Dynamic Server Version 11.10.FC2
20:12:00   Who: Session(6068, tmn@sdwghp2, 18354, c000000001a38b38)
Thread(6217, sqlexec, c000000001a10e70, 1)
File: mtex.c Line: 406
20:12:00   Action: Please notify IBM Informix Technical Support.
20:12:00  stack trace for pid 17367 written to /u1/informix/ids94ha2/tmp/af.1c31cd90
20:12:01   See Also: /u1/informix/ids94ha2/tmp/af.1c31cd90
20:12:14  Exception Caught. Type: MT_EX_OS, Context: mem
20:12:14  (-9791): ERROR: Routine execution trap -- procname=<ap_get_start_endtime> procid=236
reason: mem
20:12:14  Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem
20:12:14  IBM Informix Dynamic Server Version 11.10.FC2
20:12:14   Who: Session(6068, tmn@sdwghp2, 18354, c000000001a38b38)
Thread(6217, sqlexec, c000000001a10e70, 1)
File: mtex.c Line: 406
20:12:14   Action: Please notify IBM Informix Technical Support.
20:12:14  stack trace for pid 17367 written to /u1/informix/ids94ha2/tmp/af.1c31cd90
20:12:15   See Also: /u1/informix/ids94ha2/tmp/af.1c31cd90
20:12:26  Exception Caught. Type: MT_EX_OS, Context: mem
20:12:27  (-9791): ERROR: Routine execution trap -- procname=<sgsn_pdp> procid=243
reason: mem
20:12:27  stack trace for pid 17367 written to /u1/informix/ids94ha2/tmp/af.1c31cd90
20:12:27  Assert Failed: No Exception Handler
20:12:27  IBM Informix Dynamic Server Version 11.10.FC2
20:12:27   Who: Session(6068, tmn@sdwghp2, 18354, c000000001a38b38)
Thread(6217, sqlexec, c000000001a10e70, 1)
File: mtex.c Line: 475
20:12:27   Results: Exception Caught. Type: MT_EX_OS, Context: mem
20:12:27   Action: Please notify IBM Informix Technical Support.
20:12:27   See Also: /u1/informix/ids94ha2/tmp/af.1c31cd90
20:12:39  mtex.c, line 475, thread 6217, proc id 17367, No Exception Handler.
20:12:39  The Master Daemon Died
20:12:40  PANIC: Attempting to bring system down
00:57:35  IBM Informix Dynamic Server Started.

Tue Jul  1 00:57:38 2008
。。。。。。

05:27:00  Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem
05:27:00  IBM Informix Dynamic Server Version 11.10.FC2
05:27:00   Who: Session(1416, tmn@sdwghp2, 1618, c000000008221018)
Thread(1556, sqlexec, c0000000085d3148, 4)
File: mtex.c Line: 406
05:27:00   Action: Please notify IBM Informix Technical Support.
05:27:00  stack trace for pid 9121 written to /u1/informix/ids94ha2/tmp/af.9fc4fa4
05:27:02   See Also: /u1/informix/ids94ha2/tmp/af.9fc4fa4
05:27:12  Exception Caught. Type: MT_EX_OS, Context: mem
05:27:12  (-9791): ERROR: Routine execution trap -- procname=<ap_get_start_endtime> procid=236
reason: mem
05:27:12  Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem
05:27:12  IBM Informix Dynamic Server Version 11.10.FC2
05:27:12   Who: Session(1416, tmn@sdwghp2, 1618, c000000008221018)
Thread(1556, sqlexec, c0000000085d3148, 4)
File: mtex.c Line: 406
05:27:12   Action: Please notify IBM Informix Technical Support.
05:27:12  stack trace for pid 9121 written to /u1/informix/ids94ha2/tmp/af.9fc4fa4
05:27:13   See Also: /u1/informix/ids94ha2/tmp/af.9fc4fa4
05:27:22  Exception Caught. Type: MT_EX_OS, Context: mem
05:27:22  (-9791): ERROR: Routine execution trap -- procname=<sgsn_pdp> procid=243
reason: mem
05:27:22  stack trace for pid 9121 written to /u1/informix/ids94ha2/tmp/af.9fc4fa4
05:27:22  Assert Failed: No Exception Handler
05:27:22  IBM Informix Dynamic Server Version 11.10.FC2
05:27:22   Who: Session(1416, tmn@sdwghp2, 1618, c000000008221018)
Thread(1556, sqlexec, c0000000085d3148, 4)
File: mtex.c Line: 475
05:27:22   Results: Exception Caught. Type: MT_EX_OS, Context: mem
05:27:22   Action: Please notify IBM Informix Technical Support.
05:27:22   See Also: /u1/informix/ids94ha2/tmp/af.9fc4fa4
05:27:31  mtex.c, line 475, thread 1556, proc id 9121, No Exception Handler.
05:27:32  Fatal error in ADM VP at mt.c:13388
05:27:32  Unexpected virtual processor termination, pid = 9121, exit = 0x100

05:27:32  PANIC: Attempting to bring system down
06:23:29  IBM Informix Dynamic Server Started.

。。。。。。

09:12:00  Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem
09:12:00  IBM Informix Dynamic Server Version 11.10.FC2
09:12:00   Who: Session(5069, tmn@sdwghp2, 20113, c0000000154f3390)
Thread(5193, sqlexec, c0000000170540b8, 1)
File: mtex.c Line: 406
09:12:00   Action: Please notify IBM Informix Technical Support.
09:12:00  stack trace for pid 21884 written to /u1/informix/ids94ha2/tmp/af.18318460
09:12:01   See Also: /u1/informix/ids94ha2/tmp/af.18318460
09:12:01  Assert Failed: Condition Failed (Bad pool pointer 0xc0000000144fb040), In (mt_shm_free_pool)
09:12:01  IBM Informix Dynamic Server Version 11.10.FC2
09:12:01   Who: Session(5068, tmn@sdwg7, -1, c00000000c238bd8)
Thread(5192, sqlexec, c0000000170538a0, 3)
File: mtshpool.c Line: 3213
09:12:01   Action: Please notify IBM Informix Technical Support.
09:12:01  stack trace for pid 22055 written to /u1/informix/ids94ha2/tmp/af.18308461
09:12:02   See Also: /u1/informix/ids94ha2/tmp/af.18308461
09:12:13  Exception Caught. Type: MT_EX_OS, Context: mem
09:12:13  (-9791): ERROR: Routine execution trap -- procname=<ap_get_start_endtime> procid=236
reason: mem
09:12:13  Assert Failed: Exception Caught. Type: MT_EX_OS, Context: mem
09:12:13  IBM Informix Dynamic Server Version 11.10.FC2
09:12:13   Who: Session(5069, tmn@sdwghp2, 20113, c0000000154f3390)
Thread(5193, sqlexec, c0000000170540b8, 1)
File: mtex.c Line: 406
09:12:13   Action: Please notify IBM Informix Technical Support.
09:12:13  stack trace for pid 21884 written to /u1/informix/ids94ha2/tmp/af.18318460
09:12:14   See Also: /u1/informix/ids94ha2/tmp/af.18318460
09:12:14  Condition Failed (Bad pool pointer 0xc0000000144fb040), In (mt_shm_free_pool)
09:12:26  Exception Caught. Type: MT_EX_OS, Context: mem
09:12:26  (-9791): ERROR: Routine execution trap -- procname=<sgsn_pdp> procid=243
reason: mem
09:12:26  stack trace for pid 21884 written to /u1/informix/ids94ha2/tmp/af.18318460
09:12:26  Assert Failed: No Exception Handler
09:12:26  IBM Informix Dynamic Server Version 11.10.FC2
09:12:26   Who: Session(5069, tmn@sdwghp2, 20113, c0000000154f3390)
Thread(5193, sqlexec, c0000000170540b8, 1)
File: mtex.c Line: 475
09:12:26   Results: Exception Caught. Type: MT_EX_OS, Context: mem
09:12:26   Action: Please notify IBM Informix Technical Support.
09:12:26   See Also: /u1/informix/ids94ha2/tmp/af.18318460
09:12:38  mtex.c, line 475, thread 5193, proc id 21884, No Exception Handler.
09:12:39  The Master Daemon Died
09:12:39  PANIC: Attempting to bring system down
09:20:25  IBM Informix Dynamic Server Started.

ibm800建议 做存储过程的update

--------------------------------------------------

20080708---安全加固

远程登录方式 a) 系统是否启用SSH登陆,禁止telnet登陆以及root的远程登陆
solaris 5.8:
/etc/default/login:CONSOLE=/dev/console禁止root用户远程telnet
/etc/ftpusers:加上一行root禁止root用户远程ftp
hp-ux 11:
/etc/securetty:包含一行concole禁止root用户远程telnet
ssh/etc/sshd_config:PermitRootLogin no禁止root用户ssh
/etc/ftpd/ftpusers:root禁止root用户ftp

服务管理 b) 关闭不必要的系统服务,如sendmail以及/etc/inetd.conf文件中其它tcp小服务,如需启用请说明用途
solaris5.8:
/etc/mail/sendmail.cf
/etc/services:smtp/finger
ps -ef|grep sendmail
ps -ef|grep finger
38:# ps -ef|grep sendmail
root  2342     1  0   Apr 29 ?        0:00 /usr/lib/sendmail -bd -q15m
hp-ux 11:
/etc/rc.config.d/mailservs
117:# ps -ef|grep sendmail
root  1517     1  0  Apr 16  ?        203:36 sendmail: accepting connections on port 25

口令策略 c) 口令策略的设置情况:/etc/default/passwd文件
ok

主机信任 d) 系统是否启用信任主机方式,配置文件是否配置妥当
远程登录目录 e) 检查各个帐号目录下的.rhost、hosts.equiv,默认禁用rlogin和rsh
/etc/hosts.equiv,/.rhosts
用户的.rhosts:tmn,informix,metrica
sdwg4、sdwghp1、sdwghp2发现关于root用户的不妥当信任配置,已经改正。

系统日志审计 f) 设定系统日志及审计行为/etc/syslog.conf,是否定时进行备份
solaris:
/var/adm/messages*
/var/log/*
/etc/syslog.conf
hp-ux:
/var/adm/syslog/*.log
以上文件需要定时备份

sdwg4: 10.19.65.4,禁止了root远程登录telnet/ftp,ssh未安装
nspsvr1: 10.19.65.38,禁止了root远程登录telnet/ftp,ssh未安装
sdwghp1: 10.19.65.117,禁止了root远程telnet/ssh/ftp
sdwghp2: 10.19.65.118,禁止了root远程telnet/ssh/ftp
sdwghp3: 10.19.65.119,禁止了root远程telnet/ssh/ftp
sdwghp4: 10.19.65.120,禁止了root远程telnet/ssh/ftp

backupsyslog.sh

hostname=`hostname`
ny=`date "+20%y%m%d"`
echo $ny
cd /u1/tmn/
tar cvf backup/{$hostname}syslog$ny.tar /var/adm/syslog/*.log >/dev/null
compress backup/{$hostname}syslog$ny.tar >/dev/null
rcp backup/{$hostname}syslog$ny.tar.Z sdwg1:/space3/src_bak/src_hp_bak/backup
rm backup/{$hostname}syslog$ny.tar.Z

0 23 * * * /u1/tmn/backupsyslog.sh

hostname=`hostname`
ny=`date "+20%y%m%d"`
echo $ny
cd /u1/tmn/
tar cvf backup/{$hostname}syslog$ny.tar /var/adm/messages* /var/log/* /etc/syslog.conf>/dev/null
compress backup/{$hostname}syslog$ny.tar >/dev/null
rcp backup/{$hostname}syslog$ny.tar.Z sdwg1:/space3/src_bak/src_hp_bak/backup
rm backup/{$hostname}syslog$ny.tar.Z

--------------------------------------------------

20080725,117数据库做0级备份:
onbar -b -L 0
2008-07-25 10:03:03 19581  19579 /u1/informix/ids94ha1/bin/onbar_d -b -L 0
2008-07-25 10:03:04 19581  19579 Archive started on rootdbs, llogdbs, plogdbs, al_bak, al_index
_dbs, al_new, bureau_dbs, ensp_blob, ensp_dbs, ne_chk_db, rms_dbs, tmndbs (Requested Level 0).
2008-07-25 10:03:13 19581  19579 Begin level 0 backup rootdbs.
2008-07-25 10:03:13 19581  19579 Successfully connected to Storage Manager.

2008-07-25 11:20:31 19581  19579 Archive on rootdbs, llogdbs, plogdbs, al_bak, al_index_dbs, al_new, bureau_dbs, ensp_blob, ensp_dbs, ne_chk_db, rms_dbs, tmndbs Completed (Requested Level 0).
2008-07-25 11:20:32 19581  19579 Begin backup logical log 125769.

---------------------------------------------------

20080726,升级117数据库
备份原来的软件版本:
/u1/app1/log_bak/informix10.0FC8W3.tar
12:13:58  IBM Informix Dynamic Server Stopped.

12:14:46  IBM Informix Dynamic Server Started.
12:14:58  Segment locked: addr=c000000073cba000, size=2484404224

Sat Jul 26 12:15:00 2008

12:15:00  Warning: ONCONFIG dump directory (DUMPDIR) '/u1/app1/log_bak' has insecure permissions
12:15:00  Event alarms enabled.  ALARMPROG = '/u1/informix/ids94ha1/etc/alarmprogram.sh'
12:15:00  Booting Language <c> from module <>
12:15:00  Loading Module <CNULL>
12:15:00  Booting Language <builtin> from module <>
12:15:00  Loading Module <BUILTINNULL>
12:15:07  DR: DRAUTO is 0 (Off)
12:15:07  Dynamically allocated new message shared memory segment (size 3172KB)
12:15:07  Memory sizes:resident:2426176 KB, virtual:506344 KB, no SHMTOTAL limit
12:15:07  IBM Informix Dynamic Server Version 10.00.FC8W3   Software Serial Number AAA#B000000
12:15:07  HPUX Version B.11.11 -> Using flag/select style KAIO
12:15:07  HP KAIO concurrent requests changed from 1000 to 3000
12:15:10  (15) connection rejected - no calls allowed for sqlexec
12:15:10  (16) connection rejected - no calls allowed for sqlexec
12:15:10  IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.

12:15:10  Physical Recovery Started at Page (3:169309).
12:15:10  Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
12:15:11  Logical Recovery Started.
12:15:11  10 recovery worker threads will be started.
12:15:14  Logical Recovery has reached the transaction cleanup phase.
12:15:14  Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks

12:15:15  Dataskip is now OFF for all dbspaces
12:15:15  Checkpoint Completed:  duration was 0 seconds.
12:15:15  Checkpoint loguniq 126100, logpos 0x5018, timestamp: 0x25e55b02

12:15:15  Maximum server connections 0
12:15:15  Quiescent Mode

12:33:00  IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.

12:33:00  Physical Recovery Started at Page (3:169309).
12:33:00  Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
12:33:00  Logical Recovery Started.
12:33:00  40 recovery worker threads will be started.
12:33:06  Logical Recovery has reached the transaction cleanup phase.
12:33:06  Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks

12:33:07  Dataskip is now OFF for all dbspaces
12:33:07  Conv/rev: Started check phase of conversion for component RSAM
12:33:07  Conv/rev: Finished check phase of conversion for component RSAM
12:33:07  Conv/rev: Started check phase of conversion for component SQL
12:33:07  (1380) connection rejected - no calls allowed for sqlexec
12:33:07  listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in quiescent mode.

12:33:07  Conv/rev: Finished check phase of conversion for component SQL
12:33:07  Conv/rev: Started check phase of conversion for component SMI
12:33:07  Conv/rev: Finished check phase of conversion for component SMI
12:33:07  Conv/rev: Started check phase of conversion for component BAR
12:33:07  Conv/rev: Finished check phase of conversion for component BAR
12:33:07  Conv/rev: Started check phase of conversion for component PLOAD
12:33:07  Conv/rev: Finished check phase of conversion for component PLOAD
12:33:07  Conv/rev: Started check phase of conversion for component RTREE
12:33:07  Conv/rev: Finished check phase of conversion for component RTREE
12:33:07  Conv/rev: Started check phase of conversion for component SECURE
12:33:07  Conv/rev: Finished check phase of conversion for component SECURE
12:33:07  Conv/rev: Started check phase of conversion for component SCHAPI
12:33:07  Conv/rev: Finished check phase of conversion for component SCHAPI
12:33:07  Conv/rev: Started check phase of conversion for component HA
12:33:07  Conv/rev: Finished check phase of conversion for component HA
12:33:07  Conv/rev: Started conversion for component RSAM
12:33:07  (1382) connection rejected - no calls allowed for sqlexec
12:33:40  The dummy updates succeeded while converting database ensp_test.
12:33:40  processing alarmbak
12:33:40  Converting database alarmbak ...

 

12:33:41  The database alarmbak has been converted successfully.

12:33:42  The dummy updates succeeded while converting database alarmbak.
12:33:42  processing authdb

12:33:43  The dummy updates succeeded while converting database authdb.
12:33:43  Conv/rev: Finished conversion for component SQL
12:33:43  Conv/rev: Started conversion for component SMI
12:33:43  Build of sysmaster and sysutils databases Started
12:33:43  Converting/Rebuilding 'sysmaster' database ...
12:33:47  Booting Language <spl> from module <>
12:33:47  Loading Module <SPLNULL>
12:33:48  Unloading Module <SPLNULL>
12:33:50  Loading Module <SPLNULL>
12:33:51  'sysmaster' database successfully converted/rebuilt
12:33:51  Conv/rev: Finished conversion for component SMI
12:33:51  Conv/rev: Started conversion for component BAR
12:33:51  WARNING:Target server version must have a certified Storage Manager
installed after conversion/reversion and before bringing up server.
12:33:51  Conv/rev: Finished conversion for component BAR
12:33:51  Conv/rev: Started conversion for component PLOAD
12:33:51  Conv/rev: No Conversion/Reversion needed for component PLOAD
12:33:51  Conv/rev: Finished conversion for component PLOAD
12:33:51  Conv/rev: Started conversion for component RTREE
12:33:51  'sysutils' database built successfully.
12:33:51  'sysuser' database already exists.
12:33:56  R-tree error message conversion completed successfully.
12:33:59  Conv/rev: Finished conversion for component RTREE
12:33:59  Conv/rev: Started conversion for component SECURE
12:34:00  'sysuser' conversion completed successfully.
12:34:03  Conv/rev: Finished conversion for component SECURE
12:34:03  Conv/rev: Started conversion for component SCHAPI
12:34:03  Conv/rev: Finished conversion for component SCHAPI
12:34:03  Conv/rev: Started conversion for component HA
12:34:03  Conv/rev: Finished conversion for component HA
12:34:03  Conversion Completed Successfully
12:34:03  Building 'sysadmin' database ...
12:34:04  Unloading Module <SPLNULL>
12:34:05  Loading Module <SPLNULL>
12:34:06  'sysadmin' database built successfully.
12:34:06  SCHAPI: Started dbScheduler thread.
12:34:06  SCHAPI: Started 2 dbWorker threads.
12:37:45  listener-thread: err = -951: oserr = 0: errstr = SYSTEM@10.19.65.9: Incorrect password or user SYSTEM@10.19.65.9 is

--------------------------------------

20080805:137安装oracle10g
sys、system等密码:sdwg10
已经创建了一个实例,文件系统的可供使用。

-----------------------------------

20080806:137需要划分裸设备,供使用。
目前裸设备的划分情况:dg名字datadg,由两块盘阵组成分别是datadg01、datadg02,每块300G。datadg01划出了40G做文件系统。
之后,10个2G做裸设备的卷计20G;再后是4G做卷,2-1~2-10,3-1~3-10,共20个4G计80G。
目前已经投入使用的裸设备:用于informix
/dev/vx/rdsk/datadg/rawdata1-1
/dev/vx/rdsk/datadg/rawdata1-2
/dev/vx/rdsk/datadg/rawdata1-3
/dev/vx/rdsk/datadg/rawdata1-4
/dev/vx/rdsk/datadg/rawdata1-5
/dev/vx/rdsk/datadg/rawdata2-1
/dev/vx/rdsk/datadg/rawdata2-2
/dev/vx/rdsk/datadg/rawdata2-3
/dev/vx/rdsk/datadg/rawdata2-4
/dev/vx/rdsk/datadg/rawdata2-5
/dev/vx/rdsk/datadg/rawdata2-6
/dev/vx/rdsk/datadg/rawdata2-7
/dev/vx/rdsk/datadg/rawdata2-8
/dev/vx/rdsk/datadg/rawdata2-9
/dev/vx/rdsk/datadg/rawdata2-10

root@sdwg10 # vxassist -g datadg make rawdata4-01 4g datadg01
VxVM vxassist ERROR V-5-1-10127 associating subdisk datadg01-17 with rawdata4-01-01:
License has expired or is not available for operation

经华胜检查,是hostid改了以后,原来的vxvm软件不能正常使用。改回hostid之后,恢复正常。
建立如下卷:
4-1~4-10、5-1~5-10、6-1~6-10、7-1~7-10、8-1~8-10。

vxassist -g datadg make rawdata4-1 10g datadg01;sleep 2

/dev/vx/rdsk/datadg下面可以看到已经建立的卷,实际建立的卷是:前40个卷和8的6个卷,计460G。
root@sdwg10 # ls -l rawdata8-*
crw-------   1 root     root     285,14071 Aug  6 16:28 rawdata8-1
crw-------   1 root     root     285,14076 Aug  6 16:28 rawdata8-10
crw-------   1 root     root     285,14072 Aug  6 16:28 rawdata8-2
crw-------   1 root     root     285,14073 Aug  6 16:28 rawdata8-4
crw-------   1 root     root     285,14074 Aug  6 16:28 rawdata8-6
crw-------   1 root     root     285,14075 Aug  6 16:28 rawdata8-8

vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-1
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-2
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-3
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-4
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-5
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-6
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-7
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-8
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-9
vxedit -g datadg set user=oracle group=dba mode=660 rawdata3-10

3-1~3-10每个卷是4G,以后每个卷是10G。

SQL> create tablespace ts_test datafile '/dev/vx/rdsk/datadg/rawdata3-1' size 4194000k;
以如上方式建立表空间即可。

---------------------------------------------------

20080813,138上将来安装网络神探系统,需要使用大量的大文件主要是计费文件,挂接的磁盘全部作为文件系统使用,目前创建的卷需要释放掉,新建几个大卷,挂在系统上。
另外还需建立informix数据库。

vxassist -g datadg remove volume rawdata3-10

for i in 1 2 3
do
vxassist -g datadg remove volume datavol-${i}
done

目前:
dm datadg01     c1t5d0s2     -        708802624 -       -        -       -
dm datadg02     c3t5d0s2     -        708802624 -       -        -       -

datadg01已经使用83886080,还剩708802624-83886080=624916544=297G

vxassist -g datadg make datavol-1 297G datadg01
vxassist -g datadg make datavol-2 168G datadg02
vxassist -g datadg make datavol-3 168G datadg02

/etc/vfstab:
/dev/vx/dsk/datadg/datavol-1    /dev/vx/rdsk/datadg/datavol-1   /space1 vxfs    2       yes     -
/dev/vx/dsk/datadg/datavol-2    /dev/vx/rdsk/datadg/datavol-2   /space2 vxfs    2       yes     -
/dev/vx/dsk/datadg/datavol-3    /dev/vx/rdsk/datadg/datavol-3   /space3 vxfs    2       yes     -

mkfs -F vxfs /dev/vx/rdsk/datadg/datavol-1
mount /space1
space2/3类同

--------------------------------------------------

20080909---工作日志:139-sdwg12上安装ids11.10FC2,需要联系第三方搞到合适的软件。
已经完成。步骤:
建立informix用户组及informix用户;
用root用户执行ids_install。

--------------------------------------------------------

20080910---legato
sdwghp4用root登录,执行nwadmin,进入图形管理界面。

--------------------------------------------------

20081028---sdwg5(10.19.65.67)安装、配置oracle
把原来的/mirrordisk/data8做成/oracle,共20G多,用来安装oracle
http://10.19.65.67:1158/em/是管理地址
oracle用户的密码是oralce,数据库各个管理用户的默认密码也是oralce
mirrordisk/data3、6、7、9可以用做表空间

需要安装卷管理软件,sun的有免费的可以下载使用。

------------------------------------------

20081204---117-informix故障信息
14:45:22  Assert Failed: Condition Failed (Ignoring free of pool '12543735' (0xc00000
00cb72a040) in use by blkpool), In (mt_shm_free_pool)
14:45:22  IBM Informix Dynamic Server Version 11.10.FC2W4
14:45:22   Who: Session(12543735, tmn@? 1078, c0000000e31fa020)
Thread(12817466, sqlexec, c000000118e20170, 8)
File: mtshpool.c Line: 3328
14:45:22   Action: Please notify IBM Informix Technical Support.
14:45:22  stack trace for pid 4838 written to /u1/informix/ids94ha1/tmp/af.98227c82
14:45:23   See Also: /u1/informix/ids94ha1/tmp/af.98227c82, shmem.98227c82.0, //core,
gcore.98227c82.0.4838
14:46:27  Fatal error in ADM VP at mt.c:13463
14:46:27  Unexpected virtual processor termination, pid = 4838, exit = 0xb

14:46:28  PANIC: Attempting to bring system down
14:53:14  IBM Informix Dynamic Server Started.

发现数据库没有合适的0级备份,做0级备份。
共计花费80分钟。
带库是3代的带库,每盘500G,80盘。

liking

这个人很懒,什么都没留下

文章评论