Archive files not accesible SARA

[Former Member]

hi all!

I upgraded a test system using the restore from backup of product. system.

Both systems have same arch objects . But paths to arch objs on OS lvl different.

After restore in test system i change os lvl path in SARA:

customizing -> Cross-Client File Names/Paths -> ARCHIVE_GLOBAL_PATH-> Assignment of Physical Paths to Logical Path->UNIX->Selection-> Physical Path.

In SARA Arch Administration:Arch File Detail i have Archive File Not Accessible

physical path to arch files in os lvl correct.

On os lvl (Solaris) arch files have permissions :

sidadm : sapsys -rw-rw----

arch dirs (obj_names) have perm:

sidadm : sapsys drwxrwxrwx

in what may be the problem?

tnanks

[JPReyes · Accepted solution]

Check the the path for your content repositories is consistent on OAC0. Are you using a content repository or just archiving directly to the file system?

Regards

Juan

[Former Member · Accepted solution]

archiving performed directly to the filesystem

[JPReyes · Accepted solution]

Is the path of the transfer directory maintained properly in OAC0?

[Former Member · Accepted solution]

Hi Andrey,

There are a some SAP notes regarding this problem, I think the following notes could be helpful:

Note 110923 - Archives cannot be read or accessed

Note 35992 - File name/directory for application archiving

Note 1609676 - Archive Routing: Archive files are not accessible

Cheers,

Diego.

[Former Member · Accepted solution]

Thanks for answers guys!

I understand what in my problem, but i don't know how resolve

Archiving performed on test and prod systems in different times

Names of arch objs different in prod and test system. For example: SD_SD_VBRK_20110213_102833_0.ARCHIVE in test system and prod name: SD_SD_VBRK_20110306_122139_0.ARCHIVE

I restore from prod to test system and i see names of arch objs from prod system into test.

How can i use files archiving in test system?

Edited by: Andrey Burakov on Nov 29, 2011 11:08 AM

[JPReyes · Accepted solution]

Well.. its natural that if your performed a refresh on your test system it will be looking at the archived files with naming they were exported in PROD. Why don't you simply copy the archived files from prod to your test system?... You should not have any problems with archive runs produced after the copy.

Regards

Juan

[Former Member · Accepted solution]

I copy prod arch files and set the path into test system

thanks