ORA-04092 immediate execution may engage in a trigger - Reset sequence

Similar Questions

• HELP-immediate execution in PL/SQL has received the error ORA-00904: invalid identifier

  What is the problem with the following codes from PL/SQL (actually it comes to Oracle Metalink Note: 313175.1):
  ===========
  declare
  cursor c1 is select * from $ semantic;
  v_statement VARCHAR2 (255);
  v_nc number (10);
  v_nt number (10);
  Start
  immediate execution
  "select count (*) from $ semantics" in v_nc;
  immediate execution
  ' select count (distinct s_table_name) of semantics$ "in v_nt;
  dbms_output.put_line
  ('Edit' | v_nc |) 'columns ' | v_nt | "tables");
  to r1 c1 loop
  v_statement: = 'ALTER TABLE ' | R1.s_owner | '.' || R1.s_table_name;
  v_statement: = v_statement | «change (' |)» R1.s_column_name | ' ';
  v_statement: = v_statement | R1.s_data_type | ' (' | r1.s_char_length;)
  v_statement: = v_statement | ' CHAR))';
  immediately run v_statement;
  end loop;
  dbms_output.put_line ('Done');
  end;
  /
  =====
  Executed once the codes as sysdba against 10gr 2 database, I got this error:
  From build to select columns to change
  Editing columns 4428 35249
  declare
  *
  ERROR on line 1:
  ORA-00904: invalid identifier
  ORA-06512: at line 22
  
  I see nothing wrong with the line of "immediate execution". I appreciate your help!
  
  Thank you.

  Hello
  Try to print the offending instruction using exception, I used small test cases by changing the pl/sql block, you may need to change to respond to all other types of data in this table.

  CREATE TABLE semantics$
  AS
     SELECT USER AS owner,
            table_name,
            data_type AS s_data_type,
            column_name,
            data_length AS s_char_length
     FROM cols
     WHERE table_name = 'MY_OBJECTS';
  
  DECLARE
     CURSOR c1
     IS
        SELECT *
        FROM semantics$;
  
     v_statement   VARCHAR2 (255);
     v_nc          NUMBER (10);
     v_nt          NUMBER (10);
  BEGIN
     EXECUTE IMMEDIATE 'select count(*) from semantics$' INTO v_nc;
  
     EXECUTE IMMEDIATE 'select count(distinct table_name) from semantics$'
        INTO v_nt;
  
     DBMS_OUTPUT.put_line(   'ALTERing '
                          || v_nc
                          || ' columns in '
                          || v_nt
                          || ' tables');
  
     FOR r1 IN c1
     LOOP
        v_statement   := 'ALTER TABLE ' || r1.owner || '.' || r1.table_name;
        v_statement   := v_statement || ' modify (' || r1.column_name || ' ';
        v_statement   :=
           v_statement || r1.s_data_type || '(' || r1.s_char_length;
  
        IF (r1.s_data_type = 'NUMBER')
        THEN
           v_statement   := v_statement || '))';
        ELSE
           v_statement   := v_statement || ' CHAR))';
        END IF;
  
        DBMS_OUTPUT.put_line (v_statement);
  
        -- EXECUTE IMMEDIATE v_statement;
     END LOOP;
  
     DBMS_OUTPUT.put_line ('Done');
  EXCEPTION
     WHEN OTHERS
     THEN
        DBMS_OUTPUT.put_line ('Statement = ' || v_statement);
        DBMS_OUTPUT.put_line (SUBSTR (SQLERRM, 1, 200));
        RAISE;
  END;
  

  _ Output

  ALTERing 13 columns in 1 tables
  ALTER TABLE MY_OBJECTS modify (OWNER VARCHAR2(30 CHAR))
  ALTER TABLE MY_OBJECTS modify (OBJECT_NAME VARCHAR2(30 CHAR))
  ALTER TABLE MY_OBJECTS modify (SUBOBJECT_NAME VARCHAR2(30 CHAR))
  ALTER TABLE MY_OBJECTS modify (OBJECT_ID NUMBER(22))
  ALTER TABLE MY_OBJECTS modify (DATA_OBJECT_ID NUMBER(22))
  ALTER TABLE MY_OBJECTS modify (OBJECT_TYPE VARCHAR2(19 CHAR))
  ALTER TABLE MY_OBJECTS modify (CREATED DATE(7 CHAR))
  ALTER TABLE MY_OBJECTS modify (LAST_DDL_TIME DATE(7 CHAR))
  ALTER TABLE MY_OBJECTS modify (TIMESTAMP VARCHAR2(19 CHAR))
  ALTER TABLE MY_OBJECTS modify (STATUS VARCHAR2(7 CHAR))
  ALTER TABLE MY_OBJECTS modify (TEMPORARY VARCHAR2(1 CHAR))
  ALTER TABLE MY_OBJECTS modify (GENERATED VARCHAR2(1 CHAR))
  ALTER TABLE MY_OBJECTS modify (SECONDARY VARCHAR2(1 CHAR))
  Done
  

  Concerning

  Published by: OrionNet on January 5, 2009 23:53

  Published by: OrionNet on January 5, 2009 23:55

