Explanation

The table name must be fully qualified. The format is authid.tablename where authid contains 1 to 128 bytes and tablename contains 1 to 128 bytes in.

The utility stops processing.

Explanation

The table name must be fully qualified and in the format authid.name where authid contains 1 to 128 bytes and name contains 1 to 128 bytes and must be located at a valid application address.

The utility stops processing.

Explanation

The address for the list is not valid, the number of entries in the list is less than the number of indexes specified, or the address for an index in the list is not valid.

The utility stops processing.

Explanation

The utility stops processing.

Explanation

The sharelev parameter in the RUN STATISTICS command must be R for reference or C for change.

The utility stops processing.

Explanation

The tname parameter specified a view or nickname rather than a table.

The utility stops processing.

Explanation

The table or index identified by name does not exist in the database, or the index identified by name is not defined on the specified table. The qualifier for the table or one of the indexes may be incorrect.

The utility stops processing.

Explanation

The Run Statistics utility command may not be run against a system table.

The utility stops processing.

Explanation

The index name must be a fully qualified name. The format is authid.name where authid contains 1 to 128 bytes and name contains 1 to 128 bytes.

The utility stops processing.

Explanation

The index name must be a fully qualified name. The format is authid.name where authid contains 1 to 128 bytes and name contains 1 to 128 bytes.

The utility stops processing.

Explanation

An error occurred while the utility was gathering statistics.

The sqlcode number in the token sqlcode indicates more specifically what the underlying error was.

Explanation

The user attempted to run statistics on the specified table without the appropriate authorization. If the table specified for the RUNSTATS command is the root table of a table hierarchy, the table name returned in the message might be a subtable of the specified root table.

For tables, CONTROL privilege on the table or one of the following authorities is required: SYSADM, SYSCTRL,SYSMAINT,DBADM,SQLADM, or LOAD.

For statistical views, both of the following authorizations are required:

• CONTROL privilege on the table or one of the following authorities: SYSADM, SYSCTRL,SYSMAINT,DBADM,SQLADM
• The appropriate privilege to access rows in the view. This means for each table, statistical view, or nickname referenced in the statistical view, you need one of the following privileges or authorities: SYSADM, DBADM, DATAACCESS, CONTROL or SELECT.

The utility stops processing.

Explanation

The setting of the database configuration parameter stat_heap_sz is not big enough to collect non-uniform distribution statistics on the table.

Explanation

The setting of the database configuration parameter stat_heap_sz is not big enough to collect non-uniform distribution statistics on the table. Only <n1> of <n2> rows could be processed.

Explanation

The query optimizer uses statistics to determine the best access plan for a query. When inconsistent statistics are present, the optimizer performs access plan evaluation with information that is less accurate then if a consistent set of statistics was available. This might result in an access plan that is not optimal.

Possible causes of this warning include the following.

1. Issuing RUNSTATS on the table only may result in a situation where the table level statistics are inconsistent with the already existing index level statistics. Likewise, issuing RUNSTATS for indexes only or during index creation may leave table level statistics in an inconsistent state. For example, if index level statistics are collected on a particular table and later a significant number of rows is deleted from this table, issuing RUNSTATS on the table only may end up with the table cardinality less than FIRSTKEYCARD which is an inconsistent state.
2. If a RUNSTATS is issued with the ALLOW WRITE ACCESS option when many inserts, updates, or deletes are occurring concurrently, then inconsistencies may occur because of table changes between the time that table and index statistics are collected.
3. If a RUNSTATS is issued with the TABLESAMPLE option, then an excessively low sample size may cause statistics to be inaccurately extrapolated, resulting in inconsistencies. The chance of inaccurate extrapolation is higher for SYSTEM sampling than for BERNOULLI sampling.

Explanation

The statistics profile for this table does not exist in the catalog table SYSIBM.SYSTABLES.

The utility stops processing.

Explanation

The maximum size of the STATISTICS_PROFILE column is 32768 bytes. If the size of the statistics profile is greater than this amount, the Runstats command strings is truncated to the maximum size.

The utility continues processing.

Explanation

