Sending trigger rows to stored procedure?

I want to put lengthy row validation logic into a PL/SQL stored procedure and send it the :NEW row from my trigger (and return a varchar2 value with results). I can't seem to do it this way:
FUNCTION My_Proc(pRow IN my_table%ROWTYPE) RETURN Varchar2
IS
BEGIN
........CODE HERE.........
END;
Now, if I call this from a trigger as such, I get a "bad bind variable" error:
vResults := My_Proc(:NEW);
How else can I do this?

Oracle team - if this cannot currently be done please consider this an enhancement request.
Passing the entire row from a trigger would allow the row validation logic to be implemented in one place.
For example a Java Stored Procedure could be implemented that could be called from java or from SQL.
This would allow the BUSINESS RULES relating to row validation (and by inference column validation) to be put into the MIDDLE TIER rather than at the back-end.
Thanks for considering this.
null

Similar Messages

Sender JDBC support the stored procedure in SQL Server 2005

Dear All,
My question here is , Sender is JDBC adpter support to call the Stored procedure in Microsoft SQL Server 2005?
I followed the below thread before posting this question
Sender JDBC Adapter Supports Stored Procedures????
In the thread Suraj response has mentioned SAP note: 941317, I checked the note, Note says it supported only ORACLE DBMS versions.
Could you please clarify about this to possibility to call the stored procedure in Microsoft SQL server 2005?
Thank you in Advance
Sateesh

Hi Sateesh,
To answer your query, Yes it does. SP call works with SQL Server 2005 as well, the SP call should be "execute SPNAME <paramas>". In the place of update statement put any junk value as mentioned in the earlier comment.
But just one thing to be noted, the select or any other query returning the desired resultset must be the first statement in youre SP returning value to the calling app. Means if there are any update, deletion or intermediate select queries to be used with in your SP, those all should be placed after the Main Select query that returns the desired resultset. Variable declarions and assignments are allowed.
But if the seq of statements in your SP are like:
@var1 Varchar
Update <tablename>....
Select * from <tablename>
Then the output of the SP is :
1 row updated
<the resultset from select>
In such cases, PI can recognise the first value returned only, that is "1 row updated" and hence the returned resultset wouldn't be seen by PI or not be passed to integration engine. Hence the update should come after the main Select.
One more interesting piece of information, even if you copy and paste the entire SP code in place of the query string of Sender JDBC adapter, that too will work with all your variable declarations, multiple queries and updates and everything. Just have to follow the above rule.
Let us know what you find.
Regards,
Suddhasatta

How send mail from Oracle stored procedure?

Hi,
I need send mail using Oracle stored procedure. Can anybody helpme with any recomendation about that, sample code or so?.
[email protected]
null

Hi Raul Martinez
utl_smtp package is available since oracle 8.1.6.
If U have a older version then U can not.
Thank U.
edwin

Sender JDBC Adapter Supports Stored Procedures????

Dear All,
I was trying to use the Sender JDBC adapter to call the Stored procedure in the Sender JDBC adapter is possible to do this???
I don't think Sender JDBC Adapter is supported to execute the Oracle Started Procedures. With my understanding only the Receiver JDBC Adapter will supported for the Stored Procedures using the message mapping Action = EXECUTE and Table = DBO.EmployeeMasterTable.
Please let me know how to achieve the below scenario.
My Scenario JDBC to RFC
Query SQL Statement:
select * from dbo.emp where flag = 'Insert' or flag = 'Update' or flag = 'Delete'
Update SQL Statement:
UPDATE dbo.emp SET flag = null WHERE flag IN ('Insert', 'Update');
DELETE dbo.emp WHERE flag = 'Delete';
In the my update statement I need to update few data flag with Insert , Update and need to delete the of the old records as mentioned above the query.
In the response mapping I am using the Action = INSERT and Table = emp.
Thanks,
Jane F.

Hi Jane,
>>My requirment is to select from the DB and update and delete needs to be done. How I need to call this stored procedure in Sender JDBC adapter.
An example of SP call is mentioned in the previous note Note 941317 - XI / PI JDBC Adapter: Known Problems / Incompatibilities
SP Code
          ---------- pkg1 ----------
CREATE PACKAGE pkg1 AS
TYPE numset_t IS TABLE OF NUMBER;
FUNCTION f1(x NUMBER) RETURN numset_t PIPELINED;
END pkg1;
CREATE PACKAGE BODY pkg1 AS
-- FUNCTION f1 returns a collection of elements (1,2,3,... x)
FUNCTION f1(x NUMBER) RETURN numset_t PIPELINED IS
BEGIN
    FOR i IN 1..x LOOP
      PIPE ROW(i);
    END LOOP;
    RETURN;