• Changing table via the package with immediate execution (problem)

  Hello

  I have a unusual problem. I have a package that contains the procedure that via execute immediate statement, creates a table on which he performs different actions for example:

  -alter table some_owner.dummy_table noparallel

  -create index some_owner.idx_name on some_owner.dummy_table (column)...

  But I only managed to run move and create synonym table/public via execute immediate statement. Actions as alter table and create index fails with error ORA-01031: insufficient privileges.

  Note If call these commands outside the package (a simple script) this all done OK.

  I found a way, where I set the AUTHID CURRENT_USER command create package statement. In this way all the actions executed OK.

  I wonder why I can't change the table via the package with immediate execution on a table that is in the tablespace "SOME_TABLESPACE" and the title of owner "SOME_OWNER", without putting the AUTHID command on the package.

  There must be a problem why a package cannot change the table which is owned by the user 'SOME_OWNER '.

  All useful responses would be appreciated.

  I have a unusual problem.

  No - you don't have. This question has been answered SEVERAL times on this forum and others.

  But I only managed to run move and create synonym table/public via execute immediate statement. Actions as alter table and create index fails with error ORA-01031: insufficient privileges.

  OK - your username doesn't have privileges to do these operations or only received privileges through roles.

  Roles are DISABLED in named PL/SQL blocks that use of the AUTHOR's rights.

  Note If call these commands outside the package (a simple script) this all done OK.

  I found a way, where I set the AUTHID CURRENT_USER command create package statement. In this way all the actions executed OK.

  Of course - the roles are NOT disabled in named PL/SQL blocks that use the rights of the APPELLANT or in anonymous blocks.

  I wonder why I can't change the table via the package with immediate execution on a table that is in the tablespace "SOME_TABLESPACE" and the title of owner "SOME_OWNER", without putting the AUTHID command on the package.

  Well now you know!

• SQL dynamic immediate execution

  Hi all
  
  We have a table where we keep the query that will be executed and using bind variables.
  
  But im facing some problems when I try to use it in immediate execution.
  
  guess
  
  function validate is
  varaux varchar2 (200);
  Start
  for r1 in (select query,
  using_bind
  from table_1) loop
  run immediately r1.query in varaux using r1.using_bind;
  Return varaux;
  end loop;
  Returns a null value.
  end;
  
  I know that's not the way to do it, but can you give me instructions in the topic...
  
  Thank you
  Bruna
  
  Published by: Bruna on January 4, 2013 03:07

  >
  We have a table where we keep the query that will be executed and using bind variables.

  But im facing some problems when I try to use it in immediate execution.
  >
  No - the problems you are experiencing are because your function uses invalid syntax. The problems have NOTHING to do with 'run immediately '. This works for me and no changes have been made to the dynamic part.

  create or replace function fn_validate return varchar2 is
  varaux varchar2(200);
  begin
  for r1 in (select 'select ename from emp where empno = :1' query,
  7369 using_bind from dual) loop
  execute immediate r1.query into varaux using r1.using_bind;
  return varaux;
  end loop;
  return null;
  end; 
  
  declare
   myVar varchar2(200);
  begin
   myVar := fn_validate();
   dbms_output.put_line(myVar);
  end;
  
  SMITH
  

