Messages BMC396400 through BMC396499

For the ALTER and CHANGE MANAGER for DB2 products, this topic explains each message in the designated range.
Number Description
BMC396400I

CHECK ENVIRONMENT ROUTINE SUCCESSFUL RC=0

Explanation: The environment parameters that were detected during Analysis matched those detected during Execution.

User response: No action is required.

BMC396400I

ZPARM CHECKS SUCCESSFUL RC=0


Explanation: The product has verified that the values of the DB2 ZPARMs do not prevent Execution.

User response: No action is required.

BMC396401E

CHECK ENVIRONMENT ROUTINE FATAL ERROR error RC=12

Explanation: When checking environment parameters, the product discovered one or more incompatible values, which will prevent Execution.

User response: Call BMC Customer Support.

BMC396401E

ZPARM CHECKS FATAL ERROR error RC=12


Explanation: The product has checked the DB2 ZPARMs and discovered one or more incompatible values, which will prevent Execution.

User response: Call BMC Customer Support.

BMC396402E

LOB TS databaseName.tableSpaceName CANNOT BE COMPRESS YES. BASE TS databaseName.tableSpaceName IS NOT A UNIVERSAL TABLESPACE.


Explanation: You attempted to compress a LOB table space, but the base table space is not a universal table space, which is not supported. The product cannot perform the ALTER statement.

User response: Return to Specification, and correct the error. Then run Analysis, and execute the worklist.

BMC396403E

AUXILIARY INDEX indexOwner.indexName HAS CHANGES FOR THE BUFFER POOL TO OR FROM 4 KB AND CHANGES TO PIECESIZE IN THE SAME WORK ID.


Explanation: You attempted to change both the bufferpool size value and the PIECESIZE value for an auxiliary index in the same work ID. 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 then change the PIECESIZE value:

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

    2. Run Analysis, and execute the worklist.

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

  • If you want to change the change the PIECESIZE value and then increase the bufferpool size from 4KB:

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

    2. Run Analysis, and execute the worklist.

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

BMC396404E

AUXILIARY INDEX indexOwner.indexName HAS CHANGES TO COMPRESSION AND CHANGES TO PIECESIZE IN THE SAME WORK ID


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

User response: Perform one of the following actions:

  • If you want to change the COMPRESS value from NO to YES, and then change the PIECESIZE value:

    1. Return to Specification, and change the COMPRESS value for the auxiliary index from NO to YES .

    2. Run Analysis, and execute the worklist.

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

  • If you want to change the PIECESIZE value, and then change the COMPRESS value from NO to YES :

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

    2. Run Analysis, and execute the worklist.

    3. In a subsequent work ID, change the COMPRESS value from NO to YES.

BMC396405E

TB tableOwner.tableName COL column CHANGES TO BOTH DATATYPE AND SUBTYPE ARE NOT ALLOWED IN THE SAME WORK ID WHEN DDL_MATERALIZATION IS SET TO ALWAYS_PENDING.


Explanation: You attempted to change both the data type and the subtype of a column in the work ID the DB2 ZPARM DDL_MATERIALIZATION = ALWAYS_PENDING. Analysis cannot make both changes in the same work ID.

User response: Perform one of the following actions:

  • If you want to change the data type value, and then change the subtype value:

    1. Return to Specification, and change the data type value.

    2. Run Analysis, and execute the worklist.

    3. In a subsequent work ID, change the subtype value.

  • If you want to the change the subtype value, and then change the data type value:

    1. Return to Specification, and change the subtype value.

    2. Run Analysis, and execute the worklist.

    3. In a subsequent work ID, change the data type value.

BMC396406E

TB tableOwner.tableName COL column CHANGES TO BOTH DATATYPE AND DEFAULT VALUE ARE NOT ALLOWED IN THE SAME WORK ID WHEN DDL_MATERALIZATION IS SET TO ALWAYS_PENDING.


Explanation: You attempted to change both the data type and the default value of a column in the same work ID when the DB2 ZPARM DDL_MATERIALIZATION = ALWAYS_PENDING. Analysis cannot make both changes in the same work ID.

User response:

  • If you want to change the data type value, and then change the default value:

    1. Return to Specification, and change the data type value.

    2. Run Analysis, and execute the worklist.

    3. In a subsequent work ID, change the default value.

  • If you want to change the change the default value, and then change the data type value:

    1. Return to Specification, and then change the default value.

    2. Run Analysis, and execute the worklist.

    3. In a subsequent work ID, change the data type value.

