PROVE IT !!If you know it then PROVE IT !! Skill Proficiency Test

Teradata Error

Error No : 2147 Internal error detected while comparing two strings.

Explanation: During the comparison of two strings,an internal error was detected by the float subsystem.

Generated By: Float subsystem.

For Whom: Field Engineer.

Remedy: Contact your Support Representative.

Error No : 2148 Internal error detected while copying a string.

Explanation: While making a copy of a string, an internal error was detected by the float subsystem.

Generated By: Float subsystem.

For Whom: Field Engineer.

Remedy: Contact your Support Representative.

Error No : 2149 Internal error detected while comparing two strings.

Explanation: During the comparison of two strings, an internal error was detected by the float subsystem.

Generated By: Float subsystem.

For Whom: Field Engineer.

Remedy: Contact your Support Representative.

Error No : 2504 Bad Parameter passed to file system.

Explanation: An invalid parameter was passed to a file system routine.

Generated By: JnlLogRd, RedDos, RedSvc, blkReplace, RowBPeek, RowUpdIns, RowReplace, RowRIDL, RowRLHas, and TabRBlks

For Whom: Site support representative.

Notes: This error results when a sanity check of parameters passed to a file system routine indicates one or more invalid parameters. This can be caused by internal software problems or data corruption.

Remedy: Contact your System Representative.

Error No : 2507 Out of spool space on disk.

Explanation: Insufficient disk space was available on the AMP to allow an operation to complete. Context state is CtxNull and access to the CI and DB is dropped.

Generated By: File System

For Whom: End User

Notes: This indicates that a request has exceeded the physical storage limits imposed by a given configuration without exceeding the logical limits imposed by PERM or SPOOL space allocations for a given database.

Remedy: If out of SPOOL space, resubmit the request, preferably when there is less activity on the system. If out of PERM space, reduce permanent space usage by archiving journals or user tables where possible.

Error No : 2509 AMP internal error (see traceback)

Explanation: One of the AMP software’s many sanity checks has failed, indicating an internal inconsistency in data or processing state. This error causes a system restart.

Generated By: AMP software.

For Whom: Site support representative.

Notes: One of many fatal error conditions detected by sanity checks in AMP software could have caused this error message. Because this error is non-specific, it is necessary to qualify any Error No : 2509 error with the associated traceback.

Remedy: Save the crashdump for offloading. Have all traceback information ready. Then contact your Support Representative.

Error No : 2511 Bad locator parameter.

Explanation: A bad locator is specified in a parameter.

Generated By: RowInser.

For Whom: Site support representative.

Notes: This error is strictly for file system internal checking. It may be retired after system integration to improve performance.

Remedy: Contact your System Representative.

Error No : 2513 A data row is too long.

Explanation: The length of the row specified by the caller is greater than SysMaxRow, the maximum length allowed for any row in the database. The row could be either one specified directly by the user, or an intermediate results row required for query processing.

Generated By: File System

For Whom: End User Field Engineer

Notes: This indicates that a row is too long. Query processing often requires intermediate results rows that are longer than the data being selected. For example, ORDER BY and GROUP BY columns require sort keys that increase intermediate results row size.

Remedy: Reduce the size of row required. Fewer or smaller columns, or less complex queries may solve the problem. Otherwise, contact support personnel.

Error No : 2514 Operation not allowed: %DBID.%FSTR is being used to log ARC selected partition restore errors.

Explanation: This error occurs when a user issues a request to access the error table that is actively being used to log errors during an ARC restore of selected partitions to a PPI base table. Only read or drop access is permitted.

Generated By: AMP Steps.

For Whom: End User.

Notes: The table does exist with limited access rights.

Remedy: Wait until the ARC restore is finished, then resubmit the request.

Error No : 2516 Error in calculating/updating disk space.

Explanation: Reported when the system encounter errors while updating disk space in Dbase and DataBaseSpace table.

Generated By: USVCalDs.

For Whom: Site support representative.

Notes: Software error.

Remedy: Contact your System Representative.

Error No : 2517 Empty DataBaseSpace Table Header.

Explanation: Reported when there is no DataBaseSpace table header.

Generated By: USVUDRcv.

For Whom: Site support representative.

Notes: Software error.

Remedy: Contact your System Representative.

Error No : 2520 A variable field offset exceeds the next variable offset or the row length.

Explanation: This message is displayed if a variable field offset in the row header is greater or equal to the next variable field offset or the row length.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 25Error No : 25 Fatal read error encountered during Reconfig.

Explanation: An unrecoverable disk read error is encountered during Reconfig. The bad data block cannot be rebuilt. Reconfig is terminated due to the error.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Manual intervention is required to rebuild the bad block. Contact your Support Representative.

Error No : 2530 End Transaction Error after space accounting.

Explanation: Error encountered when the system try to remove the transaction from the TIP and release associated Locks.

Generated By: SSSMain.

For Whom: Site support representative.

Remedy: Contact your System Representative.

Error No : 2531 No task found for task ID/Transaction ID.

Explanation: No task was found under the transaction ID that matched the task ID that was passed to LokRTTsk.

Generated By: LokRTTsk

For Whom: Site support representative.

Remedy: Contact your System Representative.

Error No : 2532 Unrecoverable read error detected. Retry.

Explanation: A disk read error is encountered. The bad data block cannot be rebuilt with the Teradata system on-line. The AMP which detects the error will remain offline.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Manual intervention (table rebuild) or a restart may fix the problem.

Error No : 2533 Shut down DBS and rebuild the disk.

Explanation: A disk read error is encountered. The bad data block cannot be rebuilt with the processor online. The AMP which detects the error will remain offline.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Shutdown the DBS, rebuild the bad disk and then restart the Teradata DBS.

Error No : 2534 System recovering from disk read error on spool file.

Explanation: A disk read error is encountered. The bad data block was in a spool file and will automatically recover when the system restarts.

Generated By: RbkCtrl.

For Whom: Operator.

Remedy: None. The Teradata DBS will restart itself and automatically recover from the disk read error.

Error No : 2536 Data lost while recovering from a read error.

Explanation: A disk read error occurred in a table which:

1) has no fallback copy, or

2) is an abended fastload table, or

3) is an abended restore table, or

4) is an invalid index table, or

5) is a permanent journal table, or

6) has been recovery aborted.

7) has been rebuild aborted.

8) has been reconfig aborted.

9) has fallback copy with amp down in the cluster.

10) is one of the following mload work subtables: – private permanent journal. – local checkpoint – foreign checkpoint – bit map – data was corrupted in other amp in the cluster such as missing table header or table is being rebuilt.

11) is mload dump work subtable. Some data was lost, and the Teradata DBS cannot or will not rebuild it.

Generated By: U2URBK/RbkRcvy.

For Whom: Operator. DBA. End User.

Notes: Table header will be updated to indicate rebuild in process if rebuild failed.

Remedy:

  • If the table has no fallback copy, you may recover the table from an archive.
  • If the table is in fastload state, you may delete all the associated fastload tables and resubmit the fastload job. If the table is in restore state, you may recover the table from an archive.
  • If the table is an invalid index table, you may drop the index and recreate the index.
  • If the table has been recovery aborted, you may drop it or recover the data from an archive.
  • If the table has been rebuild aborted, you should try to rebuild the whole table via Rebuild utility.
  • If the table has been reconfig aborted, you may drop it or recover the data from an archive.
  • If the table is a permanent journal table, Contact your Support Representative.
  • If there is an amp down in the cluster, we should try to bring the down amp back to configuration and attempt to rebuild the table again. If rebuild fails after down amp rejoins the configuration, it usually means the table has been rebuilt aborted in more then one amp in the cluster. In order to recover the data, you may need to do restore and rollforward.
  • If the table is one of those mload work subtables which can not be recovered due to no fallback. In order to recover the target table prior mload take place, restore (and rollforward) may require.
  • If the rebuild table was corrupted in other amp in the rebuild cluster, in order to recover the target table prior mload take place, restore and rollforward may require.
  • If the table is mload dump work subtable, subtable will be deleted, however table header will NOT be marked as rebuild in process.

Error No : 2538 A disk read error occurred in the tables area.

Explanation: A disk read error occurred in DBS tables DCR5858-cy2-01 area of the disk. An attempt will be made to recover the data. If recovery is not possible, either the system will crash or the data table will remain locked. An event will be logged that indicates what action the Teradata DBS will take.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: This is an information only message. The next event logged will inform the user of the action taken as a result of the error.

Error No : 2542 Requested rebuild is already running.

Explanation: This is an internal status error created when a restartable rebuild is attempted on an AMP which is currently running a rebuild.

Generated By: RbdRstar

For Whom: Operator.

Remedy: Allow the first rebuild to finish.

Error No : 2543 Operation not allowed: %DBID.%TVMID is being Rebuilt.

Explanation: This error occurs only when a user issues a request for a table that is being Rebuilt.

Generated By: AMP Steps.

For Whom: End User.

Notes: The table does exist, but it is not in a form in which it may be accessed.

Remedy: Wait until the Table Rebuild is finished, then resubmit the request.

Error No : 2544 Operation not allowed: %DBID.%TVMID had an error when Rebuilt.

Explanation: This error occurs only when a user issues a request for a table that was Rebuilt, and the

rebuild did not successfully complete.

Generated By: AMP Steps.

For Whom: End User.

Notes: The table does exist, but it is not in a form in which it may be accessed.

Remedy: Either resubmit the request after the table has been restored or drop the table.

Error No : 2545 Operation not allowed: %DBID.%TVMID was Rebuilt without fallback.

Explanation: This error occurs only when a user issues a request for a table that was Rebuilt, and the

table was not fallback protected.

Generated By: AMP Steps.

For Whom: End User.

Notes: The table does exist, but their is no data in the table on the rebuilt AMP.

Remedy: Either resubmit the request after the table has been restored, drop the table, or rebuild the table without the LOCK NO FALLBACK TABLES option.

Error No : 2549 A read error occurred in a permanent journal table.

Explanation: A disk read error occurred in a permanent journal table. The bad data block cannot be rebuilt automatically by the Teradata DBS. Manual intervention is required. AMP which detected error will remain offline.

Generated By: RbkCtrl.

For Whom: Operator. DBA. Site support representative.

Remedy: The permanent journal table must be rebuilt. If any user table which journals to this permanent journal table is not defined as dual image, then there will be loss of data in the permanent journal table during the table rebuild. Contact your Support Representative.

Error No : 2550 MLoad error: bad internal status – %VSTR

Explanation: This error occurs when an internal consistency check fails. The possible inconsistency are:

1)Session status not in order.

2) MLoad phase status not in order.

3) MLoad state status not in order.

4) Target table is in MLoad state but WorkTable is missing.

Generated By: AMP Steps.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2551 MLoad has already been terminated.

Explanation: The MLoad operation on the DBS side has already been terminated. Session is no longer exists. This problem possible cause is the host MLoad Utility is ignoring the error returned from DBS and still send down data parcels.

Generated By: AMP MLoad Processing.

For Whom: Host MLoad Utility. Customer Engineer

Notes: The Utility should terminate if there is any error returned while it is sending data parcels to the DBS.

Remedy: Cancel the MLoad job on the Host. Correct the Utility if it is ignoring errors.

Contact your Support Representative, if the user is not at fault.

Error No : 2552 BEGIN Mload executed without MLoad Init.

Explanation: This error occurs when a message is processed to start a MLoad without the necessary preparation for the operation.

Generated By: STPEBE

For Whom: End User.

Notes: This error means either that the user is incorrectly trying to use MLoad, or that there has been an error in the execution of the MLoad utility.

Remedy: If the user is not at fault, contact your Support Representative

 

Error No : 2553 Exceed maximum (100) DML Step Limit.

Explanation: DBS received too many DML steps for one MLoad job.

Generated By: AMP MLoad Processing.

For Whom: End User.

Notes: One MLoad operation can only handle up to 100 DML steps.

Remedy: Reduce DML statements in your MLoad job.

Error No : 2554 Inconsistent situation occurs in restart MLoad – %VSTR

Explanation: Inconsistency encountered in DBS during restarting a MLoad job. The possible inconsistent situations are:

1) The Base work table id maintained in table headers of all target tables are not the same.

2) The target tables given in the step are not the same as the ones saved in the table headers.

3) The existence of field 4 in table headers of all the MLoad tables are not consistent.

4) Table already existed when attempting to create default work (WT_) or error (ET_, UV_) tables in Multiload.

Generated By: STPEBE

For Whom: Site support representative.

Notes: All target tables should share one base work table within a MLoad job. All Mload related tables should have field 4 in their table headers after MLoad steps are processed.

Remedy: Contact your Support Representative.

Error No : 2555 Table does not belong to the MLoad job.

Explanation: The table does not exist in the given MLoad entry of the load information segment.

Generated By: STPEED

For Whom: MLoad Host Utility.

Notes: BEGIN MLoad should already define all the MLoad tables in the Load information segment before MLOAD step is processed.

Remedy: Contact your Support Representative.

Error No : 2556 Duplicate match tag found.

Explanation: Duplicate match tag found in MLoad work tables.

Generated By: STPEDM

For Whom: MLoad Host Utility.

Notes: Each DML step should provide unique match tag, the utility should ensure the uniqueness of each match tag.

Remedy: Cancel the MLoad job on the host. Correct the error to ensure match tag uniqueness.

Error No : 2557 Too many target tables in the MLoad job.

Explanation: DBS received too many MLOAD steps.

Generated By: AMP MLoad Processing.

For Whom: Mload host utility.

Notes: One MLoad operation can only handle 5 target tables. The Utility should terminate and report error if more than 5 target tables are used.

Remedy: Cancel the MLoad job on the Host. Correct the Utility to include the limit check.

Error No : 2558 The Mload step was sent more than once.

Explanation: DBS received the same MLoad step.

Generated By: StpEED

For Whom: MLoad host utility.

Notes: If DBS receives the same MLOAD step more than once, this must be a programming error.

Remedy: Contact your Support Representative.

Error No : 2559 MLoad not allowed: %DBID.%FSTR is a permanent journal table.

Explanation: This error occurs only when a user issues a request for a table that is a permanent journal table.

Generated By: STPEBE

For Whom: End User.

Notes: The table does exist, but it is not in a form in which it can be edited by user.

Remedy: Remove the journal table from your,  MLOAD job and resubmit the request.

Error No : 2560 Mload table has not been initialized for MLoad.

Explanation: This error normally means field 4 is missing in the table header of the MLoad related table.

Generated By: AMP MLoad Steps

For Whom: Site support representative

Notes: All the MLoad related tables must have field 4 defined in their table headers.

Remedy: Contact your Support Representative.

Error No : 2561 MLoad related table %TVMID has bad usage field in table header

Explanation: The usage field in the table header does not match with the real usage of the table.

Generated By: AMP MLoad Steps For Whom: Site support representative

Notes: The usage field in field 4 of table header of target table and error tables should be Target. The usage field in field 4 of table header of work tables should be Worktable.

Remedy: Contact your Support Representative.

Error No : 2562 MLoad not allowed: table %TVMID has been rebuilt.

Explanation: While the table is being edited, table was rebuilt and failed.

Generated By: AMP MLoad step.

For Whom: End User.

Notes: Some data is lost, and cannot be recovered.

Remedy: Drop this table and its associated tables, and resubmit the MLoad job.

Error No : 2563 MLoad not allowed: DBS had been reconfigured.

Explanation: The Teradata DBS had been reconfigured before the table completed the editing.

Generated By: AMP MLoad step.

For Whom: End User.

Notes: Partial data was edited and the Teradata DBS was reconfigured. The data in the Teradata DBS was invalidated.

Remedy: Drop this table and its associated tables, recreate them, then resubmit the request.

Error No : 2565 The operation does not honor Single Processor Recovery mode

Explanation: The operation that caused the system reset does not allow Single Processor Recovery mode. The operation is most likely RECONFIG.

Generated By: ACTSPF.

For Whom: End User.

Remedy: None.

Error No : 2566 Processor nnnn failed to respond

Explanation: Processor is hung during Single Processor

Generated By: SSSSPF.

For Whom: End User.

Remedy: None.

Error No : 2567 The system has no PE or PEs running

Explanation: There must be at least one PE or PE available before Single Processor Recovery can be performed.

Generated By: SSSSPF.

For Whom: End User.

Remedy: None.

Error No : 2570 Operation not allowed: %DBID.%FSTR is a MLoad worktable.

Explanation: This error occurs only when a user issues a request for a MLoad worktable.

Generated By: AMP Steps.

For Whom: End User.

Notes: The table does exist, but it is a MLoad worktable which may not be accessed for select or update.

Remedy: None.

Error No : 2571 Multiload task still running against table %TVMID

Explanation: An attempt is made to release MLoad target table before the initial MLoad termination is done.

Generated By: STPERE

For Whom: Site support representative

Notes: The MLoad entry should be removed from the load control segment before STPERE is called.

Remedy: Contact your Support Representative.

Error No : 2572 MLoad table %TVMID can not be released.

Explanation: An attempt is made to release a MLoad target table which has entered apply phase already.

Generated By: STPERE

For Whom: Site support representative

Notes: RELEASE MLOAD statement will be aborted if any table in the list has passed the acquisition phase.

Remedy: You may recover the tables via restore or permanent journal.

Error No : 2573 Invalid match tag found.

Explanation: The match tag of a data parcel does not match those in the MLoad work tables.

Generated By: StpESD

For Whom: Host MLoad Utilities

Notes: This data parcel will be inserted into the MLoad error table.

Remedy: Contact your Support Representative.

Error No : 2574 Operation not allowed: %DBID.%FSTR is being MLoaded.

Explanation: This error occurs only when a user issues a request for a table that is being MLoaded.

Generated By: AMP Steps.

For Whom: End User.

Notes: The table does exist, but it is not in a form in which it may be accessed.

Remedy: Wait until the MLoad is finished, then resubmit the request.

Error No : 2575 Timed out waiting for lock on %DBID.%TVMID

Explanation: This error occurs when a transaction is unable to obtain a lock on a database object (table, view or macro) within a reasonable time. The time allowed for the lock depends on the type of transaction being performed.

Generated By: AMP Steps.

For Whom: End User.

Remedy: Look for sources of lock contention on the indicated object and remove them if possible; then resubmit the request that generated the error.

Error No : 2576 Number of Field IDs exceeds SysMaxFields

Explanation: This error occurs when an attempt is made to write a Field ID/Field Name List Row in a

worktable, when the number of FIDs exceeds the system- defined maximum of ’SysMaxFields’.

Generated By: Mload Begin Edit Delete Step.

For Whom: Site support representative.

Remedy: A Software error may have occurred during generation of the parameters passed to ’EDTCRFID’, which generates the worktable row.

Error No : 2578 Shutdown DBS and rebuild the DOWN amp in the cluster.

Explanation: When this error occurs, there must be a down/catchup amp in the same cluster of the amp which detects read error. The read error is encountered on table which contains data for recovering the down/catchup amp.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Rebuild the DOWN amp via table rebuild utility.

Error No : 2579 System recovering from disk read error.

Explanation: A disk read error is encountered. The bad data block cannot be rebuilt automatically. The table must be rebuilt manually.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Manual intervention (table rebuild).

Error No : 2580 MLoad not active on table %TVMID.

Explanation: An attempt to release MLoad on a table not MLoading.

Generated By: STPERE

For Whom: User.

Remedy: This is an information only message.

Error No : 2581 Processor reset via software reset simulation tool

Explanation: This is a request from the testing tool to generate a software error.

Generated By: SPFTsk

For Whom: User.

Note: This is to simulate a software error. It is for internal use only.

Error No : 2582 Not an operational configuration for MLoad

Explanation: An AMP has gone down in a cluster which already has another AMP marked as logically

down for the apply phase of a given MultiLoad job. Although the configuration is still operational at the system level, the MLoad restart logic in the AMPs considers it non-operational for apply phase processing in the current job.

Generated By: AMP MLoad steps

For Whom: User. Site support representative.

Notes: In addition to the user error returned to the MLoad host utility, this error will also be logged to the DBS console and the error log. Every effort should be made to preserve the data on the

down AMP, since it is not possible to rebuild an MLoad target table during the apply phase. Once this phase has been entered, the MLoad must run to completion or the target tables will have to be restored from archived copies.

Only as a last resort, therefore, should the down

AMP repair include an HDA replacement with its consequent data loss.

Remedy: Bring the down AMP back online with all its disk data intact, if possible, and restart the MLoad job. For problem analysis of the down AMP, consult the errors logged at the time the AMP went down, not the MLoad error described here. For further help, contact your Support Representative.

Error No : 2583 %VSTR is missing for %DBID.%TVMID during MLoad restart.

Explanation: WorkTable or Error table is missing during restart.

Generated By: STPEBE

For Whom: User.

Remedy: Drop the existing worktable and error tables of the MLoad job. If the error is diagnosed before the end of the acquisition phase, issue the RELEASE MLOAD statement on the MLoad target tables. Otherwise, the target tables should be dropped. Finally, restart the MLoad job.

Error No : 2585 An I/O error on an MLOAD table caused a crash.

Explanation: An I/O error has occurred on an MLOAD table and it was necessary to crash.

Generated By: RBKRcvy.

For Whom: End User.

Remedy: Try running MLOAD again.

Error No : 2586 AMP has been marked as an MLOAD nonparticipant

Explanation: An AMP has been marked as an MLOAD nonparticipant. This error is only used internally.

Generated By: RBKRcvy.

For Whom: U2URbk.

Remedy: None.

Error No : 2587 Segment overflow — FastExport request is too complex to process.

Explanation: The FastExport job requires too many segments ( 100) to redistribute data when data is to be sorted.

Generated By: StpExpVR

For Whom: End User

Remedy: Simplify the request or avoid sorting the data. If neither approach succeeds, contact your Support Representative.

Error No : 2588 Invalid block number in the FastExport Initiate request.

Explanation: The block number defined in the FastExport initiate request was outside the range of the number of blocks in the answer set.

Generated By: LCTExpSt

For Whom: End user

Remedy: Modify the request block number and resubmit the initiate request

.

Error No : 2589 Request block is not found.

Explanation: The file system does not find the request block in the spool file. Either we have a software bug or the spool file has been deleted by the host (i.e., an End Request has been issued by the host).

Generated By: LCTExpSt

For Whom: End user

Remedy: If the spool file was not explicitly deleted by the host, then contact your Support Representative.

Error No : 2590 Buffer size is too small for the response.

Explanation: The buffer size specified in the FastExport Initiate request was smaller than that specified in the Select request.

Generated By: LCTExpSt

For Whom: End user

Remedy: Modify the buffer size and resubmit the initiate request.
Error No : 2591 There is no response data for the specified statement in the FastExport request.

Explanation: There is no response data in the DBS for the specified statement number in an FastExport initiate request. Either the SQL Select request results no response data or the statement number is incorrect.

Generated By: LCTExpSt

For Whom: End user

Remedy: Correct the statment number and resubmit the initiate request.

Error No : 2592 Select request has not been processed.

Explanation: Either the host has not sent down the SQL Select request or the DBS is still processing the first Select statement in the SQL request.

Generated By: LCTExpSt

For Whom: End user

Remedy: Submit the SQL Select request or wait until the Select completes.

Error No : 2593 The Select request is not completed yet.

Explanation: The SQL Select request is currently in process. The user must wait until the request completed to submit the FastExport Initiate request.

Generated By: LCTExpSt

For Whom: End user

Remedy: Wait until the Select request is successfully completed then submit the initiate request.

 

Error No : 2594 One of the FastExport session has been logged off

Explanation: The host has logged off one of the FastExport session which causes the response data inaccessible. If the log off occurs during the processing of SQL Select then the Select should have been aborted. On the other hand, if the log off occurs after the completion of SQL Select then the answer set is inaccessible by any remaining FastExport sessions. In this case, however, the host is still responsible to send down an End Request to delete the answer set spool file.

Generated By: LCTExpSt

For Whom: End user

Remedy: Delete the answer set spool file if necessary and then resubmit the SQL Select.

 

Error No : 2595 The FastExport select request has been aborted.

Explanation: The current Select request has been aborted.

Generated By: LCTExpSt

For Whom: End user

Remedy: Examine the reason of the abort, do whatever necessary to correct the problem and then resubmit the Select request.

Error No : 2596 Invalid parcel sequences in the FastExport Initiate request.

Explanation: The FastExport Initiate request from the host has an invalid parcel flavor. The request should consists of PclFMReq/PclReq and PclResp where the request parcel should conatin two 4-byte integer indicating the desired statement number and block number.

Generated By: LCTExpSt

For Whom: End user

Remedy: Contact your Support Representative.

 

Error No : 2597 Table Rebuild procedures required to recover AMP.

Explanation: A disk read error was encountered while executing a recovery function. The bad data block

cannot be rebuilt with the processor on-line. The AMP which detects the error will remain offline.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Run Table Rebuild to recover the failing table and then restart the Teradata DBS.

 

Error No : 2598 Discrepancy between CI DBD and data block.

Explanation: Following a read of a data block, the file system discovered that the information in the header portion of the data block itself did not match information in the Data Block Descriptor in the Cylinder Index. This could be due to an undetected I/O error on a previous write, an undetected I/O error on the current read, an undetected memory error, or a software error. The logical location of the block on disk and whether the table was a spool table or permanent table is recorded in additional text printed with this message.

Generated By: Miscellaneous file system read routines.

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2599 One of the Foreign Key columns has a Null value.

Explanation: This is not really an error message. It is used by the DBS code to determine that the Foreign Key value has a null value.

Generated By: SutGnIR1.

For Whom: Whoever invokes SutGnIR1.

Remedy: None.

Error No : 2600 Stack overflow — expression too complicated.

Explanation: This error occurs because an expression employs too many levels of parentheses or is too complex. The maximum stack depth is eight.

Generated By: The interpretative expression processor.

For Whom: End User.

Remedy: Resubmit the request using an expression that does not nest as many levels as the expression that caused the error.

Error No : 2601 Stack overflow calculating expression involving %TVMID.%FLDID.

Explanation: This error occurs because an expression employs too many stack push operations. The maximum stack depth is eight. The tablename and columnname identified are those of the last fields accessed in forming the stack entries.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Resubmit the request using an expression that does not nest as many levels as the expression that caused the error.

Error No : 2602 Internal error — Stack Underflow.

Explanation: If this error occurs while processing pseudo code, it indicates that (a) something has caused the stack to become empty, and that (b) some instruction expected to find some data on the stack.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

Error No : 2603 Bad argument for SQRT function.

Explanation: SQRT called with negative or nonnumeric argument.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Change query to avoid bad call to SQRT.

Error No : 2604 Bad argument involving %TVMID.%FLDID for SQRT function.

Explanation: SQRT called with negative or nonnumeric argument. The indicated field is a part of the argument.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Change query to avoid bad call to SQRT.

Error No : 2605 Bad argument for LOG function.

Explanation: LOG called with zero, negative, or nonnumeric argument.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: CHange query to avoid bad call to LOG.

Error No : 2606 Bad argument involving %TVMID.%FLDID for LOG function.

Explanation: LOG called with a zero, negative, or non-numeric argument. The indicated field is a part of the argument.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Change query to avoid bad call to LOG.

Error No : 2607 Bad argument for LN function.

Explanation: LN called with a zero, negative, or nonnumeric argument.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Change query to avoid bad call to LN.

Error No : 2608 Bad argument involving %TVMID.%FLDID for LN function

Explanation: LN called with a zero, negative, or nonnumeric argument. The indicated field is a part of the argument.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Change query to avoid bad call to LN.

Error No : 2609 Internal error: improper field reference.

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs if there is either no output row to place the field in or no field already open.

Remedy: Contact your Support Representative.

Error No : 2610 Internal error: field maintenance error

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs if an Append Op is executed without a field to append to.

Remedy: Contact your Support Representative.

Error No : 2611 Internal error: illegal comparison operation

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs if the pseudo machine is told to perform a comparison operation with mismatched types (for example, CHAR with BYTE).

Remedy: Contact your Support Representative.

Error No : 2612 Internal error: illegal opcode detected.

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs if pseudo code contains an Op Code that is not recognized.

Remedy: Contact your Support Representative.

Error No : 2613 Internal error: illegal datatype conversion

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs if the pseudo machine is asked to perform an illegal type conversion during a pop operation.

Remedy: Contact your Support Representative.

Error No : 2614 Precision loss during expression evaluation.

Explanation: This error indicates that an expression has produced a result that is too small to be expressed in the requested data type.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Resubmit the request after changing the type specified to accommodate the result. (For example, convert DECIMAL to FLOAT.)

Error No : 2615 Precision loss calculating expression involving %TVMID.%FLDID.

Explanation: This error indicates that an expression has produced a result that is too small to be expressed in the requested data type. The indicated field is a part of the expression.

Generated By: The interpretative instruction processor.

For Whom: End User.

Notes: This error occurs for the same reason as ErrAMPEPresisn. However, in this case more information exists about the calculation that produced the precision loss error.

Remedy: Resubmit the request after changing the type specified to accommodate the result. (For example, convert DECIMAL to FLOAT.)

Error No : 2616 Numeric overflow occurred during computation.

Explanation: This error indicates that an expression has produced a result that is too large to be expressed in the requested data type. (For example, a result of 100,000.00 and a data type of DECIMAL(5,2).)

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Resubmit the request after changing the type specified to accommodate the result.

Error No : 2617 Overflow occurred computing an expression involving %TVMID.%FLDID

Explanation: This error indicates that an expression has produced a result that is too large to be expressed in the requested data type. The indicated field is part of the expression.

Generated By: The interpretative instruction processor.

For Whom: End User.

Notes: This error occurs for the same reason as ErrAMPEOverflo. However, in this case more information exists about the calculation that produced the precision loss error.

Remedy: Resubmit the request after changing the type specified to accommodate the result.

 

Error No : 2618 Invalid calculation: division by zero.

Explanation: This error indicates that an expression has attempted to divide by zero.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Resubmit the request after removing the division by zero.

Error No : 2619 Division by zero in an expression involving %TVMID.%FLDID.

Explanation: This error indicates that an expression has attempted to divide by zero. The indicated field is part of the expression being calculated.

Generated By: The interpretative instruction processor.

For Whom: End User.

Notes: This error occurs for the same reason as ErrAMPEZeroDiv. However, in this case more information exists about the calculation that produced the error.

Remedy: Resubmit the request after removing the division by zero.

 

Error No : 2620 The format or data contains a bad character.

Explanation: This error indicates that the user has submitted a numeric-to-character conversion with an illegal format, or that, in a character-to-numeric conversion, the data or the format contains a bad character.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Verify the format used. If it is legal, then an illegal character is present in the data being converted from character to numeric.

Error No : 26Error No : 21 Bad character in format or data of %TVMID.%FLDID.

Explanation: This error indicates that the user has submitted a numeric-to-character conversion with an illegal format, or that, in a character-to-numeric conversion, the data or the format contains a bad character.

Generated By: The interpretative instruction processor.

For Whom: End User.

