DB2 V9 NFM 00C90110 error on load/replace

B.J. Davis

DB2 V9 NFM 00C90110 error on load/replace
We have never seen this error before and would like to know if anyone has seen this before. If you have experienced this error, please reply with your solution to the problem. We were executing a load/replace batch job in a test environment running DB2 V9 NFM when one of the jobs received a SYSTEM ABEND CODE 04E REASON CODE 00C90110. After we received the error, we were not able to drop any objects in the database or drop the database. We had to re-cycle DB2 in this environment before we could continue using this database. We have been running loads with no problems until this morning.

Thanks in advance for any help!

_________________________________________________________________

Register NOW for the IDUG DB2 Tech Conference in Anaheim, May 2-6, 2011!
_________________________________________________________________
International DB2 User Group (IDUG) - Independent, not-for-profit, User Run
Your only source for independent, unbiased, and trusted DB2 information

Lockwood Lyon

Re: DB2 V9 NFM 00C90110 error on load/replace
(in response to B.J. Davis)
Betty,

The message description in the manual is clear:

The data manager detected an inconsistent data condition. This may be
caused by an inconsistency in either the DB2 catalog or the DB2 directory.

It also instructs you:

To prevent further damage and possible loss of data, the inconsistency
must be corrected before any further SQL access is attempted to this
database.

This error generates a message on SYS1.LOGREC and an SVC dump. The error message description in the manual tells you the probable causes, instructs you to gather diagnostic information. It also points you to the Diagnosis Guide (Part 5) for analysis.

- Lock Lyon
Fifth Third Bancorp

-----Original Message-----
From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Betty Davis
Sent: Friday, May 06, 2011 3:53 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 V9 NFM 00C90110 error on load/replace

We have never seen this error before and would like to know if anyone has seen this before. If you have experienced this error, please reply with your solution to the problem. We were executing a load/replace batch job in a test environment running DB2 V9 NFM when one of the jobs received a SYSTEM ABEND CODE 04E REASON CODE 00C90110. After we received the error, we were not able to drop any objects in the database or drop the database. We had to re-cycle DB2 in this environment before we could continue using this database. We have been running loads with no problems until this morning.

Thanks in advance for any help!



This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.


_________________________________________________________________

Register NOW for the IDUG DB2 Tech Conference in Anaheim, May 2-6, 2011!
_________________________________________________________________
International DB2 User Group (IDUG) - Independent, not-for-profit, User Run
Your only source for independent, unbiased, and trusted DB2 information


Chris Hoelscher

Re: DB2 V9 NFM 00C90110 error on load/replace
(in response to Lockwood Lyon)
-----Original Message-----
From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Betty Davis
Sent: Friday, May 06, 2011 3:53 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 V9 NFM 00C90110 error on load/replace

We have never seen this error before and would like to know if anyone has seen this before. If you have experienced this error, please reply with your solution to the problem. We were executing a load/replace batch job in a test environment running DB2 V9 NFM when one of the jobs received a SYSTEM ABEND CODE 04E REASON CODE 00C90110. After we received the error, we were not able to drop any objects in the database or drop the database. We had to re-cycle DB2 in this environment before we could continue using this database. We have been running loads with no problems until this morning.

Thanks in advance for any help!


Betty - in addition to Lock's information - I see the following explanation

The DBD in storage may be inconsistent.
Specifically, the OBDDMAP(OBID) array element should contain an offset
into the DBD where the OBD should be located. However, in this case the
OBD expected was not at the indicated offset.

This could also mean corrupted storage - the fact that you cycled the subsystem and then the data manager no longer found the inconsistency night substantiate this theory - in any event - do not take my word for it - put your software fees to work and open an issue with IBM on this - assuming you have the dump - IBM should be able to detect the defect ...

Chris Hoelscher


The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.


_________________________________________________________________

Register NOW for the IDUG DB2 Tech Conference in Anaheim, May 2-6, 2011!
_________________________________________________________________
International DB2 User Group (IDUG) - Independent, not-for-profit, User Run
Your only source for independent, unbiased, and trusted DB2 information


Avram Friedman

Re: DB2 V9 NFM 00C90110 error on load/replace
(in response to Chris Hoelscher)
00C90110 is the 0C4 of database errors.
It is VERY common and I am surprized that you have never seen one before.

I 100% percent agree with Chris' suggestion that you ask IBM for help ...
usually kills a few days but you will get a good answer.

In more of a hurry? Then we can guess

A common cause of 00C0110 is DSN1COPY use / abuse.
There is an entire appendix in one of the DB2 manuals on the subject.

Doing a lot of loads are you?
Is there something that we really do not need to know like are you cloning a system?
Where did all the load files come from? An unload job perhaps?
Is there something you are not telling us because we don't need to know?


Tell me how did you obtain the DDL for creating the databases, Tablespaces, tables, indexes etc?
Were any of these objects ever altered on the original system (even if the system giving you problems is the original system)
If these objects have been altered have they been reorged since the alter?
Is there something you are not telling us because we don't need to know?

Of course I would personally never ask about things I don't need to know.

Best wishes
Avram Friedman

On Fri, 6 May 2011 19:53:25 +0000, Betty Davis <[login to unmask email]> wrote:

>We have never seen this error before and would like to know if anyone has seen this before. If you have experienced this error, please reply with your solution to the problem. We were executing a load/replace batch job in a test environment running DB2 V9 NFM when one of the jobs received a SYSTEM ABEND CODE 04E REASON CODE 00C90110. After we received the error, we were not able to drop any objects in the database or drop the database. We had to re-cycle DB2 in this environment before we could continue using this database. We have been running loads with no problems until this morning.
>
>Thanks in advance for any help!
>
>_________________________________________________________________
>
>Register NOW for the IDUG DB2 Tech Conference in Anaheim, May 2-6, 2011!
>_________________________________________________________________
> International DB2 User Group (IDUG) - Independent, not-for-profit, User Run
> Your only source for independent, unbiased, and trusted DB2 information

_________________________________________________________________

Register NOW for the IDUG DB2 Tech Conference in Anaheim, May 2-6, 2011!
_________________________________________________________________
International DB2 User Group (IDUG) - Independent, not-for-profit, User Run
Your only source for independent, unbiased, and trusted DB2 information