CASE INSIDE PL/SQL BLOCK

Hi,
Im executing a procedure with a dynamic sql query,
inside the dynamic query there is a case statement:
(CASE
           WHEN m.sender is not null
              THEN ''PULL_PUSH''
           ELSE ''NOT PULL_PUSH''
        END
       ) download_type,and the server gives me the next error:
ORA-00904: downloadtype: invalid identifier tips_
what can I do to change the "is not null " comparision?
Thanks in advanded...

IF PULL_PUSH and NOT PULL_PUSH are parameters or variables then you might have to add || So, the code will look something like
(CASE
           WHEN m.sender is not null
              THEN ' || PULL_PUSH || '
           ELSE NOT ' || PULL_PUSH || '
        END
       ) download_type,But this is just a wild assumption,
And as Karthick, said it will be beneficial if you provide the complete query for more analysis.

Similar Messages

DDL inside PL/SQL Block

Is there anyone knows if DDL statement can be include inside the PL/SQL block?
I mean, creating a table, doing DML in that table and then dropping it? I have to do this because I'm having integrity constraint errors (ORA-02291) in the tables I will use.
I need to
update table_1 set id = 2 where id = 1
but it it found child records in table_2.
when i tried:
update table_2 set id = 2 where id = 1
Of course I cannot as well update table_2 because it will not found parent record in table_1, as it had an error earlier and there were more records in table_1 than table_2.
table_1 records = 374 rows
table_2 records = 38 rows
I did some strange logic below:
a. Creating a temporary table,
b. inserting there records in table_1,
c. updating the temp table,
d. delete the records i got in table_1,
e. update table_2 (can now do an update since no child records in table_1 will be found after the delete),
f. insert records from temp table to table_1
g. drop the temp table.
BUT, I cannot create, manipulate, and drop that temp table inside the PL/SQL table.
Any thoughts.
Thanks in advance!

Another scenario is to create your constraints as deferred. I'v recently blogged about another deferred constraint usage here
http://gplivna.blogspot.com/2007/05/deferred-constraint-real-life-scenario.html
but your case also is appropriate.
But the ultimate problem BTW is that you need to update your PK values and that's at least very questionable (ok to my mind bad) design.
Gints Plivna
http://www.gplivna.eu

No Data Found: Exception in SQL inside PL/SQL block

Hi Friends
I am trying to execute an SQL SELECT stmt inside a PL/SQL block. But when i execute the procedure, it gives me No Data Found Exception.
I know it is because no row is fetched in the query, but the condition of the SELECT query i have specified is being satisfied, i have checked it by running it on the SQL prompt.
But somehow, it is not running from inside the PL/SQL procedure.Can anybody help me out on this as to why is this happening?? I am giving my code for reference and have Highlighted the Query inside it:
CREATE OR REPLACE procedure insert_sfdc_account
as
--DECLARE
CURSOR C1 IS
SELECT customer_code, name1, name2, name3, name4, phone_number, fax, web_address, industry_sector, customer_profile, customer_type,
address, city, postal_code, country_key, zzcust_type, vat_code
FROM load_cust_general
WHERE account_group = 'ZSIT';
v_cust_cur c1%ROWTYPE;
-- type sales_tab is table of load_cust_sales_area%rowtype;
v_sales_area load_cust_sales_area%ROWTYPE;
-- v_sales_area sales_tab;
     v_salesorg varchar2(10);
     v_sales_district varchar2(10);
     v_salesoff varchar2(10);
     v_custgrp varchar2(10);
     v_salesgrp varchar2(10);
v_type varchar2(20);
v_nature varchar2(10);
v_partner_code varchar2(10);
v_parent_cust varchar2(20);
v_credit_blk varchar2(20);
BEGIN
open c1;
loop
fetch c1 into v_cust_cur;
exit when c1%NOTFOUND;
for i in (SELECT customer_code, salesorg from load_cust_partner
where customer_code = v_cust_cur.customer_code ) LOOP
dbms_output.put_line(v_cust_cur.customer_code );
                    SELECT partner_code into v_partner_code from load_cust_partner
where customer_code = i.customer_code and salesorg = i.salesorg and partner_function = 'Z1';
dbms_output.put_line(v_partner_code||i.customer_code);
SELECT salesorg, sales_district, salesoff, salesgrp, custgrp INTO v_salesorg, v_sales_district, v_salesoff, v_salesgrp, v_custgrp FROM load_cust_sales_area
          WHERE customer_code = i.customer_code and salesorg = i.salesorg;
               dbms_output.put_line(v_salesorg||i.salesorg);
                    SELECT parent_customer INTO v_parent_cust from load_cust_hierarchy
WHERE customer_code = i.customer_code and salesorg = i.salesorg and hierarchy_type = 'G'; dbms_output.put_line(v_parent_cust);
                    SELECT credit_block INTO v_credit_blk from load_cust_company_cod
          WHERE customer_code = i.customer_code;
dbms_output.put_line(v_credit_blk);
for j in (SELECT account_group, customer_type from load_cust_general
where customer_code IN (select customer_code from load_cust_partner
                              where partner_code = i.customer_code and salesorg = i.salesorg and partner_function = 'ZS'))
                                                  LOOP
-- exit when j%NOTFOUND;
     dbms_output.put_line(j.account_group);
if (j.account_group = 'ZDIS') THEN
v_type := 'DISAC';
          v_nature := '06';
     --     EXIT ;