Page-level sampling, or SYSTEM SAMPLING, could not be performed on the statistical view specified for RUNSTATS. For statistical views, SYSTEM sampling can only be applied to a single base table referenced in the view definition. If the view contains multiple tables, SYSTEM sampling is possible if a single table among all the tables in the statistical view can be identified as being joined with all primary keys or unique index columns of the other tables used in the view.

The referential integrity constraints can be informational. If the view meets the previously described criteria, page-level sampling will be done on the child table.

Because the statistical view specified did not satisfy these conditions, row-level sampling, or BERNOULLI SAMPLING, was done instead.

Explanation

The backup failed because the database is in an inconsistent state.

The utility stops processing.

Explanation

During the utility operation a corrupted database page was encountered. The database is in an unpredictable state and the utility cannot continue.

Explanation

Online backup cannot be performed while the database is not logging for forward recovery as forward recovery will be required at restore time. Forward recovery is placed into effect by setting either the database configuration LOGARCHMETH1 or LOGARCHMETH2 and then performing an offline backup of the database.

Explanation

The tape which the utility is using has become full.

Explanation

The archive log command can only be used on databases that are in recoverable mode. A database is in recoverable mode if LOGARCHMETH1 is set to DISK, TSM, VENDOR, USEREXIT, or LOGRETAIN, or if LOGARCHMETH2 is set to DISK, TSM, or VENDOR.

Explanation

The database specified in the dbase parameter of the Database Backup command could not be found.

Explanation

During the processing of a database utility, the target disk became full. The utility has stopped and the target is deleted.

Explanation

During the Backup operation an initial backup header needs to be created at the start of the backup image. This header must fit on one tape when backing up to tape. There is insufficient space on the tape to contain this header.

Explanation

This message is returned when a table space level backup cannot be performed because the database is not recoverable or a backup pending condition is in effect. This can happen under the following conditions:

• The database is in an offline backup pending condition. This can be caused by a topology change, or when the database has been made recoverable.
• Table space level backup cannot be performed while the database is not logging for forward recovery as forward recovery will be required at restore time.

Explanation

Some of the index files required by the backup are missing. These index files must be recreated prior to backing up the database.

Explanation

The TSM or vendor supplied archive server might not be in operational state.

Explanation

During an online backup, all buffered log records are forced to disk and the last active log file is truncated. During the current backup, truncation of the last active log file has failed. As a result, new log records will continue to be written into the last log file used during the backup.

Explanation

Incremental backups are not enabled for a table space until after modification tracking has been activated for the database and a non-incremental backup has been performed on the table space.

Possible reason codes:

1. The configuration parameter TRACKMOD has not been set for the database.
2. The TRACKMOD configuration parameter has been set but at least one table space has not had a non-incremental backup taken since the TRACKMOD parameter was set.

Explanation

A compressed backup image is being created with the plug-in library being included in the image. However, the library does not contain all the functions needed to decompress the backup image when it is restored.

The utility stops processing.

Explanation

You can include database log files in a backup image by specifying the INCLUDE LOGS parameter with the BACKUP command. When the INCLUDE LOGS parameter is specified with the BACKUP command, if any of the logs required for rollforward recovery cannot be retrieved and copied into the backup image the backup operation fails.

There are multiple reasons why the backup utility might encounter a problem while retrieving and copying the log files into the backup image, including these examples:

• An administrative action, such as unmounting the drive on which the log path resides or changing the permissions on the directory where the log path is located, has occurred which prevents the backup utility from access the log files.
• The contents of the log path have been moved or log files have been deleted.
• The archive log path contains log files from a previous database that has the same name as a current database.

Explanation

The backup of a partitioned database failed on one or more database partitions.

When the database server backs up a partitioned database, a failure on any one of the partitions causes the whole backup to fail.

The backup operation terminated. No backup image was generated.

Explanation

The database server successfully backed up the partitioned database containing this partition.

However, some of the table spaces that were specified in the BACKUP command do not exist on this partition. This might be because the table spaces specified are located on other partitions of this database; or because the list of table spaces specified contains an error.

The backup completed successfully.

Explanation

The database server successfully backed up a partitioned database.

