When the schema name you set during deployment of WSRR does not match the one in database, WSRR will not correctly start, as it will not find the required tables. This article will tell you how to update the schema name which WSRR is trying to use, so you will be able to start WSRR successfully. This process applies to WSRR V8 and Oracle databases.
When starting WSRR, you may observe the following exception:
[7/23/13 10:28:56:810 CST] 00000042 api E
com.ibm.serviceregistry.ServiceRegistryActivityLoggingDBBean createAPICall (byte, Stringx4) GSR5000I: Captured exception :
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
INSERT INTO WSRR.SR_ACTIVITY_APICALL(CONTAINER_ID, API_TYPE, METHOD, ROOT_OBJECT,USERID, TIME_CREATED, ID) VALUES (?,?,?,?,?,?,WSRR.SEQ_SR_ACTIVITY_APICALL_ID.nextval) ID}
[7/23/13 10:28:56:809 CST] 00000042 OracleDataSto > findMappingClass for : Entry jva.sql.SQLSyntaxErrorException:
ORA-00942: table or view does not exist
In this case, the exception is caused because WSRR is looking for tables under schema name 'WSRR', but on inspection of the WSRR database, the mentioned tables are under defined under another schema name.
WSRR v8.0, Oracle 10g and Oracle 11g databases
Resolving the problem
You may resolve this by updating ServiceRegistry.ear during the application deployment process:
1. Stop the ServiceRegistry application.
2. Check ServiceRegistry application and click "export".
3. Save the ServiceRegistry ear to your computer.
4. Check ServiceRegistry application once more, and click "update".
5. Under 'Application update options', choose to load the exported ServiceRegistry.ear from step 3.
6. In the 'preparing for application update' page, click "Detailed", and ensure the 'Specify bindings to use' dropdown box lists 'merge new and existing bindings'. Click Next.
7. In the 'Application Security Warnings' page, click next.
8. In the Deployment steps list, go to 'Step 12: Map environment entries for EJB modules'
9. Change the value for the schema name you wish to change from <VALUE> (the schema name mentioned in the systemout log) to the correct schema name for your database.
10. Once you have made the schema changes, click on Step 18, and click to 'Finish' to complete application deployment process. WAS will now update the application in your environment. Once this completes, click 'Save' to save the changes to your configuration.
11. Restart ServiceRegistry.ear. The errors previously seen in the logs should now no longer occur.