DTP failed due to exception error

Question

Hi there,
DTP failed due to an exception error message An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause
Please Help
Thanks
J

Answer 1

Hi.....
I think the full Error is :
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Actually this is a Database related error............the only thing that u can do is increase the number of process assigned for your system .............and just make sure that no other loads are going on at that time..........if going on also.......it should be very limited.........
Also u can check the SAP Note : 631668..............I don't know u have access to SAP Notes or not.........So I am copying it here..........
Symptom
This note applies only to BW systems under ORACLE.
Loading data into InfoCubes terminates with an error: ORA 60, "deadlock detected". The monitor log displays the entry "CALLER 70 missing" and the request is flagged as red.
Other terms
Caller 70, DEADLOCK, ora0060, bitmap, indexes, DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
Reason and Prerequisites
In SAP BW, there are two fact tables for including transaction data for Basis InfoCubes: The F and the E fact table.
Unlike the E fact table, the F fact table contains the information about the request from where the transaction data originates.
Therefore, transaction data is always written to the F fact table and the package dimension contains the request to which the loaded data belongs.
Using 'Request compression', the system reads the data of a request from the F fact table and writes it to the E fact table without request ID and compresses.
For good reporting performance, you must keep only the data of a few requests in the F fact table since the F fact table is partitioned according to the key of the package dimension and the data of all requests is always read. Therefore, you should compress the request if you are sure that the loaded data is correct and that you no longer have to delete the request.
When you install BW on an ORACLE database, BITMAP indexes are created on the fact tables to improve the reporting performance of the system.
These have a negative effect on the performance when loading data and the deadlock mentioned above (ORA 60) may occur as a result. The DEADLOCKs occur during parallel insert operations because ORACLE does not support a blocking concept for BITMAP indexes at data record level.
Solution
Before loading movement data, delete secondary indexes from the F fact table and create them again after the loading process. If the F fact table is small, no performance problems occur.
Alternatively, you can also load requests serially into InfoCubes by first loading the data only into the Persistent Staging Area (PSA) and then serially into the InfoCube. If you use the data transfer process (DTP) for loading in BW 7.0, this option is no longer available.
           NOTE
           This avoids the deadlock problem. However, you should note that after some loading processes, it is necessary to reorganize the BITMAP indexes because they degenerate very heavily and, therefore, the read and writing performance deteriorates dramatically.
Hope this helps........
Regards,
Debjani.......