BMC396407E

TB tableOwner.tableName COL column CHANGES TO BOTH LENGTH AND INLINE LENGTH ARE NOT ALLOWED IN THE SAME WORK ID WHEN DDL_MATERALIZATION IS SET TO ALWAYS_PENDING.


Explanation: You attempted to change both the length and inline length value of a column in the same work ID when the DB2 ZPARM DDL_MATERIALIZATION = ALWAYS_PENDING. Analysis cannot make both changes in the same work ID.

User response:

  • If you want to change the length value, and then change the inline length value:

    1. Return to Specification, and then change the length value.

    2. Run Analysis, and execute the worklist.

    3. In a subsequent work ID, change the inline length value.

  • If you want to change the change the inline length value, and then change the length value:

    1. Return to Specification, and change the inline length.

    2. Run Analysis, and execute the worklist.

    3. In a subsequent work ID, change the length.

BMC396408E

LOB TS databaseName.tableSpaceName COMPRESS ALTER IS NOT ALLOWED WITH OTHER LOB TS ALTERS

ALTER: CLOSE

ALTER: LOCKSIZE

ALTER: LOCKMAX

ALTER: ERASE

ALTER: PRIQTY

ALTER: SECQTY

ALTER: GBPCACHE

ALTER: STOGROUP


Explanation: You are attempting to perform ALTER COMPRESS on the specified LOB table space together with one of the listed ALTER statements that cannot be performed in the same work ID on the table space.

User response:

  • Return to Specification and ensure that only the ALTER COMPRESS statement is specified.

  • Run Analysis, and execute the worklist.

BMC396409I

DB2 CURRENT FUNCTION LEVEL IS VnnRnMnnn


Explanation: This message provides information about the current function level of the DB2 subsystem. This message is displayed only for DB2 Version 12 or later subsystems.

User response: No action is required.

BMC396411I

DB2 CATALOG LEVEL IS VnnRnMnnn


Explanation: This message provides information about the current catalog level of the DB2 subsystem. This message is displayed only for DB2 Version 12 or later subsystems.

User response: No action is required.

BMC396412E

ALTER AND CHANGE MANAGER DO NOT CURRENTLY SUPPORT THIS UTILITY ON DB2 VERSION 12: utilityName


Explanation: You have selected a utility that the product does not support on DB2 Version 12.

User response: Return to the Analysis override options and select a supported utility. Then run Analysis, and execute the worklist.

BMC396413E

ALTER AND CHANGE MANAGER DO NOT SUPPORT THIS UTILITY ON DB2 VERSION 12 WITH ALUIN KEYWORD DB2IGNORE SPECIFIED: utilityName


Explanation: You have inserted the DB2IGNORE keyword into the ALUIN input stream, and selected a utility that the product does not support on DB2 Version 12.

User response: Return to the Analysis override options and select a supported utility. Then run Analysis, and execute the worklist.

BMC396414E

ALTER AND CHANGE MANAGER DO NOT SUPPORT THIS UTILITY ON THE DB2 VERSION 12 OBJECT.

UTILITY: utilityName

OBJECT: objectOwner.objectName

REASON: reason


Explanation: You cannot use this utility on a DB2 Version 12 object, for one of the following reasons:

Reason

Description

PERIOD BUSINESS_TIME INCLUSIVE

You have defined BUSINESS_TIME INCLUSIVE on the specified table. This is not supported.

COMPRESS IX PENDING DDL

You want to compress an index, which results in pending DDL. This pending DDL is not supported.

PENDING DDL FROM DDL_MATERIALIZATION=ALWAYS_PENDING

You have set the DSNZPARM DDL_MATERIALIZATION= ALWAYS_PENDING. This pending DDL is not supported.

COMPRESS LOB TABLESPACE

You have a LOB table space that is compressed or has been altered to be compressed. This is not supported.

User response: Return to Specification and correct the error. Then run Analysis, and execute the worklist.

BMC396415W

TABLES ARE BEING CONVERTED TO TABLE CONTROLLED PARTITIONING. BECAUSE THE DB2 DSNZPARM IX_TB_PART_CONV_EXCLUDE = YES, FEWER TABLE-CONTROLLED PARTITIONING KEYS MIGHT EXIST IN THE PARTITIONING INDEX AFTER THE CONVERSION. IF A LIMIT KEY VALUE DEPENDS ON A PARTITIONING KEY THAT WAS EXCLUDED, EXECUTION MIGHT FAIL.


