Messages BMC396300 through BMC396399

TB tableOwner.tableName LINK HISTORY IS SET TO YES BUT NO HISTORY TABLE INFORMATION SPECIFIED.

Explanation: You specified to link the history table to the base table, but you did not specify the history table.

User response: Specify the history table.

RC = returnCode RESOLVING COPY DYNAMIC EXPORT DATASET NAME

PREFIX: prefix

Explanation: The JCL Generation component was unable to resolve the name of a dynamically allocated EXPORT data set.

User response: Verify that the symbolic variables that are specified in the name of the data set are correct. If you are unable to correct the problem, contact BMC Customer Support.

DB.TS databaseName.tableSpaceName - LENGTH ERROR IN COPY DYNAMIC EXPORT DATASET NAME DATASET dataSetName

Explanation: The name of the data set for the dynamically allocated EXPORT data set resolved to a length of zero or more than 44 bytes. The BMC ALTER for DB2 or BMC CHANGE MANAGER for DB2 product appends a period, two-character abbreviation, and six-digit number (such as .EX123456) to the prefix to create the name of the data set. The data set name that you specify in the JCL Generation override panels must allow for the additional nine bytes.

User response: Correct the name of the prefix for the EXPORT data set in the JCL Generation override panels.

TABLES LISTED BELOW HAVE DROP RESTRICT AND ARE BEING REBUILT IN THIS WORKLIST

Explanation: One or more tables in the worklist are defined with DROP RESTRICT. As a result, the BMC CHANGE MANAGER for DB2 product will re-create the tables.

User response: No action is required.

PARTCOPY TURNED ON TO SUPPORT BMCREORG AND NODYNREORG

Explanation: The worklist contains a reorganization that uses the BMC REORG PLUS for DB2 utility and contains the NODYNREORG ALUIN keyword. The BMC CHANGE MANAGER for DB2 product automatically added the PARTCOPY ALUIN keyword to support the utility and to provide a partition-level image copy of the partitioned table space or index, if required.

User response: No action is required.

INDEX COPY NOT INCLUDED IN WORKLIST WHEN TABLESPACE IS DEFINED AS NOT LOGGED. IX indexOwner.indexName

Explanation: The worklist contains an index that is defined as COPY YES. The table space that contains the table referenced by the index is defined as NOT LOGGED. DB2 requires that the image copy command for the index must be in the same copy command as the table space. However, image copies for table spaces and indexes are in independent commands in the worklist. As a result, the index image copy was omitted from the worklist.

User response: Perform an image copy of the index and table space in a post-worklist process.

SYSTEM TEMPORAL TABLE tableOwner.tableName IS MISSING REQUIRED required COLUMN.

Explanation: The named system-period temporal table requires an 'AS ROW BEGIN,' 'AS ROW END,' and 'AS TRANSACTION START ID' default value column.

User response: Add the missing column.

INDEX indexOwner.indexName FOR AUX TABLE tableOwner.tableName CANNOT BE EXPLICITLY DROPPED.

Explanation: You attempted to drop an index for an auxiliary table without dropping the auxiliary table.

User response: Either undo the drop for the auxiliary index, or drop the auxiliary table.

TABLES tableOwner.tableName1 AND tableOwner.tableName2 ARE LINKED TO THE SAME HISTORY OR SYSTEM TEMPORAL TABLE tableOwner.tableName3.

Explanation: Two tables have a versioning relationship with a third table. The two tables could be either two history tables that are linked to the same system-period temporal table, or two system-period temporal tables that are linked to the same history table.

User response: Return to Specification and resolve the conflict. Either remove the link between one of the two tables to the third table, or specify a new history table or system-period temporal table.

HISTORY TABLE COLUMN tableOwner.tableName.columnName CANNOT BE reason COLUMN.

Explanation: You defined a column for a history table with an invalid clause. The variable reason represents the following values:

• AS GENERATED ALWAYS
• AS ROW BEGIN
• AS ROW END
• AS TRANSACTION START ID
• ROWID IS NOT SET TO GENERATED ALWAYS
• AN IDENTITY
• A GENERATED BY DEFAULT ROW CHANGE TIMESTAMP
• A GENERATED ALWAYS AS

User response: Return to Specification. In the table column list, change the default value for the column to N, and specify a blank for the period.

ALTER AND CHANGE MANAGER DO NOT SUPPORT DB2 VERSION 11 OBJECT type objectCreator.name. REASON: reason

Explanation: The specified object exploits a feature of DB2 Version 11 that ALTER and CHANGE MANAGER do not support. The variable reason represents one of the following explanations:

ALTER AND CHANGE MANAGER DO NOT SUPPORT DB2 VERSION 11 OBJECT type objectCreator.name. REASON: reason

Explanation: The specified object exploits a feature of DB2 Version 11 that ALTER and CHANGE MANAGER do not support. The variable reason represents one of the following explanations:

THE FOLLOWING TABLES ARE VERSIONED. THIS MAY AFFECT LOADS AND UNLOADS IN THE LOB DATA MOVER PROGRAM. IF YOU ADDED ONE OR MORE LOB COLUMNS TO ANY OF THE TABLES AFTER YOU REORGANIZED THE TABLES, PERFORM ONE OF THE FOLLOWING ACTIONS: REORGANIZE THE TABLES AND THEN EXECUTE THE WORKLIST, OR DESELECT THE USE LOBDATAMOVER FOR LOBS OPTION AND RERUN ANALYSIS. tableOwner.tableName