The backup image of each database partition contains only the log files that was were active at the time of the backup. It is not possible to rollforward the whole partitioned database using only the log files included in the backup images, if any of those log files does not span a period of time including the database minimum recovery time.

The minimum recovery time (MRT) for a database object is the earliest point in time to which it can be rolled forward.

In a partitioned database, the database MRT is the latest MRT of any one of its database partitions.

You can only roll forward a partitioned database if you have a set of log files on all database partitions that span a period of time that includes the database MRT.

The log files included with the backup image might not satisfy this requirement.

The backup completed successfully.

Explanation

A snapshot backup enables you to use fast copying technologies for the data copying and movement parts of DB2 database backup and restore operations.

The EXCLUDE LOGS parameter was specified for a snapshot backup, but the path for the given log directory or directories shares a path or storage device with other paths or storage devices used by the database being backed up.

When the log directory shares a path or storage device with other paths or storage devices used by the database being backed up, it is not possible for the snapshot backup to include the shared path or storage device without including the log directory.

For example: when you create a database, the log directory is created under the main database directory by default. Because a snapshot backup will include everything under the main database directory, the log directory will be included in the resulting backup image too. If you use the default log path when you create a database, you will not be able to exclude the logs from the backup image when you perform a snapshot backup on that database.

The mechanism for grouping database directories varies among the snapshot backup support provided by different storage management software.

Explanation

A redirected restore is a restore in which the set of table space containers for the restored database is different from the set of containers for the original database at the time the backup was done.

When you define new table space containers that are to be used by the restored database, you can define an architecture for the new table space containers that is not the same as the architecture of the original table space containers. For example, you can use a redirected restore operation to change a database that currently uses two table space containers to use a single table space container.

If the architecture of the table spaces to be used by the restored database is different from the architecture of the original database, it is possible that there are table space altering operations in the database log files that will have to be replayed during rollforward that are not valid in the new table space architecture.

This message is returned during a redirected restore operation when the rollforward utility attempts to replay a table space operation that is invalid for the target table space container architecture. Specifically, this message is returned when the rollforward utility attempts to perform a table space operation on a REGULAR or USER TEMPORARY DMS table space that causes the size of the table space to increase beyond the defined maximum allowed size, as determined by the PAGESIZE database configuration parameter.

Explanation

This message is returned when an attempt is made to have multiple active databases in a DB2 pureScale environment, but the activation of one database fails because there is not enough memory in the cluster caching facility, also known as CF, for that database.

You can configure the total amount of memory that is available for the CF using the cf_mem_sz database manager configuration parameter. You can configure the percentage of the total CF memory that is assigned to each database that has the cf_db_mem_sz database configuration parameter set to AUTOMATIC using the DB2_DATABASE_CF_MEMORY registry variable. (Any database that has cf_db_mem_sz set to a specific value will ignore the DB2_DATABASE_CF_MEMORY registry variable.)

Use of the DB2_DATABASE_CF_MEMORY registry variable must be coordinated with the cf_db_mem_sz database configuration paremter and the numdb database manager configuration parameter.

Example

If there are four databases to be active at once, then the configuration parameters should be coordinated like this:

• The database manager configuration parameter numdb should be set to 4
• If the database configuration parameter cf_dm_mem_sz is set to AUTOMATIC for each of the four database, then the registry variable DB2_DATABASE_CF_MEMORY should be set to 25

One reason this error can occur is because the DB2_DATABASE_CF_MEMORY registry variable is set to 100 when numdb is greater than 1.

Explanation

You can use the redistribute utility to rebalance the distribution of data across database partitions after adding or removing database partitions, or to achieve a desired data distribution across partitions. This message is returned when an attempt is made to redistribute data in a database, using the REDISTRIBUTE DATABASE PARTITION GROUP command for example, but the redistribute utility determines that there are one or more tables that are not in an appropriate state to be redistributed.

If the PRECHECK YES OR PRECHECK ONLY command parameter was specified in the REDISTRIBUTE DATABASE PARTITION GROUP command, this error message describes the first check that failed; data redistribution does not commence. In all other cases, the data redistribution was attempted and failed; tables that were partially processed are put in "redistribute pending" state.

