Previous	Next		Contents	Index	Navigation	Glossary	Library

Status messages are inserted into the log table as different events in the Archive/Purge process take place, such as starting or completing a module. The modules that make up the Archive/Purge process are submitted by a 'control module' which produces many of the generic status messages.

Error messages are inserted into the log table when a module fails. You can then use the error messages to help you restart the correct programs and avoid repeating processes which completed successfully.

Monitoring Your Archive/Purge

During processing of any Archive/Purge run, multiple concurrent requests will be submitted. For example, if you submit the Archive-Preview, there will be a parent concurrent request for the control module, named Archive-Preview. This request will submit requests for the selection and validation process, for the archive, for the report, and so on. These child requests are submitted sequentially, so you can monitor the progress of your Archive/Purge by ensuring each child request completes successfully. When all child requests have completed successfully, all the messages in AR_ARCHIVE_PURGE_LOG are written to the report output file of the parent request.

If you want to monitor the progress of each request more closely, you can access the AR_ARCHIVE_PURGE_LOG table directly using SQL*Plus. Use the following commands to write the contents of the log table to a file titled log.lst in the directory where you logged on to SQL*Plus:

spool log

COLUMN MESSAGE format A50

select MESSAGE, TIME

from AR_ARCHIVE_PURGE_LOG;

spool off

You can then review this file to check your progress.

You will also need to access the log table directly if one of your concurrent requests fail. You can access AR_ARCHIVE_PURGE_LOG to see what the last message in the table is. This will be the final error message inserted before the program failed. You can match this error against the list of error messages below to determine your next course of action.

If there is a problem with your concurrent manager you can view the status of each concurrent request by accessing the AR_ARCHIVE_CONTROL table. Use the following commands to create a file containing status information for the current Archive/Purge run titled control.lst, in the directory where you logged on to SQL*Plus:

spool control

select request_id, status

from AR_ARCHIVE_CONTROL

WHERE archive_id = '<current archive_id in the format YYMMDDHHMMSS>';

spool off

Refer to the table descriptions later in this essay for more information on how these tables are populated.

Status and Error Messages

Control module status messages:

Message	Message Description
The following message is used each time the control module starts a new program
AR_ARCHIVE_ CONT_START	Starting the <program_name>
The following message appears as the control module calls each child program
AR_ARCHIVE_ SUB_START	Calling <program_name> process
The following message appears as the control module submits a concurrent request for each child program
AR_ARCHIVE_ REQ_SUB	Submitted concurrent request <request_id>
The following message returns the status of the above request.
AR_ARCHIVE_ REQ_TERM	Request: <request_id> Completed/Errored
The following message appears if the above returns an error. It will be the last message in the file if there is an error and will return the 'technical' error code. For example: PL*SQL error. Contact your system administrator or support if you receive this message.
AR_ARCHIVE_ ERROR	<function_name> <error_message> <error_code>
The following message is the last message for each child process called.
AR_ARCHIVE_ SUB_COMP	<program_name> process complete
The following message appears at the very end, when everything completes
AR_ARCHIVE_ CONT_COMP	Completed the <program_name>
Table 1 - 168. (Page 1 of 1)

Selection module status messages:

Message	Message Description
AR_ARCHIVE_START_SEL	Starting Data Selection...
AR_ARCHIVE_PUR_INT	Purging interim and auxiliary tables
AR_ARCHIVE_RETR_TRX	Retrieving transactions
AR_ARCHIVE_TRX_LOAD	Loaded <count> Transactions into AR_PURGE_TRX_AUX
AR_ARCHIVE_RETR_REC	Retrieving receipts
AR_ARCHIVE_REC_LOAD	Loaded <count> Receipts into AR_PURGE_REC_AUX
The following messages print every 10,000 lines.
AR_ARCHIVE_COUNT	Loaded <count> rows into auxiliary tables
AR_ARCHIVE_COMP_SEL	Data selection complete
The following messages appear if PA is installed.
AR_ARCHIVE_CONTEXT	Oracle Project Accounting context is <PA_transaction_flexfield_context>
AR_ARCHIVE_START_CYC	Validating data
AR_ARCHIVE_COMP_CYC	Validation complete
AR_ARCHIVE_INS_INT	Inserting into AR_ARCHIVE_PURGE_INTERIM
Table 1 - 169. (Page 2 of 2)

Archive module status messages:

Message	Message Description
AR_ARCHIVE_ ARC_START	Archiving...
AR_ARCHIVE_ ARC_TRX	Archiving transaction id range: <id_low> to <id_high>
AR_ARCHIVE_ ARC_TRX_C	Finished archiving transaction id range: <id_low> to <id_high>
AR_ARCHIVE_ ARC_COMP	Archive Complete
AR_ARCHIVE_ REP_START	Running archive report
AR_ARCHIVE_ REP_COMP	Archive report complete
Table 1 - 170. (Page 1 of 1)

Purge module status messages:

Message	Message Description
AR_ARCHIVE_PUR_START	Purging...
AR_ARCHIVE_PUR	Purging Transaction/Receipt/Batch_ID range: <id_low> to <id_high>
AR_ARCHIVE_PUR_C	Finished purging Transaction/Receipt/Batch_ID range: <id_low> to <id_high>
AR_ARCHIVE_PUR_COMP	Purge Complete
Table 1 - 171. (Page 1 of 1)

Error Messages: The messages in the following table are generic error messages that are used for more than one error situation where noted. When you submit the Archive/Purge programs, records in the following tables are deleted as indicated.

• AR_PURGE_TRX_AUX

• Records in this table are deleted before Archive-Preview and Archive and Purge.

• AR_PURGE_REC_AUX

• Records in this table are deleted before Archive-Preview and Archive and Purge.

• AR_ARCHIVE_PURGE_INTERIM

• Records in this table are deleted before Archive-Preview and Archive and Purge.

• AR_PURGE_OE_EXCEPTIONS

• Records in this table are deleted before Archive-Preview and Archive and Purge.

• AR_ARCHIVE_PURGE_LOG

• Records in this table are deleted before Archive-Preview and Archive and Purge.

• AR_ARCHIVE_HEADER

• Records in this table are deleted before Archive-Restart.

• AR_ARCHIVE_DETAIL

• Records in this table are deleted before Archive-Restart.

• AR_ARCHIVE_CONTROL_DETAIL

• Records with the current archive_id are deleted before Archive-Restart.

See Also

Preparing to Run Archive and Purge

Archive and Purge Cycle

Purge Criteria

Tables Purged

Archive Level

Data Not Archived