activation of ODS in 3.5 is taking a long time

[Former Member]

Hi,

The activation of ODS in 3.5 is taking a long time for even 5000 records.

The Bex reporting icon is unchecked.

When i see the job log , it has taken more one hour to move from the 3rd step

18.09.2008 13:02:31 Activation is running: Data target Zxctr, from 305,451 to 305,458

18.09.2008 14:04:48 Data to be activated successfully checked against archiving objects

What could be the reason and how to tackle this ?

PVC

[Former Member]

Hi

Of there is no short dump, then the probable reason for long running jobs is performance.

Check sm21(system logs) from there you will get an idea of the system performance.

The other probable reason is that the ODS is trying to read or write from a table which is busy in performing some other task.

goto job log of ods. double click the job name.

A new windoe opens. Click the job details tab, there copy the application server name and see also the job pid(process id)

go back to the job log screen. Click application servers.

See if there are many jobs on the server which are on hold or waiting or stopped status, then it sa performance issue.

Also check the status of the job. if its on hold or waiting, it is not getting the space to execute the job.

If it is running, check what is it doing, whether reading or writingto a table.

If yes, may be you need to check the locks on the table.

Goto st04, check the locks ans deadlocks monitor.

Check if there is a lock or a deadlock on the pid of your ods.

If yes, then you have to probably kill the ods activation job.

Let the other job get successful, and then repeat the ods activation.

Otherwise, check if the other job in non crtical, then probably you can kill that job and proceed with the ods.

Or contact the basis team for checking and improving the table spaces.

Hope this helps

Regards

Shilpa

[former_member345199]

Hi,

There are a couple of places where you can see the activation progress.

1) To start with SM37 job log > (give BI_PROCESS_ODSACTIVAT or BI_ODSA*)

and it should give you the details about the activation job. If its active make sure that the job log is getting updated at frequent intervals. If its completed check the log for ODS activation.

2) For very huge number of records SM37 job log may not get update frequently. In that case you have a workaround.

Go to contents > Active Data table > No. of entries > This will keep on increasing at frequent intervals.

3) SM66 > Get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. See if its accessing/updating some tables or is not doing anything at all.

4) Go to Activate button in Target > Request tab. Inside you can see a job log button. It will also show some log regarding the last activation.

5) If the Reporting icon has appeared near the request id in ODS. If it appears that may indicate that request is available for reporting

6) Check the request status in these tables.

Table RSICCONT table contains the requests that are actually loaded in a target.

Table RSMONICDP contains the request id of the fact table.

Table RSODSACTREQ contains information if an ODS is available for reporting/deleting inactive requests also possible.

Table RSODSACTUPDTYPE.

Check OSS Notes 494639 & 595104 (if they are applicable to your system)

https://service.sap.com/sap/support/notes/963760

https://service.sap.com/sap/support/notes/1042182

Also refer solution here:

Hope this helps,

Jitu K

[former_member207028]

HI,

Go to RSODSO_SETTINGS transaction meant for maintaining ODS runtime parameters.

ODS has its parameters for activation, Sid generation & parameters for rollback.

we can have radio buttons like serial processing , parallel processing, processing in dialog processes , processing in backgroun processes and other options like Number of parallel processes, maximum package size etc.

choose options like parallel processing and processing in background processes.

delete the change log table also.

Regards

Daya Sagar

[ssurampally]

Hi,

It might be one of the reasons is, if your load is completed for the ODS, and QM status is not changed to Green. YOu change it later manually. In between your process chain triggered the ODS activation, it takes lot of time to get the Archeiving step.

or You can check in SM66, whether the work process is allocated to the App server and see the performance.

[Former Member]

Hi PVC,

did you check, if you got a dump in ST22 ? Something like "DBIF_RSQL_SQL_ERROR" or similar. If that is the case, take a look at the tablespaces, because the problem may be there (not enough memory).

If the ODS ist enabled for reporting, check your characteristics. Perhaps some buffering for SID generation would be a good idea. And in the lane lays another possibility: If another process load an infoobject for which entries are generated by the activation a deadlock may occur.

These are just some ideas what can slow down an activation.

Kind regards,

Jürgen

[Former Member]

there is no dump in ST22.

also the ODS is a data store only . so Bex option is not checked

why it takes solong to get into teh archiving step

[Former Member]

Hi pvc,

This might have happened because of its huge size. What size does ODS have?

Denis.

[Former Member]

The ods has only 5000 records for the 3 requests