Explanation: You are converting one or more tables in the worklist to table-controlled partitioning and are altering the limit key values. The DSNZPARM IX_TB_PART_CONV_EXCLUDE keyword is set to YES. Execution might fail after the table has been converted when the limit key values are altered.

User response: Check if there are fewer partitioning keys in the partitioning index than before you converted the tables to table-controlled partitioned tables. If yes, perform one of the following actions:

    1. Set the value of the DSNZPARM IX_TB_PART_CONV_EXCLUDE keyword to NO.

    2. Then run Analysis, and execute the worklist.

    1. Create a new alter work ID.

    2. In the new work ID, alter the limit keys of the partitioning index.

    3. Then run Analysis, and execute the work ID.

    4. Reanalyze the work ID that failed, and execute it.

BMC396419E

BASE TABLE DOES NOT HAVE AUX OBJECTS SELECTED FOR MIGRATION.
AUX OBJECTS MUST BE INCLUDED WHEN USING STDRULES.
TBB: tableOwner.tableName

Explanation : You are migrating a table with one or more LOB columns and have included the STDRULES keyword in the ALUIN input stream. You specified AUX = N in the scope rules of the migration, which is not allowed with STDRULES. 

User response: Return to Specification and modify your scope rules to AUX = Y. Then run Analysis, and execute the worklist.

BMC396420W

CHANGE RULE(S) LOST ON AUX TS WITH STDRULES.

AUX TS/TB/IX: ownerName.objectName

Explanation : You are attempting to change an auxiliary object (table space, table, or index) by applying change rules. You have selected to use the STDRULES keyword in the ALUIN input stream. The STDRULES keyword prevents the implementation of changes to the auxiliary object.   

User response : No action is required. 

BMC396421E

USE OF REORGPENDONLY NOT ALLOWED FOR TS: databaseName.tableSpaceName REORG OF TS IS REQUIRED FOR DEFERRED ACTION ON IX: indexOwner.indexName


Explanation: You have entered the REORGPENDONLY keyword into the ALUIN input stream. The reorganization cannot remain pending, because the table space must be reorganized to perform an action on the specified index.

User response : Return to Specification and select Perform Reorg whenever Reorg is applicable (REORGALL). Then run Analysis, and execute the worklist.

BMC396422W

MIGRATE OF DATA USING NGT COPY EXPORT / NGT RECOVER IMPORT OF TB OBJECT WITH LOB COLUMN(S) AND USING  STDRULES. IMPORT PROCESSING MAY FAIL IF THE AUX TABLESPACE  IS DEFINE NO.  ENSURE THAT THE AUX TABLESPACE FOR THE LOB IS NOT IN  A DEFINE NO STATE.                                                         

   TB tableOwner.tableName

Explanation :You selected the NGT Copy EXPORT and NGT Recover IMPORT option to migrate data in a migrate-type work ID. However, the named table has one or more LOB columns and you have selected to use the STDRULES keyword, which might cause the migration to fail for the following reason: 

  1. The use of STDRULES could result in the auxiliary table space being defined as DEFINE NO on the target SSID.
  2. If the auxiliary table space exists in a DEFINE NO state, the NGT Recover IMPORT command might fail.            

User response : Before you execute the work ID, ensure that the auxiliary table spaces for the named table is not in a DEFINE NO state on the target SSID.       

BMC396423W

{VW viewOwner.viewName | TR triggerSchema.triggerName | TB tableOwner.tableName} HAS A SCHEMA CHANGE RULE FOR UNQUALIFIED USER DEFINED FUNCTION schema.functionName. CHECK CURRENT PATH TO ENSURE THAT THE SCHEMA FOR THE USER DEFINED FUNCTION IS CORRECT.

Explanation: You specified a change rule for the schema of an unqualified user-defined function. Analysis updated the schema in the CURRENT PATH statement.

User response: Review the CURRENT PATH statement for the view, trigger, or materialized query table.

BMC396424E

FORMAT OF UNLOADED BASELINE DATA REQUIRES NGT LOAD.

Explanation: The baseline data was unloaded in the format used by the NGT UNLOAD utility. The ALUIN selection of IBM LOAD or BMC LOAD is

not compatible with NGT UNLOAD.

User response: Do one of the following: Is this allowed? Two options?

  • Run analysis again and specify NGT LOAD.
  • Recover with the current data.