END;
END pkg1;
In sender channel mention
>> SELECT * FROM TABLE(pkg1.f1(5));
>>Is this need to be in the one stored procedure right. Can ou let me know how it should be handled in JDBC Adapter.
Yes it shoudl be a single SP. Mention a select statement as given in above example.
What is your Oracle version?
Regards
Suraj

Cannot Send Email Notification Using Stored Procedure.

Hi Friends,
I tried to execute this job scheduler...
begin
dbms_scheduler.create_job(
job_name => 'ILMS_JOB_SCHEDULE'
,job_type => 'PLSQL_BLOCK'
,job_action => 'begin ilms.check_reminder(); end; '
,start_date => SYSTIMESTAMP
,repeat_interval => 'FREQ=DAILY'
,enabled => TRUE
     ,end_date => NULL
,comments => 'Ilms job schedule for notification.');
end;
However, since the effect is too long I rescheduled the frequency to be every one minute in this set attribute...
BEGIN
DBMS_SCHEDULER.SET_ATTRIBUTE(
          name => 'ILMS_JOB_SCHEDULE'
          ,attribute => 'repeat_interval'
          ,value => 'FREQ=MINUTELY;INTERVAL=1'
DBMS_SCHEDULER.DISABLE('ILMS_JOB_SCHEDULE');
DBMS_SCHEDULER.ENABLE('ILMS_JOB_SCHEDULE');
END;
Check Reminder is the stored procedure invoked by job scheduler to check values in database columns before sending email notification to the respective recipients' email address and also the format of the email notification to be sent to the recipients...
CREATE OR REPLACE PROCEDURE check_reminder AS
NO number;
CURSOR emp_cur is
select * from pergerakan_ks where TASK_FLAG=7 and TASK_STATUS='InProgress';
emp_rec emp_cur%rowtype;
email_to varchar2(200);
default_email varchar2(200);
mesg varchar2(4000);
no_kes varchar2(100);
subj varchar2(4000);
kpi number;
crlf VARCHAR2( 2 ):= CHR( 13 ) || CHR( 10 );
BEGIN
default_email:='@abc.com.my';
FOR emp_rec in emp_cur
LOOP
if emp_rec.PKS_TKH_TERIMA is null then
dbms_output.put_line('count day ' || round(sysdate - to_date(emp_rec.pks_tkh_hantar)) || crlf || crlf);
if round(sysdate - to_date(emp_rec.pks_tkh_hantar)) >3 then
email_to:=emp_rec.pks_penghantar_id||default_email;
select b.KS_BIL_NO into no_kes from kertas_siasatan b where b.KS_ID = emp_rec.pks_ks_id;
subj:='Reminder untuk Membuat Tindakan Bagi No Kes '||no_kes;
mesg:='Reminder untuk Membuat Tindakan Bagi No Kes '||no_kes;
dbms_output.put_line('Sending email to ' || email_to || ' subject: ' || subj);
dbms_output.put_line('update old pergerakan pks_id : '||emp_rec.pks_id);
update pergerakan_ks set task_status='Done' where pks_id=emp_rec.pks_id;
dbms_output.put_line('insert new pergerakan ks : ');
insert into pergerakan_ks(pks_id,pks_ks_id,pks_km_id,pks_penghantar_id,pks_tkh_hantar,
pks_penerima_id,pks_tkh_terima,task_name,task_owner,task_status,task_flag,fb_id)
values(pks_id_seq.nextval,emp_rec.pks_ks_id,emp_rec.pks_km_id,
emp_rec.pks_penghantar_id,sysdate,
null,
null,emp_rec.task_name,
emp_rec.pks_penghantar_id,
'InProgress',6,emp_rec.fb_id);
commit;
e_mail_message(email_to,email_to,subj,mesg);
end if;
end if;
if emp_rec.PKS_TKH_TERIMA is not null then
dbms_output.put_line('emp_rec.pks_km_id ' || emp_rec.pks_km_id || crlf);
select c.KM_KPI into kpi from keluar_masuk_ks c where c.KM_ID = emp_rec.pks_km_id;
no := round(sysdate - to_date(emp_rec.pks_tkh_terima))-kpi;
dbms_output.put_line('count day - kpi' || no || crlf);
dbms_output.put_line('kpi ' || kpi || crlf);
if no = 1 then
email_to:=emp_rec.pks_penghantar_id||default_email;
select b.KS_BIL_NO into no_kes from kertas_siasatan b where b.KS_ID = emp_rec.pks_ks_id;
subj:='Reminder untuk Membuat Tindakan Bagi No Kes '||no_kes;
mesg:='Reminder untuk Membuat Tindakan Bagi No Kes '||no_kes;
dbms_output.put_line('Sending email to ' || email_to || ' subject: ' || subj);
email_to:=emp_rec.task_owner||default_email;
subj:='Reminder untuk Membuat Tindakan Bagi No Kes '||no_kes;
mesg:='Reminder untuk Membuat Tindakan Bagi No Kes '||no_kes;
dbms_output.put_line('Sending email to ' || email_to || ' subject: ' || subj);
e_mail_message(email_to,email_to,subj,mesg);
e_mail_message(email_to,email_to,subj,mesg);
end if;
if no = 3 then
select b.KS_BIL_NO into no_kes from kertas_siasatan b where b.KS_ID = emp_rec.pks_ks_id;
email_to:=emp_rec.task_owner||default_email;
subj:='Reminder untuk Membuat Tindakan Bagi No Kes '||no_kes;
mesg:='Reminder untuk Membuat Tindakan Bagi No Kes '||no_kes;
dbms_output.put_line('Sending email to ' || email_to || ' subject: ' || subj);
e_mail_message(email_to,email_to,subj,mesg);
end if;
end if;
END LOOP;
END;
E_mail_message is the stored procedure invoked by the check_reminder to tell scheduler information of the connection and the email address of the recipients...
CREATE OR REPLACE procedure
e_mail_message
from_name in varchar2,
to_name in varchar2,
subject in varchar2,
message in varchar2
is
l_mailhost VARCHAR2(64);
l_from VARCHAR2(64);
l_to VARCHAR2(64);
crlf VARCHAR2( 2 ):= CHR( 13 ) || CHR( 10 );
l_mail_conn UTL_SMTP.connection;
mesg VARCHAR2( 4000 );
BEGIN
select a.SERVER into l_mailhost from email_setting a where a.SERVER is not null;
select a.USERNAME into l_from from email_setting a where a.SERVER is not null;
--UTL_SMTP.open_data(l_mail_conn);
mesg:= 'Date: ' || TO_CHAR( SYSDATE, 'dd Mon yy hh24:mi:ss' ) || crlf ||
'From: <'||l_from||'>' || crlf ||
'Subject: ' ||subject|| crlf ||
'To: '||to_name || crlf || '' || crlf ;
mesg:=mesg||message;
l_mail_conn := UTL_SMTP.open_connection(l_mailhost, 25);
UTL_SMTP.helo(l_mail_conn, l_mailhost);
UTL_SMTP.mail(l_mail_conn, l_from);
UTL_SMTP.rcpt(l_mail_conn, to_name);
UTL_SMTP.data(l_mail_conn, mesg);
UTL_SMTP.quit(l_mail_conn);
END;
I tried to execute to execute the e_mail_message procedure but received this error. Also, no notification sent to the email address...
ORA-29279: SMTP permanent error: 501 5.1.3 Invalid address
ORA-06512: at "SYS.UTL_SMTP", line 21
ORA-06512: at "SYS.UTL_SMTP", line 99
ORA-06512: at "SYS.UTL_SMTP", line 241
ORA-06512: at "ILMS.E_MAIL_MESSAGE", line 33
ORA-06512: at line 13
Please help so that I can receive the email notification into my email...thanks in advance for your time..

user13281540 wrote:
ORA-29279: SMTP permanent error: 501 5.1.3 Invalid address
ORA-06512: at "SYS.UTL_SMTP", line 21
ORA-06512: at "SYS.UTL_SMTP", line 99
ORA-06512: at "SYS.UTL_SMTP", line 241
ORA-06512: at "ILMS.E_MAIL_MESSAGE", line 33
ORA-06512: at line 13This is not an Oracle error - this is the mail server saying "+hey, I don't like that e-mail address you are supplying, I'm not accepting it!+".
If you look at RFC821 (Request For Comments memo 821 describes the SMTP specifications), you'll see that the sender and recipient needs to be supplied in the format +<[email protected]>+, e.g. +<[email protected]>+.
I have found that not all SMTP servers are equal in this regard. Some may insist on the brackets around the address, some may not.
You need to confirm the format of the addresses you use in the "+MAIL FROM+" and "+RCPT TO+" commands.. and ensure that these formats are accepted by your SMTP server - and if not, change your code to use an acceptable format.
The easiest way to do this is using telnet - and interacting directly and manually with the server. SMTP is a clear text protocol and easy to use manually. Try it. It is the best way to test SMTP interaction and validate the approach and SMTP commands and arguments used by your code.

How can I use a button to trigger a SQL Stored Procedure?

I have a stored procedure (UpdateAdsUsers) that performs updates on multiple tables all tied together with one
parameter - @username
(I'm using DWCS5, SQL SERVER 2008, ASP VB)
UPDATE users SET defaultview='0' WHERE user_name=@username
UPDATE db_settings SET valuestr='MM/DD/YYYY' WHERE keyword='dateformat' AND user_name=@username
UPDATE db_settings SET valuestr='Y' WHERE keyword='COPY_MSG_VIA_EMAIL' AND user_name=@username
UPDATE db_settings SET valuestr='4' WHERE keyword='web_download_rend' AND user_name=@username
UPDATE db_settings SET valuestr='Y' WHERE keyword='cpy_confirm' AND user_name=@username
UPDATE db_settings SET valuestr='WLPG:12' WHERE keyword='INITIAL_ASSETS' AND user_name=@username
UPDATE db_settings SET valuestr='20' WHERE keyword='thumb_disp_row' AND user_name=@username
UPDATE db_settings SET valuestr='20' WHERE keyword='text_disp_row' AND user_name=@username
UPDATE db_settings SET valuestr='5' WHERE keyword='para_disp_row' AND user_name=@username
UPDATE db_settings SET valuestr='a.editorial.company_name' WHERE keyword='sortorder1' AND user_name=@username
UPDATE db_settings SET valuestr='a.editorial.title' WHERE keyword='sortorder2' AND user_name=@username
UPDATE db_settings SET valuestr='a.editorial.production_type' WHERE keyword='sortorder3' AND user_name=@username
UPDATE tnailview_fields SET rendition='1', first_field='company_name', second_field='title', third_field='adsx_type', fourth_field='adsx_status' WHERE user_name=@username
UPDATE textview_fields SET rendition='1', first_field='company_name', second_field='title', third_field='title_desc', fourth_field='production_type', fifth_field='audio_summary', sixth_field='totalruntime', seventh_field='adsx_type', eighth_field='adsx_status' WHERE user_name=@username
UPDATE paraview_fields SET rendition='1', first_field='company_name', second_field='title', third_field='title_desc', fourth_field='production_type', fifth_field='audio_summary', sixth_field='totalruntime', seventh_field='adsx_type', eighth_field='adsx_status' WHERE user_name=@username
SELECT * FROM adsx_preferences WHERE user_name=@username
This functions perfectly in SQL.
Using Dreamweaver CS5, I've added the Procedure as a Command (ADS_User) with the one variable (@username).
<%
set ADS_User = Server.CreateObject("ADODB.Command")
ADS_User.ActiveConnection = MM_ADSX_STRING
ADS_User.CommandText = "dbo.UpdateAdsUser"
ADS_User.Parameters.Append ADS_User.CreateParameter("@RETURN_VALUE", 3, 4)
ADS_User.Parameters.Append ADS_User.CreateParameter("@username", 129, 1,32,ADS_User__username)
ADS_User.CommandType = 4
ADS_User.CommandTimeout = 0
ADS_User.Prepared = true
ADS_User.Execute()
%>
In a perfect world, either an image click or a form submit would run the procedure. The parameter (@username) is currently sent to the page as a URL Querystring of the same name.
I'm sure it's something obvious, but I'm new.
Thanks in advance

I'm not sure what your question is. Is this currently failing? Or are you not able to figure out how to send the username to the script page? You really just need to create a form and pass the value in a form field.
>The parameter (@username) is currently sent to
>the page as a URL Querystring of the same name.
Never use a querystring to update data. It is too dangerous. Use the post method instead.

Issue with sending mail through java stored procedure in Oracle

Hello
I am using Oracle 9i DB. I created a java stored procedure to send mail using the code given below. The java class works fine standalone. When its run from Java, mail is sent as desired. But when the java stored procedure is called from pl/sql "Must issue a STARTTLS command first" error is thrown. Please let me know if am missing something. Tried the same code in 11.2.0.2 DB and got the same error
Error:
javax.mail.MessagingException: 530 5.7.0 Must issue a STARTTLS command first. va6sm31201010igc.6
Code for creating java stored procedure: (T1 is the table created for debugging)
==================================================
create or replace and compile java source named "MailUtil1" AS
import java.util.Enumeration;
import java.util.Properties;
import javax.mail.Message;
import javax.mail.Session;
import javax.mail.Transport;
import javax.mail.internet.InternetAddress;
import javax.mail.internet.MimeMessage;
public class MailUtil1 {
public static void sendMailwithSTARTTLS(String host, //smtp.projectp.com
String from, //sender mail id
String fromPwd,//sender mail pwd
String port,//587
String to,//recepient email ids
String cc,
String subject,
String messageBody) {
try{
Properties props = System.getProperties();
props.put("mail.smtp.starttls.enable", "True"); // added this line
props.put("mail.smtp.host", host);
props.put("mail.smtp.user", from);
props.put("mail.smtp.password", fromPwd);
props.put("mail.smtp.port", port);
props.put("mail.smtp.auth", "true");
#sql { insert into t1 (c1) values ('1'||:host)};
Session session = Session.getDefaultInstance(props, null);
MimeMessage message = new MimeMessage(session);
message.setFrom(new InternetAddress(from));
#sql { insert into t1 (c1) values ('2')};
InternetAddress[] toAddress = new InternetAddress[1];
// To get the array of addresses
for( int i=0; i < toAddress.length; i++ ) { // changed from a while loop
toAddress[i] = new InternetAddress(to);
//System.out.println(Message.RecipientType.TO);
for( int i=0; i < toAddress.length; i++) { // changed from a while loop
message.addRecipient(Message.RecipientType.TO, toAddress);
if (cc!=null) {
InternetAddress [] ccAddress = new InternetAddress[1];
for(int j=0;j<ccAddress.length;j++){
ccAddress[j] = new InternetAddress(cc);
for (int j=0;j<ccAddress.length;j++){
message.addRecipient(Message.RecipientType.CC, ccAddress[j]);
message.setSubject(subject);
message.setText(messageBody);
message.saveChanges();
#sql { insert into t1 (c1) values ('3')};
Enumeration en = message.getAllHeaderLines();
String token;
while(en.hasMoreElements()){
token ="E:"+en.nextElement().toString();
#sql { insert into t1 (c1) values (:token)};
token ="ConTyp:"+message.getContentType();
#sql { insert into t1 (c1) values (:token)};
token = "Encod:"+message.getEncoding();
#sql { insert into t1 (c1) values (:token)};
token = "Con:"+message.getContent();
#sql { insert into t1 (c1) values (:token)};
Transport transport = session.getTransport("smtp");
#sql { insert into t1 (c1) values ('3.1')};
transport.connect(host, from, fromPwd);
#sql { insert into t1 (c1) values ('3.2')};
transport.sendMessage(message, message.getAllRecipients());
#sql { insert into t1 (c1) values ('3.3')};
transport.close();
#sql { insert into t1 (c1) values ('4')};
catch(Exception e){
e.printStackTrace();
String ex= e.toString();
try{
#sql { insert into t1 (c1) values (:ex)};
catch(Exception e1)
Edited by: user12050615 on Jan 16, 2012 12:18 AM

Hello,
Thanks for the reply. Actually I have seen that post before creating this thread. I thought that I could make use of java mail to work around this problem. I created a java class that succesfully sends mail to SSL host. I tried to call this java class from pl-sql through java stored procedure. That did not work
So, is this not supported in Oracle ? Please note that I have tested this in both 9i and 11g , in both the versions I got the error. You can refer to the code in the above post.
Thanks
Srikanth
Edited by: user12050615 on Jan 16, 2012 12:17 AM

Retreiving multiple rows with stored procedures

Hi,
I'm having a little problem over here. I need to retreive some data (from an oracle db) via stored procedures. But I don't know how I can retreive multiple rows because when I execute a stored procedure which gives more dan 1 row back, Jave throws an exception.
If someone could show me an example (or url) from how it should be done, it will be very much appreciated :-)
Thanks in advance.

A collection of (mostly) fully working example programs is provided by Oracle.
http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/index.html
I think what you're looking for it the RefCursor example, under "JDBC Basic Samples"

Sending data to mssql stored procedure that accepts variable of text data

Hi all
i have a stored procedure in mssql 2000 whole input parameter is of type text
how can i send data of type string from java class while calling storedprocedure using callable statement
if ui use setString() function it gives an exception that data will be trunctated
com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would be truncated.
     at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
     at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.sendExecute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(Unknown Source)
     at com.clearcube.util.DMLLayer.processClientRequest(DMLLayer.java:49)
     at com.clearcube.discovery.PushDiscoveryHandler.init(PushDiscoveryHandler.java:90)
     at com.clearcube.discovery.PushDiscoveryController$1.run(PushDiscoveryController.java:113)
     at java.util.TimerThread.mainLoop(Unknown Source)
     at java.util.TimerThread.run(Unknown Source)
c
if any one have solution to this problem plz reply me

my stored procedure accepts input of type text
i use text type becouse nvarchar is not enough to
place data.
and i want to send data that is greater than the
length of varcharUnder setString in the API:
"The driver converts this to an SQL VARCHAR or LONGVARCHAR value (depending on the argument's size relative to the driver's limits on VARCHAR values) when it sends it to the database."
I am not sure what you should use then? Maybe setCharacterStream?

Return Rows from Stored Procedure - My 1st Attempt

Hi Everyone,
The code below compiles with error 'Error(11,1): PLS-00103: Encountered the symbol "/" '.
I'm using SYSDATE in this example for simplicity. The real procedure will do much more.
Thank You in Advance for Your Help,
Lou
create or replace
PACKAGE pkg_Search
AS
TYPE CUSTOM_REF_CURSOR IS REF CURSOR;
PROCEDURE My_Procedure (
arg_Cursor IN OUT CUSTOM_REF_CURSOR);
END;
/ -- LINE 11
CREATE OR REPLACE PACKAGE BODY pkg_Search
AS
PROCEDURE My_Procedure (
arg_Cursor IN OUT CUSTOM_REF_CURSOR)
IS
BEGIN
OPEN arg_Cursor FOR
SELECT sysdate FROM DUAL;
END;
END;
/

copy the spec and the body separately in SQL*Plus and you're fine
SQL> create or replace
2 PACKAGE pkg_Search
3 AS
4 TYPE CUSTOM_REF_CURSOR IS REF CURSOR;
5 PROCEDURE My_Procedure (
6 arg_Cursor IN OUT CUSTOM_REF_CURSOR);
7 END;
8 /
Package created.
SQL> CREATE OR REPLACE PACKAGE BODY pkg_Search
2 AS
3 PROCEDURE My_Procedure (
4 arg_Cursor IN OUT CUSTOM_REF_CURSOR)
5 IS
6 BEGIN
7 OPEN arg_Cursor FOR
8 SELECT sysdate FROM DUAL;
9 END;
10 END;
11 /
Package body created.

Problem in executing Stored Procedure from Trigger

Hi,
Case1.
I am executing a stored procedure form a trigger. The stored procedure is not executing fully.
Case 2.
But when when I execute Stored Procedure alone it is executing.
CREATE OR REPLACE TRIGGER mhubadmin.call_proc_ratesheet_new
after INSERT OR delete ON mhubadmin.pvt_br_ratesheet
FOR EACH ROW
declare
var_orgid number;
begin
if inserting then
select org_child_id into var_orgid from business_relationship where br_id=:new.br_id;
mhubadmin.proc_ratesheet_new(var_orgid);
else
select org_child_id into var_orgid from business_relationship where br_id=:old.br_id;
mhubadmin.proc_ratesheet_new(var_orgid);
end if;
end;
CREATE OR REPLACE PROCEDURE proc_ratesheet_new(var_orgid in number)
IS
cursor c3 is select distinct(purs.user_id) from hubuser hu
inner join PVT_USER_RATESHEET purs on hu.USER_ID=purs.USER_ID
               where hu.ORG_ID=var_orgid;
cursor c1(varUser_id number) is select purs.user_id,purs.ratesheet_id from hubuser hu
inner join PVT_USER_RATESHEET purs on hu.USER_ID=purs.USER_ID
               where hu.ORG_ID=var_orgid and purs.USER_ID=varUser_id;
cursor c2(varUser_id number) is select hu.user_id,pbr.ratesheet_id from HUBUSER hu
                         inner join BUSINESS_RELATIONSHIP br on hu.ORG_ID=br.ORG_CHILD_ID
                         inner join PVT_BR_RATESHEET pbr on br.BR_ID=pbr.BR_ID
                              where hu.user_id in(select distinct(purs.USER_ID) from hubuser hu
                                   inner join PVT_USER_RATESHEET purs
                                                                 on hu.USER_ID=purs.USER_ID
                                             where hu.ORG_ID=var_orgid) and hu.user_id=varUser_id;
foundFlag boolean;
incrFound integer;
insertFound integer;
deleteFound integer;
str varchar2(4000);
BEGIN
     incrFound:=0;
     insertFound:=0;
     for c3var in c3 loop
for c2var in c2(c3var.user_id) loop
          insert into test values ('Step3:'||c2var.user_id);
          foundFlag:=false;
          for c1var in c1(c3var.user_id) loop
               if c2var.ratesheet_id=c1var.ratesheet_id then
                    foundFlag:=true;
                         incrFound:=incrFound+1;
                         exit;
                    end if;
               end loop;
               if foundFlag=False then
               --insert into pvt_user_ratesheet (username_ratesheet_id,user_id,ratesheet_id) values (SEQ_USER_RATESHEET.nextval,c3var.user_id,c2var.ratesheet_id);
               dbms_output.put_line('Inserted for user :'||c3var.user_id||' is - ratesheet :'||c2var.ratesheet_id);
               insertFound:=insertFound+1;
               end if;
          end loop;
end loop;
     commit;
     incrFound:=0;
     deleteFound:=0;
     for c3var in c3 loop
          for c1var in c1(c3var.user_id) loop
          foundFlag:=false;
          for c2var in c2(c3var.user_id) loop
                    if c1var.ratesheet_id=c2var.ratesheet_id then
                    foundFlag:=true;
                    incrFound:=incrFound+1;
                    exit;
                    end if;
               end loop;
               if foundFlag=False then
               --delete from pvt_user_ratesheet where user_id=c3var.user_id and ratesheet_id=c1var.ratesheet_id;
                    --dbms_output.put_line('Deleted for userid:'||c3var.user_id||' for ratesheet :'||c1var.ratesheet_id);
                    deleteFound:=deleteFound+1;
               end if;
          end loop;
end loop;
     commit;
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.put_line (SQLCODE||' '|| SQLERRM);
END;
Regards,
Mathew

In general, I would suggest that you only catch errors that you can handle reasonably. If you know that a SELECT INTO might return 0 rows for example, handle the NO_DATA_FOUND exception. Having a WHEN OTHERS, particularly without re-raising the exception, only serves to hide the source of the problem. I would much rather that my code fail quickly and explicitly than hope that I see an error message in the output and that other code doesn't start failing because the system wasn't left in an appropriate state.
As Mark suggests, you may choose to implement a comprehensive logging framework using autonomous transactions, in which case a WHEN OTHERS would be reasonable, but you would still want to propagate exceptions you cannot handle.
If you see a WHEN OTHERS clause and there is no RAISE, you probably have an error waiting to happen.
Justin

Sender JDBC Adapter - Stored procedure

Hello all, I just read a lot of topics in this forum about this subject.
I found two indications in contracdictions in the documentation :<a href="http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/frameset.htm">Configuring the Sender JDBC Adapter</a>
1. Concerning Query SQL Statement
You have the following options:
● Specify a valid SQL SELECT statement to select the data to be sent from the specified database.
● Specify an SQL EXECUTE statement to execute a stored procedure, which contains exactly one SELECT statement.
2. Concerning Update SQL Statement :
This is recommended if the data has not only been read, but also changed by a stored procedure entered under Query SQL Statement.
It is ambigous, isn't it ?
My question is simple :
Does somebody already use Sender JDBC Adapter with Stored procedure as Select statement including many steps :
- update actions on database
- select query to return data to XI adapter
(Update statement stay empty or with value <TEST>.
To provide more information, I have a reference table to read. But this reference table must be updated by a stored procedure before being able to be read accordingly.
So As I can't do both process with Sender Adapter (call a procedure and execute a select statement) => I want to include both actions (updates and select) in an alone stored procedure.
Could I get wanted data as a resultset ?

Hi,
>><i>Update statement stay empty or with value <TEST>.</i>
It should be <TEST> if you do not want an Update to happen.
Regarding Sender JDBC adapter with stored procedures, which DB are you trying to access. Sender JDBC adapter does not support Oracle Stored Procedures as they return Cursors and Sender JDBC adapter can deal with only Resultset.
As for executing both Update and Select in the SP, though I havent tried, this should surely be possible.
Regards,
Bhavesh

Send char to stored procedure.

Hello!
I use the methods in the class CallableStatement to send
parameters to a stored procedure in a MySQL database. i.e.
cstmt.setString(1, "HELLO!");
But what should i do if i want to send a char?
The type in the MySQL database is CHAR(1).
There is no setChar method in CallableStatement.
Thank you.

Just use setString() here too. If the string you provide is to long for the CHAR[x] type, an error should araise. If the string is to short, the JDBC driver should padd with spaces at the end of the string to make it fit.
- Roy

Parent-Child Table Update via Single Stored Procedure

Uses: Oracle 9i Server via a Remote Connection with restriction, Oracle 9i client, .NET 2.0+System.Data.Oracle namespace, Delphi+BDE;
I have an entry form which consists of a parent and a child table. I'm so keen in knowing whether there is any possibilities of updating the records via a single stored procedure? I mean if parent have a single record and corresponding to it, child have few records (more than 1 rows). I need to take the parent's value and child's value send it to the stored procedure and update it.
Regards,

The entry form gets the raw data from the user. So yes the data is captured front end but not updated nor processed. Once the user clicks "Save" or what ever the values are taken to the SP. In the SP the operations are done either as update or insert. Lets concentrate on Inserts only at the moment.
I.e. there are 2 tables as:
tbl_Payment(_PaymentID_, PaymentMode,PaymentDate, TotalPaymentValue);
tbl_PaymentAccount(_PaymentID,AccountID_,PaymentValue);
So the form has a top part which is bounded to the Parent Table which is "tbl_Payment" to few text boxes, and below it has a Datagrid, bounded to Child Table which is "tbl_PaymentAccount". And assume the the Single Stored Procedure as "sp_payment_addchg".
I can pass newly entered values to the SP as:
Command.Text = "sp_payment_addchg";
/*so all the parent table bounded values are updated as*/
Command.Parameter[0].value = text1.text;
Command.Parameter[1].value = text2.text;
and so on
Since the DataGrid may have multiple rows, I cant figure it out how to get those rows into a single parameter.
Regards,

How to improve stored procedure performance?

hi,
Suppose I have a stored procedure which contains 30 insert/update statements. How do I know Stored Procedure is slowly running or don't have any performance issue? how to improve performance?
Thanks in advance.
Anujit Karmakar Sr. Software Engineer

Stored Procedures Optimization Tips
Use stored procedures instead of heavy-duty queries.
This can reduce network traffic, because your client will send to server only stored procedure name (perhaps with some parameters) instead of large heavy-duty queries text. Stored procedures can be used to enhance security and conceal underlying data objects
also. For example, you can give the users permission to execute the stored procedure to work with the restricted set of the columns and data.
Include the SET NOCOUNT ON statement into your stored procedures to stop the message indicating the number of rows affected by a Transact-SQL statement.
This can reduce network traffic, because your client will not receive the message indicating the number of rows affected by a Transact-SQL statement.
Call stored procedure using its fully qualified name.
The complete name of an object consists of four identifiers: the server name, database name, owner name, and object name. An object name that specifies all four parts is known as a fully qualified name. Using fully qualified names eliminates any confusion about
which stored procedure you want to run and can boost performance because SQL Server has a better chance to reuse the stored procedures execution plans if they were executed using fully qualified names.
Consider returning the integer value as an RETURN statement instead of an integer value as part of a recordset.
The RETURN statement exits unconditionally from a stored procedure, so the statements following RETURN are not executed. Though the RETURN statement is generally used for error checking, you can use this statement to return an integer value for any other reason.
Using RETURN statement can boost performance because SQL Server will not create a recordset.
Don't use the prefix "sp_" in the stored procedure name if you need to create a stored procedure to run in a database other than the master database.
The prefix "sp_" is used in the system stored procedures names. Microsoft does not recommend to use the prefix "sp_" in the user-created stored procedure name, because SQL Server always looks for a stored procedure beginning with "sp_"
in the following order: the master database, the stored procedure based on the fully qualified name provided, the stored procedure using dbo as the owner, if one is not specified. So, when you have the stored procedure with the prefix "sp_" in the
database other than master, the master database is always checked first, and if the user-created stored procedure has the same name as a system stored procedure, the user-created stored procedure will never be executed.
Use the sp_executesql stored procedure instead of the EXECUTE statement.
The sp_executesql stored procedure supports parameters. So, using the sp_executesql stored procedure instead of the EXECUTE statement improve readability of your code when there are many parameters are used. When you use the sp_executesql stored procedure to
executes a Transact-SQL statements that will be reused many times, the SQL Server query optimizer will reuse the execution plan it generates for the first execution when the change in parameter values to the statement is the only variation.
Use sp_executesql stored procedure instead of temporary stored procedures.
Microsoft recommends to use the temporary stored procedures when connecting to earlier versions of SQL Server that do not support the reuse of execution plans. Applications connecting to SQL Server 7.0 or SQL Server 2000 should use the sp_executesql system
stored procedure instead of temporary stored procedures to have a better chance to reuse the execution plans.
If you have a very large stored procedure, try to break down this stored procedure into several sub-procedures, and call them from a controlling stored procedure.
The stored procedure will be recompiled when any structural changes were made to a table or view referenced by the stored procedure (for example, ALTER TABLE statement), or when a large number of INSERTS, UPDATES or DELETES are made to a table referenced by
a stored procedure. So, if you break down a very large stored procedure into several sub-procedures, you get chance that only a single sub-procedure will be recompiled, but other sub-procedures will not.
Try to avoid using temporary tables inside your stored procedure.
Using temporary tables inside stored procedure reduces the chance to reuse the execution plan.
Try to avoid using DDL (Data Definition Language) statements inside your stored procedure.
Using DDL statements inside stored procedure reduces the chance to reuse the execution plan.
Add the WITH RECOMPILE option to the CREATE PROCEDURE statement if you know that your query will vary each time it is run from the stored procedure.
The WITH RECOMPILE option prevents reusing the stored procedure execution plan, so SQL Server does not cache a plan for this procedure and the procedure is recompiled at run time. Using the WITH RECOMPILE option can boost performance if your query will vary
each time it is run from the stored procedure because in this case the wrong execution plan will not be used.
Use SQL Server Profiler to determine which stored procedures has been recompiled too often.
To check the stored procedure has been recompiled, run SQL Server Profiler and choose to trace the event in the "Stored Procedures" category called "SP:Recompile". You can also trace the event "SP:StmtStarting" to see at what point
in the procedure it is being recompiled. When you identify these stored procedures, you can take some correction actions to reduce or eliminate the excessive recompilations.
http://www.mssqlcity.com/tips/stored_procedures_optimization.htm
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

Sending trigger rows to stored procedure?

Similar Messages

Maybe you are looking for