Delete job failed in IDOC archiving

Hi Gurus
Delete job for IDOC archiving failed with the following error.
"Job started
Step 001 started (program RSEXARCD, variant PROD_DELETE, user ID CTMBATCH)
Archive file 002558-001IDOC is being verified
Operating system message: Permission denied
Archive file 002558-001IDOC does not exist
Error during verification when accessing archive file 002558-001IDOC
1 archive file(s) were not successfully verified
Job cancelled after system exception ERROR_MESSAGE "
I checked the status of the job in management , and it says Write and Storage is successful. I checked for the archive file and it is present in Exchange directory.
As the error message states that "Operating system message:Permission denied", so I am expecting that It should be related to some authorization for the directory. Or might be if authorizations has been modified for uid which. But I am not sure on this. How can I confirm this on SAP level ??
This job is a weekly job but it failed this time. What else should I check?
Please let me know if anyone has encountered similar issue before. I wish to know the reason for this error and the resolution to it.

Hi,
based on your description I am not quite sure if this is really a question on DMS. Could you please provide more details about which IDOC type do you use and maybe some error message number. This would help to clarify the reason faster.
Best regards,
Christoph

Similar Messages

Archived files missed after deletion job

Hi All,
We are generally doing the techinical archiving for some objects in ECC 6. Here for one object, write job & delete job is finished. but any how, archived file is missed before store job. There was some hardware failure.
Now, we have get them restored from backup but i am not able to access the restored files from tcode SARA to store them in our storage server. It is still showing the files as failed in Store job archive file selection screen.
I need to store those files in our storage server but archive file is not accessible from file system.
Now, please let me know, what should i do in this case.
Thanks in advance.
br
Ankit

Hi,
I do a little bit of Archiving using SARA, but not any expert
We had such situations when the file was deleted from OS level while Archiving run was in progress at SARA.
What we do in such situation is to disable the existing Run in "SARA" -> Put in Archiving Object name --> click Management, click on the failed Run and "Mark it for deletion".
Start a new run for the same Archiving object, Keep the variant same ( I mean keep the selection dates same as earlier run) and start all over again with Write, delete, store etc.
I dont know how much it helps
Might be different from the scenario you might have on hand.

RSEXARCD: Idoc archiving deletion program issues

Hi,
I have two queries:
1. The Idoc archive deletion program, RSEXARCD, when executed in background, terminates when there are no archive files to process (as seen in SARA). How can we prevent this? Our deletion jobs are scheduled weekly, but sometimes there are no archive files created from the archive write program RSEXARCA.
2. Secondly, how can we process multiple archive files using this program RSEXARCD in background? Currently, it processes only one archive file at a time and takes up the oldest unprocessed archive file. Also, would like to know how it gets this information of the oldest unprocessed archive file?
Thanks.

if a program terminates, then you should look into the dump to see the root cause and follow the instructions. e.g. search for OSS notes with the metioned terms
I just searched with the terms "archiving idocs termination" and found 12 notes with program fixes.
Further, the program names you mentioned are not the most recent programs.
Have a look into OSS note Note 582828 - IDoc archiving: Standardization
maybe you will not have your problems anymore if you use the new programs

Archive Delete job taking too much time - STXH Sequential Read

Hello,
We have been running Archive sessions in our production system in last couple of months. We use SARA and selecting the appropriate variants for WRITE, DELETE and STORAGE options.
Currently we use the Archive object FI_DOCUMNT and the write job is finished as per the normal time (5 hrs based on the selection criteria). After that normally the delete job is used to complete in 1hr or less than 2hrs always (in last 3 months).
But in last few days the delete job is taking too much to complete (around 8 - 10hrs) when I monitor the system found that the Sequential Read for table STXH is taking too much time to read and it seems this is the cause.
Could you please provide a solution for the same, so that the job will run faster as earlier.
Thanks for your time
Shyl

Hi Juan,
After the statistics run the performance is quite good. Now the job getting finished as expected.
Thanks. Problem solved
Shyl

Long runnning IDOC Archiving jobs

Hi Techies,
Long runnning IDOC Archiving jobs: ARV_IDOC_WRI* are being observed in PRD system with Avg runtime > 150,000 sec.
Job Details:
Main Program: RSEXARCA
Parameter: IDOC ALL MONTH
These jobs are also resource consuming & extensively using CPU & Memory.
For info: These jobs are getting finished but only after long runtime.
Some SQL stmts observed while this job-execution:
SELECT
"OBJKEY" , "OBJTYPE" , "LOGSYS" , "ROLETYPE" , "ROLEID" , "UTCTIME"
FROM
"SRRELROLES"
WHERE
"CLIENT" = :A0 AND "OBJKEY" = :A1 AND "OBJTYPE" = :A2#
SELECT
"MANDT" , "DOCNUM" , "COUNTER" , "PAGENO" , "TIMESTMP" , "PAGELG" , "VARDATA"
FROM
"EDI40"
WHERE
"MANDT" = :A0 AND "DOCNUM" = :A1
ORDER BY
"MANDT" , "DOCNUM" , "COUNTER" , "PAGENO"#
SELECT
"DOCNUM" , "DOCREL" , "STATUS"
FROM
"EDIDC"
WHERE
"MANDT" = :A0 AND "UPDDAT" >= :A1 AND "UPDDAT" BETWEEN :A2 AND :A3 AND "DIRECT" BETWEEN :A4 AND :A5 AND
"STATUS" = :A6 AND NOT "MESTYP" IN ( :A7 , :A8 , :A9 , :A10 , :A11 , :A12 , :A13 , :A14 , :A15 , :A16 ,
:A17 , :A18 , :A19 , :A20 , :A21 , :A22 , :A23 , :A24 , :A25 , :A26 , :A27 , :A28 , :A29 , :A30 , :A31 )
Please suggest as to how the job runtime can be reduced.
Awaiting for your reply.

Hi,
Since the variant used is fetching data for the entire month, you could try splitting the jobs and have multiple runs instead.
You can also try to schedule the jobs when there is minimum system load, incase its not already done.
As far as the program is concerned, if this is standard program, there is little scope for tuning.
You can always check for related index quality and statements with high CPU costs to better understand why the job is running for such a long duration.

Archive jobs / Delete job

I have some questions regarding Archiving / Deleting..
1) What are the implication of not setting 'DELETION' category parameters in 'Specific configuration'.
2) How do I delete the messages that are archived? Will 'Delete job' handle this also?
3) Also I had archived some messages using Archiving job.. When try to lookup this message using 'Archived XML Messages (Search using Archive), I get a list of Archived messages. When I click on any of this messages, I get "Could not find message in archive" message.

hi,
- did you activate SAP_BC_XMB info structure?
- did you do all the configuration?
http://help.sap.com/saphelp_nw04/helpdata/en/0e/80553b4d53273de10000000a114084/content.htm
BTW
you can also fill activated information structure retrospectively for already existing archives:
http://help.sap.com/saphelp_nw04/helpdata/en/5c/11afaad55711d2b1f80000e8a5b9a5/content.htm
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

CO_COSTCTR Archiving Write Job Fails

