Messages BMC70500 through BMC70599

BASELINE baselineOwner.baselineName NOT CATALOG TYPE

Explanation: BLRECOVERPOINT and BLRECOVER can work only with catalog-type baselines. The baseline referenced is a data definition language (DDL)-type.

User response: Specify the correct baseline name.

SG storageGroupName REFERRED TO BY DB databaseName

Explanation: You attempted to change the name of a storage group, but the specified database refers to the storage group as its default. This product does not automatically drop and rebuild databases to rename the storage group.

User response: If the name change is required, return to Specification, generate a mixed list of all databases that use this storage group, and change the storage group name for each database.

OPTION FOR COPY ON BMCLOAD USED WITH DEVICE TYPE OF WORK

Explanation: The same device type will be used for BMCLOAD work data sets as for the output of the COPY function. If the device type of WORK generates temporary data sets, the COPY may be lost before needed. This message applies only to BMC Software LOADPLUS utility jobs.

User response: Either change the device type and rerun Analysis or edit the BMCLOAD commands in the worklist.

THE RESULTING VALUE value FROM RULE rule IS TOO LARGE

Explanation: When the product applied the specified change rule, the resulting value for the attribute exceeded the allowable length for the value. For example, you specified a rule that changed the name of a database. The new name of the database exceeded eight characters.

User response: Correct the change rule.

RULES EXCLUDED ALL {COLUMNS | VOLS} FOR objectType objectName

Explanation: Application of exclude-type change rules left no columns remaining in the table or view, or no volumes in the storage group.

User response: Correct the change rules.

RULES EXCLUDED ALL {COLUMNS | COLS} FOR objectType objectName

Explanation: Application of exclude-type change rules left no columns remaining in the index, foreign key, or unique constraint. The object is changed to DROP and is not included in the resulting worklist.

User response: Return to Specification, examine the change rules, and verify that this result is acceptable. Alternatively, correct the change rules or undo the migration of the object.

IX indexOwner.indexName IS PARTITIONED BUT NOT CLUSTER

Explanation: Partitioned indexes must be clustering indexes.

User response: Return to Specification and correct the error.

VW viewOwner.viewName HAS COLS-IN-TEXT BUT NOT COLUMNS

Explanation: You attempted to import a view that has no column list but which has the COLS-IN-TEXT flag set to YES.

User response: Return to Specification and enter the column list that you want for this view.

TABLE tableOwner.tableName HAS PRIKEY LEN GREATER THAN MAX ALLOWED

Explanation: The table has a primary key that is greater than the maximum allowed.

User response: Correct the primary key definition.

COL ATTRIBUTES PROPAGATED TO TB tableOwner.tableName

Explanation: The column attributes have been propagated to the table by primary key propagation. The table will be rebuilt and the data converted if necessary.

User response: No action is required.

PARM MISSING IN ALUIN FOR GLAUTHID

Explanation: The GLAUTHID parameter value in the input stream is missing.

User response: Supply the GLAUTHID parameter value.

NO PARMS FOR keyword KEYWORD

Explanation: No parameters were specified for the INCLUDE, REGISTER, COPYDDN, or SMSINCLUDE keyword.

• The keywords permitted for INCLUDE are (SQL AMS DATA REBIND) for alter-type work IDs, and (SQL AMS DATA BIND) for migrate-type work IDs.

• The keywords REGISTER and COPYDDN must be followed by a list of ddnames in parentheses.

• The keywords permitted for SMSINCLUDE are (DATACLAS MGMTCLAS STORCLAS).

User response: Specify the necessary parameters.

NO CORRESPONDING PLAN FOUND FOR PACKAGE location.collectionID.packageName

Explanation: The named package was not found in any plan. This message is a warning only. No plan will be bound containing this package.

User response: No action is required.

PARSER: PCTFREE FOR UPDATE VALUE OUT OF RANGE AT LINE lineNumber

Explanation: The PCTFREE FOR UPDATE value must be between -1 and 99, inclusive. The line number identifies the command sequence number in a Change Definition Language (CDL) or worklist data set or the line number in a data definition language (DDL) data set where the error occurs. This error should not occur in a CDL or worklist data set generated by CHANGE MANAGER.

User response: If the data set was edited or generated externally to CHANGE MANAGER, correct the error and rerun the job. If the data set was generated by CHANGE MANAGER and not edited, contact BMC Customer Support.

