Last updated on MARCH 08, 2017

Applies to:

Symptoms

Created a new IAM for OAM domain for our OIM 11gR2 logical environment. which already has an OIM domain and has had the configureSecurityStore script run successfully.
When attempting to join the new IAM_domain with this syntax
"[oracle@tvloim01 bin]$ ./wlst.sh /bnz/home/oracle/Middleware/Oracle_IDM1/common/tools/configureSecurityStore.py -d /bnz/home/oracle/Middleware/user_projects/domains/IAM_domain/ -t DB_ORACLE -j cn=jpsroot -p ****** -c IAM -m join "

we get the following result.
Info: Data source is: opss-DBDS
Info: User chose to skip importing encryption key.
Info: DB JDBC driver: oracle.jdbc.OracleDriver
Info: DB JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=dildoi01-vip.nz.oracle.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=idm.nz.oracle.com)(INSTANCE_NAME=ora1d1)))
[oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator] checkServiceSetup - done
Oct 9, 2012 11:48:25 AM oracle.security.jps.internal.credstore.ldap.LdapCredentialStore
WARNING: Could not create credential store instance. Reason oracle.security.jps.service.policystore.PolicyStoreException: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
[oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator] updateServiceConfiguration - done
.
.
Oct 9, 2012 11:48:41 AM oracle.security.jps.internal.config.ldap.LdapAuditServiceConfigurator checkIfConfigurationValid
INFO: Audit store re-association not supported.
[oracle.security.jps.internal.config.db.DbAuditStoreServiceConfigurator] checkServiceSetup - Audit store re-association not supported.
persist to output: /bnz/home/oracle/Middleware/user_projects/domains/IAM_domain/config/fmwconfig - done
Error: Failed to join security store, unable to locate diagnostics data.
Error: Join operation has failed.

Cause