cancel
Showing results for 
Search instead for 
Did you mean: 

ODS Activation failed - Communication error (RFC call) occurred

former_member208595
Active Participant
0 Kudos
200

Hi All,

While activating ODS (BW3.5), we are getting this below error.

Communication error (RFC call) occurred

Activation of data records from ODS object A2Z1OWEB terminated

No confirmation for request ODSR_4KGJ2HIBEH68WPDF9U5J3TNKB when activating the ODS object A2Z1OWEB

Request REQU_4KHXEKWQB8G29LZ54Z2OFLHMZ, data package 000001 incorrect with status 9 in rsodsacstreq

Request REQU_4KHXEKWQB8G29LZ54Z2OFLHMZ, data package 000001 not correct

Inserted records 1-; Changed records 1-; Deleted records 1-

Datasource is flat file based, from this we are loading data to ODS. We are loading only 2records. The datasource is active, connection check is ok. There is no SID issue also.

Need your inputs urgently.

Regards,

Asish

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi,

1. Check the data that ur loading, because there are some errors in data which ur loading, such that the Qualtity status is not ok. If the qualtity status is not ok, activation of data is not possible.

2. May be you have select the checkbox "Automatically activate the records", when you are creating the ODS, but you didn't select "Automatically make the quality status to OK" in the setting of ODS.

So, Create a new ODS, and select "Automatically make the quality status to OK" and "automatically activate the records in ODS".

Thanks & Regards,

Vipin

former_member208595
Active Participant
0 Kudos

Hi,

The quality status is maintained as OK in the ODS settings.

Regards,

Asish

Answers (3)

Answers (3)

Ram7
Explorer
0 Kudos

Hello

I think this issue is because of high disk space consumption. I think to resolve this Basis team should be contacted and if they are in a position to extend the same it possibly won't happen. This is purely because of disk space.

Please check in the transaction DB02 and verify the percentage of use (Production system) PSABWP. This needs to be get to less percentage indeed to solve this issue. At the same time please delete OLD PSAs to get few move on.

I hope this helps all.

Thanks,

Ram

Former Member
0 Kudos

Hi,

Just check the date preview before loading it and then load the data.

former_member21257
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Asish,

These are the related error cdes:

Communication error (RFC call) occurred

Message no. RSDRO108

Activation of data records from ODS object A2Z1OWEB terminated

Message no. RSM1102

No confirmation for request ODSR_4KGJ2HIBEH68WPDF9U5J3TNKB when activating the ODS object A2Z1OWEB

Message no. RSM1185

I expect that there are related ORA errors (possibly ORA-00600) in your System log.

Usually these notes will solve this issue:

84348 - Oracle deadlocks, ORA-00060

634458 - ODS object: Activation fails - DEADLOCK

515711 - Missing indexes after reorganizing PSA tables

595975 - ODS object: Activating SAPSQL_ARRAY_INSERT_DUPREC (also relevant for BW 3.50)

Rgds,

COlum

former_member208595
Active Participant
0 Kudos

Hi Cronin,

I have checked all the SAP notes given by you, but didnt help. Can you give us any more suggestion for the same.

Regards,

Asish

shanthi_bhaskar
Active Contributor
0 Kudos

Activate the Datasource and and DTP try to load once agian

former_member21257
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

Are there any related ORA errors in SM21 or dumps in ST22?

Rgds,

Colum

former_member208595
Active Participant
0 Kudos

Hi Cronin,

There is DBIF_RSQL_SQL_ERROR (An SQL error occurred when accessing a table "/BIC/B0001104000"). I have checked with my project Basis team & found that many deadlocks happened in the database.

Regards,

Asish

former_member208595
Active Participant
0 Kudos

Hi ,

Already we tried initially, but no luck.

Regards,

Asish

Former Member
0 Kudos

Hi Asish,

Since you are saying that basis has confirmed that there were many deadlocks during earlier activation, so please try to activate the request again and check if the same issue appears again.

You can check if there is any other lock on the DSO in SM12.

Regards,

Hemant Khemani