Hello,
The CO_COSTCTR archiving write job fails with the error messages below.
Input or output error in archive file \\HOST\archive\SID\CO_COSTCTR_201209110858
Message no. BA024
Diagnosis
An error has occurred when writing the archive file \\HOST\archive\SID\CO_COSTCTR_201209110858 in the file system. This can occur, for example, as the result of temporary network problems or of a lack of space in the fileing system.
The job logs do not indicate other possible causes. The OS and system logs don't have either. When I ran it in test mode it it finished successfully after long 8 hours. However, the error only happens during production mode where the system is generating the archive files. The weird thing, I do not have this issue with our QAS system (db copy from our Prod). I was able to archive successfully in our QAS using the same path name and logical name (we transport the settings).
Considering above, I am thinking of some system or OS related parameter that is unique or different from our QAS system. Parameter that is not saved in the database as our QAS is a db copy of our Prod system. This unique parameter could affect archiving write jobs (with read/write to file system).
I already checked the network session timeout settings (CMD > net server config) and the settings are the same between our QAS and Prod servers. No problems with disk space. The archive directory is a local shared folder \\HOST\archive\SID\<filename>. The HOST and SID are variables which are unique to each system. The difference is that our Prod server is HA configured (clustered) while our QAS is just standalone. It might have some other relevant settings I am not aware of. Has anyone encountered this before and was able to resolve it?
We're running SAP R3 4.7 by the way.
Thanks,
Tony

Hi Rod,
We tried a couple of times already. They all got cancelled due to the error above. As much as we wanted to trim down the variant, the CO_COSTCTR only accepts entire fiscal year. The data it has to go through is quite a lot and the test run took us more that 8 hours to complete. I have executed the same in our QAS without errors. This is why I am bit confused why in our Production system I am having this error. Aside that our QAS is refreshed from our PRD using DB copy, it can run the archive without any problems. So I made to think that there might be unique contributing factors or parameters, which are not saved in the database that affects the archiving. Our PRD is configured with High availability; the hostname is not actually the physical host but rather a virtual host of two clustered servers. But this was no concern with the other archiving objects; only in CO_COSTCTR it is giving us this error. QAS has archiving logs turned off if it’s relevant.
Archiving 2007 fiscal year cancels every after around 7200 seconds, while the 2008 fiscal year cancels early around 2500 seconds. I think that while the write program is going through the data in loops, by the time it needs to access back the archive file, the connection has been disconnected or timed out. And the reason why it cancels almost consistently after an amount of time is because of the variant, there is not much variety to trim down the data. The program is reading the same set of data objects. When it reaches to that one point of failure (after the expected time), it cancels out. If this is true, I may need to find where to extend that timeout or whatever it is that is causing above error.
Thanks for all your help. This is the best way I can describe it. Sorry for the long reply.
Tony

Archiving and Delete Job

Hi,
I having problem in PI 7.0, SXMB_MONI XML Messages does shows only 1 day, Messages, I understand there are 2 jobs are running in background
Job: SAP_BC__XMB_DELETE Program: RSXMB_DELETE_MESSAGES
Job: SAP_BC_XMB_HIST_DELETE Program: RSXMB_DELETE_HISTORY
These jobs are running every 6 hrs.
Is that can I change the job time like delete messages every 1 or 2 weeks, is that my problem will be solve, or should I do someitng else... please tell me
Thanks in Advanced
Angeline Purnama

Hi Angeline,
Define the retention period for archiving and deletion in SXMB_ADM ->Define Interfaces for archiving and retention periods.
Re Shcedule the jobs using SXMB_ADM ->Schedule Archiving Jobs and Schedule Deletion Jobs.
Then check if the messages are getting deleted.
Revert if it works.
Regards
RAGHU

Batch Jobs fail because User ID is either Locked or deleted from SAP System

Business Users releases batch jobs under their user id.
And when these User Ids are deleted or locked by system administrator, these batch jobs fail, due to either user being locked or deleted from the system.
Is there any way that these batch jobs can be stopped from cancelling or any SAP standard report to check if there are any batch jobs running under specific user id.

Ajay,
What you can do is, if you want the jobs to be still running under the particular user's name (I know people crib about anything and everything), and not worry about the jobs failing when the user is locked out, you can still achieve this by creating a system (eg bkgrjobs) user and run the Steps in the jobs under that System User name. You can do this while defining the Step in SM37
This way, the jobs will keep running under the Business User's name and will not fail if he/she is locked out. But make sure that the System User has the necessary authorizations or the job will fail. Sap_all should be fine, but it really again depends on your company.
Kunal