Explanation: You attempted to make changes to versioned tables. If you have added LOB columns to these tables after you reorganized the tables, then this will affect the ability of the LOB DATA MOVER program (LOBDATAMOVER) to perform LOAD and UNLOAD.

User response: Perform one of the following actions:

• Reorganize the tables and then execute the worklist

• Deselect the USE LOBDATAMOVER FOR LOBS option and rerun Analysis

objectType owner.name attribute FOR COLUMN columnName IN BASE TABLE DOES NOT MATCH COLUMN IN THE MQT COLLIST

Explanation: The specified column attribute does not match the attribute of the respective column in the materialized query table column list.

User response: No action is required.

THE FOLLOWING TABLES ARE INCLUDED IN A TABLE SPACE OR INDEX SPACE THAT IS DEFINED WITH THE DEFINE NO ATTRIBUTE. WHETHER OR NOT YOU INCLUDE THE UNLOADEMPTY KEYWORD IN THE ALUIN INPUT STREAM, ANALYSIS GENERATES THE -ISMT STATEMENT. ANALYSIS DOES NOT GENERATE UNLOAD AND LOAD STATEMENTS.

Explanation: You have attempted to make changes to tables that are included in a table space or in an index space that has been defined with the DEFINE NO attribute. The UNLOADEMPTY keywork is not valid with this configuration. Consequently, Analysis generates the -ISMT statement, and does not generate unload or load statements.

User response: No action is required.

LIMIT KEY VALUES FOR THE FOLLOWING TABLE SPACE OVERLAP ON THE EXISTING LAST PARTITION AND THE ROTATED PARTITIONS. PARTITIONS CANNOT BE ROTATED UNTIL CHANGES ARE MADE TO THE SPECIFIED LIMIT KEYS. TS dataBaseName.tableSpaceName

Explanation: Limit key values on the current last partition and rotated partition overlap. Edit the limit key on the existing last partition to enable new partitions to be rotated. The rotated partitions may be required to prevent any loss of data from the last partition.

User response: Carefully verify the data and determine if rows exist in the overlap.

• If no data exists in the overlap range, add the ALLOWREORG keyword to the ALUIN input stream. Analysis will generate a worklist that:

  • Alters limit keys and reorganizes the table space

  • Rotates partitions

  Warning

  Data loss can occur if you do not accurately verify whether there are rows in the overlap range.

• If data exists in the overlap range, partitions cannot be rotated. You will need to manually specify the limit key changes and allow REORG to discard the desired rows. Analysis will generate a worklist that alters limit keys and reorganizes the table space.

  Rows will probably be discarded according to the limit key specifications.

type CreatorName COL columnName IS A ROW CHANGE TIMESTAMP COLUMN AND CANNOT BE USED IN AN MQT.

Explanation: You have included a row change timestamp column in a materialized query table (MQT), which is not supported.

User response: Re-create the MQT without this column. Then, rerun Analysis.

EARLY REORG WAS REQUIRED FOR TS TO ENSURE SUCCESS OF SUBSEQUENT ALTERS

Explanation: To ensure that the worklist can be successfully executed, the product performed a REORG to materialize pending changes to the definition of the table space. Additional alters may occur that would require a subsequent REORG of this table space.

User response: No action is required.

TABLESPACE WAS REORGED AS A RESULT OF ALLOWREORG ALUIN KEYWORD. databaseName.tableSpaceName

Explanation: The ALLOWREORG ALUIN keyword was used to allow Analysis to generate a REORG statement for the named table space or table spaces. A previous Analysis process issued either message BMC396318E or BMC396319E.

User response: Review either message BMC396318E or BMC396319E.

TABLESPACE WAS REBUILT AS A RESULT OF ALLOWREBUILD ALUIN KEYWORD.dataBaseName.tableSpaceName

Explanation: The ALLOWREBUILD ALUIN keyword was used to allow analysis to generate UNLOAD, DROP, CREATE, and LOAD statements for the listed table space. A previous Analysis process issued message BMC396318E.

User response: Review message BMC396318E.

WORKLIST CONTAINS OBJECT WITH ROLE AS OWNER. WORKLIST MUST BE EXECUTED USING TRUSTED CONTEXT TO PRESERVE ROLE OWNERSHIP. ANALYSIS PROCESSED WITH ROLEOWN, AUTHSWOFF WAS SET AUTOMATICALLY.

Explanation: You have created a worklist with the ROLEOWN option. As the result, the AUTHSWOFF option was automatically set. Objects in the worklist are intended to have a ROLE as OBJECT OWNER.

User response: Execute the worklist using TRUSTED CONTEXT to preserve object ownership by a ROLE.

WORKLIST CONTAINS OBJECT WITH ROLE AS OWNER. WORKLIST MUST BE EXECUTED USING TRUSTED CONTEXT TO PRESERVE ROLE OWNERSHIP. RERUN ANALYSIS USING OVERRIDE ROLEOWN OR DEFAULT OPTION ROLEOWN=Y. objectCode objectName ROLE roleName