BMC396425W

{VW viewOwner.viewName | TR triggerSchema.triggerName | TB tableOwner.tableName} HAS A SCHEMA CHANGE RULE FOR UNQUALIFIED USER DEFINED FUNCTION schema.functionName. BECAUSE THE CHANGE RULE HAS A PART2 VALUE SPECIFIED, ANALYSIS DOES NOT CHANGE THE CURRENT PATH.

Explanation: You specified a change rule for Part 2 of the schema of an unqualified user-defined function. As a result, Analysis did not update the schema in the CURRENT PATH statement.

User response: Review the CURRENT PATH statement for the view, trigger, or materialized query table.

BMC396426W

{VW viewOwner.viewName | TR triggerSchema.triggerName | TB tableOwner.tableName} HAS A SCHEMA CHANGE RULE FOR UNQUALIFIED USER DEFINED FUNCTION schema.functionName. HOWEVER, THE CURRENT PATH WAS MODIFIED IN THE WORKID. THUS, THE SCHEMA IN THE CURRENT PATH WILL NOT BE UPDATED WITH THE CHANGE RULE.

Explanation: You specified a change rule for the schema of an unqualified user-defined function. However, you also modified the path for the named object. As a result, Analysis did not update the schema in the CURRENT PATH statement.

User response: Review the CURRENT PATH statement for the view, trigger, or materialized query table.

BMC396427E

TS databaseName.tableSpaceName PART partNumber HAS INVALID COMBINATION OF PCTFREE pctFreeValue and PCTFREE FOR UPDATE pctFreeForUpdateValue. SUM MUST BE LESS THAN 100.

Explanation: The sum of the values you entered for PCTFREE and PCTFREE FOR UPDATE exceeds the limit , which is 99.

User response: Modify the values entered for PCTFREE and PCTFREE FOR UPDATE so the sum of the values does not exceed 99.

BMC396428E

TS databaseName.tableSpaceName PART partNumber HAS A VALUE SPECIFIED FOR PCTFREE FOR UPDATE. IT IS NOT ALLOWED ON DB2 V10. UNDO CHANGE TO PCTFREE FOR UPDATE AND RERUN ANALYSIS.

Explanation: You specified values other than zero for the PCTFREE_UPD and NEW_PCTFREE_UPD columns in the CD_TABLEPART table that the application does not support on a DB2 Version 10 subsystem.

User response: Set the values for the PCTFREE_UPD and NEW_PCTFREE_UPD columns to zero and rerun analysis.

BMC396429E

TABLE tableOwner.tableName COLUMN columnName IS AN INVALID NON-DETERMINISTIC GENERATED EXPRESSION COLUMN. REASON: reason

Explanation: Analysis determined that the specified column is ineligible to be a NON-DETERMINISTIC GENERATED EXPRESSION column. Possible reasons are as follows:

  • VALUE value IS NOT VALID
  • VALUE IS MISSING
  • MORE THAN ONE COLUMN IS DEFINED AS DATA CHANGE OPERATION
  • {SESSiON VARIABLE | SPECIAL REGISTER} value COLUMN IS NOT NULL
  • DATA CHANGE OPERATION IS NOT NULL

User response: To correct the problem, perform one of the following actions and then rerun Analysis:

  • Remove the changes on the specified column.
  • Resolve the problem with the specified column name, as indicated by the specified reason.
BMC396430W

PROCESSING DFSMS-ENCRYPTED OBJECTS OR OBJECTS THAT WILL BE ENCRYPTED AS A RESULT OF PROCESSING REQUIRES THE IBM UTILITIES.

Explanation: Using utilities other than IBM utilities might not process encrypted objects successfully.

User response: Use IBM utilities to rerun the Analysis process.

BMC396431W

PROCESSING DFSMS-ENCRYPTED OBJECTS OR OBJECTS THAT WILL BE ENCRYPTED AS A RESULT OF PROCESSING MIGHT REQUIRE THE KEYLABEL PARAMETER IN -AMS WORKLIST COMMANDS.

Explanation: -AMS commands in worklists do not include KEYLABEL parameters for encrypted volume catalog (VCAT) defined objects.

User response: To correct the problem, perform one of the following actions:

  • Exclude the objects from the scope of the worklist and rerun Analysis.
  • In the worklist, add the appropriate KEYLABEL parameter to the relevant -AMS commands before executing the worklist.
BMC396433W

