cancel
Showing results for 
Search instead for 
Did you mean: 

PSA Delete Step is Taking too long

0 Kudos

Hi,

Can anyone please help me narrow down an issue where a scheduled "Delete PSA Request" that has historically taken no more than 5 minutes to complete (in process chain) is now taking more than 8 hours? What are some of the things that I can look at to determine why this is the case? Thanks in advance!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi ,

Normally index creation or deletion takes longer time when  your database statistics are not updated properly, so you can check databease stats after your data loading is completed and index generation is done.

If the following chain is running number of times in a day then you need not delete and create the Index again and again .

Then you can remove the delete and create index step from the Original chain and create an separate chain with delete and create index step and run it once when you have less load on the system .

Hope this helps .

Thanks

Answers (5)

Answers (5)

Former Member
0 Kudos

Are you facing the same while manually deleting the PSA?

former_member319798
Discoverer
0 Kudos

Are you using a SQL Server db by any chance? There's an snote for PSA performance issue with this DB.

former_member182196
Contributor
0 Kudos

Hi,

Try to activate all data source with the help of this program "RSDS_DATASOURCE_ACTIVATE_ALL" and after that check it.

and delete your PSA table data ones in SE14 then select this option

I hope this will help.

Regards,

SM

former_member182470
Active Contributor
0 Kudos

Have you checked/analyzed the PSA deletion job log in the process chain-->Display messages?

You can understand easily which step is taking long time and Why?

I feel you must have more BGds available in SM50. You can split your variants in to two branches in the chain and distribute the datasources equally.

You can find PSA tables in RSDSTS, RSTSODSPART tables

0 Kudos

Hi Suman,

I did. I looked at the displaying messages and noted that one of the logs that took the longest was:

"Request REQU_# deleted from PSA;

RSREQICODS entry also deleted"

The above step started at 8:47 AM and it was not until 14:55 that the next step started

And then again, another one of these was logged at 14:58

"Request REQU_# deleted from PSA;

RSREQICODS entry also deleted"

but it was not until 19:24 that it had to be manually cancelled by our team.

I also went on SM37 to see these entries but I do not get much info other than start time and description. How can you easily tell the "why" part of taking too long from these logs? especially with a request that was already deleted from PSA....thank you again!

former_member182470
Active Contributor
0 Kudos

You can check parallely in SM50 while deletion of PSA job going on. I mean you can see what all SQL statements have been running and where it is spending long time etc..

I suspect there are no proper indexes on RSREQICODS table. That's why your job spends lot of time there, it seems. Try to create indexes on it and run your deletion job again.

Message was edited by: Suman Chakravarthy K

MGrob
Active Contributor
0 Kudos

Hi

Have you tried with tx RSRV -> PSA Tables -> Consistency Check for PSA?

Sounds like an inconsitency in your psa table

Hope it helps

Martin

0 Kudos

Thank you Martin. The PSA Delete variant has several datasources for which PSAs are deleted. Is there an easy way to find the PSA table names? We are on BW 7.3 sp 6. Thanks again!

RamanKorrapati
Active Contributor
0 Kudos

Hi ,

Am not sure, try to check table RSPCPROCESSLOG, process type as PSA_DEL(similar term) keep filter and check it out. you will get all psa deletion chains which are have. finding to particular might be hard.

As you said your PC chian takig more time mean you will know the process chain so thru that we can know the psa/data source.

Coming to your issue:

As my guess your data source may be disturbed.so better to try to activate your Data source by using program"RSDS_DATASOURCE_ACTIVATE_ALL" and later check it.

Thanks

Former Member
0 Kudos

You can use function module RSS2_PSA_NEW_OLD_DS to get PSA table name.

If it is the situation before & after migration to 7.3, program RSTCT_DELETE_PSA_DATA might be useful.

Thanks,

Surya

MGrob
Active Contributor
0 Kudos

Hi

Double click on your psa then goto -> technical attributes and you'll see your psa table.

do that for each you need to check.

hope that helps

Martin

former_member182196
Contributor
0 Kudos

Hi,

Double click on data source and click on this technical setting

In this below screen you can find psa table name.

Do this process for each you need.

Regards,

SM