Notes: This error occurs for the same reason as message Error No : 2620, above. However, in this case more information exists about the calculation that produced the error.

Remedy: Verify the format used. If it is legal, then an illegal character is present in the data being converted from character to numeric.

 

Error No : 2622 Bad argument for ** operator.

Explanation: An argument is non-numeric or an attempt has been made to evaluate 0**0 or 0**(negative argument). Results are undefined for 0**0 and 0**(negative value).

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Change query to avoid bad use of **.

Error No : 2623 Bad argument involving %TVMID.%FLDID for ** operator.

Explanation: An argument is non-numeric or an attempt has been made to evaluate 0**0 or 0**(negative argument). Results are undefined for 0**0 and 0**(negative value). The indicated field is a field in the expression.

Generated By: The interpretative instruction processor.

For Whom: End User.

Remedy: Change query to avoid bad use or **.

Error No : 2624 Internal error: no format given for editing

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs either on a DeEditOp or a EditOp, when the format given happens to be a null string.

Remedy: Contact your Support Representative.

Error No : 26Error No : 25 Internal error: nested open parcel operations

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: Two open parcel ops occurred without a close parcel op between them.

Remedy: Contact your Support Representative.

Error No : 26Error No : 26 Internal error: parcel closed prior to open

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: The Pseudo Machine was instructed to terminate a parcel that was not opened.

Remedy: Contact your Support Representative.

Error No : 2627 Internal error: invalid operand for UpCaseOp

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs if, for instance, an UpCaseOp is performed on YnetAsc or YnetDesc format data.

Remedy: Contact your Support Representative.

Error No : 2628 Internal error: creating fields out of order.

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: For example, the user was told to put field 1009 before field 1007, but did not.

Remedy: Contact your Support Representative.

 

Error No : 2629 Internal error: bad data type for operation.

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs when an operation is requested that does not make sense (for example, comparing numbers to characters, adding character or byte strings, etc.).

Remedy: Contact your Support Representative.

Error No : 2630 Internal error: null lower set bound

Explanation: This error indicates that an illegal sequence of Op Codes has been executed.

Generated By: The interpretative instruction processor.

For Whom: Site support representative.

Notes: This error occurs when a Set Check operation is performed and the field checked first is Null or not there.

Remedy: Contact your Support Representative.

 

Error No : 2631 Transaction ABORTed due to %VSTR.

Explanation: This error indicates that:

(1) an excessive number of transactions were queued waiting for locks, and the user’s request would have blocked on the lock queue, or

(2) the request conflicted with another request, causing a deadlock, or

(3) a software problem (for example, a lost message) occurred, causing the request to "time out".

Generated By: AMP Software.

For Whom: End User.

Remedy: Resubmit the transaction.

 

Error No : 2632 All AMPs own sessions for this Fast/Multi Load or FastExport.

Explanation: This error occurs when all AMPs have a session assigned to them for the ongoing FastLoad, MLoad or FastExport.

Generated By: AMP Software.

For Whom: Internal Message Only.

Notes: This error exists only to instruct the utility program to stop attempting to log sessions onto the Teradata DBS.

Remedy: None possible.

Error No : 2633 Too many load/unload tasks running: try again later

Explanation: This error occurs when more than a certain number (currently 5) of Fast/Multi Loads, FastExport are simultaneously active.

Generated By: AMP Software.

For Whom: End User.

Notes: This error exists because of the need to set a limit on the number of concurrent Fast/Multi load , FastExport

operations. Check var/adm/streams for more information.

Remedy: For fastload resubmit request later. Multiload automatically resubmits when it gets this error.

 

Error No : 2634 Existing ERROR table(s) or Incorrect use of %TVMID in Fast Load operation.

Explanation: This error occurs if the table/error

table(s) specified either;

(a) existed before the start of the Fast Load, or

(b) did not indicate that it was involved in this specific Fast Load.

Generated By: AMP Software.

For Whom: End User.

Notes: This error means either that the user has referenced existing tables for the ERRORFILES in a Fast Load that is not restarting, or that incorrect tables were referenced in a restart of a Fast Load.

Remedy: If this is not a restart of a previous Fast Load, delete the referenced error files. If this is a restart, correct the Begin Loading Statement so that the error files are those specified for the original Fast Load.

 

Error No : 2635 Error tables are invalid OR %TVMID is in an invalid state for Load – %VSTR

Explanation: This error occurs if the table specified for the Fast/Multi Load is already being used by some other process (for example, a Dump/Restore or another Fast/Multi Load). This error could also occur if different error tables are specified for a table whose load job is not completed successfully.

Generated By: AMP Software.

For Whom: End User.

Notes: This error means that the user has referenced a table that another user is using for some other purpose.

Remedy: Find out who is using the named table, or use a different table. If previous load operation on the same table is not completed successfully then check whether error tables are same.

 

Error No : 2636 %TVMID must be empty for Fast Loading.

Explanation: This error occurs if the table to be loaded exists and contains data.

Generated By: AMP Software.

For Whom: End User.

Notes: This error means that the user has referenced a table that contains data rows.

Remedy: Delete all the rows in the specified table, or specify a different table.

 

Error No : 2637 BEGIN LOADING executed without FastLoad Init.

Explanation: This error occurs when a message is processed to start a Fast Load without the necessary preparation for the operation.

Generated By: AMP Software.

For Whom: End User.

Notes: This error means either that the user is incorrectly trying to use Fast Load, or that there has been an error in the execution of the Fast Load utility.

Remedy: If the user is not at fault, contact your Support Representative.

 

Error No : 2638 No dump image found on system.

Explanation: This error occurs when a request is made to save a system crash dump and there are no dumps to save.

Generated By: AMP Software.

For Whom: Internal Use Only.

Notes: This error means that all AMPs in the system are operational and none of them contains a dump image.

Remedy: This is an internal message, not a user error.

 

 

 

Error No : 2639 Too many simultaneous transactions.

Explanation: This error occurs if a new transaction is initiated but the system cannot accommodate it.

Generated By: AMP Software.

For Whom: End User.

Notes: This error means that an AMP has as many active transactions as it can hold.

Remedy: Resubmit the request.

 

Error No : 2640 Specified table does not exist in %DBID.

Explanation: A table was dropped before a statement that references the table was processed.

Generated By: AMP Software.

For Whom: End User.

Remedy: The table that is referenced no longer exists. If it is needed, it must be re-created.

 

Error No : 2641 %DBID.%TVMID was restructured. Resubmit.

Explanation: A table was changed before a statement hat references the table was processed. (For example, an index may have been added or a field removed.)

Generated By: AMP Software.

For Whom: End User.

Notes: The statement may not have the intended result because of the change in the table.

Remedy: Examine the table and resubmit the request.

Error No : 2642 AMP Down: the request against nonfallback %TVMID cannot be done.

Explanation: This error occurs when an AMP on which a nonfallback table resides is unavailable and

(a) a request is entered to modify a row in the table or

(b) an all-AMPs operation is initiated for the table.

Generated By: AMP Software.

For Whom: End User.

Remedy: Wait until the unavailable AMP is available, then resubmit request.

 

Error No : 2643 Internal error: inconsistent constraint code.

Explanation: This error occurs when pseudo code reports that a row does not meet the constraints placed on it and does not also indicate why it does not.

Generated By: AMP Step Processing Software.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

Error No : 2644 No more room in database %DBID.

Explanation: This error occurs only when an attempt is made to increase the amount of space used by a database,

and there is no space left to accommodate the increase.

Note: The numeric database id may be displayed in place of the database name when the name is not available.

This would be the case, for example, when a CREATE DATABASE or CREATE USER statement fails

because there is insufficient space in the new database for a default journal table.

Generated By: AMP Step Processing Software.

For Whom: End User.

Remedy: Either drop some of the tables currently contained in the database, or have the permanent space

limit for the database increased. Then resubmit the request.

 

Error No : 2645 Internal error: bad Response.Kind.

Explanation: This error occurs only if a message is received by the AMPs that does not have a legal mode of response.

Generated By: AMP Step Processing Software.

For Whom: Site support representative.

Notes: This error is the result of a random consistency check, and may imply that there is a serious problem.

Remedy: Contact your Support Representative.

 

Error No : 2646 No more spool space in %DBID.

Explanation: Insufficient space available in the specified database for the spool file.

Generated By: AMP Step Processing Software.

For Whom: End User.

Remedy: Have the spool space limit for the database increased and resubmit the request.

 

Error No : 2647 Internal error: OneAMP operation found.

Explanation: The AMP has been instructed to execute in a mode that is not yet supported. (For example, a

message that should have been sent to an AMP using the hash code was instead sent using processor number.)

Generated By: AMP Step Processing Software.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2648 Internal error: could not find spool header.

Explanation: This error occurs only when the step that is building a local spool file cannot find the table

header immediately after building it.

Generated By: AMP Step Processing Software.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2649 Internal error: illegal index type

Explanation: This error occurs only when the step that is building a new secondary index discovers that the index is to be both unique and unhashed.

Generated By: AMP Step Processing Software.

For Whom: Site support representative.

Notes: This type of index is recognized by the AMP, but is not currently supported.

Remedy: Contact your Support Representative.

Error No : 2650 Numeric processor operand error.

Explanation: This error occurs only when the numeric co-processor returns an operand error. This error code can also be returned when the right operand of a MOD expression is zero.

Generated By: The Numeric Processor.

For Whom: Site support representative.

Notes: This is normally caused by an attempt to load data that is not numeric.

Remedy: Try to resubmit the request. If unsuccessful, contact your Support Representative.

 

Error No : 2651 Operation Error computing expression involving %TVMID.%FLDID.

Explanation: This error occurs only when the numeric co-processor returns an operand error. This error code can also be returned when the right operand of a MOD expression is zero.

Generated By: The Numeric Processor.

For Whom: Site support representative.

Notes: This normally indicates the presence of bad data. However, it may also be a hardware error.

Remedy: Try to resubmit the request. If unsuccessful, Contact your Support Representative.

 

Error No : 2652 Operation not allowed: %DBID.%TVMID is being Loaded.

Explanation: This error occurs only when a user issues a request for a table that is being Fast/Multi Loaded.

Generated By: AMP Steps.

For Whom: End User.

Notes: The table does exist, but it is not in a form in which it may be accessed.

Remedy: Wait until the Fast/Multi Load is finished, then resubmit the request.

 

Error No : 2653 Fast Load not allowed: table %TVMID has been rebuilt.

Explanation: While the table is being Fast Loaded, a disk error occurred causing the table to be rebuilt.

Generated By: AMP Software.

For Whom: End User.

Notes: Some data is lost, and cannot be recovered.

Remedy: Drop this table and its associated tables, recreate them, then resubmit the request.

 

Error No : 2654 Operation not allowed: %DBID.%TVMID is being Restored.

Explanation: This error occurs when a user issues a request for a table that is being restored.

Generated By: AMP Steps.

For Whom: End User.

Notes: A table that is being restored may not be accessed for select or update.

Remedy: Wait until the restore operation is completed, then resubmit the request. If a restore is not in process, the operation may have been aborted, and needs to be restarted or started over, or the table must be dropped.

 

Error No : 2655 Invalid parcel sequences during Load

Explanation: This error occurs when the data parcel block sent from the host has an invalid parcel flavor, the

flavor is out of sequence, the length of a parcel is invalid or data was sent without Fast Load/MLoad initialization.

Generated By: StpLin/StpESD/LctStrtR

For Whom: Host Fast Load/MLoad Utility.

Notes: A problem occurred in the processing of a FastLoad/MLoad.

Remedy: Contact your Support Representative.

Error No : 2656 %TVMID Load error: bad internal status – %VSTR

Explanation: This error occurs when an internal consistency check fails. This may have been caused by one Fast/Multi Load job started immediately right after another Fast/Multi Load had just finished.

Generated By: AMP Steps.

For Whom: Site support representative.

Notes: A problem occurred in the processing of a Fast/Multi Load.

Remedy: Try to resubmit the Fast/Multi Load request. If unsuccessful, contact your Support Representative.

 

Error No : 2657 FALLBACK cannot be added or removed when an AMP is down.

Explanation: This error occurs when a user tries to add or drop the FALLBACK option while an AMP is not available.

Generated By: AMP Steps.

For Whom: End User.

Remedy: Wait until all AMPs are available and resubmit the request.

 

Error No : 2658 Data type conversion is not supported in Fast Load.

Explanation: This error occurs when:

(a) a Fast Load operation attempts to store a character string as a numeric, or vice versa, or;

(b) an attempt is made to store one type of numeric data in another type of numeric (for example, INTEGER in DECIMAL).

Generated By: AMP Steps.

For Whom: End User.

Remedy: If it is necessary to convert data types, a host program must be written to do the conversion.

 

Error No : 2659 The DBS restarted between FastLoad or MLoad requests.

Explanation: This error is returned when a restart occurs between requests during a FastLoad or MLoad operation.

Generated By: AMP FastLoad/MLoad processing.

For Whom: The FastLoad/MLoad Utilities.

Notes: This error code is designed to be intercepted by a host utility and should never be seen by the end user.

Remedy: None required. The load utility should recover and continue the load.

Error No : 2660 Illegal INSERT detected after the END LOADING was started.

Explanation: This error occurs during Fast Load if the INSERT statement is retransmitted after END LOADING has been started.

Generated By: AMP Fast Load Processing.

For Whom: End User.

Remedy: Remove the INSERT statement from the FastLoad request.

 

Error No : 2661 Invalid numeric value or bad string length.

Explanation: This error occurs due to either of two conditions:

(1) An attempt was made to move a character or byte string data item into a character or byte field of shorter length (for example, moving a 5-character data item into a 4-character field). (2) The row under construction in EvlBuild is appending

a numeric field that has a value not consistent with its evlRepresent_t length definition (for example, integer64 has value of length 2).

Generated By: The interpretative instruction processor.

For Whom: End User for case 1. Site support representative. for either case.

Notes: This is used for development debugging purposes and should never occur in the field.

Remedy: For case 1, the problem can be circumvented by changing the request to use strings of equal length. In either case, this is an internal error. Contact your Support Representative.

 

Error No : 2662 SUBSTR: string subscript out of bounds.

Explanation: This error occurs when a SUBSTR is used, and either the start position used is beyond the end of the string, the start offset plus the specified length is greater than the string length, or the specified length is negative.

Generated By: The interpretative instruction processor.

For Whom: End User.

Notes: This can be caused by an error in the second or third argument of SUBSTR.

Remedy: Fix the DBC/SQL request and resubmit.

Error No : 2663 SUBSTR: string subscript out of bounds in %TVMID.%FLDID.

Explanation: This error occurs when a SUBSTR is used, and either the start position used is beyond the end of the string or the start offset plus the specified length is greater than the string length.

Generated By: The interpretative instruction processor.

For Whom: End User.

Notes: This can be caused by an error in the second or third argument of SUBSTR.

Remedy: Fix the DBC/SQL request and resubmit.

Error No : 2664 The requested aggregate operation is too complex to execute.

Explanation: This error occurs when a request requires a segment longer than 32K.

Generated By: Database software for the AMPs.

For Whom: End User.

Notes: Either the request specifies many aggregate operations or one of the fields being operated on has a potential size of several K.

Remedy: Simplify the query or avoid use of the large field. If neither approach succeeds, contact your Support Representative.

 

Error No : 2665 Invalid date.

Explanation: This error occurs when date arithmetic is attempted on an invalid date.

Generated By: AMP Steps.

For Whom: End User.

Notes: Dates are stored as integers in the form YYMMDD, where YY is a calendar year beginning with 1900. Values such as 861332 are invalid as dates and may not be used where the value is to be used as a DATE data type. This error can also occur when character strings are being converted to DATE and the character data is in the wrong format or conversion results in an invalid value.