Explanation: You have created a worklist that contains an object under a TRUSTED CONTEXT with ROLE as OBJECT OWNER.

User response:

1. Use the ROLEOWN ALUIN keyword to override the installation option, or change the setting of the ROLEOWN installation option to Y.

2. Rerun Analysis.

3. Execute the worklist using the proper TRUSTED CONTEXT to preserve the ownership of the objects by a ROLE.

DB2IGNORE IS SPECIFIED IN THE ALUIN INPUT STREAM. AS A RESULT, UNPREDICTABLE AND POSSIBLY UNDESIRABLE RESULTS MIGHT OCCUR.

Explanation: You are attempting to create a worklist for objects that are not currently supported. The worklist does not have all of the information needed to recreate the objects as they are currently are on the catalog.

User response: No action is required.

ARCHIVE TB tableOwner.tableName CANNOT BE A CLONE TABLE OR A TABLE WITH A CLONE DEFINED ON IT.

Explanation: You attempted to designate a clone table or a table with a clone defined on it as an archive table, which is not supported.

User response: Return to Specification and select a table that is neither a clone table or a table with a clone defined on it. Then, rerun Analysis.

TABLES tableOwner.tableName AND tableOwner.tableName ARE LINKED TO THE SAME ARCHIVE-ENABLED TABLE OR AN ARCHIVE TABLE tableOwner.tableName.

Explanation: You attempted to link two tables as archives to the same archive-enabled table, or to link two archive-enabled tables to the same archive table.

User response: Return to Specification, and select a different table. Then, rerun Analysis.

ARCHIVE TB tableOwner.tableName CANNOT BE IN A MULTI-TABLE TABLE SPACE.

Explanation: You have created or assigned an archive table in a multi-table table space, which is not supported.

User response: Return to specification and remove other tables in table space or move table to a new table space. Then, rerun Analysis.

TB tableOwner.tableName LINK ARCHIVE IS SET TO YES BUT NO ARCHIVE TABLE INFORMATION SPECIFIED.

Explanation: You have linked an archive-enabled table to an archive table, but you have not specified the archive table information.

User response: Return to Specification and specify the archive table information. Then, rerun Analysis.

ARCHIVE-ENABLED TABLE tableOwner.tableName HAS DIFFERENT NUMBER OF COLUMNS THAN ARCHIVE TABLE tableOwner.tableName.

Explanation: The archive-enabled table and the linked archive table must have the same number of columns.

User response: Return to Specification and make the necessary changes to the tables, or link the archive-enabled table to a different table. Then, rerun Analysis.

COLUMNS FOR TABLE tableOwner.tableName DO NOT MATCH COLUMNS FOR ARCHIVE TABLE tableOwner.tableName.

Explanation: The column definitions of the archive-enabled table and the archive table do not match.

User response: Return to Specification and make the necessary changes to the tables, or link the archive-enabled table to a different table. Then, rerun Analysis.

ARCHIVE TABLE tableOwner.tableName FOR ARCHIVE-ENABLED TABLE tableOwner.tableName NOT FOUND.

Explanation: The product cannot find the archive table that you linked to the archive-enabled table.

User response: Return to Specification and verify the name of the archive table. Then, rerun Analysis.

ARCHIVE-ENABLED TABLE COLUMN DOES NOT MATCH ARCHIVE TABLE COLUMN.tableOwner.tableName.columnName tableOwner.tableName.columnName reason

Explanation: The named columns in the archive-enabled table and the archive table do not match. The variable reason represents the following values:

• CCSID
• COLUMN LENGTHS
• COLUMN NAMES
• DATA TYPES
• FIELDPROCS
• HIDDEN VALUES
• NULL ATTRIBUTES
• PRECISION
• SUBTYPES
• Table encoding schemes are different for columns with CCSID values greater than zero

User response: Return to Specification and make the necessary changes to the tables, or link the archive-enabled table to a different table. Then, rerun Analysis.

ARCHIVE-ENABLED TABLE OR AN ARCHIVE TABLE COLUMN tableOwner.tableName.columnName CANNOT BE reason COLUMN.

Explanation: The column has an attribute that is unsupported for archive or archive-enabled tables.

User response: Return to Specification and change the column attribute. Then, rerun Analysis.

VERSIONING TB tableOwner.tableName CANNOT BE AN ARCHIVE TABLE OR AN ARCHIVE-ENABLED TABLE.

Explanation: A versioning table cannot be an archive table or an archive-enabled table.

User response: Return to Specification and select a different table as an archive table or an archive-enabled table. Then rerun Analysis.

BASE TABLE tableOwner.tableName MISSING ARCHIVE TABLE tableOwner.tableName IN MIGRATE.

Explanation: You are attempting to migrate an archive-enabled table without the corresponding archive table.

User response: Return to Specification and select the archive table for migration. Then, rerun Analysis.

ARCHIVE TABLE tableOwner.tableName MISSING BASE TABLE baseTableOwner.baseTableName IN MIGRATE. ALTER/DROP FOR ARCHIVE CONNECTIONS COMMENTED OUT IN WORKLIST.

Explanation: You selected to migrate an archive table, but did not select the corresponding archive-enable table.

User response: Return to Specification and select the archive-enabled table for migration. Then, rerun Analysis.

tableOwner.tableName.columnName CREATION OF INDEX-CONTROLLED PARTITIONED OBJECTS IS NOT ALLOWED. TS databaseName.tableSpaceName.

Explanation: You cannot create an index-controlled partitioned object in this work ID because either the STOPICP installation option is Y or the STOPICP keyword is in the ALUIN input stream.

User response:

1. Undo the specified changes for the object.

2. Make the object a table-controlled partitioned object and re-specify the changes, as follows:

   • If the object is new (you are creating it), specify it as a table-controlled partitioned object.

   • If the object is not new, convert it to a table-controlled partitioned object and re-specify your changes.

   • If you are migrating the object, convert it to a table-controlled partitioned object.

3. Rerun Analysis.

CREATION OF INDEX-CONTROLLED PARTITIONED OBJECTS IS NOT ALLOWED. INDEX-CONTROLLED PARTITIONED OBJECTS CANNOT BE INCLUDED IN THE SCOPE OF OR RECOVERED FROM A FULL-RECOVERY BASELINE. databaseName.tableSpaceName

Explanation: For index-controlled partitioned objects, you attempted to create a full-recovery baseline or to recover to a full-recovery baseline. These actions are not allowed in the worklist because the STOPICP installation option is Y or the STOPICP keyword is in the ALUIN input stream..

User response: If you are creating a full-recovery baseline, complete the following steps:

1. Create and execute a separate worklist that will convert index-controlled partitioned objects to table-controlled partitioned objects.

2. Create and execute the worklist to establish a full-recovery baseline.

1. Set the IBM DB2 DSNZPARM option PREVENT_NEW_IXCTRL_PART to N.

2. Add the ALLOWICP keyword to the ALUIN DD input stream.

3. Run Analysis using the option to reload data from a previous full-recovery baseline.

4. Execute the worklist to recover the baseline.

5. Reset PREVENT_NEW_IXCTRL_PART to Y.

6. Create and execute a separate worklist that will convert index-controlled partitioned objects to table-controlled partitioned objects.

7. Create and execute a separate worklist to establish a full-recovery baseline.

CREATION OF INDEX-CONTROLLED PARTITIONED OBJECTS MIGHT BE PROHIBITED BY DSNZPARM SETTING PREVENT_NEW_IXCTRL_PART.

Explanation: This worklist contains create statements for index-controlled objects. Whether or not these objects can be created is dependent upon the DSNZPARM PREVENT_NEW_IXCTRL_PART.

User response: Verify that the IBM DB2 subsystem DSNZPARM option PREVENT_NEW_IXCTRL_PART is set to N and is correctly configured. This setting (N) enables index-controlled partitioned objects to be created in the worklist.

DB2 SUBSTITUTED FOR UNCONVERTIBLE CHARACTER(S) IN THE FOLLOWING STORED PROCEDURES schema.storedProcedureName VER version

Explanation: In the specified stored procedures, IBM DB2 replaced characters that could not be converted.

User response: No action is required.

DROP AND CREATE STATEMENTS GENERATED FOR VERSIONED TABLE tableOwner.tableName TO ADD CLONE TABLE tableOwner.tableName

Explanation: The OLDEST_VERSION of the versioned table does not match the CURRENT_VERSION of the table in the table space. Before Analysis can generate a statement to add a clone table to the versioned table, Analysis must generate statements to drop the versioned table and then create the table.

User response: No action is required.

WHEN THE DSSIZE OF A TABLE SPACE IS GREATER THAN 4 GB, DB2 REQUIRES THAT THE TABLE SPACE AND THE INDEX SPACE USE EXTENDED ADDRESSIBILITY ENABLED DASD DEVICES (STOGROUPS).

Explanation: IBM DB2 encountered a table space with a DSSIZE that exceeds 4 GB. For that table space and index space, DB2 will use extended addressability enabled DASD devices, or STOGROUPS.

User response: Ensure that the STOGROUP uses extended addressibility.

IN TABLESPACE databaseName.tableSpaceName, THE VALUE OF FREEPAGE IS GREATER THAN OR EQUAL TO THE VALUE OF SEGSIZE. AS A RESULT, DB2 WILL CHANGE THE VALUE OF FREEPAGE TO EQUAL SEGSIZE MINUS ONE

Explanation: The value you specified for FREEPAGE is greater than or equal to the value of the existing SEGSIZE. As a result, DB2 will change the value of FREEPAGE to one less than SEGSIZE.

User response: No action is required.

TABLESPACE databaseName.tableSpaceName HAS BEEN DROPPED AND REBUILT. REASON: THE NEW VALUE FOR FREEPAGE IS GREATER THAN OR EQUAL TO THE CURRENT VALUE FOR SEGSIZE

Explanation: The value you specified for FREEPAGE is greater than or equal to the value of the existing SEGSIZE. As a result, Analysis generated commands to drop and create the table space.

User response: No action is required.

ERROR WITH EXCLUDE NULL KEYS FOR INDEX indexOwner.indexName. REASON reason