The reason that the table failed to meet data redistribution prerequisites is indicated by the reason code:

1

The table is in "set integrity pending" state.

2

The table is in "load in progress" state. The LOAD utility is currently operating on this table, no access is allowed until the LOAD is finished.

3

The table is in "load pending" state. A previous LOAD attempt on this table resulted in failure. No access to the table is allowed until the LOAD operation is restarted or terminated.

4

The table is in "read access only" state. This state can occur during on-line LOAD processing (LOAD INSERT with the READ ACCESS option), or after an on-line LOAD operation, but before all constraints have been validated in the newly appended portion of the table using the SET INTEGRITY statement. No update activity is allowed on this table.

5

The table is in "reorg pending" state. This can occur after an ALTER TABLE statement containing a REORG-recommended operation.

6

The table is unavailable.

7

The table is an MDC table with a deferred index cleanup rollout operation in progress.

8

The table is a target table for an active event monitor of type "WRITE TO TABLE".

9

The table is in "not load restartable" state, which is a partially loaded state that will not allow a load restart operation.

10

The table is not in FULL access mode (ACCESS_MODE='F' in SYSCAT.TABLES).

11

The table has data partitions that are currently being attached (SYSCAT.DATAPARTITIONS.STATUS = 'A').

12

The table has detached data partitions and there are dependent tables that need to be incrementally maintained with respect to these detached data partitions (SYSCAT.DATAPARTITIONS.STATUS = 'D').

13

The table has detached data partitions that are involved with an index cleanup operation that is currently running (SYSCAT.DATAPARTITIONS.STATUS = 'I').

Explanation

You can move data into and out of databases, using utilities such as LOAD, IMPORT, INGEST, and EXPORT.

There are several ways to specify how data movement utilities should handle implicitly hidden columns:

• Explicitly specify the list of columns to include in the data movement operation.
• Specify the hidden column-related parameter in the data movement command.
• Set the hidden column-related registry variable to indicate how all data movement utilities should handle hidden columns.

This message is returned when an attempt is made to move data into or out of one or more tables that contain implicitly hidden columns, and the data movement utility cannot determine whether the implicitly hidden columns should be included in the data movement operation because none of the methods described have been used to specify how hidden columns should be handled.

Explanation

You can move data into and out of databases, using utilities such as LOAD, IMPORT, INGEST, and EXPORT.

There are several ways to specify how data movement utilities should handle implicitly hidden columns:

• Explicitly specify the list of columns to include in the data movement operation.
• Specify the hidden column-related parameter in the data movement command.
• Set the hidden column-related registry variable to indicate how all data-movement utilities should handle hidden columns.

This message is returned when data is being moved into or out of one or more tables that contain implicitly hidden columns, and the data movement utility cannot determine whether the implicitly hidden columns should be included in the data movement operation because none of the methods described have been used to specify how hidden columns should be handled.

Data has been moved, but data in any implicitly hidden columns was not moved.

Explanation

When the DB2_BCKP_INCLUDE_LOGS_WARNING registry variable is set to ON, online backups that include logs can succeed even if some of the logs required for the successful rollforward recovery of the image cannot be retrieved and copied into the backup image.

If this backup image is restored, it will not be able to complete rollforward recovery unless all of the required logs are made available.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert utility.

This message is returned when the db2convert command is called and one or more tables to be converted are either already in the process of being converted or are involved in a table move operation.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert utility.

This message is returned when either an invalid parameter is specified with the db2convert command, or when an invalid combination of parameters is specified.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert utility.

When you run the db2convert command, you must use the -d parameter to specify the name of the database in which the tables to convert are located.

This message is returned when the db2convert command is called but no database is specified with the -d parameter.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can perform the conversion operation all in one step. However, you can also choose to perform the conversion operation in two steps:

1. Perform only the INIT, COPY, and REPLAY phases of the conversion by calling the db2convert command specifying the -stopBeforeSwap parameter.
2. Complete the conversion operation by calling the db2convert command specifying the -continue parameter.

If you choose to perform the conversion in two steps, the table specification in the first db2convert call and in the second db2convert call must match, and the first step must be completed before you can perform the second step.

