SLT | SQL exception occurred in receiver system (rfc dest. NONE)

[Former Member]

Hi There,

SLT | Error while replication from LTRC (Application Logs)

------------------------------------------------------------------------------------------

Start of batch processing

Begin of data transfer (mass processing 016, access plan/precalc. 00001)

Current server:

Current work process number: 19261

Run 0000000001 started at 20150812 053255

SQL exception occurred in receiver system (rfc dest. NONE)

Execution of program /1CADMC/OLC_800000000000252 failed, return code 3

Run 0000000001 started at 20150812 053256

SQL exception occurred in receiver system (rfc dest. NONE)

Execution of program /1CADMC/OLC_800000000000254 failed, return code 3

End of batch processing

------------------------------------------------------------------------------------------

Any thoughts welcome!

regards,

Rv

[Saritha_K · Accepted solution]

Hi,

Can you please tell us about your DMIS version?

Is SLT on same source system or on a different server?

Please check logs(ST22/M21) on both source and SLT system.

Have you applied all correction notes for your DMIS version?

Regards,

Saritha K

[Former Member · Accepted solution]

Hi Saritha,

We are on DMIS SP07, SLT is on source system.

Standard logs gave no useful info & correction notes were applied.

I guess its better to upgrade SP09, will update this post with SP09 result. 

regards,

Rv

[Former Member · Accepted solution]

Updated to SP09 applied notes

0002175207 SLT (2011 SP09) - Correction 01

0002200105 SLT (2011 SP09) - Correction 02

Error still persists...

SQL exception occurred in receiver system (rfc dest. NONE)

Execution of program /1CADMC/OLC_800000000000252 failed, return code 3

[Saritha_K · Accepted solution]

Hi,

Is note 1765890 ,2199644,2191243 applicable in your case?

Regards,

Saritha K

[former_member195828 · Accepted solution]

Hi Saritha,

I have been facing same issue in SLT server while replicating for small tables ( T001) also. Suggested notes by you are not applicable to my system It seems.

Current version of my system is as below.

Kernel : 721 Release and patch level is 100

BASIS : SAP EHP 2 for SAP NetWeaver 7.0 ( 7.02 Patch level 12)

DMIS : 2011_1_700 and SP08

Connection established between ECC ( source ) >SLT > Oracle ( TOAD tool) ( Target)

And also I can see below erros for the table (T001) in LTRC

Please let me know if you have any other thoughts on this.

Balimi : Please share if you resolved this issue. Thank in advance.

Thanks,

Naresh

[Former Member · Accepted solution]

This error tuned out to be much more than a typical SLT error.

Its an SQL exception.

INSERT /1LT/00000000247 CLIENT SPECIFIED CONNECTION (con_name)
FROM TABLE _IT_IO_R_DD02L
ACCEPTING DUPLICATE KEYS.

and it fails with sqlcode 10709- and message Connection failed

Details below :

In order to reproduce the issue:

• TA LTRC ->Expert Functions -> Reset Load and Replication Status and execute the report to RESET Failed flags
• TA LTRC -> Tab ‘Data Transfer Monitor’ Doubleclick the table DD02L
• Open a SE37 with /1CADMC/OLO_800000000000404 and set a breakpoint at line 123.
  This is our problematic ddl-statement.
• Run the transfer job by using SE38 report DMC_STARTER with following parameter:

• Run the program and you should get to the breakpoint.

Note: During this process the configuration has to be turned off (LTRC –> Administration Data).

   Will update the post with the developments further

[former_member195828 · Accepted solution]

Hi Balimi,

Did you resolve the issue? I have raised an OSS message but yet to receive update from them.

Still am getting same error. Please share if you managed to resolve this SQL issue.

Execution of program /1CADMC/OLC_010000000002453 failed, return code 3

Message no. DMC_RT_MSG046

Thanks in advance.

Naresh

[Former Member · Accepted solution]

We managed to identify the root cause:

SLT connection reads both DB instance numbers (source & target), In our case source(02) and Target(88).

We have identified SLT looking for Taget(00) instead, So we changed target to 00 and it worked.

This may be a work around only, need to identify why SLT is not accepting 88.

Hope this helps

regards,

Rv

Be responsive: Please mark answer as "helpful” or “correct” so that other members can find the answers easily.

[former_member195828 · Accepted solution]

Hi,

This issue resolved after applying the latest dboraslib (/sapmnt/<sid>/exe ) files.

Naresh

[former_member182537 · Accepted solution]

hi Balimi,

We have started facing same issue suddenly but in our case target is oracle

so its like SAP-->SLT->ORACLE...

sm21 logs says memory space issue in oracle and hence now we are not able to laod any tables.

was your issue same as well ? what was target in your case ?

thanks

Nilesh

[arsnlgunnr · Accepted solution]

Naresh,

where did you apply the latest dboraslib?  Just on the SLT instance or both the SLT and the Source?

Thanks.

[former_member195828 · Accepted solution]

Hi Jayson,

Need to apply the patches only on SLT server.

Naresh