BBOU0127E THE CONFIGURATION OF THE LOCAL HOST NAMESPACE HAS FAILED. NAMESPACE CONFIGURATION HAS NOT BEEN COMMITTED.
 Technote (FAQ)
 
Problem
BBOU0127E THE CONFIGURATION OF THE LOCAL HOST NAMESPACE HAS FAILED.
NAMESPACE CONFIGURATION HAS NOT BEEN COMMITTED.
 
 
Solution
Problem:

From BBONMC:
BBOU0401E The Local Host Root Naming Context couldn't be created.
BBOU0127E THE CONFIGURATION OF THE LOCAL HOST NAMESPACE HAS FAILED.
NAMESPACE CONFIGURATION HAS NOT BEEN COMMITTED.

From BBONMS:
BBOU0243E IMPLEMENTATION OF CLASS NamingServiceDO::NamingContextDO
EITHER CAUSED OR RAISED EXCEPTION CORBA::PERSIST_STORE
DURING INVOCATION OF METHOD insertToDataStore.

Possible Solution:

Verify the job BBOLD2DB has been run. BBOLD2DB primes the LDAP name space.

One way to verify LDAP has been primed is to issue the following command from a telnet session. You must insert the appropriate values for "password" and "was_Suffix"

ldapsearch -v -p 1389 -h 127.0.0.1 -D "cn=CBAdmin" -w password -b "was_Suffix" "objectclass=*"

Another way to verify BBOLD2DB has been run. Execute the following SQL query for DB2.

SELECT DN_TRUNC FROM LDAP_ENTRY;

The SQL output should appear as:

DN_TRUNC
---------+---------+---------+---------+---------+---------+---------+--
1ST ROW REQUIRED TO PREVENT REFERENTIAL INTEGRITY VIOLATIONS ON ROOT
INSERT
CN=LOCALHOST
O=BOSS,C=US
CN=CBADMIN,O=BOSS,C=US
O=WASNAMING,C=US
CN=WASADMIN,O=WASNAMING,C=US
IBM-WSNTREE=t1,O=WASNAMING,C=US
DSNE610I NUMBER OF ROWS DISPLAYED IS 7
DSNE616I STATEMENT EXECUTION WAS SUCCESSFUL, SQLCODE IS 100

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Install
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1114476
IBM Group: Software Group
Modified date: Jul 11, 2003