Problem when using execute immediate str variable into refcursor var

Hi,
I have a packaged function which returns a "strong refcursor" variable to the calling program.
inside this packaged function, i had to use dynamic sql ....
i am doing it somethingl like this...
execute immediate lc_submit_Sql into lrc_submitted;
where lc_submit_Sql contains the query. and lrc_submitted is declared as a refcursor variable which is a recordtype.
when calling this packaged function from an anonymous block getting an error.....
"ora-00932 inconsistent datatypes:expecting - got -"
I checked the select statment columns and the record type columns, their types and order. they are fine.
not sure abt the reason.
any help is appreciated. have some dead lines to meet.
Thanks in advance.
Kiran

Hi John,
the following is the code ....
package spec...
CREATE OR REPLACE PACKAGE refcur_kk IS
--Sample submitted Function
TYPE r_submitted IS RECORD(
q_party_name apps.bpsicc_crm_quote_header_v.party_name%TYPE,
q_party_id apps.bpsicc_crm_quote_header_v.cust_party_id%TYPE,
q_quote_header_id apps.bpsicc_crm_quote_header_v.quote_header_id%TYPE,
q_creation_date apps.bpsicc_crm_quote_header_v.quote_creation_date%TYPE,
q_created_by apps.bpsicc_crm_quote_header_v.quote_created_by%TYPE,
q_quote_status apps.bpsicc_crm_quote_header_v.quote_status%TYPE,
q_quote_name apps.bpsicc_crm_quote_header_v.quote_name%TYPE,
q_quote_number apps.bpsicc_crm_quote_header_v.quote_number%TYPE,
q_internal_project_details apps.bpsicc_crm_quote_line_v.internal_project_details%TYPE,
ql_item apps.bpsicc_crm_item_all_v.item_number%TYPE,
ql_item_link apps.bpsicc_crm_item_all_v.item_link%TYPE,
ql_party_link apps.bpsicc_gcm_party_details_v.party_link%TYPE,
ql_quantity apps.bpsicc_crm_quote_line_v.quantity%TYPE,
q_country apps.bpsicc_gcm_party_sites_v.party_site_country_name%TYPE,
q_territory apps.bpsicc_crm_party_by_terr_mv.territory%TYPE,
q_region apps.bpsicc_crm_party_by_terr_mv.region%TYPE,
q_created_disp apps.bpsicc_crm_quote_header_v.quote_created_by_username%TYPE,
reqst_shipdate apps.bpsicc_crm_quote_header_v.date_of_request%TYPE,
q_item_color apps.bpsicc_crm_item_all_v.item_color%TYPE
TYPE rc_submitted IS REF CURSOR;
RETURN r_submitted;
FUNCTION get_submitted(
pd_start_date IN DATE,
pc_time IN VARCHAR2,
pd_end_date IN DATE,
pc_party_id IN VARCHAR2,
pc_price_class IN VARCHAR2,
ps_section IN VARCHAR2,
pn_sales_channel IN NUMBER,
pc_country IN VARCHAR2,
pc_territory IN VARCHAR2,
pc_region IN VARCHAR2)
RETURN rc_submitted;
and the body of it.....
ls_submit_sql:= 'SELECT bcqhv.party_name q_party_name,'||
'bcqhv.cust_party_id q_party_id,'||
'bcqhv.quote_header_id q_quote_header_id,'||
'TRUNC(bcqhv.quote_creation_date) q_creation_date,'||
'bcqhv.quote_created_by q_created_by,'||
'bcqhv.quote_status q_quote_status,'||
'bcqhv.quote_name q_quote_name,'||
'bcqhv.quote_number q_quote_number,'||
'bcqlv.internal_project_details q_internal_project_details,'||
'bciav.item_number ql_item,'||
'bciav.item_link ql_item_link,'||
'bgpdv.party_link ql_party_link,'||
'bcqlv.quantity ql_quantity,'||
'bgpsv.party_site_country_name q_country,'||
'bcpbtv.territory q_territory,'||
'bcpbtv.region q_region,'||
'bcqhv.quote_created_by_username q_created_disp,'||
'bcqhv.date_of_request reqst_ship_date,'||
'bciav.item_color q_item_color '||
'FROM apps.bpsicc_crm_quote_header_v bcqhv,'||
'apps.bpsicc_crm_party_by_terr_mv bcpbtv,'||
'apps.bpsicc_gcm_party_sites_v bgpsv,'||
'apps.bpsicc_crm_quote_line_v bcqlv,'||
'apps.bpsicc_crm_item_all_v bciav,'||
'apps.bpsicc_gcm_party_details_v bgpdv '||
'WHERE bciav.inventory_item_id = bcqlv.inventory_item_id '||
'AND bcqhv.cust_party_id = bcpbtv.party_id '||
'AND bcqhv.sold_to_party_site_id = bgpsv.party_site_id '||
'AND bgpdv.party_id = bcqhv.cust_party_id '||
'AND bcqlv.quote_header_id = bcqhv.quote_header_id '||
'AND bcqhv.quote_status IN ('||chr(39)||'Submitted to Lab for Review'||chr(39)||','||chr(39)||'Submitted to US Lab for Review'||chr(39)||')';
execute immediate ls_submit_sql into lrc_submitted;
returning lrc_submitted to the report which is calling this function.
using oracle report builder.
kiran

Similar Messages

Have problem when using EXECUTE IMMEDIATE.

Hi, i'm new here... i having problem when trying to use execute immediate statement... :(
procedure code as below:
create procedure copy_row(
p_table varchar2,
p_key varchar2,
p_keyval varchar2,
p_user varchar2,
p_frmto varchar2 default 'FROM')
IS
V_SQL VARCHAR2(500);
BEGIN
if upper(p_frmto)='FROM' then
V_SQL:='INSERT INTO '||P_TABLE||
' SELECT * FROM '||P_USER||'.'||P_TABLE||' WHERE '||P_KEY||' = '''||P_KEYVAL||'''';
elsif upper(p_frmto)='TO' then
V_SQL:='INSERT INTO '||P_USER||'.'||P_TABLE||
' SELECT * FROM '||P_TABLE||' WHERE '||P_KEY||' = '''||P_KEYVAL||'''';
end if;
EXECUTE IMMEDIATE V_SQL;
exception
when others then
raise_application_error(-20000,'PROCEDURE: COPY_ROW - UNABLE TO COPY ROWS! SQL='||V_SQL,TRUE);
end;
is there any limitation on using EXECUTE IMMEDIATE command? i need to use procedure because i'm using old form builder.... but the database server was 9i which able to use this command, so... i decide to use procedure....
i've done some testing on this.... assume the structure of schema1.table1 and schema2.table1 are same....
SQL> CREATE PROCEDURE TESTING IS
2 BEGIN
3 exeCute IMMEDIATE 'INSERT INTO schema1.table1 SELECT * FROM schema2.table1 WHERE column1 = ''abc''';
4 END;
5 /
Procedure created.
SQL> BEGIN
2 TESTING;
3 END;
4 /
BEGIN
ERROR at line 1:
ORA-00942: table or view does not exist
ORA-06512: at "SCHEMA1.TESTING", line 3
ORA-06512: at line 2
any idea?? or have better solution other than this?
database server:9i
sqlplus:SQL*Plus: Release 8.0.6.0.0

Do you have an access to tables you are going to insert into / select from ?
Dynamic SQL checks the access permissions at runtime, not at the compilation stage:
SQL> create user master identified by master default tablespace users temporary
2 tablespace temp;
User created.
SQL> alter user master quota unlimited on users;
User altered.
SQL> grant create session to master;
Grant succeeded.
SQL> grant create table to master;
Grant succeeded.
SQL> grant create procedure to master;
Grant succeeded.
SQL> conn master/master
Connected.
SQL> create procedure wrong_prc
2 is
3 begin
4   execute immediate 'insert into master.t select * from scott.t';
5 end;
6 /
Procedure created.
SQL> create table t (id number);
Table created.
SQL> exec wrong_prc;
BEGIN wrong_prc; END;
ERROR at line 1:
ORA-00942: table or view does not exist
ORA-06512: at "MASTER.WRONG_PRC", line 4
ORA-06512: at line 1
SQL> conn scott/tiger
Connected.
SQL> grant select on t to master;
Grant succeeded.
SQL> conn master/master
Connected.
SQL> exec wrong_prc;
PL/SQL procedure successfully completed.
SQL> select * from t;
        ID
         1And don't use literals in dynamic SQL - you should use binding variables instead.
Rgds.

Coercion problem when using Shared Variable

I have a curious coercion problem when using Shared Variables. I want to share the state of a State Machine, which is an enum saved as a control (typedef) called TYPE State (see attached). I create a shared variable called State and define it as a Custom Control, using the just-mentioned typedef. So far, so good. I've attached three simple VIs -- the first one, Init State, simply wires a constant to the input of the Shared Variable to initialize it -- the wired constant is, of course, defined by the typedef. However, the Get State and Set State, meant to wire an indicator (for reading the state) or control (for setting it), develop coercion dots when wired into the Shared Variable. Why? How do I get rid of the dot? [I suppose I could abandon my typedef and custom control, but the beauty of typedefs and custom controls is that it "enforces" rules, lets you use enums for clarity, keeps the code "honest", etc. -- I'd hate to give that up just to get rid of a dot!].
On a related note, the code seems to work. This is much too simplistic to do anything, but if you open Set State and Get State, set the state to anything, run it (it immediately stops, of course), then run Get State, you'll see the chosen state appear in the indicator. So it does appear to work. The "error" (coercion dot) may, I suppose, be a "bug" in Labview because it can't figure out the mapping of the (very simple!) Custom Control, but if so, I hope it gets fixed quickly!
Bob Schor
Attachments:
Coercion Problem1.zip ‏38 KB

