ODS Activation failures

Question

Generally it is obesreved that the ODS activation failes with error something like 'SID cannot be determined'. Also many times we see that ODS activation goes on for 2-3 hours. In this case when we manuall activate the ods it gets completed successfully. However, can anyone tell me the reason for long activation time and the error mentioned above. It would further be helpful if you could tell me the possible preventive measures to avoid manual interventions...Thanks for help in advance

Answer 1

Hi Lye
First i will explain the reasons for long running ODS.
1.This is probably because of too many parallel ODS activations running at the same time.
2.some times some particular jobs running may lock your ODS activation which you can monitor in SM37 which results lock waits and dead locks.
If you see the PID no for the job which is involved in lock waits,if you feel that particular job is not important at that point of time you can terminate the job(not ODS activation job) and repeat the job after the succesful completion of the ODS activation.
If the ODS activation fails with SID error as you mentioned,i hope this solution may help you.
1.Check the request for the infopackage which is loading the ODS in RSRQ
2.give the request of the bearing infopackage or request ID and execute in RSRQ
3.it shows whether that reqest is updated in to your target correctly or not.If its not loaded check the IP processing setting whether the reuested data is reaching in to targets are not.some times data load happens till PSA then push the data by doing process manually step.
4.Now reapeat the ODS activation step.
but if it is SID issue, then load the master data for that particular characteristic and repeat the ODS activation step.
Hope may help you
Regards,
Venkata Lakshmikanth