Hello everyone.
We have a new portion of questions and we'll be very grateful for any replies.
Today we encounter yet another new problem. The issue is connected with the table tblDTSlog.
In a certain moment this table became self-blocked i.e. one process of inserting data in the table became “sleeping” and the entire table was locked because of it. The following inserts or updates were “suspended” because of the lock. This resulted in inability to connect to the server via Excel add-in or connect to BPC administration. Also any activity in the system became impossible, “view status” button resulted in an empty query after a long delay, packages didn’t run.
After restarting both application and database servers the situation normalized for a mere two hours when the same problem reoccurred again.
Our next thought was about a large tblDTSlog table(200k rows, we have a rather busy environment). Several notes and threads on this forum regarding the size of the table were found. After that we cleared the table and now hope that solved the issue.
After work I've found a relevant note 1551852 which describes a bug. But unfortunately I can't understand whether this bug was fixed in some service pack or not. How that question could be clarified?
Also I think we should schedule some sort of archiving and clearing of the table say in Sunday night. Is that a reasonable thought? And could the size of the table be the cause of the problem? We have many users running different packages and a scheduled Light Optimized Package every 5 minutes. Besides that our application has about 90 million of records in FACT table. Could that affect the performance a lot?
Also new packages with an empty start time field display after clearing the table at the end of Status window. I've found a thread http://scn.sap.com/thread/1666612 about the same behavior and will try some solution mentioned tomorrow.
One last question - is there any list of tables which should be especially "tenderly" maintained? For instance, tblLogs(or something like that, can't provide the exact name right now) table in Appset database has also more than 200k rows. Should we consider archiving and clearing it?
Thanks in advance for any thoughts.
BR, Dmitry.
