ABAP/4 processor: DBIF_DSQL2_SQL_ERROR ... help m...

Former Member · ‎2008 Oct 17

Hello ppl ,

below are the details of the problem i am facing , looking forward to some answers ... thanks in advance ...

Runtime Errors DBIF_DSQL2_SQL_ERROR

Except. CX_SY_NATIVE_SQL_ERROR

Date and Time 13.10.2008 11:15:23

Short dump has not been completely stored (too big)

The error "-60" occurred in the current database connection "LCA".

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

How to correct the error

Database error text........: "POS(1) Work rolled back: tExcept 18757 in

APS_ORDER_GET_"

Database error code........: "-60"

Triggering SQL statement...: "EXECUTE PROCEDURE "APS_ORDER_GET_DATA""

Internal call code.........: "[DBDS/NEW DSQL]"

Please check the entries in the system log (Transaction SM21).

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"

"/SAPAPO/SAPLOM_PLANNING" or "/SAPAPO/LOM_PLANNINGU07"

"/SAPAPO/OM_ORDER_GET_DATA"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"/SAPAPO/OM_ORDER_GET_DATA" "(FUNCTION)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Information on where terminated

Termination occurred in the ABAP program "/SAPAPO/SAPLOM_PLANNING" - in

"/SAPAPO/OM_ORDER_GET_DATA".

The main program was "/SAPAPO/BACKGROUND_SCHEDULING ".

In the source code you have the termination point in line 201

of the (Include) program "/SAPAPO/LOM_PLANNINGU07".

The program "/SAPAPO/SAPLOM_PLANNING" was started as a background job.

Job Name....... "BI_PROCESS_ABAP"

Job Initiator.. "KPPNKS432623"

Job Number..... 10324500

The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred

in

procedure "/SAPAPO/OM_ORDER_GET_DATA" "(FUNCTION)", but it was neither handled

locally nor declared

in the RAISING clause of its signature.

The procedure is in program "/SAPAPO/SAPLOM_PLANNING "; its source code begins

in line

