DB2v10.1 for zOS. Strange behaviour tablespace with params "MEMBER CLUSTER"

Colin Clayton

DB2v10.1 for zOS. Strange behaviour tablespace with params "MEMBER CLUSTER"
A few issues with this.

An AREO status should not prevent access, it is an ADVISORY status suggesting you should reorg soon. Was it AREO or AREO* ?

Secondly, the REASON 00E30100 message tells you that “A parallel task running on a DB2 terminates abnormally.”, and TYPE OF RESOURCE 00000906 is DB2 so unlikely to be caused by your ALTER…ADD COLUMN.

Finally, I don’t believe you ran a RECOVER TABLESPACE, when the messages belong to DFSMShsm.

You should be able to resolve the AREO with a reorg, but I can’t say what damage the restore might have done.



From: Oleg Dayneko [mailto:[login to unmask email]
Sent: 10 May 2018 15:05
To: [login to unmask email]
Subject: [DB2-L] - DB2v10.1 for zOS. Strange behavior tablespace with params "MEMBER CLUSTER"


Hi!

Today the programmer send me sql-scripts, that add 1 columns.

ALTER TABLE XXXX.MYTABLE1 ADD COLUMN mycolumn1 INTEGER;

I apply this script.

After this table space shows as RW,AREO.

DDL tablespace:

CREATE TABLESPACE "TSXXX"
IN DBXXX
USING STOGROUP SGIS23DW
PRIQTY 500000 SECQTY 50000 ERASE NO
FREEPAGE 0
PCTFREE 5
GBPCACHE CHANGED
TRACKMOD YES
COMPRESS NO
DEFINE YES
LOGGED
MEMBER CLUSTER
BUFFERPOOL BP22
CCSID ASCII
CLOSE NO
LOCKMAX SYSTEM
LOCKSIZE ANY
MAXROWS 255;



All SQL query that worked with this table get error:

DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN
UNAVAILABLE RESOURCE. REASON 00E30100, TYPE OF RESOURCE 00000906, AND
RESOURCE NAME

I try to restore this table space usage DB2 utility: RECOVER TABLESPACE. The tablespace resored. JCL ended with rc=0. But tablespace remain unavailable for all SQL-s.

I recreate TS exclude param(DB2 work not in cluster environment): MEMBER CLUSTER

and load date from other db2 subsystem. I don't understand: Why TS is crashed after add 1 column and why RECOVER TABLESPACE really don't restored tablespace?

SYSPRINT for restore tablespace:

ARC1801I FAST REPLICATION DATA SET RECOVERY IS 309
ARC1801I (CONT.) STARTING FOR DATA SET
ARC1801I (CONT.) IBDP.DSNDBC.IS23DW.DWM#DOC.I0001.A001, AT 14:22:30 ON
ARC1801I (CONT.) 2018/05/10
ARC1861I THE FOLLOWING 0001 DATA SET(S) WERE 313
ARC1861I (CONT.) SUCCESSFULLY PROCESSED DURING FAST REPLICATION DATA
ARC1861I (CONT.) SET RECOVERY:
ARC1861I (CONT.) IBDP.DSNDBC.IS23DW.DWM#DOC.I0001.A001, COPYPOOL=DSN$IBD
P$DB, DEVTYPE=DASD
ARC1802I FAST REPLICATION DATA SET RECOVERY HAS 315
ARC1802I (CONT.) COMPLETED FOR DATA SET
ARC1802I (CONT.) IBDP.DSNDBC.IS23DW.DWM#DOC.I0001.A001, AT 14:23:02 ON
ARC1802I (CONT.) 2018/05/10, FUNCTION RC=0000, MAXIMUM DATA SET RC=0000
ARC1801I FAST REPLICATION DATA SET RECOVERY IS 316
ARC1801I (CONT.) STARTING FOR DATA SET
ARC1801I (CONT.) IBDP.DSNDBC.IS23DW.DWM#DOC.I0001.A002, AT 14:23:02 ON
ARC1801I (CONT.) 2018/05/10
ARC1860I THE FOLLOWING 0001 DATA SET(S) FAILED DURING 317
ARC1860I (CONT.) FAST REPLICATION DATA SET RECOVERY:
ARC1860I (CONT.) IBDP.DSNDBC.IS23DW.DWM#DOC.I0001.A002, COPYPOOL=DSN$IBDP$DB, DEVTYPE=DASD, VOLUME=******, ARC1866, RC=06
ARC1802I FAST REPLICATION DATA SET RECOVERY HAS 319
ARC1802I (CONT.) COMPLETED FOR DATA SET
ARC1802I (CONT.) IBDP.DSNDBC.IS23DW.DWM#DOC.I0001.A002, AT 14:23:02 ON
ARC1802I (CONT.) 2018/05/10, FUNCTION RC=0008, MAXIMUM DATA SET RC=0066

...

-----End Original Message-----