IBM服务器升级了内存和CPU后启动sybase异常
这是客户自己升级的，具体还做什么操作了就不太清楚了，但是从现在看出来的还有Firmware Version也升级了。
现在出了问题，客户来找我们说了。
System Model: IBM,7028-6C4
Machine Serial Number: ****
Processor Type: PowerPC_POWER4
Number Of Processors: 4
Processor Clock Speed: 1453 MHz
CPU Type: 64-bit
Kernel Type: 32-bit
LPAR Info: 1 NULL
Memory Size: 9216 MB
Good Memory Size: 9216 MB
Firmware Version: IBM,RG080425_d79e22_r
Console Login: enable
Auto Restart: true
Full Core: false
下面我附上SYBASE启动日志
附件：
SYBASE.log (9.49 MB)
23同行回答
贴出的日志很长，包含了2006至今的数据，说实话没看完，但是已经基本确定了几个信息：
1. Adaptive Server Enterprise/12.5.2/EBF 11792/P/RS6000/AIX 4.3.3/ase1252/1831/32-bit/FBO/Fri Apr 9 06:30:35 2004
2. server name is 'SYBASE'
3. /opt/sybase-12.5/ASE-12_5/SYBASE.cfg
其实最有意义的还是最后一段
os_find_good_keyfile: Too many dangling memory segments, nead a clean up
kbcreate: couldn't get shmid for server region 0.
kistartup: could not create shared memory
请参照以下办法试试
1.备份并删除文件
文件 /opt/sybase-12.5/ASE-12_5/SYBASE.krg
2.设置最大共享内存
文件 /opt/sybase-12.5/SYBASE.cfg
参数 allocate max shared memory = DEFAULT
3.重新启动Sybase服务
目录 /opt/sybase-12.5/ASE-12_5/install/
命令 startserver -f RUN_SYBASE
startserver -f RUN_SYBASE_back
startserver -f RUN_SYBASE_mon
* 以下摘自Sybase官方
A.有关/sybase/hostname.krg文件
The .krg file contains the address of the shared memory segment that the Sybase server has allocated. This is so that other Sybase processes(backup server, for example) can attach itself to the same memory segment. If the files are still there on the next start they simply get overwritten.
B.有关共享内存超过16G的补丁
List of Fixes for EBF 15445
---------------------------
Following is a list of fixes which are cumulative to this release. Each
fix is listed along with the EBF in which it was first released and the
description of the problem. The list is sorted by the EBFID column.
The list of fixes represents changes included after the ASE 12.5.4 Release.
EBFID BugID Description
----- ------ -------------------------------------------------
14078 425945 On IBM AIX 5.1, when ASE tries to allocate shared
memory larger than 16G, the error message
"kernel os_find_good_keyfile: Found shared memory
segment: key 0xce0013ac, id 1048593 kernel
os_find_good_keyfile: If SQL Server using it is
not running, remove it by hand kernel
os_find_good_keyfile: Too many dangling memory
segments, nead a clean up kernel kbcreate:
couldn't get shmid for kernel region. kernel
kistartup: could not create shared memory" may be
reported in the error log.收起
1. Adaptive Server Enterprise/12.5.2/EBF 11792/P/RS6000/AIX 4.3.3/ase1252/1831/32-bit/FBO/Fri Apr 9 06:30:35 2004
2. server name is 'SYBASE'
3. /opt/sybase-12.5/ASE-12_5/SYBASE.cfg
其实最有意义的还是最后一段
os_find_good_keyfile: Too many dangling memory segments, nead a clean up
kbcreate: couldn't get shmid for server region 0.
kistartup: could not create shared memory
请参照以下办法试试
1.备份并删除文件
文件 /opt/sybase-12.5/ASE-12_5/SYBASE.krg
2.设置最大共享内存
文件 /opt/sybase-12.5/SYBASE.cfg
参数 allocate max shared memory = DEFAULT
3.重新启动Sybase服务
目录 /opt/sybase-12.5/ASE-12_5/install/
命令 startserver -f RUN_SYBASE
startserver -f RUN_SYBASE_back
startserver -f RUN_SYBASE_mon
* 以下摘自Sybase官方
A.有关/sybase/hostname.krg文件
The .krg file contains the address of the shared memory segment that the Sybase server has allocated. This is so that other Sybase processes(backup server, for example) can attach itself to the same memory segment. If the files are still there on the next start they simply get overwritten.
B.有关共享内存超过16G的补丁
List of Fixes for EBF 15445
---------------------------
Following is a list of fixes which are cumulative to this release. Each
fix is listed along with the EBF in which it was first released and the
description of the problem. The list is sorted by the EBFID column.
The list of fixes represents changes included after the ASE 12.5.4 Release.
EBFID BugID Description
----- ------ -------------------------------------------------
14078 425945 On IBM AIX 5.1, when ASE tries to allocate shared
memory larger than 16G, the error message
"kernel os_find_good_keyfile: Found shared memory
segment: key 0xce0013ac, id 1048593 kernel
os_find_good_keyfile: If SQL Server using it is
not running, remove it by hand kernel
os_find_good_keyfile: Too many dangling memory
segments, nead a clean up kernel kbcreate:
couldn't get shmid for kernel region. kernel
kistartup: could not create shared memory" may be
reported in the error log.收起
浏览2304