Remedy: Correct and resubmit the request.

 

Error No : 2666 Invalid date supplied for %TVMID.%FLDID.

Explanation: This error occurs when an operation is attempted on an invalid date and a known data field is involved.

Generated By: AMP Steps.

For Whom: End User.

Notes: Dates are stored as integers in the form YYMMDD, where YY is a calendar year beginning with 1900. Values such as 861332 are invalid as dates and may not be used where the value is to be used as DATE data type. This error can also occur when character strings are being converted to DATE type and the character data is in the wrong format or conversion results in an invalid value. This is the same error as Error No : 2665, except that Tvmid and Fldid are available.

Remedy: Correct and resubmit the request.


Error No : 2667 Left-over spool table found : transaction aborted.

Explanation: This error occurs if a left-over spool is used by a transaction other than the transaction for which it was created. The transaction attempting to use this left-over spool is aborted, and diagnostic information about the left-over spool appears on the system console screen.

Generated By: SutBldSp, SutRespF.

For Whom: Site Support Representative

Notes: Developers researching the left-over spool problem will be interested in the console-screen output produced by the logging of this error.

Remedy: Contact your Support Representative.

 

Error No : 2668 Output row buffer size exceeded (in MoveRow).

Explanation: This error occurs if, during Fast Load, the segment size limit for the output row in MoveRow is exceeded.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: A software error may have occurred during definition of the output row.

Remedy: Contact your Support Representative.

 

 

 

Error No : 2669 Outrow reference to source is illegal case (in MoveRow).

Explanation: This error occurs if, during Fast Load, the cross reference to the source in MoveRow is an unspecified case.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: A software error may have occurred during definition of the output row.

Remedy: Contact your Support Representative.

Error No : 2670 Source data kind is illegal kind (in MoveRow).

Explanation: This error occurs if, during Fast Load, the type that defines the source data in MoveRow is unspecified.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: A software error may have occurred during definition of the output row.

Remedy: Contact your Support Representative.

 

Error No : 2671 Unable to find a source constant (in MoveRow).

Explanation: This error occurs if, during Fast Load,the source constant in MoveRow cannot be found.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: A software error may have occurred during definition of the output row.

Remedy: Contact your Support Representative.

Error No : 2672 Output data kind is illegal kind (in MoveRow).

Explanation: This error occurs if, during Fast Load, the type that defines the output data in MoveRow is unspecified.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: A software error may have occurred during definition of the output row.

Remedy: Contact your Support Representative.

Error No : 2673 The source parcel length does not match data that was defined.

Explanation: This error occurs if the source parcel definition is inconsistent.

Generated By: MoveRow.

For Whom: End User.

Notes: This is probably caused by incorrect definition of the input parcel from the host computer.

Remedy: Check the definition of the input parcel.

 

Error No : 2674 Precision loss during data conversion.

Explanation: The data conversion has resulted in a value that is too small to be expressed in the requested data type.

Generated By: MoveRow.

For Whom: End User.

Remedy: Resubmit the request after changing the data type specified for the result. (For example, convert DECIMAL to FLOAT.)

Error No : 2675 Numerical overflow occurred during computation.

Explanation: The data conversion has resulted in a value that is too large to be expressed in the requested data type. (For example, trying to store 100,000.00 as DECIMAL(5,2).)

Generated By: MoveRow.

For Whom: End User.

Remedy: Resubmit the request after changing the data type specified for the result. (For example, convert DECIMAL to FLOAT.)

 

Error No : 2676 Invalid calculation: division by zero

Explanation: This error occurs when an attempt is made to divide by zero.

Generated By: MoveRow.

For Whom: End User.

Remedy: Resubmit the request after removing the division by zero.

 

 

 

 

Error No : 2677 NDP stack overflow.

Explanation: This error occurs when MoveRow exceeds the numeric co-processor stack of 8 numbers in converting numeric data.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: This is probably caused by a software error that occurred during definition of the output row.

Remedy: Contact your Support Representative.

Error No : 2678 NDP stack underflow.

Explanation: This error occurs when MoveRow converts numeric data and the numeric co-processor stack of 8 numbers is empty.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: This is probably caused by a software error that occurred during definition of the output row.

Remedy: Contact your Support Representative.

Error No : 2679 The format or data contains a bad character.

Explanation: This error occurs when the user submits a numeric-to-character conversion with an illegal format, or when, in converting characters to numeric, either the data or the format contains a bad character.

Generated By: MoveRow.

For Whom: End User.

Remedy: Validate the format used. If it is legal, then an illegal character is present in the data being converted from character to numeric.

Error No : 2680 Numeric processor operand error.

Explanation: This error occurs only when the numeric co-processor sends back an operand error.

Generated By: The Numeric Processor.

For Whom: End User.

Notes: This may be caused by an attempt to load data that is not numeric.

Remedy: Verify that valid numeric data was submitted from the host computer.

 

Error No : 2681 Fast Load not allowed: DBS had been reconfigured.

Explanation: The Teradata DBS had been reconfigured before the FAST LOAD of the table was completed.

Generated By: AMP Software.

For Whom: End User.

Notes: Partial data was FASTLOADed and the Teradata DBS was reconfigured. The data in the Teradata DBS was invalidated.

Remedy: Drop this table and its associated tables, recreate them, then resubmit the request.

 

Error No : 2682 Precision loss during data conversion.

Explanation: The data conversion has resulted in a value that is too small to be expressed in the requested data type.

Generated By: MoveRow.

For Whom: End User.

Remedy: Resubmit the request after changing the type specified for the result. For example, convert DECIMAL to FLOAT.

 

Error No : 2683 Numeric overflow occurred during computation.

Explanation: The data conversion has resulted in a value that is too large to be expressed in the requested data type. (For example, an attempt is made to store 100,000.00 as DECIMAL(5,2).)

Generated By: MoveRow.

For Whom: End User.

Remedy: Resubmit the request after changing the type specified for the result. For example, convert DECIMAL to FLOAT.

Error No : 2684 Invalid calculation: division by zero.

Explanation: This error occurs when an attempt is made to divide by zero.

Generated By: MoveRow.

For Whom: End User.

Remedy: Resubmit the request after removing the division by zero.

Error No : 2685 NDP stack overflow.

Explanation: This error occurs when, in converting numeric data, MoveRow exceeds the numeric co-processor stack of 8 numbers.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: This is probably caused by a software error that occurred during definition of the output row.

Remedy: Contact your Support Representative.

 

Error No : 2686 NDP stack Underflow.

Explanation: This error occurs when MoveRow converts numeric data and the numeric co-processor stack of 8 numbers is empty.

Generated By: MoveRow.

For Whom: Site support representative.

Notes: This is probably caused by a software error that occurred during definition of the output row.

Remedy: Contact your Support Representative.

Error No : 2687 The format or data contains a bad character.

Explanation: This error occurs when the user submits a numeric-to-character conversion with an illegal format,or when, in converting characters to numeric, either the data or the format contains a bad character.

Generated By: MoveRow.

For Whom: End User.

Remedy: Validate the format used. If it is legal, then an illegal character is present in the data being converted from character to numeric.

Error No : 2688 Numeric Processor Operand Error.

Explanation: This error occurs only when the numeric co- processor sends back an operand error.

Generated By: The Numeric Processor.

For Whom: End User.

Notes: This may be caused by an attempt to load data that is not numeric.

Remedy: Verify that valid numeric data was submitted from the host computer.

 

Error No : 2689 Field is null for column defined as NOT NULL.

Explanation: This error occurs only when the input parcel contains a null field that is not defined as nullable.

Generated By: MoveRow.

For Whom: End User.

Notes: This is caused by an incorrect input parcel.

Remedy: Verify that valid data was submitted from the host computer.

 

Error No : 2690 Zero table length in Unload.

Explanation: This error occurs only when the description of the row to be unloaded has a length of zero.

Generated By: MoveOut.

For Whom: Site support representative.

Notes: This is caused by an incorrect list of EvlReprs.

Remedy: Verify that the data definition is valid.

Error No : 2691 Reference to a deleted fieldid

Explanation: The caller is attempting to find a field whose fieldid has been deleted.

Generated By: FldLocat.

For Whom: Site support representative.

Notes: This may be caused by an incorrect field 5 header.

Remedy: Contact your Support Representative.

Error No : 2692 Reference to a fieldid less than the base-id.

Explanation: The caller is attempting to find a field whose fieldid is less than the base fieldid for the table.

Generated By: FldLocat.

For Whom: Site support representative.

Notes: This may be caused by an incorrect field 5 header.

Remedy: Contact your Support Representative.

Error No : 2693 The fieldids in field 5 are not contiguous.

Explanation: The field descriptors in field 5 should be contiguous, they are not.

Generated By: FldLocat.

For Whom: Site support representative.

Notes: This is caused by an incorrect field 5 header.

Remedy: Contact your Support Representative.

 

Error No : 2694 The row is incorrectly formatted.

Explanation: The row has inconsistent header information or length, or is not in the new row format.

Generated By: FldLocat.

For Whom: Site support representative.

Notes: This is caused by an incorrect field 5 header.

Remedy: Contact your Support Representative.

Error No : 2696 Error in the Numeric Data Processor.

Explanation: This error is caused by problems in the numeric co-processor.

Generated By: the Numeric Operations.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2697 Release 3 to 4 conversion process not complete.

Explanation: This error is the result of attempting to run Release 4 without following the proper Release 3 to 4 conversion process.

Generated By: SSSMain.

For Whom: Site support representative.

Notes: The system will pause in system startup when this error is detected.

Remedy: The only remedy for this error is to perform an IdLoad. Typically this IdLoad would be done at release 3 and user data archived via the release 3 Archive and Recovery Utility would then be restored. For further assistance, contact your Support Representative.

Error No : 2698 A disk read error has occurred in primitive dump area.

Explanation: The dump area is mentioned in the event message (for example, "AMPDUMP could not be saved"). The rest of the crash dump is saved regardless.

Generated By: DBS Startup.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2699 Inconsistent ROM pointer information in a crash dump ignored

Explanation: The crash dump being saved is mentioned in the event message (e.g., "Error saving crash dump from AMPDUMP"). The crash dump is saved anyway, using "reasonable" defaults for saving into the crash tables.

Generated By: DBS Startup.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2700 Referential constraint violation: invalid Foreign Key value.

Explanation: The new Foreign Key value in the referencing table has no corresponding value in the referenced

table. Note, this is typically caused by an SQL Insert or Update statement on a referencing table.

Generated By: SutCK1Rw & SutCKNRw.

For Whom: End user.

Remedy: Insert the new Foreign Key value into the referenced table first and then resubmit the request.

 

Error No : 2701 Unable to access the /tdsw/etc directory or the DBS config files.

Explanation: The /tdsw/etc directory is missing or we were unable to read/write the DBS configuration files in this directory.

Generated By: sssrss.

For Whom: Support Representative.

Notes: This indicates the the DBS has not been properly installed.

Remedy: Contact your Support Representative.

Error No : 2702 Missing DBS config file in /tdsw/etc.

Explanation: The DBS configuration files are not present in the /tdsw/etc directory.

Generated By: Unused at this time.

For Whom: Support Representative.

Notes: This indicates that the DBS configuration files may have been inadvertently removed.

Remedy: Contact your Support Representative.

 

Error No : 2703 The DBS config file is empty.

Explanation: The DBS configuration file is present but it is empty (i.e., zero byte length).

Generated By: Unused at this time.

For Whom: Support Representative.

Notes: This indicates that the DBS configuration file may have been touched before/after they were created by the DBS.

Remedy: Contact your Support Representative.

Error No : 2704 DBS config file I/O error.

Explanation: There was a system I/O error while accessing the DBS configuration file.

Generated By: sssrss.

For Whom: Support Representative.

Notes: This indicates that there was a Unix system I/O error.

Remedy: Contact your Support Representative.

Error No : 2705 Invalid DBS config file format.

Explanation: The DBS configuration file is not in the

expected format.

Generated By: Unused at this time.

For Whom: Support Representative.

Notes: This indicates that the DBS configuration file is not a regular Unix file.

Remedy: Contact your Support Representative.

Error No : 2706 Invalid DBS config file address.

Explanation: The internal address for the DBS configuration file is invalid.

Generated By: Unused at this time.

For Whom: Support Representative.

Notes: This indicates that the internal Unix path name of filep pointer is invalid.

Remedy: Contact your Support Representative.

Error No : 2707 Invalid DBS config file path name.

Explanation: The internal DBS configuration file path name is invalid.

Generated By: Unused at this time.

For Whom: Support Representative.

Notes: This indicates the the internal Unix path name is invalid.

Remedy: Contact your Support Representative.

Error No : 2708 DDF Leading/Trailing Version Number mismatch.

Explanation: The Leading & Trailing Version Numbers of the Distributed DBS File do not match.

Generated By: sssutl

For Whom: Support Representative.

Notes: This indicates that a version mismatch was detected while performing a status check.

Remedy: Contact your Support Representative.

Error No : 2709 SSSWAIT has timed out.

Explanation: The maximum time allowed for SSSWAIT has expired.

Generated By: sssutl.

For Whom: Support Representative.

Notes: This indicates that the time allowed waiting for a success response from the last Vproc done with a specific step during DBS start-up has expired.

Remedy: Contact your Support Representative.

 

 

Error No : 2710 Invalid channel state in SSSWAIT.

Explanation: An invalid channel state occured during an SSSWAIT.

Generated By: sssmain

For Whom: Support Representative.

Notes: This indicates that the channel used to determine the status of DBS start-up is not in either of the recognized states.

Remedy: Contact your Support Representative.

Error No : 2711 Inconsistent AMP/PE Vproc count.

Explanation: The AMP/PE VProc counts are inconsistent.

Generated By: sssmain.

For Whom: Support Representative.

Notes: This indicates that AMP/PE Vproc counts are inconsistent with that of the well know static groups.

Remedy: Contact your Support Representative.

Error No : 2712 Distributed DBS File (DDF) failure.

Explanation: Internal DDF failure.

Generated By: Unused at this time.

For Whom: Support Representative.

Notes: This indicates that there has been a failure in the Distributed DBS File module.

Remedy: Contact your Support Representative.

Error No : 2713 Problem creating DBS – RSS shared memory segment

Explanation: Problem creating a shared memory segment for communication between DBS and RSS.

Generated By: sssrss.

For Whom: Support Representative.

Notes: This indicates that there has been a failure obtaining a UNIX Shared memory segment.

Remedy: Contact your Support Representative.

Error No : 2714 Resusage discarded some monitoring information because of insufficient

resources

Explanation: ResUsage software was not able to keep up with its workload, as described in the message. This usually happens because the system is too busy to handle the resusage log rate specified in the control GDO.

Generated By: SSSRSS — resource usage monitoring.

For Whom: System Administrator, System Support Representative.

Notes: This event is informational.

Remedy: Consider setting longer resusage collect and log intervals or disabling one or more ResUsage tables. If this is infeasible or the explanation does not seem to fit your case, contact your Support Representative.

Error No : 2715 Convert Time function failed

Explanation: Converttime function failed for the given secs value and ResUsage table.

Generated By: resd daemon.

For Whom: System Support Representative

Notes: This indicates the corruption of rss data buffers.

Remedy: Contact the Support Representative.

Error No : 2716 Convert Date function failed

Explanation: Convertdate function failed for the given secs value and ResUsage table.

Generated By: RESD daemon.

For Whom: System Support Representative

Notes: This indicates the corruption of rss data buffers.

Remedy: Contact the Support Representative

 

 

