Bootstrap Phase2 Naming Registration Fails in Systems Management
 Technote (FAQ)
 
Problem
The BBOIRC job ran successfully, but after stopping the servers and issuing the start again with the 'parms='-orbcbi cold' to complete the bootstrap phase, the system management server received the following errors:

BBOU0652E NAMING REGISTRATION FAILED FOR SERVER BBONM
BBOU0652E NAMING REGISTRATION FAILED FOR SERVER BBOSM

These errors were also found in the was.error log:

2002/01/24 22:43:04.504 01 SYSTEM=DIPN SERVER=BBOSM01 JobName=BBOSM
ASID=0X0251 PID=0X0402025A TID=0X3E6A1000 0X000003 c=UNK
./bbooorbr.cpp+853 ... BBOU0041E Function IWMEDELE failed with rc=4,
REASON=03330411
22:43:04.497 01 SYSTEM=DIPN SERVER=BBOSM01 JobName=BBOSMS
ASID=0X02A3 PID=0X03020320 TID=0X3E6F3800 0X00000B c=UNK
./bbottscu.cpp+900 ... BBOU0011W The function
BBOT_TransactionCurrentRep_SR::commit(CORBA::Boolean,CORBA::Boolean)+9
00 raised CORBA system exception CORBA::TRANSACTION_ROLLEDBACK.
Error code is C9C2184D

22:43:04.485 01 SYSTEM=DIPN SERVER=BBOSM01 JobName=BBOSMS
ASID=0X02A3 PID=0X03020320 TID=0X3E6F3800 0X00000B c=UNK
./bbottscu.cpp+815 ... BBOU0012W The function
BBOT_TransactionCurrentRep_SR::commit(CORBA::Boolean,CORBA::Boolean)+8
15 received CORBA system exception CORBA::TRANSACTION_ROLLEDBACK.
Error code is C9C2184D

22:43:04.216 01 SYSTEM=DIPN SERVER=DWSSM01 JobName=DWSSMS
ASID=0X02A3 PID=0X03020320 TID=0X3E6F3800 0X00000B c=UNK
./bbomsbo7.cpp+1789 ... BBOU0013W The function
registerHomeNamingRegistrationEntry(Ism_NamingRegistrationEntry&,IHome
PrimaryKey*,const char*,IBOIM390PrivateLocalToServer::IMContainer*,ILi
feCycleRepositoryLocalObjectImpl::FactoryRepository*)+1789 raised a
user exception Ism_Scripting::Ism_Conversation::NamingRegistrationFailed
 
Cause
Possibly the BBONMC job was not run, or failed when executed. Follow the directions below to determine if your scenario matches the following results.
 
Solution
If BBOSMSS was run with TRACEBUFFLOC=SYSPRINT you can track through the SYSMGMT trace, looking for the following history (from newest to oldest message):

BBOU0652E - NAMING REGISTRATION FAILED FOR SERVER DWSNM

C9C21823 - txn. is pending rollback
C9C21444 - invalid key = CORBA invalid object reference
C9C21444 was in message inbound to Sys.Mgmt. from Naming.

Then use the Naming Server data and look for the following trace entries from the BBONMS job output:


Description: IM Trace Exception Data
Home Name: NamingContext
Primary Key: data_address=3ef656e8, data_length=16
-------------------------------------------------------------------
OSet| Address = 3ef656e8 Length = 0010 | EBCDIC | ASCII
----+-----------------------------------+----------------+---------
0000|03000000 00000000 00000004 002F0000|................|.............
/
-------------------------------------------------------------------
Class Name: NamingServiceDO::NamingContextDO
Method Name: retrieveFromDataStore
Exception Id: IDL:ITLSIMFException/IDataKeyNotFound:1.0
Trace: 2002/02/28 14:54:51.582 01 t=7C6E88 c=1.85 key=P8 (00000007)
Description: Catch CORBA user exception
exception id: IManagedClient::INoObjectWKey
from file: ./bboi3pli.cpp
at line: 3711
Trace: 2002/02/28 14:54:51.584 01 t=7C6E88 c=1.85 key=P8 (00000004)
Description: Throw CORBA system exception
exception id: CORBA::INV_OBJREF
minor code: c9c21444
from filename: ./bboi3pli.cpp
at line: 3712


Above in the, "IM Trace Exception Data" in the ASCII section there is the key that is not found, "/". This is the Naming root which should have been created by the BBONMC job that should have been run previously. If this step was not run, or the BBONMC job failed then you should follow the steps below to recover. (Since you are at step 13 of Phase 2 of the bootstrap process there have been some updates done to DB2 tables that can only be 'undone' by following the following below:)

  1. Run BBOLDTBD - This will delete the corrupted LDAP DB2 tables
  2. In the BBOINSTR member go back to the step where you are instructed to run BBOMCRDB. Run this job and continue following the instructions from that point forward.

Be sure you run BBOLDTBD with an ID that has adequate DB2 access since this job, and several of the other installation jobs create DB2 tables and execute DB2 binds and grants.
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > System Management/Repository
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1156711
IBM Group: Software Group
Modified date: Jan 2, 2004