05 | Dump created |
A brief explanation follows of how the DBH responds to the different error weights when the DBH session is running with transaction management.
Transaction management can be deactivated for a session in which only CALL DML applications are running. Important DBH backup functions are not active in this case and the DBH cannot react appropriately to consistency checks with certain error weights. The user may then have to take more extensive action. This is described separately under the heading “Response”.
The following table contains only consistency checks that require special responses.
Consistency checks that are not listed here are to be handled according to their error weights.
Consistency check | Detecting functional unit | Diagnostic documentation |
SEA....: AD/gg/uu | SESADM | SESADM dump and maybe a |
SED....: XX/gg/uu | DDL functions and | SESAM dump. |
SEDFRVM: XX/gg/uu | Free space administration of | SESAM dump |
SEDTA..: XX/gg/uu | DDL transaction management | SESAM dump |
SEFBM..: XX/gg/uu | Transaction logging | SESAM dump, |
SEL....: XX/80/uu | DDL interpreter | SESAM dump |
SEM....: XM/gg/uu | SESAM monitor | SESAM monitor dump |
SESADXS: XX/05/99 | Administration handler after | SESAM dump |
SESAGPM: AA/gg/uu | Logical data backup | SESAM dump, |
SESCO..:XX/05/uu | Job logging | Correct DMS error in the CO- |
SESLOMA: XX/gg/uu | Recovery | SESAM dump, |
SEU....: XX/80/uu | Utility interpreter | SESAM dump |
SEUTA.. : XX/gg/uu | DDL transaction management | DDLTA file |
Error weight 05 - Dump created
Meaning
An event has occurred during the run, but processing of a request, the transaction and the DBH session can be continued. Later, however, there may be a need for clarification. A dump is generated for this purpose.
Examples of these events are:
The DBH has received a defective message.
In this case the DBH sends a request to the sender task to write a dump.An error has occured when writing to the CO-LOG file.
In this case the DBH turns off the file concerned.
The DBH session continues both during and after this error.
Response
In the case of the CO-LOG file, eliminate the cause of the DMS error. In the case of defective message reception, save the DBH dump and the application program dump and send this with the error message report to customer support. If the errors occurred after the execution of EXPORT or IMPORT statements, you should also save the export file as an additional diagnostic document.
Error weight 10 - Transaction rolled back
Meaning
During processing of a request, an error occurs that does not affect either concurrent requests or the overall system. After rolling back the current transaction, the DBH continues with the session.
Response
Save the dump and send it to customer services along with the error message.
Error weight 11 - Transaction rolled back due to DMS error
Meaning
A DMS error occurred during the processing of a job that does not affect parallel jobs or the overall system. After rolling back the current transaction, the DBH continues with the session.
Response
Recover the DMS error.
Error weight 12 - Transaction rolled back with application program dump
Meaning
An inconsistency between the application program and the DBH has been found that does not affect parallel jobs or the overall system. After rolling back the current transaction, the DBH continues with the session.
Response
Save the DBH dump and the application program dump and send them to customer services along with the error message.
Error weight 30 - Restart due to system inconsistency
Meaning
An inconsistency has occurred in the system which cannot be allocated to any specific job but which can be recovered through a restart. All requester sessions are closed. If transaction management is not active, the session is terminated.
Response
Save the dump and send it to customer services along with the error message.
Error weight 32 - I/O error space
Meaning
After an I/O error in a space the DBH executes an internal restart and rolls back all open transactions so that the space is in a consistent state again. All requester sessions are closed. The DBH session is continued, the space remains in the session. If transaction management is not active in the session, the affected space no longer used.
Response
Recover the hardware problem and inform customer services of the error report. If transaction management was not active in the session, repair the affected space using Media Recovery facilities.
Error weight 33 - Maximum space size reached
Meaning
The maximum possible space size of 64 Gbytes has been reached. The space (created in SESAM/SQL V7.0 or lower) can no longer be expanded. The DBH executes an internal restart and rolls back all the open transactions, which ensures that the space is once more in a consistent state. All requester sessions are closed. The DBH session is continued, the space remains in the session.
Response
Reorganize the space using the utility statement REORG SPACE. Relieve the load on the space by deleting records which are no longer required, by relocating tables and indexes, or by partitioning tables.
Error weight 34 - Secondary index defective
Meaning
The DBH rolls back all open transactions in the course of an internal restart. The index is marked as defective. All requester sessions are closed. The DBH session is continued without the affected index.
Response
Regenerate the defective index using the RECOVER INDEX utility statement and inform customer services of the error message.
Error weight 36 - Table defective
Meaning
A table is inconsistent. Other tables and indexes in the space are generally not involved. The DBH rolls back open transactions by means of an internal restart. The affected table is marked as defective. All requester sessions are closed and the DBH session is continued. The defective table can no longer be accessed.
Response
Report the error message to customer services. If a diagnosis requires information on the space containing the defective table, make a copy of the space. Then use the RECOVER utility statement to repair the space containing the defective table to make the table accessible again.
Error weight 37 - Space defective
Meaning
A space is inconsistent. The DBH rolls back open transactions by means of an internal restart. The defective space is closed and flagged as “defective”. The DBH only opens it again for processing after recovery. All requester sessions are closed. The DBH session continues.
Response
Report the error message to customer services. If a diagnosis requires information on the defective space, make a copy of the space. Then repair the space using the RECOVER utility statement.
Error weight 38 - Database catalog space defective
Meaning
Inconsistency in a catalog space. The DBH rolls back open transactions by means of an internal restart. The database is closed and the catalog space is flagged as “defective”. The DBH only opens the database again for processing after recovery. All requester sessions are closed. The DBH session continues.
Response
Report the error message to customer services. If information on the defective catalog space is required for diagnosis, first make a backup copy of the catalog space, then use the RECOVER CATALOG_SPACE or RECOVER CATALOG ... SCOPE PENDING utility statement to repair it. The advantage of using RECOVER CATALOG ... SCOPE PENDING is that it repairs defective data and index spaces in addition to the catalog space.
Error weight 39 - Database CAT-REC file defective
Meaning
Inconsistency in the CAT-REC file of the affected database. The DBH sets the database to ACCESS=READ, rolls back all open transactions in an internal restart, closes all requester sessions and then continues with the DBH session.
Response
Check whether the CAT-REC file comes from a previous version or whether some other handling error occurred. Make the correct CAT-REC file available, if possible. If the reason for the error was not a handling error, report the error message to customer services. If a diagnosis requires information on the defective CAT-REC file, make a copy of the CAT-REC file and the catalog space. Create a new CAT-REC file with the help of customer services where necessary.
Error weight 40 - Management error
Meaning
Error in transaction management or in error handling. All files opened by the DBH are closed and the DBH is terminated. No internal restart.
Response
If transaction management is active in the session: perform an external restart and report the error message to customer services. In a CALL DML session without transaction management, use the resources of media recovery to repair CALL DML tables being directly updated at the time of termination of the session. Report the error message to customer services.
Error weight 80 - System defective
Meaning
Consistent continuation of the DBH session is not possible due to an error in internal system procedures or in the management tables. The DBH generates a dump and then terminates the session.
Response
Send the dump and the error message to customer services.
Error weight 82 - System defective and system dump
Meaning
As a result of an error in coordination with the operating system, it is not possible for the DBH session to continue in a consistent state. The DBH generates a system dump, if possible, and then terminates the session.
Response
Send the dump and the error message to customer services.
Error weight 83 - System defective and local dump
Meaning
Consistent continuation of the DBH session is not possible due to an error in the internal system procedures which affects the local task data modules. The DBH generates a task dump and terminates the session.
Response
Report the error message to customer services.
Error weight 88 - System and current database defective
Meaning
A catalog space inconsistency indicates that there is a serious error in the administration tables of the DBH. The database is closed and the catalog space is flagged as “defective”. The DBH only opens the database again for processing after recovery. The DBH then proceeds as described for error weight 80 (system defective).
Response
Send the dump and the error message to customer services. If a diagnosis requires information on the defective catalog space, make a copy of the catalog space. Then repair the catalog space using the RECOVER utility statement.