This message is returned when the db2convert command is run with the -continue parameter, but no matching call to the db2convert command with the -stopBeforeSwap parameter has completed.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

For example, the following command converts all row-organized tables in database db1 that satisfy the matching criteria "owned by user1 and in schemaA":

db2convert -d db1 -u user1 -z schemaA

This message is returned when no tables satisfy the matching criteria that were specified with the db2convert command.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

This message is returned when the db2convert utility has completed the conversion process successfully for all tables that match the specified criteria.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when the db2convert fails to convert one or more tables.

There are multiple reasons that a table might have failed to be converted, including the following examples:

• The table includes functionality that is not supported with column-organized tables.
• The table includes functionality that cannot be converted by the db2convert utility due to a restriction.
• An error occurred while the table was being converted.

The db2convert utility prints summary information to stdout upon completion. That summary information includes a list of tables that were converted and tables that were not converted, including details about what errors occurred.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when the db2convert fails to convert any tables.

There are multiple reasons that a table might have failed to be converted, including the following examples:

• The table includes functionality that is not supported with column-organized tables.
• The table includes functionality that cannot be converted by the db2convert utility due to a restriction.
• An error occurred while the table was being converted.

The db2convert utility prints summary information to stdout upon completion. That summary information includes a list of tables that were converted and tables that were not converted, including details about what errors occurred.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when none of the tables that match the specified criteria are row-organized tables.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

You can perform the conversion operation in one step. However, you can also choose to perform the conversion operation in two steps:

1. Perform only the INIT, COPY, and REPLAY phases of the conversion by calling the db2convert command specifying the -stopBeforeSwap parameter.
2. Complete the conversion operation by calling the db2convert command specifying the -continue parameter.

Performing the operation in two steps allows you to back up the database before completing the conversion.

This message is returned when the db2convert utility has successfully completed the first step of the two-step conversion process for all tables that match the specified criteria.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

You can perform the conversion operation in one step. However, you can also choose to perform the conversion operation in two steps:

1. Perform only the INIT, COPY, and REPLAY phases of the conversion by calling the db2convert command specifying the -stopBeforeSwap parameter.
2. Complete the conversion operation by calling the db2convert command specifying the -continue parameter.

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when the db2convert fails to convert one or more tables.

There are multiple reasons that a table might have failed to be converted, including the following examples:

• The table includes functionality that is not supported with column-organized tables.
• The table includes functionality that cannot be converted by the db2convert utility due to a restriction.
• An error occurred while the table was being converted.

The db2convert utility prints summary information to stdout upon completion. That summary information includes a list of tables that were converted and tables that were not converted, including details about what errors occurred.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

You can perform the conversion operation in one step. However, you can also choose to perform the conversion operation in two steps:

1. Perform only the INIT, COPY, and REPLAY phases of the conversion by calling the db2convert command specifying the -stopBeforeSwap parameter.
2. Complete the conversion operation by calling the db2convert command specifying the -continue parameter.

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when the db2convert is unable to convert any tables.

There are multiple reasons that a table might have failed to be converted, including the following examples:

• The table includes functionality that is not supported with column-organized tables.
• The table includes functionality that cannot be converted by the db2convert utility due to a restriction.
• An error occurred while the table was being converted.

The db2convert utility prints summary information to stdout upon completion. That summary information includes a list of tables that were converted and tables that were not converted, including details about what errors occurred.

Explanation

Rebinding is the process of recreating a package for an application program that was previously bound. You can rebind a package by using the REBIND command.

This message is returned when an attempt is made to rebind a package that is generated for an SQL object (such as an SQL procedure or a compiled function, among others) that is invalid. The SQL object might have become invalid for one of multiple reasons, such as because something in the body of the SQL object has changed since the SQL object and the associated package was created.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert utility. You can cause all message text output from the db2convert utility to be printed to a file by specifying an output file name with the -o option. If the specified file does not exist, the db2convert utility will create the file. If the specified file exists, the db2convert utility will overwrite the existing file.

This message is returned when a file name is specified with the -o option, but the db2convert utility cannot write output to the specified file. There are different reasons why the db2convert utility might be unable to print to the specified output file, including the following examples:

