How To Fix DB6569 - Status des Tabellenbereichs

SAP Error Message - Details

• Message type: E = Error

• Message class: DB6 - DB6: Alert Monitoring and Alert Configuration

• Message number: 569

• Message text: Status des Tabellenbereichs

Was verursacht dieses Problem?

From the point of view of the database, a tablespace can be in different
states, as far as availability and processing are concerned. The
appropriate current state is displayed here.

Systemantwort

The consequences depend on the state. There is a list below of the
possible states (For the sake of completeness, all states familiar to
DB2 are listed here, although of course a number cannot occur in a
running system ):
<ZH>Normal </> ,,Restore pending ,,Storage may be defined
Quiesced: SHARE ,,Recovery pending (not used) ,,StorDef is in 'final'
state
Quiesced: UPDATE ,,Disable pending ,,StorDef was changed prior to
rollforward
Quiesced: EXCLUSIVE ,,Reorg in progress ,,<ZH>DMS rebalancer is active
</>
Load pending ,,<ZH>Backup in progress ,,TBS deletion in progress</>
Delete pending ,,Storage must be defined ,,TBS creation in progress
Backup pending ,,Restore in progress ,,For service use only
Roll forward in progress ,,Offline and not accessible
Roll forward pending ,,Drop pending
(The states that are possible for a running SAP System appear in bold)
If there is no tablespace available, the SAP system cannot be started
If a tablespace is in another state (for example, during rebalancing
after an extension), this can have massive effects on the system
performance.
For more information, see the DB2 documentation.

Wie behebe ich diesen Fehler?

If a tablespace is not available, you must analyze the cause of the
error with DB2 resources (DB2 DIAG log) and eliminate it (for example,
by roll forward recovery or by importing a backup copy).

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE