IBM HPSS manual Hpss Installation Guide July Release 6.2 Revision 230

Resolution: Either the wrong filename or the wrong subsystem Id for that filename was entered. Rerun the conversion program with the correct subsystem Id and filename.

SQL0968C The file system is full. SQLSTATE=57011 => This error message usually follows 10 or so other SQL messages, and means that the load operation for the long running conversion program failed because, most likely, the system temporary tablespace (which defaults to TEMPSPACE1) has run out of room. Or it could mean that the tablespace that was being written to is full (an SMS or system managed tablespace).

Resolution: Either add a container to TEMPSPACE1, or define a new tablespace of type system temporary with a new container (new device) to expand the available system temporary space for the database. Recycle the database to enable use of the newly defined system temporary tablespace and rerun the conversion program. Or add a container to the tablespace where data was being written and rerun the conversion program following restart procedures in Section 6.3.13.5: Restarting the Long Running Utilities on page 207.

SQL0289N Unable to allocate new pages in table space "BITFILESMALLSPACE". SQLSTATE=57011 => The tablespace "BITFILESMALLSPACE" is full. It is slightly different than the error above because BITFILESMALLSPACE is a DMS (database managed) container or raw device.

Resolution: Add a container to the tablespace or extend the size of the existing container and rerun

the conversion program using restart procedures in Section 6.3.13.5: Restarting the Long Running Utilities on page 207.

Error: mm_InsertRecord failed, mm_status = -2001, for entry -5590 => This error translates to an mmlib HPSS_E_MM_DB_ERROR, which could mean several things. Most likely the program was trying to insert data into a table that does not exist. But the table could also exist in a locked tablespace (i.e., in a load pending state).

Resolution: Ensure the table exists for the running conversion program. Also check the tablespaces to ensure the state is Normal, and not Quiesced, or Load Pending. If the tablespace is not in a Normal state, then ensure that no other conversion programs are running. If the tablespace should not be in a Load Pending or Quiesced state, then recycle the database. Finally, run the conversion program again.

Error: mm_InsertRecord failed, mm_status = -2014, for entry 0 => This error translates to an mmlib HPSS_E_MM_DUPLICATE error which means that the table, where the data insert was attempted, already has data. If this error appears while running db_config_convert or db_subsys_convert, it is likely that the db_config_convert_empty or db_subsys_convert_empty script failed (the tables are emptied before running the db_config_convert and db_subsys_convert programs).

Resolution: Use the db2 CLI (type 'db2') and connect to the database where the records are to be inserted, then do a 'select * from ????' where ???? is the table where the records are to be inserted. If records exist, then it's likely that the transaction log is full (i.e., an attempt was made to delete lots of records but the transaction log isn't big enough). If the transaction log is full, then increase the size of LOGFILSIZ (database configuration parameter). If this is already set at the maximum value, then try increasing the number of primary log files (database configuration parameter). Ensure sufficient log file or disk space (that these database configuration parameters are not over allocated when there isn't enough space). Recycle the database after adjusting the database configuration parameters mentioned above and rerun the conversion program.

HPSS Installation Guide	July 2008
Release 6.2 (Revision 2.0)	230