Reorganization Troubleshooting with SAPDBA (SAP Library - SAP Database Guide: Informix (BC-DB-INF-DBA))

Reorganization Troubleshooting with SAPDBA

Purpose

If reorganization of a group of tables or a dbspace with SAPDBA for Informix runs into problems, this process helps you to find a solution. SAPDBA normally issues a message to tell you what has happened.

Prerequisites

You have problems with any of the following table or dbspace reorganizations:

Reorganizing a Single Table with SAPDBA using method Reorganize Table by 'insert into select from …' or Reorganize Table by 'Export/Import'. See SAPDBA menu Reorganize Single Table.

Reorganizing a Group of Tables with SAPDBA. See SAPDBA menu Reorganize Group of Tables.

Reorganizing a Dbspace and Its Tables with SAPDBA. See Reorganize Dbspace.

Process Flow

You write down any message that SAPDBA issues.

You look at the reorganization log, which is essential in the diagnosis of problems, especially when contacting the Informix hotline. Refer to Reorganization Log with SAPDBA.

If the problem is not easy to solve – for example, you have had a database crash during the reorganization – you refer to Fixing Difficult Reorganization Problems with SAPDBA. Be sure to call the Informix hotline if you are not sure how to proceed.

Having resolved the problem which prevented successful completion, you can do either of the following:

Restart the processing. Refer to Restarting Uncompleted Reorganization Requests with SAPDBA.

Delete the uncompleted requests to remove them from the SAPDBA control table. Do not perform this action if you have an outstanding problem that you have not yet solved. Refer to Deleting Uncompleted Reorganization Requests with SAPDBA.

Note

The only reason why a restart of an uncompleted request is not possible for a particular table is when data has been lost (that is, either entire tables, or rows from a table, or views or indexes). In any case, you should be able to restart the uncompleted requests for the other tables from the same request.