Problems using DDL & EXECUTE IMMEDIATE in package

Hi...
I have an 8i package in which I am trying to execute some DDL via EXECUTE IMMEDIATE to create temporary tables from which I then populate a REF_CURSOR by selecting from the last table created in the DDL. The problem is that the compiler doesn't seem to like the DDL.
Here's what I'm using:
CREATE OR REPLACE PACKAGE BODY NEREP_REF
AS
Procedure GetNE_REF (
i_Node IN VARCHAR2,
io_cursor IN OUT t_cursor )
IS
sql_stmt varchar2(200);
v_cursor t_cursor;
BEGIN
sql_stmt := 'CREATE TABLE tmp AS SELECT * FROM nerep4;';
EXECUTE IMMEDIATE sql_stmt;
OPEN v_cursor FOR
SELECT NE_Node, NE_Type, EHA, Status, Curr_Func, TP_Name,
Order_Item_Name, Required_Start, Required_End, Trail_Name
FROM tmp
WHERE NE_Node = i_Node ;
io_cursor := v_cursor;
END GetNE_REF;
END NEREP_REF;
The problem is that when I compile the package I get the errors below:
SQL> @sp_nerep_body
Warning: Package Body created with compilation errors.
SQL> show err
Errors for PACKAGE BODY NEREP_REF:
LINE/COL ERROR
20/7 PL/SQL: SQL Statement ignored
23/14 PLS-00201: identifier 'NE_NODE' must be declared
So it seems that it doesn't like the DDL (have I got the sql_stmt assignment in the wrong place maybe?) and then it complains it can't find the columns, which is reasonable because of course it doesn't know that the table 'tmp' comes from the result of the DDL statement!
If I change the table name in the 'OPEN v_cursor FOR' select clause to a table that already exists (ie: not created in this package) it runs just fine and I get the data I asked for... the problem is that I need to create this table on the fly by using DDL in my package!
This is driving me crazy - basically I need to be able to execute DDL to do various 'create table ... as select ... from ...' statements which eventually builds a final table which I then want to populate using a REF_CURSOR so I can return the results back to ASP via ADO... but I just can't get the DDL bit to work no matter what I try!!
Can anyone see what I'm doing wrong here?
Mike.
null

Here are a some ideas to try:
Remove the extra semicolon from your sql_stmt, so that line reads:
sql_stmt := 'CREATE TABLE tmp AS SELECT * FROM nerep4';
Ensure that you have proper privileges as an individual user, not just through a role, by:
connecting to the database using username system and password manager and granting yourself the proper privileges. For example, if you are user SCOTT, then:
SQL> GRANT CREATE TABLE TO SCOTT;
Then, exit and connect as yourself and try to compile and execute your procedure again.
If that still doesn't work, try testing one little piece at a time until you can identify the part that causes trouble. For example, start with a procedure that does nothing but try to create the tmp table using execute immediate, then add the other pieces, then try to put the procedure in a package.

Similar Messages

Unplanned Use Of EXECUTE IMMEDIATE

Hi Gurus,
I have joined a new project in my company. I have seen that there are lot of use of EXECUTE IMMEDIATE in the coding. But these use of EXECUTE IMMEDIATE is totally unnecessary. For Example
INSERT INTO table_name SELECT column1,column2 FROM table_name2is written as
EXECUTE IMMEDIATE 'INSERT INTO table_name SELECT column1,column2 FROM table_name2'May be
SELECT 'X' INTO myvar FROM DUALis written as
EXECUTE IMMEDIATE 'SELECT 'X' FROM DUAL' INTO myvarI have a serious allergy with this type of coding. But I need some good points and reference from authenticate source (Oracle Documentation/Articles/White paper etc) to convince others.
So please post your valuable comments!.

You can also argument that the dynamic version is a little slower. In fact this does not make any real difference performancewise. But still each little be may count. ;)
Here is a test case:
09:28:54 SQL> set time on
09:28:55 SQL> set timing on
09:28:57 SQL> declare
09:28:58   2    myVar pls_integer;
09:28:58   3 begin
09:28:58   4     for i in 1..1000000 loop
09:28:58   5        execute immediate('select count(*) from dual') into myVar;
09:28:58   6     end loop;
09:28:58   7 end;
09:28:58   8 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:27.02
09:29:25 SQL>
09:29:25 SQL> declare
09:29:25   2    myVar pls_integer;
09:29:25   3 begin
09:29:25   4     for i in 1..1000000 loop
09:29:25   5        select count(*) into myVar from dual;
09:29:25   6     end loop;
09:29:25   7 end;
09:29:25   8 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:26.24
09:29:51 SQL> As you can see the difference is marginal (3% faster). But still there is a slight difference.