Hello Bob,
I am also seeing this behavior, I will escalate this question to our LabVIEW developers and post again here no later than next Tuesday, November 27th as National Instruments will be closed for the remainder of this week.
If this issue does turn into a product suggestion, I would suspect the workaround would to live with the coersion dot for the time being.
Enjoy the holiday
Regards,
Erik J.
Applications Engineer
National Instruments

Problem using EXECUTE IMMEDIATE

Hi,
I am running the following procedure..
table emp ( empno number,ename varchar2 , dept varchar2 )
CREATE OR REPLACE PROCEDURE Sp_Test11 ( p_dept IN VARCHAR2 )
IS
m_count               NUMBER               :=     NULL;
m_sql_query               VARCHAR2(32767) := 'SELECT COUNT(*) INTO m_count FROM emp WHERE dept = ';
BEGIN
m_sql_query := m_sql_query||''''||p_dept||''''||';';
     EXECUTE IMMEDIATE m_sql_query ;
END Sp_Test11;
I am getting the "Invalid character" error on execute immediate statement when i debug ..
Please guide.

venkata wrote:
Use RETURN or RETURNING INTO Keywords in execute immediate statement.RETURNING INTO is used with INSERT/UPDATE/DELETE statements when there will be triggers that will populate something on the table after an insert or update etc. e.g. when you insert a new record and you want to return the primary key that is automatically generated from a sequence so you can use it in your code for something else.
If you are SELECTing data then you would use the INTO keyword as Gj demonstrated.
SQL> ed
Wrote file afiedt.buf
1 declare
2    v_cnt number;
3 begin
4    execute immediate 'select count(*) from x' returning into v_cnt;
5* end;
SQL> /
declare
ERROR at line 1:
ORA-06547: RETURNING clause must be used with INSERT, UPDATE, or DELETE statements
ORA-06512: at line 4
SQL> ed
Wrote file afiedt.buf
1 declare
2    v_cnt number;
3 begin
4    execute immediate 'select count(*) from x' into v_cnt;
5* end;
SQL> /
PL/SQL procedure successfully completed.
SQL>It's amazing how many people are just jumping in here with wrong answers.

Why or When should we use Execute Immediate in PLSQL??

Hi Frnds,
Long Ago i have received a interview question that ...
How can U create a table in the PLSQL object(Function or procedure)?
But the thing y should we use execute immediate?
In which scenario we should we should use????????????
Why or When should we use Execute Immediate in PLSQL????

OR
http://stackoverflow.com/questions/18375990/oracle-what-does-execute-immediate-means
For DML you'd use it when running statements that you don't have available at compile time, e.g. if the column list is based on a selection from the user.
In your case it's being used because DDL cannot be run as static SQL from within PL/SQL. Only certain query, DML and TCL commands are valid. Anything else has to be treated as dynamic.
I'd say it's rare to need to use DDL from a PL/SQL block. TRUNCATE might be reasonable; if you find anything creating or dropping objects on the fly then that might be more of a concern as it can suggest a suboptimal data model.
EXECUTE IMMEDIATE itself does not automatically commit; but if you execute DDL then that will behave the same as if you ran it outside PL/SQL, so it will commit in your case, yes.
Incidentally, I'm not sure why your code is using an intermediate variable to hold the statement; that's useful if you want to display what it's going to run maybe, but you don't seem to be doing that. What you have could be done as:
EXECUTE IMMEDIATE 'TRUNCATE TABLE BD_BIDS_EXT_DET';
Thank you

Problem in Update statement using Execute Immediate

Hi All,
I am facing problem in update statement.
I am creating dynamic sql and use "execute immediate" statement to execute a update statement.
But it is not updating any thing there in the table.
I have created a query like :
update_query='Update '|| Table_Name ||' t set t.process_status =''Y'' where t.tid=:A';
Execute immediate update_query using V_Id;
commit;
But it is not updating the table.
I have a question , is execute immediate only does insert and delete?
Thanks
Ashok

SQL> select * from t;
                 TID P
                 101 N
SQL> declare
2     V_Id          number := 101;
3     Table_Name    varchar2(30) := 'T';
4     update_query varchar2(1000);
5 begin
6     update_query := 'Update '|| Table_Name ||' t set t.process_status =''Y'' where t.tid=:A';
7     Execute immediate update_query using V_Id;
8     commit;
9 end;
10 /
PL/SQL procedure successfully completed.
SQL> select * from t;
                 TID P
                 101 Y

Error while insert data using execute immediate in dynamic table in oracle

Error while insert data using execute immediate in dynamic table created in oracle 11g .
first the dynamic nested table (op_sample) was created using the executed immediate...
object is
CREATE OR REPLACE TYPE ASI.sub_mark AS OBJECT (
mark1 number,
mark2 number
t_sub_mark is a class of type sub_mark
CREATE OR REPLACE TYPE ASI.t_sub_mark is table of sub_mark;
create table sam1(id number,name varchar2(30));
nested table is created below:
begin
EXECUTE IMMEDIATE ' create table '||op_sample||'
(id number,name varchar2(30),subject_obj t_sub_mark) nested table subject_obj store as nest_tab return as value';
end;
now data from sam1 table and object (subject_obj) are inserted into the dynamic table
declare
subject_obj t_sub_mark;
begin
subject_obj:= t_sub_mark();
EXECUTE IMMEDIATE 'insert into op_sample (select id,name,subject_obj from sam1) ';
end;
and got the below error:
ORA-00904: "SUBJECT_OBJ": invalid identifier
ORA-06512: at line 7
then when we tried to insert the data into the dynam_table with the subject_marks object as null,we received the following error..
execute immediate 'insert into '||dynam_table ||'
(SELECT

887684 wrote:
ORA-00904: "SUBJECT_OBJ": invalid identifier
ORA-06512: at line 7The problem is that your variable subject_obj is not in scope inside the dynamic SQL you are building. The SQL engine does not know your PL/SQL variable, so it tries to find a column named SUBJECT_OBJ in your SAM1 table.
If you need to use dynamic SQL for this, then you must bind the variable. Something like this:
EXECUTE IMMEDIATE 'insert into op_sample (select id,name,:bind_subject_obj from sam1) ' USING subject_obj;Alternatively you might figure out to use static SQL rather than dynamic SQL (if possible for your project.) In static SQL the PL/SQL engine binds the variables for you automatically.

Error while using execute immediate

Hi,
I am trying to get the record count of a table. The table name is saved in a variable..
when i am writing the code like below its working fine.
SELECT count(*) into count1 FROM emp1;
DBMS_OUTPUT.PUT_LINE(count1);
but when i am using the code for the table name in variable its giving error
execute immediate 'SELECT count(*) into count1 FROM ' || t_name;
DBMS_OUTPUT.PUT_LINE(count1);
the error is
ERROR at line 1:
ORA-00905: missing keyword
ORA-06512: at "SYSTEM.TEST_COL", line 14
ORA-06512: at line 1
any help
Ashish

Interesting, the into count doesn't be a problem, but the count variable usage does :
SQL> set serveroutput on
SQL> l
1 declare
2     count number;
3     t_name varchar2(30):='all_objects';
4 begin
5     execute immediate 'select count(*) from ' || t_name into count;
6 exception when others then dbms_output.put_line(sqlcode||' : '||sqlerrm);
7* end;
SQL> /
PL/SQL procedure successfully completed.
SQL> declare
2     count number;
3     t_name varchar2(30):='all_objects';
4 begin
5     execute immediate 'select count(*) from ' || t_name into count;
6     dbms_output.put_line(count);
7 exception when others then dbms_output.put_line(sqlcode||' : '||sqlerrm);
8* end;
SQL> /
   dbms_output.put_line(count);
ERROR at line 6:
ORA-06550: line 6, column 25:
PLS-00204: function or pseudo-column 'COUNT' may be used inside a SQL statement
only
ORA-06550: line 6, column 4:
PL/SQL: Statement ignoredNicolas.

Oracle 11G Copying a table using execute immediate

I want to copy the contents of one table into another using execute immediate.
This keeps failing with the following error
ORA-00903: invalid table name
ORA-06512: at "TABLE_COPY", line 6
ORA-06512: at line 8
create or replace
procedure TABLE_COPY(
TABLE1 varchar2,
TABLE2 varchar2)
is
begin
execute immediate 'insert into '||TABLE2||' (select * from '||TABLE1||')';
end;
Edited by: user9213000 on 24-Jan-2013 07:38

user9213000 wrote:
I want to copy the contents of one table into another using execute immediate.
This keeps failing with the following error
ORA-00903: invalid table name
ORA-06512: at "TABLE_COPY", line 6
ORA-06512: at line 8
create or replace
procedure TABLE_COPY(
TABLE1 varchar2,
TABLE2 varchar2)
is
begin
execute immediate 'insert into '||TABLE2||' (select * from '||TABLE1||')';
end;
Edited by: user9213000 on 24-Jan-2013 07:38The standard advice when (ab)using EXECUTE IMMEDIATE is to compose the SQL statement in a single VARCHAR2 variable
Then print the variable before passing it to EXECUTE IMMEDIATE.
COPY the statement & PASTE into sqlplus to validate its correctness.

Using EXECUTE IMMEDIATE with an NVARCHAR2 parameter

Hi everyone,
In the system I'm working on, my stored procedure receives an NVARCHAR2 parameter which contains a complete SQL statement. e.g.
'UPDATE SomeTable SET SomeTable.Value = 0'
I want to be able to execute this dynamically, using EXECUTE IMMEDIATE, but I've encountered a problem where this is apparently not supported (because the string is Unicode).
It is crucial that the string stays as Unicode, because of the data that may possible be baked into the SQL statement, and so casting it off to a VARCHAR2, or changing the parameter type, is not acceptable.
Is there a work-around for this issue? Even if it has a performance hit, it will be better than nothing :)
I've tried something like this;
declare
myVal VARCHAR2(256);
begin
myVal := 'UPDATE SomeTable SET SomeTable.Value = 2';
execute immediate 'BEGIN :x; END;' using myVal;
end;
But I get an error;
"bind variable 'X' not allowed in this context"
Has anyone any ideas?
Thanks for your help,
Chris

uhmm, I'm not sure if this is a valid testcase. the string could still be converted into ascii or we8iso8859p1 or whatever 1byte-character set you want.
What I think you should test is a two-byte character as part of SQL, PL/SQL resp. as in SQL all words are defined you can not enlarge it with a 2byte word. But in PL/SQL you could define your own variable. If this variable name itself contains a 2byte character, I guess it will fail.
(I have used l_vär and l_vér as variable names in my example)
Message was edited by:
Leo Mannhart
According to the PL/SQL Reference Guide PL/SQL consists of:
PL/SQL programs are written as lines of text using a specific set of characters:
Upper- and lower-case letters A .. Z and a .. z
Numerals 0 .. 9
Symbols ( ) + - * / < > = ! ~ ^ ; : . ' @ % , " # $ & _ | { } ? [ ]
Tabs, spaces, and carriage returns
This seems no longer up-to-date as I could define a variable l_vär for instance as long as I use a 1byte char set (like iso8859p1). The same variable name as a n-byte char set like UTF-8 will give an error as my example shows.

Create Partition tables in PL/SQL using Execute Immediate

Hi
I have to create a partiton table in PL/SQL using Execute Immediate. I concat the necessary Create Table syntax into a variable and use Execute Immediate variable name. This gives a error ORA-00900: invalid SQL statement. However if i cut and paste the SQL statement from DBMS_OUTPUT, the table creation goes through without any problem.
What could be the issue. Has anyone face this before please.
I am using 10G DB

Thanks for your reply. It is a big code. I am pasting the part required.
v_sqlstmtout :='CREATE TABLE a_10(MYDATE DATE NOT NULL,ID NUMBER(14) NOT NULL)';
v_sqlstmtout := v_sqlstmtout || ' PARTITION BY RANGE (MYDATE) ';
v_sqlstmtout := v_sqlstmtout || 'SUBPARTITION BY HASH(id) ';
v_sqlstmtout := v_sqlstmtout || 'SUBPARTITION TEMPLATE(';
v_sqlstmtout := v_sqlstmtout || 'SUBPARTITION SP1,SUBPARTITION SP2) ';
v_sqlstmtout := v_sqlstmtout || '(PARTITION mth_dummy VALUES LESS THAN ';
v_sqlstmtout := v_sqlstmtout || '('||V_SQLSTMT3||')' || v_sqlstmt||')';
EXECUTE IMMEDIATE ''''||v_sqlstmtout||'''';
variables are substituted through data from different tables.
The output looks like the following
CREATE TABLE a_10(MYDATE DATE NOT NULL,ID NUMBER(14) NOT NULL)
PARTITION BY RANGE (mydate) SUBPARTITION BY HASH(id) SUBPARTITION
TEMPLATE(SUBPARTITION SP1,SUBPARTITION SP2) (PARTITION mth_dummy VALUES
LESS THAN ('01-MAY-2006'), PARTITION mth_JAN2007 VALUES LESS THAN
('01-FEB-2007'))
The above is the output from DBMS_OUTPUT. If i run this statement the table is created. Please help..

Delete From More than 1 table without using execute immediate

Hi,
Am new to PL/SQL, I had been asked to delete few of the table for my ETL jobs in Oracle 10G R2. I have to delete(truncate) few tables and the table names are in another table with a flag to delete it or not. So, when ever I run the job it should check for the flag and for those flag which is 'Y' then for all those tables should be deleted without using the Execute Immediate, because I dont have privilages to use "Execute Immediate" statement.
Can anyone help me in how to do this.
Regards
Senthil

Then tell you DBA's, or better yet their boss, that they need some additional training in how Oracle actually works.
Yes, dynamic sql can be a bad thing when it is used to generate hundreds of identical queries that differ ony in the literals used in predicates, but for something like a set of delte table statements or truncate table statements, dynamic sql is no different in terms of the effect on the shared pool that hard coding the sql statements.
This is a bad use of dynamic sql, because it generates a lot of nearly identical statements due to the lack of bind variables. It is the type of thing your DBA's should, correctly, bring out the lead pipe for.
DECLARE
   l_sql VARCHAR2(4000);
BEGIN
   FOR r in (SELECT account_no FROM accounts_to_delete) LOOP
      l_sql := 'DELETE FROM accounts WHERE account_no = '||r.account_no;
      EXECUTE IMMEDIATE l_sql;
   END LOOP;
END;This will result in one sql statement in the shared pool for every row in accounts_to_delete. Although there is much else wrong with this example, from the bind variable perspective it should be re-written to use bind variables like:
DECLARE
   l_sql VARCHAR2(4000);
   l_acct NUMBER;
BEGIN
   FOR r in (SELECT account_no FROM accounts_to_delete) LOOP
      l_sql := 'DELETE FROM accounts WHERE account_no = :b1';
      EXECUTE IMMEDIATE l_sql USING l_acct;
   END LOOP;
END;However, since you cannot bind object names into sql statements, the difference in terms of the number of statements that end up in the shared pool between this:
DECLARE
   l_sql VARCHAR2(4000);
BEGIN
   FOR r in (SELECT table_name, delete_tab, trunc_tab
             FROM tables_to_delete) LOOP
      IF r.delete_tab = 'Y' THEN
         l_sql := 'DELETE FROM '||r.table_name;
      ELSIF r.trunc_tab = 'Y' THEN
         l_sql := 'TRUNCATE TABLE '||r.table_name;
      ELSE
         l_sql := NULL;
      END IF;
      EXECUTE IMMEDIATE l_sql;
   END LOOP;
END;and something like this:
BEGIN
   DELETE FROM tab1;
   DELETE FROM tab2;
   EXECUTE IMMEDIATE 'TRUNCTE TABLE tab3';
END;or this as a sql script
DELETE FROM tab1;
DELETE FROM tab2;
TRUNCTE TABLE tab3;is absolutley nothing.
Note that if you are truncating some of the tables, and wnat/need to use a stored procedure, you are going to have to use dynamic sql for the truncates anyway since trncate is ddl, and you cannot do ddl in pl/sql wiothout using dynamic sql.
John

How to use Execute Immediate to execute a procedure and return a cursor?

The procedure name is unknown until run time so I have to use Execute immediate to execute the procedure, the procedure return a cursor, but I can't figure out the right syntax to pass the cursor out.
To simplify the issue here, I create two procedures as examples.Assume I have a procedure called XDTest:
     p_cur OUT SYS_REFCURSOR
IS
BEGIN
OPEN p_cur FOR
Select * from dummy_table;
END XDTest;
In another procedure, I want to use Execute Immediate to execute XDTest and obtain the result that return from the cursor into a local cursor so I can process the records:
     p_cur OUT SYS_REFCURSOR
IS
l_cur SYS_REFCURSOR;
BEGIN
execute immediate 'BEGIN XDTest (:1); END;' using OUT l_cur;
END XDTest2;
However, this is not working, I get ORA-03113: end-of-file on communication channel error.
What syntax should I use here?
Cheers

well...
I update the XDTest2 procedure as below but when execute it get exceptions.I think the v_sqlstmt syntax is wrong, but I don't know what meant to be correct, please give some suggestions .
Cheers
-------------------- XDTest procedure --------------------------------------------------
     p_cur OUT SYS_REFCURSOR
--AUTHID CURRENT_USER
IS
BEGIN
OPEN p_cur FOR
Select Table_Name from USER_Tables;
END XDTest;
-------------------- XDTest2 procedure --------------------------------------------------
     p_cur OUT SYS_REFCURSOR
IS
TYPE T1 IS TABLE OF VARCHAR2(4000) INDEX BY BINARY_INTEGER ;
v_sqlstmt varchar2(1000):=null;
v_cursor number;
x_num number;
LN$Lig number := 0 ;
LN$MaxCol number := 0 ;
t T1 ;
v VARCHAR2(4000) ;
userTb User_Tables%ROWTYPE;
l_cur number;
BEGIN
LN$Lig := 0 ;
LN$MaxCol := 1 ;
--OPEN p_cur FOR
--execute immediate 'BEGIN XDTest (:1); END;' using OUT l_cur;
v_cursor:=dbms_sql.open_cursor;
v_sqlstmt:='begin :p_cur:="XDTest"(); END; ';
dbms_sql.parse(v_cursor,v_sqlstmt,DBMS_SQL.NATIVE);
dbms_sql.bind_variable(v_cursor,':p_cur',l_cur);
dbms_output.put_line('1');
-- Define the columns --
dbms_sql.DEFINE_COLUMN(v_cursor, 1, userTb.Table_Name, 30);
x_num:=dbms_sql.execute(v_cursor);
dbms_output.put_line('2');
-- Fetch the rows from the source query --
LOOP
IF dbms_sql.FETCH_ROWS(v_cursor)>0 THEN
-- get column values of the row --
dbms_sql.COLUMN_VALUE(v_cursor, 1,userTb.Table_Name);
dbms_output.put_line(userTb.Table_Name);
ELSE
-- No more rows --
EXIT;
END IF;
END LOOP;
dbms_sql.close_cursor(v_cursor);
END XDTest2;
---------------------- Error when execute ------------------------------------------------
1
BEGIN DevD0DB.XDTest2(:l_cur); END;
ERROR at line 1:
ORA-01007: variable not in select list
ORA-06512: at "SYS.DBMS_SYS_SQL", line 1010
ORA-06512: at "SYS.DBMS_SQL", line 212
ORA-06512: at "DEVD0DB.XDTEST2", line 35
ORA-06512: at line 1
----------------------------------------------------------------------------------------------------

Selecting data from a table using Execute Immediate in 9i

Hi,
I was wondering how I would be able to do a SELECT on a table using EXECUTE IMMEDIATE. When I tried it (with the proc below), I got the following below. Can anyone tell me what I am doing wrong?
Using Scott/Tiger I tried this:
SQL> ed
Wrote file afiedt.buf
1 CREATE OR REPLACE PROCEDURE P2
2 IS
3 v_SQL VARCHAR2(100);
4 BEGIN
5 v_SQL := 'Select * from Emp';
6 EXECUTE IMMEDIATE v_SQL;
7* END;
SQL> /
Procedure created.
SQL> exec p2
PL/SQL procedure successfully completed.
SQL> set serveroutput on
SQL> exec p2
PL/SQL procedure successfully completed.
SQL>
Thanks in advance.
Sincerely,
Nikhil Kulkarni

1 CREATE OR REPLACE PROCEDURE P2
2 IS
3 v_SQL VARCHAR2(100);
erec emp%rowtype;
4 BEGIN
5 v_SQL := 'Select * from Emp';
6 EXECUTE IMMEDIATE v_SQL into erec;
7* END;
SQL> /

Using EXECUTE IMMEDIATE with XML

Database version : 10.2.0.3.0 - 64bi
Hi All,
I have a xml which is stored in a table, xmltype column.
i have target insert tables whose column names and xml nodes are same.
using all_tab_columns table i will generate columns to be passed to xmltable.
all these data i will store in variables and finally pass to xmltable as below
just want to know using execute immediate is good to use in XML?
SQL_STMT := 'insert into '||table_name|| ' ( '||V_COLUMN_NAME||')';
SQL_STMT := SQL_STMT ||' SELECT ' ||V_XTAB_COLUMN_NAME ||
' FROM TO_XML,
XMLTABLE(' ||v_xpath||
'PASSING XML_VALUE
columns ' || V_COLUMNS_DATA_TYPE
||') XTAB
WHERE Seq_NO = ' || P_SEQUENCE_NO ;
EXECUTE IMMEDIATE SQL_STMT ;
Thanks and Regards,
Rubu

1) is it OK? As I stated above, it can be made to work. It would not be my first choice, but then none of us here know the full details as well as you do so maybe there is a compelling reason to use dynamic SQL.
Here is the documentation for [url http://docs.oracle.com/cd/E11882_01/appdev.112/e25519/executeimmediate_statement.htm#LNPLS01317]EXECUTE IMMEDIATE.
Actually now I finally realize your XML resides in table TO_XML so that means you won't be putting the actual XML into the shared pool via an incorrectly written dynamic SQL statement at least. That is what Odie and I were first concerned about with dynamic SQL usage, that the XML would be hard-coded into your SQL_STMT variable. You are simply changing the columns (in 3 locations). With that setup, you have no need for (nor can use) bind variables. The overall issue of dynamic SQL being slightly slower than static SQL still exists as the SQL statement will first have to be parsed and validated.
A larger issue in terms of performance is how 10.2 handles XMLTypes. If the underlying XML is large, XMLTable performance degrades quickly. Options around this are to parse the XML in PL/SQL or to upgrade to some version of 11 and use SECUREFILE BINARY XML as the underlying storage structure for the TO_XML.XML_VALUE column.

Problem when using execute immediate str variable into refcursor var

Similar Messages

Maybe you are looking for