The issue was a job failed that left Logging Online Archive on a number of tables on one of the Teradata databases.
First step was to identify the tables affected, which can be found one of two ways.
One way is to query the DBC.ArchiveLoggingObjsV view in Teradata SQL Assistant.
select * from DBC.ArchiveLoggingObjsV;
The other way is to find the tables by running the CheckTables utility. Click HERE to go to a post on how to run the check table utility. The results displayed show three tables have Logging Online Archive on.
RESOLUTION:
Start a vi session to create a script that will remove Online Archive Logging found on tables.
The script is going to need user & password with enough access to log on to the Arcmain utility. Teradata Express is used in this example, so the dbc account is being used. Recommended using another account with enough permissions.
A line for each table will be need to remove Online Archive Logging. The OVERRIDE parameter will be needed in each statement.
Paste or write the script in the vi session, then save & close.
.LOGON 127.0.0.1/dbc,dbc ; LOGGING ONLINE ARCHIVE OFF FOR (RETAIL.CLIENT), OVERRIDE; LOGGING ONLINE ARCHIVE OFF FOR (RETAIL.ITEM), OVERRIDE; LOGGING ONLINE ARCHIVE OFF FOR (RETAIL.PRODUCT), OVERRIDE; .LOGOFF;
To execute the arcmain script, type arcmain then the less then sign then the script name (no double quotes). In testing adding spaces did not hurt the execution.
arcmain < "script name" example: arcmain < stop_archive_logging.arc
Arcmain may take a minute to get started. When successful, arcmain will display severity of 0 when completed. Requery DBC.ArchiveLoggingObjsV or rerun CheckTable to verify. Then as a security precaution, remove the password from the script, if planned to be saved & reused.
