Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Dump in time evaluation PT60

Former Member
0 Likes
1,436

Dear experts I am getting this dump when time evaluation is run..

It was working fine till yeaterday.

Dump info---

Short text
    SQL error in the database when accessing a table.

Information on where terminated
  Termination occurred in the ABAP program "SAPLPA_PACKAGE_SERVICES" - in
   "WRITE_TO_DATABASE".
  The main program was "RPTIME00 ".

  In the source code you have the termination point in line 441
  of the (Include) program "LPA_PACKAGE_SERVICESF02".
  The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
  procedure "WRITE_TO_DATABASE" "(FORM)", but it was neither handled locally nor
   declared
  in the RAISING clause of its signature.

  The procedure is in program "SAPLPA_PACKAGE_SERVICES "; its source code begins
   in line
  405 of the (Include program "LPA_PACKAGE_SERVICESF02 ".

Source code

439
440 * write and commit via secondary db connection
441--> "dump"   delete from pakdatbuf connection (db_con) where relid like 'X%'. "" dump statement
442   insert pakdatbuf connection (db_con) from table pakdatbuf_tab.
443   commit connection (db_con).
444
445 endform.                    " WRITE_TO_DATABASE

Regards,

Sumit Nene

Dear experts I am getting this dump when time evaluation is run..

It was working fine till yeaterday.

Dump info---

Short text
    SQL error in the database when accessing a table.

Information on where terminated
  Termination occurred in the ABAP program "SAPLPA_PACKAGE_SERVICES" - in
   "WRITE_TO_DATABASE".
  The main program was "RPTIME00 ".

  In the source code you have the termination point in line 441
  of the (Include) program "LPA_PACKAGE_SERVICESF02".
  The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
  procedure "WRITE_TO_DATABASE" "(FORM)", but it was neither handled locally nor
   declared
  in the RAISING clause of its signature.

  The procedure is in program "SAPLPA_PACKAGE_SERVICES "; its source code begins
   in line
  405 of the (Include program "LPA_PACKAGE_SERVICESF02 ".

Source code

439
440 * write and commit via secondary db connection
441--> "dump"   delete from pakdatbuf connection (db_con) where relid like 'X%'. "" dump statement
442   insert pakdatbuf connection (db_con) from table pakdatbuf_tab.
443   commit connection (db_con).
444
445 endform.                    " WRITE_TO_DATABASE

Regards,

Sumit Nene

8 REPLIES 8
Read only

Former Member
0 Likes
1,256

Hi Sumit,

We are also facing same issue, your any help would be appreciated.

Read only

0 Likes
1,256

Hello

We faced similar issue. I think this is not particular to HR transaction, it's seem to occur all the other transactions too like pftc, se38, etc. This seems to be an issue when you are trying to access the DB system for writing the data.

Basis team helped us in fixing the issue, am not sure about the solution though.

- Ranganath

Read only

0 Likes
1,256

Ranganath,

We are facing the same issue. Can you ask your Basis Team what they did?

Thanks,

Diana

Read only

d_brummelman
Discoverer
0 Likes
1,256

Hello,

Nobody a solution?

After a upgrade (to EHP4 ECC6.0) we have also this problem.

Best regards,

Dick Brummelman

Read only

Former Member
0 Likes
1,256

We have the same problem.

The delete statement sometimes takes up to 40 seconds to complete.

Read only

Former Member
0 Likes
1,256

Hi,

I think SAP has fixed the problem by a note. The Note has been developed and released on 07-Sep-201.

Please download the same and check it.

Symptom

Any SAP application is aborted with the error term in the program IMPORT_FORMAT_ERROR SAPLPA_PACKAGE_SERVICES.

Solution

The correction of this note catches this situation and calculates the new list.

If none of the attached correction instructions valid for your release level, run the following program change manually:

Change the code SE38 LPA_PACKAGE_SERVICESF02 with the transaction.

Locate the line in the subroutine READ_FROM_DATABASE

Set the modification in the original transaction SPAU back on as soon as a support package level is reached, which includes the correction of this note either, or allow the automatic installation of the notice.

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1629112

Shiva

Read only

Former Member
0 Likes
1,256

Hi there,

The OSS note you mention is not related to my issue.

Thanks

Read only

sjeevan
Active Contributor
0 Likes
1,256

It could be what Shiva Mentioned but I could only find the german version of the note and had to use google translate to translate it into english.

But I also found a note which might be relevant Note 1300463. Y'all may wanna look it up.