1 of the (Include program "/SAPAPO/LOM_PLANNINGU07 ".

former_member188685 · ‎2008 Oct 17

looks like the error is from standard program.search for any OSS note. with the following key words "DBIF_DSQL2_SQL_ERROR"

"/SAPAPO/SAPLOM_PLANNING"

Former Member · ‎2008 Oct 17

i have forwarded this to the basis team . lets see what comes out.

Former Member · ‎2008 Oct 17

This is strange. Has the problem started occuring after a reboot of the SCM server or after the application of a support package or kernel upgrade?

The shortdump is occuring in function module /SAPAPO/OM_ORDER_GET_DATA during the call to the livecache procedure APS_ORDER_GET_DATA.

During the call to function module /SAPAPO/OM_ORDER_GET_DATA a connection is made to livecache and the APS_ORDER_GET_DATA procedure is called so if livecache is OK then the APS_ORDER_GET_DATA procedure should return correctly.

Steve.

Former Member · ‎2008 Oct 17

thanks steve ...

we had applied kernel 159 some time back which is the latest package ... and we are also applying the SCM patch 14 now .

lets see , i will try to run after we have applied this patch. if the problem persists , i will get back to this forum for all you people's valuable inputs

Former Member · ‎2008 Oct 17

Hello,

This looks like a problem with livecache. Is livecache up and running? You can check using transaction LC10 or ask the BASIS team.

Regards,

Steve.

Former Member · ‎2008 Oct 17

live cache is fine ... i have asked the basis team

Former Member · ‎2010 Dec 24

Hi Vinay ,

Is your problem get solved by applieng the patches ?

I am also facing the same problem. How to solve it ?

Regards,

Deepak.

Clemenss · ‎2010 Dec 24

Hi, there are so many SAP notes on this. Did you check?

i.e.

1. 	0.280 	SCM-APO-SNP-BF 	1263135 	SNP planned order has capreqs for all alternative resources 	07.12.2010
	2. 	0.320 	SCM-APO-INT-PPS 	760511 	Order could not be scheduled, or a dump occurs 	04.10.2010
	3. 	0.220 	SCM-APO-ATP-BF-PAC 	1467959 	Backorder processing takes too long 	14.07.2010
	4. 	0.310 	SCM-APO-PPS-DST-PRE 	1433587 	Dump when navigating to DSPB after Optimizer run 	18.06.2010
	5. 	0.320 	SCM-APO-PPS-POM 	1399327 	/SAPAPO/POM1: Dump due to missing PDS header data 	14.06.2010
	6. 	0.330 	SCM-APO-PPS-POM 	1423833 	Report for checking order iPPE guids w/o entry in database 	19.01.2010
	7. 	0.220 	BC-DB-LCA 	1242250 	Copying lccheck2->lccheck1 	24.08.2009
	8. 	0.260 	SCM-APO-INT-CCR-SLS 	1267216 	/sapapo/CCR: DBIF_DSQL2_SQL_ERROR and performance 	18.11.2008
	9. 	0.260 	SCM-APO-VS-BF 	1251099 	Short dump while executing OM17 for Shipments 	24.10.2008
	10. 	0.220 	BC-DB-LCA 	1241135 	Rescheduling at the end of upload (download or upload) 	03.09.2008
	11. 	0.230 	BC-DB-LCA 	1093076 	SAP liveCache 5.1 LCA build 08 	29.07.2008
	12. 	0.220 	BC-DB-LCA 	1089914 	SAP liveCache 5.0 LCA build 13 	15.07.2008
	13. 	0.220 	BC-DB-LCA 	1156067 	Parallelization during upgrade to SCM 5.0 	21.05.2008
	14. 	0.220 	BC-DB-LCA 	1132416 	/SAPAPO/OM_LC_DOWNLOAD_UPLOAD with large IO lists 	16.01.2008
	15. 	0.220 	BC-DB-LCA 	1034717 	Composite note for Support Package 2, area /SAPAPO/ 	26.10.2007
	16. 	0.250 	SCM-APO-SNP-BF 	1025132 	Performance when reading handling resource data 	25.10.2007
	17. 	0.320 	SCM-APO-PPS-EVA 	1074619 	0APO_PPDS_OPERATION_01 results in short dump 	17.10.2007
	18. 	0.220 	BC-DB-LCA 	1038550 	/sapapo/om_upgr_overview 	03.04.2007
	19. 	0.220 	BC-DB-LCA 	1023146 	Changes to LCAPPS_2006 Support Package 1 	07.03.2007
	20. 	0.220 	BC-DB-LCA 	1019581 	Composite note for Support Package 1, area /SAPAPO/ 	07.03.2007
	21. 	0.220 	BC-DB-LCA 	809824 	Improvement of internal test programs for SP6 	31.03.2006
	22. 	0.250 	BC-DB-LCA 	871122 	SAPAPO 3.1 COM object Build 29 	19.09.2005
	23. 	0.220 	BC-DB-LCA 	516235 	New test programs for quality assurance of SCM 4.0 	09.03.2005
	24. 	0.230 	BC-DB-LCA 	772788 	Improvement to internal test programs for Support Package 15 	04.02.2005
	25. 	0.310 	BC-DB-LCA-ATP 	800154 	Incorrect liveCache connection leads to error 	04.01.2005
	26. 	0.220 	BC-DB-LCA 	775343 	Changes for SCM4.1 Support Package 03 	15.12.2004
	27. 	0.250 	SCM-APO-PPS-PVW 	791123 	TIME_OUT with planning board call from context 	08.12.2004
	28. 	0.310 	SCM-APO-PPS-DST-PRE 	680684 	Exception handling in the XM layer 	03.11.2004
	29. 	0.250 	BC-DB-LCA 	740353 	Search for defective orders 	21.06.2004
	30. 	0.240 	SCM-APO-MD-PDS-GEN 	726166 	Corrections for PDS generation from iPPE master data part 2 	16.06.2004
	31. 	0.290 	SCM-APO-INT-PPS 	727275 	R/3-> APO: Exception condition "LC_APPL_ERROR" raised 	21.05.2004
	32. 	0.260 	SCM-APO-INT-CCR-EP 	587290 	Delta report termination: obj. does not exist" 	16.04.2004
	33. 	0.270 	SCM-APO-PPS-EVA 	696381 	Program termination due to lack of memory 	13.01.2004
	34. 	0.320 	SCM-APO-VS 	681900 	Short dump during creation of TPVS shipment for STO 	20.11.2003
	35. 	0.240 	SCM-APO-INT-CCR-SHP 	678892 	Different problems with delta report for TP/VS transports 	14.11.2003
	36. 	0.250 	SCM-APO-PPS-MMP 	594188 	Genetic algorithm: Activity-fixed orders 	26.08.2003
	37. 	0.220 	BC-DB-LCA 	627937 	Improved internal test programs for SP2 	17.06.2003
	38. 	0.220 	BC-DB-LCA 	588730 	Improved internal test programs as of Support Package 24 	16.05.2003
	39. 	0.220 	BC-DB-LCA 	532325 	/sapapo/om_switch Changing a liveCache 	21.01.2003
	40. 	0.220 	BC-DB-LCA 	497066 	Enhancement of test tools 	17.12.2002
	41. 	0.220 	BC-DB-LCA 	550969 	Improvement of internal test programs for SP11 	10.10.2002
	42. 	0.220 	BC-DB-LCA 	532813 	Improvement of internal test programs for SP22 	10.10.2002
	43. 	0.250 	SCM-APO-INT 	539057 	Missing orders in R/3 and APO after a LC crash 	29.08.2002
	44. 	0.220 	BC-DB-LCA 	401856 	Enhancements to transaction /sapapo/om 03 	16.07.2002
	45. 	0.220 	BC-DB-LCA 	511856 	Improvement of internal test programs for SP21 	01.07.2002
	46. 	0.250 	SCM-APO-PPS-DST 	527256 	Performance of DS applications 	19.06.2002
	47. 	0.230 	BC-DB-LCA 	493033 	Create recovery test program 	06.02.2002
	48. 	0.310 	BC-DB-LCA 	444508 	om16: Short dump during display of orders of a peg area 	19.10.2001
	49. 	0.320 	BC-DB-LCA 	397561 	Diverse short dumps in the om17 	19.04.2001
	50. 	0.330 	SCM-APO-INT-PPS 	382287 	CIF confirmation: Error handling and log entry 	26.03.2001

Regards,

Clemens

Former Member · ‎2010 Dec 24

/giggle

I bet the next question will be like: thanks Clemens can you tell me which note i should look for?

ABAP/4 processor: DBIF_DSQL2_SQL_ERROR ... help me out