• How how to escape double match in immediate execution in the trigger

  Hi all
  
  Please inform me what is the error in this procedure.
  I think that the problem in the way to escape double match.
  
  SQL > create or replace procedure P2
  2 is
  3. start
  4 run immediately 'create or replace trigger t2.
  5 |' before insertion '
  6: ' on tb_test'
  7: ' for each row '
  8: ' declare '
  9: ' start '
  * 10 |' immediate execution "create table t1 as select distinct (NVL (soundex (namess),"'NONE "')) test ' *;
  11: ' end; »
  12 end;
  13
  14.
  
  CAUTION: Procedure created with compilation errors.
  
  SQL > show error
  Errors of PROCEDURE P2:
  
  LINE/COL ERROR
  -------- -----------------------------------------------------------------
  10/83 PLS-00103: encountered the symbol "NONE" when expecting one of
  What follows:
  * & = - + ; <>/ is mod remains not return rem
  return < an exponent (*) > <>or! = or ~ = > = < = <>and or
  as like2 like4 likec between using | Member in bulk
  submultiset
  
  SQL >

  Hello

  Try the code below:

  create or replace procedure P2
  is
  Start
  run immediately "create or replace trigger t2 before insertion
  on tb_test
  for each line
  declare
  Start
  run immediately "create table t1 as select distinct (NVL (soundex (account_number),"NONE")) of the test";
  end;';
  end;
  /

• Appeal procedure set up by IMMEDIATE EXECUTION

  SQL> Create table bipul_test (a number(3), b number(2), c number(5), d varchar2(10), status varchar2(10));
  
  Table Created.
  
  SQL> desc bipul_test
   Name                                      Null?    Type
   ----------------------------------------- -------- ----------------------------
   A                                                  NUMBER(3)
   B                                                  NUMBER(2)
   C                                                  NUMBER(5)
   D                                                  VARCHAR2(10)
   STATUS                                             VARCHAR2(10)
  
  
  SQL> insert into bipul_test values(1,1,1,'a', null);
  SQL> insert into bipul_test values(1,1,1,'b', null);
  SQL> insert into bipul_test values(2,1,2,'c', null);
  SQL> insert into bipul_test values(2,2,2,'d', null);
  SQL> insert into bipul_test values(null, null, null, 'x',null);
  SQL> commit;
  
  SQL> select * from bipul_test;
  
           A          B          C D          STATUS
  ---------- ---------- ---------- ---------- ----------
           1          1          1 a          
           1          1          1 b          
           2          1          2 c          
           2          2          2 d
                                   x

  Package: my_package
  Procedure: proc2, proc3
  

  CREATE OR REPLACE PACKAGE SRGUPTA.my_package AS
      -- PROCEDURE proc2;
      PROCEDURE proc2 (status OUT varchar2);
      PROCEDURE proc3 (Proc_name IN VARCHAR2, status IN OUT varchar2);
  END my_package;
  
  /
  
  CREATE OR REPLACE PACKAGE BODY SRGUPTA.my_package
  IS
  -- PROCEDURE proc2
  PROCEDURE proc2(status OUT varchar2)
  AS
  n number(2);
     BEGIN
       update bipul_test set status ='SUCCESS' where A=1;
       commit;
       status:='FAILURE';
  end proc2;
  
  PROCEDURE proc3 (proc_name varchar2, status IN OUT varchar2)
  AS
  x varchar2(100):=null;
     BEGIN
       --EXECUTE IMMEDIATE 'BEGIN '||proc_name||'; END;';
       EXECUTE IMMEDIATE 'BEGIN '||proc_name||'(status); END;';
       
       if status='FAILURE' then
          update bipul_test set status ='FAILURE' where A=2;
          commit;
       end if;
  end proc3;
  END  my_package;
  /

  The Code of the appellant:
  

  set feedback on
  set serveroutput on
  DECLARE status VARCHAR2(100):='';
   begin
  my_package.proc3('my_package.proc2', status);
  end;
  /
  EXIT;

  Without THE normal execution mode param works very well. Above code is an effort through which I tried to capture the value of OUT to the appellant PROC3 param.
  
  PROC3 call PROC2 with immediate execution. Now if PROC2 have a parameter OUT and I want to capture in PROC3, is it possible?
  
  Out of desire to my code:
  

  SQL> select * from bipul_test;
  
           A          B          C D          STATUS
  ---------- ---------- ---------- ---------- ----------
           1          1          1 a          SUCCESS
           1          1          1 b          SUCCESS
           2          1          2 c          FAILURE
           2          2          2 d           FAILURE
                                  x

  Published by: handsome June 3, 2011 06:29

  SQL> Create table bipul_test (a number(3), b number(2), c number(5), d varc
  (10));
  
  Table created.
  
  SQL> insert into bipul_test values(1,1,1,'a', null);
  
  1 row created.
  
  SQL>
  SQL> insert into bipul_test values(1,1,1,'b', null);
  
  1 row created.
  
  SQL> insert into bipul_test values(2,1,2,'c', null);
  
  1 row created.
  
  SQL> insert into bipul_test values(2,2,2,'d', null);
  
  1 row created.
  
  SQL> insert into bipul_test values(null, null, null, 'x',null);
  
  1 row created.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> select * from bipul_test;
  
           A          B          C D          STATUS
  ---------- ---------- ---------- ---------- ----------
           1          1          1 a
           1          1          1 b
           2          1          2 c
           2          2          2 d
                                   x
  

  SQL> CREATE OR REPLACE PACKAGE my_package AS
    2    -- PROCEDURE proc2;
    3    PROCEDURE proc2(status OUT varchar2);
    4    PROCEDURE proc3(Proc_name IN VARCHAR2, status IN OUT varchar2);
    5  END my_package;
    6  /
  
  Package created.
  
  SQL> CREATE OR REPLACE PACKAGE BODY my_package
    2  IS
    3  -- PROCEDURE proc2
    4  PROCEDURE proc2(status OUT varchar2)
    5  AS
    6  n number(2);
    7     BEGIN
    8   update bipul_test set status ='SUCCESS' where A=1;
    9   commit;
   10   status:='FAILURE';
   11  end proc2;
   12
   13  PROCEDURE proc3 (proc_name varchar2, status IN OUT varchar2)
   14  AS
   15  x varchar2(100):=null;
   16     BEGIN
   17   --EXECUTE IMMEDIATE 'BEGIN '||proc_name||'; END;';
   18   EXECUTE IMMEDIATE 'BEGIN '||proc_name||'(:1); END;' USING IN OUT status;
   19
   20   if status='FAILURE' then
   21      update bipul_test set status ='FAILURE' where A=2;
   22      commit;
   23   end if;
   24  end proc3;
   25  END  my_package;
   26  /
  
  Package body created.
  
  SQL> set serverout on
  SQL> DECLARE
    2  status VARCHAR2(100):='';
    3   begin
    4  my_package.proc3('my_package.proc2', status);
    5  dbms_output.put_line(status);
    6  end;
    7  /
  FAILURE
  
  PL/SQL procedure successfully completed.
  
  SQL> 
  

