Teradata SQL Error and Failure Codes from Error 9000 To 9016

SQLServerF1_Header_Small

9000 Operation not allowed: the target table is being online archived.
Explanation: A request to restore/rollforward/rollback/archive the target table while it is currently in the middle of
another online archive job.
Generated By: Hut Control Segment procedure HcsInTbl
For Whom: End User
Notes: Online Archive places NO lock on the target table.
Remedy: Corrective actions include: – Verify that the restore/rollforward/rollback job is not submitted on the table that
is in the middle of online archive job. – Verify that only 1 online archive job is running concurrently for a given table.

9001 Operation not allowed: the target table is being restored.
Explanation: A request to online archive the target table while it is currently in the middle of a restore/rollforward/rollback
job.
Generated By: Hut Control Segment procedure HcsInTbl
For Whom: End User
Notes: Online Archive places NO lock on the target table. This scenario could happen if the target table is logging active
and a job to archive the table right after its preceding restore/rollforward/rollback job on the same table.
Remedy: Corrective actions include: – Verify that no online archive job is running concurrently with a restore/rollforward/
rollback job for a given table.

9011 Table being Archived/Restored/Copied was dropped by some other transaction.
Explanation: The table that is being Archived/Restored/Copied has been dropped by some other transaction. This can
happen when the HUT Lock is released using RELEASE LOCK statement allowing for Drop Table.
Generated By: ModifyTblHdr.
For Whom: End Users.
Remedy: This is a user error. User must not release the HUT LOCK and drop table while Arc/Restore/Copy is in progress.

9012 Operation skipped due to the table/index has containing down regions or was marked down.
Explanation: The table/index that is being Archived has containing down regions or if any of its data or index subtables
are marked down. The dump operation will skip.
Generated By: HUT.
For Whom: End Users.
Remedy: Corrective actions include: – Run checktable utility at level 3 to identify possible table corruption. – Repair the
down regions or reset the down status of the table/index or, – Restore the down table/index status before archive opearion.

9013 Invalid alternate parcel header sent by host.
Explanation: This error is returned for following cases:
1) ARCMAIN needs to user the Alternate Parcel Header (APH) in 13.1. If no HUT request is sent by client using the APH,
this error is returned.
2) The alternate parcel header has 2 reserved bytes following the parcel flavor that must be set to 0. If this is a non zero
value, this error is reported.
Generated By: HUT subsystem.
For Whom: Support Representative.
Remedy: Ensure that the ARCMAIN software is compatible with the DBS
ARCMAIN must submit all requests using the alternate parcel header format or handle the error code received.

9014 Journal Data migration is not supported when the source system is from an older release.
Explanation: Journal data is used for Roll Forward operations after restore/copy. When the source data was generated
from previous major release, journal data migration is not supported by DBS.
Generated By: HUTRDB module .
For Whom: End User.
Remedy: When the source data was archived from previous major release, take full dump on source system and migrate
to Target System. On target system empty journal tables will be created. As we are taking whole dump on source system,
journal data is not required.

9015 Invalid variable length object name in parcel.
Explanation: Object names in some HUT parcels are referenced using and offset and length to a variable length area at
the end of the parcel. This error is returned for the following inconsistencies.
1) The length of the object name sent by ARCMAIN is greater than the maximum length expected (120 bytes as of release
13.1).
2) The offest plus length of the object name sent by ARCMAIN is greater than the parcel length.
As of release 13.1, the following parcels may encounter this error:
PCLHUTINSROW PCLHUTEVT PCLHUTRECVY
Generated By: HUT subsystem.
For Whom: Support Representative.
Remedy: Ensure that the ARCMAIN software is compatible with the DBS.

9016 Invalid variable length dataset name in parcel.
Explanation: Dataset names in some HUT parcels are referenced using
and offset and length to a variable length area at the end of the parcel. This error is returned for the following inconsistencies.
1) The length of the dataset name sent by ARCMAIN is greater than the maximum length expected (176 bytes as of release
13.1).
2) The offest plus length of the dataset name sent by ARCMAIN is greater than the parcel length.
As of release 13.1, the following parcels may encounter this error:
PCLHUTINSROW PCLHUTEVT PCLHUTRECVY
Generated By: HUT subsystem.
For Whom: Support Representative.
Remedy: Ensure that the ARCMAIN software is compatible with the DBS.

Above are list of Teradata Errors or Failure Codes from Error 9000 To 9016 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *