![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
CHILD % POINTER FOR PAGE % IS INVALID; BRANCH IGNOREDThe specified entry number on the indicated group or primary index page is -1, which is invalid. A completion code of 8 is generated.PAGE % IS GREATER THAN HIGHEST PAGE BACKED UPThe specified page was referenced but it cannot be located in the page header table. This indicates an incomplete backup or archive, or an internal error. A completion code of 8 is generated.DUPLICATE REFERENCE TO PAGE % DETECTEDThe specified page is referenced in more than one place. A completion code of 12 (X'0C') is generated.Stop processing the segment and contact TIBCO Support immediately. Do not continue processing on the tables in error.PAGE % REFERENCED BUT NOT FOUND IN BACKUP FILEThe specified page was referenced but it cannot be located in the page header table. This indicates one of the following:POINTER ERROR ON PAGE %; EXPECTED PREVIOUS %; FOUND %The chain pointers on the page specified do not match the pointers expected by the index level above. Either the index or the data chain is invalid. A completion code of 8 is generated.POINTER ERROR ON PAGE %; EXPECTED NEXT %; FOUND %The chain pointers on the page specified do not match the pointers expected by the index level above. Either the index or the data chain is invalid. A completion code of 8 is generated.The page type indicator on the specified page is not consistent with other pages in the chain. A completion code of 8 is generated.The page type indicator on the specified page is not supported. If the type code specified is in lowercase, an update process (such as SIXBUILD, SIXDELETE, or Table Clear) may have failed to complete properly. A completion code of 8 is generated.PAGE % HEADER CANNOT BE PROCESSED; REJECTEDThe header of the specified page failed to pass a validation test; the page was rejected from the process. A completion code of 8 is generated.INVALID PAGE TYPE %; PAGE % FROM BACKUP FILEThe page type indicator on the specified page is not supported. If the type code specified is in lowercase, an update process (such as SIXBUILD, SIXDELETE, or Table Clear) may have failed to complete properly. A completion code of 8 is generated.The page specified in the message is not referenced by any of the tables on the segment, but the system indicates it is not available. The page header information for this page will be listed in the ORPHAN LIST. A completion code of 4 is generated.% IS REFERENCED BUT INDICATED FREE BY THE SYSTEMThe page specified in the message is referenced by a table, but the system thinks it is available for use. The page will be reported in the ORPHAN LIST. A completion code of 4 is generated.Stop using the segment and contact TIBCO Support immediately. If processing continues on the segment, duplicate page errors may occur.PAGE % IS AN ALLOCATE PAGE WITH ROWS OR SIZEThe page specified in the message has a page type of ALLOCATED, and the rows and entry size fields are not zero. A completion code of 8 is generated.The page specified in the message has a page type that has been tagged for a secondary index build in progress or a table clear in progress. The operation did not complete properly. A completion code of 8 is generated.Do one of the following with the table whose name you will find in the REFLOG (the output reference log file from Batch Pointer Check):
• If a secondary index build was in progress, clear and rebuild the secondary index.
• If a table clear was in progress, try to clear the table again. The table is not currently usable.The Bit Map Page indicated is invalid and is ignored.PAGE % SEQUENCE ERROR OR DUPLICATE PAGE THIS PAGE IGNOREDThis can occur if you run the Pointer Check on a Cumulative Journal which contains multiple copies of changed pages. If this is the case, run Pointer Check against a true backup. Ensure that the segment involved is not corrupted, take a backup and try this program again. If the backup truly reflects the content of your segment:
1. Protect the segment from any further access/updates.PAGES MADE ORPHANS BY MISSING CONTROL PAGE NOT REPORTEDThis warning indicates that at least one control (bit map) page was reported as missing. The pages whose usage is controlled by the missing control page(s), if checked, would be classified (possibly incorrectly) as orphans when the reason they are orphans is due to the fact that the control page(s) are missing. Refer message: S6BBP129E. This message will occur twice: prior to the list of all orphans and at the end of the list of orphans.This warning indicates a serious problem exists in the archive (backup) being checked and under no circumstance should it be used, do not restore. Contact TIBCO Support.The Resident Table Index (RTIX) indicates that a secondary index exists for this table but it was not found.INVALID EXECUTION PARAMETER RECEIVEDThe execution parameter list was invalid. One or more of the parameters are not supported.Processing terminated. Check spelling to make sure the parameter is correct.SPECIFIED SEGMENT NUMBER CONTAINS MORE THAN 5 DIGITSThe value of the segment parameter or command line option is invalid.SPECIFIED SEGMENT NUMBER CONTAINS INVALID NUMERICSThe segment number provided (EXEC-PARM/command option) is invalid.Failed to obtain enough memory for index-level buffers.Make more memory available to the utility and retry.WORK FILE TO RETAIN PAGE IMAGES FAILED TO OPENAs the backup or archive file is processed, entire selected page images are captured. The file used to retain these pages failed to open for output. User abend code 200 is issued.See the job log for additional information.WORK FILE TO RETAIN INDEX POINTERS FAILED TO OPENAs the backup or archive file is processed, indexing information is captured and stored in a variable blocked file. The file used to retain this data failed to open for output. User abend code 200 is issued.See the job log for additional information.INPUT ARCHIVE FILE TYPE DETERMINATION FAILEDThe S6BBRPTR program will accept input of a VSAM or a sequential file. When the program attempted to determine the type of the file supplied, an error was detected. User abend code 200 is issued.See the job log for additional information.BACKUP/ARCHIVE TAPE FAILED TO OPEN FOR INPUTThe backup or archive sequential file (on tape or disk) failed to open for input. User abend code 200 is issued.BACKUP/ARCHIVE VSAM FILE FAILED TO OPEN FOR INPUTThe backup or archive VSAM file failed to open for input. User abend code 200 is issued.An attempt to read the next record in the backup or archive VSAM file resulted in a nonzero return code. User abend code 200 is issued.ERROR DETECTED WHEN FREEING UNUSED SPACEWhen S6BBRPTR processes the backup or archive file page, header information is retained in tables above the line. When a new data set is detected, enough space is obtained to hold the maximum number of page headers. When the data set is complete, unused space is released. The program detected a nonzero return code on the free main. User abend code 200 is issued.See the job log for additional information.SPACE NOT AVAILABLE TO RETAIN PAGE HEADER DATAWhen a change in an Object Service Broker page data set is detected, a block of storage is obtained that is large enough to retain page header information for all the possible pages in the data set. When attempting to retrieve this space, the utility received a nonzero return code. User abend code 200 is issued.Check the storage limits above the line, and contact TIBCO Support.An 80-character record is generated for each Object Service Broker page that is referenced. The file used to retain these records failed to open. User abend code 200 is issued.SPACE NOT AVAILABLE FOR BITMAP PROCESSINGA bitmap is used to indicate which pages are assigned and which ones are free. The GETMAIN to obtain the above-the-line storage for the bitmap table resulted in a nonzero return code. User abend code 200 is issued.ORPHAN CAPTURE LOG FAILED TO OPEN FOR OUTPUTA file is used to retain page information for pages where actual and expected usage differ. This file failed to open for output. User abend code 200 is issued.SPACE NOT AVAILABLE BELOW THE LINE FOR I/O BUFFERThe GETMAIN to obtain storage for I/O buffers resulted in a nonzero return code. The request was approximately 22 KB. User abend code 200 is issued.INDEX STACK OVERFLOW DETECTED; PROCESSING ABORTEDThe indexing levels for the table being processed exceed the limit that the program was designed to handle (i.e., there are too many indexing levels). User abend code 200 is issued.PAGE HEADER TABLE OVERFLOW DETECTED AT PAGE %The page header information is retained in a table that is intended to hold the maximum number of pages in a data set. The program detected a table overflow condition. User abend code 200 is issued.On z/OS, increase the memory available for S6BBRPTR. On Windows or Solaris, use the -p flag for hrnbrptr to specify a larger buffer to hold your Pagestore.When the utility attempted to retrieve a stored page image, either the PAGE file failed to open, or the page could not be found. User abend code 200 is issued.See the job log for additional information and contact TIBCO Support.When the utility attempted to retrieve an index page from the internal index table, the specified page could not be located. User abend code 200 is issued.When the utility attempted to retrieve an index record from the INDEX file, either the file failed to open, or the record could not be found. User abend code 200 is issued.See the job log for additional information, and contact TIBCO Support.While processing the backup or archive file, the utility detected a sequence error at the page specified. User abend code 200 is issued.Sort the backup or archive file and rerun the utility. If the error occurs again, contact TIBCO Support.When the utility processes the backup or archive file, only the pages for one segment are processed. The segment number is defaulted to zero unless a SEGMENT parameter is specified. The backup or archive file did not contain any pages for the segment being processed. User abend code 200 is issued.Ensure that the backup or archive file is for the segment being processed.A sequence error was detected in the index data capture file. User abend code 200 is issued.To increase program efficiency and reduce I/O requirements, captured index information is retrieved from the INDEX file and retained in memory tables when space permits. The process of retrieving the index record resulted in an unexpected table overflow. User abend code 200 is issued.The Header log could not be opened for output. This could be due to permissions or a lack of space, or because the file already exists.At least one default filename cannot be opened, probably because the file already exists.This is a serious error and indicates that under no circumstances should the archive (backup) be used. Each segment extent is preceded by a control page, which contains the usage bitmap, among other things, for the pages in its extent. As the control page is missing, usage information is missing. Therefore, all apparent used pages in the extent would be classified as orphans. This message appears once for each missing control page, even though all pages within the extent are affected, refer to message S6BBP018W.Do not use this archive (backup) for any purpose. Contact TIBCO Support.A system-required table was not found on the MetaStor.A table name has been used more than once.A system table that must have a fixed root location does not have one.Table names on the Resident Table Index (RTIX) must be in ascending sequence.This line identifies a secondary index field whose index has been flagged as invalid. If the table is parameterized, the secondary index of at least one of the table instances is invalid.This is a warning only. The performance of access via the secondary index might be slightly degraded as an extra read of the primary key will be required. As primary indices are normally resident, no extra I/O should be required.DATA PAGE ENTRY SIZE ERROR DETECTED AT xxxxxxxxThe data page entry size indicates the total length of data (rows + lengths) on that page. If the entry size does not match the data rows various unpredictable problems can occur when processing the table to which the data page belongs.DATA PAGE ROW SIZE ERROR DETECTED AT xxxxxxxxData page rows have a maximum and minimum row-length; an invalid length has been found. Invalid row sizes can result in various unpredictable problems when processing the table to which the data page belongs.The segment number specified does not exist in the input file.NEITHER ARCHIVE NOR DBDLIB COULD BE OPENEDYou must provide a valid BACKUP or DBDLIB DD statement.The offline segment cannot be processed.Investigate the cause of the problem, correct it, and then try again.DSN XX BITMAP # PAGES= XXXXXXX LESS THAN ACTUAL PAGES=XXXXXXIn the data set number indicated, the number of pages the control page controls (either in use or not) is less than the number of pages on the data set.No immediate action is required. This discrepancy should disappear the next time the segment is formatted (S6BTLFPS) and restored (S6BTLRPS).DSN XX BITMAP # PAGES = XXXXXXX GREATER THAN ACTUAL PAGES = XXXXXXXXIn the data set number indicated, the number of pages the control page thinks it controls exceeds the actual number of pages on the data set.This error could result in serious problems if the Data Object Broker attempts to use the nonexistent pages beyond the end of the data set. If there is any danger of this, do not use this segment until the problem has been resolved. Contact TIBCO Support.PAGE # XXXXXXXX INCORRECTLY LABELLED XXXXXXXXPage numbers should match the page's location in the data set. The number on this page does not.Do not use the segment until this problem has been resolved. Further use could make a potentially serious problem, worse. Contact TIBCO Support.ACCUMULATED FIELD SIZES NOT EQUAL ROW SIZEThe field sizes within the current row have been totaled and do not equal the specified row size.The following information appears on the next line:
• ACCSZ=Total value of accumulated field sizes (HEX)
• ROWOF=Offset of row relative to page start (HEX)
• FLDOF=Offset of field relative to page start (HEX)A field size encountered is too big for its row size.The following information is provided on the next line:
• ROWOF=Offset of row relative to page start (HEX)
• FLDOF=Offset of field relative to page start (HEX)An invalid field size was encountered.
• ROWOF=Offset of row relative to page start (HEX)
• FLDOF=Offset of field relative to page start (HEX)DATA PAGE VALIDATION ERROR DETECTED AT PAGE XXXXXXXXDuring data page validation, the indicated page was found to be in error. The first such error results in the utility abandoning further validation of the indicated page's data. A more specific message identifying the error can be found preceding this message.DATA PAGE ROW SIZE IS TOO BIG FOR PAGE XXXXXXXXA row size has been encountered on this page that is larger than the specified header-entry size.
• ROWOF=Offset of row relative to page start (HEX)Using the row size and/or field size to traverse the page's data results in encountering an obviously incorrect row size.
• ROWOF=Offset of row relative to page start (HEX)
• FLDOF=Offset of field relative to page start (HEX)A file I/O related error has occurred. Messages that follow give the context for the error.The function and errno information may be used to further diagnose the problem.FILE I/O ERROR, FILE '%', FUNCTION '%', ERRNO % %A file I/O related error has occurred. Messages that follow will give the context for the error.The file, function, and errno information may be used to further diagnose the problem.The file that holds the execution report failed to open for output. This file is intended to be SYSOUT or a similar device. User abend code 201 is issued.The file that holds the error message report failed to open for output. This file is intended to be SYSOUT or a similar device. User abend code 201 is issued.ERROR ON OUTPUT - INDEX TEMPORARY WORK FILEAn error occurred when trying to write to this work file.The error was probably due to either lack of space or an unauthorized work directory. Correct and retry.ERROR ON OUTPUT - PAGE TEMPORARY WORK FILEAn error occurred trying to write to this work file.Probably due to either lack of space or an unauthorized directory. Correct the problem and try again.MISSING DATASET REFERENCE - ARCHIVE INCOMPLETEPointer Check has been run on an incomplete segment backup.Processing terminated. This can occur if backups are taken of individual segment-data sets and those data sets are then concatenated. It can also occur (if tape backup) if all tapes are not mounted. Check the number of data sets that comprise your segment and investigate.Pointer Check has been run on an incomplete segment backup.Processing terminated. This can occur if backups are taken of individual segment-data sets and those data sets are then concatenated. It can also occur (if tape backup) if all tapes are not mounted. Check the number of data sets that comprise your segment and investigate.The archive (input file) appears to be incomplete.This utility cannot process archives which have missing page zeros.CANNOT PROCESS ARCHIVE - JOB ABORTEDThe file cannot be processed as an archive. Something about the file leads the utility to believe that the file is not a legal archive.Refer to the associated error message for more detailed information.An illegal page number was read from the archive. This page number is higher than the highest legal page number on a segment file.This error indicates either Pagestore corruption or that the file being processed is not an archive. If your investigation does not reveal the cause of the error, contact TIBCO Support. Make sure that the Pagestore file that appears to be corrupted is not used until the reason for the problem is discovered.ILLEGAL SEGMENT NUMBER - IGNORED SEG# XXXX PAGE#:XXXXXXXXA page was encountered containing an invalid segment number.Check that the data set or file used as input to the utility is valid. If it is, contact TIBCO Support.An error was discovered when processing the dbdef file.The dbdef must be properly formatted as per the documentation. The error must be corrected before the utility can process the requested segment.The dbdef file specified could not be opened.Make the segment file accessible and try again. This problem may be caused by the segment file being active. The segment must be offline and if the target segment is the MetaStor, the Data Object Broker must be shut down.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |