ods activation error: datapackage status 9

[Former Member]

Hello BW Experts,

ODS activation error

( Red light )Requset REQU_xxx , data package 000004 incorrect with status 9

( Red light ) Communication error ( RFC call ) occurred

( Red light ) Activation of data records from ODS objects ZCUSTSAL terminated

( Red light ) Request REQU_xxx , data package 000004 not correct.

When we have status 9 for the data package, would it be the best idea to reload the data ?

Any suggestions appreciated.

Thanks,

BWer

[Former Member · Accepted solution]

1.You check SM21 and chek if another session was active at same time, this error occured when your session and another session are waiting for a resource locked by the other.

Moreover Check the infopackage selection and choose PSA and ...3rd option.

Bye

Alessandro

[Former Member]

post the detailed log of error and of surely existant dump in st22

[Former Member]

from st22

Database error text........: "ORA-00060: deadlock detected while waiting for

resource"

Internal call code.........: "[RSQL/UPDT//BIC/AZCUSTSAL00 ]"

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:

-

---

"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC

"GP3XFJK5O3PRLP1IONSCK67HMI2" or "GP3XFJK5O3PRLP1IONSCK67HMI2"

"UPDATE_ATAB"

how can this be corrected?

is there something we can do on the

1) BW Side

2) Basis side

3) DB side

Please suggest

Thanks,

BWer

[Former Member]

Hi

1. Can you go to the MANAGE SCREEN of the ODS.

2. Click on ACTIVATE.

3. A dialog pops up. Then click on the LOG.

4. Select the one which has RED ENTRY and double click.

5. Then it takes you to another screen. Here click the exexute button. This shows a log of WHAT the issue is.

This kind of error usually occurs when the DATA is not in good form. By that I mean any NON BW FORMAT characteristics if not maintained in RSKC.

If it is DEADLOCK 60 then it is a deadlock entry on BW end. Just ACTIVATE it again and it should be solved. Ensure that in TCODE SM12, there are no LOCKS pertaining to that ACTIVE / CHANGE log of ODS.

Let me know, if you need any information.

Regards,

Praveen

Message was edited by: Praveen

[Former Member]

ORA-00060: deadlock detected while waiting for resource

Cause: Your session and another session are waiting for a resource locked by the other. This condition is known as a deadlock. To resolve the deadlock, one or more statements were rolled back for the other session to continue work.

• retry the load

• Wait until the lock is released, possibly a few minutes, and then re-execute the rolled back statements.

IMP--> if you try another time please set the 3rd option of infopackage PSA ... then in Data target so only 1 process at time will be processed..

Message was edited by: Claudio Caforio