Not Able To Start Siebel Server After Deploying srf.
(Doc ID 523134.1)
Last updated on OCTOBER 17, 2022
Applies to:
Siebel System Software - Version 7.5.2.216 [16084] to 8.1.1.4 [21225] [Release V7 to V8]IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.2.216 [16084]
Database: IBM DB2/UDB 7.2
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1
Symptoms
When trying to start Siebel server on Solaris, it fails with the following in the log file.
SVR-00031: Attached to the wrong shared memory instance
Steps:
Run the below command
$ start_server all
Cleaning up previous execution of siebeldev1::sbl0stl0 ...
The parameter values in the header of file /siebel/siebsrvr/sys/os
siebeldev1.sbl0stl0 do not correspond to the current parameter values:
nFileSize 0 7649556
nSiebNLatch 0 10259
nSiebLatch 0 2500
nSiebRWLock 0 503
nSiebNSema 0 1021
nSiebSema 0 1000
nSiebLatchNameLen 0 256
nSiebSemaNameLen 0 64
nSiebProcExit 0 256
Error 1300003 in OSDInit (os = 17)
already stopped at Thu Aug 7 14:19:53 2003
Siebel Server "sbl0stl0" (Enterprise "siebeldev1")
Error 1300003 in OSDInit
On further reviewing the siebl.log
$ tail -f siebel.log
2021 2003-08-07 15:36:04 2003-08-07 15:36:04 -0500 00000003 001 001f 0001 09 siebel 1368294 1 /siebel/siebsrvr/log/siebel.log 7.5.2.216 [16084] ENUENU
GenericLog GenericError 1 2003-08-07 15:36:04 (sissrvr.cpp 47(2695) err=2000031 sys=0) SVR-00031: Attached to the wrong shared memory instance
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |