Hi
When we run /SAPAPO/SEQ_PLANNING_RUN
we met one dump.
Hope you experts can help me.
The detailed information listed below.
Runtime Errors DBIF_DSQL2_SQL_ERROR
Exception CX_SY_NATIVE_SQL_ERROR
Date and Time 18.12.2007 04:37:37
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 600 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: DbpError -28815
errorKind = 0 i"
Database error code........: 600
Triggering SQL statement...: "EXECUTE PROCEDURE "APS_ORDER_CHANGE""
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_PLANNINGU08"
"/SAPAPO/OM_ORDER_CHANGE"
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_CHANGE" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "sishu080"
Network address...... "210.75.71.155"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 38
Shortdump setting.... "full"
Database server... "sishu091"
Database type..... "ORACLE"
Database name..... "SPA"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 31 2006 20:53:47"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 2799072
EM...... 0
Heap.... 1354694704
Page.... 24576
MM Used. 1353766000
MM Free. 65120
User and Transaction
Client.............. 210
User................ "******"
Language key........ "E"
Transaction......... " "
Program............. "/SAPAPO/SAPLOM_PLANNING"
Screen.............. "/SAPAPO/SEQ_PLANNING_RUN 1000"
Screen line......... 33
Information on where terminated
Termination occurred in the ABAP program "/SAPAPO/SAPLOM_PLANNING" - in
"/SAPAPO/OM_ORDER_CHANGE".
The main program was "/SAPAPO/SEQ_PLANNING_RUN ".
In the source code you have the termination point in line 104
of the (Include) program "/SAPAPO/LOM_PLANNINGU08".
The program "/SAPAPO/SAPLOM_PLANNING" was started as a background job.
Job Name....... "DY10_D_PPDS02 MMP_ST_L1"
Job Initiator.. "YINGBQ"
Job Number..... 04004200
The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
in
procedure "/SAPAPO/OM_ORDER_CHANGE" "(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_PLANNINGU08 ".
Source Code Extract
Line SourceCde
74 ls_get_changed_options-send_chg_ionode = gc_true.
75 ENDIF.
76 IF et_changed_io_pp_nodes IS REQUESTED and
77 ( not IS_GET_CHANGED_OPTIONS is supplied or
78 IS_GET_CHANGED_OPTIONS-send_chg_io_pp = gc_true ).
79 ls_get_changed_options-send_chg_io_pp = gc_true.
80 ENDIF.
81 IF et_changed_pegids IS REQUESTED and
82 ( not IS_GET_CHANGED_OPTIONS is supplied or
83 IS_GET_CHANGED_OPTIONS-send_chg_pegid = gc_true ).
84 ls_get_changed_options-send_chg_pegid = gc_true.
85 ENDIF.
86 IF et_deleted_fix_pegging IS REQUESTED and
87 ( not IS_GET_CHANGED_OPTIONS is supplied or
88 IS_GET_CHANGED_OPTIONS-send_del_fix_peg = gc_true ).
89 ls_get_changed_options-send_del_fix_peg = gc_true.
90 ENDIF.
91
92 ls_controlparameters = is_controlparameters.
93 IF NOT et_sched_log IS REQUESTED.
94 ls_controlparameters-get_schedlog = gc_false.
95 ENDIF.
96
97 start_function 'OM_ORDER_CHANGE'. "#EC *
98 * Verbindung zum liveCache aufbauen
99 check_server.
100 connect_to_livecache.
101 * COM-Routine zum Anlegen bzw. Überschreiben eines Zeitstrahls
102
103 EXEC sql.
/>>>>> execute procedure "APS_ORDER_CHANGE" (
105 in :ls_gen_com_params,
106 out :lv_rc,
107 OUT :Et_rc,
108 in :it_order_method,
109 in :it_ordkeys,
110 in :it_ordmaps,
111 in :it_orders,
112 in :it_activities,
113 in :it_mode,
114 in :it_cap_reqs,
115 in :it_positions,
116 in :it_inputs,
117 in :it_outputs,
118 in :it_prodflow,
119 in :it_intern_constraints,
120 in :it_extern_constraints,
121 in :it_charact_val_acts,
122 in :it_charact_req_inpnode,
123 in :it_charact_val_outnode,
Contents of system fields
........
Edited by: Xiangnian Liu on Dec 18, 2007 7:58 AM
Edited by: Xiangnian Liu on Dec 18, 2007 7:59 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.