Question on Error Return Code SQL0902 Reson Code 18

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • globomike
    #1

    Question on Error Return Code SQL0902 Reson Code 18

    Hi,

    can anybody tell me what the reason code 18 means in combination with
    a SQL0902 error?
    It would be helpful to know details about the reason code but I could
    not find any details about that code.

    Here is the full error message (out of a DataStage job)

    E_STG_CRM_PROFI LE..xfm3: [IBM][CLI Driver] SQL0902C A system error
    (reason code = "18") occurred. Subsequent SQL statements cannot be
    processed. SQLSTATE=58005

    [IBM][CLI Driver] SQL30081N A communication error has been detected.
    Communication protocol being used: "TCP/IP". Communication API being
    used: "SOCKETS". Location where the error was detected:
    "10.21.16.5 8". Communication function detecting the error: "recv".
    Protocol specific error code(s): "10055", "*", "*". SQLSTATE=08001

    SQLFetch: Error retrieving results from server.


    Thanks in advance
    Michael

    Tags: None
    • thiyagu
      #2
      Re: Question on Error Return Code SQL0902 Reson Code 18

      On Nov 5, 8:31 pm, globomike <M_Tiefenbac... @gmx.dewrote:
      Hi,
      >
      can anybody tell me what the reason code 18 means in combination with
      a SQL0902 error?
      It would be helpful to know details about the reason code but I could
      not find any details about that code.
      >
      Here is the full error message (out of a DataStage job)
      >
      E_STG_CRM_PROFI LE..xfm3: [IBM][CLI Driver] SQL0902C A system error
      (reason code = "18") occurred. Subsequent SQL statements cannot be
      processed. SQLSTATE=58005
      >
      [IBM][CLI Driver] SQL30081N A communication error has been detected.
      Communication protocol being used: "TCP/IP". Communication API being
      used: "SOCKETS". Location where the error was detected:
      "10.21.16.5 8". Communication function detecting the error: "recv".
      Protocol specific error code(s): "10055", "*", "*". SQLSTATE=08001
      >
      SQLFetch: Error retrieving results from server.
      >
      Thanks in advance
      Michael
      Hi,

      check the service configured with SVCE_NAME in dbm cfg. Seems that
      client couldn't connect to the specified port

        Comment

        • Eric.Jones
          #3
          Re: Question on Error Return Code SQL0902 Reson Code 18

          globomike wrote:
          Hi,
          >
          can anybody tell me what the reason code 18 means in combination with
          a SQL0902 error?
          It would be helpful to know details about the reason code but I could
          not find any details about that code.
          >
          The SQL0902C message usually implies bad things have happened in the DB.
          For the system error specifics (rc=18), you have to check your platform.
          (Windows, AIX, Solaris, etc.) Most POSIX compliant platforms ie. AIX
          (/usr/include/sys/errno.h) show 18 mapped to EXDEV.
          >
          [IBM][CLI Driver] SQL30081N A communication error has been detected.
          Communication protocol being used: "TCP/IP". Communication API being
          used: "SOCKETS". Location where the error was detected:
          "10.21.16.5 8". Communication function detecting the error: "recv".
          >
          In many cases the -902 will result in DB2 marking the DB as "Bad".
          All further (re)connections to the DB will be refused, as a precaution
          to avoid propagating possibly corrupt data. So the SQL30081N sometimes
          can cause confusion about what's really wrong.

          Best to check in the DB2 notification log for database marked bad msgs.
          Also examine the db2diag.log file for more detailed info around the time
          when the SQL0902 error first occurred. You may be able to narrow the
          scope by which function was executing when the error happened.


          Eric

            Comment

            Previous template Next
            Working...