Explanation: The option to include null key values was set to N for the named index. However, the index meets one of the following conditions and the null key values cannot be excluded:

• CANNOT BE AN XML INDEX

• INVALID WITH BUSINESS_TIME WITHOUT OVERLAPS

• CANNOT HAVE A KEY EXPRESSION

• CANNOT BE A UNIQUE INDEX

• CANNOT HAVE AN INCLUDE KEY

• HAS A KEY COLUMN THAT IS NOT NULL

• CANNOT BE A PARTITIONING INDEX FOR ICP

User response: Return to Specification, edit the index, and set the Include Null Keys option to Y. Then, rerun Analysis.

TO SUPPORT TAKING COPIES USING A GDG, DYNCOPY HAS BEEN TURNED ON.

Explanation: You have selected to use GDG image copy data sets. In addition, you selected the following Analysis options:

• Use dynamic REORG data sets

• Do not use dynamic COPY data sets

User response: No action is required.

TO SUPPORT TAKING COPIES USING A GDG, DYNREORG HAS BEEN TURNED ON.

Explanation: You have selected to use generation data group (GDG) image copy data sets. In addition, you selected the following Analysis options:

• Use dynamic REORG data sets

• Use dynamic COPY data sets

User response: No action is required.

COPIES USING A GDG CANNOT MIX DYNAMIC AND STATIC ALLOCATION. CHANGE DYNCOPY TO NODYNCOPY OR REMOVE THE GDG FROM COPY PREFIX AND RERUN ANALYSIS.

Explanation: You have selected to use generation data group (GDG) image copy data sets. In addition, you selected the following Analysis options:

• Do not use dynamic REORG data sets

• Use dynamic COPY data sets

• Operations are being performed on tables with XML columns

• Operations are being performed on a partition-by-growth table space that contains a table with XML or AUX columns

User response: Perform one of the following actions:

• If dynamic COPY data sets are not required, edit the ALUIN input stream and change DYNCOPY to NODYNCOPY. Then, rerun Analysis.

• If dynamic COPY data sets are required, edit the JCL Generation options for the copy data set and remove the (&GDG) from the prefix. Then, rerun Analysis.

COPIES USING A GDG CANNOT MIX DYNAMIC AND STATIC ALLOCATION. REMOVE THE GDG FROM COPY PREFIX AND RERUN ANALYSIS

Explanation: You have selected to use generation data group (GDG) image copy data sets. In addition, you selected the following Analysis options:

• Do not use dynamic REORG data sets

• Use dynamic COPY data sets

• Operations are being performed on tables with XML columns

• Operations are being performed on a partition-by-growth table space that contains a table with XML or AUX columns

User response: Edit the JCL Generation options for the copy data set and remove the (&GDG) from the prefix. Then, rerun Analysis.

COPIES USING A GDG CANNOT MIX DYNAMIC AND STATIC ALLOCATION. CHANGE NODYNREORG TO DYNREORG AND RERUN ANALYSIS.

Explanation: You have selected to use generation data group (GDG) image copy data sets. In addition, you selected the following Analysis options:

• Do not use dynamic REORG data sets

• Use dynamic COPY data sets

User response: Eedit the ALUIN input stream and change NODYNREORG to DYNREORG. Then, rerun Analysis.

EARLY REORG WAS REQUIRED FOR TS TO ENSURE SUCCESS OF ALTER FREEPAGE. databaseName.tableSpaceName

Explanation: Analysis generated a worklist to reorganize the named table space before altering the FREEPAGE attribute.

User response: No action is required.

INDEX indexOwner.indexName REQUIRES A REBUILD BECAUSE TABLE tableOwner.tableName HAS A CLONE, BUT YOU HAVE SELECTED THE NOREBUILD OPTION.

Explanation: You specified to add an index to a base table that has a clone table. This action places the index in rebuild-pending status. The Analysis component cannot include a utility command to reorganize the associated table space or to rebuild the index because you have specified the NOREORG and the NOREBUILD keywords in the ALUIN input stream.

User response: In the Analysis override options, choose to use the NGT Recover utility or the IBM REBUILD INDEX utility to allow Analysis to include a rebuild utility in the worklist. Then, rerun Analysis.

Utility BMCUtilityName DOES NOT SUPPORT DB2 VERSION 11.

Explanation: You have selected a BMC utility that currently does not support DB2 V11. The relevant utilities are:

• BMC REORG PLUS for DB2

• BMC CHECK PLUS for DB2

• BMC UNLOAD PLUS for DB2

• BMC LOADPLUS for DB2

User response: Select the suitable alternative utility, and rerun the worklist:

• IBM REORG

• IBM CHECK

• IBM UNLOAD

• IBM LOAD

tableOwner.tableName USES THE EXTENDED RBA FORMAT.

Explanation: You are creating a migrate type worklist using one of the following products or solutions:

• The NGT Recover product

• The NGT Copy EXPORT and NGT Recover IMPORT option (part of the Copy Migration feature in the BMC Recovery Management for DB2 and BMC Database Administration for DB2 solutions)

User response: Ensure that the table space on the receive side has an extended RBA format.

TABLE tableOwner.tableName CANNOT BE AN ARCHIVE TABLE OR AN ARCHIVE-ENABLED TABLE. REASON: TABLE reason

