Execute Dynamic SQL statement using procedure builder

i want to execute a dynamic SQL statment using procedure builder not using forms
because my statement depending on a variable table name
i know that i can do that from forms using
FORMS_DDL('SQL_STAT');
but i wanna to use the procedure builder
which function i should use and how?
please explain in example if you don't mind.
thanks

Hi,
You can very well use DBMS_SQL Package supplied by Oracle for doing this.
Search for DBMS_SQL in OTN. You will get all info regarding this.
Regards.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by itslul:
i want to execute a dynamic SQL statment using procedure builder not using forms
because my statement depending on a variable table name
i know that i can do that from forms using
FORMS_DDL('SQL_STAT');
but i wanna to use the procedure builder
which function i should use and how?
please explain in example if you don't mind.
thanks<HR></BLOCKQUOTE>
null

Similar Messages

How can I execute Dynamic SQL statement in Forms?

Hi All,
I have to execute dynamic SQL statement from Forms
Below statement I have to execute
"EXECUTE IMMEDIATE v_stmt INTO v_return;".
Googled for the same got results saying, Better use Database function or procedures to execute these Dynamic Statements but We want to execute in forms only.
Can any one help me..
Thanks,
Madhu

So in short you are trading code obfuscation for maintainability and the ability to share code between tools? If from somewhere else you need a procedure already implemented in database PL/SQL (and now ported to forms) this would mean you'd need to implement it in every other tool. In times where you might want to integrate your forms with $other_technology and putting stuff on the database is the first step to share functionality you just go the opposite way? And all that because someone is afraid that somebody might steal your source code? I am sorry to be blunt, but this is just plain stupid.
Leaving aside that some things like Analytic Functions, Bulk processing or execute immediate are not even available in forms your software consists of how many LOC? How long does it take to bring a new developer up to speed with your source code? Imagine how long that would take for a developer who doesn't have coleagues who know their way around.
And just so you know: I work for a ISV selling a closed-source product as well. We have 200+ customers all over the planet. We are well aware that wrapped packages can be reverse engineered. The premise is: stored procedures can be reused in every tool we have, if it makes sense to put stuff on the database by all means do it. If someone would want to reverse engineer our software I'd wish him good luck as some parts are implemented in such a hilarious complicated way I have troubles understanding them (and quite frankly I refuse to understand certain parts, but that's another story). I do work for almost 10 years for that ISV.
In any case the possible solutions have already been mentioned: you have exec_sql, create_group_from_query and forms_ddl to execute dynamic SQL in forms whereas forms_ddl is a one way street and most certainly not the thing you need or want. Take a look at the documentation for the other 2 things.
cheers

How to dynamically execute generated SQL statements using 11gR2 ?

Hello,
I'd like to know if it is possible to do what the following statement intended to do:
select * from (select replace('select empno from emp',
                             '') from dual);in other words, is it possible to dynamically generate and execute a select statement in a from clause ?
thank you for your help,
John
Edited by: 440bx on Jul 16, 2010 3:57 PM changed "generate" to "generated" in subject

Hello Aketi,
That is totally WICKED !!
I've been playing with the code you posted, pretty much since you did, trying to figure out how it works. I have some idea of how it works now but, I cannot figure out why I get the set of results, not once but TWICE.
When I run the query you posted above, this is what I get:
SQL> @getxml2
TABLE_NAME                          count
CLOB_EXAMPLE                            1
D42                                     1
DEPT                                    4
DEPT_2                                  0
DEPT_ACCIDENTS                          6
DEPT_EAST                               2
... some tables deleted to shorten the output
T1                                      1
T10                                    10
T100                                    0
22 rows selected.
TABLE_NAME                          count
CLOB_EXAMPLE                            1
D42                                     1
DEPT                                    4
DEPT_2                                  0
DEPT_ACCIDENTS                          6
DEPT_EAST                               2
... some tables deleted to shorten the output
T1                                      1
T10                                    10
T100                                    0
22 rows selected.
SQL>The result is shown TWICE. I cannot figure out why. Any ideas as to why the result is shown twice ? (I ran the statement from SQL*Plus and started a fresh instance of SQL*Plus to ensure that no settings from previous scripts would be the cause).
Thank you for your help, great little piece of code!
John.
Edited by: 440bx on Jul 16, 2010 5:30 PM
Edited by: 440bx on Jul 16, 2010 5:31 PM - corrected name in Hello greeting
Edited by: 440bx - 11gR2 on Jul 17, 2010 2:55 AM - corrected misspelling
Edited by: 440bx - 11gR2 on Jul 17, 2010 2:56 AM - corrected another misspelling

