Messages BMC397000 through BMC397099
This group includes messages for the BMC AMI Log Master for Db2 product.
| Number | Description |
|---|---|
| BMC397000 | REPORT TEMPLATE xmlParser PARSE ERROR - parserErrorText Explanation: The product displays this message as it processes a report template. The template contains invalid XML syntax. The message displays the error text that is returned by the product's internal XML parser. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397001 | REPORT BREAK POSITIONING ERROR - ELEMENT elementName RESTRICTED TO USAGE context Explanation: The product displays this message as it processes a report template. The template currently defines at least one order by field (report break) in a context that is not supported by the product. For example, some types of reports require that a given order by field must be either the first, last or only defined field. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397002 | REPORT TEMPLATE QUERY FAILED - MODULE moduleName Explanation: The product displays this message as it processes a report template. The product has encountered an error as it attempts to load internal software that processes XML documents. User response: Submit the job again to determine if the error condition is transitory. If the problem occurs again, contact BMC Support. |
| BMC397003 | REPORT TEMPLATE ERROR - INVALID CHILD ELEMENT elementName01, PARENT ELEMENT elementName02 Explanation: The product displays this message as it processes a report template. The template currently defines at least one element that does not have the required logical relationship to other elements within the template. The message displays the incorrectly-positioned element as elementName01. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397004 | REPORT TEMPLATE ERROR - INVALID ReportData DATA DICTIONARY VALUE elementValue, ATTRIBUTE TYPE='attribValue' Explanation: The product displays this message as it processes a report template. For at least one ReportData element in the template, the value of the element conflicts with the value of the Type attribute of the element. For example, if the value of the ReportData element is URID, the value of the Type attribute cannot be Counters because that combination is not defined as valid in the product's report data dictionary. The message displays the invalid ReportData value and the value of that element's type attribute. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397005 | REPORT TEMPLATE ERROR - CANNOT FIND REPORT TEMPLATE templateID IN THE REPOSITORY Explanation: The product displays this message as it attempts to generate a report by using a report template. The SYSIN syntax for your job or job step defines a template ID that does not exist in the product's Repository on the current Db2 subsystem. Processing terminates. User response: Use the product's online interface to verify the valid template IDs for the current subsystem. Edit the SYSIN syntax of your job or job step to specify the correct template ID. If the template exists on a different subsystem, consider exporting the template to a data set and specifying that data set name in your SYSIN syntax. If you have verified that the specified template ID exists in the Repository for the current subsystem, contact BMC Support. |
| BMC397006 | REPORT TEMPLATE ERROR - UNKNOWN ELEMENT elementName Explanation: The product displays this message as it processes a report template. At least one element in the template does not exist in the product's report data dictionary (which defines all valid elements, attributes, and values for a report template). The message displays the invalid element name. This condition should not occur when a template is created by using the product's online interface. All element and attribute values in a report template are case-sensitive. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397007 | REPORT TEMPLATE ERROR - INVALID ELEMENT VALUE elementValue, ELEMENT elementName Explanation: The product displays this message as it processes a report template. The value of at least one element in the template does not exist in the product's data dictionary (which defines all valid elements, attributes, and values for a report template). The message displays the invalid element value and the valid element name. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397008 | REPORT BREAK ELEMENT elementName01 SPECIFIED BUT PREVIOUS ELEMENT elementName02 MUST BE LAST OR ONLY BREAK Explanation: The product displays this message as it processes a report template. The template currently defines more than one order by field (report break), but the report type requires that one of the preceding order by fields must be the last or only field. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397009 | REPORT TEMPLATE ERROR - INVALID ATTRIBUTE VALUE attribName='attribValue', ELEMENT elementName Explanation: The product displays this message as it processes a report template. A valid element within the template has a valid attribute, but the value of the attribute is not valid. The message displays the valid attribute name, the invalid attribute value, and the valid element name. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397010 | REPORT TEMPLATE ERROR - MISSING ATTRIBUTE attributeName, ELEMENT elementName Explanation: The product displays this message as it processes a report template. A valid element within the template does not define at least one of that element's required attributes. The message displays the name of the value element and the name of the missing attribute. This condition should not occur when a template is created by using the product's online interface. All element and attribute values in a report template are case-sensitive. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397011 | REPORT TEMPLATE ERROR - EMPTY REPORT TEMPLATE FILE Explanation: The product displays this message as it attempts to generate a report by using a report template. The SYSIN syntax of your job or job step defines a template data set, but the data set does not contain a valid report template. Processing terminates. User response: Use the product's online interface to verify whether your specified data contains a valid report template. (Attempt to import a template from the data set.) Edit the SYSIN syntax of your job or job step to specify the correct data set name. Submit the job again. |
| BMC397012 | REPORT TEMPLATE ERROR - INVALID ATTRIBUTE DATA TYPE: attribName='attribValue', ELEMENT elementName Explanation: The product displays this message as it processes a report template. A valid element within the template defines a valid attribute, but the value defined for that attribute is not the correct data type. For example, an attribute that requires a numeric value might be defined with an alphanumeric value. The message displays the valid attribute name, the invalid attribute value, and the valid element name. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397013 | sectionType OPTIONS keyword01 AND keyword02 ARE MUTUALLY EXCLUSIVE Explanation: This message indicates that two syntax keywords within the same section type definition conflict with each other. For example, in REPORT options, the TEMPLATE keyword specifies a report template (which includes the order by fields for sorting). If your batch syntax also specifies fields with the ORDER BY keyword, the product cannot determine which set of order by fields to use. Processing terminates. User response: Edit the SYSIN syntax of your job or job step. Remove or change the value of one of the conflicting syntax keywords. Submit the job again. |
| BMC397014 | REPORT TYPE reportType DOES NOT MATCH THE REPORT TYPE DEFINED IN TEMPLATE templateStorageType templateLocation Explanation: The product displays this message as it attempts to generate a report by using a report template. The template defines a report type (for example, Audit, Detail, Summary, and so forth), but the SYSIN syntax of your job or job step defines a different report type. The message displays either the template ID or the template data set name (depending on the location specified by your SYSIN syntax). Processing terminates. User response: Edit the SYSIN syntax of your job or job step. Either change your report type to match the template, or change your template to match the report type. Submit the job again. |
| BMC397015 | columnType ROLLBACKS PROCESSED nnnnnn Explanation: The product displays this informational message as it processes data from large-volume columns (such as LOB or XML columns). The message displays the number of rollback actions that affected large-volume columns. Processing continues. User response: No action is required. |
| BMC397016 | PROCESSING ERROR OCCURRED IN IDCAMS SERVICES, SEE PRECEDING MESSAGES Explanation: The product is attempting to perform an operation on a data set (allocation, deletion, and so forth) and has encountered an IDCAMS error during the operation that prevents successful completion. Processing terminates. User response: Use any preceding or subsequent operating system messages to determine the cause of the error and resolve it. If you cannot resolve the error condition or if there appears to be no valid reason for the error, contact BMC Support. |
| BMC397017 | dataSetType DATASETS THAT HAVE BEEN ALLOCATED nnnnnn Explanation: The product displays this informational message as it allocates data sets for use as external VSAM files for large-volume columns (such as LOB or XML columns). The message displays the type of file and the number of allocated data sets. Processing continues. User response: No action is required. |
| BMC397018 | REPORT TEMPLATE ERROR - ELEMENT VALUE elementName INVALID FOR REPORT TYPE reportType Explanation: The product displays this message as it processes a report template. The template defines a valid report type (for example, Audit, Detail, Summary, and so forth), but it also contains at least one element that is not valid for the current report (although the element might be valid for other reports types). The message displays the invalid element name and the report type of the template. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397019 | REPORT TEMPLATE ERROR - ELEMENT VALUE elementName INVALID FOR REPORT SECTION reportSection Explanation: The product displays this message as it processes a report template. At least one of the elements in the template is contained within a report section (for example, report header, break footer, and so forth) that does not support that element. The message displays the element name and the name of the report section that does not support the element. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface and the template has not been edited, contact BMC Support. |
| BMC397020 | DECOMPRESSION REQUIRED FOR RBA X'rbaValue' Explanation: This warning message indicates that the product needs to decompress a log record for a compressed table space. The product is attempting to obtain the applicable compression dictionary from either an available image copy or from the current table space. Processing continues. User response: No immediate action is required. If the product cannot obtain the required compression dictionary, it might terminate later with additional error messages. |
| BMC397021 | event01 FOUND AT X'rbaValue01' AND action02 FOUND AT X'rbaValue02' WITH NO VALID FULL COPY Explanation: This warning message indicates that the product has encountered the log records of two events that restrict compression dictionary and row completion processing. No image copy exists to provide compression dictionaries or row images for the range of log between these two events. Standard practices of recoverable Db2 operation normally prevent this situation from occurring. The product might not be able to process the range of logs between the two events successfully. Processing continues. User response: No immediate action is required. If the product needs to obtain a compression dictionary for (or perform row completion processing on) log records between the two events, it might terminate later with additional error messages. |
| BMC397022 | DATASET dataSetName IS A PDS BUT NO MEMBER WAS SPECIFIED Explanation: The product displays this message as it attempts to read or write an external data set (for example, a report template data set). Your job or job step specifies a partitioned data set (PDS) but does not specify a member within the PDS. Processing terminates. User response: Edit your SYSIN syntax (or redefine your work ID through the online interface) to complete the specified PDS with a member name. Submit the job again. |
| BMC397024 | INVALID RECFM FOR DATASET dataSetName Explanation: The product displays this message as it attempts to read or write an external data set (for example, a report template data set). Your job or job step specifies a data set, but the data set you specified has a record length that is not compatible with the data that the product expects to read or write. Processing terminates. User response: Edit your SYSIN syntax (or redefine your work ID through the online interface) to specify a valid record format. Submit the job again. |
| BMC397025 | XML RECORD NOT FOUND FOR DOCID nodeValue VERSION versionNumber Explanation: The product displays this warning message as it processes log records related to an XML column. The product has encountered a log record of a change to a table that contains an XML column but cannot find a log record of a related change to the corresponding XML table space. This situation can occur when the product processes the log records of a LOAD LOG YES action. The log can contain duplicate log records for the table with the XML column, but no duplicate records for the XML table space. Processing continues. User response: No immediate action is required. If a LOAD LOG YES action has not occurred during the time frame of your log scan, contact BMC Support. |
| BMC397026 | LOG MASTER TECHNOLOGY IS PROTECTED BY U.S. PATENT NUMBER patentNumbers Explanation: These informational messages list patents that cover the current version of the product. Processing continues. User response: No action is required. |
| BMC397027 | CREATE INSTANCE FAILED: COMID< nnnn> CLSID< nnnn> IID< nnnn> HRESULT< nnnn> Explanation: The product encountered an internal error during processing. The product requires one of its internal parts (modules), but that module is not currently available. Many possible reasons exist for this problem, including installation problems or other failures in your environment. In some cases, this message can indicate that the product cannot find the module in your STEPLIB concatenation. Processing terminates. User response: To determine the missing module, contact BMC Support. |
| BMC397028 | QUERY INTERFACE FAILED: COMID nnnn CLSID nnnn IID nnnn HRESULT nnnn Explanation: An internal error occurred during processing. This error might be because of a failed or corrupted installation. Processing terminates. User response: Contact BMC Support. |
| BMC397029 | INTERFACE ERROR: COMID nnnn CLSID nnnn IID nnnn HRESULT nnnn Explanation: An internal error occurred during processing. This error might be because of a failed or corrupted installation. Processing terminates. User response: Contact BMC Support. |
| BMC397030 | LINES PER PAGE OF linePageValue01 FOR TEMPLATE templateLocation IS INSUFFICIENT, AT LEAST linePageValue02 REQUIRED FOR HEADERS, FOOTERS, AND DATA Explanation: The product can display this message as it processes a report template or as it attempts to generate a report by using a template. The current template defines a number of lines per page that is too small. The currently defined page cannot contain all of the template's headers and footers (for the report and the defined report breaks) and at least one body/detail record. The message displays either the template ID or the data set name of the template and provides an estimated minimum line per page value. Processing terminates. User response: Use the product's online interface to change the template and either increase the number of lines per page, or decrease the number of lines in the report's headers, footers, and body detail records. Submit the job again. |
| BMC397031 | REPORT TEMPLATE ERROR syntaxErrorText Explanation: The product displays this message as it processes a report template. The template contains invalid XML syntax. The message displays the error text that is returned by the product's internal XML parser. This condition should not occur when a template is created by using the product's online interface. Processing terminates. User response: If you created the report template by using the product's online interface, and the template has not been edited, contact BMC Support. |
| BMC397032 | objectType objectName WAS IMPLICITLY CREATED FOR XML COLUMN. DO NOT EXPLICITLY SPECIFY XML objectType TO RECOVER THE OBJECT IN DROPRECOVERY PROCESSING Explanation: The new XML table or table space to be created implicitly by Db2 might not have the same object name as the dropped object. User response: In the DROPRECOVERY statement, specify the name of the XML base table or table space that you want to recover, and then submit the job again. |
| BMC397033 | RECORD BUFFER SIZE buffersize TOO SMALL, recordType LENGTH recordLength, RBA recordRBA Explanation: The variable recordType is one of the following values:
User response: Contact BMC Support. |
| BMC397034 | INVALID SORT ORDER FOR reportType REPORT, ORDER MUST BE requiredOrder Explanation: The specified order for sorting data in the report is not valid for the report that you are generating. User response: Correct the sort order to use the order displayed in the message, and then try the report again. |
| BMC397035 | WARNING: INVALID COMPRESSION DICTIONARY FOUND IN THE REPOSITORY: databaseName.tableSpaceName, DSNUM: partitionNumber, STARTRBA: X'startRbaValue', BUILTRBA: X'builtRbaValue' Explanation: The product attempted to load and use a compression dictionary from the repository, but the object was incomplete or not valid. This can happen if a REPOS UPDATE job was terminated while it was updating the repository, or if the ALPOLDO table was manually modified. The compression dictionary object in the Repository is not usable. The product will attempt to load the compression dictionary from other sources, such as image copies. Processing continues. User response: Determine why the compression dictionary is not valid, or contact BMC Support. |
| BMC397036 | PREDICATE TYPE predicateType NOT VALID FOR NON-DATASHARING SUBSYSTEM Explanation: Your filter specifies a selectable field and value related to data sharing (for example, MEMBER NAME=Db2A). However, the Db2 subsystem that you are running on is a non-data-sharing environment. User response: Correct your filter by removing the predicate type and value. Submit the job again. |
| BMC397037 | DDNAME = ddname Explanation: This message displays a ddname associated with another message. User response: This message does not require immediate action. Your overall response depends on the content of the associated messages. |
| BMC397038 | NO OBJECT SET FOUND FOR objectSetNameOrPattern Explanation: BMC AMI Log Master found no matches for the object set name or pattern that you specified in the filter. User response: Correct the object set name or pattern in the filter and submit the job again. |
| BMC397039 | INVALID TOKEN allocationParameter AFTER DATASET dataSetName ALLOCATION. PARAMETER IS NOT ALLOWED FOR DDNAME OUTPUT SYNTAX AS DSN NAME IS 8 BYTES OR LESS Explanation: For the output type that is specified in the job, BMC AMI Log Master treats a data set name of eight bytes or less as a DD name, and does not allow allocation parameters. User response: Remove the allocation parameters and submit the job again. |
| BMC397041 | QUEUE NODE OFFLOAD # number COMPLETE FOR URID X'uridRbaValue' Explanation: This message indicates the number of queue node offloads that occurred, and the URID that was offloaded. User response: No action is required. |
| BMC397042 | TOTAL ALLOCATED STORAGE USED amountK, NUMBER OF RECORDS OFFLOADED number Explanation: This message indicates the maximum storage that was used for Queue Manager storage before a URID/queue node was offloaded to prevent exceeding the storage limit. The maximum storage limit is specified by the value of either the QBLRBUF installation option or the LOGRECORD BUFSIZE keyword of the OPTION statement. User response: No action is required. |
| BMC397043 | QUEUE NODE OFFLOAD DATASET dataSetName RETURNED FOR REUSE Explanation: This message indicates that a queue node offload data set was returned to the list of free allocated data sets for reuse when another queue node offload is required. User response: No action is required. |
| BMC397044 | LOG BYTES SORT READY TO BE CLOSED Explanation: BMC AMI Log Master has gathered all of the required information, and the sort input phase is complete. User response: No action is required. |
| BMC397045 | ZIIP ENABLED (xbmReturnCode) USING XBM SUBSYSTEM ssid Explanation: BMC AMI Log Master enabled zIIP processing successfully, and discovered the specified XBM subsystem for zIIP enablement. XBM issues the return code after enablement. User response: No action is required. |
| BMC397046 | ZIIP NOT ENABLED (xbmReturnCode) USING XBM SUBSYSTEM ssid Explanation: See explanation for message BMC397047. User response: See response for message BMC397047. |
| BMC397047 | ZIIP NOT ENABLED (xbmReturnCode) Explanation: These messages indicate that zIIP processing was not enabled successfully. However, BMC AMI Log Master might have discovered an XBM subsystem. XBM issues the return code, and the value depends on the reason for the error. User response: Some possible return codes and responses are as follows. If you cannot correct the problem, contact BMC Customer Support.
|
| BMC397048 | CORR ID: correlationID AUTH ID: authorizationID PLAN NAME: planName CONN TYPE: connectionType CONN ID: connectionID Explanation: The linear Queue Manager spilled a URID to a data set. Message BMC397041 follows with more information. User response: No action is required. |
| BMC397049 | ALLOCATION PARAMETERS FOR dataSets DATASETS ARE MISSING Explanation: The allocation parameters for the data set named in the message are not correct. BMC AMI Log Master requires either SMS parameters or the volume serial number. User response: Correct the allocation parameters and submit the job again. |
| BMC397050 | DUPLICATE FILE REFERENCE DATASETS FOUND FOR COLUMNS columnName AND columnName. columnType COLUMNS REQUIRE A UNIQUE NAME Explanation: Your job uses a file reference data set name that already exists in the log scan. User response: Rename the file reference data set and submit the job again. |
| BMC397051 | BEFORE IMAGE FOR UPDATE FOUND FOR tableName, NOT HANDLED FOR LOAD DB2 OUTPUT Explanation: Log Master detected an inline LOB for which some data is stored in the LOB auxiliary store. No, before the image is associated with that data; therefore, if you generate UNDO SQL, the SQL UPDATE statement will not include that data. BMC AMI Log Master can only generate UNDO SQL to undo an update action on an inline LOB column when the LOB is contained entirely in the inline section, and you use Data Capture Changes (DCC). User response: No action is required. |
| BMC397052 | COLUMN NAME: columnName ROWID: rowID LOGRBA: logRba Explanation: This message identifies the record associated with message BMC397051. User response: No action is required. |
| BMC397053 | INVALID recordType RECORD FOUND FOR idType, NOT HANDLED FOR outputType OUTPUT Explanation: A LOB or XML record has the invalid bit set, and BMC AMI Log Master skipped the record. User response: No action is required. |
| BMC397054 | FOUND PENDING CHANGE(S) ON TABLESPACE tableSpaceName, CANNOT UNDO THE SPECIFIC CHANGES FOR UNDO DDL Explanation: Log Master cannot UNDO a specific pending change for UNDO DDL. Comments in the DDL output show the pending changes. User response: No action is required. |
| BMC397055 | CANNOT POINT INTO LOG FILE dataSetName Explanation: The product displays this informational message as it attempts to use point processing (random access) to read information from the data set listed in the message. However, random access is not available for one of the following reasons:
User response: No action is required. |
| BMC397056 | DISCARDING SYSOBD RECORD DUE TO reason Explanation: Log Master cannot process SYSOBD records for cloned tables or aborted URIDs. BMC AMI Log Master also suppresses the older version log records that are associated with the clone and its base table. User response: No action is required. |
| BMC397057 | PROCESSING SYSOBD RECORD OF COMMITTED URID X'uridRbaValue' Explanation: This message indicates that BMC AMI Log Master is passing the SYSOBD record of the specified URID to the Db2 Solution Common Code (SCC) API that it uses. User response: No action is required. |
| BMC397058 | REGISTRATION OF PSID: psidValue RETURNED A WARNING Explanation: This message indicates that the Db2 Solution Common Code (SCC) API that BMC AMI Log Master uses returned a warning message when BMC AMI Log Master registered a table space for which no versions exist. User response: No action is required. |
| BMC397060 | SOME DDL STATEMENT TEXT(S) MAY NOT BE AVAILABLE DUE TO LOB NOT INCLUDED OR LOB DATA UNAVAILABLE Explanation: BMC AMI Log Master cannot generate DDL statement text that is stored in LOB data. This error occurs when you are running BMC AMI Log Master for Db2 on a Db2 version 10 or later subsystem, and one of the following conditions exists:
User response: If you are using an input logical log file, ensure that the file is generated with INCLUDE LOBS or INCLUDE DDL and submit the job again. To avoid the unavailable LOB data condition, regularly make image copies of the system catalog and LOB table spaces. If the problem persists, contact BMC Support. |
| BMC397061 | messageText Explanation: The text shown is output from a facility used by this product (for example, IDCAMS). User response: Consult the technical documentation for the facility that issued the original message, or contact BMC Support. |
| BMC397062 | EITHER DB2 CONNECTION OR XML STRING FILE IS REQUIRED FOR PROCESSING XML DATA Explanation: The SQL or LOAD output included XML data from a logical log input file that did not include an XMLSTRING control file. This file contains the string IDs and string data that Db2 uses to encode the data in XML columns. User response: If you received the message BMC097444, then you must establish a Db2 connection. To do so, specify a WORKID statement or a LOGMARK statement in the job syntax. Rerun the job with the Db2 connection, or regenerate the logical log input file to include the XMLSTRING control file. |
| BMC397063 | icType RECORD FOUND IN SYSCOPY FOR databaseName.tableSpaceName DSNUM partitionNumber AT RBA X'startRba' Explanation: BMC AMI Log Master discovered an SYSCOPY entry for the indicated table space with the RBA/LRSN value indicated that might affect log processing. If the indicated ICTYPE value is MODIFY (the result of a MODIFY RECOVERY utility), information that Log Master requires (for example, image copy information, REORG activity, and log ranges) might not be available. The result might be incomplete or errant processing. ICTYPE values include MODIFY, ALTER (ADD PARTITION), ALTER (DROP PARTITION), ALTER (MOVE TABLE), REORG (MOVE TABLE SOURCE), REORG (MOVE TABLE FROM <databaseName.tableSpaceName>), ALTER (PBG TO PBR), and ALTER (PBG TO PBR) (DROP PARTITION). User response: Review the output for completeness. |
| BMC397064 | UNFORMATTED PAGES IN ACTIVE LOG - NUM PAGES REDUCED FROM oldPages TO newPages Explanation: This message may follow BMC97346 if a new log file added to a Db2 subsystem (via DSNJU003 or -SET LOG NEWLOG) is being accessed before it has been fully formatted. The number of pages that will be read will be reduced based on the high used RBA of the data set. User response: No action is required. |
| BMC397065 | DSN MODEL NAME CANNOT EXCEED 41 BYTES FOR outputType OUTPUT Explanation: The length of the DSN model name specified for DROPRECOVERY or OUTCOPY is longer than the 41 characters allowed. for the data set is too long. User response: Verify the DSN name, especially the symbolism used in the name, and shorten the name as necessary. |
| BMC397066 | OVERTIME OBJECT FOR TABLE DBID.OBID dbidValue.obidValue NEEDED TO PROCESS RECORD AT RBA X'rbaValue' DOES NOT EXIST Explanation: This error message is issued when processing a log record for a LOAD output and the corresponding table description is not found in either the Db2 Catalog, because the table had been dropped, or in the product's Repository because it had not been updated. BMC AMI Log Master cannot scan the specified range. User response: Possible user actions before retrying are:
|
| BMC397070 | PLANNED LOG FILES: plannedLogFiles PLANNED PAGES: plannedLogPages Explanation: This informational message provides the estimated number of Db2 log files and pages needed for log processing. The actual number of Db2 log files and pages read could differ. This message is displayed for primary and completion processing. User response: No action is required. |
| BMC397071 | LOGS READ: logFilesRead (logFilesPercentage COMPLETE), PAGES READ: logPagesRead (logPagesPercentage COMPLETE) Explanation: This informational message provides the number of Db2 log files and pages read and a percentage of completion based on the estimated number of log files and pages needed for log processing. User response: No action is required. |
| BMC397072 | EXCHANGE RECORDS = nnnnnn, MASS DELETE = nnnnnn Explanation: This message displays the number of exchange and mass delete records generated for the load. User response: No action is required. |
| BMC397073W | UNABLE TO LOAD COMPRESSION DICTIONARY FOUND IN THE LOG: tableSpaceName.partNum, DSNUM n, RBA: X'rbaValue Explanation: BMC AMI Log Master has encountered incomplete or invalid compression pages when scanning the Db2 log. The rbaValue is the RBA of the last compression page of the invalid dictionary that was encountered in the scan range. User response: No action required. |
| BMC397074 | DUPLICATE VALUES FOUND FOR OPTIONS |option1| AND |option2| IN type SYNTAX Explanation: The product has detected duplicate values between two syntax options/elements in the specified syntax. For example, a comma ' , ' is specified as values for both TERMINATEDBY and DECIMAL POINT in LOAD FORMAT CSV syntax. User response: Edit the element values to resolve the duplication, and resubmit the job. |
| BMC397075 | PROCESSING IS INCOMPLETE - numberOfIncompleteRecords XML UPDATE/DELETE BEFORE IMAGES NOT FOUND IN LOG RANGE Explanation: BMC AMI Log Master is not able to complete an UPDATE or a DELETE of XML transactions. This can occur when the XML delete transactions are not included in the LOGSCAN range. User response: Rerun the LOGSCAN, pushing the TO range out to include the XML delete transactions. |
| BMC397076 | BASE RBA: X'baseRBA', UPDATE TYPE: updateType, RID rowID Explanation: BMC AMI Log Master is not able to complete an UPDATE or a DELETE of XML transactions. This can occur when the XML delete transactions are not included in the LOGSCAN range. User response: Rerun the LOGSCAN, pushing the TO range out to include the XML delete transactions. |
| BMC397077 | XML RECORDS REMAIN IN QUEUE NODE, numberOfRecords RECORDS NOT WRITTEN TO VSAM DATASET Explanation: The end commit for a URID with XML delete transaction is not included in the LOGSCAN range. User response: Rerun the LOGSCAN, pushing the TO range out to include the entire URID. |
| BMC397078 | CANNOT RESOLVE SEPARATE LOAD DSN FOR TABLESPACE dataBaseName.tableSpaceName WITH MULTIPLE TABLES, A SINGLE-TABLE TABLE SPACE IS REQUIRED Explanation: The separate load output data set for the table space listed could not be resolved due to a conflict of multiple tables within the table space. This usage requires a partitioned or universal table space. User response: Correct the problems and submit a modified job to create the outputs that were suppressed due to problems in this run. |
| BMC397079 | COMPRESSION DICTIONARY FOR TABLE SPACE databaseName.tableSpaceName DSNUM n WAS REBUILT AFTER LOG MASTER PROCESSING STARTED. NEW BUILTRBA: X'builtRBA' Explanation: BMC AMI Log Master has detected that the compression dictionary that was loaded from the table space was rebuilt by a Db2 utility during BMC AMI Log Master execution. The compression dictionary is no longer valid for decompressing the records within the log range determined by the SYSCOPY event found at the start of processing. BMC AMI Log Master attempts to reload a valid compression dictionary from other sources (for example, image copies or the BMC AMI Log Master repository). User response: No action is required. In some situations, you might need to provide this information to BMC Support for problem diagnosis. |
| BMC397080 | type COMMAND CREATED COUNTERS: TOTAL STMTS = nnnnnn, BINDS = nnnnnn, FREES = nnnnnn, REBINDS nnnnnn Explanation: The number of command statements generated in a log scan step is detailed. User response: No action is required. |
| BMC397082 | reposDeleteReportText Explanation: This message displays information related to the REPOS DELETE record count. This message is usually followed by one or more BMC097952 messages with the number of qualified records on a repository table for the specified object. For example: User response: No action is required. |
| BMC397083 | action REPOS RECORDS WITH qualifierType LOWER THAN specifiedValue Explanation: The value of the qualifier specification is displayed. REPOS DELETE used the qualifier specification to report or delete qualified repository records based on the specified condition. User response: No action is required. |
Comments
Log in or register to comment.