Teradata SQL Error and Failure Codes from Error 8225 To 8235

SQLServerF1_Header_Small

8225 Missing checkpoint begin row.
Explanation: A checkpoint end row that has no associated checkpoint begin row was found while dumping the journal.
Generated By: HutJnlRd.
For Whom: Teradata FE.
Remedy: This indicates that the saved part of the permanent journal has been corrupted, possibly during down AMP
recovery or journal rebuild.
The journal cannot be dumped.
Delete the saved journal to eliminate the problem.

8226 Missing checkpoint end row.
Explanation: A checkpoint begin row that has no associated checkpoint end row was found while dumping the journal.
Generated By: HutJnlRd.
For Whom: Teradata FE.
Remedy: This indicates that the saved part of the permanent journal has been corrupted, possibly during down AMP
recovery or journal rebuild.
The journal cannot be dumped.
Delete the saved journal to eliminate the problem.

8227 Tables in the APPLY TO list were not copied
Explanation: No tables in the apply to list were copied and therefore may not be the subject of an APPLY TO list.
Generated By: StpAlt Amp procedure.
For Whom: End User.
Remedy: Resubmit the job with correct list of data tables in the APPLY TO list.

8228 DBS software cannot convert this dictionary schema.
Explanation: DBS AMP software has not been upgraded to a level that allows it to restore data from the current archive
because the format of system dictionary tables are inconsistent with the current system dictionary tables.
Generated By: HUTINR and HUTRDB Amp procedures and DSMain.
For Whom: End User.
Remedy: 1) ANALYZE the archive to determine the “System Internal Format” number (if the number is NOT printed
out, then try to determine the DBS software release level that created archive). FOR DSA, you can run the job with INFO
logging level and look at the BARLog file to see the Source System Format. 2) Determine the current DBS software release
level. 3) Contact software support to see if there is a level of DBS software that will allow you to restore this archive. There
may or may not be.

8230 Tried to re-hash data when table header in wrong state
Explanation: During a restore operation, it was discovered that the table header row was not properly set up to indicate
the table was in a restore state that required re-hashing of the data. This is probably indicative of some kind of software
error.
Generated By: HUTRDB Amp procedure.
For Whom: Support Representative/System Administrator.
Remedy: Contact software support and explain the scenario.

8231 Tried to re-hash journal/index block
Explanation: During a restore operation, it was discovered that a block of either permanent journal or secondary index
rows were sent to the DBS when re-hashing of the data was required. This is probably indicative of some kind of software
error.
Generated By: HUTRDB Amp procedure.
For Whom: Support Representative/System Administrator.
Remedy: Contact software support and explain the scenario.

8232 Cannot build re-hashed table with AMP off-line
Explanation: Non-fallback protected tables cannot be built when an AMP is off-line if the rows need to be re-hashed.
Rows can be initially loaded but they cannot be properly re-hashed and sorted until all AMPs are up.
Generated By: HUTBLD Amp procedure.
For Whom: End User.
Remedy: The utility will report the error and skip to the next table to be processed. Later, you need to bring the bad AMP
back on-line and perform an explicit BUILD NO FALLBACK operation.

8233 Invalid table state for build sort request
Explanation: The table states among the AMPs are inconsistent when processing the build sort request. It happens when
more than one AMP has been rebuilt before restore completed.
Generated By: Host Utilities.
For Whom: End User.
Notes: This is an error related to system administration. Someone might have rebuilt more than one AMP before the
restore is complete.
Remedy: The build sort request cannot be processed. The user must restore the table from the beginning.

8234 Restore cannot be restarted on Multiset table
Explanation: Restore will be aborted, if a restart occurs during a restore/copy of a MULTISET table when an archive and
restore have either different hash buckets or different configuration.
Generated By: This error code is generated by HUTRDB Amp procedure.
For Whom: End User.
Remedy: The table for which this error is returned needs to be copied or restored from the beginning.

8235 Journal Data migration is not supported when Source and Target Systems have different Row
Formats.
Explanation: Journal data is used for Roll Forward operations after restore/copy. When Source and target systems have
different row formats, journal data migration is not supported by DBS.
Generated By: HUTRDB module .
For Whom: End User.
Remedy: When source and target systems have different row formats, 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.

Above are list of Teradata Errors or Failure Codes from Error 8225 To 8235 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 *