How to pass a sequence by 'using' for execute immediate

how i can pass a sequence.nxlval as a parameter through using , here is my code looks like
sql_string is -> insert into some_tab (col1,col2, ....) (select col1,:passed_seq,......) where .... (i want to insert sequence values for col2)
and i am calling this as
passed_seq := 'seq_'||some_dynamic_num||'.nextval' ( in my db there will be sequences with the formed string like seq_10.nextval)
EXECUTE IMMEDIATE sql_string using passes_seq;
if i am doing like this i am getting
Error : -1722:ORA-01722: invalid number seq_10.nextval
Edited by: DIVI on Jan 8, 2013 7:40 AM

Hi,
I hope you have created sequence as below
SQL>
SQL> CREATE SEQUENCE seq
2 MINVALUE 1
3 START WITH     1
4 INCREMENT BY   1
5 NOCACHE
6 NOCYCLE;
Sequence created.
SQL>
SQL> SELECT * FROM TEST1;
     EMPNO EMPTYPE              EMP_ADDRESS              SALARY     DEPTNO
         1 HR                   MUMBAI                    10000         10
         2 ADMIN                THANE                      6000         20
SQL>
SQL> INSERT INTO TEST1 (EMPNO)
2 VALUES(SEQ.NEXTVAL);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT * fROM TEST1;
     EMPNO EMPTYPE              EMP_ADDRESS              SALARY     DEPTNO
         1 HR                   MUMBAI                    10000         10
         2 ADMIN                THANE                      6000         20
         1
SQL>Now if you need to add different numbe in differenct condition then create multiple sequence and use them accounding.

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.

Execute immediate on DDL command

Below sample SQL is 1 of the many code that is running OK in our database. And this code has causes a lot of latch contention to our database and it's being called so many times that cause hard parse.
/* test code */
CREATE OR REPLACE PROCEDURE dsal (p_client_id NUMBER) IS
BEGIN
EXECUTE IMMEDIATE
'create table tmp_dsal_'||p_client_id
' (client_id number, '||
' trade_id number, '||
' ps_id number, '||
' ps_liquid varchar2(2), '||
' status_code varchar2(3) default ''NA'' not null, '||
' start_value_dte date, '||
' end_value_dte date)';
EXECUTE IMMEDIATE 'drop table tmp_dsal_'||p_client_id;
END;
I want to improve it by using bind variable. The below program compile with no error.
CREATE OR REPLACE PROCEDURE dsal (p_client_id NUMBER) IS
BEGIN
EXECUTE IMMEDIATE
'create table tmp_dsal_:client_id'||
' (client_id number, '||
' trade_id number, '||
' ps_id number, '||
' ps_liquid varchar2(2), '||
' status_code varchar2(3) default ''NA'' not null, '||
' start_value_dte date, '||
' end_value_dte date)' using p_client_id;
EXECUTE IMMEDIATE 'drop table tmp_dsal_:client_id' using p_client_id;
END;
When I execute it, I'm getting the below error. I understand DML statement using bind variable in execute immediate command but not sure on DDL. Is there a workaround on issue or this is limitation?
SQL> exec dsal(223);
BEGIN dsal(223); END;
ERROR at line 1:
ORA-00922: missing or invalid option
ORA-06512: at "SYS.DSAL", line 3
ORA-06512: at line 1
Appreciate any comment/help. Thanks

Assuming that all of the client load processes run in seperate session, then do this once in the database and use this global temporary table for the loads. A GTT is a permanent object in the database, but the data it contains is only visible to the session that inserts it. Multiple sessions can access the same GTT at the same time, and will never see each other's data.
CREATE TEMPORARY TABLE tmp_dsal (
   client_id       NUMBER,
   trade_id        NUMBER,
   ps_id           NUMBER,
   ps_liquid       VARCHAR2(2),
   status_code     VARCHAR2(3) DEFAULT 'NA' NOT NULL,
   start_value_dte DATE,
   end_value_dte   DATE)
ON COMMIT [PRESERVE|DELETE] ROWSThe on commit clause determines what happens to the data in the GTT when the session that created the data issues a commit. DELETE will automaticall delete all of that session's data while PRESERVE will keep the data until the session either explicitly deletes it or the session ends.
John

Dynamic USING clause in execute immediate

Hi All,
Is it possible to build a dynamic using clause in execute immediate command.
EXECUTE IMMEDIATE <dynamic query> USING <dynamic clause>;
Rgrds,
Nitin.

