Break the dynamic SQL

All,

I try to print after statement in two lines

MY NAME IS XYZ;
GOT IT;

I'm trying yo use code similar to the one below, but it keeps me gives error

select 'MY NAME IS XYZ;
         GOT IT'
from dual;

How can I reach above in sqlplus itself?

Hello

When I try in SQL * Plus, it looks like SQL * Plus is to make an analysis and interprets them. at the end of a line as the end of a statement.
Try to hide the semicolon within the line, like this:

select 'MY NAME IS XYZ;' || '
         GOT IT'            AS txt
from dual;

Output:

TXT
-------------------------------
MY NAME IS XYZ;
         GOT IT

Otherwise, SQL * more seems to do this kind of analysis before it resolves the substitution variables, then the following also works:

DEFINE sym = ";"

select 'MY NAME IS XYZ&sym
         GOT IT'            AS txt
from dual;

Tags: Database

Similar Questions

using the dynamic SQL syntax
I am trying to create a dynamic sql to execute the following statement:

create the table mytbl_20100901 in select * from matbl double;

When I try the following error I
ORA-06550: line 6, column 10:
PLS-00103: encountered the symbol "SELECT" at the expected in the following way:

;;;;;;;;;;;;;;;;;;;;;;;;;;;
declare
sql_cmd varchar2 (1000);

Start

sql_cmd: = select "create table mytbl_ | To_char (sysdate, 'YYYYMMDD') | ' in select * from matbl ' double.

immediately run sql_cmd;

end;
;;;;;;;;;;;;;;;;;;;;;;;;;

How to fix the sql_cmd assignment statement?

Thank you.
Hello

user1035690 wrote:
I am trying to create a dynamic sql to execute the following statement:

create the table mytbl_20100901 in select * from matbl double;

When I try the following error I
ORA-06550: line 6, column 10:
PLS-00103: encountered the symbol "SELECT" at the expected in the following way:

;;;;;;;;;;;;;;;;;;;;;;;;;;;
declare
sql_cmd varchar2 (1000);

Start

sql_cmd: = select "create table mytbl_ | To_char (sysdate, 'YYYYMMDD') | ' in select * from matbl ' double.

immediately run sql_cmd;

end;
;;;;;;;;;;;;;;;;;;;;;;;;;

How to fix the sql_cmd assignment statement?

Thank you.

The dual table is not necessary a lot in PL/SQL.
You can simply say:
```
sql_cmd := 'create table mytbl_' || TO_CHAR(sysdate, 'YYYYMMDD') || ' as select * from mytbl';
dbms_output.put_line (sql_cmd || ' <= sql_cmd');
-- EXECUTE IMMEDIATE sql_cmd;
```
During the development of the dynamic SQL statements, I suggest that you post the command rather than run it first.
When it seems correct, then a comment instructions EXECUTE IMMEDIATE.
Before the Production code, remove or comment the call to out_line.

Retrieve and display a result set using the dynamic sql?
Hi all

How would display a result set in Oracle using the dynamic SQL? Reason being, the table where I'd retrieve and display the result set is a GLOBAL TEMP TABLE created in a stored procedure. If I try to use the loop as usual, the compiler complains that the table does not exist. This makes sense because the compiler does not recognize the table because it is created dynamically. Here is an example:

create or replace PROCEDURE maketemptab IS
sql_stmt VARCHAR2 (500);
OutputString VARCHAR2 (50);

BEGIN
-create temporary table
sql_stmt: = ' CREATE of TABLE TEMPORARY GLOBAL globtemptab (id NUMBER, col1 VARCHAR2 (50))';
EXECUTE IMMEDIATE sql_stmt;
dbms_output.put_line ('... created table ');

-Insert a row into the temporary table
sql_stmt: = "INSERT INTO globtemptab values (1, 'some data of a test')';"
EXECUTE IMMEDIATE sql_stmt;
dbms_output.put_line ('... inserted row ');

-Insert a row into the temporary table
sql_stmt: = ' INSERT INTO globtemptab values (2, "some more test data");
EXECUTE IMMEDIATE sql_stmt;
dbms_output.put_line ('... inserted row ');

-Select the row on temporary table
sql_stmt: = 'SELECT col1 FROM globtemptab WHERE id = 1';
EXECUTE IMMEDIATE sql_stmt INTO outputstring;
dbms_output.put_line ('... selected line: ' | outputstring);

-drop temporary table
sql_stmt: = 'DROP TABLE globtemptab;
EXECUTE IMMEDIATE sql_stmt;
dbms_output.put_line ('... moved table ');

-display the result set
for tabdata loop (select col1 from globtemptab)
dbms_output.put_line ('... test of recovered data are' | tabdata.col1)
end loop;
end;

In short, how to rewrite the SQL below the comment "to display the result set" using the dynamic sql?

Thank you
Amedeo.
Hello

Try this:
```
CREATE OR REPLACE PROCEDURE maketemptab IS
   sql_stmt     VARCHAR2(500);
   outputstring VARCHAR2(50);
   v_cursor     SYS_REFCURSOR;
   v_col1       VARCHAR2(30);
BEGIN
   -- create temp table
   sql_stmt := 'CREATE GLOBAL TEMPORARY TABLE globtemptab(id NUMBER, col1 VARCHAR2(50))';
   EXECUTE IMMEDIATE sql_stmt;
   dbms_output.put_line('...table created');

   -- insert row into temp table
   sql_stmt := 'INSERT INTO globtemptab values (1, ''some test data'')';
   EXECUTE IMMEDIATE sql_stmt;
   dbms_output.put_line('...row inserted');

   -- insert row into temp table
   sql_stmt := 'INSERT INTO globtemptab values (2, ''some more test data'')';
   EXECUTE IMMEDIATE sql_stmt;
   dbms_output.put_line('...row inserted');

   -- select row from temp table
   sql_stmt := 'SELECT col1 FROM globtemptab WHERE id=1';
   EXECUTE IMMEDIATE sql_stmt
      INTO outputstring;
   dbms_output.put_line('...row selected: ' || outputstring);

   OPEN v_cursor FOR 'SELECT col1 FROM globtemptab';

   LOOP
      FETCH v_cursor
         INTO v_col1;
      EXIT WHEN v_cursor%NOTFOUND;
      dbms_output.put_line('...test data retrieved is' || v_col1);
   END LOOP;
   CLOSE v_cursor;

   -- drop temp table
   sql_stmt := 'DROP TABLE globtemptab';
   EXECUTE IMMEDIATE sql_stmt;
   dbms_output.put_line('...table dropped');
END;
/
```
Kind regards

