db2checkCOL - Check database for table accessibility in a prior fix pack command

Authorization

Required connection

This command establishes a database connection.

Command syntax

>>-db2checkCOL--database_alias-- -checkFP----------------------->

>--+------------------+----------------------------------------><
   '-userid--password-'   

Command parameters

database_alias

Specifies the alias of the database to scan. The specified database must be a local database.

-checkFP

Returns a list of all tables that cannot be accessed in a fix pack before DB2 Cancun Release 10.5.0.4. If an attempt is made to access such tables in a fix pack before DB2 Cancun Release 10.5.0.4, SQL0901N ("Table dictionary version mismatch") is returned.

userid

Specifies the user ID to use to connect to the database.

password

Specifies the password for the user ID.

Example

db2checkCOL testdb -checkFP

Starting Phase 1 of 3: Query Catalog Tables
Starting Phase 2 of 3: Loading Table Descriptors
Starting Phase 3 of 3: Analyzing Table Descriptors
ERROR: Table "MYSCM7 "."MYTB7" is affected.
ERROR: Table "NEWTON "."MYTB8" is affected.
DBT7112E The database has been completely tested, and one or more tables
  were found that require additional action.
Exiting with return code "-800".

Usage notes

• Before you run this command, set the appropriate environment variable for your operating system:
  • On the Linux operating system, set the LD_LIBRARY_PATH environment variable to ~/sqllib/lib64. On the AIX® operating system, set the LIBPATH environment variable to ~/sqllib/lib64.
• The db2checkCOL command is an online tool, but it is recommended that you run it during nonpeak periods. Run time can range from seconds to approximately an hour, depending on the number of tables and the amount of concurrent activity.
• On average, 500 KB of disk space per column-organized table might be required for temporary files.
• The command returns one of the following values:

  Table 1. Codes returned by the db2checkCOL command

  Return code	Description
  0	You can access all tables in a fix pack before DB2 Cancun Release 10.5.0.4.
  -100	The command encounters an internal error while testing the database. If this return code is being returned consistently, the assistance of IBM software support is needed to diagnose the problem.
  -300	It is not possible to scan or process all the column-organized tables in the database (for example, because a table space is offline or there is insufficient disk storage for temporary files). When the issue is resolved, rerun the command.
  -400	The command encounters an internal error while testing the database. If this return code is being returned consistently, the assistance of IBM software support is needed to diagnose the problem.
  -500	The authorization ID of the command does not hold the required authorization. Rerun the command with an authorization ID that holds the required authorization.
  -600	A syntax error is encountered. Correct the syntax and rerun the command.
  -700	The command encounters an internal error while testing the database. If this return code is being returned consistently, the assistance of IBM software support is needed to diagnose the problem.
  -800	One or more tables cannot be accessed in a fix pack before DB2 Cancun Release 10.5.0.4.

• If the db2checkCOL command identifies a table that cannot be accessed in a fix pack before Fix Pack 4, take the following steps:
  1. Export the table data in Fix Pack 4 by using the EXPORT command.
  2. Revert to the prior fix pack.
  3. Rebuild the table-level compression dictionary at a version that is appropriate for the fix pack by using the LOAD REPLACE command to load the exported data.