Restart Log File Size Limit - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

Even though a Restart of Teradata ARC is only supported on mainframe systems, the Restart Log in integral to arcmain's operations and is therefore still used by arcmain on all supported platforms. When using 32-bit versions of arcmain, the 32-bit version of the 'C' library is compiled into the arcmain executable file and it may limit the size of the files (including the Restart Log) that arcmain creates to 2GB in size. If the Restart Log exceeds this size, you may get the following error message when arcmain tries to write another record to the Restart Log:

 *** Internal Failure ARC0001:NO DATA ARE WRITTEN TO 'DBCLOG'. 

Reaching the 2GB file size limit will cause your arcmain job to abort. The ARC0001 error message is a generic message that can be generated by many different error conditions. To determine if the 2GB file size limit is the cause of your particular error, look at the size of your Restart Log file to see if it has reached the 2GB threshold. The size of the Restart Log is dependent on how many objects are being processed. Therefore, one work-around to this 2GB file size limit is to break up your archive/copy/restore job into smaller pieces so that each piece processes fewer objects, thus requiring a smaller Restart Log. If you are executing a 32-bit version of arcmain on a 64-bit machine, another work-around is to switch to the 64-bit version of arcmain, which is compiled with the 64-bit version of the 'C' library. The 64-bit version of the 'C' library should allow for files larger than 2GB in size. Note that using the 64-bit version of arcmain is not possible on a 32-bit machine.