Error No : 2717 Segget failure occured in sssrss

Explanation: segget function failed for bundling the resusage rows into the segment due to lack of segments.

Generated By: resd/restpad daemon.

For Whom: System Support Representative

Notes: This indicates that resusage data will not be logged or some of the rows will be missed. There will be

no impact other than this on the system – although other areas may be affected by lack of segments.

Remedy: Contact the Support Representative

Error No : 2718 FASTLOAD CHECKPOINT must be within the Data Loading transaction.

Explanation: The CHECKPOINT LOADING statement and the FASTLOAD INSERT statement must be in

the same transaction.

Generated By: AMP FASTLOAD Processing.

For Whom: Host FASTLOAD Utility.

Remedy: Put the CHECKPOINT statement within the same transaction as the INSERT statement.

Error No : 2719 FASTLOAD END LOADING cannot be inside the Data Loading phase.

Explanation: The END LOADING statement cannot be inside the same transaction as the INSERT statement.

Generated By: AMP Fastload Processing.

For Whom: Host Fastload Utility.

Remedy: Put the END LOADING statement outside the transaction which contains the INSERT statement.

 

 

Error No : 2720 Fast/MLoad or FastExport has already been terminated.

Explanation: If this was a FastLoad or MLoad job then the load operation on the DBS side has already been terminated, but data parcels are still being sent down from the host. Possible cause is the Host Load Utility is ignoring the error returned from DBS. If this was a FastExport job then the FastExport session has been logged off. The SQL Select is either aborted or

if it has been completed then the logoff results the answer set inaccessible. In the latter case, the host must submit an End Request to delete any spool files created on the AMPs.

Generated By: AMP Load Processing.

For Whom: Host Load Utility.

Notes: The Utility should terminate if there is any error returned while it is sending data parcels to the DBS.

Remedy: Cancel the Load job on the Host. Correct the Utility if it is ignoring errors.

Error No : 27Error No : 21 Fast Load Utility fails to recognize error in previous request.

Explanation: DBS has decided to abort this Fast Load due to some error conditions caused by the previous request during the data loading phase, but the Host Fast Load Utility fails to acknowledge the error returned and continues to send data parcels to the DBS.

Generated By: AMP Fast Load Processing.

For Whom: Host Fast Load Utility.

Remedy: Correct the Host Fast Load Utility.

 

Error No : 2722 Too many in-doubt 2PC transactions.

Explanation: There are more in-doubt 2PC transactions than can be accommodated.

Generated By: AMP

For Whom: End User.

Notes: This error means that an AMP has as many indoubt 2PC transactions as it can accommodate.

Remedy: Resolve the in-doubt 2PC transactions and resubmit the request.

 

 

Error No : 2723 Too many Locks used by 2PC transactions.

Explanation: During a COLDWAIT restart, the number of locks for in-doubt 2PC transactions to be placed on a catch-up AMP to bring it on-line exceeded the lock manager lock resources.

Generated By: AMP

For Whom: Operator. DBA.

Notes: This error causes a COLD restart of the DBC to bring the system back up, but the catch-up AMP will

not be on line.

Remedy: Resolve the in-doubt 2PC transactions, then COLDWAIT restart the DBC if the AMP must be brought on-line immediately.

 

 

Error No : 2724 The two-phase commit transaction is indoubt.

Explanation: An in-doubt transaction was detected during a restart.

Generated By: AMP

For Whom: End User.

Notes: The transaction was in this state when the DBC was restarted.

Remedy: The transaction must be committed or aborted by the coordinator automatically, or by the TPCCONS utility.

 

 

Error No : 27Error No : 25 Too many 2PC transactions for COLDWAIT restart

Explanation: Too many in-doubt transactions exist to allow a COLDWAIT DBC restart. The DBC will be restarted with a COLD restart.

Generated By: AMP

For Whom: Operator. DBA.

Notes: This condition occurs if the number of in-doubt 2PC transactions on the on-line AMPs in a cluster with a

catch-up AMP exceeds the total capacity (number of indoubt transactions) the catch-up AMP would have to establish in a COLDWAIT restart.

Remedy: Following COLD restart of the DBC, the indoubt 2PC transactions must be committed/aborted in order to reduce the number of in-doubt 2PC transactions. A subsequent COLDWAIT restart should allow the catch-up AMP to come on- line.

 

Error No : 27Error No : 26 Referential constraint violation: cannot

delete/update the Parent Key value.

Explanation: At least one of the Parent Key (i.e. referenced columns) values being deleted or updated is referenced by some Foreign Key values. By definition, the Parent Key value cannot be deleted or updated if there exists a Foreign Key value which is referencing it. Note, this is typically caused by an SQL Delete or Update statement on a referenced table.

Generated By: SutCKPRw.

For Whom: End user.

Remedy: Delete the corresponding Foreign Key value from the Child table (i.e. referencing table) first and then resubmit the request.

 

 

Error No : 2728 Aborted due to a non-valid reference index on %DBID.%TVMID.

Explanation: The table being accessed has a reference index that is not valid. This could be resulted from the following two cases:

(1) The target table or other table which references or being referenced by the target table was rollforward/back or restored. (2) The target table has some unresolved references because it is referencing some non-existent tables. For either case, no inserts, updates, or deletes are allowed.

Generated By: SutCK1Rw & SutCKNRw.

For Whom: End user.

Remedy: For the Roll and Restore case, drop the corresponding referential constraint and resubmit the request. For the unresolved references case, create all the missing referenced table and resubmit the request.

Error No : 2729 Dictionary parent count does not match header parent count.

Explanation: This message is displayed if the parent count field in the table header does not match the corresponding

parent count in the DBC.TVM record for the table.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2730 Warning: RI is not valid on one or more AMPs.

Explanation: This message is displayed if any AMP does not have the valid state set for the index. All remaining checks for the index are bypassed.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2731 Warning: Unable to access the parent table header.

Explanation: This message is displayed if any AMP fails to lock the parent table or fails to read the parent table header. All remaining checks for the index are bypassed.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2732 Warning: Skipping parent key validation in level 3 checking.

Explanation: This message is displayed if any AMP fails to lock the parent table in order to check the parent keys. Only parent key validation is bypassed in level 3 checking.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2733 Primary and fallback RI row checksums do not match.

Explanation: A mismatch is detected when the checksum of the primary copy of a reference index row is compared to its fallback copy.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2734 Data row count is less than RI count.

Explanation: This message is displayed when the number of rows in the primary data subtables across all AMPs is less than the number of rows in the corresponding reference index subtables across all AMPs. Note, data count must be greater than or equal to the RI count.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2735 Primary and fallback RI counts do not match.

Explanation: This message is displayed when the count of rows in the primary reference index subtable on each AMP does not match the sum of counts of the rows in the corresponding fallback reference index subtables on other AMPs in the same cluster.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2736 RI row out of order.

Explanation: Out of order reference index rows are detected as the reference index subtables are traversed.

The row is discarded from the remainder of the checking process.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2737 RI row has same row id as previous row.

Explanation: Duplicated reference index rows are detected as the reference index subtables are traversed. The row is discarded from the remainder of the checking process.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2738 %TVMID already has Fastload running

Explanation: This error occurs if a user submits a FastLoad operation for a table that already is being loaded by another FastLoad job.

Generated By: AMP Software.

For Whom: End User.

Notes: This error means that a user has submitted a Fastload on a table that is being loaded by another Fastload.

Remedy: Take administrative action to determine which FastLoad job should be run against the table. If necessary, delete existing rows and reload the data.

Error No : 2739 Mload did not find an insert for insert missing update rows.

Explanation: Multi Load attempted to perform an insert for a missing update row but could not find the  insert statement. This could be caused by having different table names in the update and insert parts of the statement.

Generated By: AMP Multi Load Processing.

For Whom: Multi Load user.

Notes: The User should ensure that the table names in both parts of the statement are the same.

Remedy: Correct the Multi load script and resubmit the job.

 

 

Error No : 2740 One or more rows found for table not in  DBC.TVM.

Explanation: If any rows are found on any AMP for tables which are not recorded in TVM.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2741 Table header not found.

Explanation: This message is displayed if one or more AMPs are missing a table header.

Generated By: CheckTable

For Whom: Site support representative

Note: This code is also used as an express request crash code on a missing DBC.NEXT table header.

Remedy: Contact your Support Representative.

Error No : 2742 Extraneous subtable

Explanation: This message is displayed for each AMP on which an extraneous subtable is detected. CheckTable formats the message text as: Extraneous subtable nnnnn on AMP vvvvv where nnnnn is the decimal subtable number vvvvv is the

AMP processor

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2743 Mismatch on the following table header components:

Explanation: This message if displayed when the following components of the table headers on all AMPs are different from the table header of the AMP with the lowest physical processor number of all online AMPs. The components are:

. ExternalName . DataBaseId . AccountId . StructVersion . UtilVersion . PermJrnlTblId . Protection . UserJournal .

HashedTable . Journal . Fields in field 5 . Index descriptors Only components for which a mismatch is detected on some AMP are listed.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2744 Dictionary version does not match header version.

Explanation: This message is displayed if the version field in the table header does not match the corresponding version number in the DBC.TVM record for the table.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2745 Warning: USI flagged as invalid on one or more AMPs.

Explanation: This message is displayed if any AMP does not have the valid flag set for the index. All remaining checks for the index are bypassed.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2746 Warning: NUSI flagged as invalid on one or more AMPs.

Explanation: This message is displayed if any AMP does not have the valid flag set for the index. All

remaining checks for the index are bypassed.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2747 Primary and fallback data counts do not match.

Explanation: This message is displayed if the count of rows in the primary data subtable on each AMP does not match the sum of the counts of the rows in the corresponding fallback data subtables on other AMPs in the same cluster.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2748 Data count does not match the USI count.

Explanation: This message is displayed when the sum of rows in the primary data subtables across all AMPs does not  atch the sum of the rows in the corresponding primary unique secondary index subtables across all AMPs.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2749 Primary and fallback USI counts do not match

Explanation: This message is displayed when the count of rows in the primary unique secondary subtable on each AMP does not match the sum of counts of the rows in the corresponding fallback unique secondary index subtables on other AMPs in the same cluster.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2750 Data subtable count does not match NUSI count.

Explanation: This message is displayed when the counts of the rows in each data subtable does not match the count of rows indexed by the corresponding index subtable.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2751 Data row out of order.

Explanation: A data row is found to be out of order when the data subtables are scanned.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2752 Data row has same row id as previous row.

Explanation: Two adjacent rows with the same row id are found when the data subtables are scanned.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2753 Primary data row is on wrong AMP.

Explanation: A row is found to be on the wrong AMP when the data subtables are scanned.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2754 Fallback data row is on wrong AMP.

Explanation: A row is found to be on the wrong AMP when the data subtables are scanned.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2755 Fallback data row is in wrong subtable.

Explanation: A row is found to be in the wrong subtable when the data subtables are scanned.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2756 Fallback data row is missing.

Explanation: Missing fallback data rows are detected.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2757 Primary data row is missing.

Explanation: Extra fallback data rows are detected.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2758 USI row out of order.

Explanation: Out of order index rows are detected as the index subtables are traversed. The row is discarded from the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2759 USI row has same row id as previous row

Explanation: Duplicated index rows are detected as the index subtables are traversed. The row is discarded  from the remainder of the checking process. Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2760 Primary USI row is on wrong AMP

Explanation: Incorrectly distributed index rows are detected as the index subtables are traversed. The row is discarded from the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2761 Fallback USI row is on wrong AMP.

Explanation: Incorrectly distributed index rows are detected as the index subtables are traversed. The row is discarded from the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2762 Fallback USI row is in wrong subtable.

Explanation: Incorrectly distributed index rows are detected as the index subtables are traversed. The row is discarded from the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2763 USI row indexes non existent data row.

Explanation: Non existent indexed data rows are detected during the check for unique secondary indexes.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2764 Data row not indexed by USI.

Explanation: Unindexed data rows are detected during the check for unique secondary indexes.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2765 Data row indexed multiple times by USI.

Explanation: Multiply indexed data rows are detected during the check for unique secondary indexes.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2766 Fallback USI row is missing.

Explanation: A missing fallback unique secondary index row is detected.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2767 Primary USI row is missing.

Explanation: A missing primary unique secondary index row is detected.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2768 NUSI row out of order.

Explanation: Out of order index rows are detected as the index subtables are traversed. The row is discarded from the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2769 NUSI row has same row id as previous row.

Explanation: Duplicated index rows are detected as the index subtables are traversed. The row is discarded from the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2770 Data row id referenced by NUSI is on wrong AMP.

Explanation: An indexed data row id is found which belongs to another AMP during the traversal of index subtables.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2771 Data row id referenced by fallback NUSI in wrong subtable.

Explanation: An indexed data row id is found which belongs to another fallback subtable during the traversal of index subtables.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2772 NUSI row indexes non existent data row.

Explanation: A non existent indexed data row is detected when a check is made for nonunique secondary indexes.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2773 Data row not indexed by NUSI.

Explanation: An unindexed data row is detected when a check is made for nonunique secondary indexes.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2774 Data row indexed multiple times by NUSI.

Explanation: Multiple indexed data rows are detected when a check is made for nonunique secondary indexes.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2775 Data row hash code is incorrect.

Explanation: A primary (or fallback if an AMP is down) data row has incorrect hash code. The row’s hash code will not be corrected in the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative Note: This code is also used internally by MultiLoad to log a row hashing anomaly to the error table during the application phase.

Remedy: Contact your Support Representative.

Error No : 2776 Data row has duplicate unique primary key.

Explanation: A primary (or fallback if an AMP is down) data row has the same primary key as another row in the same hash code (unique primary index). The row is not ignored in the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Note: This code is also used as a crash code during system startup if the DBC.TRANSLATION table contains

rows with duplicate primary keys.

Remedy: Contact your Support Representative.

 

 

Error No : 2777 Data row is duplicate.

Explanation: A primary (or fallback if an AMP is down) data row is a duplicate of another row in the same hash code (nonunique primary index). The row is not ignored in the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2778 Primary and fallback data rows do not match.

Explanation: A mismatch is detected during a byte by byte comparison of the primary copy of a data row to its fallback copy.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2779 USI row hash code is incorrect.

Explanation: A primary (or fallback if am AMP is down) unique secondary index row has incorrect hash code. The hash code is not corrected in the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2780 USI row has duplicate key.

Explanation: A primary (or fallback if an AMP is down) unique secondary index row which has the same index key as another row in the same hash code. The row is not ignored in the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2781 Data row indexed by USI row with incorrect key.

Explanation: A discrepancy is detected when the key of each unique secondary index row is compared to the expected key extracted from the data row.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2782 Primary and fallback USI rows do not match.

Explanation: A mismatch is detected during a byte by byte comparison of the primary copy of an index row to its fallback copy.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2783 NUSI row incorrectly has continuation flag set. ***OBSOLETE***

Explanation: Inconsistencies in the setting of the index continuation flags are detected during traversal of index subtables. The row still participates in the remainder of the check.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2784 NUSI row incorrectly has continuation flag clear.

Explanation: Inconsistencies in the setting of the index continuation flags are detected during traversal of index subtables. The row still participates in the remainder of the check.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2785 Data row indexed by NUSI row with  incorrect key.

Explanation: A discrepancy is detected when the key of the nonunique secondary index row which indexes each data row is compared to the expected key extracted from the data row.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2786 NUSI data row ID out of order.

Explanation: Out of order indexed data rows are detected during the check for nonunique secondary indexes.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2787 Table check bypassed due to pending

