Topic
  • 8 replies
  • Latest Post - ‏2012-09-27T10:12:01Z by UteBaumbach
michaelw
michaelw
8 Posts

Pinned topic CDPMA1109E can't open file error when logging into OPM 5.1

‏2012-09-26T08:00:32Z |
All,

We're using OPM 5.1 on AIX. Everything's been working fine and then yesterday our support team needed to reboot the vm image that OPM is installed on. After the reboot I haven't been able to successfully connect to OPM. I get the error msg below when logging in through the web interface.

I searched for the CDPMA1109E msg id but couldn't find anything on it. Same with the -4223 error code. I find it strange that it's talking about a missing file on c: when our repository db is on AIX. There's no temp directory on our AIX image.

Anyone seen this before or know how to resolve?

CDPMA1109E

A connection to the repository database failed.

You cannot proceed without a connection to the repository database.
Details for SQLException: com.ibm.db2.jcc.am.SqlException: jcc1025710960http://3.63.81 Unable to open file c:\temp/trace_sds_8257. ERRORCODE=-4223, SQLSTATE=null, SQLState=<null>, ErrorCode=<0>.

Review the trace files to find the cause of the problem. Check the repository console and log files and trace files for more information in case the problem is also at the repository server.
Updated on 2012-09-27T10:12:01Z at 2012-09-27T10:12:01Z by UteBaumbach
  • UteBaumbach
    UteBaumbach
    55 Posts

    Re: CDPMA1109E can't open file error when logging into OPM 5.1

    ‏2012-09-26T08:49:27Z  
    Hi,
    if restarting OPM does not help then please attach the log files from the <OPM install path>/logs directory. Maybe we see something obvious.

    Regards
    Ute Baumbach
  • michaelw
    michaelw
    8 Posts

    Re: CDPMA1109E can't open file error when logging into OPM 5.1

    ‏2012-09-26T18:24:04Z  
    Thanks for the reply. Restarting OPM didn't work. The only other action I did last week was update the licensing from Try & Buy to the full Enterprise license. Otherwise it failed to come back up after a reboot of the system.
  • michaelw
    michaelw
    8 Posts

    Re: CDPMA1109E can't open file error when logging into OPM 5.1

    ‏2012-09-26T22:53:32Z  
    datatools.log
  • michaelw
    michaelw
    8 Posts

    Re: CDPMA1109E can't open file error when logging into OPM 5.1

    ‏2012-09-26T23:24:58Z  
    I'm not seeing my attachments coming through so I'll email them to you.
  • michaelw
    michaelw
    8 Posts

    Re: CDPMA1109E can't open file error when logging into OPM 5.1

    ‏2012-09-26T23:47:08Z  
    • michaelw
    • ‏2012-09-26T23:24:58Z
    I'm not seeing my attachments coming through so I'll email them to you.
    Figured it out...file was too large.
  • michaelw
    michaelw
    8 Posts

    Re: CDPMA1109E can't open file error when logging into OPM 5.1

    ‏2012-09-26T23:58:48Z  
    • michaelw
    • ‏2012-09-26T23:47:08Z
    Figured it out...file was too large.
    .
  • michaelw
    michaelw
    8 Posts

    Re: CDPMA1109E can't open file error when logging into OPM 5.1

    ‏2012-09-27T00:01:59Z  
    • michaelw
    • ‏2012-09-26T23:58:48Z
    .
    .
  • UteBaumbach
    UteBaumbach
    55 Posts

    Re: CDPMA1109E can't open file error when logging into OPM 5.1

    ‏2012-09-27T10:12:01Z  
    Hi,
    all of your posted log files are full with these error messages. They are happening during connection to the repository database. There are no additional indications in the files why this is happening.
    My current conclusion is that we have to look at the DB2 site for the cause and not on the OPM site. Have you tried restarting DB2 ? Do you see any problems in the db2diag.log file ? Can you connect from the command line to the repository database ?
    The log files that you posted belong all to the web console of OPM. Would be interesting to know whether the repository server faces the same problem. Do you see the message in the repository server log file db2pesrv.log as well ?
    If we don't get any hints from the DB2 site and if restarting DB2 does not help then I suggest to open a PMR. Probably some more trace and log files must be exchange to figure that out which is not possible via the forum.

    Regards
    Ute Baumbach