Topic
  • 3 replies
  • Latest Post - ‏2012-03-15T13:45:20Z by SUGS_Brian_Trapp
jmueller
jmueller
26 Posts

Pinned topic CDPMA5101E

‏2010-08-10T11:54:35Z |
Hello OPM Team,

First thanks for the great work to build such a tool. It's really great.

But... I believe there is a problem within my environment:
Sometimes the session ends an the WAS on the AIX machine is crashed. I don't not why.

Today another error(exeption) occured:
CDPMA5101E
The metric results cannot be created.
An internal error occurred while creating the metric results. Details for SQLException: jcct4106512306http://3.58.90 Caught java.io.CharConversionException. See attached Throwable for details. ERRORCODE=-4220, SQLSTATE=null, SQLState=<null>, ErrorCode=<-4220>.
Collect trace files and contact IBM Software Support. You can also review the trace files to find the cause of the problem.

And the connection was lost.

root@r7l01 [/opt/IBM/OPM/bin]>./WASstatus.sh
ADMU0116I: Tool information is being logged in file
/opt/IBM/OPM/appServer/profiles/AppSrv01/logs/server1/serverStatus.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0500I: Retrieving server status for server1
ADMU0509I: The Application Server "server1" cannot be reached. It appears to be
stopped.
Environment:
System with 4 cpu's and 8GB RAM

db2dpp@r7l01
[/db2/db2dpp]> db2 '? sql4220'
SQL10007N Message "4220" could not be retrieved. Reason code: "4".
db2dpp@r7l01
[/db2/db2dpp]> oslevel -s
6100-02-03-0909

db2dpp@r7l01
[/db2/db2dpp]> db2level
DB21085I Instance "db2dpp" uses "64" bits and DB2 code release "SQL09072" with
level identifier "08030107".
Informational tokens are "DB2 v9.7.0.2", "s100514", "IP23082", and Fix Pack
"2".
Product is installed at "/opt/IBM/db2/V9.7".

Thanks and best regards,
Joachim
Updated on 2012-03-15T13:45:20Z at 2012-03-15T13:45:20Z by SUGS_Brian_Trapp
  • UteBaumbach
    UteBaumbach
    55 Posts

    Re: CDPMA5101E

    ‏2010-08-10T14:34:24Z  
    Hello Joachim,
    regarding the java.io.CharConversionException. During which action did you get this error in the Web UI ?
    This error can happen if the collected data contain non-ascii characters, for example SQL statements that contain German characters like ä, ü, ö.
    The workaround would be the following: In the OPM DB2 instance set DB2CODPAGE=1208 as DB2 registry variable, restart DB2 and OPM ( pestop/pestart ).

    Regarding the WAS crash. Best would be if you could open a PMR which can be routed then to the WAS queue to analyze that. Would that be possible for you ? So far we have seen WAS crashes due to AIX problems, where one is fixed with APAR IZ73931 http://www-01.ibm.com/support/docview.wss?uid=isg1IZ73931 and another WAS security problem is fixed in AIX 6.1.-005. We have also seen WAS crashes due to java problems which are fixed with IBM Java Development Kit 1.6 Fix Pack SR7 or SR8.

    Best regards
    Ute Baumbach
  • jmueller
    jmueller
    26 Posts

    Re: CDPMA5101E

    ‏2010-08-11T13:42:24Z  
    Hello Joachim,
    regarding the java.io.CharConversionException. During which action did you get this error in the Web UI ?
    This error can happen if the collected data contain non-ascii characters, for example SQL statements that contain German characters like ä, ü, ö.
    The workaround would be the following: In the OPM DB2 instance set DB2CODPAGE=1208 as DB2 registry variable, restart DB2 and OPM ( pestop/pestart ).

    Regarding the WAS crash. Best would be if you could open a PMR which can be routed then to the WAS queue to analyze that. Would that be possible for you ? So far we have seen WAS crashes due to AIX problems, where one is fixed with APAR IZ73931 http://www-01.ibm.com/support/docview.wss?uid=isg1IZ73931 and another WAS security problem is fixed in AIX 6.1.-005. We have also seen WAS crashes due to java problems which are fixed with IBM Java Development Kit 1.6 Fix Pack SR7 or SR8.

    Best regards
    Ute Baumbach
    Hello Ute,

    I believe that we don't use "umlauts" within our sql statement but I'm not the developer.
    I don't know where the error occured. So I have to watch OPM over a longer time.

    Regarding the WAS crash I will open a PMR after my vacation in tweo weeks. The APAR ist not yet installed in our environment and the JDK is up to date:

    java version "1.6.0"
    Java(TM) SE Runtime Environment (build pap6460sr8-20100409_01(SR8))
    IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr8-20100401_55940 (JIT enabled, AOT enabled)
    J9VM - 20100401_055940
    JIT - r9_20100401_15339
    GC - 20100308_AA)
    JCL - 20100408_01

    for another problem we had with OPM. Our first use of this forum.

    Best regards and hoping the weather in Germany will be sunny...
    Joachim
  • SUGS_Brian_Trapp
    SUGS_Brian_Trapp
    1 Post

    Re: CDPMA5101E

    ‏2012-03-15T13:45:20Z  
    • jmueller
    • ‏2010-08-11T13:42:24Z
    Hello Ute,

    I believe that we don't use "umlauts" within our sql statement but I'm not the developer.
    I don't know where the error occured. So I have to watch OPM over a longer time.

    Regarding the WAS crash I will open a PMR after my vacation in tweo weeks. The APAR ist not yet installed in our environment and the JDK is up to date:

    java version "1.6.0"
    Java(TM) SE Runtime Environment (build pap6460sr8-20100409_01(SR8))
    IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr8-20100401_55940 (JIT enabled, AOT enabled)
    J9VM - 20100401_055940
    JIT - r9_20100401_15339
    GC - 20100308_AA)
    JCL - 20100408_01

    for another problem we had with OPM. Our first use of this forum.

    Best regards and hoping the weather in Germany will be sunny...
    Joachim
    I know this is old, but I just ran across this and wanted to share the fix that worked for me. We added "-Ddb2.jcc.charsetDecoderEncoder=3" to our java arguments, and that mapped the naughty characters to null so the SQL could continue. Here's a link to a DB2 doc that talks about the root cause: https://www-304.ibm.com/support/docview.wss?uid=swg21412846
    -B. Trapp