03-16-2011
Is it possible to add "Execute procedure" script in my current existing "Create or Replace Procedure script".
I would like this to work simultaneously "create and execute the procedure"
The script to create procedure is;
HTML Code:
CREATE OR REPLACE PROCEDURE PDAC_UPDATE_ALLOW_DENY_SERV
IS
tmpVar NUMBER;
/******************************************************************************
NAME: UPDATE_ALLOW_DENY_SERV
PURPOSE:
REVISIONS:
Ver Date Author Description
--------- ---------- --------------- ------------------------------------
1.0 11/29/2010 Mohamed.S.Rahman 1. Created this procedure.
NOTES:
Automatically available Auto Replace Keywords:
Object Name: UPDATE_ALLOW_DENY_SERV
Sysdate: 11/29/2010
Date and Time: 11/29/2010, 11:14:18 AM, and 11/29/2010 11:14:18 AM
Username: rsa11355 (set in TOAD Options, Procedure Editor)
Table Name: (set in the "New PL/SQL Object" dialog)
******************************************************************************/
BEGIN
tmpVar := 0;
UPDATE DMERCLINE
SET allow_serv = allow_serv / 1000
WHERE sadmerc_receipt_dt BETWEEN TO_DATE ('06-Oct-09')
AND TO_DATE ('30-Jun-10');
UPDATE DMERCLINE
SET deny_serv = deny_serv / 1000
WHERE sadmerc_receipt_dt BETWEEN TO_DATE ('06-Oct-09')
AND TO_DATE ('30-Jun-10');
END PDAC_UPDATE_ALLOW_DENY_SERV;
/
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Guys,
I am trying to tun a oracle proedure throgh unix shell script but it is not running i dont know why ? i have tested this procedure in sqlplus and it was working fine.
can you see the script and sql file and let me know where is my mistake.
script:bm_chart_table_loading.sh
... (3 Replies)
Discussion started by: shary
3 Replies
2. Shell Programming and Scripting
Hi everyone!
I'm new with Shell Scripting, and I have to do a shell script to call a procedure, which have 2 input parameters, the directory(from server) and the txt file (which have informations to update/insert in DB).
I have to create a shell script to execute that procedure for each txt... (5 Replies)
Discussion started by: renatoal
5 Replies
3. Shell Programming and Scripting
How to execute the stored procedure from shell script and is there any possibility to print the dbms output in a log file. (2 Replies)
Discussion started by: dineshmurs
2 Replies
4. Shell Programming and Scripting
Hi,
Below is the code to execute the procedure "dbms_job.broken" from the shell script.
on executing manually, it works properly without any error.
but it is not working when scheduled using the cronjob.
#!/usr/bin/bash
user_name="oracdb"
password="ora123"
tns="localdb"... (2 Replies)
Discussion started by: milink
2 Replies
5. Shell Programming and Scripting
I am invoking a SQL script from shell script. This SQL script will invoke a stored procedure(which has the OUT parameter). I want to have the OUT parameter in the shell script as a variable. Is this possible? (6 Replies)
Discussion started by: vel4ever
6 Replies
6. Shell Programming and Scripting
Hi,
I want to have a automted script to exceute 20 procedures one by one.
Suppose below is one procedure once it get executed script will write
"PL/SQL procedure successfully completed." to a log
for ex-
exec dbms_stats.gather_table_stats();
Now later procedure starts executing... (1 Reply)
Discussion started by: sv0081493
1 Replies
7. Shell Programming and Scripting
hi all,
i have a unix script where i am calling a database procedure from it. while executing the procedure i am getting an error:
but when i tried to call the same procedure manually then it ran successfully, i goggled this issue and found timezone.dat file missing at... (0 Replies)
Discussion started by: lovelysethii
0 Replies
8. Shell Programming and Scripting
below code is not executing the stored procedure,not sure what the issue.Even sqllog is blank.please help me its very urgent.
sqlplus -s $connect_str@$DB_ORACLE_SID >> ${SQL_LOG_FILE} << EOF
set serverout on
set feed off
set head off
set pages 0
set colsep ,
set tab off
set lin 150... (3 Replies)
Discussion started by: katakamvivek
3 Replies
9. Shell Programming and Scripting
i have the following code inside a shell script .prog in oracle server when i call the program
DBMS_OUTPUT.PUT_LINE(x_return_status|| ln_rep_req_id);
will return 0 , it is very strange , i try to submit the concurrent request in oracle , and it can successfully executed, what am i missing ? i... (1 Reply)
Discussion started by: feilhk
1 Replies
10. Shell Programming and Scripting
Hi All,
I am running the below proc in unix by connecting through sqlplus and the procedure is completing successfully. But when i am trying to run through shell scripting by using function. I am getting the error as follows. Please guide me where I am going wrong.
#!/bin/sh
opera ()
{... (6 Replies)
Discussion started by: bhas85
6 Replies
LEARN ABOUT NETBSD
set_transaction
SET
TRANSACTION(7) SQL Commands SET TRANSACTION(7)
NAME
SET TRANSACTION - set the characteristics of the current transaction
SYNOPSIS
SET TRANSACTION transaction_mode [, ...]
SET SESSION CHARACTERISTICS AS TRANSACTION transaction_mode [, ...]
where transaction_mode is one of:
ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
READ WRITE | READ ONLY
DESCRIPTION
The SET TRANSACTION command sets the characteristics of the current transaction. It has no effect on any subsequent transactions. SET SES-
SION CHARACTERISTICS sets the default transaction characteristics for subsequent transactions of a session. These defaults can be overrid-
den by SET TRANSACTION for an individual transaction.
The available transaction characteristics are the transaction isolation level and the transaction access mode (read/write or read-only).
The isolation level of a transaction determines what data the transaction can see when other transactions are running concurrently:
READ COMMITTED
A statement can only see rows committed before it began. This is the default.
SERIALIZABLE
All statements of the current transaction can only see rows committed before the first query or data-modification statement was exe-
cuted in this transaction.
The SQL standard defines two additional levels, READ UNCOMMITTED and REPEATABLE READ. In PostgreSQL READ UNCOMMITTED is treated as READ
COMMITTED, while REPEATABLE READ is treated as SERIALIZABLE.
The transaction isolation level cannot be changed after the first query or data-modification statement (SELECT, INSERT, DELETE, UPDATE,
FETCH, or COPY) of a transaction has been executed. See in the documentation for more information about transaction isolation and concur-
rency control.
The transaction access mode determines whether the transaction is read/write or read-only. Read/write is the default. When a transaction is
read-only, the following SQL commands are disallowed: INSERT, UPDATE, DELETE, and COPY FROM if the table they would write to is not a tem-
porary table; all CREATE, ALTER, and DROP commands; COMMENT, GRANT, REVOKE, TRUNCATE; and EXPLAIN ANALYZE and EXECUTE if the command they
would execute is among those listed. This is a high-level notion of read-only that does not prevent all writes to disk.
NOTES
If SET TRANSACTION is executed without a prior START TRANSACTION or BEGIN, it will appear to have no effect, since the transaction will
immediately end.
It is possible to dispense with SET TRANSACTION by instead specifying the desired transaction_modes in BEGIN or START TRANSACTION.
The session default transaction modes can also be set by setting the configuration parameters default_transaction_isolation and
default_transaction_read_only. (In fact SET SESSION CHARACTERISTICS is just a verbose equivalent for setting these variables with SET.)
This means the defaults can be set in the configuration file, via ALTER DATABASE, etc. Consult in the documentation for more information.
COMPATIBILITY
Both commands are defined in the SQL standard. SERIALIZABLE is the default transaction isolation level in the standard. In PostgreSQL the
default is ordinarily READ COMMITTED, but you can change it as mentioned above. Because of lack of predicate locking, the SERIALIZABLE
level is not truly serializable. See in the documentation for details.
In the SQL standard, there is one other transaction characteristic that can be set with these commands: the size of the diagnostics area.
This concept is specific to embedded SQL, and therefore is not implemented in the PostgreSQL server.
The SQL standard requires commas between successive transaction_modes, but for historical reasons PostgreSQL allows the commas to be omit-
ted.
SQL - Language Statements 2010-05-14 SET TRANSACTION(7)