Skip to Content
0
Jan 25, 2023 at 02:28 PM

IDoc Archiving: Write Program(RSEXARCA) performance issue?

425 Views

Hello All,

We are facing issue with IDoc Archiving program. This program scheduled a batch job after 12 hours the job failed with error 'Internal session terminated with a runtime error DBSQL_SQL_ERROR'.

I still see millions of IDOC's records left in IDOC tables to Achieve. And program selection criteria variant has only few status codes(03, 12, 18, 33, 38, 53, 68).

Category ABAP programming error

Runtime Errors DBSQL_SQL_ERROR

Except. CX_SY_OPEN_SQL_DB

ABAP Program SAPLEDI_ARCH

Application Component BC-MID-ALE

Short Text : SQL error "SQL code: -10807" occurred while accessing table "EDID4".

Error:

Database error text: "SQL message: Connection down: [89006] System call 'send'

failed, rc=104:Connection reset by peer {10.5.0.233:62344 ->10.5.0.214:30015}"

  • How to increase the program's performance?
  • Is it possible to run parallel jobs with different variants?
  • Can we have split jobs with different variant?

The Archive Logical file path name is with Date and time ARCHIVE_FILE_IDOC_<DATE>_<TIME>. Will it cause any issue if i run parallel jobs with different variant?

Please help me into it. Please let us know if we have any OSS notes to improve program performance.

Thanks for support in advance.

Regards,

Ashok