THE CURRENT FUNCTION LEVEL functionLevel IS GREATER THAN THE APPLCOMPAT applCompatLevel ON THE PRODUCT PACKAGES.  THE PRODUCT PACKAGES MUST BE BOUND WITH APPLCOMPAT EQUAL TO THE CURRENT FUNCTION LEVEL TO ENSURE FULL EXPLOITATION OF THE CURRENT FUNCTION LEVEL.

Explanation: The product packages are bound with an application compatibility level (applCompatLevel) that might not allow the product to fully exploit all functionality available at the current active function level (functionLevel).

User response: Rebind the product packages using an application compatibility (APPLCOMPAT) level that is the same as the current active function level (functionLevel).

BMC396434E

THE CURRENT FUNCTION LEVEL functionLevel IS GREATER THAN THE APPLCOMPAT applCompatLevel ON THE PRODUCT PACKAGES. APPLCOMPAT PROHIBITS USE OF FEATURE: KEYLABEL objectType OBJECT NAME objectName

Explanation: The product and the current function level support the specified feature. However, the product cannot exploit the specified feature because of the application compatibility level of the product packages.

User response: To correct the problem, perform one of the following actions and rerun Analysis:

  • Rebind the product packages using an application compatibility level equal to the current active function level.
  • Remove the specified feature from the scope.
BMC396435W

THE CURRENT FUNCTION LEVEL functionLevel IS GREATER THAN THE APPLCOMPAT applCompatLevel ON THE PRODUCT PACKAGES. APPLCOMPAT PROHIBITS USE OF FEATURE: KEYLABEL objectType OBJECT NAME objectName

Explanation: Even though the product supports the specified feature, the application compatibility level of the product packages does not permit the product to exploit the specified feature. Also, the current function level does not support the specified feature. The product ignores the specified feature.

User response: No action is required.

BMC396436E

USE OF KEYLABEL NOT ALLOWED ON objectType objectName. REASON: reason         

Explanation: IBM DB2 does not allow using the specified feature on the object for the reason shown. Possible reasons are as follows:

  • TS USES VCAT
  • IX USES VCAT
  • AUX TS USES VCAT
  • AUX IX USES VCAT
  • AUXILIARY TABLE
  • CLONE TABLE
  • GLOBAL TEMPORARY TABLE
  • ACCELERATOR-ONLY TABLE

User response: Remove the specified changes on the specified object and rerun Analysis.

BMC396437E

TB DQJBNRB1.T_T02SSEG - LENGTH ERROR IN DYNAMIC UNLOAD DATASET NAME
DATASET datasetName

Explanation: The name of the data set for the dynamically allocated discard data set resolved to a length of 0 or more than 44 bytes. ALTER or CHANGE MANAGER appends a period, two-character abbreviation, and six-digit number (in the format: .SDnnnnnn) to the prefix, to create the name of the data set. If all of the following conditions are true, ALTER or CHANGE MANAGER also appends the Ppart variable to the prefix (.SDnnnnnn.Ppart) to create the name of the data set:

  • You are using the NGT UNLOAD and NGT LOAD utilities to dynamically allocate the data set.
  • You are using a partitioned table space.
  • DISCARDS is set to a value other than 1.
  • You are multitasking unloading and loading data.

The data set name that you specify in the JCL Generation override panels must allow for the additional bytes.

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

BMC396438E

RC = 12 RESOLVING LOAD DYNAMIC COPY DATASET NAME
PREFIX:
prefix.XXXX.spname.Ppart What is XXXX?

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

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

BMC396439E

DB.TB DQJBNRB1.T_T02SSEG - LENGTH ERROR IN LOAD DYNAMIC COPY DATASET NAME.
DATASET datasetName

Explanation: The name of the data set for the dynamically allocated copy 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 .LP123456) 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 copy data set in the JCL Generation override panels.

BMC396440E

RC = 12 RESOLVING LOAD DYNAMIC DISCARD DATASET NAME
PREFIX:
prefix.wkid.XXXXXX XXXXXX?

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

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

BMC396441E

DB.TS DQJBNRB1.T_T02SSEG - LENGTH ERROR IN LOAD DYNAMIC DISCARD DATASET NAME
DATASET datasetName

