Did you make room already? That should be the first thing.
After that monitor the background tasks to ensure that they restart and then go back to SP12, re-run the consistency check and delete the orphaned entries (note that you may still see some of these if you re-run the consistency check again).
Orphaned entries mean the Temse Object name which showing "Unable to access related file"? Yeah i did make some room and some jobs have started. But i doubt why did my standard jobs did not run yesterday night?
When you run SM37, can you go back a day to see if the SAP standard jobs failed? That information should still be there since it is stored in the DB (instead of the TemSe files out on the OS).
These jobs probably all failed because they could not write to those OS based job logs.
You will definitely want to run the consistency checks against TemSe manually since the scheduled jobs that do this may not run until later.
Thanks for your concern bur plzz let me know this Does Orphan job logs mean the temse objects shown with erro " Unable to access related file" because after i ran SP12-->spool consistency check ..it showed me many files with the error "Unable to access related file"
You will want to delete these orphans that are listed to remove the inconsistencies between what is stored in the DB and what has been saved at the OS level. The status of the background jobs was saved but no logs were created.
No when i run the spool consistency checy in SP12, i got a biglist of temse objects and all are having .log extension and all are having message as "Unable to access related file". My question is , Do i need to delete all these? are these the orphaned job logs?
Hi. Check messages in sm21. Check tablespaces in DB02. Also in server check free space (Or check file system monitor in rz20) , the os log check in st06. Are everefing fine ? Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.