Messages NGTP000 through NGTP999
Number | Description |
---|---|
NGTP004 | THE TABLESPACE MUST HAVE MORE THAN 1 PARTITION DEFINED. Explanation: REPART functions only on partitioned table spaces, and only if there is more than one partition defined. User response: Correct the input statement to name a table in a partitioned table space with more than one partition. Resubmit the job. |
NGTP005 | ARCHIVE STARTING FOR PARTITION 1. Explanation: ARCHIVE has been requested for the data from the first partition of the table space. User response: No action is required. |
NGTP006 | ARCHIVE COMPLETED FOR PARTITION 1, number-1 ROWS WRITTEN. Explanation: ARCHIVE has been requested for the data from the first partition of the table space. It is completed User response: No action is required. |
NGTP007 | FAILURE DURING ARCHIVE OF PARTITION 1. Explanation: Some failure occurred during the ARCHIVE of the data from the first partition of the table space. User response: Check system messages for error indications. If no message can be found, contact BMC Support. |
NGTP008 | NAMED EXIT CANNOT BE FOUND. Explanation: The exit named in the REPART statement USING clause could not be found or the REXX initialization failed for this exit. User response: Check the library specified in the CDBEXEC or NGTAUTO DD card. If the member exits, check for system messages. If no apparent reason can be found, contact BMC Support. |
NGTP009 | ONLY THE SAMPLE DATABASE CAN BE DONE DURING TRIAL. Explanation: During the trial period, only table spaces from the Db2 sample database can be processed. User response: Contact BMC Support. |
NGTP010 | UPDATE FAILURE - DBD NOT IN. Explanation: A failure occurred accessing the DBD for the database that owns the modified table space. This message will be followed by an abend. User response: This may be caused by a temporary state within Db2. Rerun the job with the 'RESTART' parameter. If the failure persists, contact BMC Support. |
NGTP011 | DISPLAY FAILURE Explanation: A failure occurred issuing the -DISPLAY command for the database that owns the modified table space. This message will be followed by an abend. User response: This may be caused by a temporary state within Db2. Rerun the job with the 'RESTART' parameter. If the failure persists, contact BMC Support. |
NGTP012 | BEGINNING LIMITKEY UPDATE. Explanation: This message marks the start of the Partitions Limitkey Update function of REPART. User response: No action is required. |
NGTP013 | LIMITKEY UPDATE COMPLETED. Explanation: This message marks the successful end of the Partitions Limitkey Update function of REPART. User response: No action is required. |
NGTP014 | RETRY IN PROGRESS AFTER -911. Explanation: This message indicates that a -911 SQL error has occurred. The process will be repeated up to 5 times. User response: No action is required. |
NGTP017 | LIMITKEY UPDATE FAILED (code) Explanation: REPART was unable to update the database DBD or Db2 catalog with new limit keys. The indicated code describes the reason as follows:
User response: Run the job using the RESTART parameter. REPART will retry the limit key update. If the problem persists, contact BMC Support. |
NGTP018 | REPART REQUIRES A DEFINED CLUSTERING INDEX. Explanation: No clustering index is defined on the table in the table space named in the REPART statement. The table must have a defined clustering index for REPART processing. User response: A clustering index will need to be defined for this table in order to run REPART. |
NGTP019 | MULTI-TABLE TABLESPACES NOT ELIGIBLE FOR REPART. Explanation: The table space named in the REPART statement contains more than one table. REPART can only process table spaces with one table. User response: Each table that is to be processed will have to be migrated to a new table space with only the one table. |
NGTP020 | REPART STARTING FOR tableSpaceName Explanation: This message signals the start of REPART processing and names the table space being processed. User response: No action is required. |
NGTP021 | PART number-1 number-2 TS PAGES, number-3 IX PAGES Explanation: This message is part of a space analysis report printed as part of REPART initialization. One line is printed per partition showing the number of used pages in the table space and partitioning index. User response: No action is required. |
NGTP022 | TOTALS number-1 TS PAGES, number-2 IX PAGES Explanation: This message is part of a space analysis report printed as part of REPART initialization. This line is a total of all partitions and shows the number of used pages in the table space and partitioning index. User response: No action is required. |
NGTP023 | THE DD STATEMENT FOR A UNLOAD DATA SET (string-1) IS NOT IN THE JCL. Explanation: The TSDDN or IXDDN keyword named a DDname for unloading table space or clustering index information. A DD statement must be provided with this DDname. User response: Correct the input REPART statement or add the correct DD statement to the JCL. The data set can be on tape or DASD. |
NGTP024 | UNLOAD/RELOAD CONTROLLER TASK STARTING. Explanation: The Unload/Reload controller task manages the process of unloading all rows from the existing table space and reloading them into the 'new' table space and index. User response: No action is required. |
NGTP025 | INDEX LOADER TASK STARTING Explanation: The index loader is the task that reads the file of index keys and writes the new partitioning indexes. User response: No action is required. |
NGTP026 | INDEX LOADER TASK ENDING Explanation: The index loader is the task that reads the file of index keys and writes the new partitioning indexes. User response: No action is required. |
NGTP027 | INDEX LOADER INIT COMPLETE, PROCESSING number-1 KEYS. Explanation: The index loader is the task that reads the file of index keys and writes the new partitioning indexes. Number-1 is the total number of keys from all partitions. User response: No action is required. |
NGTP028 | INDEX LOADER RESTARTING. number-1 OF number-2 PARTITIONS PREVIOUSLY COMPLETED. Explanation: The index loader is the task that reads the file of index keys and writes the new partitioning indexes. This is a restart and completed partitions need not be rebuilt. User response: No action is required. |
NGTP029 | INDEX WORKFILE TASK STARTING. Explanation: The index work file task builds the file of partitioning index keys. User response: No action is required. |
NGTP030 | number-1 KEYS RECEIVED. Explanation: The index work file task builds the file of partitioning index keys. This message displays the count of keys processed. User response: No action is required. |
NGTP031 | INDEX WORKFILE TASK ENDING. Explanation: The index work file task builds the file of partitioning index keys. User response: No action is required. |
NGTP032 | TASK STATISTICS: EVENTS=number-1 RWE=number-2 TWE=number-3. Explanation: This message displays internal task control counts during the clustering analysis phase. User response: No action is required. |
NGTP033 | TASK(string-1) STARTED FOR INDEX PART(number-1). Explanation: String-1 is the task identifier assigned to the clustering index read task started for partition number number-1. User response: No action is required. |
NGTP034 | TASK(string-1) ENDED CODE(hexstring-1) FOR INDEX PART(number-1). Explanation: String-1 is the task identifier assigned to the clustering index read task that is ending. X'Hexstring-1' is the task completion code. User response: No action is required if the completion code is 0. If not, check for prior messages indicating the cause of the error. If the cause is not apparent, contact BMC Support. |
NGTP035 | INDEX READ COMPLETE PART(number-1). Explanation: This message marks the end of a single partitioning index read. User response: No action is required. |
NGTP036 | INDEX KEYS ARE UNSUITABLE FOR PARTITIONING. Explanation: New partition counts were supplied by an Exit, but these counts total to more rows than exist in the table space. User response: Modify the exit so the counts total to the passed value. |
NGTP037 | ALL KEYS USED BEFORE HIT LAST PARTITION. Explanation: New partition limit keys were supplied by an Exit, but using these keys leaves empty partitions. User response: Modify the exit so there are some rows in every partition. |
NGTP038 | LIMITKEYS NOT ASCENDING, PART number-1 . Explanation: New partition limit keys were supplied by an Exit, but these keys are not in the proper sequence. They must be ascending. Number-1 is the partition number out of sequence. User response: Modify the exit so the keys are in ascending sequence. |
NGTP039 | NO PARTITION MAY HAVE ZERO KEYS. CHECK PART number-1 Explanation: New partition counts were supplied by an Exit, but at least one partition has 0 rows. All partitions must have some rows so the limit keys can be determined. User response: Modify the exit so there are no non-zero counts. |
NGTP040 | TOTAL NEW ROWS (numberOfRows1) DOES NOT MATCH INPUT (numberOfRows2). Explanation: New partition counts were supplied by an Exit, but the total exceeded the number of rows in the table space. Number-1 is the accumulated count and number-2 is the expected total value. User response: Modify the exit so the total number of rows equals the passed value. |
NGTP041 | TOTAL NEW ROWS LEAVES EMPTY PART number-1. Explanation: New partition counts were supplied by an Exit, but the counts leave empty partitions. Number-1 is the first empty partition. User response: Modify the exit so there are some rows in every partition. |
NGTP042 | TABLESPACE LOADING TERMINATED, REASON=(INVALID COUNTS). Explanation: The process of reloading the 'new' table space image from the workfile has failed due to a count mismatch between the actual number of records written to the file and the number of records read from it. User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. Contact BMC Support. |
NGTP043 | TABLESPACE LOADER TASK STARTING. Explanation: The table space loader is the task that reads the file of rebuilt pages and writes the new partitions. User response: No action is required. |
NGTP044 | TABLESPACE LOADER TASK ENDING. Explanation: The table space loader is the task that reads the file of rebuilt pages and writes the new partitions. User response: No action is required. |
NGTP045 | TABLESPACE LOADER INIT COMPLETE. Explanation: The table space loader is the task that reads the file of rebuilt pages and writes the new partitions. User response: No action is required. |
NGTP046 | TABLESPACE LOADER RESTARTING. number-1 OF number-2 PARTITIONS PREVIOUSLY COMPLETED. Explanation: The table space loader is the task that reads the file of rebuilt pages and writes the new partitions. This is a restart and completed partitions need not be rebuilt. User response: No action is required. |
NGTP047 | TABLESPACE WORKFILE TASK STARTING. Explanation: The table space work file task builds the file of rebuilt table space pages with new limit key boundaries. User response: No action is required. |
NGTP048 | number-1 TOTAL ROWS RECEIVED Explanation: The tablespace workfile task builds the file of rebuilt tablespace pages with new limit key boundaries. This message displays the count of total rows processed for all partitions. User response: No action is required. |
NGTP049 | TABLESPACE WORKFILE TASK ENDING. Explanation: The tablespace workfile task builds the file of rebuilt tablespace pages with new limit key boundaries. User response: No action is required. |
NGTP050 | NEW PARTITION number-1 COMPLETED WITH number-2 ROWS. Explanation: The tablespace workfile task builds the file of rebuilt tablespace pages with new limit key boundaries. This is a status message showing the number of rows written to the 'new' partition. User response: No action is required. |
NGTP051 | PART CHANGE RID hexstring-1. Explanation: This is a tracing message written by the index writer task that is reading the index workfile. X' Hexstring-1 'is the Rid that triggered the partition change. User response: No action is required. |
NGTP052 | REPART RESTART STATUS: Explanation: This message starts a series of messages that describe the previous REPART run, showing which phases had completed. User response: No action is required. |
NGTP053 | LIMITKEYS UNCHANGED - RUN TERMINATES Explanation: The new limit keys are exactly the same as the currently defined values. REPART will terminate because nothing will be accomplished by this run. User response: Use the Limitkeys exit to define new values for the limit key or use the Counts exit to define new rows-per-partition values. |
NGTP054 | INDEX WORK DATASET DELETED - RUN STARTS OVER Explanation: At least one of the index work data sets built by a prior run during the clustering index read phase has been deleted. The run will restart from the beginning. User response: No action is required. |
NGTP055 | UNLOAD FILE string-1 CANNOT BE USED. string-2 DATASET IS UNACCEPTABLE. Explanation: Certain types of data sets cannot be used for the unload files. String-1 is the DDname of the data set in error. String-2 is the unacceptable characteristic. User response: Reference a sequential data set for this unload file. Correct the JCL and resubmit. |
NGTP056 | RUNSTATS FILE CANNOT BE FOUND. RUNSTATS TURNED OFF. Explanation: The Runstats restart file allocation failed. Runstats is turned off for this run. All other processing continues. User response: No action is required. |
NGTP057 | ERROR number-1 ON RUNSTATS FILE. RUNSTATS TURNED OFF. Explanation: An error occurred reading or writing the Runstats restart file. Runstats is turned off for this run. All other processing continues. User response: Check the system messages for any indication of open error or I/O error. If none, contact BMC Support. |
NGTP058 | PARTITION number-1 EXCEEDS DB2 LIMIT. RUN ABORTED. Explanation: During the table unload phase, REPART has determined that a partition exceeds the Db2 limit for physical size based on the number of parts. User response: Use different limit key values to adjust the physical size, or specify different Counts to alter the selected limit keys. Consider specifying USING SIZE to control the max size per partition. |
NGTP059 | SPECIFIED SIZE LEAVES EMPTY PARTITIONS AT THE END. Explanation: 'USING SIZE n' was specified on the REPART statement. Using that size value, all data was written before the penultimate partition was accessed. All partitions except the last must have data with 'USING SIZE'. User response: Use a different (smaller) size value. The run must be restarted. |
NGTP060 | REXX INTERFACE IS NOT ACTIVE. VERIFY //NGTAUTO DD Explanation: REXX Exits could not be processed. One common cause of this is that the CDBEXEC or NGTAUTO DD statement is not provided in the JCL. The CDBEXEC or NGTAUTO DD names the library containing the REXX exits. User response: If the CDBEXEC or NGTAUTO DD is specified and is referencing a PDS, then contact BMC Support. |
NGTP061 | PROCESSING INTERRUPTED BECAUSE 'UNLOAD PAUSE' Explanation: UNLOAD PAUSE was specified in the REPART control statement. All data has been unload. An abend 4095 will accompany this message. User response: Restart the job to continue REPART processing. |
NGTP062 | REPART CANNOT PROCESS A TABLESPACE WITH NO PARTITIONING INDEX. Explanation: The table to be processed by REPART has no partitioning index. At this time, REPART requires that a partitioning index be exist. User response: Define a partitioning index and rerun REPART |
NGTP063 | LOADING PARTITION number-1 WITH number-2 ROWS. Explanation: The tablespace loader is the task that reads the file of rebuilt pages and writes the new partitions. This message signals start of I/O processing for the named partition. The expected number of rows is shown in the message. User response: No action is required. |
NGTP064 | ONE OR MORE OF THE PHYSICAL DB2 DATASETS IS MISSING Explanation: One or more the physical Db2 data sets (the VSAM clusters) is missing. An IDCAMS LISTC was done to locate the data set by name and received an error. User response: The run is aborted. |
NGTP065 | CLUSTERING INDEX NAME SPECIFIED DOES NOT EXIST Explanation: The CLIX(name) keyword was used on the REPART statement, but the index named does not exist. Specify the index name, not the index space name. Do not specify the creator-id. User response: The run is aborted. |
NGTP066 | PART NUMBERS IN RANGE EXCEED THE CURRENT NUMBER OF PARTS. Explanation: The PARTS a:b keyword was used on the REPART statement, but the partition values are not within the current number of partitions in the Tablespace.. User response: The run is aborted. |
NGTP067 | TOTAL OF NEW COUNTS NOT MATCH EXISTING TOTAL Explanation: The USING COUNT exit supplied new rows for partitions in the range of parts being processed, but the total of the new rows did not match the total passed to the exit. User response: The run is aborted. |
NGTP068 | ONLY LIMITKEYS FOR PARTS WITHIN RANGE CAN BE CHANGED, PART number-1 . Explanation: The USING LIMITKEYS exit supplied new values for limitkeys for partitions NOT in the range of parts being processed. Also, the limit key of the last part in the range cannot be changed. User response: The run is aborted. |
NGTP069 | NOTE THAT ALL SYSCOPY RECORDS WERE DELETED BY MODIFY EVEN THOUGH Explanation: REPART was required to do a MODIFY on the entire Tablespace., not just the partition. range being processed to prevent invalid COPY entries from being left on SYSIBM.SYSCOPY. User response: No action is required. |
NGTP070 | ONLY A RANGE OF PARTITIONS WERE REBUILT. FULL COPY IS REQUIRED. Explanation: See message NGTP069. You must run a COPY of the entire partitioned Tablespace.. User response: No action is required. |
NGTP071 | BEGINNING CATALOG (LIMITKEY AND LARGE) UPDATE. Explanation: This message marks the start of the Partitions Limitkey and LARGE Update function of REPART. User response: No action is required. |
NGTP072 | CATALOG (LIMITKEY AND LARGE) UPDATE COMPLETED. Explanation: This message marks the successful end of the Partitions Limitkey and LARGE Update function of REPART. User response: No action is required. |
NGTP073 | TABLESPACE IS EMPTY. Explanation: The tablespace has no rows and cannot be processed. In order to be processed by REPART, at least 1 partition must have some rows so the limitkeys can be determined. User response: The run is aborted. |
NGTP074 | TABLESPACE UNLOAD SKIPPED. TABLESPACE IS EMPTY. Explanation: The UNLOAD phase will be bypassed for the tablespace because the tablespace contains no rows. User response: No action is required. |
NGTP075 | TSRID2 LOAD ERROR ON FILE string-1. Explanation: An error occurred reading the translate RIDs from file. String-1 is the ddname of the file. The header information in the file does not match expected values or the file is missing data. User response: The run is aborted. |
NGTP076 | LAST PARTITION'S LIMITKEY LESS THAN HIGHEST KEY Explanation: The tablespace is a LARGE tablespace and the last partition's limit key specified by the Limitkey exit is less than the highest key found in the tablespace. User response: The run is aborted. |
NGTP077 | PROCESSING INTERRUPTED TO ALLOW DROP/CREATE Explanation: PARTS was specified in the REPART control statement. REPART is pausing to allow DROP and CREATES to be issued. All data has been unloaded. An abend 4095 will accompany this message. User response: Restart the job to continue REPART processing. |
NGTP078 | NEWNAME IGNORED, NUMBER OF PARTITIONS NOT CHANGING. Explanation: PARTS and NEWNAME was specified. However, the number of new partitions is the same as the number of existing partitions. NEWNAME will be ignored. User response: No action is required. |
NGTP079 | REPART PROCESSING NPI INDEX string-1. string-2 ( string-3 ). Explanation: REPART has started the reorganization. of the list non-partitioned Index. String-1 is the index creator, string-2 is the index name, and string-3 is unique or non-unique. User response: No action is required. |
NGTP080 | UNEXPECTED END OF OBJECTS DATA SET. Explanation: REPART has encountered the end of the OBJECTs data set before all objects have been validated. User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. Contact BMC Support. |
NGTP081 | OBJECTS DATA SET CONTROL RECORD IS INVALID. Explanation: REPART has encountered an error while attempting to validate the OBJECTs data set control record. User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. Contact BMC Support. |
NGTP082 | OBJECTS DATA SET LIST STRUCTURE COUNT ERROR. Explanation: REPART has encountered an error while attempting to validate the OBJECTs data set control record. User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. Contact BMC Support. |
NGTP083 | TABLESPACE HAS DIFFERENT # PARTITIONS. Explanation: The number of partitions in the table space does not match what was specified on the REPART PARTS keyword. User response: DROP and CREATE the table space with the correct number of partitions. The run must be restarted. |
NGTP084 | TABLESPACE HAS DIFFERENT PAGE SIZE. Explanation: The page size of the table space does not match the page size of the table space before the REPART PAUSE. User response: DROP and CREATE the table space with the correct page size. The run must be restarted. |
NGTP085 | TABLESPACE HAS DIFFERENT LARGE ATTRIBUTE. Explanation: The LARGE attribute of the table space does not match the LARGE attribute of the table space before the REPART PAUSE. User response: DROP and CREATE the tablespace with the correct LARGE attribute. The run must be restarted. |
NGTP086 | TABLE EDITPROC IS DIFFERENT. Explanation: The EDITPROC of the table does not match the EDITPROC of the table before the REPART PAUSE. User response: DROP and CREATE the table with the correct EDITPROC. The run must be restarted. |
NGTP087 | TABLE # KEY COLUMNS IS DIFFERENT. Explanation: The number of key columns of the table does not match the number of key columns of the table before the REPART PAUSE. User response: DROP and CREATE the table with the correct number of key columns. The run must be restarted. |
NGTP088 | TABLE RECORD LENGTH IS DIFFERENT. Explanation: The record length of the table does not match the record length of the table before the REPART PAUSE. User response: DROP and CREATE the table with the correct record length. The run must be restarted. |
NGTP089 | TABLE # COLUMNS IS DIFFERENT. Explanation: The number of columns of the table does not match the number of columns of the table before the REPART PAUSE. User response: DROP and CREATE the table with the correct number of columns. The run must be restarted. |
NGTP090 | TABLE COLUMN DEFINITIONS ARE DIFFERENT. Explanation: The column definitions of the table does not match the column definitions of the table before the REPART PAUSE. User response: DROP and CREATE the table with the correct column definitions. The run must be restarted. |
NGTP091 | PARTITIONED INDEX IS DIFFERENT. Explanation: The partitioned index of the table does not match the partitioned index of the table before the REPART PAUSE. Either the key columns or uniqueness of the index is different. User response: DROP and CREATE the index with the correct key columns and uniqueness. The run must be restarted. |
NGTP092 | TABLE HAS A NEW INDEX. Explanation: A index was found against the table that did not exist before the REPART PAUSE. User response: DROP the index. The run must be restarted. |
NGTP093 | RESTART VERIFICATION OF TABLESPACE COMPLETED. Explanation: REPART has verified the tablespace objects are correctly defined for the PARTS keyword RESTART. REPART was paused to allow the tablespace to be rebuilt with the new number of partitions. User response: No action is required. |
NGTP094 | REPART PARTS OR TOLARGE CANNOT PROCESS TYPE 1 INDEXES Explanation: The table to be processed by REPART has some type 1 indexes. If you are using the PARTS or TOLARGE parameter, REPART requires all indexes be type 2. User response: Convert all indexes to type 2 and rerun REPART. |
NGTP095 | COUNT LIMITKEYS NOT ASCENDING, PART number-1. Explanation: In determining the limitkeys USING COUNT, REPART has found keys are not in the proper sequence. They must be ascending. Number-1 is the partition number whose limit key is in error. User response: Run a CHECK INDEX against the clustering index of the tablespace. If CHECK INDEX does not find any errors, contact BMC Support. |
NGTP096 | LIMITKEY: hexstring-1 Explanation: This message is display when an error has occurred with a limit key. It displays the limit key which caused the error. User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. |
NGTP097 | THE TABLESPACE IS A LOB TABLESPACE. Explanation: REPART does not support Large Object (LOB) table spaces. User response: Correct the input statement to name a non-LOB tablespace. Resubmit the job. |
NGTP098 | THE TABLESPACE CONTAINS LOB COLUMNS. Explanation: REPART does not support table spaces which contain tables which have Large Object (LOB) columns. User response: Correct the input statement to name a tablespace which contains a table without LOB columns. Resubmit the job. |
NGTP099 | UID 'utilityID' - 'QUICKEXIT' REQUESTED BUT DATABASE DAMAGE MAY RESULT. Explanation: The restart parameter is QUICKEXIT. However, the previous execution of this utilityID terminated in such a way that RESTART is required to preserve data integrity. The indicated utility ID is the second value in the EXEC statement PARM field. If none was provided, the utility uses the job name. User response: The utility attempts to RESTART the utility indicated by the utilityID. |
NGTP100 | 'USE' NUMBER EXCEEDS THE CURRENT NUMBER OF PARTS. Explanation: The USE keyword was used on the REPART statement, but the partition value is not less than the current number of partitions in the table space. User response: The run is aborted. |
NGTP101 | PARTITION OUT OF 'USE' RANGE MUST HAVE ZERO KEYS. Explanation: The USE keyword was used on the REPART statement, but the COUNT exit returned nonzero values for a partition outside the USE range. User response: The run is aborted. |
NGTP102 | 'KEYCOLS' NUMBER EXCEEDS NUMBER OF KEY COLUMNS. VALUE IGNORED. Explanation: The KEYCOLS keyword was used on the REPART statement, but the key columns value is greater than the current number of key columns in the index. User response: The run is aborted. |
NGTP103 | ARCHIVE COMPLETED, number-1 ROWS WRITTEN. Explanation: ARCHIVE has been requested for the data being deleted from the tablespace. It is completed User response: No action is required. |
NGTP104 | BEGINNING CATALOG (LIMITKEY AND DSSIZE) UPDATE. Explanation: This message marks the start of the Partitions Limitkey and DSSIZE Update function of REPART. User response: No action is required. |
NGTP105 | CATALOG (LIMITKEY AND DSSIZE) UPDATE COMPLETED. Explanation: This message marks the successful end of the Partitions Limitkey and DSSIZE Update function of REPART. User response: No action is required. |
NGTP106 | LOBSPACE PROCESSOR TASK STARTING. Explanation: The LOB space processor is the task that controls changes to LOB spaces. User response: No action is required. |
NGTP107 | RESTART DATA NOT COMPATIBLE. Explanation: The restart data found for this UID was build by an incompatible version of BMC/REPART. This version of BMC/REPART cannot be used to process this restart. User response: The run is aborted. Restart the job using the previous version of BMC/REPART. |
NGTP108 | PART partitionNumber CONTAINS KEYS HIGHER THAN LIMITKEY VALUE Explanation: BMC/REPART has found that the limit key for the specified partition is invalid. BMC/REPART found a key in the clustering index for the specified partition that was higher than the partitions's limit key. User response: The run is aborted. Restart the job using different limitkeys for the partition in error. |
NGTP109 | PART partitionNumber CONTAINS KEY LESS THAN PREVIOUS LIMITKEY VALUE FOR DB.TS databaseName.tableSpaceName Explanation: The BMC AMI Reorg REBALANCE job detected an invalid limit key condition that might be related to null column values. BMC AMI Reorg does not support this scenario and terminates processing for this table space. User response: BMC AMI Reorg is unable to complete the REORG rebalance on this object. |
NGTP110 | TABLESPACE HAS PARTITIONS IN REORG PENDING (REORP) STATUS Explanation: BMC/REPART has found that the tablespace contains partitions in reorg pending (REORP) status. This means an ALTER has been done against the clustering index to change the limit key values. User response: No action is required. |
NGTP111 | BMC/REPART PERFORMING REORG PENDING (REORP) PROCESSING Explanation: BMC/REPART has found that the table space contains partitions in reorg pending (REORP) status. BMC/REPART will only perform a rebalance of the partitions in REORP status using the existing limit key values. User response: No action is required. |
NGTP112 | LOB SPACES CREATED IMPLICITLY, NOT SUPPORTED Explanation: BMC/REPART has found that the lob spaces related to the base table space were created implicitly. This is not supported. User response: Currently BMC/REPART does not support implicitly defined lob spaces. |
NGTP113 | EMPTY NON-PARTITIONED INDEX ENCOUNTERED. RUN ABORTED. Explanation: BMC/REPART has found an empty non-partitioned index during the UNLOAD phase. This is not supported. User response: The run is aborted. |
NGTP114 | USE PARAMETER CANNOT BE SPECIFIED WITH A RANGE OF PARTITIONS. Explanation: The USE keyword has been specified with a PARTS keyword denoting a range of partitions. This is not supported. User response: The run is aborted. |
NGTP115 | REPPART REQUIRES A DEFINED PARTITIONING INDEX. Explanation: BMC/REPART cannot detect a defined partitioning index on this table. This is not supported. User response: The run is aborted. |
NGTP116 | INVALID DECIMAL VALUE FOUND IN LIMITKEY. RUN ABORTED. Explanation: A decimal value was for a limit key was encountered. User response: Correct the limit key value and re-submit the job. |
NGTP117 | ROW KEY EXCEEDS HIGHEST LIMITKEY VALUE. RUN ABORTED. Explanation: A key value was encountered that exceeds the highest limit key value defined, making it outside the range of acceptable values. User response: Raise the limit key value and re-submit the job. |
NGTP118 | ROW KEY = hexstring-1 Explanation: Message indicating the row key flagged in error message NGTP117. User response: See message NGTP117 for details. |
NGTP119 | CHANGING +SYNC(ALLATONCE) TO +SYNC(INDIVIDUALLY). Explanation: +SYNC(ALLATONCE) is not a valid option for BMC/REPART. User response: No action is required. |
NGTP120 | PARTITION RANGES MUST BE SPECIFIED, NOT INDIVIDUAL PARTITIONS. Explanation: Syntax error - partition ranges must be specified. User response: Correct the input statement and rerun. |
NGTP124 | DPSIS NOT SUPPORTED IN THIS RELEASE. Explanation: Table spaces with DPSIs cannot be REPARTed in this release. User response: The run is aborted. |
NGTP125 | PART string-1, #8 ROWS, #8 ACCUM Explanation: This message contains internal information about the 'new' partition. It shows the number of rows in the 'new' part and the accumulated amount. User response: No action is required. |
NGTP126 | - IN PTS number-1 - number-2 (LPL hexstring-1 number-3 XOF hexstring-2 - LF hexstring-3 RWS1 number-4) Explanation: This message contains internal information about the 'new' partition. It shows the input parts contributing to the output part. RWS1 is the number of rows from the first contributing input part. User response: No action is required. |
NGTP127 | EXIT MEMBER 'string-1' DOES NOT EXIST IN THE NGTAUTO LIBRARY Explanation: 'USING EXIT name' was specified in the REPART SYSIN statement, but the named exit does not exist in the CDBEXEC or NGTAUTO library. User response: The run is aborted. |
NGTP128 | RUN IS COMPLETED - 'CHECKSIZES' SPECIFIED. Explanation: CHECKSIZES signals to stop the REPART run after LR is complete. The size of all the 'new' tablespace partitions has been determined and none exceed Db2 limits. User response: No action is required. |
NGTP129 | USING LIMITKEYS REQUIRES NAMING THE DSNAME Explanation: USING LIMITKEYS requires you to name the data set containing the new limitkeys in the proper format. The DSN keyword must be used and name an existing data set or PDS. If a PDS, use the MEMBER keyword too. User response: Correct the input statement and rerun. |
NGTP130 | USING LIMITKEYS DATASET ERROR Explanation: The LIMITKEYS data set is of a specific format. Previous messages should have described the error. User response: Correct the data set and rerun. |
NGTP131 | LIMITKEYS DATASET DOES NOT EXIST Explanation: The data set named in USING LIMITKEYS DSN() does not exist. User response: Correct the input statement and rerun. |
NGTP132 | LIMITKEYS DATASET TITLE DOES NOT MATCH INDEX COLUMNS. Explanation: The data set named in USING LIMITKEYS DSN() is of a specific format. It can be created by a REPART TABLESPACE TESTINRW SAVELKEYS DSN(). User response: Correct the data set and rerun. |
NGTP133 | LIMITKEYS DATASET INPUT PART DATA MISSING, GOT string-1 - EXPECTED string-2 Explanation: The Limitkeys input data must have data for each part being processed and they must be in sequence. One of the parts being processed does not have input data. User response: Correct the data set and rerun. |
NGTP134 | LKEYS INPUT ERROR PT string-1, COL string-2 - string-3 Explanation: An error was detected on the input data for the part and column named. User response: Correct the data set and rerun. |
NGTP135 | SEGTS INPUT CANNOT SPECIFY PART NUMBERS. Explanation: If the input is a non-partitioned tablespace, part numbers must not be specified on the REPART statement. User response: Correct the SYSIN and rerun. |
NGTP136 | SEGTS INPUT MUST SPECIFY 'USE' KEYWORD. Explanation: If the input is a non-partitioned tablespace, the 'USE' keyword must be on the REPART statement to specify the number of new partitions. User response: Correct the SYSIN and rerun. |
NGTP137 | PAGESIZE IS 32K AND DSSIZE IS LESS THAN 2G. Explanation: The object being processed has a page size of 32K and a DSSIZE of less than 2 GB. The repartitioning of this object is not supported at this time. This object will be skipped. User response: The run is aborted. |
NGTP138 | MULTIPLE PART RANGES DETECTED. ONLY 1 ALLOWED FOR REBALANCE. TABLESPACE SKIPPED string-1.string-2. Explanation: BMC AMI Reorgdoes not support REBALANCE with multiple partition ranges specified. User response: Correct the syntax, and rerun the job. |
NGTP139 | DUPLICATE LIMITKEY FOUND FOR string-1.string-2. PROCESSING TERMINATED. Explanation: BMC AMI Reorg REBALANCE detected duplicate limit key values and terminated processing to prevent damage to the object. User response: Contact BMC Support. |
NGTP240 | DPSIS NOT SUPPORTED YET Explanation: The tablespace to be REPARTed has a DPSI. These are not supported in this release. User response: The object is skipped. |
NGTP241 | SOME TABLE ALTERS CANNOT BE DONE. number-1 PARTS OF number-2 CAN BE DONE. Explanation: Table partitioning is in effect. Db2 requires that ALTERs be done one part at a time and the limit key sequence be maintained constantly. The combination of old and new limitkeys makes this impossible. User response: The object is skipped. |
NGTP242 | SOME TABLE ALTERS CANNOT BE DONE. PART number-1 CANNOT BE ALTERED. Explanation: Table partitioning is in effect. Db2 requires that ALTERs be done one part at a time and the limit key sequence be maintained constantly. The combination of old and new limitkeys makes this impossible. User response: The object is skipped. |
NGTP243 | SOME ALTERS FAILED. Explanation: There should be error messages from Db2 about the ALTER failure. User response: Contact BMC Support. |
NGTP247 | VSAM DATASET MISSING FOR TABLESPACE string-1 . string-2 Explanation: The named tablespace does not have a VSAM data set corresponding to the Db2 Catalog definition. User response: The object is skipped. |
NGTP248 | VSAM DATASET MISSING FOR TABLESPACE string-1 . string-2 PART number-1 Explanation: The named tablespace does not have a VSAM data set corresponding to the Db2 Catalog definition. User response: The object is skipped. |
NGTP249 | VSAM DATASET MISSING FOR INDEXSPACE string-1 . string-2 Explanation: The named index space does not have a VSAM data set corresponding to the Db2 Catalog definition. User response: The object is skipped. |
NGTP250 | VSAM DATASET MISSING FOR INDEXSPACE string-1 . string-2 PART number-1 Explanation: The named index space does not have a VSAM data set corresponding to the Db2 Catalog definition. User response: The object is skipped. |
NGTP251 | OBJECT IS IN A RESTRICTED STATE string-1. string-2 -REPART ABORTED. Explanation: The named object is in a restricted state - Repart cannot be done on restricted objects. User response: The object is skipped. |
NGTP252 | OBJECT IS IN A RESTRICTED STATE string-1. string-2 PART number-1 - REPART ABORTED. Explanation: The named object is in a restricted state - Repart cannot be done on restricted objects. User response: The object is skipped. |
NGTP254 | REPART STARTING FOR TABLESPACE string-1. string-2 PART number-1 Explanation: This message indicates the REPART process has started for the named tablespace. The part number is listed if this is a partitioned tablespace. User response: No action is required. |
NGTP255 | REPART STARTING FOR TABLESPACE string-1. string-2 Explanation: This message indicates the REPART process has started for the named tablespace. The part number is listed if this is a partitioned tablespace. User response: No action is required. |
NGTP256 | REPART PHASE 1 COMPLETED FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates the REPART process has completed the Phase 1 read on the named table space. The part number is listed if this is a partitioned table space. User response: No action is required. |
NGTP257 | REPART PHASE 1 COMPLETED FOR TABLESPACE tableSpaceName Explanation: This message indicates the REORG process has completed the Phase 1 read on the named table space. The part number is listed if this is a partitioned table space. User response: No action is required. |
NGTP258 | INDEX IS DEFERRED - PROCESSING ABORTED. Explanation: Indexes cannot be Reorganized if they are in a deferred state. User response: No action is required. |
NGTP259 | REPART COPY STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates the REPART process has started the COPY phase. User response: No action is required. |
NGTP260 | REPART COPY COMPLETE FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates the REPART process has completed the COPY phase. User response: No action is required. |
NGTP261 | STARTING LR ON OUTPUT PART number-1 Explanation: REPART is assigning rows to pages for the specified part number. User response: No action is required. |
NGTP262 | OUTPUT PART number-1 WILL HAVE number-2 PAGES AND #8 ROWS Explanation: REPART has completed Logical Reorg for the named partition. The new partition will have the shown number of pages and rows. User response: No action is required. |
NGTP270 | TABLESPACE IS DEFERRED - PROCESSING ABORTED Explanation: REPART cannot process a DEFERRED object User response: Load some rows into the tablespace to DEFINE all the objects. |
NGTP271 | AN INDEX IS DEFERRED - PROCESSING ABORTED Explanation: REORG cannot process a DEFERRED object User response: Load some rows into the tablespace to DEFINE all the objects. |
NGTP272 | REPART TABLESPACE tableSpaceName PART number-1 - READING CLIX (SPACE) string-3 Explanation: This message signals the start of a CLIX read for the named table space. User response: No action is required. |
NGTP273 | REPART TABLESPACE tableSpaceName - READING CLIX (SPACE) string-3 Explanation: This message signals the start of a CLIX read for the named table space. User response: No action is required. |
NGTP274 | REPART PHASE 1 COMPLETED FOR TS tableSpaceName PART number-1 - CLIX string-3 Explanation: This message indicates the REPART process has completed the Phase 1 read on the named CLIX index space. The part number is listed if this is a partitioned table space. User response: No action is required. |
NGTP275 | REPART PHASE 1 COMPLETED FOR TS tableSpaceName - CLIX string-3 Explanation: This message indicates the REPART process has completed the Phase 1 read on the named CLIX index space. The part number is listed if this is a partitioned table space. User response: No action is required. |
NGTP276 | REPART PHASE 2 STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that REPART has completed the Phase 1 reads and is starting the Logical Reorg. User response: No action is required. |
NGTP277 | SHOULD NOT OCCUR Explanation: This message indicates that REPART has completed the Phase 1 reads and is starting the Logical Reorg. User response: No action is required. |
NGTP278 | REPART PHASE 2 COMPLETED FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that REPART has completed the Phase 2 Logical Reorg processing. The part number is the Output partition number. User response: No action is required. |
NGTP279 | SHOULD NOT OCCUR Explanation: This message indicates that REPART has completed the Phase 2 Logical Reorg processing. User response: No action is required. |
NGTP280 | REPART OUTPUT BUILD STARTING FOR PART number-1 TABLESPACE tableSpaceName - IXSPACE string-3 Explanation: This message indicates that the table space is beginning the write phase. The part number is the Output partition number. User response: No action is required. |
NGTP281 | REPART OUTPUT BUILD COMPLETE FOR PART number-1 TABLESPACE tableSpaceName - IXSPACE string-3 Explanation: This message indicates that the table space has completed the write phase. The part number is the Output partition number. User response: No action is required. |
NGTP285 | BEGINNING LR PHASE FOR TABLESPACE tableSpaceName Explanation: This message indicates that the Logical Reorg phase of REPART has begun. User response: No action is required. |
NGTP286 | COMPLETED LR PHASE FOR TABLESPACE tableSpaceName Explanation: This message indicates that the Logical Reorg phase of REPART has completed. User response: No action is required. |
NGTP287 | LIMITKEYS HAVE BEEN ALTERED FOR TABLESPACE tableSpaceName Explanation: This message indicates that the table space LIMITKEYS have been altered. The object should be in REORG PENDING status (REORGP). User response: No action is required. |
NGTP288 | REPART PHASE 4 STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that the table space is beginning Phase 4 - Log Apply. The part number is the Output partition number. User response: No action is required. |
NGTP289 | SHOULD NOT OCCUR Explanation: This message indicates that the table space is beginning Phase 4 - Log Apply. User response: No action is required. |
NGTP290 | REPART PHASE 4 COMPLETED FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that the table space Log Apply is complete. The part number is the Output partition number. User response: No action is required. |
NGTP291 | SHOULD NOT OCCUR Explanation: This message indicates that the table space Log Apply is complete. User response: No action is required. |
NGTP292 | REPART PHASE 5 STARTING FOR TABLESPACE tableSpaceName PART number-1 Explanation: This message indicates that the table space is beginning Phase 5 - COPY. The part number is the Output partition number. User response: No action is required. |
NGTP293 | SHOULD NOT OCCUR Explanation: This message indicates that the table space is beginning Phase 5 - COPY. User response: No action is required. |
NGTP294 | REPART PHASE 5 COMPLETED FOR TS tableSpaceName PART number-1 Explanation: This message indicates that the table space COPY is complete. The part number is the Output partition number. User response: No action is required. |
NGTP295 | SHOULD NOT OCCUR Explanation: This message indicates that the table space COPY is complete. User response: No action is required. |
NGTP296 | REPART AFTERACC STARTING FOR TABLESPACE tableSpaceName Explanation: This message indicates that the Afteracc processing is starting. User response: No action is required. |
NGTP297 | REPART AFTERACC COMPLETED FOR TABLESPACE tableSpaceName Explanation: This message indicates that the Afteracc processing has completed. User response: No action is required. |
NGTP298 | REPART AFTERACC string-1 ENTRY, QUE = hexstring-1, CASE = hexstring-2 Explanation: This message indicates that the Afteracc processing has started. User response: No action is required. |
NGTP299 | string-1.string-2 (number-1) number-2 PAGES EXCEEDS MAXIMUM ALLOWABLE SIZE OF number-3 PAGES Explanation: REORG INDEX will process data sets up to a maximum size. The index space exceeded that maximum. The value in parentheses is the partition number. User response: Contact BMC Support. |
NGTP911 | #ERREL S0C3 Explanation: This is a message to indicate an internal logic error User response: Contact BMC Support. |
NGTP990 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP991 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP992 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP993 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP994 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP995 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP996 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP997 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP998 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
NGTP999 | diagnostic text. Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
Comments
Log in or register to comment.