Explanation: The table header on one or more AMPs has a field 4 present which indicates that the table is in the process of being Fast Loaded, Restored or has been Recovery Aborted.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2788 Table header not found for table.

Explanation: For each table recorded in TVM which does not have a corresponding table header on one or more AMPs.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2789 Disk read error during checking process.

Explanation: A read error was encountered during CheckTable processing. The current table check is aborted and NO automatic rebuild action is taken. An error is also logged to Event Log file system. This error includes an indication of if the read error occurred on a spool file or a data or index subtable and the AMP on which the error occurred.

Generated By: CheckTable

For Whom: Site support representative

Remedy: If the error occurred on a spool file, attempt to repeat the check on the table that CheckTable was processing when the error was reported. If the error occurred on a user table, the data may be recovered via a Table Rebuild, DROP/CREATE index or Restore as appropriate. For additional assistance, contact your Support Representative.

Error No : 2790 NUSI row hash code is incorrect.

Explanation: A non-unique secondary index row has an incorrect hash code. The hash code is not corrected in the remainder of the checking process.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2791 Primary and fallback data row checksums

do not match.

Explanation: A mismatch is detected during a checksum comparison of the primary copy of a data row to its

fallback copy.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2792 Primary and fallback USI row checksums do not match.

Explanation: A mismatch is detected when a checksum comparison of the primary copy of a index row to its fallback copy.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

Error No : 2793 MLoad MARK DUPLICATE INSERT (duprow)

Explanation: An MLoad apply error table row with this code marks a duplicate-insert event where the newly built row is identical to an old row in the target table.

Generated By: AMP MLoad steps

For Whom: MLoad user

Remedy: The MLoad user must decide if the duplicate row is an anomaly. The user may then use the contents of the error table row to perform event logging or recovery actions.

Error No : 2794 MLoad MARK DUPLICATE INSERT (dupkey)

Explanation: An MLoad apply error table row with this code marks a duplicate-insert event where the newly built row has the same unique primary key value as an old row in the target table.

Generated By: AMP MLoad steps

For Whom: MLoad user

Remedy: The MLoad user must decide if the duplicate row is an anomaly. The user may then use the contents of the error table row to perform event logging or recovery actions.

Error No : 2795 MLoad MARK DUPLICATE UPDATE

Explanation: An MLoad apply error table row with this code marks a duplicate-update event where the newly built row is identical to an old row in the target table. This event will only occur if the target table has a non-unique primary index (NUPI).

Generated By: AMP MLoad steps

For Whom: MLoad user

Remedy: The MLoad user must decide if the duplicate row is an anomaly. The user may then use the contents of the error table row to perform event logging or recovery actions.

Error No : 2796 MLoad MARK MISSING DELETE

Explanation: An MLoad apply error table row with this code marks a missing-delete event where the row specified for delete is not found in the target table.

Generated By: AMP MLoad steps

For Whom: MLoad user

Remedy: The MLoad user must decide if the missing row is an anomaly. The user may then use the contents of the error table row to perform event logging or recovery actions.

Error No : 2797 MLoad MARK MISSING UPDATE

Explanation: An MLoad apply error table row with this code marks a missing-update event where the row specified for  update is not found in the target table.

Generated By: AMP MLoad steps

For Whom: MLoad user

Remedy: The MLoad user must decide if the missing row is an anomaly. In the case of this error, the mark rows for the missing update operations places nulls for the target table columns in the error table. The user may still use the contents of the error information in the error table row to perform event logging or recovery actions.

Error No : 2798 MLoad: Prime Key mismatch on insert missing update.

Explanation: The user attempted to perform the insert part of a ’DO INSERT FOR MISSING UPDATE ROWS’ with a different prime key values for the update and insert.

Generated By: AMP MLoad steps

For Whom: MLoad user

Remedy: The MLoad user must correct the job to ensure that the update and insert rows have the prime key.

 

 

Error No : 2799 MLoad MARK MISSING UPDATE INSERT

Explanation: An MLoad apply error table row with this code marks a missing-update insert event where the row specified for update is not found in the target table and is subsequently inserted into the target table.

Generated By: AMP MLoad steps

For Whom: MLoad user

Remedy: The MLoad user must decide if the missing row is an anomaly. In the case of this error, the mark rows for the missing update operations places nulls for the target table columns in the error table. The user may still use the contents of the error information in the error table row to perform event logging or recovery actions.

Error No : 2800 Aborted due to invalidated secondary index on %DBID.%TVMID.

Explanation: The table being accessed has a unique or nonunique secondary index that was invalidated as a result of one of the below operations. A restore operation with an AMP down or A rollforward operation with ’primary data’ option or

A restore operation with ’no build’ option. No updates or inserts are allowed on this table until the index is built through a ’build’ statement of arcmain or dropped.

Generated By: AMP Steps.

For Whom: End User.

Remedy: In case of AMP down, drop the invalidated secondary indexes on the table else A ’build’ statement of arcmain should follow to build the invalidated secondary indexes.

Error No : 2801 Duplicate unique prime key error in %DBID.%TVMID.

Explanation: The request generated a row whose prime key duplicated that of an existing row in a table with a unique prime key.

Generated By: AMP Steps.

For Whom: End User.

Remedy: Correct and resubmit the request.

Error No : 2802 Duplicate row error in %DBID.%TVMID.

Explanation: An update or insert request generated a row that was a duplicate of an existing row.

Generated By: AMP Steps.

For Whom: End User.

Remedy: Correct and resubmit the request.

 

 

Error No : 2803 Secondary index uniqueness violation in %DBID.%TVMID.

Explanation: A row generated by the request violated the uniqueness criteria of some unique secondary index. The unique secondary index was created with a CREATE UNIQUE INDEX statement, or a UNIQUE constraint, or a PRIMARY KEY specification.

Generated By: AMP Steps.

For Whom: End User.

Remedy: Correct and resubmit the request.

 

 

Error No : 2804 Incompatible version in recovery status row.

Explanation: The version number in the recovery status row on disk is incompatible with the current software version.

Generated By: Recovery, Booter, Idllink or AFUINQDI.

For Whom: End User.

Notes: This error occurs in two different cases:

1) An attempt was made to migrate across more software versions than supported. This may occur as a result of setting the version back to an obsolete version or by skipping forward across more than one software release.

2) An attempt was made to run with more than two joined DSUs with Release 3.0 versions of the Booter, or Idllink, or DBS software.

Remedy:

1) Reboot system at correct version or contact your Support Representative.

2) Unjoin all DSUs beyond the 2nd before running with Release 3.0 software.

 

 

Error No : 2805 Maximum row length exceeded in %TVMID.

Explanation: A row generated by the request exceeded the maximum row length allowed by the Teradata DBS.

Generated By: AMP Steps.

For Whom: End User.

Notes: A data row or an index row may be too long. If an index row is too long, the associated data row is very close to the maximum limit, and/or contains compressed fields that are not stored in compressed form in index rows.

Remedy: Correct and resubmit the request.

Error No : 2807 Internal error: Invalid message source.

Explanation: A message was received from an external(internal) source when it should have been from an internal (external) source.

Generated By: AMP worker tasks.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2808 Internal error: a received message was of invalid type

Explanation: A message was received that was of an unexpected type (Response, Simplex, or Initiating).

Generated By: AMP worker tasks.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2809 Invalid recovery sequence detected

Explanation: An illegal sequence of recovery actions has been detected. This could be a cluster Restore of a fallback table that was not preceded by a dictionary restore or a specific-AMP restore operation during a Fast Load or MLoad.

Generated By: AMP Software.

For Whom: End User.

Notes: All cluster restores of fallback tables must be preceded by a dictionary restore. This situation may arise in doing a specific-AMP restore of a no fallback table after CREATE/ DROP INDEX, a Fast Load, or an MLoad.

Remedy: To restore a fallback table to AMP clusters, you must first perform a dictionary restore of the table from a dictionary dump. If the problem is CREATE/ DROP INDEX, perform an all-AMPs restore followed by a specific-AMPs restore of the no fallback table. Then do the CREATE/DROP INDEX. If the problem is Fast Load or MLoad, the operation must finish prior to issuing the recovery operation, or all-AMPs must be restored first.

 

 

Error No : 2810 Internal error: permanent journal error found.

Explanation: An unexpected reference to permanent journals was found.

Generated By: AMP Software.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2811 Data rowid is already indexed.

Explanation: During an insert of a rowid into an index, the row id was found to exist already in the index.

Generated By: AMP Worker Tasks.

For Whom: Site support representative.

Notes: This error is a status result returned by the secondary index service routines. The caller of these routines may either ignore the error if it is expected or log an event if it was not expected.

Remedy: If this event was logged, contact your Support Representative.

 

 

Error No : 2812 Internal error: invalid record found on transient journal.

Explanation: An invalid record was found on the transient journal. The AMP which detects the error will remain offline.

Generated By: AMP System and Transaction Recovery.

For Whom: Site support representative.

Notes: This error usually results from an incorrect "Kind" field in the transient journal record header.

Remedy: Contact your Support Representative.

 

 

Error No : 2813 Internal error: bad InXaction flag in step header.

Explanation: The value of the InXaction flag in the step header was False (True) in a step that must be (must not be) in a transaction.

Generated By: AMP Steps.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2814 Data size exceeds the maximum specified.

Explanation: This status indicator is returned when the host side of host utilities specifies that it will accept n bytes of data and the AMP finds that there are more than n bytes to send.

Generated By: Host Utilities.

For Whom: Programmers.

Notes: This should never be seen by an end user or in a crash situation.

Remedy: Supply a larger max byte count and resend the parcel.

 

 

Error No : 2815 Apparent invalid restart of a restore.

Explanation: This error is returned when restarting a restore. It indicates that either the table was rebuilt by table rebuild, or was subject to a BUILD statement prior to the restore restart. This could cause data loss in the failed table.

Generated By: Host Utilities.

For Whom: End User.

Notes: This is a user error. An invalid sequence of restore operations was attempted, probably an invalid restart of a restore from the host.

Remedy: Use correct sequence of restores.

Error No : 2816 Auto CHECKTABLE mode found errors.

Explanation: This error indicates that CHECKTABLE encountered at least one error while validating the ALL TABLES.

Generated By: DBS Auto CHECKTABLE mode.

For Whom: SE/FE.

Notes: Auto CHECKTABLE mode is enable/disabled by the RcvACUTL console startable utility. When enabled, CHECKTABLE is automatically run on all tables immediately after startup has set up for transaction recovery (ie. voted and placed all required locks). To find out exactly which tables had errors, the auto CHECKTABLE mode should be disabled, the system should be restarted and CHECKTABLE should be run manually. Alternatively, if the debugger is running, a

GO AFTERTRAP will allow the system to continue and then a manual CHECKTABLE can be run. If the debugger is not running then this error does not cause the system to crash. The trace back is printed on the console but operation continues.

Remedy: See notes

 

 

Error No : 2817 Internal error: transaction not found in TIP table.

Explanation: A supposedly active transaction was not found in the Transaction In Process table on the AMP.

Generated By: AMP Steps.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2818 Invalid lock to dump table without after image journaling

Explanation: If the table to be dumped does not have after- image journaling, the USE GROUP READ LOCK option in the DUMP statement cannot be used.

Generated By: Dump.

For Whom: End User.

Remedy:

(1) Switch to USE READ LOCK option when dumping a table without after-image journaling, or

(2) ALTER TABLE for after-image journaling before dumping with USE GROUP READ LOCK option.

 

 

Error No : 2819 Internal error: unimplemented message received.

Explanation: A message was received that requested an unimplemented or unknown function.

Generated By: AMP worker tasks.

For Whom: Site support representative.

Notes: This is probably caused by a bad "Kind" or "Class" field in the message header.

Remedy: Contact your Support Representative.

 

Error No : 2820 Fallback reference index row is on the wrong AMP.

Explanation: Incorrectly distributed reference index rows are detected as the reference index subtables are traversed. The row is discarded from the remainder of the checking process.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 28Error No : 21 Internal error: invalid message kind in message header.

Explanation: A message with an unexpected "Kind" value in the message header was received.

Generated By: AMP worker tasks.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2822 Internal error: invalid message class in

message header.

Explanation: A message with an unexpected "Class" value in the message header was received.

Generated By: AMP worker tasks.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2823 Table id is inconsistent during restore operation.

Explanation: During a restore operation, a table id found on the archive data set was found to be inconsistent with other data on the archive or on the Teradata DBS being restored.

Generated By: Host Utilities.

For Whom: End User. Site support representative.

Notes: This indicates a problem with the dump tape, or an attempt to restore a database from one system to another system.

Remedy: Follow rules for restore operations or, if the rules have been followed, contact your Support Representative.

 

 

Error No : 2824 Database id is inconsistent during restore

Explanation: During a restore operation, a database id found on the archive data set was found to be inconsistent with other data on the archive or on the Teradata DBS being restored.

Generated By: Host Utilities.

For Whom: End User. Site support representative.

Notes: This indicates a problem with the dump tape, or an attempt to restore a database from one system to another system.

Remedy: Follow rules for restore operations or, if the rules have been followed, contact your Support Representative.

 

 

Error No : 28Error No : 25 No record of the last request was found after DBC restart.

Explanation: No record of the last request sent was found on the Teradata DBS after restart. The request may or may not have been rolled back. The user must determine if the request completed or not.

Generated By: System Recovery.

For Whom: End User.

Notes: This error is sent in response to a host status request from the TDP after a Teradata DBS restart.

Remedy: Resubmit the last request if it did not complete.

 

Error No : 28Error No : 26 Request completed but all output was lost due to DBC restart.

Explanation: The user’s last request completed, but all the output from the request was lost because the Teradata DBS restarted.

Generated By: System Recovery.

For Whom: End User.

Notes: This error is sent in response to a host status request from the TDP after a Teradata DBS restart.

Remedy: No action needed.

 

 

Error No : 28Error No : 27 Request was aborted by user or due to statement error.

Explanation: The last request and the transaction it was in was rolled back by a user abort or because of an error during processing of the statement. The cause of the rollback, however, has been lost because of a Teradata DBS restart.

Generated By: System Recovery.

For Whom: End User.

Notes: This error is sent in response to a host status request from the TDP after a Teradata DBS restart.

Remedy: If the rollback was not due to a user abort, correct the statement and resubmit the transaction.

 

 

Error No : 28Error No : 28 Request was rolled back during system recovery.

Explanation: The last request and its transaction was rolled back because it was in an active transaction during a Teradata DBS restart.

Generated By: System Recovery.

For Whom: End User.

Notes: This error is sent in response to a host status request from the TDP after a Teradata DBS restart.

Remedy: Resubmit the transaction.

 

 

Error No : 2829 Specified AMP does not exist.

Explanation: A processor number specified by the user in a specific-AMP(s) host utility operation does not correspond to that of a currently configured AMP.

Generated By: Host Utilities.

For Whom: End User.

Remedy: Resubmit the request with the correct processor number.

 

 

Error No : 2830 Unique secondary index must be dropped before restoring table.

Explanation: During a single-AMP restore of a nonfallback table, the table header on disk indicated the existence of a unique secondary index.

Generated By: Host Utilities.

For Whom: End User.

Notes: Because a single-AMP restore should always be preceded by an all-AMPs restore with the single AMP down, and because the unique secondary indexes on a nonfallback table are invalidated during such a restore, this error indicates a user error. Either the index was added after the AMP came back up (modifications should never be made to the database until the AMP is restored), the single-AMP restore was not preceded by an all-AMPs restore, or the single-AMP restore was not

preceded by an all-AMPs restore.

Remedy: The restore operation must be started over.

 

 

Error No : 2831 No row was found for the event in the Recovery Control Catalog.

