My Oracle Support Banner

Unable To Join SecurityStore After Creating An OAM Domain (Doc ID 1498098.1)

Last updated on JULY 13, 2018

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


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]$ ./ /bnz/home/oracle/Middleware/Oracle_IDM1/common/tools/ -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
[] checkServiceSetup - done
Oct 9, 2012 11:48:25 AM
WARNING: Could not create credential store instance. Reason 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
[] updateServiceConfiguration - done
Oct 9, 2012 11:48:41 AM checkIfConfigurationValid
INFO: Audit store re-association not supported.
[] 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.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.