Hi,
The problem is I have a query in which in some scenarios I want just one column in where clause, in other scenario I need 2 columns in the where clause.
So I would have to write 2 different queries.
execute immediate 'SELECT 1 FROM DUAL WHERE 1 = :bind1' into a using 1;
execute immediate 'SELECT 1 FROM DUAL WHERE 1 = :bind1 AND 2 = :bind2' into a using 1, 2;
Is there any way I can achieve this in a single query like:
dynamic_using_str varchar2(100);
dynamic_using_str := '1';
execute immediate 'SELECT 1 FROM DUAL WHERE 1 = :bind1' into a using dynamic_using_str;
dynamic_using_str := '1, 2';
execute immediate 'SELECT 1 FROM DUAL WHERE 1 = :bind1 AND 2 = :bind2' into a using dynamic_using_str;
~Nitin.
Edited by: user13060845 on Apr 30, 2010 12:29 PM

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

Using EXECUTE IMMEDIATE with Create Table SQL Statement not working

Hi ,
I am all the privileges given from the SYSTEM user , but still i am not able to create a table under procedure . Please see these and advice.
create or replace procedure sp_dummy as
begin
Execute Immediate 'Create table Dummy99_99 (Dummy_Field number)';
end;
even i tried this way also
create or replace PROCEDURE clearing_Practise(p_file_id in varchar2, p_country in VARCHAR2,p_mapId in VARCHAR2)
AUTHID CURRENT_USER AS
strStatusCode VARCHAR2(6);
BEGIN
EXECUTE IMMEDIATE 'create table bonus(name varchar2(50))';
commit;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('ERROR Creating Table');
END ;

William Robertson wrote:
Since the syntax is correct, my guess is you do not have CREATE TABLE system privilege granted directly to your account. A common scenario is that you have this privilege granted indirectly via a role, allowing you to create tables on the command line, but stored PL/SQL is stricter and requires a direct grant and therefore the procedure fails with 'insufficient privileges'.A bit like he's already been told on his first thread...
Using of Execute Immediate in Oracle PLSQL
Generally you would not create tables from stored PL/SQL. Also as you have found out, it's best not to hide exceptions with 'WHEN OTHERS THEN [some message which gives less detail than the one generated by Oracle]'.Again like he was told on the other thread.
There's just no telling some people eh! :)

Create a script to create multiple objects without using execute immediate.

I have a function that requires several objects (4 types, 8 functions) to run. Right now they're in separate sql files. I'd like to combine them into one file that I would run but I'd rather not use the 'execute immediate' since it seems like you have to escape quotes and the like.
How would you do that?
Thanks in advance,
J

Yeah I thought about that but I'd like them all to be in one file.
I believe I figured it out though. (about 20m after I posted no less)
Adding a '/' on it's own line after each block of code appears to do the trick. I just have to write a bit of code to drop a dependent type if it exists.
J

Using Execute Immediate in Forms9i (9.0.2.9.0)

Hi People,
I'm having trouble using the EXECUTE IMMEDIATE option from within a trigger in Forms 9i. Trigger compilation results in the error, "this feature is not supported in client-side programs". The Forms version is 9.0.2.9.0, The PL/SQL version is 9.0.1.3.1. Anyone come across this problme before and possible solutions (besides forms_ddl)
I'll continue to search further within this forum, hopefully i can get to the bottom of this. Cheers

You can use EXECUTE_IMMEDIATE only on server - stored procedure etc.
So you can call such stored procedure from Forms trigger.
I hope this will help you.

Creating cursor using Execute immediate

I am trying to create one cursor using a for loop, but I am not able to do so, could you please help me with the approach to get it done.
Here is the scenario:
I have one table table_1,it contains 2 columns source_query , target_query.
source_query and target_query are Select statements like source_query is Select name, age , valid from customer where customer_id=123456;
I fetched the data from these columns into 2 strings
select source_query into source_data from table_1;
select target_query into target_data from table_1;
Now out of these 2 I want to create 2 cursors, so that I can compare the column values one by one ( I am not using the source minus target approach because of difference in the data type).
I have to individually check the values.
So here are the cursors:
For source_data_value in ( EXECUTE immediate source_data)
LOOP
For target_data_value in (EXECUTE IMMEDIATE target_data)
LOOP
<executable statements>;
END LOOP;
END LOOP;
But the cursor creation is failing in the procedure.
Please let me know if it is possible to create a cursor using the execute immediate , if not what approach I should use other than this?

Why exactly you are doing this inside a procedure. You can take the SQL's out and write a simple query to retrieve the data. Anyways, to work it out in a procedure, I can think of the below solution. I am trying to do away with Execute Immediate and use REF cursor. Please note that this is untested and just a try to present a possible solution which can be changed to implement your original requirement. I haven't done anything sort of this before, so if this approach doesn't approach, kindly ignore
DECLARE
   TYPE TempTyp IS REF CURSOR;
   temp_cv   TempTyp;
