Skip to Content
avatar image
Former Member

Archiving Storage Job Issue

Hi All,

we got following error in Archive storage job .

Pls advice how to correct the issue

09.09.2011 10:43:02 Job started

09.09.2011 10:43:02 Step 001 started (program RSARCH_STORE_FILE, variant , user ID P1293973)

09.09.2011 10:43:02 Archive file 000143-001IDOC is being processed

09.09.2011 10:43:07 Archive file 000143-001IDOC does not exist

09.09.2011 10:43:07 Error occured when checking the stored archive file 000143-001IDOC

09.09.2011 10:43:07 Job cancelled after system exception ERROR_MESSAGE

Tks,

Raju

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Sep 12, 2011 at 10:51 AM

    Hi Raju,

    Please execute the storage job again. Do this via transaction SARA -> StorageSyst -> Store files do you get into the same error? In affirmative case doublecheck your content repository config.

    Br,

    Javier

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 12, 2011 at 11:21 AM

    Archive file 000143-001IDOC does not exist

    First thing to check is if the file above exist in the transfer directory (usually the global directory, check on OAC0)... Also, what sort of repository are you using?

    Regards

    Juan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello Raju,

      In Management option for the archive session, you can see the archive file details - You will come to know the Archive file path and name..

      With this information, you have to check couple of things:

      1. File path (noticed in archive file details - mgt function) is same in content repository OAC0 - Physical basic path?

      2. In transaction AL11 - in the directory path - check the file exist?

      With the above clarification, I think you will get the solution.

      Also note on sequence of store job execution.

      Hope these hint will help you.

      -Thanks,

      Ajay

  • avatar image
    Former Member
    Nov 02, 2011 at 09:22 AM

    The issue has been fixed

    Add comment
    10|10000 characters needed characters exceeded