IDM SSO result step 3 taking long time
Article ID: 97961
Updated On:
Products
CA Identity Manager
CA Identity Governance
CA Identity Portal
Issue/Introduction
After installing Identity Manager on WebSphere, IM fails to start after stalling at step 3 as shown below.
[5/10/18 13:44:09:198 GMT] 00000070 SystemOut O 13:44:09,198 INFO [ims.Main] * Startup Step 3 : Attempting to start ServerCommandService [5/10/18 13:44:15:320 GMT] 00000070 SystemOut O 13:44:15,320 WARN [ims.tmt.servercommandservice] JMSException:com.ibm.websphere.sib.exception.SIResourceException caught connecting to message bus (may not be ready), waiting 1 second before trying again. [5/10/18 13:44:22:324 GMT] 00000070 SystemOut O 13:44:22,324 WARN [ims.tmt.servercommandservice] JMSException:com.ibm.websphere.sib.exception.SIResourceException caught connecting to message bus (may not be ready), waiting 1 second before trying again. [5/10/18 13:44:29:331 GMT] 00000070 SystemOut O 13:44:29,331 WARN [ims.tmt.servercommandservice] JMSException:com.ibm.websphere.sib.exception.SIResourceException caught connecting to message bus (may not be ready), waiting 1 second before trying again. [5/10/18 13:44:36:338 GMT] 00000070 SystemOut
00000033 SibMessage E [:] CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The data source has produced an unexpected exception: java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges
[5/10/18 13:44:09:198 GMT] 00000070 SystemOut O 13:44:09,198 INFO [ims.Main] * Startup Step 3 : Attempting to start ServerCommandService [5/10/18 13:44:15:320 GMT] 00000070 SystemOut O 13:44:15,320 WARN [ims.tmt.servercommandservice] JMSException:com.ibm.websphere.sib.exception.SIResourceException caught connecting to message bus (may not be ready), waiting 1 second before trying again. [5/10/18 13:44:22:324 GMT] 00000070 SystemOut O 13:44:22,324 WARN [ims.tmt.servercommandservice] JMSException:com.ibm.websphere.sib.exception.SIResourceException caught connecting to message bus (may not be ready), waiting 1 second before trying again. [5/10/18 13:44:29:331 GMT] 00000070 SystemOut O 13:44:29,331 WARN [ims.tmt.servercommandservice] JMSException:com.ibm.websphere.sib.exception.SIResourceException caught connecting to message bus (may not be ready), waiting 1 second before trying again. [5/10/18 13:44:36:338 GMT] 00000070 SystemOut
00000033 SibMessage E [:] CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The data source has produced an unexpected exception: java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges
Environment
Identity Manager
WebSphere
WebSphere
Cause
By default, the schema used by a messaging engine (ME) gets created when a new bus member gets created, i. e. when a server or cluster of servers becomes a bus member. (This default can be changed, by navigating to the panel for the ME in the administrative console, then clicking Message store and unchecking the check box labeled Create tables.) If the user (which by convention in Oracle is the schema name) does not have the required privileges (create, alter, delete, etc.), however, the schema creation will fail as noted in the Symptom section.
Resolution
When using Oracle as the database for the ME data store, ensure that either the user name and the schema name specified in the message store settings (see the link below) are the same, or (if user name and schema name are different) that the user has all of the privileges listed in the link below:
Database privileges:
JR47588: DOC:TUNING PROPERTIES LINK IS INCORRECT FOR ORACLE DATABASE PRIVILEGES
Configuring a messaging engine data store to use a data source:
After this has been done, the schema should be created.
Feedback
Yes
No
Powered by
