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:)
- Run BBOLDTBD - This will delete the corrupted LDAP DB2 tables
- 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. |