Roll back of single transaction
I am learning Oracle.
I just did a Point in Time recovery.
Could someone please send me a link onl how to perform a roll back of a single transaction that was previously committed. Or is that possible ?
Thanks
Hello,
If you have flashback enabled, you can recover
Here is a link you can learn and how to implement and use flashback
http://www.oracle-base.com/articles/10g/Flashback10g.php
http://arjudba.blogspot.com/2008/04/how-to-enable-flashback-database.html
More information about flashback in general can be found under oracle documentation.
http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14192/rpfbdb003.htm
Regards
Edited by: OrionNet on Jan 11, 2009 6:27 PM
Similar Messages
-
How to continue a loop after roll back callee a Transaction in SOA
Hi All,
I Have main bpel process which calls a external web service which returns set of records,
iiterate through the set, i need to store the each record in AQ Topic.
and ack each and every record after storing them in AQTopic. if the Ack fails i should roll back the previously inserted record from AQ.
I Divided the XA transaction into two parts by using "checkpoint();" .
Based on the ack status i called throw activity with Rollback transaction, i handled that using catch all in same scope.but after that process is terminating not iterating through the loop.
i used XA Datasource.
please suggest me.
Thanks Rajashekar.Hi PuneetRekhade,
Thanks for your suggestion.
After receving the ack=sucess, before storing the Record in the AQ if system crashes Data would no longer exist in Either AQ or external web service Data base .
the Record shouldn't be lost at any cost.
in my case, if the system crashes before sending the data to AQ, nothing happens because i wouldn't send the ack to the External web service.
Thanks
Raj. -
Time taken to roll back a failed transaction
One of our customers has reported that a batch transaction, which takes about 3 hours to complete, failed after 2 hours and took 14/16 hours to roll back.
Is there a rule of thumb guideline available which can predict the time taken to roll back. Does it depend upon time the transaction was running before it failed and the size of roll back data created in rollback segment.
Thanks
CheemaThis is supplement to the original question.
Will there be a significant difference between time taken to roll back in the following two situations :
1) failure is detected by the transaction and an explicit rollback statement is issued by the stored procedure performing the transaction.
2) Connection to oracle is lost and DBA kills the session
Cheema -
Oracle 9iAS is rolling back all my transactions...any idea why?
Hi Guys,
I am involved in developing a medium sized J2EE Application Running on Oracle9iAS
Develeopment Version obtained from OTN.(version 1.0.2.2a)
The backend DB is Oracle8i RDBMS.
It has Browser based web client.
It is presently having 2- stateless session beans, with one bean acting as
Session Facade(as per J2EE Blueprints 1.2)
All transactions are container managed.
Following observations are made while load testing:
1. 9iAS Server rollbacks all the transactions when number of simultaneous
users exceeds 45.
Following are the Queries:
1. Is there any restriction on the number of Concurrent Transactions on the
9iAS Server Development version.
2. Is there any restriction on the pool size of the Resource Manager(Data
base in this case) on the 9iAS Development Version.
3. Exactly what is the difference between the Development and the Proper
Production release.
4. Are there any thing to do with my RAM?
This is my data-sources.xml -
<?xml version="1.0"?>
<!DOCTYPE data-sources PUBLIC "Orion data-sources" " " target="_new">http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
<data-sources>
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="demoPool"
location="demoPool"
xa-location="jdbc/demoPool"
ejb-location="jdbc/demoPool"
connection-driver="oracle.jdbc.driver.OracleDriver"
max-connect-attempts="10"
max-connections="1000"
username="cue"
password="cue"
url="jdbc:oracle:thin:@163.122.23.104:1521:CALVYN"
inactivity-timeout="30"
</data-sources>
Thanks in advanceDo you have any more information related to this? I don't see any errors. Are you getting any other indications like a timeout or something else? Are there any database errors being recieved?
1. Is there any restriction on the number of Concurrent Transactions on the 9iAS Server Development version. No.
2. Is there any restriction on the pool size of the Resource Manager(Data base in this case) on the 9iAS Development Version. No.
3. Exactly what is the difference between the Development and the Proper Production release. The core J2EE components are the same.
4. Are there any thing to do with my RAM? Not likely.
Thanks -- Jeff -
Regarding DB adapter transactions roll back
Hi All,
In a BPEL, using while loop i'm trying to insert records in a table(business table-Oracle XE DB). If any errors happen during the insertion, it should rollback the previous insertions happened in the business table and insert the error details in the log table.
Example: Let's say 5 records need to be inserted in business table, after first two records get inserted successfully, due to invalid data, 3rd record fails to get inserted.
Things i have done,
1) I have a catch block to catch the errors
2) I have an invoke activity in the catch block to invoke the DB adapter to insert error details in log table.
3) Throw activity with bpelx:rollback to roll back the previous transactions.
Question: After the error details get inserted in log table, since i have a throw activity with bpelx rollback, all the previous DB transactions including the log table insertion is getting rolled back. I don't want my log table record insertion to be rolled back, only the records which i have already inserted successfully in the business table needs to be rolled back.
Can anyone let me know, how to handle such a situation? your response is greatly appreciated.You need to ensure that your process is working in a single transaction.
You are correctly using the XA datasource.
Next you need to ensure that you do not have a dehydration point in the process and if there is a call to another BPEL process they are in a same transaction. -
ALSB 3 roll back a transaction without sending a fault message
Hi,
I have a proxy service exposed as a web service, which has some operations that call some tuxedo systems, do some transformation of the data, etc.
When any of it's operations is invoked I have to build an XML reply in both success AND error cases. The difference between both is a response code, if the call to the backend tuxedo system responded with a stream that starts with OK then everything is fine and I build the reply and send it back, but if an error ocurred it will send back an stream that starts with ER followed by an error code, with which I will have to build the SAME XML but using this error code and send it back to the client instead as a "successful" invocation instead of sending a SOAP fault message. Also I need to roll back the whole transaction in that error case. The system works like that and it can't be changed, we are building this proxy service based on a WSDL file given to us by the partner company that invokes our service and there's lots of other clients that do it in the same way. The problem is that I haven't found a way to roll back the transaction without making the proxy service send a fault message that the client system won't understand. The "Raise error" and "Reply with failure" do roll back the transaction but both send a fault message. Is there a way to answer "successfully" to the client but make an explicit rollback?Hi,
Check the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22017.. [original link is broken] [original link is broken] [original link is broken]
You can handle the exception on your web service and model a Notification task so that you can send e-mail notification to the sender in case of exception
Regards, Anil -
Once Again: Transaction is not rolled back...
Hi all,
I'm almost at the end of my project with Toplink. but I have to solve this transaction rollback problem. Here is my previous message. any comment is more than welcome.
The problem is this, I pass 2 objects to Toplink to update in database using activeUnitOfWork.shallowMergeClone() method.
one of the updates fails then I expect everything to be rolled back within the same unitofwork. but NOT. the other object is quite well updated in database even though they are merged in the same unit of work... please HELP...
here is the log :
UnitOfWork(31228)--JTS#beforeCompletion()
UnitOfWork(31228)--#executeQuery(WriteObjectQuery(com.vnu.publitec.axis.persistence.Parameters@7a0b))
UnitOfWork(31228)--Connection(31249)--UPDATE PARAMETERS SET PARAM_VALUE = '26' WHERE (PARAM_NAME = 'TEST_PARAMETER_2')
UnitOfWork(31228)--#reconnecting to external connection pool
UnitOfWork(31228)--#executeQuery(WriteObjectQuery(com.vnu.publitec.axis.persistence.Parameters@7a06))
UnitOfWork(31228)--Connection(31249)--UPDATE PARAMETERS SET PARAM_MAX_SIZE = 666666, PARAM_COMMENTS = 'updated by new axis...', PARAM_VALUE = '18' WHERE (PARAM_NAME = 'TEST_PARAMETER_1')
UnitOfWork(31228)--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-01438: value larger than specified precision allows for this column
INTERNAL EXCEPTION: java.sql.SQLException: ORA-01438: value larger than specified precision allows for this column
...... //some more message
UnitOfWork(31228)--JTS#afterCompletion()
UnitOfWork(31228)--release unit of work
ClientSession(31229)--client released
environment information is :
J2EE Server is Oracle9iAS (9.0.3.0.0) Containers for J2EE
and following is a piece of sessions.xml file related to external transaction controller settings :
<session-type>
<server-session/>
</session-type>
<login>
<datasource>java:comp/env/jdbc/xxx</datasource>
<uses-native-sql>true</uses-native-sql>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
thanks
Erdem.Hi James,
As Erdem is not available, I am now taking care of the issue. The datasource name in session.xml refers to the one defined in OC4J data-sources.xml "ejb-location" attribute of "data-source" element. Below, I attach the relevant sections of both files
session.xml
<session>
<name>Axis_session</name>
<project-xml>AxisCDM.xml</project-xml>
<session-type>
<server-session/>
</session-type>
<login>
<datasource>java:comp/env/jdbc/AXIS_323DS</datasource>
<uses-native-sql>true</uses-native-sql>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
data-sources.xml:
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="AXIS_323DS"
location="jdbc/AXIS_323CoreDS"
xa-location="jdbc/xa/AXIS_323XADS"
ejb-location="jdbc/AXIS_323DS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="XXX"
password="XXX"
url="jdbc:oracle:oci8:@ddb"
inactivity-timeout="30"
connection-retry-interval="1"
/>
On the client we get the following exception:
com.evermind.server.rmi.OrionRemoteException: Transaction was rolled back: Error in transaction: EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-01438: value larger than specified precision allows for this column
On the server, we have implemented SessionSynchronization to monitor the transaction. afterCompletion method gets a boolean value "true" indicating that the transaction was comitted.
Any database operation that was successful before the erroneous case was saved in DB.
Thanks,
Melih -
Transaction is not Rolling Back in Stateless Session Bean
Hi,
I am using UserTransaction in Stateless Session bean .
Transaction is not rolling back.
The following code is writen in stateless session bean. In UserTransaction i am
calling Two methods of another stateless session bean.
The problem is if doJob2() method fails, doJob1() method is rolling back. These
two methods consist of SQL statement with different Connection Object from TXDataSource.And
session bean(TestSession) is set to CMT, attribute as "Required".
try{
Context ictx=new InitialContext();
TestHome home=(TestHome)ictx.lookup("TestSession");
utx = sessionCtx.getUserTransaction();
utx.begin();
TestRemote remote=home.create();
remote.doJob1();
remote.doJob2();
utx.commit();
}catch(Exception e)
try{
utx.rollback();
}catch(Exception ex)
System.out.println("unable to rollback"+ex);
if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
in catch block. but SQL statements executed thru. doJob1() are not rolling back.
what might be the reason?
thanks
Ranganath
Thanx Priscilla ,
Transaction is working.
ranganath
"Priscilla Fung" <[email protected]> wrote:
>
>In your ejb-jar.xml, you should specify <transaction-type> element to
>be "Container"
>for container-managed transaction. If you specified it to be "Bean" for
>bean-managed
>transaction, EJB ontainer will suspend the caller's transaction before
>starting
>a new transaction for your doJobX() methods. Thus, doJob1()nd doJob2()
>will be
>executing in different transactions, and thus rolling back doJob2()'s
>transaction
>will have no effect on work done and committed in doJob1()'s transaction.
>
>Regards,
>
>Priscilla
>
>
>"Ranganath" <[email protected]> wrote:
>>
>>
>>
>>I am sending config.xml,deployment descriptors, code snippet for TestSession.
>>i
>>am using weblogic6.0sp2.
>>if you need any aditional info. please let me know.
>>
>>thanks
>>ranganath
>>
>>EJB-JAR.xml
>>
>><?xml version="1.0"?>
>>
>><!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
>JavaBeans
>>1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
>>
>><ejb-jar>
>> <enterprise-beans>
>> <session>
>> <ejb-name>TestSession</ejb-name>
>> <home>com.apar.sslbridge.test.TestHome</home>
>> <remote>com.apar.sslbridge.test.TestRemote</remote>
>> <ejb-class>com.apar.sslbridge.test.TestBean</ejb-class>
>> <session-type>Stateless</session-type>
>> <transaction-type>Bean</transaction-type>
>> <resource-ref>
>> <res-ref-name>jdbc/oraclePool</res-ref-name>
>> <res-type>javax.sql.DataSource</res-type>
>> <res-auth>Container</res-auth>
>> </resource-ref>
>> </session>
>> </enterprise-beans>
>> <assembly-descriptor>
>> <container-transaction>
>> <method>
>> <ejb-name>TestSession</ejb-name>
>> <method-intf>Remote</method-intf>
>> <method-name>*</method-name>
>> </method>
>> <trans-attribute>Required</trans-attribute>
>> </container-transaction>
>> </assembly-descriptor>
>></ejb-jar>
>>
>>
>>TestSession CODE:
>>
>>
>> public void doJob1() throws RemoteException
>> {
>> Statement st = null;
>> String query=null;
>> try{
>> con=getConnection();
>> st=con.createStatement();
>> query="insert into x values("+x+++")";
>> System.out.println(query);
>> int rec=st.executeUpdate(query);
>> }catch(SQLException sqle)
>> {
>> System.out.println("SQL Exception "+sqle);
>> throw new RemoteException("RemoteException*****SQLError");
>> } catch (Exception e) {
>> System.out.println("Exception "+e);
>> throw new RemoteException("RemoteException*****GenralError");
>> }
>>}
>>
>>
>> public void doJob2()throws RemoteException
>> {
>> Connection con=null;
>> Statement st = null;
>> String query=null;
>> try{
>> con=getConnection();
>> st=con.createStatement();
>> query="insert into y values("+x+++")";
>> System.out.println(query);
>> int rec=st.executeUpdate(query);
>> }catch(SQLException sqle)
>> {
>> System.out.println("SQL Exception "+sqle);
>> throw new RemoteException("RemoteException*****SQLError");
>> } catch (Exception e) {
>> System.out.println("Exception "+e);
>> throw new RemoteException("RemoteException*****GenralError");
>>}
>>}
>>private Connection getConnection(){
>>try {
>>Connection con = StaticParams.POOL_DATASOURCE.getConnection();
>>return con;
>> } catch(Exception e) {
>> System.out.println("TestBean.getConnection() Unable to get get pool
>>connection
>>" + e);
>> }
>>}
>>
>>
>>
>>
>>"Priscilla Fung" <[email protected]> wrote:
>>>
>>>It should work if you are using TxDataSource. Could you post your
>config.xml,
>>>deployment descriptors, code snippet for TestSession?
>>>
>>>Regards,
>>>
>>>Priscilla
>>>
>>>"Ranganath" <[email protected]> wrote:
>>>>
>>>>Hi,
>>>>
>>>> I am using UserTransaction in Stateless Session bean .
>>>> Transaction is not rolling back.
>>>>
>>>>The following code is writen in stateless session bean. In UserTransaction
>>>>i am
>>>>calling Two methods of another stateless session bean.
>>>> The problem is if doJob2() method fails, doJob1() method is rolling
>>>> back. These
>>>>two methods consist of SQL statement with different Connection Object
>>>>from TXDataSource.And
>>>>session bean(TestSession) is set to CMT, attribute as "Required".
>>>>
>>>> try{
>>>> Context ictx=new InitialContext();
>>>> TestHome home=(TestHome)ictx.lookup("TestSession");
>>>> utx = sessionCtx.getUserTransaction();
>>>> utx.begin();
>>>> TestRemote remote=home.create();
>>>> remote.doJob1();
>>>> remote.doJob2();
>>>> utx.commit();
>>>> }catch(Exception e)
>>>> {
>>>> try{
>>>> utx.rollback();
>>>> }catch(Exception ex)
>>>> {
>>>> System.out.println("unable to rollback"+ex);
>>>> }
>>>> }
>>>>if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
>>>>in catch block. but SQL statements executed thru. doJob1() are not
>>rolling
>>>>back.
>>>>what might be the reason?
>>>>
>>>>thanks
>>>>Ranganath
>>>
>>
>
-
Container transaction NOT rolled back after a long period of time.
Hi, I am using Weblogic 6.1SP5 on RedHat 7.1 and I have seen an unexpected
behaviour with an MDB and I would like to know if there is any circumstance
in which a transaction is not rolled back automatically by the container
after the transaction timeout specified on MDB descriptor expired.
The fact is I have seen a thread locked for 3 entire days without any
exception being raised (the trans timeout was set to 900 seconds for
debugging porpouses)
Sadly I didn't thought on issuing a ps -ax and a netstat -np in order to see
if there was any connection active for any of the JVM threads.
As an aside note I had to throw a kill -9 to Weblogic's JVM in order to
completely stop it because using the standard "stopWeblogic.sh" script it
got stalled.
The only unusual thing that I can think of the MDB is doing is opening a
connection against a remote system via a socket.
My question is. Is it possible that a thread locked on I/O (in this case a
socket) to be out of control in terms of throwing at it a "Transaction
rolled back exception"?
I have modified my code in order to set SO_TIMEOUT on the socket just in
case the other peer hangs and never returns control. But I would like to
know the problem could be there.
I know for sure that at the time the thread stalled the other peer died
(exceptions on other MDBs trying to connect to remote system) but I expected
a "socket exception" to be thrown by the O.S. to the stalled thread instead
of having the thread waiting forever on that "open" socket.
Thanks in advance.
Ignacio.
While a tramsaction may be rolled back at the transaction timeout,
the thread is not stopped. The actual exception won't occur until
the MDB completes. If the MDB doesn't complete (as in this case),
you won't get the exception.
"Ignacio G. Dupont" <[email protected]> wrote in message news:[email protected]...
> Hi, I am using Weblogic 6.1SP5 on RedHat 7.1 and I have seen an unexpected
> behaviour with an MDB and I would like to know if there is any circumstance
> in which a transaction is not rolled back automatically by the container
> after the transaction timeout specified on MDB descriptor expired.
>
> The fact is I have seen a thread locked for 3 entire days without any
> exception being raised (the trans timeout was set to 900 seconds for
> debugging porpouses)
>
> Sadly I didn't thought on issuing a ps -ax and a netstat -np in order to see
> if there was any connection active for any of the JVM threads.
>
> As an aside note I had to throw a kill -9 to Weblogic's JVM in order to
> completely stop it because using the standard "stopWeblogic.sh" script it
> got stalled.
>
> The only unusual thing that I can think of the MDB is doing is opening a
> connection against a remote system via a socket.
>
> My question is. Is it possible that a thread locked on I/O (in this case a
> socket) to be out of control in terms of throwing at it a "Transaction
> rolled back exception"?
>
> I have modified my code in order to set SO_TIMEOUT on the socket just in
> case the other peer hangs and never returns control. But I would like to
> know the problem could be there.
>
> I know for sure that at the time the thread stalled the other peer died
> (exceptions on other MDBs trying to connect to remote system) but I expected
> a "socket exception" to be thrown by the O.S. to the stalled thread instead
> of having the thread waiting forever on that "open" socket.
>
> Thanks in advance.
>
> Ignacio.
>
>
-
Transaction - the subprocess rolling back parent JTA
According to Oracle documentation,
"if the caller partner link specifies transaction=participate and the subprocess also specifies transaction=participate, the subprocess rolls back the client JTA transaction."
But what I experience is if I just set transaction=participate for the partner link alone (and not having transaction=participate in the subprocess), when the subprocess rolls back, it rolls back parent JTA transaction also.
In fact, if we have just transaction=participate for the partner link (and not having transaction=participate in the subprocess), then the rollback in either Parent or Subprocess, is rolling back both Parent and Subprocess.
Can somebody provide the exact usage of using transaction=participate at the subprocess level?
Thanks,
JoeJoe,
You are seeing expected behaviour. Even though both flags are called "transaction" and both are set to "participate", they do different things.
By specifying transaction=participate on the partner link, you are instructing the subprocess to enlist in the transaction. When the subprocess starts, it will then enlist itself. That's all. Now if a rollback occurs, all participating processes will be rolled back.
If you specify transaction=participate at the process level, it has a different effect, and doesn't affect whether or not the transaction is rolled back or not. As I said in the previous paragraph, if the partner link specified transaction=participate, the subprocess will roll back if a rollback is issued, no matter what other settings you have.
So what effect does that setting have at the process level? According to the doc:
When transaction=participate, the process produces a fault that is not handled by fault handlers, which calls the transaction to be rolled back.
This is not exactly crystal clear, to me, anyway. In practice if this is set and your subprocess throws an unhandled fault, it triggers a rollback instead of throwing a fault as it normally would. This exception goes immediately back to the calling process since it is participating on the transaction as well.
If the property is not set, and the subprocess throws an unhandled fault, you get the normal behavior. Namely, the process will be flagged as faulted, and the calling process will wait until it gets a transaction timeout (no relation to the JTA transaction we're talking about here).
It's a simple test. Create two processes, then run it twice. Once with that property set, and one without.
The key is to remember that although they are both called "transaction=participate", the effect they have is very different. It was probably not a good move to use the same name and value like that. Hope this helps.
Regards,
Robin. -
Hii All how to roll back from CALL TRANSACTION?
or is there any BAPI for source list maintain for ME01 other than BAPI_SOURCEDETERMIN_GETSOS.
so that i can roll back ME01 updation.?hi..
you can use
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
IMPORTING
return = i_return1. -
Hi,
Needed your inputs on approach to implement a job using dbms_scheduler.
We have around 2000 schemas. Each schema has a package with 2 procedures.
The requirement is to create a single job in SYS that would loop through each schema and run the procedures at a specific time ( once a day) and send email notification on success or failure.
Job script:
BEGIN
dbms_scheduler.create_job( job_name=> 'LOAD_EACH_SCHEMA_AUDIT_DATA',
job_type=>'PLSQL_BLOCK',
job_action=>'BEGIN sys.p_loadaudit;
END;',
start_date=>systimestamp,
repeat_interval=>'FREQ=MINUTELY;INTERVAL=1',
number_of_arguments=>0,
enabled=> true,
comments=>'Job repeat interval is every 5 mins' );
END;
Note: for testing purpose i have set repeat interval to minutely.
Procedure job will be executing:
Procedure sys.p_loadaudit:
CREATE OR REPLACE
PROCEDURE p_loadaudit
AS
v_count NUMBER:= 0;
lv_error_message VARCHAR2(4000);
vstmt VARCHAR2(4000);
BEGIN
FOR i IN
( SELECT username FROM dba_users WHERE username LIKE 'ABCFIRM%'
LOOP
vstmt:= 'begin ' || i.username || '.pkg_audit_info.p_load_coa; end;';
EXECUTE immediate vstmt;
vstmt:= 'begin ' || i.username || '.pkg_audit_info.p_load_am; end;';
EXECUTE immediate vstmt;
END LOOP;
EXCEPTION
WHEN OTHERS THEN
lv_error_message := 'Error in procedure p_loadaudit: ' || SQLCODE || ' -ERROR- ' || SUBSTR(
sqlerrm,1,300) || '*' || dbms_utility.format_error_backtrace;
raise_application_error(-20002,lv_error_message);
END p_loadaudit;
Example of one schema: SCHEMA_01
create or replace
PACKAGE pkg_audit_info
AS
type cursortype
IS
ref
CURSOR;
PROCEDURE p_load_COA;
PROCEDURE p_load_AM;
END pkg_audit_info;
create or replace
PACKAGE body pkg_audit_info
AS
PROCEDURE p_load_COA
AS
BEGIN
INSERT INTO TABLE1();
EXCEPTION
WHEN OTHERS THEN
lv_error_message := 'Error in procedure pkg_audit_info.p_load_COA: ' || SQLCODE
|| ' -ERROR- ' || SUBSTR(SQLERRM,1,300) || '*' || dbms_utility.format_error_backtrace;
RAISE_application_error(-20002,lv_error_message);
END p_load_COA;
PROCEDURE p_load_AM
AS
BEGIN
INSERT INTO TABLE2();
EXCEPTION
WHEN OTHERS THEN
lv_error_message := 'Error in procedure pkg_audit_info.p_load_AM: ' || SQLCODE ||
' -ERROR- ' || SUBSTR(SQLERRM,1,300) || '*' || dbms_utility.format_error_backtrace;
RAISE_application_error(-20002,lv_error_message);
END p_load_AM;
END pkg_audit_info;
Table1 and table1 exist in schema_01.
All 2000 schemas have same package.procedures.
Due to security reasons i have removed the actual code.
I was able to execute the job successfully. However, when a schema procedure (SCHEMA_01.pkg_audit_info.p_load_COA) throws an exception, the job fails and all transaction is rolled back.
Is there a way to loop through each schema and execute the related procedures. Even if exception happens, it should rollback only for that schema and continue the other schemas in the loop?
Please let me know if there is a better way to achieve this. Is the way i am handling exceptions in the job/procedure correct?
ThanksHi,
RAISE_APPLICATION_ERROR will cause the program to exit back to the caller, even if you place it in a block within the loop, so the RAISE or RAISE_APPLICATION_ERROR instruction should be placed in your "pkg_audit_info.p_load_AM" and "pkg_audit_info.p_load_coa" procedures. This way, you can use a block inside the loop and log the error.
FOR i IN
( SELECT username FROM dba_users WHERE username LIKE 'ABCFIRM%'
LOOP
BEGIN
vstmt:= 'begin ' || i.username || '.pkg_audit_info.p_load_coa; end;';
EXECUTE immediate vstmt;
vstmt:= 'begin ' || i.username || '.pkg_audit_info.p_load_am; end;';
EXECUTE immediate vstmt;
EXCEPTION
WHEN OTHERS THEN
--> Log the error in a custom log table otherwise you will not know what happened for that schema: don't forget the username
END;
END LOOP; -
Transaction rolled back when system exception occurs.
Hello,
I understand that when a exception occurs that extends RuntimeException or RemoteException, the current transaction is rolled back. Is that also the case when the system exception is caught and dealt with?
Julien Martin.Hi Julien,
It depends whether the system exception was ever propagated back to the container. E.g. If the container-managed transaction only spans a single EJB business method and the exception is both thrown AND caught within that business method, then no, the container will not mark the tx for rollback.
However, take the case where EJBs A and B both have container-managed transactions and tx attribute TX_REQUIRED. If EJB A calls business method foo() on EJB B and foo() throws a system exception, the tx will be marked for rollback by B's container as part of the post-processing of foo(). When control returns to EJB A, the same tx is still active, but it has been marked for rollback. Even if EJB A "eats" the system exception and returns normally, it won't change the disposition of the transaction, so the tx will be rolled back by A's container.
--ken
Kenneth Saks
J2EE SDK Engineering
SUN Microsystems -
Stateless SessionBean Transaction not Rolling Back
I have a situation to create two Entity Beans within a single Transaction,
so I created a Session Bean to create the two Entity Beans.
I have the Session bean with attribute
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
And 2 Entity beans with attributes:
<persistence-type>Container</persistence-type>
<trans-attribute>Required</trans-attribute>
Inside the Session Bean I have a method which calls the create on the two
Entity Beans.
create ContactInfo(){
Phone ph = phoneHome.Create(phoneData);
Address ad = addressHome.Create(addressData);
When the secound bean fails to create (Key voilation), my transaction is not
getting rolled back.
The Phone Create did not roll back eventhough the address create failed.
Please give me some suggetion which transaction attributes to use
I am using Weblogic 6.0
For Create Exceptions , the transactions may or may not rollback. Mostly it
wont rollback. You have to set the sessionctx.setRollbackOnly() to mark it
for rollback in the catch block of the Create Exception.
Regards,
Swaminathan K.N.
santo comar <[email protected]> wrote in message
news:3b8dbb61$[email protected]..
> I have a situation to create two Entity Beans within a single Transaction,
> so I created a Session Bean to create the two Entity Beans.
>
> I have the Session bean with attribute
>
> <session-type>Stateless</session-type>
> <transaction-type>Container</transaction-type>
>
> And 2 Entity beans with attributes:
>
> <persistence-type>Container</persistence-type>
> <trans-attribute>Required</trans-attribute>
>
> Inside the Session Bean I have a method which calls the create on the two
> Entity Beans.
>
> create ContactInfo(){
> Phone ph = phoneHome.Create(phoneData);
> Address ad = addressHome.Create(addressData);
> }
>
> When the secound bean fails to create (Key voilation), my transaction is
not
> getting rolled back.
> The Phone Create did not roll back eventhough the address create failed.
> Please give me some suggetion which transaction attributes to use
>
> I am using Weblogic 6.0
>
>
>
-
MDB transaction getting silently rolled back?
I have an MDB that is doing a delete of a database record in the onMessage method.
It seems to work fine. I see no errors in the log, in fact I have some debug
statements that indicate everything was completed normally. I even do a count
sql using the same where clause and print the results and see a '0'.
However, when I check the database, the record is still there.
It seems as if the transaction is getting rolled back somehow. The MDB is transaction
required/container tx. I never setRollbackOnly anywhere.
The topic was originally published in a transaction that was rolled back, if that
makes any difference. In fact, the point of the MDB is to clean up a record that
was created during the transaction but not within the transaction.
Any help is appreciated!
ken
It turned out that the MDB was using a different connection pool than it should
have, which was pointed to an old copy of the database. So it wasn't really rolling
back, it really was deleting records as desired, just in the wrong database.
Thanks
ken
Tom Barnes <[email protected].bea.com>
wrote:
>Some random ideas:
>
>Is the app sending a delete request to the MDB, and
>the MDB acting on it, before the record is even inserted?
>
>Does the delete request have the correct row-id/PK?
>
>Is the MDB app failing without your knowledge? You
>can instrument the MDB onMessage() with a
>"try catch Throwable" to see.
>
>Is the MDB tx timing out trying to get a lock
>on the row? You can instrument the onMessage
>with timestamps to see if its taking longer than 30 seconds...
>
>Tom
>
>Ken Clark wrote:
>
>> I have an MDB that is doing a delete of a database record in the onMessage
>method.
>> It seems to work fine. I see no errors in the log, in fact I have
>some debug
>> statements that indicate everything was completed normally. I even
>do a count
>> sql using the same where clause and print the results and see a '0'.
>>
>> However, when I check the database, the record is still there.
>>
>> It seems as if the transaction is getting rolled back somehow. The
>MDB is transaction
>> required/container tx. I never setRollbackOnly anywhere.
>>
>> The topic was originally published in a transaction that was rolled
>back, if that
>> makes any difference. In fact, the point of the MDB is to clean up
>a record that
>> was created during the transaction but not within the transaction.
>>
>> Any help is appreciated!
>>
>> ken
>
Maybe you are looking for
-
so i bought 100,000 coins on the Plants vs Zombies game on the ipod touch and i did not get the coins i bought. however, they DID take my money! how can i get the coins or my money back?
-
Hi All, I have configured below point to point link with FR switch in GNS 3. below is the configuration for the senario. R1#sh run int serial 0/0 Building configuration... Current configuration : 144 bytes interface Serial0/0 no ip address encapsulat
-
JNDI Lookup for EJB3 (Bean to Bean)
Hi Forum, i've search the whole internet and two books but I could not find an answer that pleased me. I want to get a reference to an EJB3 by JNDI Lookup. With container managed dependency injection everything works fine but I have to do a little mo
-
Only text is showing in Itunes store
Anyone now?
-
Action Cam Error 513 no streaming function
Hello-- wonder if anyone else has come across this- I am paired fine on both apps however when I try to turn on live streaming the EE Action App says 'unknown error 513' and the digital display shows a warning triangle Only had it a few hours-- very