Skip to Content
0
Former Member
Sep 05, 2012 at 02:40 PM

Unable to delete the DSO content .

85 Views

Hi,

I am unable to delete the content from the Standard DSO. This is happening in the Quality System.

1)I did delete the data from the Above Cubes.

2) Tried to delete the data request by request---No success.- The Screen turns back to normal with the Reporting symbol

3) Tried right click delete content - then it runs for long time and gives the following message - "Database table /BIC/AXXXXXXX could not be deleted or recreated."

4) Tried Deleting in the Background - No success - Here is the message from the Job Log

"No records found for request ODSR_4ZXXXXXXXXXXXXXXXXX in change log /BIC/B0002873000 of DataStore ZXXXXXX

Deletion of request DTPR_4RXXXXXXXXXXXXXXXXX from data target ZXXXXX failed

Deletion of request DTPR_4QZXXXXXXXXXXXXXXXXX from data target ZXXXXXfailed

Deletion of request DTPR_4QYXXXXXXXXXXXXXXXXX from data target ZXXXXXfailed

Deletion of request DTPR_4R1B5XXXXXXXXXXXXXXXXX from data target ZXXXXX failed

Deletion of request DTPR_4QZSXXXXXXXXXXXXXXXXX from data target ZXXXXX failed

Deletion of request DTPR_4QYWNXXXXXXXXXXXXXXXXX from data target ZXXXXXfailed

No records found for request ODSR_4R1XXXXXXXXXXXXXXXXX in change log /BIC/BXXXXXXX of DataStore ZXXXXX"

This is referring to the Change log table. Intersting point i saw is the change log table was empty , this is because there was process type in the process chain to delete the change log content older then 5 days.

5) Tried SE14 - No success...Error Message

"

Activate dependent table type /BIC/WAZYXXXXXXXXXXX

Table type /BIC/WAZYXXXXXXXXXXX was activated

sql:

DROP TABLE "/BIC/AZXXXXXXX" +LOCATION

[IBM][CLI Driver][DB2] UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE

RESOURCE. REASON 00E70081

DDL time(___1): ...600.698 milliseconds

/BIC/AZYBLD01900 could not be removed

Statements for Table /BIC/AZXXXXXXXX could not be executed

Request for /BIC/AZYXXXXXXXXXX could not be executed"

Please provide your valuable suggestions what might have gone wrong here?

Regards,

Adhvi.