ReSA RTLOG File Movement (Doc ID 2767426.1)

Last updated on OCTOBER 17, 2023

Applies to:

Symptoms

Saimptlog batch does not moving the ReSA RTLOG file when file is corrupt to reject directory.
The corrupt file is kept in the same /u01/retail/rms/data/in , only it is renamed adding .1.2 at the end eg RTLOG_xxxx.DAT.3.3.3.3 and the next batch run, it fails again.

EXPECTED BEHAVIOR
-----------------------
Expected result if ReSA comes across a corrupted/invalid RTLOG file:
The invalid RTLOG file is automatically moved to the reject folder.
ReSA continues processing of valid RTLOG files.

Steps to  reproduce:

1. Filewatcher moves the file from Incoming SFTP folder to /u01/retail/rms/batch/incoming.
2. Then batch wrapper scripts take the completed files from /u01/retail/rms/batch/incoming and moves them to /u01/retail/rms/data/in
3. Similarly, batches generate output files in /u01/retail/rms/data/out.
4. The Batch wrapper moves these files to /u01/retail/rms/batch/outgoing (and generates .complete files).
5. Filewatcher moves the file from /u01/retail/rms/batch/outgoing to outgoing SFTP folder.
6. Saimptlog batch reads the RTLOGs from /u01/retail/rms/data/in and once successfully processed, the batch moves the processed RTLOG files to /u02/app_files_merch/retail/rms/data/processed, but for when corrupt file, this file kept in the same /u01/retail/rms/data/in , only it is renamed adding .1.2 at the end eg RTLOG_xxxx.DAT.3.3.3.3 and the next batch run, it fails again.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.