Execute 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 receive the error:
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 execute immediate correctly.
DB Version: 11g
Unfortunately i cannot provide you with the sql of the other tables to create them.... Maybe you should try without all the grants... :)
Thanks in advance,
Bahchevanov.
Edited by: bahchevanov on Oct 11, 2012 6:14 AM

bahchevanov wrote:
Any ideas? Sure. EXECUTE IMMEDIATE executes a single statment while you are trying to execute whole bunch. 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.

Avoid Hard Parsing for executing dynamic SQL using DUAL table Oracle

I want to know if dynamic sql statements involving DUAL table can be modified to remove HARD PARSING.
We have several SQL statements are stored in configuration table, here is sample example
-- query 1 before replacing index values as stored in config table ---
select count(*) from dual where 'REPLACE_VALUE_OF_INDEX_3' IN ('K')
AND (('REPLACE_VALUE_OF_INDEX_13' IN ('1053','1095','1199') ) OR ('REPLACE_VALUE_OF_INDEX_13' IN ('1200') ))
AND 'REPLACE_VALUE_OF_INDEX_2' IN ('6')
AND 'REPLACE_VALUE_OF_INDEX_15' IN ('870001305')
-- query 1 after replacing index values--
select count(*) from dual where 'REPLACE_VALUE_OF_INDEX_10' IN ('K')
AND (('1030' IN ('1053','1095','1199') ) OR ('1030' IN ('1200') ))
AND '2' IN ('6')
AND 'X' IN ('870001305')
-- query 2 before replacing index values as stored in config table --
select count(*) from dual where 'REPLACE_VALUE_OF_INDEX_5' IN ('361A','362A')
AND 'REPLACE_VALUE_OF_INDEX_22' BETWEEN '200707' AND '200806'
-- query 2 after replacing index values--
select count(*) from dual where '3MAA' IN ('361A','362A') AND '201304' BETWEEN '200707' AND '200806'