NO DDN SPECIFIED FOR COPY01

Explanation: You must supply a ddname for use by the COPY utility.

User response: Correct the input.

COPY DDN RECV02 SPECIFIED BUT NO RECV01

Explanation: You cannot specify RECV02 without specifying RECV01.

User response: Correct the input.

REGISTER DDN WITH NO CORRESPONDING COPYDDN

Explanation: You cannot specify remote copies (RECV) without specifying at least one local copy (COPYDDN).

User response: Correct the input.

UNIQUE CONSTRAINT FOR IX indexOwner.indexName LOST

Explanation: The table referenced by this index was created by using the UNIQUE clause. This index satisfies all of the criteria of uniqueness. The table will be re-created without the UNIQUE clause. Uniqueness will be satisfied by the creation of the unique index.

User response: If you want the CREATE TABLE statement to include the UNIQUE clause, change the worklist by specifying the clause for the affected table.

TB tableOwner.tableName COL column CANNOT USE MIXED DATA

Explanation: You have requested that a table column use MIXED data when your system cannot support MIXED data.

User response: Use Specification to modify the work ID entries so that the data subtype value of the column is one that is allowed by your system. Then, rerun Analysis.

objectType objectName ROSHARE NOT SAME AS MIGRO

Explanation: The MIGRO (Migrate Roshare) option differs between the named object and its parent object, or between the work ID Migrate Roshare option and the database.

User response: Use Specification to ensure that the Migrate Roshare flag is specified properly for all read-only objects and dependents. Then, rerun Analysis.

objectTypeobjectOwner.objectName UNEXPECTED END OF TEXT

Explanation: The text for the view, trigger, check constraint, materialized query table (MQT), or index ended when more data was required or the last token was unrecognized.

User response: Correct the text by using Specification to examine and modify the object.

objectTypeobjectOwner.objectName HAS DUP CORRELATION, NO NAME PROPAGATION

Explanation: The specified view, trigger, check constraint, materialized query table (MQT), or index has at least two identical correlation names. The product will not perform name propagation for this object.

User response: If you need name propagation, manually edit the worklist or edit the object to remove the duplicate correlations. Then, rerun Analysis.

VW viewOwner.viewName HAS NO SELECT KEYWORD

Explanation: The VIEW does not have a SELECT statement.

User response: Correct the VIEW.

objectTypeobjectOwner.objectName {SYNTAX | UNKNOWN} ERROR AT token. {RETCODE: code}

Explanation: A text validation error was found at the presented token but might have occurred earlier. This error can occur during a catalog-to-catalog comparison if the product accesses a remote catalog. As documented in the IBM documentation, vertical bars (||) and the not sign (^) can cause parsing errors in statements that pass from one DBMS to another with certain source and target CCSIDs.

User response: Examine the object and modify it before trying again. If this error is due to dissimilar CCSIDs across DBMSs, change the text to use CONCAT instead of vertical bars, and use <> in place of the not sign. For more information, see the IBM documentation.

VW viewOwner.viewName INVALID NAME TOKEN name

Explanation: The view contains an invalid name.

User response: Correct the name.

WORKLIST HAS NON-STANDARD COMMAND SET

Explanation: Analysis override options have been modified by the user to something other than the defaults. The defaults are SQL, DATA, and AMS for a migrate-type work ID or SQL, DATA, AMS, and REBINDS for an alter-type work ID. Anything else specified is considered nonstandard and results in this warning message.

User response: No action is required.

REGISTER FOR {COPY02 | RECV02} BUT NOT {COPY01 | RECV01}

Explanation: You cannot register the second local or remote copy without registering the primary copy first.

User response: Correct the input.

VW viewOwner.viewName INVALID FROM LIST token

Explanation: The FROM clause of the SELECT statement in the view text is invalid.

User response: Correct the input.

VW viewOwner.viewName SELECT LIST TB NOT FOUND token

Explanation: The table is not in the view SELECT list.

User response: Correct the input.

VW viewOwner.viewName IS INCOMPLETE

Explanation: The view is missing one or more required clauses.

User response: Correct the input.

VW viewOwner.viewName HAS BAD WITH CHECK CLAUSE

Explanation: The WITH CHECK DATA clause of the view statement is invalid.

User response: Correct the input.

