DB2 - Problembeschreibung
Problem IC91676 | Status: Geschlossen |
SET WRITE SUSPEND FAILS WITH SQL1550N RC 5 DUE TO TABLE SPACE IN BACKUP PENDING OR OFFLINE STATE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
If the SET WRITE SUSPEND command is issued on a database that has at least one table space in the Backup Pending or Offline state, the SET WRITE SUSPEND command will fail with SQL1550N reason code 5 indicating that the current state of one or more table spaces does not permit the suspension of write operations. However, if a table space is in the Backup Pending or Offline state it cannot be written to in the first place, hence it is not necessary to suspend write operations for such a table space. The Backup Pending and Offline states should be considered safe for the purpose of SET WRITE SUSPEND, and table spaces in these states should be skipped. The purpose of this APAR is to lift the current restriction and allow write operations on databases with table spaces in the Backup Pending or Offline state to be suspended. Sample diagnostic data: $ db2 set write suspend for db SQL1550N The SET WRITE SUSPEND command failed because of the condition that is indicated by the reason code. Reason code = "5". The DB2 diagnostic log will contain messages similar to: 2013-04-11-12.29.29.640157 Instance:db2inst1 Node:000 PID:24903714(db2agent (SAMPLE) 0) TID:80639 Appid:*N0.db2inst1.130411172640 base sys utilities sqleDoMemberSuspendProcessing Probe:4215 Database:SAMPLE ADM6014E Write operations could not be suspended or resumed on this DB2 member because one or more table spaces are not in NORMAL state. 2013-04-11-12.29.29.653484 Instance:db2inst1 Node:000 PID:24903714(db2agent (SAMPLE) 0) TID:80639 Appid:*N0.db2inst1.130411172640 base sys utilities sqleSetWriteSuspend Probe:5006 Database:SAMPLE ADM6004N The SET WRITE SUSPEND command failed for the database. Database name: "SAMPLE ". | |
Problem-Zusammenfassung: | |
See Problem Description | |
Local-Fix: | |
Bring the table space out of the Backup Pending or Offline state. As for Backup Pending, take for example a table space level backup. As for Offline, determine the reasons why the table space has been switched into this state (DB2 diagnostic log should help). | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in IBM DB2 10.1 for Linux, UNIX, and Windows Fix Pack 3 | |
Workaround | |
See Problem Description | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95287 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 19.04.2013 21.10.2013 21.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |