EXEC SQL STMT

What does an EXEC SQL stmt do in ABAPTM? What is the disadvantage of using it?

Hi
EXEC SQL statement will occupy more memory
when you done program just check in SQL trace tool.
performance tool is there to check
just go to SE39.Enter your program if its red you have to change SQL query in your program.If its green thats a good program.
if its useful reward points
Thanks
senthil

Similar Messages

What does an EXEC SQL stmt do in ABAP? What is the disadvantage of using it

hi,
What does an EXEC SQL stmt do in ABAP? What is the disadvantage of using it?
regards.

sorry, question resolved.

EXEC SQL

Hi,
What does an EXEC SQL stmt do in ABAP?
What is the disadvantage of using it?
Regards,
Kalai

Hi
EXEC SQL
EXEC SQL [PERFORMING subr].
ENDEXEC.
These statements define an area in an ABAP program in which one or more Native SQL statements are to be carried out. The area between EXEC and ENDEXEC is not completely checked by the syntax check. The statements entered there are passed to the Native SQL interface and processed there as follows:
Almost all SQL statements that are valid for the addressed database system can be included between EXEC and ENDEXEC, in particular the DDL statements. These SQL statements are passed from the Native SQL interface to the database system largely unchanged. The syntax rules are specified by the database system, in particular the case sensitivity rules for database objects. If the syntax allows a separator character between individual statements, you can include several Native SQL statements between EXEC and ENDEXEC. Generally, the semicolon ( is used as the separator character.
You can also include SAP-specific Native SQL language elements between EXEC and ENDEXEC. These statements are not passed directly from the Native SQL interface to the database, but are converted appropriately. These SAP-specific language elements are::
Host variables
Statements for cursor processing
Database procedure calls
Statements for establishing database connections
All Native SQL statements bypass SAP buffering. Automatic client handling is not performed.
System fields
The statement ENDEXEC sets the system fields sy-subrc and sy-dbcnt.
sy-subrc Meaning
0 The statements between EXEC and ENDEXEC were executed successfully.
4 The statements between EXEC and ENDEXEC were not executed.
The ENDEXEC statement sets sy-dbcnt to the number of table rows processed in the last Native SQL statement.
Programs with Native SQL statements are generally dependent on the database system used, so that they cannot be executed in all SAP Systems. This is especially true for the examples in this section, which was written for Informix database systems.
Example Inserting two rows in the database table SCARR. If neither of these rows exists, sy-subrc is set to 0 by ENDEXEC and sy-dbcnt to 1. Otherwise, an exception is raised and handled.
DATA: exc_ref TYPE REF TO cx_sy_native_sql_error,
 error_text TYPE string.
TRY.
 EXEC SQL.
 INSERT INTO scarr
 (MANDT, CARRID, CARRNAME, CURRCODE, URL)
 VALUES ('000', 'FF', 'Funny Flyers', 'EUR',
 'http://www.ff.com');
 INSERT INTO scarr
 (MANDT, CARRID, CARRNAME, CURRCODE, URL)
 VALUES ('000', 'EF', 'Easy Flyers', 'EUR',
 'http://www.ef.com');
 ENDEXEC.
CATCH cx_sy_native_sql_error INTO exc_ref.
 error_text = exc_ref->get_text( ).
 MESSAGE error_text TYPE 'I'.
ENDTRY.
Reward if usefull

EXEC SQL and DBIF_DSQL2_CONNECTERR error

Hello,
Currently our shipping system is communicating with SAP below are the parameters used:
<SAPProgramID>kewill_LXD</SAPProgramID>
<SAPGatewayHost>10.XX.40.XX</SAPGatewayHost>
<SAPGatewayService>sapgw00</SAPGatewayService>
<TransHandlerConnString>STMT=;OPTION=3;DSN=didb;UID=sn_usr;PASSWORD=sipndb;DESC=MySQL ODBC 3.51 Driver;DATABASE=didb;SERVER=localhost;PORT=3306</TransHandlerConnString
This is what I have in DBCON or tcode DBCO
Connection Name: Ship
DBMS: MSS
User Name: sn_usr
Password: sipndb
Conn. info: MSSQL_SERVER=localhost;MSSQL_DBNAME=didb
I get a dump with DBIF_DSQL2_CONNECTERR error when I try to use this in the EXEC SQL:
REPORT ZKEWILL_CONN .
Tables: DBCON.
DATA: BEGIN OF WA,
 ship_date(10), S2Name1(50),
 END OF WA.
DATA : bdate(10) value '2008-09-29',
 edate(10) value '2008-10-05'.
EXEC SQL.
CONNECT TO 'KEWILL' AS 'K'
ENDEXEC.
EXEC SQL.
SET CONNECTION 'K'
ENDEXEC.
EXEC SQL.
SELECT ship_date, s2name1 INTO :WA FROM shipment_header
 WHERE ship_date >= :bdate
 AND ship_date <= :edate
ENDEXEC.
WRITE: / WA-ship_date, WA-s2name1.
We are in 4.6C. Please let me know if I need to make changes to the DBCO or to the program or both.... thanks!!
AJ

Hi Jimmy,
The issue is more related to livecache.So can you please close this tread and create new thread under forum 'SAP MaxDB/livecache'.
Thanks & Regards,
Sunitha

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

Getting core dump when using EXEC SQL CLOSE

In my pro*c program , i have used a cursor to fetch the set of accounts.Once cursor is opened , code will perform set
of operation using fetched data and then cursor is closed. Between open and closing of cursor , i have used 23 EXEC
SQL CLOSE. For example i am copying the value of a to b using strlcpy between fetch and close cursor statement.If
returned value from strlcpy is greater than size of destination variable, then flow should not proceed , in that case I will
close the cursor using EXEC SQL CLOSE and return the flow to calling program. Similarly i have closed the cursor at
another 22 locations.
When i compile the code and run binary the core dump occurs. On analyzing the core it shows
t@null (l@8) terminated by signal SEGV (no mapping at the fault address)
0xffffffffffffffff: <bad address 0xffffffffffffffff>
dbx: core file read error: address 0xfc4ffe48 not in data space
Current function is dbMtBaseClass::Pswd_Change
7860 sqlcxt(&_dbMtCtx, &sqlctx, &sqlstm, &sqlfpn);
if I remove any of the three EXEC SQL CLOSE commands , core dump does not occurs.
It looks strange.Please help me to resolve the issue.

In my pro*c program , i have used a cursor to fetch the set of accounts.Once cursor is opened , code will perform set
of operation using fetched data and then cursor is closed. Between open and closing of cursor , i have used 23 EXEC
SQL CLOSE. For example i am copying the value of a to b using strlcpy between fetch and close cursor statement.If
returned value from strlcpy is greater than size of destination variable, then flow should not proceed , in that case I will
close the cursor using EXEC SQL CLOSE and return the flow to calling program. Similarly i have closed the cursor at
another 22 locations.
When i compile the code and run binary the core dump occurs. On analyzing the core it shows
t@null (l@8) terminated by signal SEGV (no mapping at the fault address)
0xffffffffffffffff: <bad address 0xffffffffffffffff>
dbx: core file read error: address 0xfc4ffe48 not in data space
Current function is dbMtBaseClass::Pswd_Change
7860 sqlcxt(&_dbMtCtx, &sqlctx, &sqlstm, &sqlfpn);
if I remove any of the three EXEC SQL CLOSE commands , core dump does not occurs.
It looks strange.Please help me to resolve the issue.

Use Of "#EC CI_EXECSQL in ABAP with EXEC SQL. Statement giving Syntax Error

Dear Gurus,
I have encountered an issue while trying to remove warning for using Native SQL statement using pseudo comment "#EC CI_EXECSQL
The thing is like this -- i have used follwing native sql command in abap.
EXEC SQL.
    CONNECT TO 'SURROUND_DB'
ENDEXEC.
Now when i am checking this code in code inspector it is showing a warning with information below
CA CL_CI_TEST_CRITICAL_STATEMENTS0006
Code Inspector
Critical Statements
Use of Native SQL
Authorization checks cannot be appropriately run using EXEC SQL and should be carried out at program level.
The message can be hidden using the pseudo-comment "#EC CI_EXECSQL
Use of exceptin handling section for that warning showing me to use :
The message can be hidden using pseudo
comment      "#EC CI_EXECSQL
Now when I am using "#EC CI_EXECSQL in the abap like below :
EXEC SQL. "#EC CI_EXECSQL
    CONNECT TO 'SURROUND_DB'
ENDEXEC.
It is giving syntax error
The text literal ""#EC CI_EXECSQL        " is longer than 255
characters.Check whether it ends correctly.
Please provide the guideline to resolve this issue.
Thanks & regards
Saifur Rahaman.

Hi Saifur,
You can remove the warning using the following syntax:
EXEC "#EC CI_EXECSQL
SQL.
    CONNECT TO 'SURROUND_DB'
ENDEXEC.
At least, it worked fine for me when using OPEN CURSOR, SELECT, FETCH and so on statements.
The way to use the pseudo comment is not very intuitive, but at least for my examples worked fine.
I hope this may help you.
Best regards,
Edgardo G. König

EXEC SQL join in ABAP program

Hi All,
I am using EXEC SQL join in my ABAP report,but it is giving dump.could you please correct my following code?
START-OF-SELECTION.
CONCATENATE '%' pa_match '%' INTO tp_match.
EXEC SQL.
 OPEN dbcur FOR
 SELECT kunnr,name1, banks
 FROM kna1 as a inner join
 knbk as b
 on akunnr = bkunnr
 WHERE a.kunnr = b.kunnr and
 upper(a~name1) LIKE :tp_match
ENDEXEC.
DO.
 EXEC SQL.
 FETCH NEXT dbcur INTO :wa_name1
 ENDEXEC.
 IF sy-subrc <> 0.
 EXIT.
 ENDIF.
 APPEND wa_name1 TO ta_name1.
 COLLECT wa_name1 INTO ta_name1.
ENDDO.
EXEC SQL.
 CLOSE dbcur
ENDEXEC.

Remove the 'As' from the statement
EXEC SQL.
OPEN dbcur FOR
SELECT kunnr,name1, banks
FROM kna1 a inner join "Delete 'AS' here
knbk b
on a~kunnr = b~kunnr
WHERE a.kunnr = b.kunnr and
upper(a~name1) LIKE :tp_match
ENDEXEC.

Where can i set up connection in "exec sql"?

i have code block like this:
EXEC SQL.
 SET CONNECTION :'PA'
ENDEXEC.
IF SY-SUBRC <> 0.
Connection not yet opened.
 EXEC SQL.
 CONNECT TO :'PA'
 ENDEXEC.
 IF SY-SUBRC <> 0.
 write: / sy-msgid ,sy-msgno,sy-msgty,sy-msgv1,sy-msgv2,sy-msgv3,sy-msgv4.
 write: / 'connect error'.
 RAISE EXCEPTION TYPE cx_sy_native_sql_error.
 ENDIF.
ENDIF.
where can i set up the 'PA'?thanks very much!!!!

You set up new databse connection for SAP to communincate with using 'DBCO' tcode.

ORacle sales analyzer doesn't display sql's using show sq.sql.stmts

Hi,
I cannot view the sql statements generated by Oracle Sales analyzer cube using show sq.sql.stmts.
Moreover when I check on db I don't see any sql's being issued by web OSA session.
What could be the possible reason for this?

Lang wrote:
Hi
Can anyone help please, I am using SQL developer 3.0, and I have come across a lot of cases that after compiling a package , the compiler doesn't show me any errors, and It shows me the package is compiled , but it 's not valid after I close down the sql developer and log back in again.
I am using 11g instantclient with it.Really?
& here I thought SQL Developer used JDBC Thin to connect to the DB.

How to use INSERT in EXEC SQL ...... ENDEXEC ?

Hi,
The following code;
DATA: BEGIN OF str_insert,
        a(3) TYPE c,
        b(3) TYPE c,
      END OF str_insert.
EXEC SQL.
SET CONNECTION DEFAULT
ENDEXEC.
str_insert-a = 'a'.
str_insert-b = 'b'.
EXEC SQL.
INSERT INTO ZSAP VALUES :str_insert
ENDEXEC.
The Structure of the ZSAP table (There is no data in ZSAP);
A CHAR 3 (Primary Key)
B CHAR 3
I cannot instert a record to this table it throughs the following error;
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Exceptn                CX_SY_NATIVE_SQL_ERROR
How could use a structure to insert values into ZSAP?
Thanks,
Kishan

Hello..
loop at T_PC.
    loop at T_PCD .
      at new NUMREFERENCIA.
        exec sql.
         INSERT INTO tblPolizaContableR3
            (LibroMayor, PeriodoContable, Prefijo, NumReferencia,
            Fecha, FuenteDiario, ComentarioPoliza, Moneda,
            TipoCambio, RefExternaID1, RefExternaID2, RefExterna1,
            RefExterna2, DescRefExterna)
         VALUES (:T_PC-LIBROMAYOR, :T_PC-PERIODOCONTABLE,
          :T_PC-PREFIJO, :T_PC-NUMREFERENCIA, :T_PC-FECHA,
          :T_PC-FUENTEDIARIO, :T_PC-COMENTARIOPLIZA, :T_PC-MONEDA,
          :T_PC-TIPOCAMBIO, :T_PC-REFEXTARNAID1, :T_PC-REFEXTERNAID2,
          :T_PC-REFEXTERNA1, :T_PC-REFEXTERNA2, :T_PC-DESCREFEXTERNA)
        endexec.
      endat.
        exec sql.
         INSERT INTO tblPolizaContableDetR3
            (LibroMayor, PeriodoContable, Prefijo, NumReferencia,
            Partida, Cuenta, CuentaIMSA, CCostoIMSA,
            Cargo, Abono, ComentarioPartida)
         VALUES (:T_PCD-LIBROMAYOR, :T_PCD-PERIODOCONTABLE,
          :T_PCD-PREFIJO, :T_PCD-NUMREFERENCIA, :T_PCD-PARTIDA,
          :T_PCD-CUENTA, :T_PCD-CUENTAIMSA, :T_PCD-CCOSTOIMSA,
          :T_PCD-CARGO, :T_PCD-ABONO, :T_PCD-COMENPARTIDA)
        endexec.
    endloop.
Hope this help you.
Regards, Gustavo Estrada

Count (*) for select stmt take more time than execute a that sql stmt

HI
count (*) for select stmt take more time than execute a that sql stmt
executing particular select stmt take 2.47 mins but select stmt is using the /*+parallel*/ (sql optimer) in that sql command for faster execute .
but if i tried to find out total number of rows in that query it takes more time ..
almost 2.30 hrs still running to find count(col)
please help me to get count of row faster.
thanks in advance...

797525 wrote:
HI
count (*) for select stmt take more time than execute a that sql stmt
executing particular select stmt take 2.47 mins but select stmt is using the /*+parallel*/ (sql optimer) in that sql command for faster execute .
but if i tried to find out total number of rows in that query it takes more time ..
almost 2.30 hrs still running to find count(col)
please help me to get count of row faster.
thanks in advance...That may be because your client is displaying only the first few records when you are running the "SELECT *". But when you run "COUNT(*)", the whole records has to be counted.
As already mentined please read teh FAQ to post tuning questions.

Exec sql Execute in Pro*C

Hi,
My ProC code works fine when I have Exec sql in it but when I include plsql block in it using EXEC SQL EXECUTE, it throws the following error:
/tmp/cc88UGZa.o(.text+0x2c0): In function `main':
: undefined reference to `ECPGget_sqlca'
I have included all these below header files:
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
#include <sqlca.h>
#include <sqlda.h>
#include <sqlcpr.h>
and the path have been mentioned in pcscfg.cfg as well.
what can be the reason and the solution to this please? Help is appreciated.
Thanks in advance!
Ash

You have to use 'BEGIN procedure_name END' in the execute statement while calling PL/SQL Procedures
EXEC SQL EXECUTE
DECLARE
BEGIN
END;
END-EXEC;

EXEC SQL Error: ORA-01401: Inserted value too large for column

Getting this SQL Error: ORA-01401: Inserted value too large for column..on an EXEC SQL Insert statement when writing to an
external Oracle DB from SAP.
On further analysis..it appears that this happens to the fields..when the string length matches the field length.
Example: Plant field is defined as char(4) on the SAP side and it is a Varchar2(4) on the Oracle side.
When a value like '1015' is passed thru a variable in the insert statement then this ORA-01401 error pops up.
No error:
   - if the value '1015' is passed directly in the insert statement to the external table (or)
   - when a value with 3 chars or less(like the first three chars..101) is passed thru a variable defined as 'Plant(4) type c'.
   - when using EXEC sql within SAP
   - when reading from the external db table
This was working ok until the Oracle Patch P9147110 was installed recently.
Any suggestions !

Hello Dvas,
what's the characterset of your external database?
What's the column definition in your external database (byte or character based)?
If you use a characeterset like UTF8 it is possible, that one character needs more than one byte and then you will run into such kind of issues if the definition is too small.
Regards
Stefan

File: e:\pt849-905-R1-retail\peopletools\SRC\PSRED\psred.cppSQL error. Stmt #: 1849 Error Position: 24 Return: 3106 - ORA-03106: fatal two-task communication protocol error Failed SQL stmt:SELECT PROJECTNAME FROM PSPROJECTDEFN ORDER

File:
e:\pt849-905-R1-retail\peopletools\SRC\PSRED\psred.cppSQL error. Stmt #:
1849 Error Position: 24 Return: 3106 - ORA-03106: fatal two-task
communication protocol error
Failed SQL stmt:SELECT PROJECTNAME FROM PSPROJECTDEFN ORDER
BY PROJECTNAME
Got this error when opening the peopletools application designer 8.49. The same is working fine within the server, but not working from the client's machine.
We can still able to connect to the database & URL
Please help by throwing some lights.
Thanks,
Sarathy K

Looks like a SQL error. ARe you able to connect to the database with SQL*Plus ? Probably the Oracle client is badly configured.
Nicolas.

EXEC SQL STMT

Similar Messages

Maybe you are looking for