Explanation: The event number specified by the host utility was not found in the Recovery Control Catalog table.

Generated By: Host Utility steps

For Whom: Site support representative.

Notes: This is a logic error in the Host Utility.

Remedy: Contact your Support Representative.

Error No : 2832 Unique secondary index violation on table %DBID.%TVMID during restore.

Explanation: During a restore operation, a duplicate unique secondary index was encountered.

Generated By: Host Utilities.

For Whom: End User.

Notes: This is the result of reapplying dump data sets in the incorrect sequence during a restore operation.

Remedy: Apply archive data sets in the correct  sequence during restore.

 

 

Error No : 2833 Row already exists with different content.

Explanation: During a restore operation, an attempt was made to restore a row that already existed, but whose data was different from that of the one being restored.

Generated By: Host utilities.

For Whom: End User.

Notes: This is probably caused by applying single- AMP dump tapes of the same data, but made at a different time.

Remedy: Use the correct sequence of archive data sets during the restore.

 

 

Error No : 2834 Another user released the lock requested by the current operation.

Explanation: While the current operation was waiting for a host utility lock, another user released all host utility locks on the specified object via the "override" option. The current operation was aborted.

Generated By: Host Utilities.

For Whom: End User.

Notes: This error is not returned to the user if the lock has already been granted when another user releases it.

No error is returned in this case.

Remedy: Resubmit the host utility operation.

 

 

Error No : 2835 A unique index has been invalidated; resubmit request.

Explanation: Unique secondary index for retrieval has been invalidated by a restore operation.

Generated By: AMP Steps.

For Whom: End User.

Remedy: Resubmit the request.

Error No : 2836 The specified index id was not found.

Explanation: The specified index id was not found in the table header.

Generated By: AwtLocID.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2837 Table being Fast/Multi Loaded; no data dumped.

Explanation: The table being dumped is in the process of being Fast/Mutli Loaded. No data rows are being dumped, just the table header.

Generated By: Dump.

For Whom: End User.

Notes: When the table is restored from this dump, it will be empty.

Remedy: If the data in the table must be backed up, complete the Fast Load and dump the database again.

Error No : 2838 Table is unhashed; no data dumped.

Explanation: The table being dumped is unhashed. No data rows are being dumped, just the table header.

Generated By: Dump.

For Whom: End User.

Notes: When the table is restored from this dump, it will be empty. Crash dumps that did not originate from a DUL load are the only tables that fall in this class.

Remedy: If it is necessary to save the data in the crash dump table, use the DUL utility.

Error No : 2839 Invalid attempt to operate on a fallback table.

Explanation: An attempt was made to restore a fallback table during an operation other than an all-AMPs restore of an all-AMPs dump.

Generated By: Restore.

For Whom: End User. Site support representative.

Notes: This error may indicate that

(a) a user was attempting to add fallback during the restore attempt (which is not valid), or

(b) there is an internal error in the Archive Utility software.

Remedy: If a concurrent attempt to add fallback is not the problem, identify the tables in the database that are nonfallback, and restore them via individual restore statements. If this fails, Contact your Support Representative.

Error No : 2840 Data rows discarded due to inconsistent hash codes

Explanation: During a restore operation, some rows were discarded because of inconsistencies in the row hash codes.

Generated By: Restore.

For Whom: End User. Site support representative.

Notes: Two situations cause this error to occur:

1) During an attempt to restore a row, a row with the same rowid but different data was found on the disk.

2) During a specific-AMP restore, the AMP received a data block containing a row that it does not own, even though reconfiguration has not taken place since the dump. The situation may be caused either by a software bug (the rows were mis-distributed when the dump was taken) or a user error (updating the table before the table was completely restored).

In either case, the restore continues unaffected, except that the offending rows are discarded. Associated with this error is a count of the rows discarded.

Remedy: If the error is caused by an operational error, start the restore process over or accept an incomplete table.

If there were no operational errors, contact your Support Representative.

 

 

Error No : 2841 A Utility lock was reapplied by recovery.

Explanation: During recovery, a Utility lock was reapplied. The text that accompanies this message describes the lock that was placed: either a single-AMP Host Utility lock or a lock placed by table rebuild. After Restore/Rebuild, you must EXPLICITLY use HUT/ARC to Release Locks.

Generated By: Recovery.

For Whom: Operator.

Remedy: If necessary, dump or restore the affected database or rebuild the affected table. Release the lock when no longer needed.

 

 

Error No : 2842 A utility lock was not reapplied by recovery due to conflict.

Explanation: During recovery, a Utility lock was not reapplied because of a conflict with some other utility lock. The text associated with this message describes the lock that was not reapplied.

Generated By: Recovery.

For Whom: Operator.

Notes: Normally, this error is caused by a global deadlock brought on when two operations attempt to place utility locks at the same time.

Remedy: If the error is due to a deadlock, release the locks and restart the conflicting operations.

 

 

Error No : 2843 No more room in database.

Explanation: This error occurs only when an attempt is made to increase the amount of space used by a database, and there is no space left to accommodate the increase.

Generated By: Archive Utility.

For Whom: End User.

Remedy: Either drop some of the tables currently contained in the database, or have the permanent space limit for the database increased.

Error No : 2844 Journal image is longer than maximum.

Explanation: This error occurs when a journal record is generated for an update, delete, or insert operation that is larger than the maximum allowable journal record.

Generated By: AMP Steps.

For Whom: End User.

Remedy: Reduce the number of fields being updated (if the error occurs on an update operation); reduce the size of the data rows being deleted by update operations against compressed or variable-length fields; or reduce the level of archive journaling on the table.

 

 

 

 

Error No : 2845 Shut down DBS and rebuild the entire disk.

Explanation: A disk read error was encountered. The bad data block cannot be rebuilt with the processor online.

This error is logged prior to a crash due to error ErrAMPDBErrSDown.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Use Diskcopy and Table Rebuild to recover the disk and then restart the Teradata DBS.

Error No : 2846 Unrecoverable read error detected. Retry.

Explanation: A disk read error is encountered. The bad data block cannot be rebuilt with the Teradata DBS on-line. This error is logged prior to a crash due to error ErrAMPURcvReadErr.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Manual intervention (table rebuild) or a restart may fix the problem.

 

 

Error No : 2847 Internal error: Invalid record found on transient journal.

Explanation: An invalid record was found on the transient journal. This error is logged just prior to a crash due to error ErrAMPIllTJRec.

Generated By: AMP System and Transaction Recovery.

For Whom: Site support representative.

Notes: This error usually results from an incorrect "Kind" field in the transient journal record header.

Remedy: Contact your Support Representative.

Error No : 2848 Invalid record type on transient journal.

Explanation: An invalid journal kind was specified or found on a journal. This error is logged just prior to a crash due to error ErrAMPInvJnlKind.

Generated By: AwtRcv.

For Whom: Site support representative.

Notes: This is an internal error. Transaction recovery detected an inconsistency on the transient journal, and recovery will continue to abort. To restart the system, shut down the offending processor and rebuild its disk off-line.

Remedy: Contact your Support Representative.

 

 

Error No : 2849 Invalid before image on transient journal.

Explanation: The row that a before journal has written does not exist in the database. This error is logged just prior to a crash due to error ErrAMPInvBefRow.

Generated By: AwtRcv.

For Whom: Site support representative.

Notes: This is an internal error. Transaction recovery detected an inconsistency on the transient journal Rebuild the offending processor’s disk.

Remedy: Contact your Support Representative.

Error No : 2850 User %USERID Session #### logical host id #### caused a DBS crash

Explanation: This message identifies the Teradata DBS user, the associated session and logical host id which caused a Teradata DBS crash. This message is displayed during Teradata DBS Startup.

Generated By: SSSMain.

For Whom: Operator.

Remedy: This message is for information only.

 

 

Error No : 2851 Internal error: inconsistent record found on Transient journal

Explanation: An attempt was made to read a PJ record using the rowid and tableid found from the TJ but the PJ row does not contain the ’correct’ information (i.e., transno and/or PJ RowKind is neither CkPtBeg or CkPtEnd).

Generated By: StpAAB.

For Whom: Site support representative.

Notes: This is an internal error.

Remedy: Contact your Support Representative.

Error No : 2852 Inconsistent check point records found on Restored journal.

Explanation: While restoring/validating a journal table, the event number for the same check point among different AMPs were found to disagree with each other.

Generated By: Restore, StpVJT.

For Whom: Site support representative.

Notes: This is an internal error.

Remedy: Contact your Support Representative.

 

 

Error No : 2853 Restored Journal table %TVMID does not exist.

Explanation: A restored journal table might not exist on an AMP if it came back online following a Teradata DBS crash during a rollback/rollforward operation.

Generated By: StpVJT.

For Whom: End User.

Remedy: Do a specific AMP restore of the journal table and then resubmit the rollback or rollforward request.

Error No : 2854 Specified checkpoint row does not exist in Journal table %TVMID.

Explanation: The checkpoint at which the recovery will terminate does not exist in the specified journal table during a rollback/rollforward operation.

Generated By: StpVJT.

For Whom: End User.

Remedy: Correct the checkpoint name in the rollback or rollforward statement and then resubmit the request.

Error No : 2855 Specified checkpoint row already exists.

Explanation: This could occur because of a Teradata DBS restart during a checkpoint operation.

Generated By: StpVJT.

For Whom: Host Utilities.

Notes: This error code is designed to be intercepted by a host utility and should never be seen by the end user.

Remedy: None required. The utility will handle the condition without user intervention.

 

 

Error No : 2856 The journal table %TVMID is being restored.

Explanation: This error occurs when a user issues a request for a journal table that is being restored.

Generated By: StpVJT.

For Whom: End User.

Remedy: Wait until the restore operation is completed, then resubmit the request. If a restore is not in process, the operation may have been aborted, and needs to be restarted or started over, or the table must be dropped.

 

 

Error No : 2857 Rollforward/Rollback: Not applicable on specified tables.

Explanation: This error occurs when a user issues a Rollforward/Rollback request to recover some data tables. The table names specified in the statement do not have an after journal for Rollforward or before journal for Rollback.

Generated By: StpMrL.

For Whom: End User.

Notes: A Rollforward operation is applicable only if the table to be recovered has an after image journal. A Rollback operation is applicable only if the table to be recovered has a before image journal.

Error No : 2860 Operation not allowed: %DBID.%TVMID was recovery aborted.

Explanation: This error occurs only when a user issues a request for a table that was recovery aborted.

Generated By: AMP Steps.

For Whom: End User.

Notes: The table does exist, but it was recovery aborted by some authorized personnel during system recovery. The content of this table is questionable.

Remedy: The table must be dropped and data recreated in some form (either via the Restore or FastLoad facility). The owner of this table should be informed of the situation.

 

 

Error No : 2861 Data inconsistency detected – Fallback rowid already in use

Explanation: This error is logged when an AMP attempts to insert a fallback row and the rowid is already in use.

Generated By: AMP Steps.

For Whom: DBA Site support representative

Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a software problem. Additional information is logged to identify the table and row in error. This often is accompanied by a ErrAMPDataCorr error being returned in response to a user request.

Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.

If the table has not been the target of improper recovery operations, contact your Support Representative.

Error No : 2862 Data inconsistency detected – Fallback row not found

Explanation: This error is logged when an AMP attempts to access a fallback row in order to update or delete it and the row is not found.

Generated By: AMP Steps.

For Whom: DBA Site support representative

Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a software problem. Additional information is logged to identify the table and row in error. This often is accompanied by a ErrAMPDataCorr error being returned in response to a user request.

Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.

If the table has not been the target of improper recovery operations, contact your Support Representative.

 

 

Error No : 2863 Data inconsistency detected – Data row not properly indexed

Explanation: This error is logged when an AMP attempts to update or delete a row and a secondary index or reference index entry for the row is not found.

Generated By: AMP Steps.

For Whom: DBA Site support representative

Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a software problem. Additional information is logged to identify the table, row and index in error. This often is accompanied by a ErrAMPDataCorr error being returned in response to a user request. If the error is reported against a non unique secondary index, the transaction rollback which may automatically be invoked as a result of the error may fix the indexing of the specific row. Other rows or other indexes for the same row may still be incorrect.

Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it. If the table has not been the target of improper recovery operations, contact your Support Representative.

Error No : 2864 Data inconsistency detected – Data row already indexed

Explanation: This error is logged when an AMP attempts to update or insert a row and a secondary index entry for the row already exists.

Generated By: AMP Steps.

For Whom: DBA Site support representative

Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a software problem. Additional information is logged to identify the table, row and index in error.  This often is accompanied by a ErrAMPDataCorr error being returned in response to a user request.

If the error is reported against a non unique secondary index, the transaction rollback which may automatically be invoked as a result of the error may fix the indexing of the specific row. Other rows or other indexes for the same row may still be incorrect.

Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.

If the table has not been the target of improper recovery operations, contact your Support Representative.

 

 

Error No : 2865 Data corruption detected in %DBID.%TVMID.

Explanation: The current request was aborted because the Teradata DBS detected internal inconsistencies in the table.

Generated By: AMP Software.

For Whom: End User.

Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a software problem. Often, another error (such as ErrAMPDupFBRId, ErrAMPMissFBRow, ErrAMPRowNotIdx or ErrAMPRowIdx) is logged on the Teradata DBS console which contains more information about the nature of the data

corruption.

Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.

If the table has not been the target of improper recovery operations, contact your Support Representative.

 

 

Error No : 2866 Table was Recovery Aborted; no data dumped.

Explanation: The table being dumped was Recovery  Aborted. No data rows are being dumped, just the table header.

Generated By: Dump.

For Whom: End User.

Notes: When the table is restored from this dump, it will be empty.

Remedy: The data in the table is inconsistent and cannot be used in any manner. The table should be restored or dropped and recreated.

 

 

Error No : 2867 AMP nnnn failed to recover permanent journal %DBID.%TVMID.

Explanation: Down Amp recovery has failed to recover the indicated permanent journal table. The journal table on AMP nnnn has been invalidated.

Generated By: System Recovery

For Whom: End User.

Remedy: The data in the table is inconsistent and cannot be used in any manner. This is an internal error. Contact your Support Representative.

Error No : 2868 This permanent journal table is damaged; no data dumped.

Explanation: Data in this permanent journal table has been corrupted.

Generated By: Dump.

For Whom: User.

Remedy: The probable cause was a system failure during a table rebuild of the specified journal table. The rebuild operation must be completed before the journal is usable.

Error No : 2869 Requested lock cannot be granted.

Explanation: The required lock cannot be granted.

Generated By: USVLock.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2870 Database lock on DBC.DBCInfoTbl prevented updates.

Explanation: A transaction read lock or higher was encountered on some AMP for DBC.DBCInfoTbl during system startup.

Generated By: SSSUINFO

For Whom: Operator.

Remedy: The lock, most likely a lock placed by recover, should eventually be released. The DBCInfoTbl table will not be updated until the next system restart.

 

Error No : 2871 Missing table header for DBC.DBCInfoTbl, updates bypassed.

Explanation: The table header for DBC.DBCInfoTbl is missing on some AMP.

Generated By: SSSUINFO

For Whom: Site support representative.

Notes: The receipt of this error indicates that the DBCInfoTbl table is corrupted.

Remedy: Contact your Support Representative.

Error No : 2872 Unexpected DBC.DBCInfoTbl format, updates bypassed.

Explanation: The DBC.DBCInfoTbl table does not have the expected format.

Generated By: SSSUINFO

For Whom: Site support representative.

Notes: The receipt of this error indicates that the DBCInfoTbl table is corrupted in some way.

Remedy: Contact your Support Representative.

Error No : 2873 Pending operation on DBC.DBCInfoTbl prevented updates.

