cancel
Showing results for 
Search instead for 
Did you mean: 

Archive job to store data RSARCH_STORE_FILE fails

Former Member
0 Kudos

Hello Archive Gurus,

One of the archive job that stores data to the archive server fails.

The job is RSARCH_STORE_FILE.

The background is From SAR transaction in SAP the archive job is run successfully. But the created archive files are not stored to the dedicated archive server used in our case Centera. It is initiated by choosing "Store Files" in SARA session management.

the job log shows as if it is unable to accesses the file in the file system.

By the file system ownership and permissions are correct and should be able to access the file.

Here is the job Log?

Has anyone seen this kind of error message before? the archiving solution used is PBS content link and stored to centera.

Any help will be gretaly appreciated.

Step 001 started (program RSARCH_STORE_FILE, variant , user name XXXXX)

The archive file 005984-001BC_SBOOK is being processed

File BC_20071029_174959_0.XXXXX in directory /usr/sap/SID/archive/X.ARCHIV/ is not accessible

Archive file 005984-001BC_SBOOK could not be stored

Job cancelled

I have replaced the user name with 'X'.

The error message class is CMS and id 70 message type S

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

To check to see if the archive file is actually available, go to the Management data of the archive object (from transaction SARA), expand the archive session to see the file(s), double click on the file and look at the Archive Administration: Archive File Detail information. Check at the bottom of the pop-up box and you should be able to see the File Name, the Logicial Path and the Physical File Name.

Regards,

Karin Tillotson

Former Member
0 Kudos

Hello Karin,

As you have mentioned i could see the file and its path from session , also the archive file is accessible is green.

Any other idea why it would give such a message.

The archive object bc_sbook is used for testing and that is where we are seeing this error.

Former Member
0 Kudos

It was configuration issue with file name extension.