Explanation: The name of the data set for the dynamically allocated discard data set resolved to a length of 0 or more than 44 bytes. ALTER or CHANGE MANAGER appends a period, two-character abbreviation, and six-digit number (in the format:.SDnnnnnn) to the prefix, to create the name of the data set. If all of the following conditions are true, ALTER or CHANGE MANAGER also appends the Ppart variable to the prefix (.SDnnnnnn.Ppart) to create the name of the data set:

  • You are using the NGT UNLOAD and NGT LOAD utilities to dynamically allocate the data set.
  • You are using a partitioned table space.
  • DISCARDS is set to a value other than 1.
  • You are multitasking unloading and loading data.

The data set name that you specify in the JCL Generation override panels must allow for the additional bytes.

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

BMC396442E

BLNAME AND BLWORKID KEYWORDS ARE MUTUALLY EXCLUSIVE.

Explanation:   The ALUIN input stream contained both the BLNAME (baseline name) and BLWORKID (alter-type work ID that established the baseline) keywords. However, you can specify only one of the keywords in a single input stream.

User response: Remove one of the keywords from the ALUIN input stream.

BMC396443E

BASELINE FOR BLWORKID  workIDOwner.workIDName NOT FOUND.

Explanation:   Analysis could not find the baseline that the BLWORKID keyword references. BLWORKID specifies the alter-type work ID that established the baseline.

User response: Ensure that the work ID for the baseline is correct.

BMC396444I

USING BASELINE baselineOwner.baselineName  FROM BLWORKID workIDOwner.workIDName.

Explanation: Analysis is using the baseline referenced in the alter-type work ID that established the baseline (BLWORKID).

User response:   No action is required.

BMC396446E

USING NGT UNLOAD AND NGT LOAD IS NOT SUPPORTED FOR OBJECT(S):

Explanation: NGT UNLOAD and NGT LOAD are not allowed for this object.

The Reason can be one of the following: Do these reasons appear as part of the message? If so, why is there no indication of where in the message here? If not, why are they in all caps?

  • REASON: TB HAS LOB OR XML COLUMNS
  • REASON: TB HAS ROWID COLUMN
  • REASON: TB HAS BINARY OR VARBINARY COLUMNS
  • REASON: TB HAS TB CHECK CONSTRAINT
  • REASON: TS DSSIZE GREATER THAN 64G
  • REASON: TB HAS A CLONE
  • REASON: TB IS A CLONE
  • REASON: DB2 V10 NOT ALLOWED
  • REASON: TB HAS AN INDEX ON EXPRESSION
  • REASON: OVERRIDE(SYSTEMPERIOD,TRANSID) NOT SUPPORTED FOR TB
  • REASON: OVERRIDE(NONDETERMINISTIC) NOT SUPPORTED FOR TB
  • REASON: TB HAS ROW CHANGE TIMESTAMP COLUMN

User response: In the Analysis overrides, specify a supported combination of IBM or BMC unload and load utilities.

BMC396447W

UTILCOPY NOT SUPPORTED FOR NGT LOAD

Explanation: UTILCOPY was specified when using NGT LOAD. This feature is currently not allowed in the worklist environment. A standalone copy is generated into the worklist.

User response: No action is required.

BMC396454E

BASICUNLOAD IS NOT ALLOWED WHEN USING NGT LOAD

Explanation: You selected the BASICUNLOAD utility to unload data, and the NGT LOAD utility to load data. If you use the NGT LOAD utility, you must also use the NGT UNLOAD utility. User response: Return to the utility options panel and select the correct utilities.


Explanation:

NGT Unload and NGT Load are not allowed for this object.

Reason represents one of the following explanations:


REASON: TB HAS LOB OR XML COLUMNS                

REASON: TB HAS ROWID COLUMN      

REASON: TB HAS BINARY OR VARBINARY COLUMNS

REASON: TB HAS TB CHECK CONSTRAINT   

REASON: TS DSSIZE GREATER THAN 64G   

REASON: TB HAS A CLONE

REASON: TB IS A CLONE

REASON: DB2 V10 NOT ALLOWED  

REASON: TB HAS AN INDEX ON EXPRESSION

REASON:  OVERRIDE(SYSTEMPERIOD,TRANSID) NOT SUPPORTED FOR TB

REASON: OVERRIDE(NONDETERMINISTIC) NOT SUPPORTED FOR TB  

REASON: TB HAS ROW CHANGE TIMESTAMP COLUMN 

               

 User response:

In the Analysis overrides, specify to use a supported combination of IBM or BMC unload and load utilities.


Was this page helpful? Yes No Submitting... Thank you

Comments