VW viewOwner.viewName HAS COLUMN NO TB MATCH token

Explanation: The view has a column with no matching table.

User response: Correct the input.

objectType objectName USES DROPPED TB tableOwner.tableName

Explanation: The object references a table that is being dropped in this worklist. The following table lists the possible object types:

User response: Return to Specification, correct the input, and rerun Analysis. If you imported a Change Definition Language (CDL) or data definition language (DDL) file, ensure that the CDL or DDL is correct.

objectType objectName USES TB tableOwner.tableName NOT FOUND

Explanation: The Analysis component cannot find a table that the object references. The following table lists the possible object types:

User response: Return to Specification and correct the object. Then, rerun Analysis.

objectType objectName USES ITSELF

Explanation: The object references itself. The following table lists the possible object types:

User response: Return to Specification and correct the object. Then, rerun Analysis.

objectType objectName HAS attribute name MATCHING RULE.

RULE NOT APPLIED BECAUSE {VW | TR} TEXT HAS CHANGED.

Explanation: A rule was found that matches the object, but the rule will not be applied because you modified the view or trigger.

User response: If necessary, correct the view or trigger.

objectType objectName HAS COLUMN column NOT FOUND

Explanation: The product could not find the column that you used in the object on an expression. The following table lists the possible object types:

User response: Return to Specification and correct the object. Then, rerun Analysis.

objectType objectName COL column NOT IN ANY TB

Explanation: The column referenced by the object was not found in a table referenced by the object. The following table lists the possible object types:

User response: Return to Specification and correct the object. Then, rerun Analysis.

objectType objectName COL column IN MULTIPLE TB

Explanation: The column referenced by the object appears in multiple tables. The following table lists the possible object types:

User response: Return to Specification and correct the object. Then, rerun Analysis.

objectType objectName COL column WRONG DATATYPE

Explanation: The column is an invalid data type for the attempted operation. The following table lists the possible object types:

User response: Return to Specification and correct the object. Then, rerun Analysis.

VW viewOwner.viewName USES SELECT * WRONG

Explanation: The view uses a SELECT * statement, which is invalid.

User response: Correct the input.

MEMORY ERROR x PARSING {MQT | IX | VT | TR} objectOwner.objectName

Explanation: An internal error occurred while the product was parsing the object.

User response: Contact BMC Customer Support.

objectType objectName USES EXCLUDED COLUMN column

Explanation: The view or trigger references a column that is excluded by a change rule.

User response: Correct the input.

VW viewOwner.viewName REQUIRES NAMED COLUMN LIST

Explanation: The view requires a named column list. The view cannot work with an implicit column list (SELECT *).

User response: Correct the input.

VW viewOwner.viewName DUPLICATE COLNAME column

Explanation: The column name appears more than once in the view text.

User response: Correct the input.

VW viewOwner.viewName COLNAME MISMATCH TO COLLIST

Explanation: The column name does not match the column name list.

User response: Correct the input.

VW viewOwner.viewName COUNT MISMATCH TO COLLIST

Explanation: The number of columns does not match the number of columns in the views column list. The problem can result if the following conditions exist:

• The view is a SELECT * view.

• The table has hidden columns.

User response: Correct the input.

objectTypeobjectOwner.objectName INVALID LITERAL

Explanation: The parser encountered an invalid literal in the text of the specified object.

User response: Return to Specification, correct the text, and rerun Analysis.

VW viewOwner.viewName INVALID LITERAL token

Explanation: The view parser encountered an invalid literal in the text of the named view.

User response: Return to Specification to correct the view text and rerun analysis.

VW viewOwner.viewName HAS CHANGE TO TEXT

Explanation: Analysis has changed the view’s text.

User response: No action is required.

CLUSTERING INDEX indexOwner.indexName CANNOT BE REBUILT DUE TO TABLE COLUMN CHANGES

Explanation: The required clustering index cannot be rebuilt due to table column changes that have been made to the referenced table.

User response: Change the column key references in the current clustering index, create a new clustering index with different column key references, or undo the table column changes that caused the error. Then, run Analysis again.

CALCULATED {PRIQTY | SECQTY} EXCEEDS MAX FOR TS databaseName.tableSpaceName WHEN FOLLOWING RULE IS APPLIED:

CHANGE object {PRIQTY | SECQTY} oldValue newValueWHEN LIKE part1 part2

