Quantcast
Channel: SCN : Unanswered Discussions - Data Services and Data Quality
Viewing all articles
Browse latest Browse all 3719

DS job receive invalid read request id for OpenHub table

$
0
0

We recently upgrade our SAP Data Services from 4.1 SP3 to 4.2 SP4 Patch3. Since then, all the OpenHub jobs start failing intermittently with the below error:

 

Read status '' could not be set for Open Hub destination at SAP system . Error is: No suitable namespace available.

 

 

Here is a normal process flow of the OpenHub jobs.

1. DS job started

2. Dataflow trigger a BW process chain to populate the OpenHub table

3. DS RFC server wait for the read request id

4. DS RFC server receive the read request id and pass to the Dataflow

5. Dataflow set the status with the read request id and start to extract data

6. DS job finish

 

In the fail instances, we found that after step 3, DS RFC server receive a read request id (0), write it to AL_SAP_JOB, and pass this invalid 0 id to the Dataflow, even though the process chain is still running and has NOT sent back the valid read request id. The Dataflow then try to set the status to a request id 0 which does not exist in BW, and hence the error occur. The BW process chain complete successfully and send back the valid id to DS RFC server, but RFC server does not know how to deal with the valid id already. Below is the RFC logs.

 

08/25/2015 10:25:28 [    FINE ] Submitting Job : J_OCC_BW_OCC_TX_DTL_Ld on Job Server : HPRABODS002:3500 with execution command :  -NOracle -Sbods -UBODS_LOCAL -PUk0qM1FOSkw -sJ_OCC_BW_OCC_TX_DTL_Ld - ALREQU_52ZO4VKN7EH4M7QLV0LGEQC0520150825102526 -VMODE=F -t5  -BOESHPRABODS003 -BOEUAdministrator -BOEAsecEnterprise -BOEPcHJvZF9hZG1pbjEyMw

08/25/2015 10:25:28 [    FINE ] Getting execution status of the Job : J_OCC_BW_OCC_TX_DTL_Ld submitted on Job Server : HPRABODS002:3500

08/25/2015 10:25:28 [    FINE ] Finished processing RFC call to function: BAPI_ISOURCE_DP_REQUEST

08/25/2015 10:25:42 [    FINE ] (OHSP-DB) BW System PB1:Open Hub IC_D026:Database Operation - ORACLE.BODS.BODS_LOCAL-Lock Information is written to AL_RUNTIME_PARAMETER/AL_SAP_JOB.

08/25/2015 10:25:42 [    FINE ] (OHSP) Lock for open hub IC_D026 is obtained by job J_OCC_BW_OCC_TX_DTL_LD at repository ORACLE.BODS.BODS_LOCAL

08/25/2015 10:25:46 [    FINE ] (OHSP-DB) BW System PB1:Open Hub IC_D026:Database Operation - ORACLE.BODS.BODS_LOCAL-Process Chain Log Id 52ZFE7MIDR97TGIAH8YBBZ5FP with status A is written to AL_RUNTIME_PARAM.

08/25/2015 10:25:47 [    FINE ] (OHSP-DB) BW System PB1:Open Hub IC_D026:Database Operation - Green status of process chain ODL_IC_D026 is written to AL_SAP_JOB.

08/25/2015 10:25:47 [    FINE ] (OHSP-DB) BW System PB1:Open Hub IC_D026:Database Operation - Request notification reply (0) is written to AL_SAP_JOB.

08/25/2015 10:25:47 [    FINE ] (OHSP) Open hub IC_D026 request 0 is delivered to |Data flow DF_OCC_BW_OCCSTG_TX_DTL_Load|Reader IC_D026@ORACLE.BODS.BODS_LOCAL

08/25/2015 10:25:49 [    FINE ] (OHSP) Open hub IC_D026 read status as G is received from |Data flow DF_OCC_BW_OCCSTG_TX_DTL_Load|Reader IC_D026@ORACLE.BODS.BODS_LOCAL

08/25/2015 10:25:51 [    FINE ] Started processing RFC call to function: RSB_API_OHS_3RDPARTY_NOTIFY

08/25/2015 10:25:51 [    FINE ] Open hub [IC_D026] Request ID [5,575,185] Total number of records [0]

08/25/2015 10:25:51 [  SEVERE ] (OHSP) Previous Open hub IC_D026 request is not yet processed. RFC Server can not accept new request Id 5,575,185

08/25/2015 10:25:51 [    FINE ] Finished processing RFC call to function: RSB_API_OHS_3RDPARTY_NOTIFY

 

Does any one have the similar issue on OpenHub or have an idea where the 0 read request id is coming from?

 

Thanks a lot!!

Michael


Viewing all articles
Browse latest Browse all 3719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>