Company Address deleted when update job fails

Hey guys,
Last night we had an issue with a development system, because of this our IdM wasn't able to run it's nightly update job.
Now before I noticed this in the morning I had an urgent request to create a user but I couldn't create the user because I couldn't find the company address.
Had a look in IdM noticed the update job going wrong, ran it manually and out of the blue (or out of the development system) the company address is back.
Only problem: every single user now does not have a company address assigned to him/her.
So my question is: how is it possible that an update job failing is a reason for idM to remove a company address?
We've had issues where users didn't have a company address before and it gave all types of strange behavior so I'm not looking forward to that type of situation again.

Hi Srinivas S,
Create the new recurring instances of those reports which having issue. and then check
it will resolve your issue.
Regards,
Anish

SQL Server Delete statements failing

Hello,
I am using SQL 2012 SE and I have been using a purge job that deletes data older than 5 days from 4 table in a database. The job had been running fine and deleting older data for the past 5 years and it failed for the first time today with the following
error:
Time-out occurred while waiting for buffer latch type 2 for page (1:15945892), database ID 6
I am not seeing any deadlocks at the time the job failed. What caused this job to fail?
How can this be prevented? Experts need your valuable inputs.
Thanks

That's not really a normal error, and it's not trivial to diagnose. Hasrh Kumar was kind to point you to a fix for one situation where this error can occur. Unfortunately, that fix is for SQL 2008 and you are on SQL 2012, so that is not of any help for you.
My advice would be to restart SQL Server, and if the problem does not reoccur, forget it. If it comes back, my suggestion would be to open a case with Microsoft to have this resolved. I found a blog post where someone had run into this error:
http://sqlblog.com/blogs/michael_zilberstein/archive/2013/03/22/48339.aspx
but the steps the author applies are not exactly trivial.
It is a important to understand that this message is an indication that things are not what they are supposed to be, but what is the exact root cause is not apparent.
Erland Sommarskog, SQL Server MVP, [email protected]
The thing is the job is a weekly once job. It failed for the first time on saturday night and then I reran it last night and it failed again.

ERROR VNIC creation job failed

Hello All,
I have brought oracle VM X86 manager into ops center 12c control. When I try to create a new virtual machine it is throwing the ‘ERROR VNIC creation job failed’ error. Can anybody throw some light over this issue.
Thanks in advance.
Detailed log is
44:20 PM IST ERROR Exception occurred while running the task
44:20 PM IST ERROR java.io.IOException: VNIC creation job failed
44:20 PM IST ERROR VNIC creation job failed
44:20 PM IST ERROR com.sun.hss.services.virtualization.guestservice.impl.OvmCreateVnicsTask.doRun(OvmCreateVnicsTask.java:116)
44:20 PM IST ERROR com.sun.hss.services.virtualization.guestservice.impl.OvmAbstractTask.run(OvmAbstractTask.java:560)
44:20 PM IST ERROR sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
44:20 PM IST ERROR sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
44:20 PM IST ERROR sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
44:20 PM IST ERROR java.lang.reflect.Method.invoke(Method.java:597)
44:20 PM IST ERROR com.sun.scn.jobmanager.common.impl.TaskExecutionThread.run(TaskExecutionThread.java:194)
Regards,
george

Hi friends
I managed to find the answer. Internally it is has some indexes in the data base level. It still maintains the indexes in the shadow tables. Those all need to be deleted. With our Basis team help I have successfully deleted those and recreated the indexes.
As Soorejkv said sap note 1283322 will help you on this to understand the scenarios.
Thank you all.
Regards
Ram

Deleting XI Messages - Abap dump in Delete job

