Messages Reference

SQL8100 - SQL8199

Cause: When creating a database the following parameters may be specified:

• maximum number of pages per segment per file

• number of segments

Each table part may now have multiple files within the database segments. The file can grow until it reaches its maximum size in a segment (maximum number of pages per segment) and then it moves to the next segment to add more data. This occurs until it has used the maximum number of pages per segment in all configured segments, and the table becomes full.

Therefore, the total amount of space per database part is the product of the maximum number of pages and the number of segments. The table will be full if any of the table parts use all of their configured space.

DataJoiner users: this situation can be detected by DataJoiner or by the data source.

Action:

• Delete rows from the table

• Reorganize the table to make more space

• Create a new database with larger values for maximum pages per segment and number of segments, back up the original database and restore to the new database.

DataJoiner users: isolate the problem to the data source failing the request (refer to the Problem Determination Guide to determine which data source is failing to process the SQL statement) and:

• Take the necessary steps to increase the space in the table at the data source.
• If the table is on DataJoiner, create a new database with larger values for maximum pages per segment and number of segments. Back up the original database and restore to the new database.

Cause: This error could occur in two ways:

1. Every database segment has an identifier file. The file may be missing or the contents of the file may be incorrect.

2. One, or more, previously allocated database segments are missing.

Action:

• Check to ensure that the file systems are mounted correctly

• Restore the database from a backup

• Call your IBM service representative

[ DB2 List of Books | Search the DB2 Books ]