cancel
Showing results for 
Search instead for 
Did you mean: 

Query running forever

Former Member
0 Kudos

Hi ,

When i am running query it is running forever and i am not able to get the results. But , iam able to get the results by using the LISTCUBE transaction very fastly for the same selection criteria.

When I observed in SM66 , The work process is always trying to Read the table /bic/03035

appreciate your suggessions and valuble solutions

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This happened to me recently with a query that was pulling data from a multi-provider. The query also had a lot of row and column definitions.

My solution was to re-write the query so that it pulled from a basic info-cube (because multi-providers are slow) and to remove as much column definition as possible. It now refreshes very quickly.

There is a limit to how much work you can ask BW to do, and this limit should be respected or else you will encouter severe performance problems.

I hope this helps.

nikhil_chowdhary2
Contributor
0 Kudos

Hi,

I had the same problem yesterday - the only difference was that SM66 showed a different table name.

My problem was solved by getting the Database team to analyze that particular table. The DB logs showed that the table had been Analyzed a long time back. By getting the table analyzed the execution time for the query was cut down from 15 minutes to 30 seconds.

See if this helps in your scenario as well. The table name that you have given does not appear to be the full table name - enable long text in SM66 to display the table name in full and ask you DB team to check when that table was last analyzed - if it was a long time back then get then to analyze it again and see if it improves the query performance.

Hope it helps,

Regards,

Nikhil

Former Member
0 Kudos

Hi Nikhil ,

Thanks for the valuble suggession. I tried what you suggested and it is working fine.

Answers (2)

Answers (2)

former_member184494
Active Contributor
0 Kudos

Bhanu,

Looks like the query is scanning the aggregate for a particular cube ... check in RSRT and also in the execute and debug option - select "Display SQL Query" for further clarity. Make sure your Aggregates are filled up / active - in RSRT see if you can get the output when you deactivate aggregates... it could be that the aggregates have some problem..

Arun

Former Member
0 Kudos

Hi

I suspect is there any coding in the form of variable exits....something in this particular query which can this trouble

Have you checked the query in RSRT and hit the Execute + Debug

Cheers

N Ganesh

    • assign points if useful**