0 Replies Latest reply on Jan 3, 2011 10:17 AM by 764888

    Loadjava produce a core dump.

    764888
      Hi everybody,

      Here is a description of my problem :

      When I try to load some jar in the database using loadjava it core dumps.
      The weird thing is that on another environment where the same JVM is installed it works.

      Here is a snapshot of my configuration.
      DEV_env is working
      TARGET_env is not except with the little workaround explained below.

      DEV_env
      DEV@machineDEV:
      /u01/app/oracle/product/11107/jdk/jre/bin> ./java -version
      java version "1.5.0"
      Java(TM) 2 Runtime Environment, Standard Edition (build pap64dev-20070201 (SR4))
      IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423-20070201 (JIT enabled)
      J9VM - 20070131_11312_BHdSMr
      JIT - 20070109_1805ifx1_r8
      GC - 200701_09)
      JCL - 20070126
      OK

      TARGET_env     
      PRD@machinePRD [u01/app/oracle/product/11107/jdk/jre/bin]
      ] ./java -version
      java version "1.5.0"
      Java(TM) 2 Runtime Environment, Standard Edition (build pap64dev-20070201 (SR4))
      IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423-20070201 (JIT enabled)
      J9VM - 20070131_11312_BHdSMr
      JIT - 20070109_1805ifx1_r8
      GC - 200701_09)
      JCL - 20070126
      KO     


      DEV_env
      DEV@ machineDEV:/usr/java5_64/jre/bin>
      ./java -version
      java version "1.5.0"
      Java(TM) 2 Runtime Environment, Standard Edition (build pap64devifx-20090327 (SR9-SSU ))
      IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423-20081129 (JIT enabled)
      J9VM - 20081126_26240_BHdSMr
      JIT - 20081112_1511ifx1_r8
      GC - 200811_07)
      JCL - 20090327
      OK

      TARGET_env
      PRD@machinePRD[usr/java5_64/jre/bin]
      ] ./java -version
      java version "1.5.0"
      Java(TM) 2 Runtime Environment, Standard Edition (build pap64dev-20091106a (SR11 ))
      IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423-20091104 (JIT enabled)
      J9VM - 20091103_45935_BHdSMr
      JIT - 20091016_1845_r8
      GC - 20091026_AA)
      JCL - 20091106
      OK ORACLE workaround (see below)     



      As you probably know the first action of the loadjava script is to redefine the JAVA_HOME.
      By commenting_ these lines, loading my jars works.

      The loadjava script is in this directory :
      /u01/app/oracle/product/11107/bin/


      Loadjava sample

      #! /bin/sh
      #
      # %W% %E%
      #

      _#unset JAVA_HOME_
      _#JAVA_HOME=/u01/app/oracle/product/11107/jdk/jre/_
      _#export JAVA_HOME_…

      This make it work (because it picks usr/java5_64/jre/bin as JAVA_HOME) but it is absolutely not a good workaround to modify ORACLE scripts.


      My command line is :

      loadjava -v -user uuser/pwd@SID -schema user_schema -stoponerror -r my_path/ingrianlog4j-1.2.9.jar

      The dump message is :

      Unhandled exception
      Type=Segmentation error vmState=0x00000000
      J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
      Handler1=09001000A0973C78 Handler2=09001000A096B538
      R0=0000000000000000 R1=0FFFFFFFFFFFC4C0 R2=00000000000002B2 R3=00000000000002FF
      ...
      ...
      Module=/u01/app/oracle/product/11107/jdk/jre/bin/libj9jit23.so
      Module_base_address=0900000006959000
      Target=2_30_20070131_11312_BHdSMr (AIX 6.1)
      CPU=ppc64 (64 logical CPUs) (0x3ac0000000 RAM)
      JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.


      Do you know where it could come from ?
      Is there any specifics environment variable I can check to make it work ?


      Thanks for your help.

      Matt Matt

      Edited by: Matt Matt on 3 janv. 2011 02:13
      Add : core dump message