Hi all,
I would like to know if we could directly delete xml messages without archiving. We are working on a sandbox system.
I tried to schedule a delete job ARCDEL_Delete_20080612115401 / 11540100.
It cancelled giving an abap dump CALL_FUNCTION_NOT_FOUND.
the abap dump is as follows:
    The function module " " is called,
    but cannot be found in the library.
    Error in the ABAP Application Program
    The current ABAP program "ARCDEL_DELETE_PARA" had to be terminated because it
     has
    come across a statement that unfortunately cannot be executed.
Any idea why a function module with no name is called?
Thank you.
Regards,
Raghavan

Hi Raghvan,
There are few ABAP report for that
RSXMB_DELETE_MESSAGES
RSXMB_DELETE_ARCHIVED_MESSAGES
check this blog for reference :
/people/gourav.khare2/blog/2007/12/21/mass-cancellation-of-error-messages--xi
Sachin

Lo-Extraction Job Failed in SAP ECC 6.0

Hello,
My Lo-extraction job failed yesterday because of this I'm unable to extract the delta data from SAP ECC 6.0 to BI. When I extract the Delta data from 2LIS_11_VAITM to BI there is no data because of Job failed in SAP ECC 6.0.
How to get the data back to 2LIS_11_VAITM data source?
Thanks

Error log display as follows
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMCEX" or "LMCEXU14"
"MCEX_UPDATE_11"
Actually I add ZZ fields to structure if that is the case do i need to delete the data from MCEX11 ?
I delete the data from setup tables but i did not delete the LUW entries?
When do we delete the LUW entries?
If the structure changes do I need to cancel the old job and re-schedule job?
Thanks

Slow boot - com.apple.afpstat-qfa[271]) Job failed to exec

Hi,
I have a Macbook Pro Retina. All has been working fine since I first got the MBP, but now I have a 30 second delay in booting each time.
Looking in the log I see this:
16/08/2012 10:07:05.284 CalendarAgent[245]: Property list invalid for format: 100 (property lists cannot contain objects of type 'CFSet')
16/08/2012 10:07:05.798 NetUpdate[91]: Launch background checker (Post reboot: 0)
16/08/2012 10:07:25.244 com.apple.launchd.peruser.501[170]: (com.apple.afpstat-qfa[271]) Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
16/08/2012 10:07:25.244 com.apple.launchd.peruser.501[170]: (com.apple.afpstat-qfa[271]) Job failed to exec(3) for weird reason: 2
16/08/2012 10:07:26.317 appleprofilepolicyd[286]: appleprofilepolicyd: profiling drivers not loaded, loading
Every time there is a delay in boot I see a gap in the boot sequence log just before the error message in red above.
Does anyone have any idea a) what this is doing; and b) what might be causing the problem?
I have tried repairing permissions etc. but that didn't solve it.
Thanks
Darren.

I'm going to answer your question in more detail than you probably want, because it's somewhat important and I want to make a record.
The job referenced by those log messages is started when a user logs in, and the per-user launchd(8) process loads the following file:
/System/Library/LaunchAgents/com.apple.afpstat.plist
The file instructs launchd to invoke an executable at the path /usr/local/bin/afpstat. Although the syntax is correct, the executable doesn't exist. Even the directory doesn't exist, by default. I've searched all the Apple installer receipts in ML, and none of them refers to that file.
So what has happened here is that some extra pieces were inserted into ML during development, for debugging purposes no doubt. When the time came for release, the executable was removed, but the developer who removed it forgot to remove the corresponding launchd item. Every ML installation has it, and every one is being delayed during boot when it fails.
The solution to this problem is to delete the file that the Apple developer forgot to delete. In the Finder, select Go ▹ Go to Folder... from the menu bar, copy the text outlined above into the box that opens, and press return. A folder will open with the item selected. Move the selected item to the Trash, then empty. You'll be prompted for your login password.
Edit: On my Macs, although the same error is logged, it doesn't seem to be causing a delay of more than one second, so deleting the bogus LaunchAgent may not have a noticeable effect.

Delete job failed in IDOC archiving

Similar Messages

Maybe you are looking for