else
v_type := 'SPACC';
v_nature := '01';
END IF;
dbms_output.put_line(v_type||' '||v_nature);
END LOOP;
INSERT INTO sfdc_account
          (SAP_ACCOUNT_ID__C, NAME, TYPE, RECORDTYPEID, PARENTID, PHONE, FAX, WEBSITE, OWNERID, MARKETING_DOMAIN__C,
INDUSTRIAL_SECTOR__C, ABC_CLASSIFICATION__C, NAME_1__C, NAME_2__C, NAME_3__C, NAME_4__C, PAYMENT_STATUS__C,
CUSTOMER_GROUP__C, ADDRESS_STREET__C, CITY__C, POSTAL_CODE__C, COUNTRY__C, SALES_OFFICE__C, SALESORG__C,
SALESDISTRICT__C, SALESGROUP__C, NATURE__C, VATCODE__C)
VALUES((i.customer_code||i.salesorg), (v_cust_cur.Name1||' '||v_cust_cur.name2), ' ', v_type, v_parent_cust,
v_cust_cur.phone_number, v_cust_cur.fax, v_cust_cur.web_address, v_partner_code, SUBSTR(v_cust_cur.industry_sector,1,2),
v_cust_cur.industry_sector, v_cust_cur.customer_profile, v_cust_cur.name1, v_cust_cur.name2, v_cust_cur.name3,
v_cust_cur.name4, v_credit_blk, v_custgrp, v_cust_cur.address, v_cust_cur.city, v_cust_cur.postal_code,
v_cust_cur.country_key, v_salesoff, v_salesorg, v_sales_district,
v_salesgrp, v_nature, v_cust_cur.vat_code);
end loop;
end loop;
CLOSE c1;
-- Delete data from Load Table
-- EXECUTE IMMEDIATE 'TRUNCATE TABLE load_cust_general';
/* truncate table load_cust_partner;
truncate table load_cust_hierarhy;
truncate table load_cust_sales_area;
truncate table load_cust_company_cod;
commit;
exception
when others then
raise_application_error( -20001, substr( sqlerrm, 1, 150 ) );
END;
Kindly Help.....
Thanks and Regards

Create the procedure again and execute it in SQL*Plus environment and paste the output:
CREATE OR REPLACE procedure insert_sfdc_account
as
--DECLARE
CURSOR C1 IS
SELECT customer_code, name1, name2, name3, name4, phone_number, fax, web_address, industry_sector, customer_profile, customer_type,
address, city, postal_code, country_key, zzcust_type, vat_code
FROM load_cust_general
WHERE account_group = 'ZSIT';
v_cust_cur c1%ROWTYPE;
-- type sales_tab is table of load_cust_sales_area%rowtype;
v_sales_area load_cust_sales_area%ROWTYPE;
-- v_sales_area sales_tab;
v_salesorg varchar2(10);
v_sales_district varchar2(10);
v_salesoff varchar2(10);
v_custgrp varchar2(10);
v_salesgrp varchar2(10);
v_type varchar2(20);
v_nature varchar2(10);
v_partner_code varchar2(10);
v_parent_cust varchar2(20);
v_credit_blk varchar2(20);
BEGIN
open c1;
loop
fetch c1 into v_cust_cur;
exit when c1%NOTFOUND;
for i in (SELECT customer_code, salesorg from load_cust_partner
where customer_code = v_cust_cur.customer_code ) LOOP
SELECT partner_code into v_partner_code from load_cust_partner
where customer_code = i.customer_code and salesorg = i.salesorg and partner_function = 'Z1';
SELECT salesorg, sales_district, salesoff, salesgrp, custgrp INTO v_salesorg, v_sales_district, v_salesoff, v_salesgrp, v_custgrp FROM load_cust_sales_area
WHERE customer_code = i.customer_code and salesorg = i.salesorg;
dbms_output.put_line('Customer_Code : '|| i.customer_code);
dbms_output.put_line('SalesOrg : '|| i.salesorg);
SELECT parent_customer INTO v_parent_cust from load_cust_hierarchy
WHERE customer_code = i.customer_code and salesorg = i.salesorg and hierarchy_type = 'G';
dbms_output.put_line('Successfully Executed SQL st. Error is somewhere else');
SELECT credit_block INTO v_credit_blk from load_cust_company_cod
WHERE customer_code = i.customer_code;
for j in (SELECT account_group, customer_type from load_cust_general
where customer_code IN (select customer_code from load_cust_partner
where partner_code = i.customer_code and salesorg = i.salesorg and partner_function = 'ZS'))
LOOP
-- exit when j%NOTFOUND;
if (j.account_group = 'ZDIS') THEN
v_type := 'DISAC';
v_nature := '06';
-- EXIT ;
else
v_type := 'SPACC';
v_nature := '01';
END IF;
END LOOP;
INSERT INTO sfdc_account
(SAP_ACCOUNT_ID__C, NAME, TYPE, RECORDTYPEID, PARENTID, PHONE, FAX, WEBSITE, OWNERID, MARKETING_DOMAIN__C,
INDUSTRIAL_SECTOR__C, ABC_CLASSIFICATION__C, NAME_1__C, NAME_2__C, NAME_3__C, NAME_4__C, PAYMENT_STATUS__C,
CUSTOMER_GROUP__C, ADDRESS_STREET__C, CITY__C, POSTAL_CODE__C, COUNTRY__C, SALES_OFFICE__C, SALESORG__C,
SALESDISTRICT__C, SALESGROUP__C, NATURE__C, VATCODE__C)
VALUES((i.customer_code||i.salesorg), (v_cust_cur.Name1||' '||v_cust_cur.name2), ' ', v_type, v_parent_cust,
v_cust_cur.phone_number, v_cust_cur.fax, v_cust_cur.web_address, v_partner_code, SUBSTR(v_cust_cur.industry_sector,1,2),
v_cust_cur.industry_sector, v_cust_cur.customer_profile, v_cust_cur.name1, v_cust_cur.name2, v_cust_cur.name3,
v_cust_cur.name4, v_credit_blk, v_custgrp, v_cust_cur.address, v_cust_cur.city, v_cust_cur.postal_code,
v_cust_cur.country_key, v_salesoff, v_salesorg, v_sales_district,
v_salesgrp, v_nature, v_cust_cur.vat_code);
end loop;
end loop;
CLOSE c1;
-- Delete data from Load Table
-- EXECUTE IMMEDIATE 'TRUNCATE TABLE load_cust_general';
/* truncate table load_cust_partner;
truncate table load_cust_hierarhy;
truncate table load_cust_sales_area;
truncate table load_cust_company_cod;
commit;
exception
when others then
raise_application_error( -20001, substr( sqlerrm, 1, 150 ) );
END;
SQL> set serveroutput on
SQL> exec insert_sfdc_account;

Update Statement(with Case) in PL/SQL Block

Can we use Oracle case syntax (In a Update SQL)in a PL/SQL Block .
UPDATE table_name a
SET a.colum1 =
case when a.col2 IN (SELECT col1
FROM table_name1 b )
then 'Y'
else 'N'
end
It throws me an Error of code PLS-00103(This error message is from the parser. It found a token (language element) that is inappropriate in this context.)
Is there any alternative...
Thanx in Advance
null

Alas, PL/SQL has own SQL parser, and this parser dosn't know about CASE expressions (at least, it's true up to Oracle 8.1.7).
Try to use DECODE instead, something like
UPDATE table_name a
SET a.colum1 =
SELECT decode(count(*),0,'N','Y)
FROM table_name1 b
WHERE b.col1=a.colum1

Select query inside PL/SQL block.

Hello Experts,
I am just a beginner with PL/SQL.
If I write a select query from client like SQL dev and fire it against a database, it gives me result.
Eg: select * from employee;
Now when I use the same Query inside a PL/SQL block suppose:
Declare
begin
select * from employee;
end;
This gives error on execution, mentioning that an INTO is expected etc...
I have doubts here:
1. Can't I use a plain select inside a PL/SQL block (if so why?)
I know this is kind of very basic question, I tried searching this on the forum but could not find the thread, please redirect me to the link if this is already answered.

user8578271 wrote:
Hello Experts,
I am just a beginner with PL/SQL.
If I write a select query from client like SQL dev and fire it against a database, it gives me result.
Eg: select * from employee;
Now when I use the same Query inside a PL/SQL block suppose:
Declare
begin
select * from employee;
end;
This gives error on execution, mentioning that an INTO is expected etc...
I have doubts here:
1. Can't I use a plain select inside a PL/SQL block (if so why?) Because when you run a query in a tool like SQL Developer, or SQL*Plus or TOAD etc. then it opens up a cursor and fetches the data into internal memory structures before displaying it, and that is all done automatically and hidden from you. In PL/SQL, there is no interface to display the results of SQL queries, so you have to specifically tell it what to put the data into.
The syntax is (in basic terms)...
SELECT column1, column2... columnX
INTO variables or record structure
FROM ...Though that can only select a single row of data. If your query returns more than 1 row it will give a TOO_MANY_ROWS exception. If your query returns no rows you will get a NO_DATA_FOUND exception.
If you need to select multiple rows into variables etc., then you would need to "BULK COLLECT" into a collection/array structure, though this takes up valuable memory on the server and shouldn't be used unless necessary (and you understand the implications of doing it).

My First while loop inside PL/SQL block not working , please help

Hi ,
I am new to PL/sql and struck at PL SQL blocks , please help to solve this .
declare
v_A number constant :=10 ;
j number constant := 3 ;
BEGIN
WHILE j < v_A
LOOP
DBMS_OUTPUT.PUT_LINE('Hai');
END LOOP;
END;
please help as how to resolve this .
Thanks in advance .

btw it's a useful habit to use indentation to highlight the block structure. Also it's worth deciding what your convention will be for keywords (I use uppercase, lowercase is also fine as far as I'm concerned but I've set up my editor to uppercase them) and variables, database object names etc (I use lowercase), e.g:
DECLARE
   v_a CONSTANT PLS_INTEGER := 10;
   j   CONSTANT PLS_INTEGER := 3;
   i PLS_INTEGER := j;
BEGIN
   WHILE i <= v_a LOOP
      DBMS_OUTPUT.PUT_LINE(i);
      i := i +1;
   END LOOP;
END;or perhapsdeclare
   v_a constant pls_integer := 10;
   j   constant pls_integer := 3;
   i pls_integer := j;
begin
   while i <= v_a loop
      dbms_output.put_line(i);
      i := i +1;
   end loop;
end;When I see "declare" and "BEGIN" in the same block of code I worry about the standard of code I'm going to see...

A question about input values inside PL/SQL block

Dear all,
I would appreciate if you could kindly help me with this question.
Consider the following code.
DECLARE
myvar1 NUMBER;
myvar2 NUMBER;
myvar3 NUMBER;
BEGIN
myvar1 := &1;
myvar2 := &2;
myvar3 := &3;
DBMS_OUTPUT.put_line('myvar1 = ' || myvar1);
DBMS_OUTPUT.put_line('myvar2 = ' || myvar2);
DBMS_OUTPUT.put_line('myvar3 = ' || myvar3);
END;
/This program reads three values as input and prints them. However, I noticed that if instead of writing
myvar1 := &1;
myvar2 := &2;
myvar3 := &3;I write
myvar1 := '&1';
myvar2 := '&2';
myvar3 := '&3';The program will have very same result. I would like to know whether there is a semantic difference between both syntax,
that is, is there any difference between for example &myvar1 and 'myvar1'?
Thanks in advance,
Dariyoosh

Try this
CREATE TABLE test_sem (x VARCHAR2(10), y NUMBER)
INSERT INTO test_sem VALUES ('A',1);
INSERT INTO test_sem VALUES ('B',1);
INSERT INTO test_sem VALUES ('C',1);
INSERT INTO test_sem VALUES ('D',1);
SELECT * FROM test_sem WHERE x='&1' --OK
SELECT * FROM test_sem WHERE x=&1 -- error not a valid number
SELECT * FROM test_sem WHERE y=&1 -- ok
SELECT * FROM test_sem WHERE y='&1' -- ok since numbers can be converted to strings'&1' is for characters &1 for numbers;
You can verify form above test case
Regards,
Bhushan

Group By function inside a PL/sql Block

Hi,
I have a select statement which looks like this -
select Region, count(region) from QUOTE_LETTERS_MASTER where version != 'v112012' and source = 'http://esource.oraclecorp.com/portal/pls/portal/esrc.esr_portlet.show?id=74,34,12202' and region != 'eSource'
group by region
REGION     COUNT(REGION)
EMEA      25
NA     1
LAD     10
Japan 1
Now the above code will have different result based on the version and source provided.
I want to use a code on similar lines where the based on version and source which will come from a cursor, i want the region and count of region, but because the result will keep on changing based on the where clause i am not sure how to use the similar code as above inside a pl/sql block.
Thank you,
rakesh

Hi, I haven't tested this but how about something like this:
create or replace procedure testproc(p_version VARCHAR2, p_source VARCHAR2)
as
v_version varchar2(100);
v_source varchar2(1000);
cursor c1 is
select Region, count(region) as cnt
from QUOTE_LETTERS_MASTER
where version != v_version
and source = v_source
and region != 'eSource'
group by region;
begin
v_version := p_version;
v_sourse := p_source;
for r1 in c1 loop
   dbms_output.put_line(r1.region||' '||r1.cnt);
end loop;
end;

PL/SQL block to sql case

Hello,
I have a newbie sql question:
I have the following pl/sql block that I want to transform in sql case code:
             IF Num_WholesaleNonDiscountValue > 0.0 THEN
                  UsageStatus := 'CHARGE';
                  if Num_WholesaleNonDiscountValue < 1.0 then
                      WholesaleNonDiscountValue := '0' || TO_CHAR(Num_WholesaleNonDiscountValue);
                    else
                      WholesaleNonDiscountValue := TO_CHAR(Num_WholesaleNonDiscountValue);
                  end if;
              ELSE
                  UsageStatus := 'FREE';
                  WholesaleNonDiscountValue := TO_CHAR(Num_WholesaleNonDiscountValue);
              END IF;All I do is the following code:
select (case when Num_WholesaleNonDiscountValue > 0.0 then
                          (case Num_WholesaleNonDiscountValue < 1.0 then '0' || TO_CHAR(Num_WholesaleNonDiscountValue
                           else TO_CHAR(Num_WholesaleNonDiscountValue))
         else TO_CHAR(Num_WholesaleNonDiscountValue)) from table_name;I do not know how to evaluate the UsageStatus variable, where to put it in the select statement.
This is for my learning process.
Thanks in advanced,
Dan
Edited by: danut68 on Jan 13, 2010 5:52 AM

Hi, Dan,
I think you want something like this:
SELECT     CASE
          WHEN Num_WholesaleNonDiscountValue > 0
          THEN 'CHARGE'
          ELSE 'FREE'
     END                              AS UsageStatus
,     CASE
          WHEN Num_WholesaleNonDiscountValue > 0
          AND   Num_WholesaleNonDiscountValue < 1
          THEN '0'
     END || TO_CHAR (Num_WholesaleNonDiscountValue)     AS WholesaleNonDiscountValue
FROM     table_x
;A CASE expression returns one value.
In PL/SQL, you can do two or more completely separate things (set two different variables, for example) in the same IF-THEN-ELSE block.
To get the same results in SQL requires a completely different approach.
The clearest is to use a different CASE expression for each of the things you're trying to do, as I did above. The WHEN clauses of those CASE statements may be very similar, even identical.
Sometimes you can factor out some of the logic (using a sub-query, perhaps) so that the logic that has to be repeated in each CASE expression is very simple.
Another option for setting two variables is to have a single CASE expression that returns a string wihich is the concatenation of two different varibales, which you later parse into two separate variables. I would do this only as a last resort.

SQL logic help for pl/sql block

Hi All,
I need your suggestions and comments for the below issue:
I have two tables: table A and table B
Table A has two columns as id and counts:
Id Counts
99 10
999 13
9999 7
Table B has two columns as Id and order:
Id Order
99 1
999 2
9999 3
We need to update Order in Table B such that Id having highest count in table A has Order as 1 in table B and it keep on increasing the order for other Ids based on decreasing counts in table A. This will be like a job which will run daily and look for counts in table A and update Order in table B according to it.
It seems to be simple but i am not getting it. Please help me out of this by writing some PL/SQL block.
I will really appreciate your all comments and responses.
Regards
Dev

Hi,
Keen2Learn wrote:
Hi All,
I am really greatful to all fo you for all your replies and comments. I change ORDER table to ORDERS. All you replies worked for me but there is some slight change in scenario which i need to discuss with you all.
E.g: Table A has 10 rows like below:
Id Counts Type
99 10 A
999 13 A
9999 7 C
99 4 B
999 2 C
88 2 A
77 1 C
777 3 B
777 5 A
888 2 CIf you'd like help, please post CREATE TABLE and INSERT statements for your sample data (including table b as it is before the UPDATE or MERGE).
I populate data in Orders column Table B based on id, by grouping sum of counts for that id in table A.
Id 999 has highest sum(count) as 15, so it has orders as 1 in Table B and do same for descending counts for each Id.
Table B has 5 rows like below:
Id Orders
99 2
999 1
88 4
777 3
555 5
Assume Table B as static(no new record comes in it) but only its Orders changes for each Id based on counts for that Id in Table A. As you see, Table B has id 555 which is not in Table A, so we need to update its orders to the highest number by taking its Count as 0(zero). Sorry, it's unclear what you want to do.
Post what you'd like table b to look like after the UPDATE or MERGE.
Right now i am doing it like this:
declare
     cursor c1 is
     select Id, SUM (COUNT), RANK () OVER (ORDER BY SUM (COUNT)) rnk
     from TableA      AND Id IN (SELECT Id FROM TableB)
GROUP BY Id
ORDER BY rnk DESC;
i NUMBER := 1;
begin
for curr in c1
loop
     update TableB
set orders = i
     where id = curr.id;
     i := i + 1;
end loop;
end;I'm not sure what you're trying to do, but I'll bet you don't need PL/SQL to do it. Use a single UPDATE or MERGE statement (inside PL/SQL if necessary).
But it is not updating orders for Id 555 in TableB.There is no row for id=555 in table b, and, according to your requirements, there never will be, because "Table B as static(no new record comes in it)". It's behaving exactly as you said you wanted it to. What's the problem?
Please provide your suggesstions on what needs to be done to take care of this scenario. I will really appreciate your all suggesstions and comments. Please let me know if need some more explanation.Whenever you have a problem, post a little sample data (CREATE TABLE and INSERT statements, relevant columns only), and the results you want from that data.
In the case of a DML operation (such as UPDATE) the sample data should show what the tables are like before the DML, and the results will be the contents of the changed table(s) after the DML.
Explain, using specific examples, how you get those results from that data.
Always say what version of Oracle you're using.

Exit from a pl/sql block

Hi all. I'm on oracle 9i.
I have a problem: I launch my sql file, which has a part made of some SQL commands and then inside it there is a part that is a PL/SQL block.
What I want is that if a certain if condition is verified it must exit from PL/SQL block and also it must exit from all the file!
Here is a part of code:
drop table test1;
create table test1
as select * from test2;
create table prova_test1
as select * from test_1
where 1=2;
DECLARE
conta number := 0;
valore number := 0;
contap number := 0;
valorep number := 0;
istruzione varchar2(2000) := null;
BEGIN
select count(1), sum(val) into contap,valorep
from prova_test1;
select count(1), sum(val) into conta,valore
from test_1;
if conta <> contap or valore <> valorep then
istruzione := 'exit';
execute immediate istruzione;
else
others sql statements.....
end if;
end;
So what I want is that if the condition is verified it must exit from pl/sql block and also from all the process.
How can I achieve that??
Thanks for collaboration,
Fabrizio

Fabrizio Delli Priscoli wrote:
whenever sqlerror exit 99
whenever oserror exit 98
Number 99 or 98, are SQLCODE returned from my exception?No, they are NOT SQLCODE.
SQLCODE is an oracle database error code.
Now,
sqlerror is how 'Sql*Plus' (the one that is calling the pl/sql block) would handle ANY SQL ERROR coming out of pl/sql block OR other parts of the sql you are running within the SQL*Plus construct.
99 and 98 are the error numbers that SQL*Plus is returning to the script or code that is calling SQL*Plus. In this case, probably the 'shell script' that calls this SQL*Plus construct.
So, you would handle that error in the shell script.
Maybe something like this: (this is the shell script that is calling a sqlplus session).
1>>$LOGFILE 2>>$LOGFILE sqlplus -s $DBCONN <<EOF
whenever sqlerror exit 99
whenever oserror exit 98
set serveroutput on
set feedback off
BEGIN
some_code;
END;
exit
EOF
ret_value=$(echo $?)
case "$ret_value" in
99) mail -s "Error: Some sqlerror on the script on $(date)" $SOME_EMAIL <$LOGFILE ;;
98) mail -s "Error: Some oserror on the script on $(date)" $SOME_EMAIL <$LOGFILE ;;
esac

How to test for différent Select into a single PL/SQL block ?

Hi,
I am relatively new to PL/SQL and I am trying to do multiple selects int a single PL/SQL block. I am confronted to the fact that if a single select returns no data, I have to go to the WHEN DATA_NOT_FOUND exception.
Or, I would like to test for different selects.
In an authentification script, I am searching in a table for a USER ID (USERID) and an application ID, to check if a user is registered under this USERID for this APPLICATION.
There are different possibilities : 4 possibilities :
- USERID Existing or not Existing and
- Aplication ID found or not found for this particular USERID.
I would like to test for thes 4 possibilities to get the status of this partiular user regardin this application.
The problem is that if one select returns no row, I go to the exception data not found.
In the example below you see that if no row returned, go to the exception
DECLARE
P_USERID VARCHAR2(400) DEFAULT NULL;
P_APPLICATION_ID NUMBER DEFAULT NULL;
P_REGISTERED VARCHAR2(400) DEFAULT NULL;
BEGIN
SELECT DISTINCT(USERID) INTO P_USERID FROM ACL_EMPLOYEES
WHERE USERID = :P39_USERID AND APPLICATION_ID = :APP_ID ;
:P39_TYPE_UTILISATEUR := 'USER_REGISTERED';
EXCEPTION
WHEN NO_DATA_FOUND THEN
:P39_TYPE_UTILISATEUR := 'USER_NOT_FOUND';
END;I would like to do first this statement :
SELECT DISTINCT(USERID) INTO P_USERID FROM ACL_EMPLOYEES
WHERE USERID = :P39_USERID Then to do this one if the user is found :
SELECT DISTINCT(USERID) INTO P_USERID FROM ACL_EMPLOYEES
WHERE USERID = :P39_USERID AND APPLICATION_ID = :APP_ID ;etc...
I basically don't want to go to the not found exception before having tested the 4 possibilities.
Do you have a suggestion ?
Thank you for your kind help !
Christian

Surely there are only 3 conditions to check?
1. The user exists and has that app
2. The user exists and doesn't have that app
3. The user doesn't exist
You could do this in one sql statement like:
with mimic_data_table as (select 1 userid, 1 appid from dual union all
                          select 1 userid, 2 appid from dual union all
                          select 2 userid, 1 appid from dual),
-- end of mimicking your table
         params_table as (select :p_userid userid, :p_appid appid from dual)
select pt.userid,
       pt.appid,
       decode(min(case when dt.userid = pt.userid and dt.appid = pt.appid then 1
                       when dt.userid = pt.userid then 2
                       else 3
                  end), 1, 'User and app exist',
                        2, 'User exists but not for this app',
                        3, 'User doesn''t exist') user_app_check
from   mimic_data_table dt,
       params_table pt
where pt.userid = dt.userid (+)
group by pt.userid, pt.appid;
:p_userid = 1
:p_appid = 2
    USERID      APPID USER_APP_CHECK
         1          2 User and app exist
:p_userid = 1
:p_appid = 3
    USERID      APPID USER_APP_CHECK
         1          3 User exists but not for this app
:p_userid = 3
:p_appid = 2
    USERID      APPID USER_APP_CHECK
         3          2 User doesn't exist

Can some one please tell me what is the problem in the below pl/sql block

Hi, I have problem with the following pl/sql block, I need this with bulk operation.
-- Assume the following scenario, we are validating dept (master) and emp(child) which are my temporary tables and updating the status back to
-- dept ( for all the validation errors, even if we have any validation at child it has to update the header record with error message),
-- upon successful validation insert the data into dept3, and emp3 interms of batches
-- I have give the sample example with dept and emp, but i have around 10 million records which has around 30-40 validations,
-- I would like to process them in terms of batches using bulk collection as this would do fast processing
-- Can some one please tell me how to insert them in terms of bulk with every set of 1000 records in each batch in this example,for every set of 1000 records
-- i need update batch id with unique number in dept table
-- with current data i can have 50 batches , I need to pass, deptno as parameter to my emp cursor.
-- can some one please tell me how to make this validation and insertion more efficient. so that while inserting the data for every batch it should insert batch id
-- Tried with LIMIT clause as well but not working
-- I am correcting the code as per your comments Request you to please suggest me so that I can correct , I am new to PL/sql, started learning now.
step - 1:
CREATE TABLE DEPT
       (DEPTNO NUMBER(6) primary key,
        DNAME VARCHAR2(25),
        LOC VARCHAR2(23),
        batch_id number );
INSERT INTO DEPT VALUES (10, 'ACCOUNTING', 'NEW YORK', null);
INSERT INTO DEPT VALUES (20, 'RESEARCH',   'DALLAS', null);
INSERT INTO DEPT VALUES (30, 'SALES',      'CHICAGO', null);
INSERT INTO DEPT VALUES (40, 'OPERATIONS', 'BOSTON', null);
step - 2:
declare
begin
for i in 1..50000 loop
insert into dept values(40+i, 'OPERATIONS'||i,'BOSTON'||i, null);
end loop;
commit;
exception
when others then
dbms_output.put_line('Exception occured:'||SQLERRM);
end;
step - 3:
create sequence emp_seq start with 1 increment by 1;
step - 4:
CREATE TABLE EMP
       (EMPNO NUMBER(15) NOT NULL primary key,
        ENAME VARCHAR2(20),
        JOB VARCHAR2(20),
        MGR NUMBER(4),
        HIREDATE DATE,
        SAL NUMBER(7, 2),
        COMM NUMBER(7, 2),
        DEPTNO NUMBER(6));
INSERT INTO EMP VALUES
        (7369, 'SMITH', 'CLERK',     7902,
        TO_DATE('17-DEC-1980', 'DD-MON-YYYY'), 800, NULL, 20);
INSERT INTO EMP VALUES
        (7499, 'ALLEN', 'SALESMAN', 7698,
        TO_DATE('20-FEB-1981', 'DD-MON-YYYY'), 1600, 300, 30);
INSERT INTO EMP VALUES
        (7521, 'WARD',   'SALESMAN', 7698,
        TO_DATE('22-FEB-1981', 'DD-MON-YYYY'), 1250, 500, 30);
INSERT INTO EMP VALUES
        (7566, 'JONES', 'MANAGER',   7839,
        TO_DATE('2-APR-1981', 'DD-MON-YYYY'), 2975, NULL, 20);
INSERT INTO EMP VALUES
        (7654, 'MARTIN', 'SALESMAN', 7698,
        TO_DATE('28-SEP-1981', 'DD-MON-YYYY'), 1250, 1400, 30);
INSERT INTO EMP VALUES
        (7698, 'BLAKE', 'MANAGER',   7839,
        TO_DATE('1-MAY-1981', 'DD-MON-YYYY'), 2850, NULL, 30);
INSERT INTO EMP VALUES
        (7782, 'CLARK', 'MANAGER',   7839,
        TO_DATE('9-JUN-1981', 'DD-MON-YYYY'), 2450, NULL, 10);
INSERT INTO EMP VALUES
        (7788, 'SCOTT', 'ANALYST',   7566,
        TO_DATE('09-DEC-1982', 'DD-MON-YYYY'), 3000, NULL, 20);
INSERT INTO EMP VALUES
        (7839, 'KING',   'PRESIDENT', NULL,
        TO_DATE('17-NOV-1981', 'DD-MON-YYYY'), 5000, NULL, 10);
INSERT INTO EMP VALUES
        (7844, 'TURNER', 'SALESMAN', 7698,
        TO_DATE('8-SEP-1981', 'DD-MON-YYYY'), 1500, NULL, 30);
INSERT INTO EMP VALUES
        (7876, 'ADAMS', 'CLERK',     7788,
        TO_DATE('12-JAN-1983', 'DD-MON-YYYY'), 1100, NULL, 20);
INSERT INTO EMP VALUES
        (7900, 'JAMES', 'CLERK',     7698,
        TO_DATE('3-DEC-1981', 'DD-MON-YYYY'),   950, NULL, 30);
INSERT INTO EMP VALUES
        (7902, 'FORD',   'ANALYST',   7566,
        TO_DATE('3-DEC-1981', 'DD-MON-YYYY'), 3000, NULL, 20);
INSERT INTO EMP VALUES
        (7934, 'MILLER', 'CLERK',     7782,
        TO_DATE('23-JAN-1982', 'DD-MON-YYYY'), 1300, NULL, 10);
commit;
step :- 5
declare
cursor c1 is select * from dept;
k number:=0;
m number:=0;
begin
for i in c1 loop
k:=k+1;
--dbms_output.put_line('k:'||k);
--dbms_output.put_line('i.deptno:'||i.deptno);
m:=0;
for j in 1..5 loop
m:=m+1;
--dbms_output.put_line('m:'||m);
--dbms_output.put_line('i.deptno:'||i.deptno);
insert into emp values
        (9000+emp_seq.nextval, 'SMITH'||'_'||emp_seq.currval, 'CLERK'||'_'||emp_seq.currval,     7902,
        TO_DATE('17-DEC-1980', 'DD-MON-YYYY'), 800, NULL, i.deptno);
end loop;
end loop;
commit;
exception
when others then
dbms_output.put_line('Exception occured:'||sqlerrm);
end;
step :-6
create table dept3 as select * from dept where 1=2;
create table emp3 as select * from emp where 1=2;
alter table dept add object_id number;
alter table dept add status varchar(20);
alter table dept add err_msg varchar2(200);
alter table emp add object_id number;
-- I have not included the alter statements in the inital creation because i dont want them to insert into dept3 and emp3
CREATE OR REPLACE
PACKAGE test_b
AS
g_batch_id NUMBER;
PROCEDURE emp_ins(
      p_EMPNO    NUMBER,
      p_ENAME    VARCHAR2,
      p_JOB      VARCHAR2,
      p_MGR      NUMBER,
      p_HIREDATE DATE,
      p_SAL      NUMBER,
      p_COMM     NUMBER,
      p_DEPTNO   NUMBER);
PROCEDURE dept_ins(
      p_DEPTNO NUMBER,
      p_dname VARCHAR2 ,
      p_LOC    VARCHAR2,
      p_batch NUMBER);
PROCEDURE validate_prc;
PROCEDURE main;
TYPE dept_t
IS
TABLE OF dept%ROWTYPE;
hdr_tbl dept_t;
TYPE emp_t
IS
TABLE OF emp%ROWTYPE;
line_tbl emp_t;
TYPE dept_i_t
IS
TABLE OF dept3%ROWTYPE;
hdr_ins_tbl dept_i_t;
TYPE emp_i_t
IS
TABLE OF emp3%ROWTYPE;
line_ins_tbl emp_i_t;
END;
-- pacakge body
CREATE OR REPLACE
PACKAGE body test_b
AS
PROCEDURE emp_ins(
    p_EMPNO    NUMBER,
    p_ENAME    VARCHAR2,
    p_JOB      VARCHAR2,
    p_MGR      NUMBER,
    p_HIREDATE DATE,
    p_SAL      NUMBER,
    p_COMM     NUMBER,
    p_DEPTNO   NUMBER)
IS
BEGIN
INSERT
INTO EMP3
      EMPNO ,
      ENAME ,
      JOB ,
      MGR ,
      HIREDATE ,
      SAL ,
      COMM ,
      DEPTNO
    VALUES
      P_EMPNO ,
      P_ENAME ,
      P_JOB ,
      P_MGR ,
      P_HIREDATE ,
      P_SAL ,
      P_COMM ,
      P_DEPTNO
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('EXCEPTION AT EMP INSERT'||SQLERRM);
END;
PROCEDURE dept_ins
    p_DEPTNO NUMBER,
    p_dname VARCHAR2 ,
    p_LOC    VARCHAR2,
    p_batch NUMBER
IS
BEGIN
INSERT
INTO DEPT3
      DEPTNO ,
      DNAME ,
      LOC ,
      batch_id
    VALUES
      p_DEPTNO ,
      p_DNAME ,
      p_LOC ,
      p_batch
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('EXCEPTION AT DEPT INSERT'||SQLERRM);
END ;
PROCEDURE validate_prc
IS
CURSOR c1
IS
    SELECT * FROM dept WHERE status IS NULL ;--AND rownum <25;
CURSOR c2(p_dept NUMBER )
IS
    SELECT * FROM emp WHERE deptno=p_dept;
e_validation EXCEPTION;
BEGIN
OPEN c1;
LOOP
    FETCH c1 BULK COLLECT INTO hdr_tbl limit 5000;
    SELECT emp_seq.nextval INTO g_batch_id FROM dual;
    EXIT
WHEN hdr_tbl.count = 0;
    dbms_output.put_line('batch'||g_batch_id);
END LOOP;
CLOSE c1;
dbms_output.put_line('C1 closed');
--------- Loading data into the inv line table type -------------------------------
FOR i IN 1 .. hdr_tbl.count
LOOP
    dbms_output.put_line('started validation');
    -- do header level validations
    IF hdr_tbl(i).dname IS NULL THEN
      hdr_tbl(i).status := 'ERROR';
      hdr_tbl(i).err_msg :=',DNAME is null';
    END IF;
    OPEN c2(hdr_tbl(i).deptno);
    LOOP
      FETCH c2 BULK COLLECT INTO line_tbl;
      -- EXIT WHEN c2%NOTFOUND;
    END LOOP;
    CLOSE c2;
    FOR j IN 1 .. line_tbl.count
    LOOP
      -- do line validations
      IF line_tbl(j).ename IS NULL THEN
        hdr_tbl(i).status := 'ERROR';
        hdr_tbl(i).err_msg :=',ENAME is null';
      END IF;
      BEGIN
        FORALL j IN line_tbl.FIRST .. line_tbl.LAST
        SAVE EXCEPTIONS
        UPDATE EMP
        SET object_id =3
          -- I have multiple columns to update based on validations
        WHERE deptno =hdr_tbl(i).deptno------------
        AND empno    =line_tbl (j).empno;
        COMMIT;
        line_tbl.DELETE;
        dbms_output.put_line( 'Successfully updated emp temp table.');
      EXCEPTION
      WHEN OTHERS THEN
        ROLLBACK;
        dbms_output.put_line( 'Error while updating line temp table. ' || sqlerrm );
        FOR j IN 1 .. sql%BULK_EXCEPTIONS.COUNT
        LOOP
          DBMS_OUTPUT.put_line(' occurred during line temp table updation ' || sql%BULK_EXCEPTIONS(i).ERROR_INDEX );
        END LOOP;
        raise e_validation;
      END;
    END LOOP; -- j
    --CLOSE c2;
    IF hdr_tbl(i).err_msg IS NULL THEN
      hdr_tbl (i).status := 'VALID';
      hdr_tbl (i).err_msg := NULL;
    END IF;
    -- even if I have line validation failed I have to update header status and erorr msg
    BEGIN
      FORALL i IN hdr_tbl.FIRST .. hdr_tbl.LAST
      SAVE EXCEPTIONS
      UPDATE DEPT
      SET object_id =4,
        status      = hdr_tbl (i).status,
        err_msg     = hdr_tbl (i).err_msg
        -- batch_id =
        -- I have multiple columns to update based on validations
      WHERE deptno = hdr_tbl (i).deptno
      AND status IS NULL; ------------
      COMMIT;
      hdr_tbl.DELETE;
      dbms_output.put_line( 'Successfully updated dept temp table.');
      --close c1;
    EXCEPTION
    WHEN OTHERS THEN
      ROLLBACK;
      dbms_output.put_line( 'Error while updating hdr temp table. ' || sqlerrm );
      FOR i IN 1 .. sql%BULK_EXCEPTIONS.COUNT
      LOOP
        DBMS_OUTPUT.put_line(' occurred during line temp table updation ' || sql%BULK_EXCEPTIONS(i).ERROR_INDEX );
      END LOOP;
      raise e_validation;
    END;
END LOOP; --i
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('EXCEPTION AT validate'||SQLERRM);
END ;
PROCEDURE main
IS
CURSOR dept_ins_cur
IS
    SELECT * FROM dept WHERE status='VALID';
CURSOR emp_ins_cur(p_deptno NUMBER)
IS
    SELECT * FROM emp WHERE deptno= p_deptno;
BEGIN
validate_prc;
OPEN dept_ins_cur;
LOOP
FETCH dept_ins_cur BULK COLLECT INTO hdr_ins_tbl limit 1000
EXIT
WHEN dept_ins_cur%NOTFOUND;
END LOOP;
CLOSE dept_ins_cur;
--------- Loading data into the inv line table type -------------------------------
FOR i IN 1 .. hdr_tbl.count
loop
dept_ins(hdr_ins_tbl(i).deptno ,
hdr_ins_tbl(i).DNAME ,
hdr_ins_tbl(i).LOC , emp_seq.nextval);
commit;
OPEN emp_ins_cur(hdr_ins_tbl(i).deptno);
LOOP
FETCH emp_ins_cur BULK COLLECT INTO line_ins_tbl;
--EXIT WHEN emp_ins_cur%NOTFOUND;
END LOOP;
CLOSE emp_ins_cur;
for j in 1..line_ins_tbl.count loop
emp_ins(line_ins_tbl(j).EMPNO ,
line_ins_tbl(j).ENAME ,
line_ins_tbl(j).JOB ,
line_ins_tbl(j).MGR ,
line_ins_tbl(j).HIREDATE ,
line_ins_tbl(j).SAL ,
line_ins_tbl(j).comm ,
line_ins_tbl(j).DEPTNO );
end loop;
end loop;
commit;
BEGIN
forall i IN hdr_ins_tbl.first .. hdr_ins_tbl.last
SAVE exceptions
UPDATE dept
SET status   = 'INSERTED',
err_msg = null
WHERE deptno=hdr_ins_tbl (i).deptno
AND status   = 'VALID';
COMMIT;
hdr_ins_tbl.delete;
dbms_output.put_line( 'inserting into temp tables.');
EXCEPTION
WHEN OTHERS THEN
rollback;
end;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('exception in main' ||SQLERRM);
END ;
END;
Thanks in advance...
Message was edited by: 888025

Hi, I have problem with the following pl/sql block
Well, as Hoek already said, that is the understatement of the century.
I can't be absolutely certain but I think that set of DDL and code that you posted has just about every possible error and design issue that there is! It would make an excellent addition to BluShadow's FAQs an an example of what NOT to do.
I don't think it is even possible to 'fix the basics first' as Hoek suggested. IMHO the first step needs to be to create a functional requirements document (FRD) that explains in detail WHAT needs to be done. That doc should also contain info about how any errors/recovery/restart is to be handled. It is premature to try to implement ANY solution without first knowing what is needed functionally.
Once the FRD is done you should do a walk-through based on your current architecture and sample data to make sure that the document really covers ALL of the steps that need to be performed and that it adequately explains how to deal with any processing or data issues that might arise.
The next document you need is the TRD - Technical Requirements Doc that covers the different technical implementions of the FRD that can be done and the advantages/disadvantages of each.
Then you can start working on a prototype.
1. The DDL you posted isn't coherent - there are CREATE table statements and then later ALTER statements that add additional columns. There doesn't appear to be any reason for not including ALL of the columns in the CREATE table statement.
2. You are using PL/SQL types instead of SQL types. That makes it impossible to use those types in SQL statements and makes it much more difficult to test since it is much easier to test a query in SQL (e.g. using sql*plus) that to embed the query in PL/SQL.
3. You are defining the same type twice but giving it different names.
TYPE dept_t
   IS
      TABLE OF dept%ROWTYPE
         INDEX BY binary_integer;
TYPE dept_i_t
   IS
      TABLE OF dept%ROWTYPE
         INDEX BY binary_integer;
Those are both based on the same DEPT table! Why the duplication?
Also you are using associative arrays instead of just using nested tables. Get rid of the INDEX BY clause.
4. You have some serious architectural and data model issues
-- Assume the following scenario, we are validating dept (master) and emp(child) which are my temporary tables and updating the status back to
-- dept ( for all the validation errors, even if we have any validation at child it has to update the header record with error message),
Why would you do that? You say 'it has to update the header record ...'. Says who? That is just one indication that you are trying to implement a 'solution' before you have adequately defined the 'problem'.
Typically you would NOT alter any of the data tables; any validation errors/issues would get inserted into a table specifically designed to hold/log those issues. That table would contain key field values to correlate with the source of the error.
Those 'master' and 'child' entities are two SEPARATE things. Issues with a 'master' row have NOTHING to do with any possible child rows.
And issues with a 'child' row have NOTHING to do with any possible master rows. The ONLY connection between 'child' and 'master' is the foreign key that correlates them.
So you don't necessarily have to validate the 'child' rows in sync with their 'master' row. In many cases you would have a procedure that performs validation of the entire set of 'master' rows and log those issues/problems. You would use a different procedure to validate the entire set of 'child' rows and log their issues.
Those validation procedures can often work with ALL of the data using SQL statements instead of bulk processing.
5. You are using loop constructs that are not valid for the type of processing you are using
LOOP
    FETCH c1 BULK COLLECT INTO hdr_tbl;
    EXIT
WHEN c1%NOTFOUND;
END LOOP;
There can be NO exit since the bulk collect with either get EVERYTHING or NOTHING. Possibly that is just a holdover from your attempt to use the LIMIT clause but you removed that clause from the FETCH; I don't know.
There is so much wrong with what you posted it is really rather pointless to try to 'fix' it.
I suggest you start over and clarify and DOCUMENT the actual requirements without prejudice about the solution that someone seems to want to force on you.

Can't create a sequence within a pl/sql block with execute immediate.

Hi All. I created a user and granted it the 'create sequence' privilege though a role. In a pl/sql block I try to create a sequence using 'execute immediate' but get a 1031-insufficient privileges error. If I grant create sequence directly to the user, the pl/sql block completes successfully. Can anyone explain this behavior? We're running 11.2 Enterprise Editon.
Thanks,
Mark

In a definer's rights stored procedure (the default), you only have access to privileges that have been granted directly, not via a role.
There are two basic reasons for that. First, roles can be enabled or disabled, default and non-default, password-protected, etc. so the set of roles a particular user actually has is session-specific. Oracle needs to know at compile time what privileges the owner of the procedure has. The only way to do that (without deferring the privilege check) is to ignore privileges granted through roles.
Second, since 99% of privilege management DBAs do involves granting and revoking roles, it's helpful that changing role privileges will never cause objects to be marked invalid and recompiled which can have side-effects on applications. DBAs only need to worry about causing problems on those rare cases where they are granting or revoking direct privileges to users.
You can create an invoker's rights stored procedure by adding the clause (AUTHID CURRENT_USER). That defer's the security check to run-time but allows the procedure to see privileges granted through roles in the current session. But that means that the caller of the procedure would need to have the CREATE SEQUENCE privilege through the role, not the owner of the procedure.
And just to make the point, dynamic object creation in PL/SQL is almost always a red flag that there is something problematic in your design. If you are creating sequences dynamically, that means that you'd have to refer to them dynamically throughout your code which means that your inserts would need to use dynamic SQL. That's not a particularly easy or safe way to develop code.
Justin

Displaying a Message from PL/SQL block to Java Application

Hi
How can One display or populate a message in Java Application, that is generated from a PL/SQL block?

Well, the easiest option would be to have a "message" parameter that gets passed back from the PL/SQL block to the calling Java application.
I'm guessing, though, that you wouldn't be asking the question if the easy solution was a viable option... If that's the case, you're going to have to describe the problem in a bit more detail...
Justin

CASE INSIDE PL/SQL BLOCK

Similar Messages

Maybe you are looking for