on 01-06-2011 9:59 AM
Hi all,
We able to archive orders successfully to AXS Server, but unable to retrieve the orders after deletion where the u201CRSARCH_RETRIEVE_FILEu201D job fails when we retrieve.
Job started
Step 001 started (program RSARCH_RETRIEVE_FILE, variant , user ID NIO_ABAP)
Archive file 000044-001J_ISM_JHAK is being processed
Operating system message: No such file or directory
Archive file 000044-001J_ISM_JHAK does not exist
Error occurred when checking the retrieved archive file 000044-001J_ISM_JHAK
Job cancelled
We were Transfer dir, Phys. Path are mentioned in OSA0 is /usr/sap/xxx/trans but when it retrieves the archived file fetching from /usr/sap/xxx/SYS/global.
Can anyone help us where and how to change settings.
Regards,
PANU
Edited by: kumar panu on Jan 6, 2011 11:33 AM
This maybe due to a Content Repository setting as well. Please share this error with the basis team and ask if they can fix this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm in face of this problem.
In transaction File I define the:
Logical path: Z_RSEC_CHLOG
Physical path: /sap/archiving/<SYSID>/<FILENAME> (object RSEC_CHLOG)
After... in Logical File Name Definitions:
Logical File: Z_RSEC_CHLOG.
Logical Path: Z_RSEC_CHLOG
And the same procedure for other objects as: iDoc,BWREQARCH, RSECPROT, all files generated goes to file system directory /sap/archiving/<SYSID>.
But the RSEC_CHLOG goes to /usr/sap/BGD/SYS/global/
Can anyone help how to change settings
Regards,
As Sunil mentioned this is a problem with the "Logical File Path" in FILE, you are archiving in one location and looking for the file in another location.
Check the details on ARCHIVE_GLOBAL_PATH and ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK as they are the usual ones.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Juan,
As we are using the AXS as a third party for archival link and we gave AXS Server details in Repository by transaction OAC0 and We tested the connectivity test was successfully.
I changed the ARCHIVE_GLOBAL_PATH and ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK to /usr/sap/xxx/SYS/global.
Able to archive and store but not retrieval it, please find the logs for Delete, Store and Retrieve as below.
Job started
Step 001 started (program RJJARC11, variant PRODUKTIV, user ID INVENIO_ABAP)
Archive file 000085-001J_ISM_JHAK is being processed
Job finished
Job started
Step 001 started (program RSARCH_STORE_FILE, variant , user ID INVENIO_ABAP)
Archive file 000085-001J_ISM_JHAK is being processed
Archive file 000085-001J_ISM_JHAK stored
Job finished
Job started
Step 001 started (program RSARCH_RETRIEVE_FILE, variant , user ID NIO_ABAP)
Archive file 000085-001J_ISM_JHAK is being processed
Operating system message: No such file or directory
Archive file 000085-001J_ISM_JHAK does not exist
Error occurred when checking the retrieved archive file 000085-001J_ISM_JHAK
Job cancelled
============================================================
Archive File 000085-001J_ISM_JHAK
Date 10.01.2011
Time 17:29:15
Number of Objects 1
Size in MB 0.039
Status Archiving Completed
Storage System Retrieval Error
Index No index
Kindly suggest for Retrieval Error..
Regards,
PANU
Hi Juan,
Please find the Content Rep details as below...
Content Rep. XX Active
Description AXS-One Printy
Document Area
Storage type
Protocol ZAXSHTTP
Version no. 0046 Content Server version 4.6
HTTP server 10.11.118.33
Port Number 2001 SSL Port Number
HTTP Script axslink/axs1stor.dll
Transfer drctry /usr/sap/XXX/trans
Phys. path /usr/sap/XXX/trans/
OutputDevice FCCC
there is no files under Transfer Directory..
Regards
Panu.
Transfer drctry /usr/sap/XXX/trans
Phys. path /usr/sap/XXX/trans/
So... File is pointing at /usr/sap/<sid>sys/global and transfer directory is /usr/sap/<sid>/trans
That won't work.. your archived files must be sitting in the transfer directory right? ( assuming they have not been stored in the reporsitory, whatever it is)...
You need to make sure that the files are arriving to their final resting place and they are accessible . You can check that via SARA - Management and or SARI.
Regards
Juan
HI Juan,
I have changed Transfer Directory to /usr/sap/XXX/SYS/global/ in Respository by transaction OAC0.
my archival job details as below..
Job started
Step 001 started (program RJJARC10, variant TEST11, user ID NIO_ABAP)
Archiving session 000088 is being created
Logical file name or logical path name incorrectly defined
Path: /usr/sap/XXX/SYS/global/
Name for new archive file: RIS01100.191604.NIO_ABAP.ARCHIVE
Job finished
and i have checked in SARI is "No active info structures exist for archiving object J_ISM_JHAK" and Status Per Info structure "No reportable info structure exists for archiving object".
Regards,
Panu.
You have something fundamentaly wrong in your config.
Go to SARA -> enter your object -> Click on "Customizing" -> Archiving Object Specific Customizing -> Technical Settings -> you will get there the Logical File Name
Check that the transfer directory and the Logical File Name path are the same
Regards
Juan
Hi Juan,
i have checked it Transfer Directory locates to /usr/sap/XXX/SYS/global but Logical file Name exist as a "ARCHIVE_DATA_FILE" for object J_ISM_JHAK.
As i defined Logical File Path as a "ARCHIVE_GLOBAL_PATH" and "ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK" to "/usr/sap/TOI/SYS/global" to in FILE Transaction.
Please find "Logical File Name Definition, Cross-Client" as below.
Logical file ARCHIVE_DATA_FILE
Name Archive file for archiving application data
Physical file R<PARAM_1><MONTH><DAY><PARAM_2>.<TIME>.<F=EXAMPLE>
Data format
Applicat.area BC
Logical path ARCHIVE_GLOBAL_PATH
Regards,
PANU
Hi Juan,
Logical file name or logical path name incorrectly defined
Message no. BA282
Diagnosis
When generating a file name for an archive file that is to be created, the system determined that the logical file name ARCHIVE_DATA_FILE or the logical path name ARCHIVE_GLOBAL_PATH was defined incorrectly.
System Response
Despite the incorrect definition, a file name was generated. Therefore the system will now continue to create a new archive file. Errors may occur when the archive file is accessed at a later date, or when the file name is to be displayed.
Procedure
When assigning a physical file name to the logical file name, no part of the directory name may be used.
When assigning a physical path to the logical path, only component parts of the directory name may be used. In particular, file endings, such as '.ARCHIVE' are to be assigned to the physical file name.
Use these criteria to check the definition of logical file name ARCHIVE_DATA_FILE and logical path name ARCHIVE_GLOBAL_PATH.
Do not change the existing definition of a logical path, if archive files already exist for this logical path. Instead, create a new logical path that is defined correctly, and assign this path to the logical file name. This allows you to still access the archive files that were created under the old logical path.
Hi Juan,
Logical File Path Name
ARCHIVELINK_CONNECT_CUSTOMIZE_WINDOWS
ARCHIVELINK_DELIMITER Separator between path and file name
ARCHIVELINK_VIEWER_CUSTOMIZE_WINDOWS
ARCHIVE_APPLICATION Archiving path for application archiving
ARCHIVE_BCSETS BC Set Archiving
ARCHIVE_BI_PROTOCOL_PATH Path for BI log data archiving
ARCHIVE_GLOBAL_PATH /usr/sap/XXX/SYS/global
ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK /usr/sap/XXX/SYS/global
ARCHIVE_PATH_KI4 Archive path KI4
ARCHIVE_PATH_P22 Archive files from P22 (2.2)
ARCHIVE_PATH_P30 Archive files from P30 (3.X)
BCA_MIGRATIION_VALUE_BALANCES DI Correction of Daily Closing Balances
BOND_SAVINGS_PATH Canada bonds savings path
BUPA_DI_TEST01 ZGP: (generated) data transfer test file
==================================================================
Logical File Name
ARCHIVELINK_ANNOTATION_STAMP_UNIX Note stamp control file (User,Dept.,Timestamp)
ARCHIVELINK_ANNOTATION_STAMP_WINDOWS Note stamp control file
ARCHIVELINK_DELIMITER ArchiveLink: Separator between path and file name
ARCHIVELINK_DOCUMENTTYPE_TEXT_UNIX iXOS viewer text table
ARCHIVELINK_DOCUMENTTYPE_TEXT_WINDOWS iXOS viewer text table
ARCHIVELINK_VIEWER_GENERAL_CUSTOMIZE_UNIX ArchiveLink viewer customizing file
ARCHIVELINK_VIEWER_GENERAL_CUSTOMIZE_WINDOWS ArchiveLink viewer customizing
ARCHIVE_BCSETS BC Set Archiving
ARCHIVE_BI_PROTOCOL_DATA_FILE Archive file for archiving batch input logs
ARCHIVE_BUPA Archiving business partners
ARCHIVE_DATA_FILE Archive file for archiving application data
ARCHIVE_DATA_FILE1 Archiving the asset tax tables
ARCHIVE_DATA_FILE_P30 Archiv file for archiving P30 application data
Any thing as i need to define in "ARCHIVE_DATA_FILE"
Pls give ur suggestions...
I don't think the problem is related to the definition of the ARCHIVE_DATA_FILE as is still the default.
You need to fix the problem with the paths and run tests with EXAMPLE object until archive session is successful.
As you mentioned you are using a 3rd party repository I will also notify them
Regards
Juan
Hi Juan,
I have checked, it's not a space issue... when i clicked on Archive Directory in SARA its pointing to x.ARCHIVE Directory but this directory doesn't exist at OS Level.
There is a directory exist with X.ARCHIVE and files are archive to this directory.
Now i want change the Archive Directory to X.ARCHIVE Path like /usr/sap/XXX/SYS/global/X.ARCHIVE.
Can you please let me know how do i change Archive Directory path to X.ARCHIVE.
Hello Panu, Juan,
How did you solved the issue regrading retrieval path for the archive files retrieved from the content server.?
I have the same problem but I am using SAP Content Server as solution for Content Repository.
I have created a new Logical File for archives to be stored and I have set it for the archival objects(s). This path is D:\SARA
The write program writes the file to D:\SARA and, after successful creation of the archive file, they are also successfully moved into the Content Server.
But the retrieval from the Content Server brings the file in the folder D:\SARA\X.ARCHIVIN and, of course, the retrieval job ends with error bellow
====
Operating system message: No such file or directory
Archive file 000009-001ISU_PRDOCL does not exist
Error occurred when checking the retrieved archive file 000009-001ISU_PRDOCL
===
The Basic Path and Archive Path settings in OAC0 for the content repository are both D:\SARA !!
Thanks a lot for your support!
Regards,
Vasile
check under tcode FILE
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sunil,
Can you give more details like what parameter need to check,,
pls find below of FILE Transaction..
ACC_PROG_DEFAULT_PATH WinGUI Check Tool Default Memory Location
AIRS_PATH AIRS Workers' Comp. file path (CA)
ARCHIVELINK_CONNECT_CUSTOMIZE_UNIX
ARCHIVELINK_CONNECT_CUSTOMIZE_WINDOWS
ARCHIVELINK_DELIMITER Separator between path and file name
ARCHIVELINK_VIEWER_CUSTOMIZE_WINDOWS
ARCHIVE_APPLICATION Archiving path for application archiving
ARCHIVE_BCSETS BC Set Archiving
ARCHIVE_BI_PROTOCOL_PATH Path for BI log data archiving
ARCHIVE_GLOBAL_PATH Global path for archiving files
ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK
ARCHIVE_PATH_KI4 Archive path KI4
ARCHIVE_PATH_P22 Archive files from P22 (2.2)
ARCHIVE_PATH_P30 Archive files from P30 (3.X)
BCA_MIGRATIION_VALUE_BALANCES DI Correction of Daily Closing Balances
Regards,
Kumarp
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.