Explanation: A table space rule application caused the value of PRIQTY or SECQTY to exceed the allowable maximum. The old and new values specified in the rule are shown in the message. part1 (database name) and part2 (table space name) represent the first name qualifiers specified in the rule.

User response: Correct the table space rule and run Analysis again.

CALCULATED {PRIQTY | SECQTY} EXCEEDS MAX FOR IX indexOwner.indexName WHEN FOLLOWING RULE IS APPLIED:

CHANGE object {PRIQTY | SECQTY} oldValue newValue WHEN LIKE part1 part2

Explanation: An index rule application caused the value of PRIQTY or SECQTY to exceed the allowable maximum. The old and new values specified in the rule are shown in the message. part1 (index owner) and part2 (index name) represent the first name qualifiers specified in the rule.

User response: Correct the index rule and run Analysis again.

CALCULATED ASUTIME EXCEEDS MAX FOR SP schema.storedProcedureNameWHEN FOLLOWING RULE IS APPLIED:

CHANGE ASUTIME oldValue newValueWHEN LIKE part1 part2

Explanation: A stored procedure rule application caused the value of ASUTIME to exceed the allowable maximum. The old and new values specified in the rule are shown in the message. part1 and part2 represent the first name qualifiers specified in the rule.

User response: Correct the stored procedure rule and run Analysis again.

objectType objectName CANNOT QUALIFY TB tableOwner.tableName

Explanation: For an unqualified object that references an unqualified table, the owner names are different. The object is not created. The following table lists the possible object types:

User response: Correct the object and run Analysis again.

USING IBM LOAD FOR DATA RECOVERY.BASELINE DATA WAS UNLOADED USING IBM LOAD FORMATS

Explanation: Because the full-recovery baseline was created using IBM UNLOAD, Analysis must use IBM LOAD for data recovery.

User response: No action is required.

FORMAT OF UNLOADED BASELINE DATA REQUIRES BMC LOAD

Explanation: The Baseline data was unloaded in the format used by a BMC Software load utility. The ALUIN selection of IBM LOAD is not compatible.

User response: If you have the BMC Software LOADPLUS product installed, run Analysis again and specify BMCLOAD. Otherwise, recover with the current data.

PROFILE SCOPE TIMESTAMP NOT EQUAL TO BASELINE TIMESTAMP. SCOPE MAY HAVE CHANGED

Explanation: The scope changed since the selected baseline was taken.

User response: No action is required. However, you may want to investigate how the scope changed in order to avoid unwanted object additions, deletions, or modifications.

SG storageGroupName CONTAINS * VOLID WITH MORE THAN ONE VOLID AFTER RULE APPLICATION

Explanation: The storage group contains more than one volume ID, of which one is named ‘*’.

User response: Correct the rule and run Analysis again.

INVALID TEMPLATE FOR WORKID NAME

Explanation: The template specified for the work ID is invalid.

User response: Correct the template.

VIEW viewOwner.viewName HAS UNKNOWN SQLID

Explanation: The view parser is unable to determine the SQLID that is required to create the view. A SETS UNKNOWN statement was generated in the worklist.

User response: Specify the correct SQLID in the SETS statement and execute the worklist.

UNLOAD OPTION CHANGED TO BMC UNLOAD. BASELINE DATA IS UNLOADED WITH BMC LOAD FORMATS BY BMC UNLOAD.

Explanation: Because the Baseline data was unloaded by the BMC Software UNLOAD PLUS utility, the UNLOAD utility selection is changed to specify UNLOAD PLUS.

User response: No action is required.

VW viewOwner.viewName PARENS MISMATCH ON OUTER SELECT

Explanation: The outermost SELECT statement has a closing parenthesis. However, the number of closing parentheses does not match the number of opening parentheses. This DB2 view syntax is not documented.

User response: Delete the outermost parenthesis to avoid future problems.

WARNING - WORKLIST COMMAND(S) CONTAIN NAME TRUNCATION. FIND @

Explanation: This message appears in the worklist when the result of externalizing a DB2 name causes the name to be truncated. This truncation only happens if you embed quotes in a delimited name and the name cannot be represented in 20 bytes or less. This condition is not detected until the worklist is created. This message appears in the worklist before every statement that contains truncation.

User response: Search for the @ symbol to find the truncated data. Fix the truncated name.