Topic
2 replies Latest Post - ‏2013-02-03T01:29:26Z by jesus29
jesus29
jesus29
19 Posts
ACCEPTED ANSWER

Pinned topic Issue after backing up WPS DBs - table COMMONDB.SEQ_W_LIT_LONG_ID

‏2013-01-05T10:09:16Z |
Hello all,

We are in the process of installing a new version of our applications. Before installing the new ones we have backed up the WPS DBs and after doing it we see that the server is starting with some unexpected errors.

Errors like the one below are appearing frequently. We think that this issue is related to the lack of privileges when accessing the COMMONDB.SEQ_W_LIT_LONG_ID table and are about to change those privileges.

Does anybody know what the table COMMONDB.SEQ_W_LIT_LONG_ID is used for?

Does anybody know if changing the privileges will cause any problem?

This is happening in production and we have got only a few hours to solve the issue so will appreciate a lot if someone could provide any useful information.

04/01/13 23:43:03:485 GMT FFDC Exception:com.ibm.ws.repository.RepositoryRuntimeException SourceId:com.ibm.ws.lifecycle.runtime.component.LifeCycleComponentImpl.start ProbeId:108 Reporter:com.ibm.ws.lifecycle.runtime.component.LifeCycleComponentImpl@757f757f
com.ibm.ws.repository.RepositoryRuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'internal.databaseCertifier' defined in class path resource http://com/ibm/tyto/jdbc/spring/jdbc-wsf-storage.beans.xml: Invocation of init method failed; nested exception is org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar http://SELECT nextval for COMMONDB.SEQ_W_LIT_LONG_ID FROM sysibm.sysdummy1; nested exception is com.ibm.db2.jcc.am.io: DB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=WPSDB;USAGE;COMMONDB.SEQ_W_LIT_LONG_ID, DRIVER=3.57.82
at com.ibm.ws.repository.impl.RepositoryInstance.initGovernedAccess(RepositoryInstance.java:98)
at com.ibm.ws.repository.impl.RepositoryInstance.<init>(RepositoryInstance.java:61)
at com.ibm.ws.repository.impl.RepositoryFactory.getRepositoryInstance(RepositoryFactory.java:74)
at com.ibm.ws.repository.osgi.RepositoryUtil.getWithinCustomizedLogging(RepositoryUtil.java:368)
at com.ibm.ws.repository.osgi.RepositoryUtil.access$700(RepositoryUtil.java:51)
at com.ibm.ws.repository.osgi.RepositoryUtil$7.call(RepositoryUtil.java:318)
at com.ibm.ws.repository.osgi.RepositoryUtil$7.call(RepositoryUtil.java:316)
at com.ibm.ws.fabric.support.logging.LoggingConfiguration.runWithAdjustedLogging(LoggingConfiguration.java:48)
at com.ibm.ws.repository.osgi.RepositoryUtil.getWithinPrivileged(RepositoryUtil.java:316)
at com.ibm.ws.repository.osgi.RepositoryUtil.getWithinPrivileged(RepositoryUtil.java:280)
at com.ibm.ws.repository.osgi.RepositoryUtil.access$600(RepositoryUtil.java:51)
at com.ibm.ws.repository.osgi.RepositoryUtil$6.run(RepositoryUtil.java:266)
at com.ibm.ws.repository.osgi.RepositoryUtil$6.run(RepositoryUtil.java:264)
at java.security.AccessController.doPrivileged(AccessController.java:202)

Thank you very much in advance,

Jesus
Updated on 2013-02-03T01:29:26Z at 2013-02-03T01:29:26Z by jesus29
  • SystemAdmin
    SystemAdmin
    3556 Posts
    ACCEPTED ANSWER

    Re: Issue after backing up WPS DBs - table COMMONDB.SEQ_W_LIT_LONG_ID

    ‏2013-02-01T18:34:28Z  in response to jesus29
    Did you ever resolve this issue?
  • jesus29
    jesus29
    19 Posts
    ACCEPTED ANSWER

    Re: Issue after backing up WPS DBs - table COMMONDB.SEQ_W_LIT_LONG_ID

    ‏2013-02-03T01:29:26Z  in response to jesus29
    yes, we applied correct rights to some user/database and then it was ok