If I got it right you have some (maybe lots of) conditions stored in a table (be patient - it's my interpretation)
create table eb_conditions as
select 1 rid,q'{:5 IN ('361A','362A') AND :3 BETWEEN '200707' AND '200806'}' cndtn from dual union all
select 2,q'{:2 IN ('361A','362A') AND :3 BETWEEN '200707' AND '200806'}' from dual union all
select 3,q'{:1 IN ('K') AND ((:2 IN ('1053','1095','1199') ) OR (:4 IN ('1200') )) AND :3 IN ('6') AND :5 IN ('870001305')}' from dual
RID
CNDTN
1
:5 IN ('361A','362A') AND :3 BETWEEN '200707' AND '200806'
2
:2 IN ('361A','362A') AND :3 BETWEEN '200707' AND '200806'
3
:1 IN ('K') AND ((:2 IN ('1053','1095','1199') ) OR (:4 IN ('1200') )) AND :3 IN ('6') AND :5 IN ('870001305')
and you have to check the conditions using values stored in an array
I used a table instead: the vl at rid = 1 representing the value of bind variable :1 in eb_conditions table and so on ...
create table eb_array as
select 1 rid,'K' vl from dual union all
select 2,'1199' from dual union all
select 3,'200803' from dual union all
select 4,'1000' from dual union all
select 5,'870001305' from dual
RID
VL
1
K
2
1199
3
200803
4
1000
5
870001305
You want to check the conditions using select count(*) from dual where <condition with binds substituted fron the array>
Judging from the title Hard Parsing represents the major problem and you cannot avoid it since every condition to be verified is different from every other condition.
I think your best bet is not to evaluate conditions row by row - context shift cannot be avoided and there might be more than one for each iteration.
So try to do it in a single step:
declare
w_cndtn varchar2(4000);
w_clob clob;
w_cursor sys_refcursor;
one number;
two number;
begin
dbms_lob.createtemporary(w_clob,false);
for rw in (select rid,
                    max(cndtn) cndtn,
                    listagg(val,',') within group (order by rn)||',' usng
               from (select c.rid,c.cndtn,c.rn,c.bind,
                            replace(rtrim(c.bind),':'||to_char(v.rid),''''||v.vl||'''') val
                       from (select rid,
                                    cndtn,
                                    regexp_substr(cndtn,':\d+ ',1,level) bind,
                                    level rn
                               from eb_conditions
                             connect by level <= regexp_count(cndtn,':')
                                    and prior rid = rid
                                    and prior sys_guid() is not null
                            ) c,
                            eb_array v
                      where instr(c.bind,':'||v.rid||' ') > 0
              group by rid
loop
    w_cndtn := rw.cndtn;
    while instr(w_cndtn,':') > 0
    loop
      w_cndtn := replace(w_cndtn,trim(regexp_substr(w_cndtn,':\d+ ',1,1)),substr(rw.usng,1,instr(rw.usng,',') - 1));
      rw.usng := substr(rw.usng,instr(rw.usng,',') + 1);
    end loop;
    w_cndtn := 'select '||to_char(rw.rid)||' cndtn_id,count(*) from dual where '||w_cndtn||' union all ';
    w_clob := w_clob ||' '||w_cndtn;
end loop;
w_clob := substr(w_clob,1,instr(w_clob,'union all',-1,1) - 1);
open w_cursor for w_clob;
loop
    fetch w_cursor into one,two;
    exit when w_cursor%notfound;
    dbms_output.put_line(to_char(one)||':'||to_char(two));
end loop;
dbms_lob.freetemporary(w_clob);
end;
1:0
2:0
3:0
Statement processed.
Regards
Etbin

Executing multiple SQL statements fails using ODBC

Executing multiple SQL statements will fail with error 'ORA-00911 invalid character' when connecting to an Oracle database using ODBC driver version 8.01.07.00.
When I use either my application or the Oracle ODBC Test client utility connecting using ODBC driver version 8.01.07.00 I can only get a single CALL statement (as shown below) to execute:
CALL BHInsert (TO_DATE('2003.07.23 10:04:28','YYYY.MM.DD HH24:MI:SS'),'BATCH_ID','1:CLS_FRENCHVANILLA-1','
','Event File
Name','\\KILLIANS\BATCHCTL\SampleDemo1\JOURNALS\1.evt','','AREA1','','','','','','1','','','','','',' ','');
When I try to execute the following string with multiple CALL statements (as shown below) it fails with the following error being returned - ORA-00911: invalid character
CALL BHInsert (TO_DATE('2003.07.23 10:04:28','YYYY.MM.DD HH24:MI:SS'),'BATCH_ID','1:CLS_FRENCHVANILLA-1','
','Event File
Name','\\KILLIANS\BATCHCTL\SampleDemo1\JOURNALS\1.evt','','AREA1','','','','','','1','','','','','',' ','');
CALL BHInsert (TO_DATE('2003.07.23 10:04:28','YYYY.MM.DD
HH24:MI:SS'),'BATCH_ID','1:CLS_FRENCHVANILLA-1','Version','Recipe Header','1.0','','AREA1',' ','
','','','','1','','','','','',' ','');
CALL BHInsert (TO_DATE('2003.07.23 10:04:28','YYYY.MM.DD
HH24:MI:SS'),'BATCH_ID','1:CLS_FRENCHVANILLA-1','Version Date','Recipe Header','5/18/2001 1:28:32
PM','','AREA1',' ',' ','','','','1','','','','','',' ','');
CALL BHInsert (TO_DATE('2003.07.23
10:04:28','YYYY.MM.DD HH24:MI:SS'),'BATCH_ID','1:CLS_FRENCHVANILLA-1','Author','Recipe Header','Mark
Shepard','','AREA1',' ',' ','','','','1','','','','','',' ','');
I've tried adding a line feed in addition to the space at the end of each call but that doesn't seem to help. Also have tried unsuccessfully to change the seperator used between each call using various valid continuation characters.
Executing multiple CALL statements from within Oracle's SQL Worksheet connecting as the same user and password, as my application executes successfully. However when I try this from within the Oracle ODBC test client, it fails with the same ORA-00911 error that I'm seeing in my application.
I'm currently trying the more recent ODBC drivers, however any ideas or suggestions would be greatly appreciated.

Can you take the begin ... end block and run it using SQL*Plus?
I can't think of any documentation that would specifically answer this question. I'm sure if you read & absorbed the ODBC Programmers Reference (2000+ pages) you'd be able to find out, but I don't know of a quick way to find out.
You can enable SQL*Net tracing. There are a fair number of options for enabling this tracing-- http://tahiti.oracle.com has all the Oracle manuals online, which should give you enough info to configure exactly what you want.
I would suggest, however, that you look into more performant/ scalable alternatives rather than going too far down this path. A block with lots of SQL statements with literals isn't going to make your database happy even if you get it to work.
Justin

Help With SUBSTR in dynamic SQL statement

Following is the dynamic SQL statement.
EXECUTE IMMEDIATE 'UPDATE table_name pml
SET pml.'|| con_fields.field ||' = SUBSTR(pml.'||con_fields.field||' ||'' ''||
(SELECT pml1.'||con_fields.field||'
FROM table_name pml1
WHERE pml1.grp_id = '||los_concats.grp_id ||'
AND pml1.row_id = '||los_concats.row_id||'
AND pml1.loser_flg = ''Y''),1, '||con_fields.max_length||')
WHERE pml.grp_id = '||los_concats.grp_id ||'
AND pml.loser_flg IS NULL ';
what it does is that it updates a particular field. This field is concatenated by a field of a similar record.
My problem is with SUBSTR function. Since I am concatenating fields I do not want the field to be updated greater than max_length on that field, the reason why I use SUBSTR. the select query inside SUBSTR works alright with one of the AND condition in a WHERE clause not present. When I add that additional condition it gives me this error.
ORA-00907: missing right parenthesis.
Is there any way to get around this problem. Does SQL has other than SUBSTR function which can limit the character length.
Appreciate it.

The other alternative I thought about was to do this first
EXECUTE IMMEDIATE 'SELECT pml.'||con_fields.field||'
FROM table_name pml
WHERE pml.grp_id = '||los_concats.grp_id||'
AND pml.row_id = '||los_concats.row_id||'
AND pml.loser_flg = ''Y''
' INTO v_concat_field;
write into the variable v_concat_field and then use it into the previous script.
But on this I get SQL Command not properly terminated, I don't get it Why?
Donald I tried with your suggested script. It works fine with one of the conditions eliminated. I don't understand what the error trying to say?
Thanks

How to execute dynamic if statement...

Hi All,
My PL/SQL Blocks looks like this
declare
i_string :='if 3>20 then 1 else 2 end if;' varchar2(100);
begin
end;
Between begin and end i want a piece of code which executes that if statement and sends 2 as output in dbms_output.put_line since 3 is not >20 .Basically i want to know how to execute dynamic if statement.Please help
Thanks,
Preethi

Hi,
i agree with Cyn. Dynamic SQL is often a bad idea. Try to avoid it.
Dynamic PL/SQL is even worse. If you really must do something dynamic, at least try to cast it as SQL rather than PL/SQL.
Does this do what you want?
CREATE OR REPLACE FUNCTION     eval_case
(     in_txt     IN     VARCHAR2
RETURN     NUMBER
DETERMINISTIC
IS
     return_val     NUMBER;
     sql_txt          VARCHAR2 (1000);
BEGIN
     sql_txt := 'SELECT CASE '
          ||           in_txt
          || '         END'
          || ' FROM dual';
     EXECUTE IMMEDIATE sql_txt INTO return_val;
     RETURN     return_val;
END     eval_case;
SHOW ERRORSYou might use the function above like this:
declare
     i_string varchar2(100) :='WHEN 3>20 THEN 1 ELSE 2';
begin
     dbms_output.put_line ( TO_CHAR (eval_case (i_string))
                    || ' = results of eval_case ('''
                    || i_string
                    || ''')'
end;
/

How can I open a cursor for dynamic sql statement

Hi,
I'm facing issues opening a cursor for dynamic sql statement : PLS-00455: cursor 'RESULT1' cannot be used in dynamic SQL OPEN statement.
CREATE OR REPLACE FUNCTION DEMO
(MN_I in VARCHAR)
return AB_OWNER.ABC_Type.NonCurTyp is
RESULT1 AB_OWNER.ABC_Type.NonCurTyp;
sql_stmt VARCHAR2(4000);
BEGIN
sql_stmt := 'SELECT * FROM AB_OWNER.DUN WHERE JZ_I in ('||mn_i||') ORDER BY app.ACC_I';
OPEN RESULT1 FOR sql_stmt;
END IF;
return RESULT1;
END DEMO;
What changes should I make in the code so that it doesn't fail? I can't change the definition of RESULT1 cursor though.

Gangadhar Reddy wrote:
I used SYS REFCURSOR and was able to implement successfully.How many times did you run this successful implementation that does not use bind variables?
Because this is what will happen when it runs a lot.
http://download.oracle.com/docs/cd/E11882_01/server.112/e17766/e2100.htm#sthref1874
http://forums.oracle.com/forums/search.jspa?q=%2BORA-04031%20%2Bbind&objID=c84&dateRange=all&rankBy=10001&start=30
And you will have to regularly restart the server, or possibly slightly less invasive, flush the shared pool.
Flushing Shared Pool regularly
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1516005546092
>
Ok, this is an easy one to diagnose.
You are not using bind variables. This is terrible. Flushing the shared pool is a bad
solution -- you are literally killing the performance on your box by not using them.
If I was to write a book on how to build non scalable applications in Oracle, this
would be the first and last chapter. This is a major cause of performance issues and a
major inhibitor of scalability in Oracle. The way the Oracle shared pool (a very
important shared memory data structure) operates is predicated on developers using bind
variables. If you want to make Oracle run slowly, even grind to a total halt just
refuse to use them.
>
But, please feel free to go ahead with this successful implementation.
I just hope anyone else who reads this doesn't make the same mistake.

Execute the sql statement stored in table

friends i m in complication that, how can i execute sql statement which is stored in database table.
how can i fetch that particular statement from table and make it execute!!!
Thanks in advance

I think we should stop at this point and have a little think.
My understanding is that your plan is to do the following
-Execute a Dynamic SQL statement which is constructed from values in several columns in a table (Bad idea to begin with)
-The result of the execution is then loaded into PL/SQL.....not sure how you are handling different column lists but I'll assume you are not having to convert every column value to a VARCHAR2
-The values returned are then used in an INSERT statement
So basically your goal here is to take some data from one table and insert it into another table by moving data from SQL to PL/SQL then back to SQL in an elaborate, dynamic way. This is a costly waste of resources and will not scale (this is before we get to the problem of having to read the SQL statement from a table in the first place)
I would recommend looking the INSERT SELECT statement here: http://psoug.org/reference/insert.html
This will get the job done in one go. If you really do need it to be dynamic (which you don't, trust me) then you can still store this statement in your "dynamic SQL" table and execute it using EXECUTE IMMEDIATE although I can say for sure that you're going to run into more problems down the line with this architecture, it won't scale very well, and you'll probably waste at least *1* day of your time every week trying to fix a bug caused by the removal of a table, change to a column name etc.......
However if you believe that storing SQL in a table is the best solution to your problem then go ahead.....at least when you find out that it isn't you'll have learned a valuable lesson.

Error in executing dynamic SQL

i am getting error in executing dynamic SQL
declare
vr_RenewService NUMBER(10,0);
vr_sql VARCHAR2(50);
begin
vr_sql:='Select Case
when 5 <= 365 Then 1
When 1= 0 Then 1
else 0 end into' || TO_CHAR(vr_RenewService) || 'from dual;';
execute immediate vr_sql;
--dbms_output.put_line(vr_RenewService);
end;
ERROR
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 6
06502. 00000 - "PL/SQL: numeric or value error%s"
*Cause:
*Action:

i too have tried this before you posted this solution but getting error message
declare
vr_RenewService NUMBER(10,0);
vr_sql VARCHAR2(100);
begin
vr_sql:='Select Case
when 5 <= 365 Then 1
When 1= 0 Then 1
else 0 end from dual;';
execute immediate vr_sql into vr_RenewService;
--dbms_output.put_line(vr_RenewService);
end;
ORA-06512: at line 11
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:

Preparing Dynamic SQL statement for inserting in Pro*C

Hi Friends,
From quite some time i am struggling writing Dynamic SQL statement for dynamic insert and update in Pro*C.
Can somebody go through my code and suggest me the rigth way of doing.
Right now it throws an error saying " Error while updating ORA-00904: invalid column name "
Please help me.
Girish.
int main()
EXEC SQL BEGIN DECLARE SECTION;
char *uid ="scott/tiger";
static char sqlstmt[129];
struct /* DEPT record */
int dept_num;
char dept_name[15];
char location[14];
} dept_rec;
EXEC SQL END DECLARE SECTION;
EXEC SQL WHENEVER SQLERROR DO sql_error();
EXEC SQL CONNECT :uid;
dept_rec.dept_num = 50;
strcpy(dept_rec.dept_name,"ADMIN");
strcpy(dept_rec.location,"IN");
strcpy(sqlstmt,"UPDATE dept set DNAME = dept_rec.dept_name where DEPTNO = dept_rec.dept_num");
EXEC SQL EXECUTE IMMEDIATE:sqlstmt;
EXEC SQL COMMIT;
exit(0);
void sql_error()
printf("\nError while updating %s",sqlca.sqlerrm.sqlerrmc);
EXEC SQL ROLLBACK;
}

A bit rusty here but this is how I see it.
Think of it this way ..
all Oracle is going to see is:
UPDATE dept set DNAME = dept_rec.dept_name where DEPTNO = dept_rec.dept_num
Its NOT going to know what dept_rec.dept_name is or dept_rec.dept_num is ..
it doesnt go back and fill in those values.
You need something like
strcpy(sqlstmt,"UPDATE dept set DNAME = \"");
strcat(sqlstmt,dept_rec.dept_name);
strcat(sqlstmt,"\" where DEPTNO = ");
strcat(sqlstmt,dept_rec.dept_num);
printf(sqlsmt); # Just to be sure the update statement look right during testing.

Patterns to execute a SQL Statement from a Droplet (select)

Hi,
I need to perform a query on a table, Example: select * from ARF_QUERY "the database used is Oracle. I would like to know if the atg has some
standard method to perform this database connection and execute the SQL statement from a Droplet (select).
Thank.

I dont think there is any generic droplet to run a select query directly against a table.
However, there are various lookup droplets available that run on the repositories.
Like /atg/targeting/RepositoryLookup droplet. you can run it for specific id or for all.
You might want to have a look at it in documentation of how exactly to use it.
Thanks

Current running sql statement in procedure?

How to identify the current running sql statement in procedure or package? From the v$sqlarea, i can see the only procedure name with parameters, but not current execution statement? is there any dba view to know the current execution statement in 9i & 10g ?

hi
u can also use dba_source view to know which sql statement issued by which user

How to execute multiple sql statements

hi all
i am wondering if i can execute multiple sql statements in one shot with >> execute immediate command
for example:
i define the variable as X := sql statement
Y := sql statement
z := sql statement
can i do execute immediate (X,Y, Z);
if yes how ?? and if not any possible alternate
thanks

Starting with Ganesh's code
DECLARE
   l_statement                 VARCHAR2 (2000);
   v_passwd                    VARCHAR2 (200);
   v_username                  VARCHAR2 (200) := 'test';
   v_pwd_key                   VARCHAR2 (200) := 'lwty23';
   v_dblink_name               VARCHAR2 (2000);
   v_dblink_drop               VARCHAR2 (2000);
   v_dblink_create             VARCHAR2 (2000);
   v_dblink_check_connection   VARCHAR2 (2000);
   l_number                    NUMBER;
BEGIN
   --<<c_instance>>
   FOR c_instance IN (SELECT *
                        FROM v_oracle_instances
                       WHERE environment = 'Developement')
   LOOP
      SELECT encpwd_owner.display_db_encpwd (v_username,
                                             c_instance.host_name,
                                             c_instance.instance_name,
                                             v_pwd_key)
        INTO v_passwd
        FROM DUAL;
      v_dblink_name := c_instance.host_name || '_' || c_instance.instance_name;
      v_dblink_create :=
            ' CREATE DATABASE LINK '
         || v_dblink_name
         || ' CONNECT TO '
         || v_username
         || ' '
         || 'IDENTIFIED BY '
         || v_passwd
         || ' USING'
         || ' ''(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)(HOST= '
         || c_instance.host_name
         || ')(PORT='
         || c_instance.LISTENER_PORT
         || '))(CONNECT_DATA=(SID='
         || c_instance.instance_name
         || ')))''';
      v_dblink_check_connection := 'select 1 from global_name@' || v_dblink_name || '.QCM';    --- Notice this change. I am simply selecting 1. That should be enough to test the database link.
      v_dblink_drop := 'drop database link ' || v_dblink_name || '.QCMTLAF';
      -- l_statement := 'BEGIN ' || v_dblink_create ';' || v_dblink_check_connection ';' || v_dblink_drop '; END ;'
      BEGIN
          EXECUTE IMMEDIATE (v_dblink_create);
          DBMS_OUTPUT.PUT_LINE ('DB Link ' || v_dblink_name || ' Created');
     EXCEPTION
        WHEN others THEN
           dbms_output.put_line( 'Failed to create the database link ' || v_dblink_name );
           dbms_output.put_line( dbms_utility.format_error_backtrace() );
           INSERT INTO error_table( column_list )
             VALUES( <<list of values>> );
     END;
      EXECUTE IMMEDIATE (v_dblink_check_connection) INTO l_number;    --- Notice this.
      DBMS_OUTPUT.PUT_LINE ('DB Link ' || v_dblink_name || ' Tested');
      BEGIN
         EXECUTE IMMEDIATE (v_dblink_drop);
         DBMS_OUTPUT.PUT_LINE ('DB Link ' || v_dblink_name || ' Dropped');
      EXCEPTION
         WHEN others THEN
           dbms_output.put_line( 'Failed to drop the database link ' || v_dblink_name );
           dbms_output.put_line( dbms_utility.format_error_backtrace() );
           INSERT INTO error_table( column_list )
             VALUES( <<list of values>> );
     END;
   END LOOP;
END;But I agree with the point that others have brought up that it really doesn't make sense to create and drop a database link like this.
Justin

Execute Dynamic SQL statement using procedure builder

Similar Messages

Maybe you are looking for