|
|
View previous topic :: :: View next topic
|
| Author |
Message |
Jimy Carol
New User
Joined: 31 Aug 2012
Posts: 25
Location: Australia
|
|
|
|
Hello ,
I am getting "EXECUTION ABENDED, REASON=X'00E40347'
.CAUSE=X'00C9021C' " on RUNSTATS . I have copied the TABLEPSPACE vsam data sets from one SSID to other SSID and have created the same objects on target as of source . The data in source tablespace is compressed.
Howver when I do REORG of source table space the problem doesnt happen ,
I dont understand why this is happening .
Kindly help me
Regards ,
Carol |
|
| Back to top |
|
 |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1771
Location: Bloomington, IL
|
|
|
|
| Jimy Carol wrote: |
I am getting "EXECUTION ABENDED, REASON=X'00E40347'
.CAUSE=X'00C9021C' " on RUNSTATS . I have copied the TABLEPSPACE vsam data sets from one SSID to other SSID and have created the same objects on target as of source . The data in source tablespace is compressed. |
And amazingly, the explanation for reason code X'00C9021C' given in the manual is;
| Quote: |
While running a utility, the data manager detected an inconsistent data condition. A row was encountered that is not represented by a record OBD in the database descriptor (DBD). This abend may indicate an internal DB2® error, but most likely occurs due to a user error. Possible user errors may include:
Data from a DB2 subsystem was copied to another DB2 subsystem incorrectly. This is the most common error. |
Quite a coincidence, don't you think? |
|
| Back to top |
|
|
Jimy Carol
New User
Joined: 31 Aug 2012
Posts: 25
Location: Australia
|
|
|
|
| Akatsukami wrote: |
| Jimy Carol wrote: |
I am getting "EXECUTION ABENDED, REASON=X'00E40347'
.CAUSE=X'00C9021C' " on RUNSTATS . I have copied the TABLEPSPACE vsam data sets from one SSID to other SSID and have created the same objects on target as of source . The data in source tablespace is compressed. |
And amazingly, the explanation for reason code X'00C9021C' given in the manual is;
| Quote: |
While running a utility, the data manager detected an inconsistent data condition. A row was encountered that is not represented by a record OBD in the database descriptor (DBD). This abend may indicate an internal DB2® error, but most likely occurs due to a user error. Possible user errors may include:
Data from a DB2 subsystem was copied to another DB2 subsystem incorrectly. This is the most common error. |
Quite a coincidence, don't you think? |
But if COPY is a problem , then how does a REORG of source table space before copy doesnt cause the problem ? |
|
| Back to top |
|
|
|
|