Explanation: The specified table cannot be used as an archive table or an archive-enabled table for the given reason.

User response: Return to Specification and select a different table. Then rerun Analysis.

TABLE tableOwner.tableName CANNOT USE ARCHIVE-ENABLED TABLE tableOwner.tableName AS AN ARCHIVE.

Explanation: You are attempting to use an archive-enabled table as an archive, which is not supported.

User response: Return to Specification and select or generate a different table. Then rerun Analysis.

TB tableOwner.tableName CANNOT BE ADDED TO A TABLESPACE THAT HAS AN ARCHIVE TABLE OR AN ARCHIVE-ENABLED TABLE.

Explanation: An archive table or archive-enabled table must be the only table in a table space.

User response: Return to Specification and add the table to a different table space. Then rerun Analysis.

TB tableOwner.tableName CANNOT BE ADDED TO A TABLESPACE THAT HAS A SYSTEM-TEMPORAL TABLE OR A HISTORY TABLE.

Explanation: An system-temporal table or history table must be the only table in a table space.

User response: Return to Specification and add the table to a different table space. Then rerun Analysis.

TABLE tableOwner.tableName CANNOT BE A SYSTEM-TEMPORAL TABLE OR A HISTORY TABLE. REASON: TABLE reason

Explanation: The named table cannot be a system-temporal table or a history table. The variable reason represents the following values:

• IS A MATERIALIZED QUERY TABLE
• IS A CLONE OR IS IN A CLONE RELATIONSHIP
• IS A CATALOG TABLE
• IS IN A MULTI-TABLE TABLE SPACE
• Encoding Scheme does not match
• IS AN AUXILIARY TABLE
• IS A GLOBAL TEMPORARY TABLE
• IS AN IMPLICIT TABLE FOR XML COLUMN
• IS A VIEW
• IS AN ARCHIVE TABLE
• IS A SECURITY LABEL COLUMN
• IS INCOMPLETE

User response: Return to Specification and select a different table. Then, rerun Analysis.

ARCHIVE TABLE COLUMN tableOwner.tableName.columnName IS INVALID. REASON: ROWID IS NOT SET TO GENERATED ALWAYS.

Explanation: You have selected an identity column for the archive table. However, the column is not defined as GENERATED ALWAYS.

User response: Return to Specification and define the column as GENERATED ALWAYS. Then rerun Analysis.

CANNOT USE LOBDATAMOVER FOR TABLE tableOwner.tableName. REASON: INDEX WITH ROWID KEY indexOwner.indexName IS PADDED.

Explanation: LOB DATA MOVER program requires a non-padded index.

User response: Select the IBM UNLOAD and IBM LOAD utilities, or select the BMC UNLOAD PLUS and BMC LOADPLUS utilities. Then, rerun Analysis.

SUPPORT FOR SPANNED RECORDS HAS NOT BEEN ACTIVATED.

Explanation: The product currently does not support the use of spanned records.

User response:

1. Perform one of the following actions:

   • Edit your installation options and set SPANNED to N.

   • Edit your ALUIN input stream and change SPANNEDRECS to NOSPANNEDRECS.

2. Then, rerun Analysis.

LIMIT KEY VALUES FOR THE FOLLOWING TABLE SPACE OVERLAP ON THE EXISTING LAST PARTITION AND THE ROTATED PARTITIONS. PARTITIONS CANNOT BE ROTATED UNTIL CHANGES ARE MADE TO THE SPECIFIED LIMIT KEYS. TS databaseName.tableSpaceName

Explanation: Limit key values on the current last partition and rotated partition overlap. Edit the limit key on the existing last partition to enable new partitions to be rotated. The rotated partitions may be required to prevent any loss of data from the last partition.

User response: Carefully verify the data and determine if rows exist in the overlap.

• If no data exists in the overlap range, add the ALLOWREORG keyword to the ALUIN input stream. Analysis will generate a worklist that:

  • Alters limit keys and reorganizes the table space

  • Rotates partitions

  Warning

  Data loss can occur if you do not accurately verify whether there are rows in the overlap range.

• If data exists in the overlap range, partitions cannot be rotated. You will need to manually specify the limit key changes and allow REORG to discard the desired rows. Analysis will generate a worklist that alters limit keys and reorganizes the table space.

  Rows will probably be discarded according to the limit key specifications.

LIMIT KEY CHANGES WERE SPECIFIED FOR THE FOLLOWING INDEX BUT THE TABLE FOR THE INDEX IS BEING CHANGED TO TABLE CONTROLLED PARTITIONING.

Explanation: You are changing the table to table-controlled partitioning (TCP) from index-controlled partitioning (ICP). You have made changes to the index limit keys, instead of to the table limit keys. Those changes will be lost.

User response: Return to Specification, undo the index limit key changes and make these changes to the table limit keys. Then, rerun Analysis.

USING SPANNED RECORDS FOR DATA RECOVERY. BASELINE DATA WAS UNLOADED USING SPANNED RECORD FORMAT

Explanation: Because the full-recovery baseline was created using spanned records, Analysis must also use spanned records for data recovery.

User response: On the Analysis Worklist Options panel, select Use spanned records. Then, rerun Analysis.

