NI 4060 Procedure SQL-Error in Calibration Executive 2.0

hi,
while trying to calibrate a PXI-4060 DMM module (procedure version 2.0) under calibration executive 2.0 following error is screened and the calibration fails:
Error executing substep 'Post'. The following SQL command failed: 'SELECT RESISTANCE.ID, RESISTANCE.Resolution, RESISTANCE.Delay, RESISTANCE.AutoZero, RESISTANCE.Range, RESISTANCE.Test_Point, RESISTANCE.Error_24_Hour, RESISTANCE.Offset_24_Hour, RESISTANCE.Error_1_Year, RESISTANCE.Offset_1_Year, RESISTANCE.Error_Temp, RESISTANCE.Offset_Temp, RESISTANCE.TempFactor, RESISTANCE.Lower_Limit_24_Hour, RESISTANCE.Upper_Limit_24_Hour, RESISTANCE.Lower_Limit_1_Year, RESISTANCE.Upper_Limit_1_Year FROM RESISTANCE...'
Native error code -2147217904 0x80040e10
Mi
crosoft OLE DB Provider for ODBC Drivers:
[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 8.
NI-DAQ 6.9, IVI-engine 1.83 and Test-Stand 1.0.3 are installed on the system. Even the calibration with an older version (1.1) of the procedure fails (ividmm.dll error message).
When using calibration executive with E-Series modules the calibration can be performed without any error messages.
How can we fix this problem? We appreciate your help.
Best regards,
Dipl.-Ing. Philip M. Fleischmann - CTO
esz Elektronik-Service GmbH
Max-Planck-Str. 16
D-82223 Eichenau
Phone: +49-8141-88887-39
Fax: +49-8141-88887-77
e-Mail: [email protected]
http://www.calibration-support.com

Hi,
I'll have to research on this problem. I have seen it only once and haven't been able to reproduce it. What version of MDAC (Microsoft Data Access Components) do you have installed?. You can find an utility called Component Checker in the microsoft web site:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q307255&
Is this the first time you're trying to run this system?. Or, was it a running system?, if so, What changes were made?. Was LabVIEW or any other program installed?. What OS are you using?
I did a search for "ividmm.dll" at www.ni.com. Try the solution presented here for the ividmm.dll error.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/a22034dca3da035a86256a1b00641e2b?OpenDocument
I'll let you know wh
en I get more info.
DiegoF.
National Instruments

Similar Messages

SQL error 3113 occurred when executing EXEC SQL.

Hi,
We are facing one typical problem, One background is failing regularly with
below dump. as we now got all notes giving information, if database restarted
taking backup, these type of failures occur, but our database is only down for backup once in a week, but it is failing with frequenly.
in this two servers are located in different place, in this job tries to connect
another server to get material statistics.
It is giving some error message in sm21 with
SQL error 3113 occurred when executing EXEC SQL.
work procees in reconnect mode.
all notes saying these types of dump occur when database restared, but this dump
even though database is up.
below is short dump, please can anyone help me from this problem.
ABAP runtime errors    DBIF_DSQL2_SQL_ERROR
      Occurred on    08.01.2007 at 00:30:28
>> Short dump has not been completely stored. It is too big.
SQL error 3113 occurred when executing EXEC SQL.
What happened?
The error occurred in the current database connection "AZ1".
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel#"
Triggering SQL statement...: "select mara.groes, mara.brgew, mara.ntgew,
mara.gewei, mara.volum, mara.voleh, mara.mstae, mara.mstde, mara.prdha,
marc.matnr, marc.werks, marc.mmsta, marc.mmstd from sapr3.mara, sapr3.m
where sapr3.mara.mandt = sapr3.marc.mandt and sapr3.mara.matnr =
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"DBIF_DSQL2_SQL_ERROR"
"ZM2431216 " or "ZM2431216 "
"EXTRACT_GENERAL_DATA"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in th
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error o
or which actions and input led to the error.
System environment
SAP Release.............. "46C"
Application server....... "essceu3"
Network address.......... "172.19.119.198"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C7ADBD4C00"
Database server.......... "ukblx176"
Database type............ "ORACLE"
Database name............ "EU3"
Database owner........... "SAPR3"
Character set............ "es_ES.ISO8859-1"
SAP kernel............... "46D"
Created on............... "Jul 9 2006 20:26:33"
Created in............... "AIX 1 5 00447C4A4C00"
Database version......... "OCI_920__OCI_7_API "
Patch level.............. "2257"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE
8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 10.2.0.."
SAP database version..... "46D"
Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
5, , System build information:,                                      , LCHN :
841480"
User, transaction...
Client.............. 600
User................ "MPZMMES"
Language key........ "S"
Transaction......... " "
Program............. "ZM2431216 "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP/4 program "ZM2431216 " in
"EXTRACT_GENERAL_DATA".
The main program was "ZM2431216 ".
The termination occurred in line 980
of the source code of program "ZM2431216 " (when callin
The program "ZM2431216 " was started as a background jo
Source code extract
009500              mara.ntgew,
009510              mara.gewei,
009520              mara.volum,
009530              mara.voleh,
009540              mara.mstae,
009550              mara.mstde,
009560              mara.prdha,
009570              marc.matnr,
009580              marc.werks,
009590              marc.mmsta,
009600              marc.mmstd
009610        into :w_ops-groes,
009620              :w_ops-brgew,
009630              :w_ops-ntgew,
009640              :w_ops-gewei,
009650              :w_ops-volum,
009660              :w_ops-voleh,
009670              :w_ops-mstae,
009680              :w_ops-mstde,
009690              :w_ops-prdha,
009700              :w_ops-matnr,
009710              :w_ops-werks,
009720              :w_ops-mmsta,
009730              :w_ops-mmstd
009740        from sapr3.mara, sapr3.marc
009750        where sapr3.mara.mandt = sapr3.marc.mandt
009760          and sapr3.mara.matnr = sapr3.marc.matnr
009770          and sapr3.mara.mandt = :p_mandt
009780          and sapr3.mara.matnr = :w_ebs-matnr
009790          and sapr3.marc.werks = :p_owerks
    >    ENDEXEC.
009810 endform.                    " extract_general_data
009820 *&
009830 *&      Form append_i_ops
009840 *&
009850 *      Appends W_OPS to I_OPS
009860 *
009870 form append_i_ops.
009880    append w_ops to i_ops.
009890 endform.                    " append_i_ops
009900 *&
009910 *&      Form extract_material_description
009920 *&
009930 *      Extracts a Material Description from the remote database an
009940 *      modifies the current record in I_OPS.
009950 *
009960 *        >P_SPRAS Language Key
009970 *
009980 form extract_material_description using    p_spras.
009990    EXEC sql performing set_langauge.
Contents of system fields
SY field contents..................... SY field contents............
SY-SUBRC 0                            SY-INDEX 0
SY-TABIX 1                            SY-DBCNT 1
SY-FDPOS 18                            SY-LSIND 0
SY-PAGNO 0                            SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+..
W_EBS-PRAT4
                              2
                              0
W_OPS-GROES
                              22222222222222222222222222222222
                              00000000000000000000000000000000
W_OPS-BRGEW                    #######
                              0000000
                              000000C
W_OPS-NTGEW                    #######
                              0000000
                              000000C
regards,
krishnaiah.

Hi,
This is usually a SERVER SIDE DATABASE PROBLEM or SQLNET LISTENER (server side) PROBLEM. The client side should initially be ignored and instead the server should be investigated. In rare cases, this can be caused by client
side memory or other resource problem, or a DLL version mismatch, but this is
unlikely.
Enlist the assistance of your DBA. Then reproduce the ORA-3113 error on your
client application. Ask your DBA to look at the database side Alert.log and
trace files and look for ANY activity. Any activity that coincides with your
ORA-3113 will be a clue.
REgards
Vinod

Pxi-4071 error on calibration executive

hi!
i have this little problem with my NI calibration executive. The error says
" Error-1071001424 occurred at Error-1071001424 occurred at ***configcalibratorandwait.vi
Possible reason(s)
Current Compliant Voltage Exceeded".
Can you guys help me on this? I am calibrating this NI DMM PXI-4071. Please see attached captured error.
thanks.
ating

popoi,
Thanks for posting on the NI forums. I have a couple questions for you that should help us get to the bottom of the problem.
What version of Calibration Executive are you using? You should be able to find this by going to the Help Menu >> About Calibration Executive.
What Equipment are you using to perform the calibration? There is a list of equipment here.
Is this the only board that you are having difficulty calibrating with Calibration Executive?
Thanks!
Aaron W.
National Instruments
CLA, CTA and CPI

ORA-06521: PL/SQL: Error mapping function with 10.1.0 external procedure

We have an external procedure running fine on 8.1.7 on VMS. After compiling and linking succesfully under 10.1.0, I get ORA-06521 PL/SQL: Error mapping function and ORA-06522: ERROR - vms_dlsym for file x, where x in the filename of the linked executable. Another external procedure that does not connect to the 10.1.0 database runs fine. What could be causing this error in Server 10.1.0 on VMS?
Thanks,
Dave

Here is the code to create the function:
CREATE OR REPLACE FUNCTION f1
(h_file_name IN VARCHAR2)
RETURN BINARY_INTEGER
IS EXTERNAL
LIBRARY l1
NAME "f1"
LANGUAGE C
WITH CONTEXT
PARAMETERS
(CONTEST,
h_file_name string);
Here is the beginning of the Pro*C:
int f1(epctx, h_file_name)
OCIExtProcContext *epctx;
char h_file_name[70];
char h_line_txt [251];
int lineno;
FILE *fptr;
/* register the connection context ... */
EXEC SQL REGISTER CONNECT USING :epctx;
The function loads a flat file into the database. It is probably not related but are unable to SQLPLUS/ or SQLLDR/ into the database from an OS autheniticated account (get ORA-12547: TNS:lost contact.) Thanks for taking the time to look at this. There aren't many people trying this on VMS, I'd bet.

Pl sql error in procedure

I writting a procedure in which i using a cursor who will select the data through schema name from another schema.
Here is the code :
create or replace
PROCEDURE SP_CMDTRANSACTION AS
CURSOR C1 IS select originating_system, originating_system_type, intl_flag from cmdp.cmd_transaction;
BEGIN
NULL;
END SP_CMDTRANSACTION;
In the above code the cmdp is a name of schema.
When i am compiling this code it is giving "Table or View doesnot exist"
Plz suggest

shakti wrote:
this is the grant staement which i ran
GRANT SELECT ON cmdp.cmd_transaction to cmdp;
CMDP as owner already could do SELECT.
I am using a oracle plsql developer
when i ran that it shown
"GRANT SELECT succeeded."
After that when i am running me procedure same error is showing
Following is the procedureas which USER is running procedure ?
>
create or replace
PROCEDURE SP_CMDTRANSACTION AS
CURSOR C1 IS select originating_system, originating_system_type, intl_flag from cmdp.cmd_transaction;
BEGIN
NULL;
END SP_CMDTRANSACTION;
plz suggest

SQL ERROR

HI EXPERTS!
CAN ANYBODY TELL ME HOW TO RESOLVE THIS RUNTIME ERROR ON EXECUTING TRANSACTION PC00_M40_CALC.
Runtime errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
 Occurred on 07.08.2007 at 14:13:06
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"GET_SLAB_RATE" "(METHOD)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure
"GET_SLAB_RATE"
"(METHOD)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-04031: unable to allocate 4200 bytes of
shared memory ("shared pool","SELECT * FROM "T7INT1" WHERE...","library
cache","kkslpkp - literal info.")"
Internal call code.........: "[RSQL/FTCH/T7INT1 ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"CL_HRPAYIN_SLABRATES==========CP " or "CL_HRPAYIN_SLABRATES==========CM002 "
"GET_SLAB_RATE"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "hmsidev01"
Network address.......... "10.249.16.150"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "HMSIDEV01"
Database type............ "ORACLE"
Database name............ "DEV"
Database owner........... "SAPDEV"
Character set............ "English_United State"
SAP kernel............... "620"
Created on............... "Jun 13 2004 22:06:10"
Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
Database version......... "OCI_817_SHARE "
Patch level.............. "1511"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.."
SAP database version..... "620"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 100
User................ "IR1"
Language key........ "E"
Transaction......... "PC00_M40_CALC "
Program............. "CL_HRPAYIN_SLABRATES==========CP "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "CL_HRPAYIN_SLABRATES==========CP
" in "GET_SLAB_RATE".
The main program was "HINCALC0 ".
The termination occurred in line 12 of the source code of the (Include)
program "CL_HRPAYIN_SLABRATES==========CM002 "
of the source code of program "CL_HRPAYIN_SLABRATES==========CM002 " (when
calling the editor 120).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "GET_SLAB_RATE" "(METHOD)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "CL_HRPAYIN_SLABRATES==========CP ". Its source
code starts in line 1
of the (Include) program "CL_HRPAYIN_SLABRATES==========CM002 ".
Source code extract
000010 METHOD get_slab_rate .
000020
000030 DATA: wa_t7int1 TYPE t7int1,
000040 wa_t7int3 TYPE t7int3,
000050 slab_code TYPE t7int1-slcod.
000060 CLEAR: wa_t7int1 ,
000070 wa_t7int3 ,
000080 slab_code .
000090
000100
000110 * Select slab code from t7int1.
 SELECT * FROM t7int1 INTO wa_t7int1
000130 WHERE sltyp = slab_type
000140 AND begda LT ref_date
000150 AND endda GE ref_date.
000160 MOVE wa_t7int1-slcod TO slab_code.
000170 ENDSELECT.
000180
000190 * Find out the rate for the salb code in which the income falls.
000200 SELECT * FROM t7int3 INTO wa_t7int3 WHERE slcod = slab_code ORDER BY
000210 hirge.
000220 IF wa_t7int3-hirge GE income.
000230 EXIT.
000240 ENDIF.
000250 ENDSELECT.
000260
000270 slab_rate = wa_t7int3-txval.
000280
000290
000300 ENDMETHOD.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 215
SY-TABIX 63 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 1 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM SY-TITLE Payroll Driver, India
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
 Program
 Include Line
 Class
 16 METHOD GET_SLAB_RATE
 CL_HRPAYIN_SLABRATES==========CP
 CL_HRPAYIN_SLABRATES==========CM002 12
 CL_HRPAYIN_SLABRATES
 15 FORM STDDED03
 HINCALC0
 PCTAXIN0 564
 14 FORM CALC_STANDARD_DEDUCTION
 HINCALC0
 PCTAXIN0 466
 13 FORM FUINTAX
 HINCALC0
 PCTAXIN0 253
 12 FORM AS-FUNKTION
 HINCALC0
 PCASFIN0 13
 11 FORM ASLOOP
 HINCALC0
 RPCHRT09_ASLOOP 58
 10 FORM MONATSABRECHNUNG
 HINCALC0
 RPCHRT09_MONATSABRECHNUNG 48
 9 FORM RUECKRECHNUNG
 HINCALC0
 RPCHRT09_RUECKRECHNUNG 136
 8 FORM MAIN
 HINCALC0
 RPCHRT09_MAIN 134
 7 FORM %_GET_PERNR
 HINCALC0
 RPCHRT09 762
 6 FORM FILL_INFOTYPE_TABLES_AND_PUT
 SAPDBPNP
 DBPNPF03 542
 5 FORM PUTPERN
 SAPDBPNP
 DBPNPF03 470
 4 FORM LOOP_AT_INDEX_AND_PUT
 SAPDBPNP
 DBPNPF01 996
 3 FORM PUT_PERNR
 SAPDBPNP
 DBPNPF01 194
 2 FORM %_ROOT
 SAPDBPNP
 SAPDBPNP 151
 1 EVENT SYSTEM-EXIT
 HINCALC0
 20
Chosen variables
 16 METHOD GET_SLAB_RATE
 CL_HRPAYIN_SLABRATES==========CP
 CL_HRPAYIN_SLABRATES==========CM002 12
SLAB_TYPE D
 4
 4
REF_DATE 20070331
 33333333
 20070331
INCOME ####Q#
 00005991
 0001153C
SLAB_RATE ########
 00000000
 0000000C
WA_T7INT1 0000000000000000
 222233333333333333332
 000000000000000000000
WA_T7INT3 ####### #######
 222222000000022222220000000
 000000000000C0000000000000C
SLAB_CODE
 2222
 0000
%_VIASELSCR #
 0
 4
<%_TABLE_T7INT1> ???
%_SPACE
 2
 0
SYST-REPID CL_HRPAYIN_SLABRATES==========CP
 4454554544554445454533333333334522222222
 3CF820199EF3C1221453DDDDDDDDDD3000000000
SY-XPROG SAPDBPNP
 5454454522222222222222222222222222222222
 310420E000000000000000000000000000000000
SY-REPID CL_HRPAYIN_SLABRATES==========CP
 4454554544554445454533333333334522222222
 3CF820199EF3C1221453DDDDDDDDDD3000000000
SY-XFORM %_ROOT
 255445222222222222222222222222
 5F2FF4000000000000000000000000
%_DUMMY$$
 2222
 0000
<%_TABLE_T7INT3> ???
 15 FORM STDDED03
 HINCALC0
 PCTAXIN0 564
STD_DED_TAB Table[initial]
 0000FFFD
 0000FFFF
SY-TABIX 63
 3000
 F000
STD_PERCENT #####
 00000
 0000C
%_SPACE
 2
 0
SYST-REPID HINCALC0
 4444444322222222222222222222222222222222
 89E31C3000000000000000000000000000000000
SPACE
 2
 0
%_DUMMY$$
 2222
 0000
$ENDDATE 20070331
 33333333
 20070331
$PRE_DEDN_AMOUNT ####Q#
 00005991
 0001153C
$CALC_DEDN ########
 00000000
 0000000C
SY-REPID HINCALC0
 4444444322222222222222222222222222222222
 89E31C3000000000000000000000000000000000
SY ×#######?###?###########################
 D000000030003000000000000000000000000000
 70001000F000F000000000000000000000000000
... + 40 ###################################5###
 0000000000000000000080000000000000003000
 1000100010000000100040000000000000005000
... + 80 ########################################
 0000000000000000000000000000000000000000
 0000000000000000400000000000000000000000
... + 120 ################################%######
 0000000000000000000000000000000020008000
 000000000000000000000000000000005000E000
... + 160 ############XM## P############# E0 1
 0000000000005400250000000000000222432223
 0000700040008D00000020000C0000C000500001
... + 200 000 ####PNP 100
 3332222222220000545222222222222222223332
 00000000000000000E0000000000000000001000
... + 240 00
 222223322222222
 000000000000000
NO_OF_ROWS
 2
 0
SY-TFILL 63
 3000
 F000
 14 FORM CALC_STANDARD_DEDUCTION
 HINCALC0
 PCTAXIN0 466
P0015[] Table IT_204[12x147]
 F7D4DED48000C000000090000000FFFF00004500
 871900998000C000C00030000000FFFF40000F00
... + 40
 0000C020
 20001E80
SW_AUFROLLUNG X
 5
 8
%BX03242_BLOCK_1000 Log
 4662222222222222222222222222222222222222
 CF70000000000000000000000000000000000000
... + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80
 222
 000
SNAME 40INDED
 33444442
 409E4540
T559A-WTIME 000000
 333333
 000000
OGRT[] Table IT_299[0x53]
 00000000C0002000000030000000FFFF0000E300
 000000003000B100000050000000FFFF40000310
... + 40
 1000C200
 00001E00
ENDDATE 20070331
 33333333
 20070331
T596F-PGMNA HINCALC0
 4444444322222222222222222222222222222222
 89E31C3000000000000000000000000000000000
T596F-MODNA STDDED03
 55444433
 34445403
P_PRE_DEDUCTION_BALANCE ####Q#
 00005991
 0001153C
STANDARD_DEDUCTION ########
 00000000
 0000000C
P2006[] Table IT_460[37x168]
 9ED40000E000C0002000A0000000FFFF00008500
 877900006000C100500080000000FFFF40000600
... + 40
 0000C020
 20001E00
 13 FORM FUINTAX
 HINCALC0
 PCTAXIN0 253
ANNUAL_IRREGULAR_INCOME ####3#%L
 00003124
 0000365C
%_SET_VOID_%_APP_%
 222222222222222222222222222222
 000000000000000000000000000000
ANNUAL_PERK ########
 00000000
 0000000C
SET_ODC
 2
 0
%_SET_ODC_%_APP_%
 222222222222222222222222222222
 000000000000000000000000000000
SET_REVR
 2
 0
P%2007 00000000 000000000000000000000
 3333333322222222222333333333333333333333
 0000000000000000000000000000000000000000
... + 40 000000 00
 3333332222222222222222222222222222222233
 0000000000000000000000000000000000000000
... + 80 0000000000 00###### ###### 00000000000
 3333333333233000000200000022233333333333
 000000000000000000C000000C00000000000000
... + 120 0000000000000000000000000
 3333333333333333333333333222222222222222
 0000000000000000000000000000000000000000
... + 160
 222222222222
 000000000000
PRE_DEDUCTION_BALANCE ####Q#
 00005991
 0001153C
OCRSN
 2222
 0000
APER-PAPER-PABRJ 2006
 3333
 2006
APER-IAPER-PABRJ 2007
 3333
 2007
SW_INTIM
 2
 0
APER-PAPER 200612
 333333
 200612
ANN_PTAX_AMT ########
 00000000
 0000000C
 12 FORM AS-FUNKTION
 HINCALC0
 PCASFIN0 13
P0584 00000000 000000000000000000000
 3333333322222222222333333333333333333333
 0000000000000000000000000000000000000000
... + 40 000000 #
 3333332222222222222222222222222222222220
 0000000000000000000000000000000000000000
... + 80 ########################################
 0000000000000000000000000000000000000000
 00000C0000C0000C0000C0000C000000C000000C
... + 120 ####################################
 0000000000000000000000000000000000002222
 000000C000000C0000C0000C000000C0000C0000
... + 160 0000
 22222222222333322222
 00000000000000000000
ORGDIR 00000 0000000000000000 00 0
 3333322222222333333333333333322332222223
 0000000000000000000000000000000000000000
... + 40 0000000 0000000000000000000000000
 3333333222222223333333333333333333333333
 0000000000000000000000000000000000000000
... + 80 0000000000000 00000000
 3333333333333223333333322222222222222222
 0000000000000000000000000000000000000000
... + 120 00000000000000 000000000000000000000
 3333333333333323333333333333333333332222
 0000000000000000000000000000000000000000
RP-IMP-CD-SUBRC 0
 0000
 0000
CD-SUBRC 0
 0000
 0000
CD-INDEX 0
 0000
 0000
IT[] Table IT_490[63x53]
 EFC47AC4F000E000300030000000FFFF00005100
 0AB903399000A100F00050000000FFFF40000810
... + 40
 2000C000
 B0009E00
IT */418######### # ####################Q
 2233300000000020222000000000000000000005
 AF418000000000000000000000C0000000C00011
... + 40 #
 9912222222222
 53C0000000000
RGDIR_CA[] Table IT_383[0x156]
 00003ED4E0007000000090000000FFFF0000C100
 000086791000F1000000C0000000FFFF40000810
... + 40
 4000C000
 00001400
RGDIR_CA 00000 0000000000000000 00 0
 3333322222222333333333333333322332222223
 0000000000000000000000000000000000000000
... + 40 0000000 0000000000000000000000000
 3333333222222223333333333333333333333333
 0000000000000000000000000000000000000000
... + 80 0000000000000 00000000
 3333333333333223333333322222222222222222
 0000000000000000000000000000000000000000
... + 120 00000000000000 000000000000000000000
 333333333333332333333333333333333333
 000000000000000000000000000000000000
%%_DIR2[] Table IT_218[0x54]
 000000009000D000000030000000FFFF0000D100
 000000006000A000000060000000FFFF40008210
... + 40
 6000C000
 40001400
<%_TABLE_T599B> ???
PY_PM_CONTAINER 00000000
 2222222222222222222222222222222233333333
 0000000000000000000000000000000000000000
... + 40 0
 3222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 120
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 160
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 200
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 240
 222222222222222
 000000000000000
PNPSTATU-LOW
 222
 000
SET_LCW 010
 333
 010
 11 FORM ASLOOP
 HINCALC0
 RPCHRT09_ASLOOP 58
P_WITH_LOG X
 5
 8
SW_EXPORT_ES
 2
 0
ASNUM 215
 D000
 7000
APER_NUMB 15
 0000
 F000
NEXT_AS_ENTRY 244
 F000
 4000
SW_REPETITION X
 5
 8
SW_P0005_CHANGED
 2
 0
PNPSACHZ
 222222222
 000000000
PTEXT[] Table IT_139[0x548]
 0000CCC460008000000020000000FFFF00004300
 00000D79C000B000000042000000FFFF40000500
... + 40
 1000C200
 00001400
SW_VOID
 2
 0
SCREEN %_17SNS0000177553_%_%_%_%_%_%_
 2533545333333333352525252525252222222222
 5F173E30000177553F5F5F5F5F5F5F0000000000
... + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 120 SRI00001#00000 ####
 2222222222222222222225543333303333320000
 0000000000000000000003290000100000000000
SW_PROT
 2
 0
PNPSBMOD-LOW
 2222
 0000
PTEXT_LINES 0
 0000
 0000
 10 FORM MONATSABRECHNUNG
 HINCALC0
 RPCHRT09_MONATSABRECHNUNG 48
CALC_CURRENCY INR
 44522
 9E200
SY-SUBRC 0
 0000
 0000
CALC_CURR_DEC 1380862210
 0
 2
TCURX-CURRDEC 0
 0
 0
PNPPERSK-LOW
 22
 00
PNPKOSTL
 22222222222222222222222
 00000000000000000000000
SL_BRUTTO
 2
 0
FC-SL_B_N
 2
 0
%_PNPSNAME_%_APP_% PNPSNAMEEE name can be sorted to
 5455444444266662666266276776622222222276
 0E03E1D5550E1D5031E02503F24540000000004F
... + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80 @1FQMultiple selection@
 2224345547676766276666766642222222222222
 000016C1D5C490C5035C5349FE00000000000000
... + 120
 222
 000
APER-CALCD X
 5
 8
DT /AEA00200612 00000000########
 24443333333322333333330000000022222
 F1510020061200000000000000000C00000
DT[] Table IT_1916[4x35]
 F8F40000E0007000000020000000FFFF0000E400
 06090000A100C700400030000000FFFF40008610
... + 40
 1000C220
 00001E00
 9 FORM RUECKRECHNUNG
 HINCALC0
 RPCHRT09_RUECKRECHNUNG 136
APER-PAYTY
 2
 0
SY-XPROG SAPDBPNP
 5454454522222222222222222222222222222222
 310420E000000000000000000000000000000000
PYCT 0<>
 0000FFFF
 0000FFFF
PNP-SW-AUTH-SKIPPED-RECORD 0
 3
 0
P0007[] Table IT_201[4x138]
 CBC47DD48000C000000080000000FFFF00005400
 80390F99500090004000A0000000FFFF40008B00
... + 40
 0000C020
 20001E80
PNPKOKRS[] Table IT_52[0x11]
 0000000020003000000000000000FFFF04007200
 00000000A00040000000B0000000FFFF44008700
... + 40
 0000C000
 A0001400
PNPBLCKT
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80
 222
 000
FC-NT_BEGIN 0
 0000
 0000
PNP-SW-IGNORELOCKEDRECORDS Y
 5
 9
FROM_DATE 00000000
 33333333
 00000000
%_SET_LCW_%_APP_%
 222222222222222222222222222222
 000000000000000000000000000000
 8 FORM MAIN
 HINCALC0
 RPCHRT09_MAIN 134
%_PNPFKBER_%_APP_% PNPFKBERFunctional Area to
 5454444547667666662476622222222222222276
 0E06B25265E349FE1C012510000000000000004F
... + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80 @1FQMultiple selection@
 2224345547676766276666766642222222222222
 000016C1D5C490C5035C5349FE00000000000000
... + 120
 222
 000
PERNR-PERNR 00003015
 33333333
 00003015
 Table IT_235[0x178]
 000045D4A000E0000000B0000000FFFF00003400
 000080390000B000000020000000FFFF40008110
... + 40
 1000C200
 00001400
P0027[] Table IT_234[0x1851]
 0000A4D49000E000000030000000FFFF0000DE00
 00008F39F000A0000000B7000000FFFF40000610
... + 40
 0000C200
 80001E00
PNPENAME
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80
 222
 000
INFTY[] Table IT_116[34x4]
 8EC4000050007000200000000000FFFF0D008000
 0E790000A0004000200040000000FFFF43000900
... + 40
 2000C000
 20001400
INFTY 0078
 3333
 0078
PNPBLCKP Payroll period
 5677666276766622222222222222222222222222
 0192FCC00529F400000000000000000000000000
... + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80
 222
 000
SY-MSGNO 000
 333
 000
FC-PGM_TYP ABR
 4452
 1220
PY12W_MEM_ID_BUFFER T512W_BUFFER
 533355454445
 45127F256652
RSJOBINFO 00000000
 2222222222222222222222222222222233333333
 0000000000000000000000000000000000000000
... + 40 000000
 3333332222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80 ####
 0000
 0000
P0032 00000000 000000000000000000000
 3333333322222222222333333333333333333333
 0000000000000000000000000000000000000000
... + 40 000000
 3333332222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80 #####
 2222222222222222222222200000222222222222
 000000000000000000000000000C000000000000
... + 120
 2222222222222222222222222222222222222222


Hello,
strange, you have the same message in SQL Server forum, but we can see Oracle DB here:
SQL ERROR
Without developer traces it would be difficult to say. But it looks bad enough because of kernel 6.20 patch level 1511 (definitely dboraslib.dll has similar patch level) and Oracle 8.1.7 are out of support since years.
best regards

While running the livecache server test a native sql error occures

We are using scm4.1 livecache 7.5.0 And every time we are running the livecache test program he is dumping
whith the following dump
patch level scm & scm_basis is 8
Runtime Errors DBIF_DSQL2_SQL_ERROR
Except. CX_SY_NATIVE_SQL_ERROR
Date and Time 31.10.2005 16:50:55
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error 600 occurred in the current database connection "LCA".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "Work rolled back: DbpError -28814 in
APS_ORDER_CH"
Database error code .......: 600
Triggering SQL statement...: " ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? or'"
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"/SAPAPO/SAPLOM_PLANNING" or "/SAPAPO/LOM_PLANNINGU08"
"/SAPAPO/OM_ORDER_CHANGE"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"/SAPAPO/OM_ORDER_CHANGE"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "bebruap2"
Network address.......... "195.213.49.227"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "BEBRUAP2"
Database type............ "MSSQL"
Database name............ "APD"
Database owner........... "apd"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 23 2005 00:00:49"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "87"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8176
EM....................... 24040336
Heap..................... 0
Page..................... 1687552
MM Used.................. 1516920
MM Free.................. 572032
SAP Release.............. "640"
User and Transaction
Client.............. 000
User................ "CGRAULS"
Language key........ "E"
Transaction......... "/SAPAPO/OM03 "
Program............. "/SAPAPO/SAPLOM_PLANNING"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "/SAPAPO/SAPLOM_PLANNING" in
"/SAPAPO/OM_ORDER_CHANGE".
The main program was "/SAPAPO/OM_TB_FLOW_QUANTITY ".
The termination occurred in line 91 of the source code of the (Include)
program "/SAPAPO/LOM_PLANNINGU08"
of the source code of program "/SAPAPO/LOM_PLANNINGU08" (when calling the
editor 910).
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "/SAPAPO/OM_ORDER_CHANGE" "(FUNCTION)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "/SAPAPO/SAPLOM_PLANNING ". Its source code
starts in line 5
of the (Include) program "/SAPAPO/LOM_PLANNING$08 ".
Source Code Extract
Line
SourceCde
61
is_gen_params-simversion
62
is_gen_params-dont_set_netchg_flag
63
space.
64
65
Kontrollstruktur IS_GET_CHANGED_OPTIONS anpassen.
66
IF NOT et_changed_orders IS REQUESTED.
67
is_get_changed_options-send_chg_top_order = gc_false.
68
ENDIF.
69
IF NOT et_changed_cap_reqs IS REQUESTED.
70
is_get_changed_options-send_chg_cap_req = gc_false.
71
ENDIF.
72
IF NOT et_changed_io_nodes IS REQUESTED.
73
is_get_changed_options-send_chg_ionode = gc_false.
74
ENDIF.
75
IF NOT et_changed_io_pp_nodes IS REQUESTED.
76
is_get_changed_options-send_chg_io_pp = gc_false.
77
ENDIF.
78
IF NOT et_changed_pegids IS REQUESTED.
79
is_get_changed_options-send_chg_pegid = gc_false.
80
ENDIF.
81
IF NOT et_deleted_fix_pegging IS REQUESTED.
82
is_get_changed_options-send_del_fix_peg = gc_false.
83
ENDIF.
84
start_function 'OM_ORDER_CHANGE'. "#EC *
85
Verbindung zum liveCache aufbauen
86
check_server.
87
connect_to_livecache.
88
COM-Routine zum Anlegen bzw. Überschreiben eines Zeitstrahls
89
90
EXEC sql.
>>>>>
execute procedure "APS_ORDER_CHANGE" (
92
in :ls_gen_com_params,
93
out :lv_rc,
94
in :et_rc,
95
in :it_order_method,
96
in :it_ordkeys,
97
in :it_ordmaps,
98
in :it_orders,
99
in :it_activities,
100
in :it_mode,
101
in :it_cap_reqs,
102
in :it_positions,
103
in :it_inputs,
104
in :it_outputs,
105
in :it_prodflow,
106
in :it_intern_constraints,
107
in :it_extern_constraints,
108
in :it_charact_val_acts,
109
in :it_charact_req_inpnode,
110
in :it_charact_val_outnode,
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Flow Quantity Test
SY-MSGTY
S
SY-MSGID
/SAPAPO/OM_TEST
SY-MSGNO
001
SY-MSGV1
Create transSim
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
3 FUNCTION /SAPAPO/SAPLOM_PLANNING /SAPAPO/LOM_PLANNINGU08 91
/SAPAPO/OM_ORDER_CHANGE
2 FORM /SAPAPO/OM_TB_FLOW_QUANTITY /SAPAPO/OM_TB_FLOW_QUANTITY 802
CHANGE_DATA
1 EVENT /SAPAPO/OM_TB_FLOW_QUANTITY /SAPAPO/OM_TB_FLOW_QUANTITY 11
START-OF-SELECTION
Chosen variables
Name
Val.
No. 3 Ty. FUNCTION
Name /SAPAPO/OM_ORDER_CHANGE
IS_ATP_INFO
01ATP0000001~CGRAULSXX##
334553333333744545455500
011400000001E37215C38800
000000000000000000000000
000000000000000000000000
IS_CONTROLPARAMETERS
霁က#ం̂⍱㔒鲔#####
2222222222222222222222001007190000022
0000000000000000000000100221240000100
0000000000000000000000910002390000000
0000000000000000000000700C335C000C000
IS_GEN_PARAMS
01PLV0000001~CGRAULS
3354533333337445454522222
010C60000001E37215C300000
0000000000000000000000000
0000000000000000000000000
IS_GET_CHANGED_OPTIONS
2222222
0000000
0000000
0000000
IT_ACTIVITIES
Table IT_274[1x256]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ACTIVITIES
Table reference: 41
TABH+ 0(20) = 5087FFDF00000000000000002900000012010000
TABH+ 20(20) = 0100000000010000FFFFFFFF0487000000290000
TABH+ 40( 8) = 10000000C1308000
store = 0x5087FFDF
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 41 (0x29000000)
label = 274 (0x12010000)
fill = 1 (0x01000000)
leng = 256 (0x00010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000205
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x180112E0
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 126 (0x7E000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_CAP_REQS
Table IT_276[1x112]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_CAP_REQS
Table reference: 39
TABH+ 0(20) = 48BB06E000000000000000002700000014010000
TABH+ 20(20) = 0100000070000000FFFFFFFF04870000C0290000
TABH+ 40( 8) = 10000000C1308000
store = 0x48BB06E0
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 39 (0x27000000)
label = 276 (0x14010000)
fill = 1 (0x01000000)
leng = 112 (0x70000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000209
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x188D04E0
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 124 (0x7C000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_CHARACT_REQ_INPNODE
Table IT_418[0x140]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_REQ_INPNODE
Table reference: 32
TABH+ 0(20) = 00000000000000000000000020000000A2010000
TABH+ 20(20) = 000000008C000000FFFFFFFF04870000301D0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 32 (0x20000000)
label = 418 (0xA2010000)
fill = 0 (0x00000000)
leng = 140 (0x8C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000142
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_CHARACT_VAL_ACTS
Table IT_417[0x156]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_VAL_ACTS
Table reference: 50
TABH+ 0(20) = 00000000000000000000000032000000A1010000
TABH+ 20(20) = 000000009C000000FFFFFFFF04870000901D0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 50 (0x32000000)
label = 417 (0xA1010000)
fill = 0 (0x00000000)
leng = 156 (0x9C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000144
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_CHARACT_VAL_OUTNODE
Table IT_419[0x156]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_VAL_OUTNODE
Table reference: 60
TABH+ 0(20) = 0000000000000000000000003C000000A3010000
TABH+ 20(20) = 000000009C000000FFFFFFFF04870000901D0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 60 (0x3C000000)
label = 419 (0xA3010000)
fill = 0 (0x00000000)
leng = 156 (0x9C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000144
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_EXTERN_CONSTRAINTS
Table IT_416[0x124]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_EXTERN_CONSTRAINTS
Table reference: 71
TABH+ 0(20) = 00000000000000000000000047000000A0010000
TABH+ 20(20) = 000000007C000000FFFFFFFF04870000E02A0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 71 (0x47000000)
label = 416 (0xA0010000)
fill = 0 (0x00000000)
leng = 124 (0x7C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000215
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_INPUTS
Table IT_278[1x420]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_INPUTS
Table reference: 63
TABH+ 0(20) = 087400E0C0E303E0000000003F00000016010000
TABH+ 20(20) = 01000000A4010000FFFFFFFF04870000202A0000
TABH+ 40( 8) = 10000000C1308000
store = 0x087400E0
ext1 = 0xC0E303E0
shmId = 0 (0x00000000)
id = 63 (0x3F000000)
label = 278 (0x16010000)
fill = 1 (0x01000000)
leng = 420 (0xA4010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000211
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x78DC11E0
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 123 (0x7B000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x2029FFDF
hsdir = 0x00000000
ext2 = 0x00000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_INTERN_CONSTRAINTS
Table IT_415[0x124]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_INTERN_CONSTRAINTS
Table reference: 49
TABH+ 0(20) = 000000000000000000000000310000009F010000
TABH+ 20(20) = 000000007C000000FFFFFFFF04870000E02A0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 49 (0x31000000)
label = 415 (0x9F010000)
fill = 0 (0x00000000)
leng = 124 (0x7C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000215
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_MODE
Table IT_275[1x164]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_MODES
Table reference: 52
TABH+ 0(20) = A03C00E000000000000000003400000013010000
TABH+ 20(20) = 01000000A4000000FFFFFFFF0487000060290000
TABH+ 40( 8) = 10000000C1308000
store = 0xA03C00E0
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 52 (0x34000000)
label = 275 (0x13010000)
fill = 1 (0x01000000)
leng = 164 (0xA4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000207
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC8F611E0
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 125 (0x7D000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_ORDERS
Table IT_293[1x320]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDERS1
Table reference: 47
TABH+ 0(20) = 20B403E000000000000000002F00000025010000
TABH+ 20(20) = 0100000040010000FFFFFFFF0400000030380000
TABH+ 40( 8) = 01000000C1308000
store = 0x20B403E0
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 47 (0x2F000000)
label = 293 (0x25010000)
fill = 1 (0x01000000)
leng = 320 (0x40010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000286
occu = 1 (0x01000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x9080FFDF
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 1 (0x01000000)
lineAlloc = 1 (0x01000000)
store_id = 130 (0x82000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_ORDER_METHOD
Table IT_268[2x62]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDER_METHOD
Table reference: 51
TABH+ 0(20) = 8882FFDF0000000000000000330000000C010000
TABH+ 20(20) = 020000003E000000FFFFFFFF04000000B0360000
TABH+ 40( 8) = 10000000C1248000
store = 0x8882FFDF
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 51 (0x33000000)
label = 268 (0x0C010000)
fill = 2 (0x02000000)
leng = 62 (0x3E000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000278
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0868FFDF
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 122 (0x7A000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_ORDKEYS
Table IT_271[1x332]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDKEYS
Table reference: 29
TABH+ 0(20) = 80E303E000000000000000001D0000000F010000
TABH+ 20(20) = 010000004C010000FFFFFFFF04870000E0270000
TABH+ 40( 8) = 10000000C1308000
store = 0x80E303E0
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 29 (0x1D000000)
label = 271 (0x0F010000)
fill = 1 (0x01000000)
leng = 332 (0x4C010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000199
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0

Hi,
the error DbpError -28814 denotes that an object cannot be found.
Can you maybe tell me your exact liveCache version (incl. Build level) and LCA Build?
Additionally, please copy the relevant error information from the file (/sapdb/data/wrk/<SID>/)knldiag.err into this thread.
Which exact 'liveCache test program' are your referring to (which of the /SAPAPO/... transactions)?
Kind regards,
Roland

PL/SQL Errors in OTN XMLNews Application

I try to install the OTN XMLNews Application.
My database is 9.2.0.4 on Linux
When I run the xmlnews.sql script I get the following errors:
SQL> SHOW errors;
Errors for PROCEDURE UPDATEXMLNEWSDESC:
LINE/COL ERROR
8/5 PL/SQL: SQL Statement ignored
8/12 PL/SQL: ORA-00942: table or view does not exist
When I query user_errors and recompile I get:
SQL> select object_name, object_type from user_objects
2 where status='INVALID';
OBJECT_NAME
--------------------------------------------------------------------------------OBJECT_TYPE
UPDATEXMLNEWS
PROCEDURE
UPDATEXMLNEWSDESC
PROCEDURE
SQL> alter procedure updatexmlnews compile;
Warning: Procedure altered with compilation errors.
SQL> alter procedure updatexmlnewsdesc compile;
Warning: Procedure altered with compilation errors.
What is wrong?
--Flemming

I created the tables by hand, edited the script so it did not drop the user and create the tables. The script the ran with out any errors.
--Flemming

SQL error in the database when accessing a table.

Hi,
I got below error at production server. Please suggest how to reslove this error.
 
 
 
Runtime Errors DBIF_RSQL_SQL_ERROR
 
Exception CX_SY_OPEN_SQL_DB
 
Date and Time 02.01.2011 15:55:06
 
 
 
 
 
Short text
 
SQL error in the database when accessing a table.
 
 
 
How to correct the error
 
Database error text........: "[10054] TCP Provider: An existing connection was
 
forcibly closed by the remote host.
 
[10054] Communication link failure"
 
Internal call code.........: "[RSQL/INSR/SWFCNTBUF ]"
 
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_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
 
"CL_SWF_CNT_FACTORY_SHMEM======CP" or "CL_SWF_CNT_FACTORY_SHMEM======CM001"
 
| "ADD_INSTANCE"
 
 
 
Information on where terminated
 
Termination occurred in the ABAP program "CL_SWF_CNT_FACTORY_SHMEM======CP" -
 
in "ADD_INSTANCE".
 
The main program was "SAPMSSY1 ".
 
 
In the source code you have the termination point in line 16
 
of the (Include) program "CL_SWF_CNT_FACTORY_SHMEM======CM001".
 
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
 
procedure "ADD_INSTANCE" "(METHOD)", but it was neither handled locally nor
 
declared
 
in the RAISING clause of its signature.
 
 
The procedure is in program "CL_SWF_CNT_FACTORY_SHMEM======CP "; its source
 
code begins in line
 
1 of the (Include program "CL_SWF_CNT_FACTORY_SHMEM======CM001 ".
 
 
 
 
Source Code Extract
 
 
Line
SourceCde
 
 
1
METHOD add_instance .
 
2
 
3
data: ls_id type swfcntbuf.
 
4
 
5
check buffer method - store in local buffer if necessary
 
6
retcode = cl_swf_cnt_factory=>add_instance( ibf_por = ibf_por instance = instance ).
 
7
 
8
CHECK m_buffer_method EQ mc_buffer_shared.
 
9
 
10
append key to list of tasks to add stored in database table SWFCNTBUF
 
11
will be evaluated by build process for shared memory area (UPDATE_BUFFER method)
 
12
 
13
ls_id-mandt = sy-mandt.
 
14
ls_id-id = ibf_por.
 
15
 
>>>>>
INSERT swfcntbuf CONNECTION r/3*wfcontainer
 
17
FROM ls_id.
 
18
 
19
IF sy-subrc EQ 0.
 
20
Commit seems to be necessary always, even if INSERT has failed, to get rid of
 
21
database locks
 
22
COMMIT CONNECTION r/3*wfcontainer.
 
23
ENDIF.
 
24
 
25
ENDMETHOD.
 

duplicate here SQL error in the database when accessing a table.
Do not post the same question in more than on forum.

DBIF_RSQL_SQL_ERROR with SQL error in the database when accessing a table.

dear all,
i have done a system copy from production server into quality server. quality was scrapped and freshly installed with SAP then used the DB flush method to carry out the system copy. i had to change the DBS_ORA_SCHEMA in environment variables to SAP<SOURCE SID> from SAPSR3. the sap version is ECC6.0,DB is ORACLE10.2 on WIN NT.
after MMC opened, i get "SQL error in the database when accessing a table" error is coming. in SM21, I am getting "Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000 )
Database error 8103 at SEL access to table TBTCO
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
Database error 8103 at FET access to table TBTCP
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130339 sibqty_Q TY_00 " generated
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
> Short dump "081018 130339 sibqty_Q TY_00 " generated
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
Delete session 001 after error 023
Database error 8103 at DEL access to table TMSALOGAR
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130432 sibqty_Q TY_00 " generated
Database error 8103 at FET access to table SNAP
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130432 sibqty_Q TY_00 " generated
Transaction Canceled SY 002 ( SQL error in the database when accessing a table. )
Database error 8103 at FET access to table TSP02"
please find the st22 DUMP:
ow to correct the error |
Database error text........: "ORA-08103: object no longer exists"
Internal call code.........: "[RSQL/READ/TBTCO ]"
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_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPMSSY2" or "SAPMSSY2"
"INITIATE_JOB_START"
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
"INITIATE_JOB_START" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
|
please do me this favor if you know to avoid this problem..
thanks a lot..

Hello Anuj,
This is because the COUNT(*) is returning a value which is longer than the INT4 data type it is expecting. If you restrict the selection by introducing a WHERE clause, then you won't get the dump:
DATA: dyn_from TYPE string,
 dyn_where TYPE string,
 gx_sql_err TYPE REF TO cx_sy_open_sql_error,
 gv_text TYPE string.
dyn_from = `DD01L INNER JOIN DD02L ON DD02L~AS4LOCAL = DD01L~AS4LOCAL AND DD02L~AS4VERS = DD01L~AS4VERS`.
dyn_where = `DOMNAME LIKE 'Z%'`.
TRY .
 SELECT COUNT(*) FROM (dyn_from) WHERE (dyn_where).
 WRITE: / sy-dbcnt NO-GROUPING.
CATCH: cx_sy_open_sql_db INTO gx_sql_err,
 cx_sy_dynamic_osql_semantics INTO gx_sql_err,
 cx_sy_dynamic_osql_syntax INTO gx_sql_err.
ENDTRY.
IF gx_sql_err IS BOUND.
gv_text = gx_sql_err->get_text( ).
WRITE: / gv_text.
ENDIF.
BR,
Suhas

Receiving SQL Error: INTERNAL_ERROR while executing the query

Dear All,
I am receiving the below error while executing a query.
SQL Error: INTERNAL_ERROR
Diagnosis
The database system registered an SQL error. As available, the error number and a description are included in the short text. Possible causes for SQL errors include:
Overflow of database objects such as buffers, temporary tablespaces, rollback segments or data containers/tablespaces.
->These problems can generally be eliminated by system administrators.
Missing generated database objects such as tables or views based on inconsistent or inactive InfoCubes or InfoObjects. Examples of this include the view of the fact table for an InfoCube or the attribute SID table (X/Y table) of a characteristic.
-> These problems can generally be eliminated by a BW administrator.
SQL requests with incorrect content.
-> Problems of this type are generally programming errors.
System Response
Procedure
Contact your system administrator.
Procedure for System Administration
If there is no error description, look for one in the reference from the database producer.
Decide on the correct category for the SQL error and check if it can be eliminated. Generally the error can also be found in the syslog (transaction sm21). From there, transactions sm51 and sm50, the developer's trace log of the work process can be determined and the erroneous statement can be viewed in the log. This procedure is described in SAP Note 568768.
Notification Number DBMAN 257
I verified the table spaces and also done RSRV Repair of InfoObjects and InfoCubes and didnt find any error. But I am receiving this error for one particular month and remaining months are executing fine. Any ideas why i am receiving this error.
Regards
Ravi Y

OSS Note 1305568:
Symptom
A data mart query that
you want to execute within a data transfer process (DTP), for example, terminates with the
SQL error -1013 "Too many order columns".
The following is displayed in the monitor log of the data transfer process:
Error while extracting from source xxxxxx (type InfoProvider)
Message number RSBK 242
Exception CX_SQL_EXCEPTION occurred (program:
CL_SQL_STATEMENT==============CP, include:
CL_SQL_STATEMENT==============CM004, line: 32).
Message number RS_EXCEPTION 000
SQL error: POS(3306) Too many order columns
Message number DBMAN 257
Error reading the data of InfoProvider xxxxxx
Message number DBMAN 305
You have already implemented Note 1065380.
Other terms
CX_SQL_EXCEPTION, message number, RS_EXCEPTION 000, DBMAN 257, RSBK 242,
RS_EXCEPTION 000
Reason and Prerequisites
The MaxDB internal limit of 4016 bytes or 128 fields for GROUP BY columns was exceeded.
Solution
When you implement these corrections, no aggregation is performed for the data (GROUP BY) if the limits of the MaxDB database have been exceeded.
The limit values for the aggregation bahavior can also be manually reduced if there are problems with the default values.
Two RSADMIN parameters are provided for this.
MAXDB_MAX_GROUP_BY_FLDS is the maximum number of GROUP BY fields. The default value is 128.
MAXDB_MAX_GROUP_BY_LEN is the maximum total length of the GROUP BY fields. The default value is 4000.
SAP NetWeaver BI 7.00
Import Support Package 21 for SAP NetWeaver BI 7. 00 (SAPKW70021) into your BI system. The Support Package is available when Note 1270629"SAPBINews NW 7.00 BI Support Package 21", which describes this Support Package in more detail, is released for customers.

SQL Error: ORA-01704: string literal too long

select * from table(fn_split('some 10000 characters with comma separation .........................'))
Error report:
SQL Error: ORA-01704: string literal too long
01704. 00000 - "string literal too long"
*Cause: The string literal is longer than 4000 characters.
*Action: Use a string literal of at most 4000 characters.
how to pass my 10k record string

933663 wrote:
The string is through a user interface.So, that interface is using what datatype for the string? What language is the interface written in?
insert into table
select * from table(fn_split('2,4,2,5,7'));Do you understand what a string literal is? You cannot provide a varchar2 string that exceeds 4000 bytes from within SQL. Fact. It just cannot be done.
If you are passing the string from a user interface using a datatype that supports more than 4000 bytes, and you pass it directly to PL/SQL code by calling the function or procedure directly (not using SQL) then you can use up to 32767 bytes for your VARCHAR2.
The code you've posted (which happens to be some of my own code posted years ago on these forums) takes a VARCHAR2 as an input. You would have to change that to accept a CLOB datatype and work on the CLOB instead. However, you still wouldn't be able to pass in a string literal of more than 4000 bytes from SQL for it.
Looking at your other thread: Seperate the string value
... it looks like the 'user' is trying to pass in a table definition. What is it your application is trying to do? Surely you are not trying to create a table at run time?
So explain, what is the business issue you are trying to solve? We may be able to provide a better way of doing it.

Error ODS activation - sql error when accessing a table.

Hi,
sometimes occurs an error by activation ODS. I have proces chain and when is loaded second packet an error occurs. In monitor>>
-RSMPC 128, datapacket 3 is wrong, with status number 9
-RSMPC 131
-RSDRO 108 - communcation error (sql error when accessing a table)
In sm21>
-sql error when accessing a table
-The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
either caught nor passed along using a RAISING clause, in the procedure "UPDATE_ATAB" "(FORM)"
Since the caller of the procedure could not have expected this exception
 to occur, the running program was terminated.
The reason for the exception is:
The database system recognized that your last operation on the database
would have led to a deadlock.
Therefore, your transaction was rolled back
to avoid this.
ORACLE always terminates any transaction that would result in deadlock.
The other transactions involved in this potential deadlock
are not affected by the termination.
I have BW 3.5.
Thank You very much.

There are a few different scenarios that I can think of where this might come up that all involve what might resulting in parallel (concurrent)processes:
Loading packets in parallel - that is there are X number of processes loading packets concurrently. This could be set in your IMG settings system wide or in the InfoPackage for just this datasource. You seem to indicate that you don't have this.
Database parallel processing - RSAMDIN - ORA_PARALLEL_DEGREE ( there was a different RSADMIN parm for older versions - forget what SP the change came with).
You have multiple InfoPackages for the datasource, each loading what should be a different range of data, and they run atthe same time.
You could be loading from two different datasources to the ODS at the same time.
If any of these are true, I would look at bumping the INITRANS setting up. Your DBA will probably need to do this for table and its indices. There is a Note - 831234 that allows you to create a parameter in RSADMIN that will specify a INITRANS value (e.g. 20) rather than using the default. The ODS would need to be activated to pick this new setting up for the table to be altered.
You could also look at the Processing settings for the InfoPackage and change to PSA first, then target to see if that helps.
Or if you are loading from two different datasources at the same time, you might adjust your schedule so that doesn't happen.
Pizzaman

Error while parsing or executing XML-SQL document attribute "action" missin

Hi All,
I am doing a scenario for IDOC to JDBC, When I push IDOC from R/3 , IDOC sent to XI System successfully,
I have also checked in SXMB_MONI it is showing the successful staus without any errors, and I have also copied the xml structure from main document of payloads and tested the mapping in Integration Designer, and it is showing successfull message.
here is the xml structure from payloads of Request Message Mapping ........
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:RTACOGRP_RECEIVER_MT xmlns:ns0="http://prospecta.com/wsorta/cosmas/idoc2jdbc">
- <COGRP_TMP_PROC action="EXECUTE">
<IDOCNUMBER isInput="TRUE" type="CHAR">1000001</IDOCNUMBER>
<E1COGH_NUMBER isInput="TRUE" type="CHAR">1</E1COGH_NUMBER>
<E1COGH_HIGHERSEGMENT isInput="TRUE" type="CHAR">1</E1COGH_HIGHERSEGMENT>
<E1COGH_MSGFN isInput="TRUE" type="CHAR">1</E1COGH_MSGFN>
<E1COGH_GROUPTYPE isInput="TRUE" type="CHAR">1</E1COGH_GROUPTYPE>
<E1COGH_GROUPNAME isInput="TRUE" type="CHAR">1</E1COGH_GROUPNAME>
<E1COGH_KOKRS isInput="TRUE" type="CHAR">1</E1COGH_KOKRS>
<E1COGHT_NUMBER isInput="TRUE" type="CHAR">1</E1COGHT_NUMBER>
<E1COGHT_HIGHERSEGMENT isInput="TRUE" type="CHAR">2</E1COGHT_HIGHERSEGMENT>
<E1COGHT_LANGU isInput="TRUE" type="CHAR">2</E1COGHT_LANGU>
<E1COGHT_DESCRIPT isInput="TRUE" type="CHAR">2</E1COGHT_DESCRIPT>
<E1COGHT_LANGU_ISO isInput="TRUE" type="CHAR">2</E1COGHT_LANGU_ISO>
<E1COGV_NUMBER isInput="TRUE" type="CHAR">1</E1COGV_NUMBER>
<E1COGV_HIGHERSEGMENT isInput="TRUE" type="CHAR">3</E1COGV_HIGHERSEGMENT>
<E1COGV_FROMVALUE isInput="TRUE" type="CHAR">6</E1COGV_FROMVALUE>
<E1COGV_TOVALUE isInput="TRUE" type="CHAR">6</E1COGV_TOVALUE>
<E1COGS_NUMBER isInput="TRUE" type="CHAR">1</E1COGS_NUMBER>
<E1COGS_HIGHERSEGMENT isInput="TRUE" type="CHAR">5</E1COGS_HIGHERSEGMENT>
<E1COGS_SUBGROUP isInput="TRUE" type="CHAR">4</E1COGS_SUBGROUP>
<E1COGHR_NUMBER isInput="TRUE" type="CHAR">1</E1COGHR_NUMBER>
<E1COGHR_HIGHERSEGMENT isInput="TRUE" type="CHAR">6</E1COGHR_HIGHERSEGMENT>
<E1COGHR_SNAME isInput="TRUE" type="CHAR">3</E1COGHR_SNAME>
<E1COGHR_PRTCLASS isInput="TRUE" type="CHAR">3</E1COGHR_PRTCLASS>
<E1COGHR_AUTHGR isInput="TRUE" type="CHAR">3</E1COGHR_AUTHGR>
<E1COGSR_NUMBER isInput="TRUE" type="CHAR">1</E1COGSR_NUMBER>
<E1COGSR_HIGHERSEGMENT isInput="TRUE" type="CHAR">7</E1COGSR_HIGHERSEGMENT>
<E1COGSR_XSUPPRESS isInput="TRUE" type="CHAR">5</E1COGSR_XSUPPRESS>
<E1COGSR_PRTCLASS isInput="TRUE" type="CHAR">5</E1COGSR_PRTCLASS>
<E1COGSR_LNAME isInput="TRUE" type="CHAR">5</E1COGSR_LNAME>
<E1COGVT_NUMBER isInput="TRUE" type="CHAR">1</E1COGVT_NUMBER>
<E1COGVT_HIGHERSEGMENT isInput="TRUE" type="CHAR">9</E1COGVT_HIGHERSEGMENT>
<E1COGVT_LANGU isInput="TRUE" type="CHAR">7</E1COGVT_LANGU>
<E1COGVT_DESCRIPT isInput="TRUE" type="CHAR">7</E1COGVT_DESCRIPT>
<E1COGVT_LANGU_ISO isInput="TRUE" type="CHAR">7</E1COGVT_LANGU_ISO>
<E1COGVR_NUMBER isInput="TRUE" type="CHAR">1</E1COGVR_NUMBER>
<E1COGVR_HIGHERSEGMENT isInput="TRUE" type="CHAR">12</E1COGVR_HIGHERSEGMENT>
<E1COGVR_XSUPPRESS isInput="TRUE" type="CHAR">8</E1COGVR_XSUPPRESS>
<E1COGVR_PRTCLASS isInput="TRUE" type="CHAR">8</E1COGVR_PRTCLASS>
<E1COGVR_LNAME isInput="TRUE" type="CHAR">8</E1COGVR_LNAME>
</COGRP_TMP_PROC>
</ns0:RTACOGRP_RECEIVER_MT>
When I checked for component monitoring in runtime workbench....
these are the messages........
Error while parsing or executing XML-SQL document: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
Here are the messages from message monitoring ......
2007-06-07 12:42:17 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2007-06-07 12:42:17 Success JDBC adapter receiver channel RTACOGRP_COM_Chan: processing started; party , service WSORTABS
2007-06-07 12:42:17 Error No "action" attribute found in XML document ("action" attribute missing or wrong XML structure)
2007-06-07 12:42:17 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2007-06-07 12:42:17 Error Exception caught by adapter framework: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2007-06-07 12:42:17 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure).
2007-06-07 12:42:17 Error The message status set to NDLV.
Can any body please resolve the problem.....
Thanks in Advance
Murthy

Bhavesh,
Now I have changed the data structure , and the resultant structure is like this...
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:RTACOGRP_RECEIVER_MT xmlns:ns0="http://prospecta.com/wsorta/cosmas/idoc2jdbc">
- <Statement>
- <COGRP_TMP_PROC action="EXECUTE">
<IDOCNUMBER isInput="TRUE" type="CHAR">100002223</IDOCNUMBER>
<E1COGH_NUMBER isInput="TRUE" type="CHAR">1</E1COGH_NUMBER>
<E1COGH_HIGHERSEGMENT isInput="TRUE" type="CHAR">1</E1COGH_HIGHERSEGMENT>
<E1COGH_MSGFN isInput="TRUE" type="CHAR">H</E1COGH_MSGFN>
<E1COGH_GROUPTYPE isInput="TRUE" type="CHAR">H</E1COGH_GROUPTYPE>
<E1COGH_GROUPNAME isInput="TRUE" type="CHAR">H</E1COGH_GROUPNAME>
<E1COGH_KOKRS isInput="TRUE" type="CHAR">H</E1COGH_KOKRS>
<E1COGHT_NUMBER isInput="TRUE" type="CHAR">1</E1COGHT_NUMBER>
<E1COGHT_HIGHERSEGMENT isInput="TRUE" type="CHAR">2</E1COGHT_HIGHERSEGMENT>
<E1COGHT_LANGU isInput="TRUE" type="CHAR">T</E1COGHT_LANGU>
<E1COGHT_DESCRIPT isInput="TRUE" type="CHAR">T</E1COGHT_DESCRIPT>
<E1COGHT_LANGU_ISO isInput="TRUE" type="CHAR">T</E1COGHT_LANGU_ISO>
<E1COGV_NUMBER isInput="TRUE" type="CHAR">1</E1COGV_NUMBER>
<E1COGV_HIGHERSEGMENT isInput="TRUE" type="CHAR">3</E1COGV_HIGHERSEGMENT>
<E1COGV_FROMVALUE isInput="TRUE" type="CHAR">V</E1COGV_FROMVALUE>
<E1COGV_TOVALUE isInput="TRUE" type="CHAR">V</E1COGV_TOVALUE>
<E1COGS_NUMBER isInput="TRUE" type="CHAR">1</E1COGS_NUMBER>
<E1COGS_HIGHERSEGMENT isInput="TRUE" type="CHAR">5</E1COGS_HIGHERSEGMENT>
<E1COGS_SUBGROUP isInput="TRUE" type="CHAR">S</E1COGS_SUBGROUP>
<E1COGHR_NUMBER isInput="TRUE" type="CHAR">1</E1COGHR_NUMBER>
<E1COGHR_HIGHERSEGMENT isInput="TRUE" type="CHAR">7</E1COGHR_HIGHERSEGMENT>
<E1COGHR_SNAME isInput="TRUE" type="CHAR">R</E1COGHR_SNAME>
<E1COGHR_PRTCLASS isInput="TRUE" type="CHAR">R</E1COGHR_PRTCLASS>
<E1COGHR_AUTHGR isInput="TRUE" type="CHAR">R</E1COGHR_AUTHGR>
<E1COGSR_NUMBER isInput="TRUE" type="CHAR">1</E1COGSR_NUMBER>
<E1COGSR_HIGHERSEGMENT isInput="TRUE" type="CHAR">8</E1COGSR_HIGHERSEGMENT>
<E1COGSR_XSUPPRESS isInput="TRUE" type="CHAR">S</E1COGSR_XSUPPRESS>
<E1COGSR_PRTCLASS isInput="TRUE" type="CHAR">S</E1COGSR_PRTCLASS>
<E1COGSR_LNAME isInput="TRUE" type="CHAR">S</E1COGSR_LNAME>
<E1COGVT_NUMBER isInput="TRUE" type="CHAR">1</E1COGVT_NUMBER>
<E1COGVT_HIGHERSEGMENT isInput="TRUE" type="CHAR">10</E1COGVT_HIGHERSEGMENT>
<E1COGVT_LANGU isInput="TRUE" type="CHAR">T</E1COGVT_LANGU>
<E1COGVT_DESCRIPT isInput="TRUE" type="CHAR">T</E1COGVT_DESCRIPT>
<E1COGVT_LANGU_ISO isInput="TRUE" type="CHAR">T</E1COGVT_LANGU_ISO>
<E1COGVR_NUMBER isInput="TRUE" type="CHAR">1</E1COGVR_NUMBER>
<E1COGVR_HIGHERSEGMENT isInput="TRUE" type="CHAR">11</E1COGVR_HIGHERSEGMENT>
<E1COGVR_XSUPPRESS isInput="TRUE" type="CHAR">E</E1COGVR_XSUPPRESS>
<E1COGVR_PRTCLASS isInput="TRUE" type="CHAR">E</E1COGVR_PRTCLASS>
<E1COGVR_LNAME isInput="TRUE" type="CHAR">E</E1COGVR_LNAME>
</COGRP_TMP_PROC>
</Statement>
</ns0:RTACOGRP_RECEIVER_MT>
Now in message monitoring error is showing like this...
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC' (structure 'Statement'): java.sql.SQLException: General error
Now in Component Monitoring error is showing like this....
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC' (structure 'Statement'): java.sql.SQLException: General error
I have tested the stored procedure in sql by giving the same values , it was successfully executed..
Can you please tell me where is the error still in structure ...
Thanks in Advance,
Murthy.

ORA-06502: PL/SQL: error TABLE OF BOOLEAN INDEX BY BINARY_INTEGER;

Hi,
I've a Compiled Body Package which code I described below:
create or replace
PACKAGE body emp_pkg
IS
TYPE boolean_tabtype2
IS
TABLE OF BOOLEAN INDEX BY BINARY_INTEGER;
valid_jobs boolean_tabtype2;
PROCEDURE add_employee(
    first_name employees.first_name%TYPE,
    last_name employees.last_name%TYPE,
    deptid employees.department_id%TYPE,
    jobid employees.job_id%type)
IS
BEGIN
IF valid_deptid(deptid) THEN
if valid_jobid(jobid) then
              INSERT
              INTO employees
                  employee_id,
                  first_name,
                  last_name,
                  email,
                  hire_date,
                  job_id,
                  department_id
                VALUES
                  employees_seq.NEXTVAL,
                  first_name,
                  last_name,
                  SUBSTR(first_name,1,1)
                  ||SUBSTR(last_name,1,7)
                  ||'@buongio.com',
                  sysdate,
                  'SA_REP',
                  deptid
     ELSE
        RAISE_APPLICATION_ERROR (-20204, 'Invalid job ID. Try again.');
      END IF;
END add_employee;
PROCEDURE init_jobs
is
begin
FOR rec IN
(SELECT job_id FROM jobs
LOOP
    valid_jobs(rec.job_id):=true;
END LOOP;
END init_jobs;
function valid_jobid(
    jobid employees.job_id%type)
return boolean
is
BEGIN
return valid_jobs.exists(jobid);
EXCEPTION
WHEN no_data_found THEN
dbms_output.put_line('no valid');
RETURN FALSE;
END valid_jobid ;
BEGIN
init_jobs;
END emp_pkg;and the server gives me the next output
ORA-06502: PL/SQL: error : error de conversión de carácter a número numérico o de valorI suspect that the problem is the procedure init_jobs but I don't Know what could I do to resolve it.
Thanks in advance...

sorry
I forget to remove it,
the code:
create or replace
PACKAGE body emp_pkg
IS
TYPE boolean_tabtype2
IS
TABLE OF BOOLEAN INDEX BY BINARY_INTEGER;
valid_jobs boolean_tabtype2;
PROCEDURE add_employee(
    first_name employees.first_name%TYPE,
    last_name employees.last_name%TYPE,
    deptid employees.department_id%TYPE,
    jobid employees.job_id%type)
IS
BEGIN
if valid_jobid(jobid) then
              INSERT
              INTO employees
                  employee_id,
                  first_name,
                  last_name,
                  email,
                  hire_date,
                  job_id,
                  department_id
                VALUES
                  employees_seq.NEXTVAL,
                  first_name,
                  last_name,
                  SUBSTR(first_name,1,1)
                  ||SUBSTR(last_name,1,7)
                  ||'@buongio.com',
                  sysdate,
                  'SA_REP',
                  deptid
     ELSE
        RAISE_APPLICATION_ERROR (-20204, 'Invalid job ID. Try again.');
      END IF;
END add_employee;
PROCEDURE init_jobs
is
begin
FOR rec IN
(SELECT job_id FROM jobs
LOOP
    valid_jobs(rec.job_id):=true;
END LOOP;
END init_jobs;
function valid_jobid(
    jobid employees.job_id%type)
return boolean
is
BEGIN
return valid_jobs.exists(jobid);
EXCEPTION
WHEN no_data_found THEN
dbms_output.put_line('no valid');
RETURN FALSE;
END valid_jobid ;
BEGIN
init_jobs;
END emp_pkg;

NI 4060 Procedure SQL-Error in Calibratio​n Executive 2.0

Similar Messages

Maybe you are looking for

NI 4060 Procedure SQL-Error in Calibration Executive 2.0