Skip to Content

R3trans failing after refresh

HI Guys,

Target system is not coming up after the refresh , when i try execute R3trans it's ending with return code 12 .

translog

4 ETW000 [dev trc ,00000] Supported features: 20 0.008703

4 ETW000 [dev trc ,00000] ..retrieving configuration parameters 21 0.008724

4 ETW000 [dev trc ,00000] ..done 98 0.008822

4 ETW000 [dev trc ,00000] Running with UTF-8 Unicode 31 0.008853

4 ETW000 [dev trc ,00000] Running with CLI driver. 6186 0.015039

4 ETW000 [dev trc ,00000] Thu May 5 09:31:28 2011 638286 0.653325

4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1766] CON = 0 (BEGIN) 33 0.653358

4 ETW000 [dev trc ,00000] &+ DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication

4 ETW000 41 0.653399

4 ETW000 [dev trc ,00000] &+ protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected:

4 ETW000 36 0.653435

4 ETW000 [dev trc ,00000] &+ "10.40.30.38". Communication function detecting the error: "connect". Protocol specific error code(s): "79", "*"

4 ETW000 37 0.653472

4 ETW000 [dev trc ,00000] &+ , "*". SQLSTATE=08001

4 ETW000 36 0.653508

4 ETW000 [dev trc ,00000] &+

4 ETW000 36 0.653544

4 ETW000 [dev trc ,00000] &+

4 ETW000 38 0.653582

4 ETW000 [dev trc ,00000] &+

4 ETW000 37 0.653619

4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1766] (END) 21 0.653640

4 ETW000 [dbdb6.c ,00000] *** ERROR => DbSlConnect to 'CRD' as 'sapcrd' failed 68 0.653708

2EETW169 no connect possible: "DBMS = DB6 --- DB2DBDFT = 'CRD'"

trans.log: END

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on May 05, 2011 at 07:44 AM

    Hi,

    check if a connect to the database using DB2 CLP works. If yes, check if the connection parameters in file /usr/sap/SAPSID/SYS/global/db6/db2cli.ini are correct.

    Regards

    Frank

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      I assume that your connection problem is not solved .... so I suggest to take action 😉

      Manually changing permissions in the sqllib directory is certainly not a good idea. Some files need to be owned by root and need a SUID bit. The supported and tested way to solve the problem is:

      install a new DB2 copy as user root ( e.g. in /db2/db2sid/db2_software_new )

      switch your DB2 instance over to the new copy using an instance update ( db2iupdt )

      db2iupd will chnage all the links in the sqllib directory and correct the ownership/permissions of the files in this directoy.

      Regards

      Frank

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.