Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Doug Berry on Jan 18 at 5:44 PM There are also a database settings (depending on SQL or Oracle) that starts a service/table space/memory area, I would check these also. It could be that there isn't sufficient memory for a needed internal table to be defined and processed.
| | | ---------------Original Message---------------
From: SimonCrowder
Sent: Friday, January 17, 2014 8:58 AM
Subject: How DSO Activation Failure Step Can Be Rectified to Avoid RSPC_PROCESS_FINISH execution in se38 ?
Just some thoughts off top of my head?..
I assume you have checked all logs to see if detailed explaination can be found, anything showing in sm21 or ST22? Also anything in RSA1 (Right Click on DSO --> Manage --> Request Tab --> Logs for DSO --> Check for any Error details here.)
Has this always failed or just stopped recently maybe - has anyone manually activated prior request somehow and it has failed since?
Have you tried manually activating in RSA1 - does this give any better error messaging? Are all of the prior requests activated and up to date as you expect? Have you got any prior loads in ZSCO01 that show red or haven't been activated?
Have you checked you have enough processes available at the time of activation? - Have you tried repeating the Process Chain step later to see if it now works (might indicate a lock or process unavailable at the time)
I would also have a look over the data in DSO before you activate to see if there are any erroneous values?
Cheers
Simon |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
