IBM Support

CWRCV0007E: Unable to use the failed event manager after migrating to any version of WebSphere Process Server V7.0 with backend DB2zOSV9 database

Troubleshooting


Problem

After upgrading WebSphere Process Server from any version of V6.1 or V6.0 to any version of V7.0 (7.0.0.1,7.0.0.2,7.0.0.3) , the failed event manager does not work if the back-end database for the common database is using IBM DB2 V9 on z/OS. You will see error CWRCV0007E and ERRORCODE=-4461, SQLSTATE=42815.

Symptom

    After migrating to V7.0.0.1, 7.0.0.2 or 7.0.0.3 , in the CommonDB database, under the FailedEvents table, EsQualified and EventType columns are missing. When you try to select all failed events using the failed event manager, you see the following exception in the systemout.log file and FFDC of the server where the failed event manager application is running:


    [9/24/10 10:41:12:892 CEST] 00000057 Recovery      E com.ibm.wbiserver.management.FailedEventManagerMBean getAllFailedEvents(int) CWRCV0007E: The failed events cannot be retrieved.


    [9/24/10 10:41:12:877 CEST]     FFDC Exception:javax.ejb.FinderException SourceId:com.ibm.wbiserver.management.FailedEventManagerMBean.getAllFailedEvents(int) ProbeId:261 Reporter:com.ibm.wbiserver.management.FailedEventManagerMBean@5df05df
    javax.ejb.FinderException: All the events could not be retrieved due to java.lang.Exception: com.ibm.db2.jcc.am.io: [jcc][t4][10145][10897][3.57.82] Invalid parameter 15: Parameter index is out of range. ERRORCODE=-4461, SQLSTATE=42815
    at com.ibm.wbiserver.manualrecovery.ejb.FailedEventManagerEJBBean.getAllFailedEvents(FailedEventManagerEJBBean.java:502)
    at com.ibm.wbiserver.manualrecovery.ejb.EJSRemoteStatelessFailedEventManagerEJB_1411c110.getAllFailedEvents(Unknown Source)
    at com.ibm.wbiserver.manualrecovery.ejb._FailedEventManagerEJB_Stub.getAllFailedEvents(_FailedEventManagerEJB_Stub.java:328)
    at com.ibm.wbiserver.management.FailedEventManagerMBean.getAllFailedEvents(FailedEventManagerMBean.java:445)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:37)
    at sun.reflect.GeneratedMethodAccessor102.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:244)
    at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1086)
    at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:967)

    .....



    [9/24/10 10:41:12:894 CEST]     FFDC Exception:javax.management.MBeanException SourceId:com.ibm.ws.management.AdminServiceImpl.invoke ProbeId:679 Reporter:com.ibm.ws.management.AdminServiceImpl$1@66ed66ed
    javax.management.MBeanException: Exception thrown in RequiredModelMBean while trying to invoke operation getAllFailedEvents
    at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1113)
    at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:967)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)
    at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1320)
    at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
    at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1213)
    at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:181)
    at com.ibm.ws.management.connector.ipc.CallRouter.route(CallRouter.java:242)
    at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink.doWork(IPCConnectorInboundLink.java:353)
    at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink$IPCConnectorReadCallback.complete(IPCConnectorInboundLink.java:595)
    at
    ...
    ....
    Caused by: com.ibm.wbiserver.manualrecovery.exceptions.FailedEventReadException: All the events could not be retrieved due to java.lang.Exception: com.ibm.db2.jcc.am.io: [jcc][t4][10145][10897][3.57.82] Invalid parameter 15: Parameter index is out of range. ERRORCODE=-4461, SQLSTATE=42815
    at com.ibm.wbiserver.management.FailedEventManagerMBean.getAllFailedEvents(FailedEventManagerMBean.java:452)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:37)
    at sun.reflect.GeneratedMethodAccessor102.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:244)
    at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1086)
    ... 19 more

Cause

Following SQL scripts, which are used for upgrading DB2zOSV9 and DB2zOSV8 files, are missing under the Process_Server_Installation/commonDB/DB2zOSV9 directory.


    wbiserver_upgradeSchema610_Recovery.sql wbiserver_upgradeSchema602_Recovery.sql
When you upgrade the commonDB database during migration, the FailedEvents table is not upgraded.

Resolving The Problem

The SQL scripts that are used for upgrading DB2zOSV9 and DB2zOSV8 are the same. The missing wbiserver_upgradeSchema6xx_Recovery.sql file does not exist under the Process_Server_Installation/commonDB/DB2zOSV9 directory.

You can use the file wbiserver_upgradeSchema6xx_Recovery.sql from the DB2zOSV8 directory to upgrade your DB2zOSV9 database.

You can find additional instructions for a manual common database upgrade process in the Upgrading the Common database schema topic within the information center.

The missing scripts are included in Version 7.0.0 Fix Pack 4 using APAR JR37843.

[{"Product":{"code":"SSQH9M","label":"WebSphere Process Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Failed Events","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF035","label":"z\/OS"},{"code":"PF033","label":"Windows"},{"code":"PF027","label":"Solaris"},{"code":"PF016","label":"Linux"},{"code":"PF010","label":"HP-UX"}],"Version":"7.0;7.0.0.3;7.0.0.2;7.0.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21449593

Page Feedback