Topic
6 replies Latest Post - ‏2014-07-10T22:16:43Z by zaida.m
zaida.m
zaida.m
4 Posts
ACCEPTED ANSWER

Pinned topic Migrate Mysql to DB2 Error in db2gen.sh ERRORCODE=-4499, SQLSTATE=58009

‏2014-07-03T04:24:55Z |

Hi


I'm trying to migrate my data from Mysql to LUW DB2

I'm using the command line but when I run IBMDataMovementTool.sh command after all the parameters are set and during the process of testing Mysql connection and DB2 connection I see this error:

 

com.ibm.net.SocketKeepAliveParameters
com.ibm.db2.jcc.am.DisconnectNonTransientException: [jcc][t4][2055][11259][3.63.123] The database manager is not able to accept new requests, has terminated all requests in progress, 
or has terminated this particular request due to unexpected error conditions detected at the target system. ERRORCODE=-4499, SQLSTATE=58009
    at com.ibm.db2.jcc.am.fd.a(fd.java:323)
        at com.ibm.db2.jcc.t4.ab.W(ab.java:1404)
        at com.ibm.db2.jcc.t4.ab.y(ab.java:756)
        at com.ibm.db2.jcc.t4.ab.p(ab.java:726)
        at com.ibm.db2.jcc.t4.ab.l(ab.java:538)
        at com.ibm.db2.jcc.t4.ab.d(ab.java:147)
        at com.ibm.db2.jcc.t4.b.Zc(b.java:1360)
        at com.ibm.db2.jcc.t4.b.b(b.java:1278)
        at com.ibm.db2.jcc.t4.b.a(b.java:6230)
        at com.ibm.db2.jcc.t4.b.b(b.java:835)
        at com.ibm.db2.jcc.t4.b.b(b.java:758)
        at com.ibm.db2.jcc.t4.b.a(b.java:419)
        at com.ibm.db2.jcc.t4.b.a(b.java:394)
        at com.ibm.db2.jcc.t4.b.<init>(b.java:332)
        at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:231)
        at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:197)
        at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:472)
        at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:113)
        at java.sql.DriverManager.getConnection(DriverManager.java:582)
        at java.sql.DriverManager.getConnection(DriverManager.java:198)
        at ibm.DBData.getConnection(DBData.java:330)
        at ibm.DeployObjects.Open(DeployObjects.java:57)
        at ibm.DeployObjects.main(DeployObjects.java:754)
Exception in thread "main" java.lang.NullPointerException
        at ibm.DeployObjects.deployObject(DeployObjects.java:115)
        at ibm.DeployObjects.DeployAllObjectsInDB2(DeployObjects.java:683)
        at ibm.DeployObjects.main(DeployObjects.java:755)

 

I followed the prerequisites steps and also verified my db2 settings but can't figure out anything from this.
 

Is there any DB2 configuration that I need to double check?

I appreciate your help

 