temp_cv_2 Temptyp;
   emp_rec emp%ROWTYPE;
   source_data VARCHAR2(200);
     target_data VARCHAR2(200);
   BEGIN
   source_data:= 'SELECT * FROM source tablej';
   target_Date :='select * from target table';
   OPEN temp_cv FOR source_data;
   LOOP
      FETCH temp_cv INTO emp_rec;
      EXIT WHEN emp_cv%NOTFOUND;
        OPEN   temp_cv_2 FOR target_data;
          FETCH Temp_cv_2 into emp_rec emp%ROWTYPE
               loop
                    < And then your comparisons here >
     END LOOP:
     CLOST TEMP_CV_2;
   END LOOP;
   CLOSE temp_cv;
END;
Ishan

Execute immediate and dynamic sql

Dear all;
Just curious....Why do developers still use dynamic sql..and execute immediate, because I always thought dynamic sql were bads and the use of execute immediate as well...
or am I missing something...

There are no 'bad' things and 'good' things.
There are 'correctly used' and 'incorrectly used' features.
It depends what you want to do.
One simple example: Oracle 11.2 - you write a package that fetches data from range interval partitioned table (a new partition is created automatically every day when new key values are inserted). If you use static SQL then whenever Oracle creates a new partition then your package gets invalidated and has to be compiled. If your package is heavily used (by many sessions running in parallel) then you may get this:
ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package body "PACKAGE.XXXXX" has been invalidated
ORA-06508: PL/SQL: could not find program unit being called: "PACKAGE.XXXXX" Nice, isn't it?
You can avoid this kind of problems by simply using dynamic SQL. You break dependency with the table and your package is not invalidated when new partition is created.

Execute Immediate in Oracle 10g

Hi , I have a small doubt regarding execute immediate.
As per my knowledge we use execute immediate for writing DDL(create,truncate,...) statements to execute in the procedure or function.
But i have seen in my organization , some of the senior people(already left organization) used to write inserts , updates , deletes also in execute immediate even there is not much dynamic logic involved.
But as per my knowledge execute immediate can be badly used by most of the hackers with SQL injection I guess!!!!!
Is there any reason that they use execute immediate instead of writing the code directly??? Or is there any advantage in writing like this.???

Using execute immediate to create tables and other DDL is fundamentally undesirable, and should be avoided at all cost.
The use of execute immediate you seem to outline, should be avoided too. Apparently those seniors were unaware of the goal of PL/SQL and the disadvantage of execute immediate.
If I could vote to remove execute immediate from PL/SQL, I would be immediately in favor, especially in packages, procedures and functions,as they are stored, which means pre-compiled.
Sybrand Bakker
Senior Oracle DBA

Developer 6.0 doesn't like EXECUTE IMMEDIATE

I am trying to use the EXECUTE IMMEDIATE command in a WHEN-NEW-RECORD-INSTANCE trigger. However, no matter what I do, I get the following error when I try to compile the trigger:
Encountered the symbol "IMMEDIATE" when expecting one of the following:
:= . ( @ % ;
The symbol ":= was inserted before "IMMEDIATE" to continue.
My syntax looks good--I don't know what the problem is

EXECUTE IMMEDIATE , the native dynamic SQL is a feature available only from pl/sql version 8.1.5 . But forms6i is still using pl/sql engin 8.0.6. SO you can create stored procedures ( because Oracle 8i - pl/sql version -8.1.5) and call it in your forms.

How to set multiple parameters in one EXECUTE IMMEDIATE sql

I want to set both nls_language and nls_date_language, and set them as different languages. fnd_global.set_nls_context() doesn't work. So I think maybe I can use the EXECUTE IMMEDIATE, and add them together into one statement. But I don't know how to make that happen. Can anybody help me? Thanks very much.
PS: It has to be done in one call.

928091 wrote:
Hey, thanks for your answer, I forgot to mention that it has to be in begin-end block, do you know how?EXEC is a SQL Plus API that can be used to run PL/SQL code. What it does is put the PL/SQL code in a BEGIN .. END block and run it.
So you can also manually put the code in a BEGIN..END block and run like this.
SQL> begin
2     execute immediate q'[begin execute immediate 'alter session set nls_date_language = ''AMERICAN'''; execute immediate 'alter session set nls_language = ''AMERICAN'''; end;]';
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> And i dont understand what possible benefit does it makes to do a single execution into a BEGIN..END over multiple execution.
Why this code is not of your interest, something like this
begin
     execute immediate 'alter session set nls_date_language = ''AMERICAN''';
     execute immediate 'alter session set nls_language = ''AMERICAN''';
end;
/

Problems using DDL & EXECUTE IMMEDIATE in package

Similar Messages

Maybe you are looking for