I hit the following exception when trying to generate and import a new Deployment Environment: -
25/03/13 20:41:07:936 GMT] 0000002c BSpaceConfigL I BSpaceConfigureDBTask execute CWMO1116I: Using the existing data source with jndi name 'jdbc/mashupDS'.
[25/03/13 20:41:09:528 GMT] 0000002c WBITopologyMg E com.ibm.wbiserver.nd.topology.WBITopologyMgr configureTopology CWLDB9016E: The generation for deployment environment DepEnvBam8011 failed. Reason: CWLDB9014E: The configuration of component WBI_BSPACE failed. Reason com.ibm.bspace.admin.BSpaceConfigException: java.sql.SQLException: ORA-01435: user does not exist
.. If in doubt, discard the changes and do not save the failed configuration to the master repository.
[25/03/13 20:41:09:528 GMT] 0000002c WBITopologyMg E com.ibm.wbiserver.nd.topology.WBITopologyMgr configureTopology CWLDB9016E: The generation for deployment environment DepEnvBam8011 failed. Reason: CWLDB9014E: The configuration of component WBI_BSPACE failed. Reason com.ibm.bspace.admin.BSpaceConfigException: java.sql.SQLException: ORA-01435: user does not exist
.. If in doubt, discard the changes and do not save the failed configuration to the master repository.
Thankfully, I quickly picked this Technote ( for IBM WebSphere Enterprise Service Bus ): -
which says, in part: -
Environment
This only occurs when the profiles are created based on an Oracle Common Database.
This issue was observed specifically with Oracle 10.2.
Resolving the problem
To work around this issue:
On Step 5. of the Deployment Environment wizard untick the Create Tables box for the Business Space data source and then complete the wizard as normal.
If you want to use Business Space you must then do the following:
1) Locate the Business Space database configuration scripts in (for example in WESB)
${WESB_HOME}/profiles/${YOURDMGR}/dbscripts/BusinessSpace/Oracle/${YOURDBNAME}
2) Copy the scripts to your Oracle database server
3) Run the configBusinessSpaceDB script, providing the appropriate SYSTEM user name and password
4) Restart the deployment manager, all nodes and all servers
This only occurs when the profiles are created based on an Oracle Common Database.
This issue was observed specifically with Oracle 10.2.
Resolving the problem
To work around this issue:
On Step 5. of the Deployment Environment wizard untick the Create Tables box for the Business Space data source and then complete the wizard as normal.
If you want to use Business Space you must then do the following:
1) Locate the Business Space database configuration scripts in (for example in WESB)
${WESB_HOME}/profiles/${YOURDMGR}/dbscripts/BusinessSpace/Oracle/${YOURDBNAME}
2) Copy the scripts to your Oracle database server
3) Run the configBusinessSpaceDB script, providing the appropriate SYSTEM user name and password
4) Restart the deployment manager, all nodes and all servers
Once I followed the circumvention ( unstick the Create Tables box for the Business Space data source ), all was well.
:-)
No comments:
Post a Comment