Thank you !

  • nivanov
    nivanov
    14 Posts
    ACCEPTED ANSWER

    Re: Migrate Mysql to DB2 Error in db2gen.sh ERRORCODE=-4499, SQLSTATE=58009

    ‏2014-07-08T16:56:44Z  in response to zaida.m

    Are you able to connect to the database from the command line?

    db2 connect to mydb
    

    Also check the messages in db2diag.log at the time of the error.

    Updated on 2014-07-08T16:58:24Z at 2014-07-08T16:58:24Z by nivanov
    • zaida.m
      zaida.m
      4 Posts
      ACCEPTED ANSWER

      Re: Migrate Mysql to DB2 Error in db2gen.sh ERRORCODE=-4499, SQLSTATE=58009

      ‏2014-07-09T20:50:03Z  in response to nivanov

      HI

      I can connect from the command line

      But I have something for the db2diag.log, It says something about cryptographic errors:

      2014-07-01-11.05.41.999439-300 I1532037E2533         LEVEL: Error
      PID     : 24932                TID : 139861478598400 PROC : db2sysc 0
      INSTANCE: db2inst1             NODE : 000            DB   : TESTDB
      APPHDL  : 0-647                APPID: 127.0.0.1.38806.140701160541
      HOSTNAME: lx4222.austin.ibm.com
      EDUID   : 22                   EDUNAME: db2agent (TESTDB) 0
      FUNCTION: DB2 Common, Cryptography, cryptEncryptInit, probe:20
      MESSAGE : ECF=0x90000403=-1879047165=ECF_CRYPT_UNEXPECTED_ERROR
                Unexpected cryptographic error
      DATA #1 : Hex integer, 4 bytes
      0x00000000
      CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
        [0] 0x00007F341611A858 pdOSSeLoggingCallback + 0x268
        [1] 0x00007F3414CD328B /home/db2inst1/sqllib/lib64/libdb2osse.so.1 + 0x20228B
        [2] 0x00007F3414CD30B3 ossLog + 0xA3
        [3] 0x00007F341747EF68 cryptLogICCError + 0xA8
        [4] 0x00007F341747B031 cryptEncryptInit + 0x2B1
        [5] 0x00007F341747D844 cryptEncryptBuffer + 0x34
        [6] 0x00007F34165CB79C _Z18sqlexProcessToken2P14db2UCinterfacePcjP16SQLEX_AUTHINFO_TP13SQLO_MEM_POOL + 0x27C
        [7] 0x00007F34165C8C63 _Z20sqlexEngAuthenticateP14db2UCinterface + 0x2F3
        [8] 0x00007F34163EC706 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x1203706
        [9] 0x00007F34163EAA01 _ZN14sqeApplication13AppLocalStartEP14db2UCinterface + 0xF1
        [10] 0x00007F34165B1800 _Z11sqlelostWrpP14db2UCinterface + 0x20
        [11] 0x00007F34165B0ACF _Z14sqleUCengnInitP14db2UCinterfacet + 0x52F
        [12] 0x00007F34165AFD9F sqleUCagentConnect + 0x38F
        [13] 0x00007F3416667399 _Z18sqljsConnectAttachP13sqljsDrdaAsCbP14db2UCinterface + 0xD9
        [14] 0x00007F34166428DD _Z16sqljs_ddm_accsecP14db2UCinterfaceP13sqljDDMObject + 0x6D
        [15] 0x00007F341663C996 _Z17sqljsParseConnectP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCinterface + 0x66
        [16] 0x00007F341925CC93 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 0x3A3
        [17] 0x00007F3416636B2B /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x144DB2B
        [18] 0x00007F341663577F /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x144C77F
        [19] 0x00007F34166336E3 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x144A6E3
        [20] 0x00007F3416633473 _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xF3
        [21] 0x00007F34163DA811 _ZN8sqeAgent6RunEDUEv + 0x821
        [22] 0x00007F34173C9F63 _ZN9sqzEDUObj9EDUDriverEv + 0xF3
        [23] 0x00007F34173C9E69 _Z10sqlzRunEDUPcj + 0x9
        [24] 0x00007F3416E5D501 sqloEDUEntry + 0x2A1
        [25] 0x000000365B207851 /lib64/libpthread.so.0 + 0x7851
        [26] 0x000000365AEE890D clone + 0x6D
      

       

      • nivanov
        nivanov
        14 Posts
        ACCEPTED ANSWER

        Re: Migrate Mysql to DB2 Error in db2gen.sh ERRORCODE=-4499, SQLSTATE=58009

        ‏2014-07-09T21:06:11Z  in response to zaida.m

        1. Try to connect to DB2 using the same user ID and password you have configured form IDMT:

        db2 connect to mydb user myuser using mypass
        

        2. Make sure that the IBM JDK, supplied with DB2, is used by IDMT when it runs.

        • zaida.m
          zaida.m
          4 Posts
          ACCEPTED ANSWER

          Re: Migrate Mysql to DB2 Error in db2gen.sh ERRORCODE=-4499, SQLSTATE=58009

          ‏2014-07-10T04:27:59Z  in response to nivanov

          I tried the command in step 1 but  I got
          SQL1042C  An unexpected system error occurred.  SQLSTATE=58004

          When I saw this error I went to see db2diag.log and I see the same cryptographic error described above.

          I also saw a couple of info message that ends with this line:
          Warning: The DB2 Administration Server cannot be found on the system. Any DB2 functions that require the DB2 Administration Server will be disabled.

          But when I tried db2admin stop/start it didn't show any error messages

          • nivanov
            nivanov
            14 Posts
            ACCEPTED ANSWER

            Re: Migrate Mysql to DB2 Error in db2gen.sh ERRORCODE=-4499, SQLSTATE=58009

            ‏2014-07-10T12:55:17Z  in response to zaida.m

            Don't worry about the administration server. Did you check the JDK version?

            What DB2 version are you using? What Linux (it is Linux, isn't it) distribution and kernel version?

            What is the server authentication setting?  (db2 get dbm cfg | grep AUTH)

            Updated on 2014-07-10T13:02:05Z at 2014-07-10T13:02:05Z by nivanov
            • zaida.m
              zaida.m
              4 Posts
              ACCEPTED ANSWER

              Re: Migrate Mysql to DB2 Error in db2gen.sh ERRORCODE=-4499, SQLSTATE=58009

              ‏2014-07-10T22:16:43Z  in response to nivanov

              Hi 

              JDK version was OK
              I'm using DB2 V10.1 on a GNU/Linux  2.6.32-358.el6.x86_64

              Authentication setting as SERVER

              I applied the fixpack 10.1 fp4 and that did the trick. Now I'm able to connect locally and remote to my DB2 Database 
              I ran the IDMT after this and connection issues are gone, I can see my tables there I only need to clean my data, etc.

              Thanks so much for your help!