• The user who called the db2convert command does not have write permission for the specified file or the directory in which the file is located.
• A full path was specified with the file name, and the specified path does not exist.

Explanation

You can enable self-tuning for sort memory by setting the database configuration parameters SORTHEAP and SHEAPTHRES_SHR to "AUTOMATIC".

Self-tuning for sort memory is not supported with column-organized tables.

This message is returned when either the configuration parameter SORTHEAP or the configuration parameter SHEAPTHRES_SHR is updated to "AUTOMATIC" while there is a column-organized table in the database.

Explanation

If database configuration parameter CF_DB_MEM_SZ is set to AUTOMATIC, these memory consumer parameters are also automatically set to AUTOMATIC: CF_GBP_SZ, CF_LOCK_SZ and CF_SCA_SZ.

If any of the memory consumer parameters is set to a fixed value, the other two memory consumer parameters and database configuration parameter CF_DB_MEM_SZ are also automatically set to a fixed value. If CF self-tuning memory was set on, CF self-tuning memory is turned off for this database.

If any of the memory consumer parameters is set to AUTOMATIC, the other two memory consumer parameters are also set to AUTOMATIC. The value of database configuration parameter CF_DB_MEM_SZ remains unchanged.

Explanation

For CF self-tuning memory to be enabled, when registry variable DB2_DATABASE_CF_MEMORY is set to AUTO, these database configuration parameters must be set to AUTOMATIC: CF_GBP_SZ, and CF_LOCK_SZ, CF_SCA_SZ.

One of the database configuration parameters is not set to AUTOMATIC.

Explanation

Changing the setting of registry variable DB2_DATABASE_CF_MEMORY requires a database manager restart for the new value to take effect. Until the database manager is restarted, the databases are not aware of the new value and will not have their CF memory configurations adjusted according to the new value.

Explanation

Encryption-related or compressions-related configuration settings can be specified for backup operations in two ways:

• In BACKUP DATABASE command parameters
• In database configuration parameters

The reason code indicates more specifically why this message was returned:

1

Compression-related or encryption-related parameters were specified with the BACKUP DATABASE command while one of the database configuration parameters ENCRLIB and ENCROPTS was also set.

2

The BACKUP DATABASE command specified one of the parameters ENCRLIB or ENCROPTS as well as one of the parameters COMPRLIB or COMPROPTS.

Explanation

In a multiple database environment, when one of the databases was activated, the database could not get as much memory as it wanted. This will affect how large that database can grow in the future. This message can be returned when the CF self-tuning memory is enabled and database memory configuration parameter CF_DB_MEM_SZ is set to AUTOMATIC. If the instance is hosting more than one database, either:

• Too many database were activated at the same time, or
• The instance is hosting databases with both fixed and automatic CF_DB_MEM_SZ setting. The databases with fixed CF_DB_MEM_SZ are not leaving enough CF memory for the databases with AUTOMATIC CF_DB_MEM_SZ.

Explanation

An online fix pack update applies a new fix pack level to members and cluster caching facilities (CFs) while the instance remains available. However, the ability to set registry variable DB2_DATABASE_CF_MEMORY to AUTO is blocked until after the instance is committed.

Explanation

You can convert row-organized tables into column-organized tables by using the db2convert command.

If an attempt to convert tables fails, you can cancel pending conversion changes by calling the db2convert command with the -cancel parameter.

This message is returned when the db2convert command is called with the -cancel parameter, but no matching conversion operation has failed.

Explanation

To rollforward (or recover) through an upgrade operation requires multiple steps. This message is returned when the rollforward utility has reached an upgrade operation in the logs, which means additional actions are required to complete the rollforward operation.

Explanation

When the rollforward utility encounters an upgrade operation in the database logs, the utility performs verification tests before replay of the upgrade operation can continue.

This message is returned when the rollforward utility detects an upgrade operation in the database logs and verification tests fail for one of the following reasons:

1

Not all transactions before the upgrade have been successfully replayed. (For example, a transaction that is in doubt cannot be replayed.)

2

A table space is in a state that is not supported with rollforward operations.