Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Need help with below DB2 error

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
ashek15

New User


Joined: 20 Oct 2015
Posts: 35
Location: USA

PostPosted: Sat Mar 18, 2017 5:56 am    Post subject: Need help with below DB2 error
Reply with quote

Hi All

I need help in understanding below DB2 error.

DSNI014I +DB2A DSNIOST2 DATA IN USE DURING ABEND 993
REASON 00C90101
ERQUAL 5005
TYPE 00000302
NAME PAYROLLTS.T001.X'0010471C'
CONNECTION-ID=DB2A
CORRELATION-ID=Winsql.exe
LUW-ID=AC165DF3.A416.D240566B2CB6=77644

Couple of things I researched:

1) looking at error, it seems CHECK DATA needs to be run to correct the error. However tablespace is not in check pending status. Both tablespace and indexes are in RW mode only


2) This error is getting generated when the user is trying to run the query from application front end . However, when I tried to run the same query on mainframes thru SPUFI, it's running fine, though 0 rows returned.
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8117
Location: East Dubuque, Illinois, USA

PostPosted: Sat Mar 18, 2017 6:22 am    Post subject:
Reply with quote

From the DB2 Codes manual:
Quote:
Explanation

The data manager detected an internal error within DB2®. Possible causes for this error include:

Improper migration or fall back procedures.
The DB2 directory and DB2 catalog have been restored to different points in time.
A table space was restored improperly.
An error in internal DB2 control structures or code.
and the recommendations:
Quote:
System programmer response

If you suspect an error in DB2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data and Diagnosing DB2 problems.
User response

Notify the system programmer.
Problem determination

If this abend occurred while processing data in one or more pages, message DSNI014I is issued to identify each page involved. In general, the data in these pages is valid. However, if problems are reported that repeatedly involve the same pages or if the same pages are reported by other abends, analyze the set of pages specified.

Run the CHECK INDEX utility to determine the extent of index inconsistency if:

The page type indicated in message DSNI014I is index.
The page type indicated in message DSNI014I is data.
An index is defined on a table in the indicated page set.

The LOC keyword in the dump title gives the load-module.csect-name:qualifier of the location where the abend occurred. The value of qualifier is a unique, 4-digit hexadecimal number that identifies the place within the source control module (CSECT) where the abend was issued.

SYS1.LOGREC contains information in the variable recording area (VRA) of the system diagnostic work area (SDWA). Significant fields for this abend code are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and VRARRK9. The name of the CSECT involved is given in VRARRK5. The full CSECT name given in the dump title.

The csect-name value in the associated message can indicate possible causes or actions:

DSNGxxxx
If the csect-name value begins with DSNG, regardless of the xxxx portion of the name, make a copy of DSNDB01.DBD01, DSNDB01.SCT02, and DSNDB01.DSNSCT02 on tape with DSN1COPY. This might be a large copy.
DSNIDBMF:5016
An object is already in UTUT status, and a utility is trying to place UTUT status on the same object. The operation is denied with an abend. Two possible causes for this condition are:

SYSUTILX was re-initialized and the pending states were not resolved for each object by running the appropriate utility.
Two utilities ran against the same object with UTUT status.

Collect the following diagnostic items:

Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
Dynamic dump, taken to SYS1.DUMPxx data set, by DB2 (04E and 04F abends).
Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
Detailed description of events immediately prior to and during the abend.
SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
DB2 log output, including any DB2 recovery log archive tapes.
DB2 REPAIR dump of the pages identified in DSNI014I messages.
CHECK utility output.
So you may have to report the problem to IBM for further analysis -- once you've run the CHECK INDEX of course. This is one of those cases where you absolutely HAVE to get your site support group involved in the issue.
Back to top
View user's profile Send private message
ashek15

New User


Joined: 20 Oct 2015
Posts: 35
Location: USA

PostPosted: Sat Mar 18, 2017 7:06 am    Post subject: Reply to: Need help with below DB2 error
Reply with quote

Thanks for reply. However, as I mentioned earlier both table and indexes are in RW mode and not in check pending status. So how will check utility help here?..not sure if the error explanation is masking some other issue beneath because same query is running fine in spufi..Pls suggest
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8117
Location: East Dubuque, Illinois, USA

PostPosted: Sat Mar 18, 2017 8:52 am    Post subject:
Reply with quote

Contact your site support group and have them open an issue with IBM.

It doesn't really matter if the same query is running fine in SPUFI -- unless you want to always run your query in SPUFI and stop trying to run your query through the application front end. There could be a problem with the BIND (which, by the way, may not have produced any errors) due to the internal pointers DB2 maintains being out of whack (and hence the SPUFI could run fine while the application front end query is FUBAR). The TYPE 00000302 in the error message indicates table space page according to what I found.

Contact your site support group and have them open an issue with IBM.
Contact your site support group and have them open an issue with IBM.
Contact your site support group and have them open an issue with IBM.

Hopefully, with enough repetitions you'll understand what you need to do.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts DB2 Program abending without giving a... rahulgarg14 DB2 7 Mon May 29, 2017 8:10 pm
No new posts Getting error while opening a variabl... apandey1 COBOL Programming 5 Fri May 05, 2017 12:22 pm
No new posts IDC2902I Error tzeche ABENDS & Debugging 2 Tue Mar 28, 2017 11:39 am
No new posts FINDREP Syntax Error seahawk789 DFSORT/ICETOOL 4 Thu Mar 09, 2017 10:11 pm
No new posts INVOKE WEBSERVICE error danik56 CICS 11 Thu Mar 09, 2017 11:52 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us