ORA-02067: transaction or savepoint rollback required

I am performing the task of archiving the data from one database into another database. This is being achieved by using a shell script. I run the shell script to call the procedure. After running two or three hours, I am getting the following error
ORA-02067: transaction or savepoint rollback required
Even I re-ran the job I was getting the same error.
Can any one suggest me why I am getting this error and what is the possible remedial of it ?

No version number.
No operating system or hardware information.
No information as to whether both databases are on the same machine.
No information as to what the shell script does.
No information as to what the procedure does.
No information as to how communication between the databases is established.
And you want us to tell you what you are doing wrong? <g>

Similar Messages

  • Getting error ORA-02067: transaction or savepoint rollback required

    I am performing the task of archiving the data from one database into another database. This is being achieved by using a shell script. I run the shell script to call the procedure. After running two or three hours, I am getting the following error
    ORA-02067: transaction or savepoint rollback required
    Even I re-ran the job I was getting the same error.
    Can any one suggest me why I am getting this error and what is the possible remedial of it ?

    Please post this question in General Database Discussions forum.
    To get you started, here is what the documentation says about this error.
    ORA-02067:     transaction or savepoint rollback required
    Cause:     A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed.
    Action:     rollback to a previous savepoint or rollback the transaction and resubmit.

  • ORA-00604, ORA-02067

    Hi
    I am using Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit on AIX. My Database server is in shared mode and Application server is Oracle Application Server 10g Release2 (10.1.2) on AIX.
    My application is running fine on windows enviornment, but it is giving following error if it try to run this on AIX enviornment:-
    ORA-00604: error occurred at recursive SQL level 1
    ORA-02067: transaction or savepoint rollback required
    My form is generating this error, while trying to insert a row into a table.
    Can anybody suggest me, what should i do?
    Thanks
    Sandeep

    what is the code used on the form that performs this insert?
    is that the entire error?
    is there an exception when others in the code block that performs the insert?
    if there is, remove that and run again. post the entire error stack that you receive.

  • Worked Example on SET TRANSACTION, SAVEPOINT, ROLLBACK, COMMIT

    Does any one know if there is any worked examples on the use of SET TRANSACTION, SAVEPOINT, ROLLBACK, COMMIT?

    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_106a.htm#2067249
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_102a.htm#2065561

  • Container Managed XA transaction failing to rollback

              We are running two distributed instances of WL 6.0 SP1, each with their own domain,
              each accessing their own Oracle 8.1.5 database instance.
              Server 1 has the following transaction configuration:
              JDBC Transaction Pool Driver - weblogic.jdbc.oci.xa.XADataSource
              Server 2 is using the oracle thin driver, a non-XA datasource, as it's JDBC datasource.
              The JDBCTxDataSource has the attribute 'EnableTwoPhaseCommit' set to 'true'.
              The deployment descriptor's <transaction-type> is set to 'container' and the <trans-attribute>
              is set to 'required' in both of the server's session beans.
              A test is performed where server 1 calls a method on server 2, via the remote
              interface, to insert a record in server 2's database. A call is then made to
              a session bean in Server 1 to insert a record in server 1's database. In the call
              to Server 1's bean a system level error, 'EJBException', is thrown to test if
              the XA transaction driver will rollback the record inserted during the initial
              call to server 2 - it does not. However, if the method sessionContext.setRollbackOnly()
              is explicity called in the catch () block of server 1's method, where the call
              to server 2 was made, the rollback is successful on server 2.
              Is there a problem using the oracle thin driver or can the problem be related
              to the version of Oracle we are using, 8.1.5 and the fact it does not support
              JDBC 2.0? An additional note - if all goes well both data sources are successfully
              updated.
              Thanks,
              Keith Denson
              

              We are running two distributed instances of WL 6.0 SP1, each with their own domain,
              each accessing their own Oracle 8.1.5 database instance.
              Server 1 has the following transaction configuration:
              JDBC Transaction Pool Driver - weblogic.jdbc.oci.xa.XADataSource
              Server 2 is using the oracle thin driver, a non-XA datasource, as it's JDBC datasource.
              The JDBCTxDataSource has the attribute 'EnableTwoPhaseCommit' set to 'true'.
              The deployment descriptor's <transaction-type> is set to 'container' and the <trans-attribute>
              is set to 'required' in both of the server's session beans.
              A test is performed where server 1 calls a method on server 2, via the remote
              interface, to insert a record in server 2's database. A call is then made to
              a session bean in Server 1 to insert a record in server 1's database. In the call
              to Server 1's bean a system level error, 'EJBException', is thrown to test if
              the XA transaction driver will rollback the record inserted during the initial
              call to server 2 - it does not. However, if the method sessionContext.setRollbackOnly()
              is explicity called in the catch () block of server 1's method, where the call
              to server 2 was made, the rollback is successful on server 2.
              Is there a problem using the oracle thin driver or can the problem be related
              to the version of Oracle we are using, 8.1.5 and the fact it does not support
              JDBC 2.0? An additional note - if all goes well both data sources are successfully
              updated.
              Thanks,
              Keith Denson
              

  • ORA-01581: attempt to use rollback segment...

    We've started getting "ORA-01581: attempt to use rollback segment (31) new extent (3) which is being allocated" messages in our production database over the last couple of days. Of course, each time we get these the rollback segment number is different, and we are getting these randomly from different applications that connect to the same database. We are using automatic undo management, so the rollback segments are not really under our control. The action in the Oracle docs for this error message doesn't give any specific actions that we should take, but we continue to get these.
    We started to get these about the same time as we ran out of available sessions on the database (sessions = 1500 and we had 1500 open sessions). Could these be related? Could there be some open session that may be causing the rollback segment issue? Would a restart of the database fix this? Of course the max sessions issue was cleaned up two days ago but the rollback segment issue is a lingering problem.
    Any help would be appreciated. We couldn't find anything for this online and Oracle hasn't responded to our service request yet.
    Thanks,
    Bobby

    As I understand it, you can not explicitly set the size for the undo segments in automatic undo management mode. From the Concepts guide:
    "In automatic undo management mode, the system controls exclusively the assignment of transactions to undo segments, and controls space allocation for undo segments."
    It looks like we are also using the default storage options that are set when the UNDO tablespace was created. Here is the DDL used to create this tablespace:
    CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS" DATAFILE '/alpha/oradata/prod01/undotbs01.dbf' SIZE 750M REUSE AUTOEXTEND ON NEXT 25600K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs03.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 51200K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs04.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 104K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs02.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 25600K MAXSIZE 2000M

  • ORA-1650: unable to extend rollback segment

    Hi,
    We have 20 RBS's and in our production instance we got very frequent alerts related to ORA-1650: unable to extend rollback segment continuously. When I looked for select STATUS from v$rollstat; I could see most of them are with FULL status. after couple of hours they disappeared and status became online.
    How to avoid these type of alerts?
    REgards

    What version of Oracle?
    If you are 9ir2 or later, you should be going to automatic undo management. Though it won't help your 'we cannot add space' restriction. That's not an Oracle problem, that's a corporate issue.
    This problem may be caused by poor transaction design with too many processing doing too infrequent commits. That's not an Oracle problem either, that's a corporate/development issue.
    So...you don't have an Oracle problem.
    You can't stop the 1650s from occurring if you are unwilling to add space or address application issues. However, you can set up an email filter so that any emails containing ORA-01650 in the header or body get automatically sent to the trash.
    <sarcasm>
    If you can't solve a problem, then just ignore it!
    </sarcasm>

  • DAL Exception: ORA-01562: failed to extend rollback segment number 4

    Hi,
    in our application log, we got sometimes an error ORA-01562: failed to extend rollback segment number 4 and the application hangs and some transactions are blocked. checking the aler database file, we don't found this error but it's appearing often in our system.
    would you lease advise what to do to avaoid this error, or is there a script to find oracle SQl where using too much rollback segment.
    My configuration is : Oracle 10g r2 in linux SUSE.
    thank you
    Lucienot.

    Hi,
    Please refer MOS tech note *ORA-1562 and ORA-1650 Unable to Extend Rollback Segment [ID 1066542.6]*
    thanks,
    X A H E E R

  • Transaction taking default rollback segment

    Dear al,
    10.2.0.4. on solaris 10
    transaction taking default rollback segment
    set transaction use rollback segment rbs2;
    structure of rbs2:
    Create rollback segment rbs2 tablespace tempt storage (initial 1M next 1M minextents 2 maxextents 1024);
    alter ROLLBACK SEGMENT RBS2 STORAGE
    (MINEXTENTS 20
    MAXEXTENTS UNLIMITED );
    set transaction use rollback segment rbs2;
    when am running the query , am getting the below error :
    ERROR at line 3:
    ORA-01555: snapshot too old: rollback segment number 8 with name "_SYSSMU8$"
    too small
    why still the transaction is referring to system rollback segment "_SYSSMU8$" where I've explicitly set the rollback segment for the transactiom ?
    ANy idea ?
    KAI

    Thanks robert and
    Now, after setting
    undo_retention integer
    2700
    It failed with the below and now it took 20 minutes..
    ERROR at line 4:
    ORA-01555: snapshot too old: rollback segment number 9 with name "_SYSSMU9$"
    too small
    ORA-02063: preceding line from TABS2CALLS
    Elapsed: 00:20:11.40
    Please advise
    Kai

  • ORA-01554: transaction concurrency limit reached reason

    Hi Team,
    I am getting below error
    ORA-01554: transaction concurrency limit reached reason:no undo segment found with available slot params:0, 0
    Google hit says : Action: Shutdown the system, modify the INIT.ORA parameters transactions, rollback_segments or rollback_segments_required, then startup again._
    I am on 11gR2 with oracle enterprise linux. My init.ora parameters are like below
    SQL> show parameter undo;
    NAME TYPE VALUE
    undo_management string AUTO
    undo_retention integer 900
    undo_tablespace string UNDOTBS4
    SQL> show parameter rollback;
    NAME TYPE VALUE
    fast_start_parallel_rollback string LOW
    rollback_segments string
    transactions_per_rollback_segment integer 5
    SQL> show parameter transaction;
    NAME TYPE VALUE
    transactions integer 8289
    transactions_per_rollback_segment integer 5
    Any suggestion to avoid that error , without bouncing the database?
    Please Advice
    Thanks
    Edited by: user12096071 on Jul 26, 2011 3:14 PM

    user12096071 wrote:
    Hi Team,
    I am getting below error
    ORA-01554: transaction concurrency limit reached reason:no undo segment found with available slot params:0, 0
    Google hit says : Action: Shutdown the system, modify the INIT.ORA parameters transactions, rollback_segments or rollback_segments_required, then startup again._
    I am on 11gR2 with oracle enterprise linux. My init.ora parameters are like below
    SQL> show parameter undo;
    NAME TYPE VALUE
    undo_management string AUTO
    undo_retention integer 900
    undo_tablespace string UNDOTBS4
    SQL> show parameter rollback;
    NAME TYPE VALUE
    fast_start_parallel_rollback string LOW
    rollback_segments string
    transactions_per_rollback_segment integer 5
    SQL> show parameter transaction;
    NAME TYPE VALUE
    transactions integer 8289
    transactions_per_rollback_segment integer 5
    Any suggestion to avoid that error , without bouncing the database?
    Please AdviceTERMINATE session that has filled up the UNDO space.

  • ORA-25402: transaction must roll back

    I found this problem.ORA-25402: transaction must roll back
    Please introduce , how resolve problem?
    what view ? I'll able check for this problem.

    If you had a network problem it is unlikely that the client would still be connected and able to issue a rollback. I have seen this message but I cannot remember what the situation is when it occurs. What Oracle wants is for the client to issue an explicit rollback statement.
    There is a bug that produces this error unfortunately the OP did not include their Oracle version. The bug could be in all versions from 8 - 9.2.0.3 but is only confirmed to be in 9.2.0.3 where after Transaction Failover a commit or rollback incorrectly produces this error. According to the note a Select should produce this error. This would need to be a RAC system that uses transaction failover for this to apply: Note:2652886.8 Also TAF problem: Note:2652845.8
    But it seems to me you can get this error on a distributed transaction. Oracle wants the client to issue an explicit rollback so that all parties to the distributed transaction rollback. If the application terminates due to the error then RECO will rollback the transaction. If the application issues the rollback it can then continue with additional (or retry) distributed queries.
    HTH -- Mark D Powell --

  • ORA-01562: failed to extend rollback segment

    HI
    I was searching the forum for an error when i came across one of the old post regarding the same issue. The link for that post is:
    perfomance problem
    Actually i am getting an error when i run a procedure in Oracle 8i database. Error states:
    ORA-01562: failed to extend rollback segment number.....
    Now in the link i mentioned above there was a reply by JES. In the reply he recommend not to use commit after every delete in the loop. Instead use one commit after the loop. This decreased the number of commits from 175000 (5 * 35000) to 1.
    My questions is
    1) How would it reduce the number of comments?
    Can anyone explain to this point.

    sorry it should be commit rather than 'comment'
    Okay hoek i got the point but i m still confused. What my knowledge regarding rollback segment is that whenever we start a transaction using any DML a rollback segment starts to maintain unless we end the transaction using commit or rollback. So doing as
    LOOP
    DELETE.......
    DELETE......
    DELETE......
    END LOOP
    COMMIT
    will keep on increasing the size of the rollback segment. In other words rollback segment will have to keep the snapshot of all the three DML's in the loop till the commit.
    Instead if we do as
    LOOP
    DELETE.......
    COMMIT
    DELETE......
    COMMIT
    DELETE......
    COMMIT
    END LOOP
    will keep the size of the rollback segment less than the above example because we are commiting after every DML thus releasing the space before the start of the next DML.
    Don't you think the later can prevent us from ORA-01562 ?

  • ORA-20998: Transaction Failed on Headstart Utilities 6.5 installation

    Hello,
    I am having problem when running insthsu.sql script to install
    Headstart utilities 6.5. We are doing client/server approach. The
    server is Sun 450 - Oracle 8.1.7.0.0
    Designer 6i Release 4 repository was installed on the server.
    How far was the installation:
    1. Installed HST65 --> No problem found
    2. Installed HDEMO65 --> No problem found
    3. Failed on the following statement on insthsu.sql script:
    ... installing Quality Check utilities
    execute hsu_qa_app.install;
    error message:
    hsu65@devl> execute hsu_qa_app.install
    BEGIN hsu_qa_app.install; END;
    ERROR at line 1:
    ORA-20998: Transaction Failed
    ORA-06512: at "HST65.QMS$ERRORS", line 128
    ORA-06512: at "HST65.QMS_TRANSACTION_MGT", line 814
    ORA-06512: at "HSU65.CG$AIS_HSU_UTILITIES", line 39
    ORA-04088: error during execution of
    trigger 'HSU65.CG$AIS_HSU_UTILITIES'
    ORA-06512: at "HSU65.HSU_INSTALL", line 132
    ORA-06512: at "HSU65.HSU_QA_APP", line 40
    ORA-06512: at line 1
    Any idea or direction where should I go from here?
    Thanks,
    Sanny Subowo

    Ali,
    You are running into a bug in the install form. It sees the tables that you imported manually (like the message told you to do), and then complains about them. The best thing to do is change the code in the hsdinst.fmb where the check for existing objects is performed in program units CHECK_USERS:
    function hsu_objects_exist
    return boolean
    is
    cursor c_chk
    is
    select 'x'
    from user_objects
    where object_name like 'BL_%'
    -- or object_name like 'HSU_%'
    -- or object_name like 'OMR_%'
    So comment out the two lines as indicated above and recreate the fmx.
    Kind regards,
    Peter

  • ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$

    A Materalized view is scheduled to update every 12 hours . When it has tried to update it has thrown the error ...
    ORA-12008: error in materialized view refresh path
    ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$"
    too small
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 803
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 860
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 841
    ORA-06512: at line 1

    Hi,
    Can you increase the size of the UNDO Tablespace ?
    For more information, you can find on this link below:
    http://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-01555&objID=c84&dateRange=all&userID=&numResults=15
    Cheers

  • C#  TransactionOption.RequiresNew ORA-24761 Transaction Rolled Back

    Hi all,
    I am working on Web service in C# with VS 2005. I am using IIS 5.1, Oracle 10g.
    Problem:
    I used
    [WebMethod(TransactionOption = TransactionOption.RequireNew)]
    [AutoComplete]
    with each Web Method of web service. If something goes wrong inside the web method i use ContextUtil.SetAbort() to abort the transaction else ContextUtil.SetComplete()
    Now after getting some problem while executing a web method, next time when i call any web method oracle terminates the transaction passing error "ORA-24761 : Transaction rolled back". But if again, i try the same call, its got executed with no problem!
    Any kind of help, will be appreciated, its urgent.

    Hello,
    Do you have support with Oracle? If so, I would suggest opening an SR and reference bugs 5410059, 5353967, and 4432906. In some cases not using connection pooling has been a workaround.
    Regards,
    Mark

Maybe you are looking for