• difference btw dbms_sql.execution and immediate execution

  Hello
  
  IAM using 10g, difference btw immediate.please dbms_sql.execution and execution to tell me.

  797525 wrote:

  IAM using 10g, difference btw immediate.please dbms_sql.execution and execution to tell me.

  SQL all (and all the anonymous PL/SQL blocks) are analyzed by Oracle as a SQL cursors. These cursor structures are stored in the Shared Pool in the SGA (shared memory area which are essentially the "brain" of the database instance).

  Once a cursor was created for a statement SQL, how to use and interface with this SQL cursor on the server (from the point of view of the customer)?

  We use on the client side, a calling interface (or API) that allows our code to interact with this SQL cursor on the server. This interface can be ODBC. Or BDE. Or ADO. Or many other 3-4 letters for database interfaces.

  PL/SQL is also a language of 'customer' from a SQL perspective. Such as Java and c#, the code PL/SQL will be calls to the SQL engine to analyze and create SQL cursors.

  Of course, PL/SQL differs in 2 areas. It runs in the process of the Oracle server. It is the neighbour of the SQL engine.

  For this reason, PL/SQL is much more perfectly integrated with the SQL than Java or c#.

  But even in spite of this integration, you still need an interface in the client (PL/SQL) to interact with the SQL cursor, that you have created. In PL/SQL, there are a number of such interfaces customer.

  There are explicit and implicit cursors. And there are sliders DBMS_SQL and reference. And there are implicit cursors created through immediate enforcement.

  The difference between DBMS_SQL and immediate execution is therefore a difference in customer language interface. The SQL cursor on the server (in the shared Pool) doesn't know what customer interface is used. He cares not.

  Client side, each of these client interfaces to a SQL cursor has a different function. And determines which one to use.

  run immediately , it's fast and easy for dynamic SQL, but it cannot be used to determine the structure (called projection SQL) returned by a cursor to Select . So despite the dynamic SQL code, we must always know the encoding of time, just what this slider will return to consume its production.

  DBMS_SQL to 'describe' the cursor SQL projection. So, we can create a dynamic Select SQL cursor. We can question its interface describe in order to determine the number, names and the data types of the columns returned. It can be removed these column values dynamically and consume the cursor.

  There are therefore a major difference in the two feature sets. Tools for interfacing with the same SQL cursor.

  So the main points to remember are:
  -all SQL liquidation as SQL cursors on the server
  -you have different interfaces in the language of the client to interact with a SQL cursor

  ++

  Your mission as a programmer, if you choose to accept it, is to determine which of these client interfaces is better suited to meet the requirements in your code.

  This message will self-destruct in... 5.4.3 2...

