on 07-31-2011 12:08 PM
Hi Experts,
We are getting Caller 70 error due to short dump. we are loading the data from source system to data target directly. There is no PSA. When I checked in ST22 that is giving following short dump error. Please help me out ASAP.
Runtime Error DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 07/31/2011 at 01:41:09
An SQL error occurred when accessing a table.
What happened?
The database system detected a deadlock and avoided it by rolling back
your transaction.
What can you do?
If possible (and necessary), repeat the last
database transaction in the hope that locking the
object will not result in another deadlock.
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure "WRITE_ICFACT"
"(FORM)"
.
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The database system recognized that your last operation on the database
would have led to a deadlock.
Therefore, your transaction was rolled back
to avoid this.
ORACLE always terminates any transaction that would result in deadlock.
The other transactions involved in this potential deadlock
are not affected by the termination.
How to correct the error
The exception must either be prevented, caught within the procedure
"WRITE_ICFACT"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-00060: deadlock detected while waiti
resource"
Internal call code.........: "[RSQL/INSR//BIC/FWDM_CAPFC ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself
use the following search criteria:
Thanks,
Suresh
Hi,
This error generally occurs when the processing time for loading is too large.
Usually due to to large amount of data, Start Routine Looping for infinite time, Erroneous data etc.
If all records from source system has arrived into PSA. Just right click on the data packet that was not updated and select "Manual Update".
Alternatively you can check following things also,
1) If the Master Data is getting loaded for the first time then in that case we can reduce the Data Package size and load the Info Package.
2) If you are trying to load the Transactional and Master Data together and this error occurs then we can reduce the size of the Data Package and try reloading, as system may be finding it difficult to create SID's and load data at the same time. Or we can load the Master Data first and then load Tranactional Data
3) Once we are sure that the data has not been extracted completely, we can then go ahead and delete the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage again.
Regards,
Durgesh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suresh,
Drop and recreate the indexes for the mentioned cube and then try loading the data.
Regards,
Rangz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please find the below links.
http://wiki.sdn.sap.com/wiki/display/BI/Caller70Missing-error
Hope it's helps you.
Thanks and Regards,
Venkat.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
o Whenever we are loading the Master Data for the first time, it creates SIDu2019s. If system is unable to create SIDu2019s for the records in the Data packet, we can get this error message.
o If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
o Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
o If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
o It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
o It is a system error which can be seen under the u201CStatusu201D tab in the Job Over View.
What happens when this error occurs ?
The exact error message is u201CSystem response "Caller 70" is missingu201D.
It may happen that it may also log a short dump in the system. It can be checked at "Environment -> Short dump -> In the Data Warehouse".
What can be the possible actions to be carried out ?
If the Master Data is getting loaded for the first time then in that case we can reduce the Data Package size and load the Info Package. Processing sometimes is based on the size of Data Package. Hence we can reduce the data package size and then reload the data again. We can also try to split the data load into different data loads
If the error occurs in the cube load then we can try to delete the indexes of the cube and then reload the data again.
If we are trying to load the Transactional and Master Data together and this error occurs then we can reduce the size of the Data Package and try reloading, as system may be finding it difficult to create SIDu2019s and load data at the same time. Or we can load the Master Data first and then load Tranactional Data
If the error is happening while ODS activation cause of no processes free, or available for processing the ODS activation, then we can define processes in the T Code RSCUSTA2.
If error is occurring due to Read/Write in ODS then we need to make changes in the schedule time of the data loading.
Once we are sure that the data has not been extracted completely, we can then go ahead and delete the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage again.
Monitor the load for successful completion, and complete the further loads if any in the Process Chain
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Suresh,
"Caller 70 Missing" is basically comes if the "Processing Overdue".
Moreover from your dump message, there was a deadlock in your source system. You have to check with your BASIS team to unlock or make it free.
Try loading again when ever your source system load is less. Because your extractor is trying to read huge amount of data.
Regards,
Suman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.