[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dbstars

Title:DBSTARS Conference
Moderator:BROKE::BASTINE
Created:Wed Feb 02 1994
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:791
Total number of notes:1521

743.0. "desc of some db2 errors using trace (all ibm problem)" by BROKE::BITHER () Fri Jan 31 1997 11:06

Information on db2 errors that might show up in an rtg/db2 trace:
----------------------------------------------------------------

Note 1110.22                      Dbi bugcheck                          22 of 22
ORAREP::EDSCLU::WHITE                                50 lines  23-JAN-1997 12:40
--------------------------------------------------------------------------------
I cut the error messages out of your previous postings in order to
clarify the root problem.  That way you won't have to post every
error message here asking what to do.


1) These two error message sequences are the real problem:


   %LDRV-E-LU62_SUPP, -SYSTEM-F-PATHLOST, path to network partner node lost
   %LDRV-E-LU62_SUPP, -SNALU62-E-GATCOM, error communicating with Gateway node
   %LDRV-E-LU62_SUPP, %SNALU62-E-RESFRET, resource failure retry
   %LDRV-E-GNL_COMMSVC_ERR, communication service error


   %LDRV-E-LU62_SUPP, -SNALU62-E-EXIT, Gateway server task terminated
   %LDRV-E-LU62_SUPP, -SNALU62-E-GATCOM, error communicating with Gateway node
   %LDRV-E-LU62_SUPP, %SNALU62-E-RESFRET, resource failure retry
   %LDRV-E-GNL_COMMSVC_ERR, communication service error


   You are having DECnet problems which is breaking the link between the
   node with DBI and the SNA Gateway.  The DB2 Gateway has a timing problem
   in that it may bugcheck *after* the link is dropped.  So, if you fix the
   network the bugcheck goes away.  You can install DBI7 and the bugchecks
   will *probably* go away, but you'll still get these error sequences.

   Your DECnet people should have the skills to detect why links are dropping.
   Get them to look at the network and fix the base problem!


2) This error message is indeed an IBM problem.  If you see the SSCP
   deactivating a session then call your IBM side.  These do not
   normally dump, however, it could cause the timing sequence which DBI7 fixes.

   %LDRV-E-LU62_SUPP, -SNA-E-LOGUNIDEA, SSCP has deactivated the session
   %LDRV-E-LU62_SUPP, -SNALU62-E-NOTACT, SNA session no longer active
   %LDRV-E-LU62_SUPP, %SNALU62-E-RESFRET, resource failure retry
   %LDRV-E-GNL_COMMSVC_ERR, communication service error

3) Any messages with DFHxxxxxx or DSNTxxxxxx appearing in the
   %LDRV-E-LU62_SUPP text are generated either by CICS or by DB2.
   These do not cause dumps.

   %LDRV-E-LU62_SUPP, -SNALU62-E-HOSTERR, error returned from host,<CR>
        DFHAC2206 21:38:44 RJAACICS TRANSACTION DC20 HAS FAILED WITH ABE
        ND AEY9. RESOURCE BACKOUT WAS SUCCESSFUL.  
   %LDRV-E-LU62_SUPP, %SNALU62-E-DEABPR, deallocate abend program
   %LDRV-E-GNL_SRVR_ERROR, server software terminated abnormally


T.RTitleUserPersonal
Name
DateLines