How to pass the Record of entry to the dynamic SQL Code

Hi all
I am trying to run under Oracle applications API on the remote database using DB Link. I try to run using dynamic SQL. Part of the code is given below.
DECLARE
l_batch_info_rec wsh_picking_batches_pub.batch_info_rec;
l_rule_id NUMBER;
l_rule_name VARCHAR2 (240);
l_batch_prefix VARCHAR2 (240);
BEGIN
l_batch_info_rec.document_set_id: = v_document_set_id;
l_batch_info_rec.order_type_id: = v_order_type_id;
l_batch_info_rec. Default_Stage_Subinventory: = v_default_stage_subinventory;
l_batch_info_rec.pick_grouping_rule_id: = v_pick_grouping_rule_id;
l_batch_info_rec.pick_sequence_rule_id: = v_pick_sequence_rule_id;
l_batch_info_rec.autopack_level: = v_autopack_level;
l_batch_info_rec.autopack_flag: = v_autopack_flag;
l_batch_info_rec.ac_delivery_criteria: = v_ac_delivery_criteria;
l_batch_info_rec.backorders_only_flag: = v_backorders_only_flag;
l_batch_info_rec.existing_rsvs_only_flag: = v_existing_rsvs_only_flag;
l_batch_info_rec.customer_id: = v_customer_id;
l_batch_info_rec.order_header_id: = v_header_id;
l_batch_info_rec.from_scheduled_ship_date: = NULL;
l_batch_info_rec.organization_id: = v_organization_id;
l_batch_info_rec.include_planned_lines: = v_include_planned_lines;
l_batch_info_rec.autocreate_delivery_flag: = v_autocreate_deliveries_flag;
l_batch_info_rec.autodetail_pr_flag: = v_autodetail_pr_flag;
l_batch_info_rec.allocation_method: = 'I ';
l_batch_info_rec.pick_from_locator_id: = NULL;
l_batch_info_rec.auto_pick_confirm_flag: = 'n';         -The value manually to run Transact order
l_batch_info_rec.autopack_flag: = 'n';         -Manually configure to perform the manual packaging
l_rule_id: = NULL;
l_rule_name: = NULL;
l_batch_prefix: = NULL;
v_sqlstmt1: = ' START
wsh_picking_batches_pub.create_batch' | g_db_link | "(1.0,
fnd_api.g_true,
fnd_api.g_true,
: l_return_status,.
: l_msg_count,.
: l_msg_data,.
: l_rule_id,.
: l_rule_name,.
: l_batch_info_rec,.
: l_batch_prefix,.
: p_new_batch_id
);
END;';
--
EXECUTE IMMEDIATE V_sqlstmt1
With the HELP OF THE l_return_status,.
ON l_msg_count,.
ON l_msg_data,.
BY l_rule_id,
BY l_rule_name,
BY l_batch_info_rec,
BY l_batch_prefix,
OUT p_new_batch_id;
--
END;
After you run this script, I get below error "PLS-00457: expressions must be SQL types ' for variable l_batch_info_rec which is of type record. can someone please guide me how can I pass variable type dynamic SQL record.
Thank you
Priyanka

Food for thought:

On remote db:

SQL > create or replace
package 2 pkg
3 is
4 type r_type is (record
Number 5,
6 name varchar2 (10)
7                            );
(p) 8 procedure
9 p_rec in r_type,
10 p_out out varchar2
11                  );
12 end;
13.

Package created.

SQL > create or replace
package 2 body pkg
3 is
4 procedure p)
5 p_rec in r_type,
6 p_out out varchar2
7                  )
8 is
9 start
10 p_out: = "ID = ' |" p_rec.ID | 'Name =' | p_rec. Name;
11 end;
12 end;
13.

Package body created.

SQL >

On local db:

SQL > set serveroutput on
SQL > declare
v_rec 2 pkg.r_type@pdb1sol12;
3 v_out varchar2 (50);
4 start
v_rec.ID 5: = 1;
6 v_rec.name: = 'XXX ';
7 immediate execution"
8                        begin
9 pkg.p@pdb1sol12 (: 1,: 2);
10                        end;'
11 using v_rec,
12 v_out;
13 dbms_output.put_line (v_out);
14 end;
15.
using v_rec;
*
ERROR on line 11:
ORA-06550: line 11, column 20:
PLS-00457: expressions must be SQL types
ORA-06550: line 7, column 5:
PL/SQL: Statement ignored

SQL > declare
2 number of v_id: = 1;
3 v_name varchar2 (10): = 'XXX ';
4 v_out varchar2 (50);
5. start
6 immediate execution"
7 report
8 v_rec pkg.r_type@pdb1sol12.
9                        begin
10                            v_rec.id := :1;
11 v_rec.name: =: 2;
12 pkg.p@pdb1sol12 (v_rec,: 3);
13                        end;'
14 using v_id,
15 in v_name,
16 v_out;
17 dbms_output.put_line (v_out);
18 end;
19.
ID = 1 name = XXX

PL/SQL procedure successfully completed.

SQL >

SY.

Dynamic recovery for the dynamic sql query
Hi all

I want to create a query dynamically and to fetch it in a dynamic cursor record... The structure of the record should be the same as that of the query...
Can you suggest any method to do this.

for example

OPEN < dynamic news > TO < dynamic stmt >;
LOOP
FETCH < dynamic news > < DYNAMIC rec >;
---
END LOOP;
CLOSE < dynamic news >;

How to declare the rec here dynamic? I wouldn't have the columns in the query in advance either.

Thank you
Merz

Published by: merz Sep 12, 2011 17:02

Published by: merz Sep 12, 2011 17:03
Merz says:

How to declare the rec here dynamic? I wouldn't have the columns in the query in advance either.

Is not possible. What you describe is called four dynamic sql type. For this type of synamic SQL, you use the DBMS_SQL package.

SY.

execute the dynamic sql statement

Hi all

CREATE TABLE  XX_OFFICE_USER_IMP 
  (
    ID              NUMBER,
    OFFICE          VARCHAR2(10 BYTE),
    USER_NAME       VARCHAR2(10 BYTE),
    BANK_ACCOUNT_ID NUMBER,
    TRANSFERED      NUMBER
  )

Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (421,'0000','F0000',10029,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (422,'0000','F0000',10031,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (423,'0000','F0000',10033,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (424,'0000','F0000',10036,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (425,'0000','F0000',10037,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (426,'0000','F0000',10039,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (427,'0000','F0000',10041,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (428,'0000','F0000',10046,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (429,'0000','F0000',10048,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (430,'0000','F0000',10067,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (431,'0000','F0000',10072,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (432,'0000','F0000',10087,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (433,'0000','F0000',10092,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (434,'0000','F0000',10008,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (435,'0000','F0000',10012,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (436,'0000','F0000',10013,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (437,'0000','F0000',10014,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (438,'0000','F0000',10017,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (439,'0000','F0000',10019,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (440,'0000','F0000',10024,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (441,'0000','F0000',10025,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (442,'0000','F0000',10001,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (443,'0000','F0000',10002,null);

CREATE TABLE XXBG_CASIER_CASH
  (
    CASHIER         VARCHAR2(32 BYTE),
    BANK_ACCOUNT_ID NUMBER(38,0)
  )

declare 
v_exe_grant varchar2(32767 char);
begin 


for i in (select * from xx_office_user_imp where office = '0000') loop

  insert into XXBG_CASIER_CASH values (i.user_name, i.bank_account_id);

  v_exe_grant := 
                 'create user '  || i.user_name || ' identified by ' || i.user_name || ';' 
              || 'GRANT create session to ' || i.user_name || ';' 
              || 'GRANT select on apps.XXBG_CE_STATEMENT_HEADERS_CASH to ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.FND_USER TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.dFND_DESCR_FLEX_COL_USAGE_TL TO ' || i.user_name || ';' 
              || 'GRANT select on apps.fnd_descr_flex_column_usages to ' || i.user_name || ';' 
              || 'GRANT select on apps.fnd_descriptive_flexs to ' || i.user_name || ';' 
              || 'GRANT select on apps.fnd_descriptive_flexs_tl to ' || i.user_name || ';' 
              || 'GRANT select on ce.ce_statement_headers to ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.fnd_doc_sequence_assignments TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON CE.CE_STATEMENT_HEADERS_S TO ' || i.user_name || ';' 
              || 'GRANT EXECUTE ON APPS.XXBG_GET_NEXTVAL TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON CE.CE_STATEMENT_LINES TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.XXBG_CE_STATEMENT_LINES TO ' || i.user_name || ';' 
              || 'GRANT select on apps.CE_BANK_ACCOUNTS to ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.CE_BANK_BRANCHES_V TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON CE.XXBG_CASIER_CASH TO ' || i.user_name || ';' 
              || 'GRANT EXECUTE ON APPS.XXBG_ST TO ' || i.user_name || ';' 
              || 'GRANT select on ce.xxbg_ce_statement_lines_detail to ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.ce_transaction_codes TO ' || i.user_name || ';' 
              || 'GRANT select on ce.ce_statement_lines_s to ' || i.user_name || ';' 
              || 'GRANT SELECT ON CE.XXBG_CE_STATEMENT_LINES_DET_SQ TO ' || i.user_name || ';' 
              || 'GRANT select on apps.xx_pko_lines to ' || i.user_name || ';' 
              || 'GRANT SELECT ON apps.xx_rko_lines TO ' || i.user_name || ';' 
              || 'GRANT select on apps.XX_INVOICE_RELATIONS_CASH to ' || i.user_name || ';' 
              || 'GRANT select on APPS.PO_VENDOR_SITES_ALL to ' || i.user_name || ';' 
              || 'GRANT select on ap.AP_INVOICE_LINES_INTERFACE_S to ' || i.user_name || ';' 
              || 'GRANT select on ap.AP_INVOICE_LINES_INTERFACE to ' || i.user_name || ';' 
              || 'GRANT select on APPS.ap_distribution_set_lines_all to ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.AP_INVOICES_INTERFACE_S TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.AP_INVOICES_INTERFACE TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.AP_DISTRIBUTION_SETS_ALL  TO ' || i.user_name || ';' 
              || 'GRANT select on apps.ce_lookups  to ' || i.user_name || ';' 
              || 'GRANT select on ar.HZ_CUST_SITE_USES_ALL to ' || i.user_name || ';' 
              || 'GRANT select on ar.HZ_LOCATIONS to ' || i.user_name || ';' 
              || 'GRANT select on ar.HZ_PARTIES to ' || i.user_name || ';' 
              || 'GRANT select on ar.HZ_PARTY_SITES to ' || i.user_name || ';' 
              || 'GRANT SELECT ON AR.HZ_CUST_ACCT_SITES_ALL TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON AR.HZ_CUST_ACCOUNTS TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.XXBG_CLAIMS_V TO ' || i.user_name || ';' 
              || 'GRANT select on apps.xxbg_insis_agents_v to ' || i.user_name || ';' 
              || 'GRANT select on ce.xxbg_cash_doc_types to ' || i.user_name || ';' 
              || 'GRANT select on AP.AP_BANK_ACCOUNTS_ALL to ' || i.user_name || ';' 
              || 'GRANT SELECT ON AP.AP_BANK_BRANCHES TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.FND_DESCR_FLEX_CONTEXTS TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.FND_DESCR_FLEX_CONTEXTS_TL TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.AP_SUPPLIERS to ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.per_employees_x TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.fnd_doc_seq_categories_ap_v TO ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.AP_LC_INVOICE_TYPES_V to ' || i.user_name || ';' 
              || 'GRANT SELECT ON ce.xxbg_ce_statement_lines_sq to ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.XXBG_STATEMENT_HEADERS_CASH to ' || i.user_name || ';' 
              || 'GRANT SELECT ON APPS.XXBG_INSIS_POLICY_V TO ' || i.user_name || ';' 
              || 'GRANT insert  ON ce.ce_statement_lines to ' || i.user_name || ';' 
              || 'GRANT INSERT  ON CE.XXBG_CE_STATEMENT_LINES_DETAIL TO ' || i.user_name || ';' 
              || 'GRANT INSERT ON APPS.AP_INVOICES_INTERFACE TO ' || i.user_name || ';' 
              || 'GRANT INSERT ON APPS.AP_INVOICE_LINES_INTERFACE TO ' || i.user_name || ';' 
              || 'GRANT INSERT ON APPS.XX_RKO_LINES TO ' || i.user_name || ';' 
              || 'GRANT INSERT ON APPS.XX_PKO_LINES TO ' || i.user_name || ';' 
              || 'GRANT delete on ce.xxbg_ce_statement_lines_detail to ' || i.user_name || ';' 
              || 'GRANT update on ce.XXBG_CE_STATEMENT_LINES_DETAIL to ' || i.user_name || ';' 
              || 'GRANT DELETE ON CE.CE_STATEMENT_LINES TO ' || i.user_name || ';' 
              || 'GRANT INSERT ON CE.CE_STATEMENT_HEADERS TO ' || i.user_name || ';' 
              || 'GRANT update on CE.CE_STATEMENT_HEADERS to ' || i.user_name || ';' 
              || 'GRANT update on ce.CE_STATEMENT_LINES to ' || i.user_name || ';' 
              || 'GRANT select on apps.XX_AGENTS_NO_V to ' || i.user_name || ';' ;
              
              
  execute immediate v_exe_grant;
  
update xx_office_user_imp
  set transfered = 1 
  where id = i.id
;

v_exe_grant := '';
end loop;

end;
/

After execute the PL/SQL block I get the message:

Error report:
ORA-00911: invalid character
ORA-06512: at line 79
00911. 00000 -  "invalid character"
*Cause:    identifiers may not start with any ASCII character other than
           letters and numbers.  $#_ are also allowed after the first
           character.  Identifiers enclosed by doublequotes may contain
           any character other than a doublequote.  Alternative quotes
           (q'#...#') cannot use spaces, tabs, or carriage returns as
           delimiters.  For all other contexts, consult the SQL Language
           Reference Manual.
*Action:

Any ideas? I think I call correct immediate execution.

DB version: 11g

Unfortunately I can't provide you the sql code of the other tables to create their... Maybe you should try without all budgets... :)

Thanks in advance,
Bahchevanov.

Edited by: bahchevanov on 11 October 2012 06:14

Bahchevanov wrote:
Any ideas?

Sure. EXECUTE IMMEDIATE executes a unique statement when you try to run the job. So use:

execute immediate 'create user '  || i.user_name || ' identified by ' || i.user_name;
execute immediate 'GRANT create session to ' || i.user_name;
execute immediate 'GRANT select on apps.XXBG_CE_STATEMENT_HEADERS_CASH to ' || i.user_name;
.
.
.

SY.

How to integrate the dynamic SQL generated in the data definition XML file?

Hi all
I have it here is the XML file that is attached to the definition of data model RTF as below. Also, I have a function that will return to create a dynamic query as shown below.
```
<?xml version="1.0" encoding="UTF-8"?> 
<dataTemplate name="XYZ" description="iExpenses Report" Version="1.0"> 
<dataQuery> 
<sqlStatement name="Q2"> 
<![CDATA[
```
Hi guys,.

I was able to solve above the requirement. It was not possible to create only from SQL dynamically. Instead, I created a procedure that would create & update (attached to the data definition) XML file dynamically for each race.

Kind regards

Patricia K.

Rows affected the dynamic SQL

Hello
VERSION - Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64 bit Production
I want the number of rows affected by SQL dynamic, as shown below in the code where insert statement will be repeated for each record in the CURSOR.
for rec in c1
loop

ABC: =' insert into test
Select a.*,' | recomm. OP_ID |', "' | recomm. OP_NAME | " 'of BL_testI' | recomm. OP_ID: ' where START_DATE > = trunc(sysdate-2) and START_DATE < trunc(sysdate-1)';
insert into str_test values (abc);
immediately run abc;
commit;

When exit c1% notfound;
end loop;
In a normal query I would do it spontaneously SQL COUNT but cannot use it here.
Thnx in advance

Just use SQL % ROWCOUNT. What is the problem with that?

Here is an example.

SQL > declare
l_sql 2 varchar2 (4000);
3. start
4 l_sql: = ' insert into t select * from emp';
5. immediately run l_sql;
6 dbms_output.put_line(l_sql ||) ': Number of inserted rows = ' | to_char(SQL%RowCount));)
7 end;
8.

insert into t select * from EMP: number of inserted rows = 11

PL/SQL procedure successfully completed.

SQL >

Using of the dynamic SQL and the cursor in a procedure

Here is the procedure:

create or replace
Procedure type_paiement_total
is

    cursor xbtable is select table_name from user_tables where table_name like 'XB%';
    n_table user_tables.table_name%type;
    req     varchar2(256);
    journal varchar2(2);
    mois varchar2(2);
    an varchar2(2);
  begin
    for n_table in xbtable
    loop
      execute immediate 'insert into xx_jk_xb (
      clie_code,journal, periode,origine, xb_ecri,xb_libe  ,dos_code,xb_debi,xb_cred,xb_term
)
select c.code,  
substr(:1,3,2),
substr(:1,7,2)||substr(:1,5,2)||,
:1,  
xb.ecri,  
xb.libe,  
d.code,
xb.debi,
xb.cred,
xb.terme
from                      
'||n_table.table_name ||' xb,
dossier d,                      
client c                    
where xb.cmpt=''4111''                    
and xb.doss  =d.code                    
and c.code   =d.clie
and c.role=''1''' using n_table.table_name;
      execute immediate 'insert into xx_jk_logxb (recnum,xb_ref,trsf) values (seq_logmreg.nextval,:1,''OK'')' using n_table.table_name;
      commit;
      fetch xbtable into n_table;
    end loop;
  end;

What he does (or what I intend to do)
take the datas of a whole bunch of pictures and put them in the "XX_JK_XB" table and make a log of the tables covered in xx_jk_logxb give just the source table and the status (OK).
Now when I run the procedure I get a "missing expression" th ' immediate «insert into xx_jk...»» »

I just can't tell what is the problem here.

clues?

Seems to me that you are wrong assuming that the binding can be done by name and no position when you use immediate enforcement.

Example:

SQL> create table foo_tab( c1 varchar2(10), n1 number );

Table created.

SQL>
SQL> begin
  2          for i in 1..10
  3          loop
  4                  execute immediate 'insert into foo_tab values( to_char(:1), :1 )' using i;
  5          end loop;
  6          commit;
  7  end;
  8  /
begin
*
ERROR at line 1:
ORA-01008: not all variables bound
ORA-06512: at line 4

SQL>
SQL>
SQL> begin
  2          for i in 1..10
  3          loop
  4                  execute immediate 'insert into foo_tab values( to_char(:1), :1 )' using i,i;
  5          end loop;
  6          commit;
  7  end;
  8  /

PL/SQL procedure successfully completed.

SQL>

As you can see, 1 PL/SQL block attempts to re - use bind variable: 1 new - and only link once.

Fact does not work like that - you must link it again. Binding is done by bind - 1 position = 1 to the help of var, 2nd = 2nd bind using var, etc.. Name of the connection variable used is irrelevant and not unique.

How the date can be filled with timestamp in dynamic sql

Hi all
Below we have sql
v_stmt: = ' MERGE IN MTH_EQUIPMENTS_EXT_B ED
WITH THE HELP OF)
SELECT TAG_DATA,
EQUIPMENT_FK_KEY,
WORKORDER_FK_KEY,
SEGMENT_FK_KEY,
SHIFT_WORKDAY_FK_KEY,
HOUR_FK_KEY,
ITEM_FK_KEY,
READ_TIME,
ATTR_GROUP_ID,
RECIPE_NUM,
RECIPE_VERSION,
NVL (FND_GLOBAL. User_Id,-1) l_updated_by,.
NVL (FND_GLOBAL. Login_Id,-1) l_last_update_login
OF MTH_TAG_READINGS_T_STG
WHERE DB_COL = ' | " ' || v_colname | " ' ||') TS
WE (';)
v_stmt: = v_stmt | "ED. EQUIPMENT_PK_KEY = TS. EQUIPMENT_FK_KEY AND
ED. READ_TIME = TS. READ_TIME AND
ED. ATTR_GROUP_ID = TS. ATTR_GROUP_ID)
WHEN MATCHED THEN
UPDATE
GAME ED.'. v_colname |' = TS. TAG_DATA,
ED. LAST_UPDATED_BY = 1, ";
v_stmt: = v_stmt | "ED. LAST_UPDATE_LOGIN = TS.l_last_update_login
WHEN NOT MATCHED THEN
INSERT ('| v_colname |', EXTENSION_ID, EQUIPMENT_PK_KEY, WORKORDER_FK_KEY, SEGMENT_FK_KEY, SHIFT_WORKDAY_FK_KEY, HOUR_FK_KEY, ITEM_FK_KEY, READ_TIME, ATTR_GROUP_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY,';)
v_stmt: =.
v_stmt | ("LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, RECIPE_NUM, RECIPE_VERSION)
VALUES (TS. TAG_DATA, EGO_EXTFWK_S.NEXTVAL, TS. EQUIPMENT_FK_KEY, TS. WORKORDER_FK_KEY, TS. SEGMENT_FK_KEY, TS. SHIFT_WORKDAY_FK_KEY, TS. HOUR_FK_KEY, TS. ITEM_FK_KEY, TS. READ_TIME,';
v_stmt: = v_stmt | "TS. ATTR_GROUP_ID,' | '''|| SYSDATE | "'| ', 1, TS.l_last_update_login, TS.l_updated_by,'|"' | SYSDATE | " ' ||', TS. RECIPE_NUM, TS. RECIPE_VERSION)';
EXECUTE IMMEDIATE v_stmt;
After you run the above SQL last date of update in MTH_EQUIPMENST_EXT_B is filled with sysdate but timestamp is not its always 00:00:00. Can we have timestamp also populated through dynamic sql in the last update date
Kind regards
Amrit

Values to hardcode in the dynamic SQL - never use bind variables:

v_stmt: = ' MERGE IN MTH_EQUIPMENTS_EXT_B ED

WITH THE HELP OF)

SELECT TAG_DATA,

EQUIPMENT_FK_KEY,

WORKORDER_FK_KEY,

SEGMENT_FK_KEY,

SHIFT_WORKDAY_FK_KEY,

HOUR_FK_KEY,

ITEM_FK_KEY,

READ_TIME,

ATTR_GROUP_ID,

RECIPE_NUM,

RECIPE_VERSION,

NVL (FND_GLOBAL. User_Id,-1) l_updated_by,.

NVL (FND_GLOBAL. Login_Id,-1) l_last_update_login

OF MTH_TAG_READINGS_T_STG

WHERE DB_COL =: 1) TS

WE (';)

v_stmt: = v_stmt | "ED. EQUIPMENT_PK_KEY = TS. EQUIPMENT_FK_KEY AND

ED. READ_TIME = TS. READ_TIME AND

ED. ATTR_GROUP_ID = TS. ATTR_GROUP_ID)

WHEN MATCHED THEN

UPDATE

GAME ED.'. v_colname |' = TS. TAG_DATA,

ED. LAST_UPDATED_BY = 1, ";

v_stmt: = v_stmt | "ED. LAST_UPDATE_LOGIN = TS.l_last_update_login

WHEN NOT MATCHED THEN

INSERT ('| v_colname |', EXTENSION_ID, EQUIPMENT_PK_KEY, WORKORDER_FK_KEY, SEGMENT_FK_KEY, SHIFT_WORKDAY_FK_KEY, HOUR_FK_KEY, ITEM_FK_KEY, READ_TIME, ATTR_GROUP_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY,';)

v_stmt: =.

v_stmt | ("LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, RECIPE_NUM, RECIPE_VERSION)

VALUES (TS. TAG_DATA, EGO_EXTFWK_S.NEXTVAL, TS. EQUIPMENT_FK_KEY, TS. WORKORDER_FK_KEY, TS. SEGMENT_FK_KEY, TS. SHIFT_WORKDAY_FK_KEY, TS. HOUR_FK_KEY, TS. ITEM_FK_KEY, TS. READ_TIME,';

v_stmt: = v_stmt | "TS. ATTR_GROUP_ID,: 2, 1, TS.l_last_update_login, TS.l_updated_by,: 3, TS. RECIPE_NUM, TS. RECIPE_VERSION)';

V_stmt EXECUTE IMMEDIATE

With the HELP of v_colname,.

SYSDATE,

SYSDATE;

SY.

Design of the dynamic schema through SQL
Hi all

Is it possible to design a dynamic schema using SQL?
Documents or links is greatly appreciated.

Thank you
Hello

Sorry, I don't get you. Design of a scheme is more than dynamic SQL, you must think of tables, relationships, constraints, standardization, etc.. On the dynamic SQL statements, see [using dynamic SQL statements | http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28370/dynamic.htm#CACDDACH]

Kind regards

Tables created in a stored procedure cannot be used with dynamic SQL? The impact?
There is a thread on the forum which explains how to create tables within a stored procedure (How to create a table in a stored procedure , however, it does create a table as such, but not how to use it (insert, select, update, etc.) the table in the stored procedure.) Looking around and in the light of the tests, it seems that you need to use dynamic SQL statements to execute ddl in a stored procedure in Oracle DB. In addition, it also seems that you cannot use dynamic SQL statements for reuse (insert, select, update, etc.) the table that was created in the stored procedure? Is this really the case?

If this is the case, I am afraid that if tables cannot be 'created and used"in a stored procedure using the dynamic SQL, as is the case with most of the servers of DB dynamic SQL is not a part of the implementation plan and, therefore, is quite expensive (slow). This is the case with Oracle, and if yes what is the performance impact? (Apparently, with Informix, yield loss is about 3 - 4 times, MS SQL - 4 - 5 times and so on).

In summary, tables created within a stored procedure cannot be 'used' with dynamic SQL, and if so, what is the impact of performance as such?

Thank you and best regards,
Amedeo.

Published by: AGF on March 17, 2009 10:51
AGF says:
Hi, Frank.

Thank you for your response. I understand that the dynamic SQL is required in this context.

Unfortunately, I am yet to discover "that seeks to" using temporary tables inside stored procedures. I'm helping a migration from MySQL to Oracle DB, and this was one of the dilemmas encountered. I'll post what is the attempt, when more.

In Oracle, we use [global temporary Tables | http://www.psoug.org/reference/OLD/gtt.html?PHPSESSID=67b3adaeaf970906c5e037b23ed380c2] aka TWG these tables need only be created once everything like a normal table, but they act differently when they are used. The data inserted in TWG will be visible at the session that inserted data, allowing you to use the table for their own temporary needs while not collide with them of all sessions. The data of the TWG will be automatically deleted (if not deleted programmatically) when a) a commit is issued or b) the session ends according to the parameter that is used during the creation of the TWG. There is no real need in Oracle to create tables dynamically in code.

I noticed that many people say that the "Creation of the tables within a stored procedure" is not a good idea, but nobody seems necessarily explain why? Think you could elaborate a little bit? Would be appreciated.

The main reason is that when you come to compile PL/SQL code on the database, all explicit references to tables in the code must correspond to an existing table, otherwise a djab error will occur. This is necessary so that Oracle can validate the columns that are referenced, the data types of those columns etc.. These compilation controls are an important element to ensure that the compiled code is as error free as possible (there is no accounting for the logic of programmers though ;)).

If you start to create tables dynamically in your PL/SQL code, so any time you want to reference this table you must ensure that you write your SQL queries dynamically too. Once you start doing this, then Oracle will not be able to validate your SQL syntax, check the types of data or SQL logic. This makes your code more difficult to write and harder to debug, because inevitably it contains errors. It also means that for example if you want to write a simple query to get that one out in a variable value (which would take a single line of SQL with static tables), you end up writing a dynamic slider all for her. Very heavy and very messy. You also get the situation in which, if you create tables dynamically in the code, you are also likely to drop tables dynamically in code. If it is a fixed table name, then in an environment multi-user, you get in a mess well when different user sessions are trying to determine if the table exists already or is the last one to use so they can drop etc. What headache! If you create tables with table names, then variable Dynamics not only make you a lot end up creating (and falling) of objects on the database, which can cause an overload on the update of the data dictionary, but how can ensure you that you clean the tables, if your code has an exception any. Indeed, you'll find yourself with redundant tables lying around on your database, may contain sensitive data that should be removed.

With the TWG, you have none of these issues.

Also, what is the impact on the performance of the dynamic SQL statements in Oracle? I read some contrasting opinions, some indicating that it is not a lot of difference between static SQL and SQL dynamic in more recent versions of Oracle DB (Re: why dynamic sql is slower than static sql is this true?)

When the query runs on the database, there will be no difference in performance because it is just a request for enforcement in the SQL engine. Performance problems may occur if your dynamic query is not binding variable in the query correctly (because this would cause difficult analysis of the query rather than sweet), and also the extra time, to dynamically write the query running.

Another risk of dynamic query is SQL injection which may result in a security risk on the database.

Good programming will have little need for the tables of dynamically created dynamically or SQL.

Difference between static & dynamic sql

Hello
It is my first question in OTN.
I have a pl/sql procedure with no insert statements.
Insert into table values...
If I turn all these insert statements in dynamic sql, my procedure will give more effective? (execution)
Please help me.
Thanks in adv
Friend

Hello

8b00c42d-7716-467e-BCEF-c756fd9599e2 wrote:

Hello

It is my first question in OTN.

Welcome to the Forum!

To get the most out of this Forum, see the FAQ in the Forum: Re: 2. How can I ask a question on the forums?

For all performance issues, see also this Forum FAQ page: Re: 3. how to improve the performance of my query? / my query is slow.

I have a pl/sql procedure with no insert statements.

Insert into table values...

If I turn all these insert statements in dynamic sql, my procedure will give more effective? (execution)

Probably not. Dynamic SQL is generally less effective than static SQL, as well as being more difficult to code, debug and maintain.

Is there a reason why you think that the dynamic SQL would be preferable in this case? If so, what is it?

Works with dynamic sql and list of numbers as return value
Hello.

Problems:

1. How can I insert the USERNAME variable in the string so it will be replaced over time.
2. I intend to return a list of IDS as 1,4,6,7,2 I want to use later in an IN clause.

How to complete the return function with the dynamic sql output variable?
I have no preference to dynamic sql but it was just something that came into my mind
When I thought that the implementation of the obligation to choose a list of offices for specific user groups.
(select statements from the sample are cut short, they're actually really big and I want to reuse this function in my)
BI Publisher data model for multiple modells).

CREATE or REPLACE FUNCTION F_OFFICES (-input parameters)
USERNAME IN VARCHAR2
USERGROUP IN VARCHAR2,
)
-Output parameter
RETURN VARCHAR2 AS
dynSQL VARCHAR2 (1000);
BEGIN

IF USERGROUP = "local" THEN

dynSQL: = 'xxx SELECT FROM CO_B WHERE Userid = username';

ELSIF USERGROUP = "regional" THEN

dynSQL: = "SELECT...". » ;

ELSIF USERGROUP 'federal' = THEN
dynSQL: = "SELECT...". » ;

END IF;

EXECUTE IMMEDIATE dynSQL;

-RETURN?;

END F_OFFICES;

Thanks for any help.
As you have presented essentially pseudo-code we can only give you a Pseudo-solution :)

But the principle is:
```
...
--Output parameter
RETURN VARCHAR2 AS
    dynSQL VARCHAR2(1000);
    return_value varchar2(30):
BEGIN

  IF USERGROUP = 'local' THEN
    dynSQL:= 'SELECT xxx FROM CO_B WHERE userid = :1'; -- placeholder for parameter

   ...
  END IF;

  EXECUTE IMMEDIATE dynSQL
     using USERNAME -- pass parameters in placeholder order
     into return_value;   -- obviously this must match the projection of the dynamic query 

  RETURN return_value; 

END F_OFFICES ;
```
This approach is not good if you want to vary the dynamic query projection. In this case, you can use a REF CURSOR or maybe DBMS_SQL.

Cheers, APC

Dynamic SQL with dynamic identifiers
Oracle 10gXE

I have a table that is used to track student attendance. If the student is present on a given day, a record is inserted with the student ID and the date they frequented.

presence of DESC
Name of Type Null
--------------- -------- ------
ID NOT NULL NUMBER
NUMBER OF STUDENT_ID
SITE_ID NUMBER
DATE OF ATTENDANCE_DATE

I want to view a report (in TOP) which shows all students for a given site, the days when school was in session for this month (not Saturday, Sunday) and a X for the student who participated in that day or a null value if they do not have.

ID # FNAME LNAME 3 4 5 6 7 10
38754636 POE JANE X X X
81248754 DOE KAYLA X X X X X
43127409 RAO JOHN X X X X X

In this example, days 3 and 7 of the month are from Monday to Friday and 8-9 have been excluded because they are on Saturday and Sunday.

I am trying to find a way to dynamically generate a query for any month/year and returning to a report. The obstacle is that given that I don't know in advance which days in a month will be excluded, the identifiers in my select statement are not fixed.

I found a query that returns a list of day numbers and dates for a given month. It looks like this:

SELECT LEVEL lv, TO_DATE (TO_CHAR (LEVEL, '09')
|| TO_CHAR (EXTRACT (TO_DATE('01-SEP-11') MONTHS), '09')
|| To_char (EXTRACT (TO_DATE('01-SEP-11') YEAR), ' 9999'), 'dd.mm.yyyy') mon_day
OF double WHERE ROWNUM < = EXTRACT (DAY OF LAST_DAY (TO_DATE('01-SEP-11')))
CONNECT BY LEVEL = ROWNUM

I combined this request with another brings my student attendance data and results that pivots in what I need. Then, I created a function that accepts the month and year as parameters and creates the combined request.

SELECT c.ID student_id, c.last_name, c.first_name,.
MAX (decode (mon_day, ' 01 - SEPT.-11', 'X', NULL)) '1', MAX (decode (mon_day, ' 02 - SEVEN.-11', 'X', NULL)) '2 ',.
MAX (decode (mon_day, ' 05 - SEPT.-11', 'X', NULL)) '5', MAX (decode (mon_day, ' 06 - SEPT.-11', 'X', NULL)) "6."
MAX (decode (mon_day, ' 07-SEP-11', 'X', NULL)) '7', MAX (decode (mon_day, ' 08 - SEPT.-11', 'X', NULL)) "8."
MAX (decode (mon_day, ' 09 - SEPT.-11', 'X', NULL)) '9', MAX (decode (mon_day, 12-SEP-11', 'X', NULL)) "12."
MAX (decode (mon_day, 13-SEP-11', 'X', NULL)) '13', MAX (decode (mon_day, 14-SEPT-11', 'X', NULL)) "14."
MAX (decode (mon_day, 15-SEP-11', 'X', NULL)) '15', MAX (decode (mon_day, 16-SEP-11', 'X', NULL)) "16."
MAX (decode (mon_day, 19-SEP-11', 'X', NULL)) '19', MAX (decode (mon_day, 20-7.-11', 'X', NULL)) "20."
MAX (decode (mon_day, 21-SEP-11', 'X', NULL)) "21", MAX (decode (mon_day, 22-SEP-11', 'X', NULL)) '22 ',.
MAX (decode (mon_day, 23-SEP-11', 'X', NULL)) '23', MAX (decode (mon_day, 26-SEP-11', 'X', NULL)) "26."
MAX (decode (mon_day, 27-SEP-11', 'X', NULL)) '27', MAX (decode (mon_day, 28-SEP-11', 'X', NULL)) "28."
MAX (decode (mon_day, 29-SEP-11', 'X', NULL)) '29', MAX (decode (mon_day, 30-SEP-11', 'X', NULL)) '30 '.
(SELECT level lv, TO_DATE (TO_CHAR (LEVEL, '09')
|| TO_CHAR (EXTRACT (TO_DATE('01-SEP-11') MONTHS), '09')
|| To_char (EXTRACT (TO_DATE('01-SEP-11') YEAR), ' 9999'), 'dd.mm.yyyy') mon_day
OF double WHERE ROWNUM < = EXTRACT (DAY OF LAST_DAY (TO_DATE('01-SEP-11')))
CONNECTION LEVEL = ROWNUM) a, b of attendance, student c
WHERE to_char(MON_DAY,'D') NOT IN (1.7)
AND A.mon_day = b.attendance_date
AND b.student_id = c.ID
Group of c.ID, student_id, c.last_name, c.first_name

Now I'm stuck on what I can pass this request in to get my result. What I've read, dynamic SQL method 4 would work if I incorporate Pro/C. I hope this isn't my only option. I have considered to try to do this in a function table in pipeline, but since the columns returned are not known in advance, I can't create a corresponding data type.

I'm starting to wonder if I forgot a simpler method to achieve this.

Published by: David Sumner on April 12, 2012 18:52
Ignoring the actual query and looking at the dynamic SQL part of the question.

There are 3 ways to run a dynamic select SQL in PL/SQL code.

immediate execution requires a fixed number of bind variables, linking him in position and translates a single implicit output cursor extraction - requiring the projection of cursor to be known at the time of coding.

REF CURSOR are essentially the same - the only exception being that it requires an extraction explicit coding process output cursor.

DBMS_SQL differs in all of these respects. The connection is by name and not position. The connection is dynamic. Projection of the cursor must not be known at the time of coding. It is dynamically determined at runtime and fetch offers of release of the cursor with the projection of unknown SQL - coding time.

Apex uses DBMS_SQL internally (in fact he uses DBMS_SYS_SQL properly run dynamic and specific patterns of Oracle SQL, as if a session connected as a scheme runs the SQL code). This allows the Apex to take a dynamic SQL that you enter a region (which can contain a variable number of bind variable), run it and make the projection of the cursor as an HTML report.

Apex supports in turn also dynamic SQL - what you (Apex developer) to provide a dynamic SQL code for a region, instead of you having to provide SQL fixed (with bind variable) for the region in question.

As Apex creates DBMS_SQL sliders, it doesn't have your SQL as a ref cursor or cursor DBMS_SQL. All they need is the source of the SQL statement. And that's what you create dynamically.

So in the Apex, dynamic SQL means using a function from PL/SQL to return the source for Apex SQL analyze like a slider DBMS_SQL - instead of coding the source SQL statement in a fixed statement.

So, using the option of function for an area considered in the Apex, allows you to provide the following in the code that must run to get the SQL statement for the report Apex (Apex running this as a dynamic function that returns a string):
```
--// return the dynamic SQL for the report region
return(
  case
    when :P1_OPTION = 1 then
      'select * from emp'

    when :P1_OPTION = 2 then
      'select * from dept where dept_id = :P1_DEPT_ID'
  end
);
```
You can also write a PL/SQL function that is stored in the database and call this function so that it can determine what is the dynamic SQL source code statement. For example
```
--// calling database function to return the dynamic SQL for the report region
return(
  GetDynamicReportSQL( page => 1, option => :P1_OPTION )
);
```
Dynamic SQL is fully supported by Apex - but does not require that you, the developer, to create the dynamic cursor and treat the dynamic linking and dynamic recovery of this slider.

All you have to do is to provide the source code of this dynamic SQL (including the bind variable) to the Apex and it will do the whole thing from cursor for you.

Break the dynamic SQL

Similar Questions

Maybe you are looking for