• Update in immediate execution with rownum

  Can I put in an UPDATE by immediate execution that only maximum 10 lines will be updated?
  
  It is:
  

     EXECUTE IMMEDIATE 'UPDATE A_PAZIENTI_ESAMI SET  '||
                      ' NREFERTO      = :1, '|| 
                      ' DATA_REFERTO  = :2, '|| 
                      ' ANNOREFERTO   = :3, '|| 
                      ' DATA_EROGAZ   = :4, '|| 
                      ' STATO_REFERTO = :5, '|| 
                      ' MEDICO_E      = :6  '|| 
                      ' WHERE '|| WHERE_CLAUSE_ESA  
  --
  || ' and rownum <= 10'   -- this is my doubt
  
  --
  
     USING    AP_REFERTOB.NREFERTO,
                      AP_REFERTOB.DATARF, 
                      EXTRACT (YEAR FROM AP_REFERTOB.DATARF) ,
                      AP_REFERTOB.DATAEROGA,
                      STATOREFERTO,
                      AP_REFERTOB.K_MED;
     COMMIT;

  Thanks in advance

  Hello
  your query works very well. It updates only the first 10 rows based on the place where the condition.

  Thank you.

• sql dynamic and immediate execution

  Hello all;
  
  Just curious... Why developers are still using dynamic sql... and run immediately, because I always thought that dynamic sql were negative and the use of immediate execution as well...
  
  or did I miss something...

  I like this white paper on the topic: SQL in PL/SQL
  http://www.Oracle.com/technetwork/database/features/PLSQL/overview/doing-SQL-from-PLSQL-129775.PDF

• Procedure failed with ORA-01403, associated with immediate execution, captured

  This procedure compiles without error. Its purpose is to copy the sequence of one schema to another object. After it failed with ORA-01403, I added exception code of capture (see the comments in the code).

  A few notes:

  1. I started the proceedings with exec copy_sequence ('ADDRESS_SEQ', 'SST', 'TEST1');

  2. the first sql string is built correctly since I can see in the console output:

  Select last_number in the all_sequences where sequence_owner = upper('TSS') and upper('ADDRESS_SEQ') = sequence_name

  I can run this SQL command, and returns a real value;

  Here is the procedure

  SET SERVEROUTPUT ON;

  create or replace procedure copy_sequence (seq VARCHAR2, prod_schema VARCHAR2, VARCHAR2 test_schema)

  as

  Val number (21);

  s_sql varchar2 (200);

  Start

  s_sql: = ' select last_number in the all_sequences where sequence_owner = upper('''|| prod_schema ||'') ') and sequence_name = upper('''||) Seq | " ')';

  -immediate' select last_number in the Vale of all_sequences where sequence_owner = upper('''|| prod_schema ||'') ') and sequence_name = upper('''||) Seq | " ')';

  Dbms_output.put_line ('sql 1 ' | s_sql);

  execute immediate s_sql in val;  ---!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! The code does not work here!

  Dbms_output.put_line ('val' |) Val);

  s_sql: = 'delete the sequence'. test_schema |'. ' || FF.;

  Dbms_output.put_line ('sql 2 ' | s_sql);

  -execution immediate s_sql;

  s_sql: = 'create the sequence'. test_schema |'. ' || Seq |' minvalue maxvalue 1 999999999999999999999 begin by ' | Val | 'increment of 1';

  Dbms_output.put_line ('sql 3 ' | s_sql);

  -execution immediate s_sql;

  -Add the following after procedure thown ORA-01403: no data found

  exception when TOO_MANY_ROWS then DBMS_OUTPUT.put_line ('TOO_MANY_ROWS error');

  When NO_DATA_FOUND then DBMS_OUTPUT.put_line ('error NO_DATA_FOUND');

  While some other then raise_application_error (-20011, "Unknown Exception in this procedure");

  end;

  /

  Hoek wrote:

  The user (no SYSTEM, SYS, and SYSTEM are special, you should not use them unless you have TO) execution of the procedure must have the necessary privileges granted directly, bypassing a role...

  ??? There is nothing special about SYS or SYSTEM in what concerns them stored procedures. SYS by default is granted directly SELECT ANY SEQUENCE, so it does not work for the owner of MS by SYS. SYSTEM is therefore not:

  Scott@pdborcl12 > create sequence s;

  Order of creation.

  Scott@pdborcl12 > create or replace
  2 procedure system.p1
  3 is
  number of v_last_value 4;
  5. start
  6. Select last_number
  7 in v_last_value
  8 of all_sequences
  9 where sequence_owner = 'SCOTT '.
  10 and s = sequence_name ';
  11 end;
  12.

  Created procedure.

  Scott@pdborcl12 > system.p1 exec.
  BEGIN system.p1; END;

  *
  ERROR on line 1:
  ORA-01403: no data found
  ORA-06512: at "SYSTEM. "P1", line 5
  ORA-06512: at line 1

  Scott@pdborcl12 > grant select on s to the system;

  Grant succeeded.

  Scott@pdborcl12 > system.p1 exec.

  PL/SQL procedure successfully completed.

  Scott@pdborcl12 >

  SY.