Explanation: This table is in the process of being Fast Loaded Restored, or has been Recovery Aborted on  some AMP.

Generated By: SSSUINFO

For Whom: Site support representative.

Notes: Since tables in the DBS database can not be the target of a Recovery Abort or a Fast Load operation, and proper user of Restore will not leave a table in DBS in the ’restoring’ state, this error should never be encountered.

Remedy: Contact your Support Representative.

 

 

Error No : 2874 A read error occurred in a permanent journal table.

Explanation: A disk read error occurred in a permanent journal table. Refer to the accompanying Error No : 2538 error message for the permanent journal table id. The bad data block cannot be rebuilt automatically by the Teradata DBS. Manual intervention is required. This error is logged prior to a crash due to error ErrAMPPJReadErr.

Generated By: RbkCtrl.

For Whom: Operator. DBA. Site support representative.

Remedy: The permanent journal table must be rebuilt. If any user table which journals to this permanent journal table is not defined as dual image, then there will be loss of data in the permanent journal table during the table rebuild. Contact your Support Representative.

Error No : 2875 Task Lock cannot be granted – resource busy

Explanation: A Task Lock for a particular row hash or row hash range for a particular subtable is locked by another task and the requesting task does not want to wait for the resource.

Generated By: AwtTLGAl.

For Whom: Site support representative.

Notes: This is an internal condition that is handled internally. It should not cause a crash or be reported to a user.

Remedy: Contact your Support Representative.

 

 

Error No : 2876 AMP was not brought online.

Explanation: An AMP could not be brought into deferred catchup so it was put into offline recovery instead. There are several reasons why the system choose to do this, the text which follows the message should describe the factors that governed this decision.

Generated By: RcvSLUCM.

For Whom: SE/FE.

Notes: This message is logged during a restart for each processor in offline recovery. This is to help the user understand why the AMP was not brought into the configuration.

An AMP in offline recovery is not part of the DBS configuration, ie. it is logically down.

An AMP in deferred recovery is part of the DBS configuration.

An AMP is placed into deferred catchup for any of the following reasons:

1) The AMP has not completed local transaction rollback. This means that the AMP has not rolled back/completed all work that was in progress when it went down. It must also complete any deferred recovery sessions contained on it at the time it went down.

2) The number of change row journal entries summed across all AMPs in the cluster exceed some threshold. This means that the number of rows requiring updating is too great.

3) At least one long running ordered systems change journal entry needs to be processed. Long running records include saving a dump, rebuilding a table or PJ, etc..

4) A HUT lock may exist in the cluster. This means either that a HUT lock is currently held in the cluster and/or a ordered systems change journal set HUT lock record remains to be processed.

Remedy: Allow offline recovery to catch the AMP up to a point where the deferred catchup rules are met and then restart the system to place the AMP into deferred catchup. In the case of rule #4, you may need to release the HUT lock manually. The RCVMANAGER console startable utility can tell when the rules have been meet. The RESTART,COLDWAIT option can be used to guarantee that the AMP is brought online.

Error No : 2877 Table Rebuild procedures required to recover AMP.

Explanation: A disk read error was encountered while executing a recovery function. The bad data block cannot be rebuilt with the processor on-line. The AMP which detects the error will remain offline. This error is logged prior to a crash due to error ErrAMPRCErrSdown.

Generated By: RbkCtrl.

For Whom: Operator. DBA.

Remedy: Run Table Rebuild to recover the failing table and then restart the Teradata DBS.

Error No : 2878 Improper character set name %VSTR.

Explanation: This error occurs at the time when character sets are first installed as the DBS starts. The name coding convention has been improperly used.

Generated By: AMP.

For Whom: Operator. DBA.

Remedy: Correct the character set name in error to the proper convention. Reinstall the character set tables with the correct name. Restart the DBS software.

Error No : 2879 Cannot install Charset. DBS is not Kanjienabled.

Explanation: The Hash Function value in the DBSControl Record does not allow installation of this character set. This applies to Kanji character sets when the Hash Function does not indicate Japanese Localization.

Generated By: AMP.

For Whom: Operator. DBA.

Remedy: Go through Sysinit procedure to change Hash Function value.

 

 

Error No : 2880 Reference index row indexes non existent  data row.

Explanation: The Foreign Key value contained in the reference index row was found in the corresponding primary data subtable. However, the reference index row indicates that there should be N data rows with that Foreign Key value but we only found M data rows where M N.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2881 Foreign Key value is not found in any reference index row.

Explanation: The Foreign Key value in the primary data subtable was not found in the corresponding reference index subtable.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2882 Data row is not indexed by reference index row.

Explanation: The Foreign Key value contained in the primary data subtable was found in the corresponding reference index subtable. However, the reference index row indicates that there should be N data rows with that Foreign Key value but we found M data rows where N M.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2883 Fallback reference index row is missing.

Explanation: The reference index subtable is fallback. However, there is a primary reference index row which has no corresponding fallback reference index row.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2884 Primary reference index row is missing.

Explanation: The reference index subtable is fallback. However, there is a fallback reference index row which has no corresponding primary reference index row.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2885 Reference index row hash code is incorrect.

Explanation: A primary (or fallback if an AMP is down) reference index row has incorrect hash code. The hash code is not corrected in the remainder of the checking process.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2886 Reference index row has duplicate Foreign Key values.

Explanation: A primary (or fallback if am AMP is down) reference index row has the same Foreign Key value as another row in the same hash code. The row is not ignored in the remainder of the checking process.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2887 Primary and fallback reference index rows do not match.

Explanation: A mismatch is detected when the primary copy of a reference index row is compared to its fallback copy byte by byte.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2888 Invalid reference index row.

Explanation: The Foreign Key contained in the reference index row was not found in the referenced table (i.e. this particular Foreign Key value should have caused referential constraint violation).

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2889 Table header has incorrect parent count or child count.

Explanation: The parent(child) count in the table header does not agree with the number of reference index descriptors in the table header with ChildEntry field sets to false(true)).

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

Error No : 2890 Dictionary child count does not match header child count.

Explanation: This message is displayed if the child count field in the table header does not match the corresponding child count in the DBC.TVM record for the table.

Generated By: CheckTable

For Whom: Site support representative

Remedy: Contact your Support Representative.

 

 

Error No : 2891 %VSTR not found for %DBID.%TVMID.

Explanation: The Work Table or Error Table was likely dropped by a concurrently running job that was using an identically named table.

Generated By: Amp Software.

For Whom: User.

Note: Like ErrAMPWTETMissing, the accompanying error message will indicate the MLOAD resource table that has been dropped. Unlike ErrAMPWTETMissing however, there is no restart involved, and it is not generated by STPEBE.

Remedy: To avoid this error, ensure that all MLOAD resource table names are unique across jobs that may be run concurrently. To recover from this error, drop the remaining MLOAD resource tables, perform the required Target Table

recovery, then re-submit the job.

Error No : 2892 Null value eliminated in set function

Explanation: The user tried TO perform set FUNCTION on a column which has one OR more null values.

Generated By: AGR modules.

For Whom: END User.

Remedy: None.

Error No : 2893 Right truncation of string data.

Explanation: The user tried to assign a longer to a shorter string destination.

Generated By: EVLUTIL

For Whom: END User.

Remedy: None.

Error No : 2894 The cursor spool row specified is invalid.

Explanation: The spool row identifier sent by the application in the cursor parcel is invalid.

Generated By: AMP Steps.

For Whom: User.

Remedy: Resubmit the updatable cursor update or updatable cursor delete with the correct spool row identifier.

 

 

Error No : 2895 The current cursor row has already been deleted.

Explanation: The user has deleted the current cursor row and is trying to update/delete the same row again.

Generated By: SutSpCsr.

For Whom: User.

Remedy: None.

Error No : 2897 Table header row for %DBID.%TVMID is too long.

Explanation: The table being created or altered causes the table header row to exceed 64K row size limit. This can happen if the table has defined with 2048 columns and secondary indexes each consists of 64 columns and referential constraints each consists of 64 columns Foreign Key or table has more compress columns. If we get this error during the migration process, which indicates that the Table header row size is exceeding the 64K limit on target platform. This can happen while

migrating the data from 32-bit platform to 64-bit platform.

Generated By: StpCIX, StpMTB, StpCRI.

For Whom: End User.

Remedy: Contact your Support Representative.

 

 

Error No : 2898 Fallback reference index row is in the wrong subtable.

Explanation: Incorrectly distributed reference index rows are detected as the reference index subtables are traversed. The row is discarded from the remainder of the checking process.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2899 Reference index row contains non existent Foreign Key value.

Explanation: The Foreign Key value contained in the reference index row was not found in the corresponding primary data subtable.

Generated By: CheckTable.

For Whom: Site support representative.

Remedy: Contact your Support Representative.

 

 

Error No : 2900 An informative event was logged.

Explanation: The specific information is encoded within the event message (for example, "Configuration is operational").

Generated By: DBS Startup.

For Whom: Operator.

Remedy: This message is for information only.

Error No : 2901 Cannot install CharSet: Invalid ID

Explanation: The CharSet is one of the special character sets defined in the system table DBC.Translation. This error means that an attempt was made to install a CharSet with an invalid ID value.

Generated By: SSSMain (System startup)

For Whom: DBA Site support representative

Notes: When this error occurs during normal system startup, the error message logged on the console will identify both the name of the CharSet and the offending ID.

Remedy: Update DBC.Translation to use only valid ID’s. A valid ID is between EvlUserMinChar and EvlUserMaxChar, or between decimal values 65 and 1Error No : 26.

 

 

Error No : 2902 Cannot install CharSet: Non-unique ID

Explanation: The CharSet is one of the special character sets defined in the system table DBC.Translation. This error means that an attempt was made to install two or more CharSets with the same ID value.

Generated By: SSSMain (System startup)

For Whom: DBA Site support representative

Notes: When this error occurs during normal system startup, the error message logged on the console will identify both the name of the CharSet and the offending ID.

Remedy: Update DBC.Translation so all installed ID’s are unique.

 

 

Error No : 2903 Cannot install CharSet: Exceeded max

Explanation: The CharSet is one of the special character sets defined in the system table DBC.Translation. This error means that an attempt was made to install more CharSets than the maximum number allowed by  the system.

Generated By: SSSMain (System startup)

For Whom: DBA Site support representative

Notes: When this error occurs during normal system startup, the error message logged on the console will identify both the name of the CharSet and the maximum number.

Remedy: Update DBC.Translation so that the number of installed CharSets does not exceed the maximum given by constant SysMaxUserTranslations (initially 6).

 

 

Error No : 2904 NVRAM is disabled in the system.

Explanation: NVRAM is equipped but disabled on all AMPs in the configuration.

Generated By: SSSMain or SSSSPF.

For Whom: DBA Site support representative.

Notes: This is a warning more than an error. It should not cause a crash, but should be reported to a user.

Remedy: Enable NVRAM on all AMPs.

Error No : 2905 Status of NVRAM differs among AMPs.

Explanation: Not all AMPs have the same NVRAM status, or a late joining AMP’s NVRAM status differs from the rest of the system.

Generated By: SSSMain or SSSSPF.

For Whom: DBA Site support representative

Notes: This is a warning rather than an error. It does not cause a crash, but should be reported to a user.

Remedy: Make NVRAM status consistent across AMPs.

Error No : 2906 Multiple restores had mismatching  RESTORE FALLBACK options.

Explanation: During a sequence of all-AMP restores of a fallback table, some restores used the RESTORE FALLBACK option while the current one did not, or vice-versa.

Generated By: Host Utilities.

For Whom: End User.

Remedy: All restores of the same tables must use the RESTORE FALLBACK option, or all must not use this option. If the preceding restores did use the option, then correct the current one by using the RESTORE FALLBACK option. If the preceding did not use the RESTORE FALLBACK option, then remove it from the current restore.

 

 

Error No : 2907 The recovery configuration has changed.

Explanation: During a restore, rollforward or rollback operation using the primary data option upon a fallback table, or during a build operation upon a fallback table, the DBC configuration which existed during the initial cluster restore of the of the fallback table has changed.

Generated By: Host Utilities.

For Whom: End User.

Remedy: If an AMP was brought back online, then take the AMP offline again. If this is not reasonable, the repeat the restore of the AMP’s cluster for the fallback table. If an AMP was taken offline, then the restore of the AMP’s cluster must be repeated for the fallback table. If the error occurred during an all-AMPs restore operation of a cluster dump then the entire restore process must be repeated.

Error No : 2908 Specified Cluster does not exist.

Explanation: A cluster number specified by the user in a cluster-level host utility operation does not correspond

to that of a currently configured cluster.

Generated By: Host Utilities.

For Whom: End User.

Remedy: Resubmit the request with the correct cluster number.

Error No : 2909 The restored journal already exists on the specified AMP

Explanation: The restored permanent journal already exists upon one or more AMPs referenced in a specific- AMP Host Utilities permanent journal restore.

Generated By: HutRDB

For Whom: User.

Remedy: The restored journal must be deleted to perform the requested restore operation. This may be achieved by using the Delete Restored Journal Host Utilities statement.

 

 

Error No : 2910 The journal to restore does not match the  one for

Explanation: A database references a different permanent journal table than the one being restored.

Generated By: HutInr

For Whom: User.

Remedy: If the journal being restored is the one that is wanted, drop the journaling in the database. Otherwise, the restore must be done from a different archive data set.

 

 

 

Error No : 2911 A specific-AMP restore specified more than the maximum sessions.

Explanation: A specific-AMP restore may specify no more than sixteen sessions per AMP. This value was exceeded.

Generated By: HutSTbl

For Whom: User.

Remedy: Correct the number of sessions in the SESSIONS= parameter of the Host Utility program. This number should be an even multiple of the AMPs involved in the restore process.

Error No : 2912 Permanent Journaling is inconsistent for a table being restored.

Explanation: Restore found a table that references a permanent journal which no longer exists.

Generated By: HutRecvy

For Whom: User.

Notes: When restoring a data table, a dictionary row for the data table contained a reference to a non-existent permanent journal.

Remedy: The only way to restore the table is to restore the journal first. Since the journal does not exist, the journal restore must be preceded by a restore of database DBC.

 

 

Error No : 2913 A specific-AMP recovery was executed out of order.

Explanation: A specific-AMP rollback or rollforward was attempted on a nonfallback table with unique secondary

indexes.

Generated By: HutRecvy

For Whom: User.

Notes: A specific-AMP rollback or rollforward of nonfallback tables with unique secondary indexes should never happen. If a rollforward then it should have been preceded by either a restore (if recovering from a hardware failure) or by an all-AMPs rollforward if recovering from some other error. Either of these actions would invalidate any unique secondary indexes on the table. If  a specific-AMPs rollback is being attempted then it should have been preceded by an all-AMPs rollback.

Remedy: Resubmit the Utility actions in the sequence described above. Note that dropping the index will cause the structure version of the table to be changed. A rollforward or rollback is not allowed across a structure change.

 

 

Error No : 2914 A TIP/Task Matchup failure has occurred.

Explanation: A terminating task’s transaction table has an erroneous task list.

Generated By: AwtTIPSt/AwtInfi

For Whom: Site support representative.

Notes: This error indicates that AMP software has detected an internal inconsistency of some sort. Determination

of the cause of the error requires analysis by your Support Representative.

Remedy: Contact your Support Representative.

Error No : 2915 The journal for the updated table does not exist

Explanation: An update operation was specified against a data table which references a permanent journal table that does not exist.

Generated By: AtcLgIni.

For Whom: User.

Remedy: The Database containing the journal table was probably restored, but the journal itself was not.