DYNUNLD REQUIRED TO SUPPORT SPANNED RECORD FORMAT

Explanation: The ALUIN input stream does not include the DYNUNLD keyword, which is required when SPANNEDRECS is included in the ALUIN input stream. DYNUNLD dynamically allocates the unload (SYSREC) and discard (SYSDISC) data sets.

User response: Add DYNUNLD to the ALUIN input stream. Then, rerun Analysis.

TB tableOwner.tableName HAS NO STATS, SYSDISC SIZE AND NUMBER OF ROWS DEFAULTED

Explanation: The selected table has no statistical information, therefore the product used default values for the number of rows and the size of the discard (SYSDISC) data set.

User response: No action is required.

TB tableOwner.tableName HAS NO STATS, NUMBER OF ROWS DEFAULTED

Explanation: The selected table has no statistical information. As a result, the product used default values for the number of rows.

User response: No action is required.

NOLOBDATA AND NOXMLDATA ARE INCOMPATIBLE WITH SPANNED RECORD FORMAT

Explanation: The NOLOBDATA and NOXMLDATA ALUIN keywords are not supported in a table that uses spanned record format.

User response: Remove the keywords. Then, rerun Analysis.

USE OF DYNAMIC SYSRECS IS REQUIRED FOR LOB OR XML DATA WHEN USING BMC UNLOAD PLUS AND BMC LOAD PLUS

Explanation: This message is always displayed in addition to message BMC45667E. You selected to use the BMC UNLOAD PLUS and BMC LOADPLUS utilities to unload and load data. However, either you specified NODYNUNLD in the ALUIN input stream or the DYNUNLD installation option is set to N.

User response: Either change the NODYNUNLD keyword to DYNUNLD in the ALUIN input stream, or select the IBM UNLOAD and IBM LOAD utilities.

TRIGGER triggerSchema.triggerName IS NOT SECURE, YET IT IS DEFINED FOR A TABLE THAT IS USING ROW ACCESS CONTROL OR COLUMN ACCESS CONTROL.

Explanation: You did not specify the Trigger as SECURE YES. The base table is defined with either ROW ACCESS CONTROL or COLUMN ACCESS CONTROL, so DB2 requires the trigger to be specified as SECURED.

User response: Return to Specification and change the value of SECURE from N to Y. Then, rerun Analysis.

BMC REORG PLUS DOES NOT SUPPORT THE DB2 VERSION version

OBJECT objectType objectName.

REASON: reason

SELECT IBM REORG AND RERUN ANALYSIS.

Explanation: You selected to use the BMC REORG PLUS utility. However, the process made changes to the table space that result in pending DDL, which is not supported for one of the following reasons:

User response: In the ALUIN input stream, change the BMCREORG keyword to IBMREORG. Then, rerun Analysis.

TB tableOwner.tableName REFERENCED IN WORKID IS ADDED TO IDAA

Explanation: You are trying to modify a table that is registered to IDAA.

User response: Unregister the table from IDAA, or return to Specification and specify the IDAAIGNORE ALUIN keyword. Then, rerun Analysis.

TB tableOwner.tableName REFERENCED IN WORKID IS ADDED TO IDAA

Explanation: You are trying to modify a table that is registered to IDAA, and have specified the IDAAIGNORE overide. The product will modify standard IDAA tables, but will ignore type D IDAA tables and their table spaces.

User response: After the worklist has been executed, you must ensure that all the IDAA tables are correctly registered.

OPTIONS SPECIFIED ALLOW THESE UTILITIES:

utility

Explanation: Based on the options that you specified, the worklist will use one of the following utilities:

• BMC REORG PLUS
• NGT Reorg
• NGT Unload / NGT Load
• BMC UNLOAD PLUS / BMC LOADPLUS

User response: No action is required.

AUXILIARY INDEX indexCreator.indexName HAS CHANGES FOR THE BUFFERPOOL TO OR FROM 4 KB AND CHANGES TO COMPRESS IN THE SAME WORK ID.

Explanation: You attempted to change both the bufferpool size value and the COMPRESS value for an auxiliary index in the same unit of work. Analysis cannot make both changes in the same work ID.

User response: Perform one of the following actions:

• If you want to increase the bufferpool size from 4KB and change the COMPRESS value from NO to YES:

  1. Return to Specification, and increase the bufferpool size.

  2. Run Analysis, and execute the worklist.

  3. In a subsequent work ID, change the COMPRESS value for the auxiliary index.

• If you want to change the bufferpool size to 4KB and change the COMPRESS value from YES to NO:

  1. Return to Specification, and make changes to the COMPRESS value for the auxiliary index.

  2. Run Analysis, and execute the worklist.

  3. In a subsequent work ID, change the bufferpool size.

ALTER AND CHANGE MANAGER DO NOT SUPPORT DB2 VERSION 12 OBJECT objectCodequalifiedObjectName. REASON: reason.

Explanation: You are trying to modify a DB2 Version 12 object, which is not supported for one of the following reasons:

User response: Select another utility to modify this object.

ALTER AND CHANGE MANAGER DO NOT SUPPORT DB2 VERSION 12 OBJECT objectCodequalifiedObjectName. REASON: reason.

Explanation: You are trying to modify a DB2 Version 12 object and included the DB2IGNORE keyword in the ALUIN input stream. This operation is not supported for one of the following reasons:

User response: Select another utility to modify this object.

TS databaseName.tableSpaceName REFERENCED IN WORKID HAS TABLE ADDED TO IDAA

Explanation: You are trying to modify a table space that has a table registered to IDAA.

User response: Unregister the table from IDAA, or return to Specification and specify the IDAAIGNORE ALUIN keyword. Then, rerun Analysis.

TS databaseName.tableSpaceName EXCLUDED FROM WORKLIST DUE TO IDAA ONLY TABLE AND IDAAIGNORE OVERRIDE

Explanation: You are attempting to modify a type D IDAA table, and have specified the IDAAIGNORE override. The worklist is generated, but it does not include the type D table and associated table space because ALTER and CHANGE MANAGER do not support type D tables.

User response: After the worklist has been executed, you must ensure that all the IDAA tables are correctly registered.

IDAAIGNORE IS SPECIFIED IN THE ALUIN INPUT STREAM. THE USER HAS RESPONSIBILITY FOR MANAGING IDAA TABLES BEFORE AND AFTER EXECUTION OF THE WORKLIST.

Explanation: You have specified IDAAIGNORE to force the generation of worklist with IDAA objects. However, ALTER and CHANGE MANAGER do not manage IDAA relationships.

User response: After the worklist has been executed, you must ensure that all the IDAA tables are correctly registered.

DB2IGNORE IS SPECIFIED IN THE ALUIN INPUT STREAM. HOWEVER, DB2IGNORE IS IGNORED FOR ADVANCED TRIGGER

Explanation: You have selected to rebuild, alter, migrate or recover an advanced trigger, and specified DB2IGNORE in the ALUIN input stream. However, ALTER and CHANGE MANAGER do not support advanced triggers and disregard the DB2IGNORE keyword.

User response: Return to Specification and exclude the advanced trigger and any dependent objects from the workID. Then, rerun Analysis.

CREATION OF INDEX-CONTROLLED PARTITIONED OBJECTS ARE PROHIBITED BY DSNZPARM SETTING PREVENT_NEW_IXCTRL_PART. TS databaseName.tableSpaceName

Explanation: You are attempting to like, migrate, or rebuild a table in the specified index-controlled partitioned table space. However, you have set the value of ZPARM PREVENT_NEW_IXCTRL_PART =YES for the specified table space.

User response: Take one of the following actions:

• Return to Specification, and change the table that you are attempting to like, migrate, or rebuild from index-controlled to table-controlled. Then, rerun Analysis.

• Change the value of the ZPARM. Then, rerun Analysis.

CREATION OF INDEX-CONTROLLED PARTITIONED OBJECTS ARE PROHIBITED BY DSNZPARM SETTING PREVENT_NEW_IXCTRL_PART BECAUSE ALLOWICP IS SPECIFIED IN THE ALUIN INPUT STREAM, UNDESIRABLE RESULTS MIGHT OCCUR.

Explanation: The IBM ZPARM PREVENT_NEW_IXCTRL_PART is set to YES, which does not permit index-controlled partitioning. However, you have also included the ALLOWICP keyword to the ALUIN input stream, which overrides this ZPARM. The worklist might fail during Execution.

User response: Check the Execution results.

CHECK ENVIRONMENT ROUTINE STARTED

Explanation: Execution is verifying that the environment parameters detected at execution time are the same as the values detected during Analysis.

User response: No action is required.

ZPARM check routine started

Explanation: The Execution process is verifying that the ZPARMs detected at execution time are the same as the values detected during Analysis.

User response: No action is required.

BATCH PROFILES ROUTINE STARTED - startDate startTime

Explanation: The ACMPROFB batch process has started.

User response: No action is required.

CHECK ENVIRONMENT ROUTINE FOR environmentParameter FAILED. VALUE IS executionValue

Explanation: For the specified environment parameter, the value detected during Execution did not match the value detected during Analysis.

User response: Correct the problem and rerun Analysis.

ZPARM CHECK FOR zparm analysisValue FAILED. VALUE IN ZPARM IS executionValue.

Explanation: For the specified ZPARM, the value detected during Execution did not match the value detected during Analysis. Specifically for a migrate worklist, if the value of the ZPARM is PREVENT_NEW_IXCTRL_PART = YES, you cannot create index-controlled partitions on the receiving SSID.

User response: Create a new work ID, and convert the index-controlled partitioned objects to table-controlled partitioned objects. Then, rerun Analysis.

CHECK ENVIRONMENT ROUTINE FAILED RC=8

Explanation: One or more parameter checks failed, causing Execution to stop. The work ID contains objects that are not valid.

User response: Remove the invalid objects from the work ID and rerun Analysis.

ZPARM CHECKS FAILED RC=8

Explanation: One or more ZPARM checks failed, causing the Execution to stop.

User response: Change the value of the ZPARM. Then, rerun Analysis.

BATCH PROFILES ROUTINE FAILED RC=returnCode

Explanation: The statements that you entered were not processed successfully and the job failed. Either the statements had incorrect syntax or a runtime error occurred.

User response: Correct the statements and resubmit the job.