• ERROR WITH IMMEDIATE EXECUTION (ORA-00936)

  Hello
  
  I am trying to implement this statement but I get this error message (ORA-00936)
  
  RUN IMMEDIATELY 'REMOVE'. V_TABLE_DETAIL_NAME | ' WHERE ' | V_COLUMN_DETAIL_NAME |' = ' | TO_CHAR (P_DEL_VAL);
  
  
  
  Kind regards

  Hello

  I assume you are using below in the database. Try this...

  EXECUTE IMMEDIATE 'DELETE FROM '||V_TABLE_DETAIL_NAME||' WHERE '||V_COLUMN_DETAIL_NAME ||' = '''||TO_CHAR(P_DEL_VAL)||'''';
  

  -Clément

• problem with immediate execution

  Hi all
  I use 10g db.
  I wrote a database procedure. When I call front end (forms 6i) I get the error message

  ORA-00911: invalid character
  ORA-06512:at schema.update_tables line 10

  and here is my procedure

  create or replace procedure update_tables is
  BEGIN
  declare
  lstring varchar(100) := 'update ';
  lvalue varchar2(10) := 'LVM';
  begin
  for i in (select table_name,column_name from user_tab_columns where column_name like '%_COMPANY')
  loop
  lstring := lstring||i.table_name || ' set '||i.column_name || '= ' ||  chr(39) || lvalue || chr(39) || ' ; ' ;
  execute immediate lstring;
  end loop;
  end;
  END;
  /

  What could be gone bad?
  
  Thank you...
  
  Published by: GD on May 19, 2012 21:36

  Is chr (39) a quote on your system?

  Did you try my example or something else?
  (I've tried before, I posted it).

  Here is a complete example.
  I changed it to my previous post to use a variable binding to remove the tank (39).
  It will also help if lvalue contains a quote.

  create table hutest (my_company varchar2(30));
  
  Table created.
  
  insert into hutest values('djhg');
  
  1 row created.
  
  create or replace procedure update_tables is
  BEGIN
  declare
  lstring varchar(100) := 'update ';
  lvalue varchar2(10) := 'LVM';
  begin
  for i in (select table_name,column_name from user_tab_columns where column_name like '%_COMPANY')
  loop
  lstring := lstring||i.table_name || ' set '||i.column_name || '= :val';
  dbms_output.put_line(lstring);
  execute immediate lstring using lvalue;
  end loop;
  end;
  END;
  /
  
  Procedure created.
  
  set serveroutput on size 20000
  
  exec update_tables
  update HUTEST set MY_COMPANY= :val                            <------ From dbms_output
  
  PL/SQL procedure successfully completed.
  
  select * from hutest;
  
  MY_COMPANY
  ------------------------------
  LVM
  
  1 row selected.
  

  Published by: HU 2012-05-20 08:59

• Problem in IMMEDIATE EXECUTION

  I need to update some columns in a table.
  But the columns are dynamic. I can update 1, 20r 3 or more columns of this table.
  
  I tried running with the Execute immediate statement.
  But I get the error message (ORA-01747)
  
  : 1(below in code) contains the name of the column with the values. (Example:Column2 = Column2.value, Column3 = Column3.value)
  There may be more than 3 or more columns to be updated.
  

  CREATE OR REPLACE PROCEDURE PR_Bulk_CA(pn_SSCA_ID_VARRAY          BULK_UPDATE_CA_VARRAY
                                        ,pv_set_string              Varchar2
                                        ,pn_success                 OUT number
                                        )    
                                        Is
   sql_stmt  VARCHAR2(32000);
  
  BEGIN
       
  sql_stmt:= 'update table_A
                 SET :1
             WHERE  ID IN (select ID from table_A ca
                     where  ca.status in (20700,20710,20720)
                       and  ca.id in (select * from table(:2)))';
  
  EXECUTE IMMEDIATE sql_stmt USING pv_set_string,pn_SSCA_ID_VARRAY;                      
  
  COMMIT;
                   
  pn_success:=0;
  
  EXCEPTION
      WHEN OTHERS THEN
  
  pn_success:=-1;
  
  END PR_Bulk_CA;

  You can't pass the name of the column as a bind variable.

  Replace your code (passing only the varray as a bind variable):

  sql_stmt:= 'update table_A
                 SET ' || pv_set_string || '
             WHERE  ID IN (select ID from table_A ca
                     where  ca.status in (20700,20710,20720)
                       and  ca.id in (select * from table(:1)))';
  

  HTH

• Help with IMMEDIATE EXECUTION and drop

  Hi all
  
  We strive to create a procedure to do the following:
  
  * We have in the database of the tables named as C$ _XXXXXXXXX
  * We want to drop some of these tables with a common prefix (Fe C$ _1203101)
  
  DECLARE
  v_sql VARCHAR2 (300);
  BEGIN
  SELECT 'DROP TABLE ODISTAG.' | TABLE_NAME | « ; » IN v_sql FROM USER_TABLES WHERE TABLE_NAME LIKE ' C$ _1203101% ';
  EXECUTE IMMEDIATE v_sql;
  END;
  
  But we are getting this error:
  
  
  Error report:
  ORA-00911: invalid character
  ORA-06512: at line 5
  00911 00000 - "invalid character".
  * Cause: identifiers may not start with any character other than ASCII
  letters and numbers. $# _ are allowed after the first
  character. May contain identifiers surrounded by doublequotes
  any character other than a quotation mark. Other quotes
  (q' #... #') cannot use spaces, tabs or as carriage returns
  delimiters. For all other settings, consult the SQL language
  Reference manual.
  * Action:
  
  
  Any help on this please?
  
  Thank you!

  You don't need the semicolon.

• immediate execution

  Hello, I'm on 11.2.0.4, and I'm trying to write a procedure with parameter that runs immediately a DDL.

  How can I write this while I'm on the parameter which will always be 0?

  SYS@db1 AS SYSDBA > create or replace procedure set_rm_tws (o_status NUMBER)

  as

  Start

  o_status: = 0;

  run immediately ' alter system set resource_manager_plan = "DEFAULT_PLAN" scope = "both"' using o_status;

  end;

  /

  Created procedure.

  SYS@db1 AS SYSDBA > var o_status number

  SYS@db1 AS SYSDBA > exec set_rm_tws(:o_status);

  BEGIN set_rm_tws(:o_status); END;

  *

  ERROR on line 1:

  ORA-00922: missing or not valid option

  ORA-06512: at "SYS." SET_RM_TWS', line 5

  ORA-06512: at line 1

  Hello Vili Dialis

  You will get all the information of the execution. What you get is simple no and not an exception.

  create or replace procedure set_rm_tws (o_status NUMBER)

  as

  Start

  o_status: = 0;

  run immediately ' alter system set resource_manager_plan = "DEFAULT_PLAN" scope = "both"' using o_status;

  EXCEPTION, THEN THAN OTHERS

  THEN o_status: = 1;

  END;

  /

  If you have a problem with running so that you can get the 1 in the variable o_status.

  The help of the o_status should be deleted.

  I hope it helps.

  Best regards, David