OCITransCommit() returns ORA-01013 for correctly committed transaction

I had the following issue which seems to me a critial bug in Oracle 11g:
Breaking an oracle transaction asynchronously with OCIBreak() while transaction is being committed with OCITransCommit() did result in a correctly committed transaction on the database server. However OCITransCommit() returned ORA-01013 (user requested cancel of current operation) which is inconsistent. It should never happen that the transaction is correctly committed and OCITransCommit() returns anything other than OCI_SUCCESS.
My assumption is that the transaction is only committed on the database server if the OCITransCommit() returns OCI_SUCCESS. Or is this assumption not always correct?
Oracle version 11.2.0.3.0 64bit (Linux)

As Karthick says, perhaps the Call Interface forum is a better place to ask.
However, as a guess on my part (I've rarely had a need to go directly into OCI calls) from what I know of the internal workings of transactions on Oracle, the COMMIT operation is an atomic (if that's the right word to use here) operation. When you issue a COMMIT from your code, it doesn't go off to the database, do loads of work committing your data and writing it to the disks etc. before execution is returned to your code, it is a very basic instruction to the database to commit the data, which then goes off and does that in the background, whilst execution is returned immediately to the calling code, and Oracle in the background can take it's time getting the data written, and can present the data to your session and others, as if it is actually on the tables. This is all handled using the SCN and the logs internally and users don't have to worry about it (usually) because it all appears on the front end as though the data exists and is written on the tables.
So, I'm curious as to how you (or the OCI calls) are managing to issue a "break" to try and break a commit from happening. Without seeing code it's hard to see how you are testing this.
I've just looked up the documentation for TransCommit...
http://docs.oracle.com/cd/E11882_01/appdev.112/e10646/oci17msc006.htm#LNOCI13112
and I see you have the option of "Waiting" for the LGWR to write the transaction to the online redo logs, so that's a possible scenario for breaking, though I imagine you'd have to get in quickly with the break from another thread if the one thread is waiting for the commit.
Intersting part of the docs...
>
Under normal circumstances, OCITransCommit() returns with a status indicating that the transaction has either been committed or rolled back. With global transactions, it is possible that the transaction is now in doubt, meaning that it is neither committed nor terminated. In this case, OCITransCommit() attempts to retrieve the status of the transaction from the server. The status is returned.
>
Still, it would be interesting to see the test code to reproduce this.... just my morbid curiosity for low level coding.... ;)

Similar Messages

BSW% is not considered for correcting the transactional quantity

I solicit a little help from the Group. We have a Crude Vendor which is also in SAP platform . They have implemeted TSW and now Crude delivery tickets are generated from System.
On scrutinty of ticket It is observed taht BS&W percentage is not considered while calulating quantities in Transaction UOM.
Transaction code : O3QCITEST.
Conv. Group = ZCDR.=53&54A 15 °C CRUDE OIL
UoM Group = CRD.=L/L15/KG/BB6
Transaction Quantity = 100 L.
Material temp = 30 deg-C
Test temp = 15 Deg-C
Test relative density = 870 KGV.
With the above data if you put BSW% = 0, then additional quantities calculated are 0.622 BB6, 85.938 KG, 98.779 L15 , 100 L.
if you put BSW% = 0.5, then additional quantities are 0.618 BB6, 85.508
KG, 98.285 L15 , 100 L.
From above it is clear that the additional quantities in all units except in "L" change whenever the BSW% changes. This shows that BSW% is not considered in calculating the "L" quantity.
In actual practice BSW correction should happen for Transactional Quantity also.
If you have any solution for the above scenarion . please suggest.for necessary correction.
regards
Dipak
[email protected]

Dear Vishnu
You r right . Standard SAP behaves that way only. We modified badi OIB_QCI_ROUND_QTY
method: IF_EX_OIB_QCI_ROUND_QTY~ROUND_QTY
coding atatched.
Anyway thanks for reply.
METHOD IF_EX_OIB_QCI_ROUND_QTY~ROUND_QTY .
Local Data
TYPES: T_CTPARAM TYPE OIB_A10,
         T_ADQNT TYPE OIB_A05.
DATA: S_CTPARAM TYPE OIB_A10,
         S_ADQNT TYPE OIB_A05,
         S_ADQNTN TYPE OIB_A05.
DATA : L_BSW(72) TYPE C.
DATA: W_PAR_FLTP TYPE OIB_A10-PAR_FLTP,
        WF_BSW     TYPE OIB_A10-PAR_FLTP .
DATA: IT_PARAM TYPE STANDARD TABLE OF T_CTPARAM,
        IT_ADQNT TYPE STANDARD TABLE OF T_ADQNT,
        IT_ADQNTN TYPE STANDARD TABLE OF T_ADQNT.
DATA: W_TABIX TYPE SY-TABIX.
DATA: W_DIMENSION TYPE T006-DIMID,
         W_TEXT      TYPE T006T-TXDIM,
         W_MEINS     TYPE T006-MSEHI ,
         L_MENGE     TYPE MLEA-MEINH ,
         WA_PARAM    TYPE OIB_A10 .
*-----DATA DECLARATION FOR L15 START -
DATA : WF_ADQNT_L     TYPE OIB_A05-ADQNT,
         WF_ADQNT_L15   TYPE OIB_A05-ADQNT,
         WF_ADQNT_TMP   TYPE OIB_A05-ADQNT,
         WF_ADQNT_ROUND TYPE OIB_A05-ADQNT,
         WF_ADQNT_KG    TYPE OIB_A05-ADQNT.
*-----DATA DECLARATION FOR L15 END -
IT_ADQNT = TC_QT2TAB.
READ TABLE ITC_PARAM INTO S_CTPARAM WITH KEY FIELDNAME = 'UMRSL'.
IF SY-SUBRC = 0 AND S_CTPARAM-PAR_CHAR = 'ZCRD' .   " .   "AMP
    READ TABLE ITC_PARAM INTO S_CTPARAM WITH KEY FIELDNAME = 'MEINH'.
    W_MEINS = S_CTPARAM-PAR_CHAR.
    IF W_MEINS NE SPACE.
      CALL FUNCTION 'DIMENSION_GET_FOR_UNIT'
        EXPORTING
          LANGUAGE       = SY-LANGU
          UNIT           = W_MEINS
        IMPORTING
          DIMENSION      = W_DIMENSION
          TEXT           = W_TEXT
        EXCEPTIONS
          UNIT_NOT_FOUND = 1
          OTHERS         = 2.
    ENDIF.
    IF W_DIMENSION = 'VOLUME'.
      READ TABLE ITC_PARAM INTO S_CTPARAM
        WITH KEY FIELDNAME = 'BSWCN'.
      WF_BSW = S_CTPARAM-PAR_FLTP .
      READ TABLE IT_ADQNT INTO S_ADQNT WITH KEY MSEHI = 'MT' MANEN = ' '.
      IF SY-SUBRC = 0.
        W_TABIX = SY-TABIX.
        S_ADQNT-ADQNT =
                S_ADQNT-ADQNT * ( 1 - ( S_CTPARAM-PAR_FLTP / 100 ) ).
        MODIFY IT_ADQNT   FROM S_ADQNT INDEX W_TABIX TRANSPORTING ADQNT.
        TC_QT2TAB = IT_ADQNT.
      ENDIF.
      READ TABLE IT_ADQNT INTO S_ADQNT WITH KEY MSEHI = 'KG' MANEN = ' '.
      IF SY-SUBRC = 0.
        W_TABIX = SY-TABIX.
        S_ADQNT-ADQNT =
                S_ADQNT-ADQNT * ( 1 - ( S_CTPARAM-PAR_FLTP / 100 ) ).
        MODIFY IT_ADQNT   FROM S_ADQNT INDEX W_TABIX TRANSPORTING ADQNT.
        TC_QT2TAB = IT_ADQNT.
      ENDIF.
*-----Start BSW% in Litre Qty----
      READ TABLE IT_ADQNT INTO S_ADQNT WITH KEY MSEHI = 'L' MANEN = ' '.
      IF SY-SUBRC = 0.
        W_TABIX = SY-TABIX.
        S_ADQNT-ADQNT =
               S_ADQNT-ADQNT * ( 1 - ( S_CTPARAM-PAR_FLTP / 100 ) ).
        WF_ADQNT_L = S_ADQNT-ADQNT .
        MODIFY IT_ADQNT   FROM S_ADQNT INDEX W_TABIX TRANSPORTING ADQNT.
        TC_QT2TAB = IT_ADQNT.
      ENDIF.
*-----End BSW% in Litre Qty--
*---L15 start----
      READ TABLE IT_ADQNT INTO S_ADQNT WITH KEY MSEHI = 'L15' MANEN = ' '.
      IF SY-SUBRC = 0.
        W_TABIX = SY-TABIX.
        WF_ADQNT_L15 = S_ADQNT-ADQNT .
        WF_ADQNT_TMP = ( WF_ADQNT_L15 / WF_ADQNT_L ).
        CALL FUNCTION 'ROUND'
          EXPORTING
            DECIMALS      = 4
            INPUT         = WF_ADQNT_TMP
            SIGN          = 'X'
          IMPORTING
            OUTPUT        = WF_ADQNT_ROUND
          EXCEPTIONS
            INPUT_INVALID = 1
            OVERFLOW      = 2
            TYPE_INVALID = 3
            OTHERS        = 4.
        WF_ADQNT_L15   = WF_ADQNT_ROUND * WF_ADQNT_L .
        S_ADQNT-ADQNT = WF_ADQNT_L15 .
       MODIFY IT_ADQNT   FROM S_ADQNT INDEX W_TABIX TRANSPORTING ADQNT. " ---Blocked by Prasanta on 08-june-07
        MODIFY IT_ADQNT   FROM S_ADQNT INDEX W_TABIX TRANSPORTING ADQNT.
        TC_QT2TAB = IT_ADQNT.
      ENDIF.
*---L15 end----
*---KG start---
      READ TABLE IT_ADQNT INTO S_ADQNT WITH KEY MSEHI = 'KG' MANEN = ' '.
      IF SY-SUBRC = 0.
        W_TABIX = SY-TABIX.
        READ TABLE ITC_PARAM INTO S_CTPARAM
        WITH KEY FIELDNAME = 'BDICH'.
        WF_ADQNT_KG = ( WF_ADQNT_L15 / ( 1 - ( WF_BSW / 100 ) ) * ( ( S_CTPARAM-PAR_FLTP / 1000 ) - 11 / 10000 ) ) - ( WF_ADQNT_L15 / ( 1 - ( WF_BSW / 100 ) ) * ( WF_BSW / 100 ) * 9979 / 10000 ) .
        S_ADQNT-ADQNT = WF_ADQNT_KG .
        MODIFY IT_ADQNT   FROM S_ADQNT INDEX W_TABIX TRANSPORTING ADQNT.
        TC_QT2TAB = IT_ADQNT.
      ENDIF.
*---KG end---
    ENDIF.
ENDIF.
ENDMETHOD.

Return For Correction-EIT

Hello All,
We have registered an Extra Information Type and enabled security for Employee self service responsibility.Every thing is working fine except return for correction feature. Approver is able to return the notification for correction but when requester opens the returned notification and clicks on "Continue Action" link, he is not able to see the information type and getting note as "Under your current responsibility, no information types are available for this person"(May be this page is defaulted to some responsibility other than Employee self service ). He is not even able to see "Switch responsibility" list of values.
It seems i have missed something during setup. Kindly share some ideas to fix this issue and let me know if you need more information(Note that i am very new to this forum and this this my first thread)
Thanks
Dileep

In actual it should update only that SIT record which is currently under consideration and not allow other records to modify.Ayaz
this is a very valid question .. and same thing happens with EIT as well. This happens because when you create or update EITs, SITs you can do more than one at a time at the time of creation/ updation. So when approver go to update action or send it back for return for correction you create/ update multiple EITs and SITs as all of that go in single transaction.
Let us know if you find any solution for this one.

Workflow Return for correction RFC history not appearing

Hi -
I have built a custom new workflow in Oracle Learning Management.
I am using the workflow attribute WF_NOTE to capture the comments of the approvers.
When the approval moves from one approver to another, it successfully captures any comments made by the previous approvers and displays it to the next approver.
However, when any of the approvers click on return for correction ( RFC ) button and the notification moves to the creator, the approval history is blank and does not have the comments made by the approver about why he is returning for correction.
Any insight?
Thanks

In actual it should update only that SIT record which is currently under consideration and not allow other records to modify.Ayaz
this is a very valid question .. and same thing happens with EIT as well. This happens because when you create or update EITs, SITs you can do more than one at a time at the time of creation/ updation. So when approver go to update action or send it back for return for correction you create/ update multiple EITs and SITs as all of that go in single transaction.
Let us know if you find any solution for this one.

Return for correction from asynchronous page

HI ,
I have a process for Contingent Worker Placment. I am initiating the process and have 2 approvers in the supervisor hirerachy.
but requirement is that after these 2 approvers we need to have the final approval from another team. but they ll not get any notification. I ll put all the transaction details into the table n show that to the use. from there the approval group can do multiple actions like Return for Correction, approval, rejectiion etc.
To achive this , I have blocked the workflow after 2 approvers.After this the txn details are put into the table from where the final approval group can either select approve , reject or Return fo rCorrection. When they click on Approval, the workflow blocked activty will be compelted with a result of Approve and if they click reject it will complete activity with reject status.
Bothe are wokring fine. but RFC is not working. From the Admin group, I am able to launch the RFC page, but from there not able to complete the blocked activity of workflow and resume workflow as the RFC CO is a seeded CO>
please advise.
Regards,
Preeti

Dear Priyanka,
Please refer following Metalink Doc ID's it will resolve your problem:
1. Return For Correction Errors With "You Have Insufficient Privileges For the Current Operation. Please Contact your System Administrator." (Doc ID 1072042.1)
2. Error When Users with no Responsibility Use Return For Correction (Doc ID 1381514.1)
Regards,
Kathan Bhatt
*** Kindly mark Helpful/Correct if satisfied ***

Return for correction

HI ,
I have a process for Contingent Worker Placment. I am initiating the process and have 2 approvers in the supervisor hirerachy.
but requirement is that after these 2 approvers we need to have the final approval from another team. but they ll not get any notification. I ll put all the transaction details into the table n show that to the use. from there the approval group can do multiple actions like Return for Correction, approval, rejectiion etc.
To achive this , I have blocked the workflow after 2 approvers.After this the txn details are put into the table from where the final approval group can either select approve , reject or Return fo rCorrection. When they click on Approval, the workflow blocked activty will be compelted with a result of Approve and if they click reject it will complete activity with reject status.
Bothe are wokring fine. but RFC is not working. From the Admin group, I am able to launch the RFC page, but from there not able to complete the blocked activity of workflow and resume workflow as the RFC CO is a seeded CO>
please advise.
Regards,
Preeti

Check the Node attributes in the Return for Correction process through workflow builder. That should tell you where it will be sending the email.

Return for correction RFC history not appearing

Hi -
I have built a custom new workflow in Oracle Learning Management.
I am using the workflow attribute WF_NOTE to capture the comments of the approvers.
When the approval moves from one approver to another, it successfully captures any comments made by the previous approvers and displays it to the next approver.
However, when any of the approvers click on return for correction ( RFC ) button and the notification moves to the creator, the approval history is blank and does not have the comments made by the approver about why he is returning for correction.
Any insight?
Thanks

In actual it should update only that SIT record which is currently under consideration and not allow other records to modify.Ayaz
this is a very valid question .. and same thing happens with EIT as well. This happens because when you create or update EITs, SITs you can do more than one at a time at the time of creation/ updation. So when approver go to update action or send it back for return for correction you create/ update multiple EITs and SITs as all of that go in single transaction.
Let us know if you find any solution for this one.

Return For Correction - SIT

Hello,
when approver go for return for correction (RFC) on SIT, the main SIT page opens where initiator can able to add new records and also able to update any existing SIT records. This thing not happen in Absence work flow where on RFC, user update only current record which is under consideration.
In actual it should update only that SIT record which is currently under consideration and not allow other records to modify.
Thanks

In actual it should update only that SIT record which is currently under consideration and not allow other records to modify.Ayaz
this is a very valid question .. and same thing happens with EIT as well. This happens because when you create or update EITs, SITs you can do more than one at a time at the time of creation/ updation. So when approver go to update action or send it back for return for correction you create/ update multiple EITs and SITs as all of that go in single transaction.
Let us know if you find any solution for this one.

Talent Management - Return for Correction

Hi,
When the manager clicks on "Delete" button on the Return for Correction notification, the appraisal of the employee gets lost. How to avoid this? Is any way to personalize this delete button? If it is a standard functionality, how could we rollback the lost record?
Thanks in advance

I'm afraid this is standard functionality. It might be changed in R12. I try to remove the possibility of this happening by removing the function. But, unfortunately, this affects all notifications.

Workflows - reminders / Approvals / return for correction etc

Hi
Can anyone help, We are trying to set up an automated Business Process Matrix, bascially we have people that need to submit reports (annually / Monthly / Quarterly) and we want to be able to
Send them an email say 1 week before the due date (and then another say 2 days before due date.
When they submit the document I want to be notified that they've uploaded the document to a business process list and be able to approve it or return for correction
Last but not least – would like to be able to keep a historic library of the documents
Looked on google and can see how to do it with sharepoint designer – easy – but our company have denied us access to it – and we have to pay a team to do anything in designer !!!!

hi,
You're stuck without SPD for the first requirement, but I’m sure your specialised team would welcome a bit of direction :). My comments in bold
“Send them an email say 1 week before the due date (and then another say 2 days before due date"
You can use the ‘Information Management Policy’ method as described in
this blog article by Laura Rogers (it’s for MOSS and WSS but works in SP2010 also). SPD required. Alternative is custom timer job which would be dev – not ideal.
"When they submit the document I want to be notified that they've uploaded the document to a business process list and be able to approve it or return for correction"
You could use a standard ‘out of the box’ approval workflow for this. No SPD required.
"Last but not least – would like to be able to keep a historic library of the documents"
The library that the documents would be uploaded to could also function as a historic library of the documents. Perhaps your default view could only include recently uploaded documents. No SPD required. Some useful info
here.
Cheers
Matt

"Return for Correction" button in SSHR approval notification directing to External URL

In SSHR approval workflow notification mail, if we click on "Request for Correction" button, an incorrect URL is loaded.
1 - Where should this be setup to direct to the particular notification in workflist in Oracle page?
2 - How can we remove this functionality in the notification?
Thanks,
Sumanth

Check the Node attributes in the Return for Correction process through workflow builder. That should tell you where it will be sending the email.

Commited transaction durability and DB_REP_HANDLE_DEAD

From the BDB 4.8 manual "Dead replication handles happen whenever a replication election results in a previously committed transaction becoming invalid. This is an error scenario caused by a new master having a slightly older version of the data than the original master and so all replicas must modify their database(s) to reflect that of the new master. In this situation, some number of previously committed transactions may have to be unrolled."
In the application I am working on, I can't afford to have committed transactions "unrolled". Suppose I set my application to commit transactions only when a majority of electable peers acknowledges the transaction and stop the application on a DB_EVENT_REP_PERM_FAILED event. Will that guarantee the durability of committed transactions and (equivalently) guarantee that no replica will ever see DB_REP_HANDLE_DEAD error (assuming absence of bugs)?
Also as I understand it DB_REP_HANDLE_DEAD errors should never be seen on the current the master, is this correct? Is there a way to register a callback with the Replication Manager
-Sanjit

I think it is important to separate the txn commit guarantees from the
HANDLE_DEAD error return. What you are describing mitigates the
chance of getting that error, but you can never eliminate it 100%.
Your app description for your group (all electable, quorum ACKs)
uses the best scenario for providing the guarantees for txn commit.
Of course the cavaets still remain that you run risk if you use TXN_NOSYNC
and if you have total group failure and things in memory are lost.
Also, it is important to separate making a txn guarantee at the master site
with getting the HANDLE_DEAD return value at a client site. The
client can get that error even with all these safeguards in place.
But, let's assume you have a running group, as you described, and
you have only the occasional failure of a single site. I will describe
at least 2 ways a client can get HANDLE_DEAD while your txn integrity
is still maintained.
Both examples assume a group of 5 sites, call them A, B, C, D, E
and site A is the master. You have all sites electable and quorum
policy.
In the first example, site E is slower and more remote than the other 4
sites. So, when A commits a txn, sites B, C, and D quickly apply that
txn and send an ack. They meet the quorum policy and processing
on A continues. Meanwhile, E is slow and slowly gets further and
further behind the rest of the group. At some point, the master runs
log_archive and removes most of its log files because it has sufficient
checkpoint history. Then, site E requests a log record from the master
that is now archived. The master sends a message to E saying it has
to perform an internal initialization because it is impossible to
provide that old log record. Site E performs this initialization (under the
covers and not directly involving the application) but any
DB handles that were open prior to the initialization will now get
HANDLE_DEAD because the state of the world has changed and
they need to be closed and reopened.
Technically, no txns were lost, the group has still maintained its
txn integrity because all the other sites have all the txns. But E cannot
know what may or may not exist as a result of this initialization so
it must return HANDLE_DEAD.
In the second example, consider that a network partition has happened
that leaves A and B running on one side, and C, D, and E on the other.
A commits a txn. B receives the txn and applies it, and sends an ack.
Site A never hears from C, D, E and quorum is not met and PERM_FAILED
is returned. In the meantime, C, D, and E notice that they no longer can
communicate with the master and hold an election. Since they have a
majority of the sites, they elect one, say C to be a new master. Now,
since A received PERM_FAILED, it stops. If the network partition
is resolved, B will find the new master C. However, B still has the
txn that was not sufficiently ack'ed. So, when B sync's up with C, it
will unroll that txn. And then HANDLE_DEAD will be returned on B.
In this case, the unrolled txn was never confirmed as durable by A to
any application, but B can get the HANDLE_DEAD return. Again, B
should close and reopen the database.
I think what you are describing provides the best guarantees,
but I don't think you can eliminate the possibility of getting that error
return on a client. But you can know about your txn durability on the
master.
You might also consider master leases. You can find a description of
them in the Reference Guide. Leases provide additional guarantees
for replication.
Sue LoVerso
Oracle

Error committing transaction in Stored Proc call - prev solns not working

Hi All,
Our process invokes a DB adapter to fetch the response from the table for our request via Stored Procedure call but facing the below issue. Its a synchronous process. Stored Procedure is present inside the Package and we are calling the Stored procedure using that Package.
What we did is created a DB datasource of XA type and tried to call the Stored Proc but it was giving a problem “ORA-24777: use of non-migratable database link not allowed” and hence according to this thread Using DB links in Stored proc call in DB adapter 11G SOA we have modified the datasource as non-XA type.
While we do that, we could see that Stored Proc is called and the response is present in the reply payload inside the flow trace. But the instance is getting faulted and the error is “Error committing transaction:; nested exception is: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source.”
We have tried the properties of global transaction support as one phase commit, emulate two phase commit and logging last resource but error remains the same.
Database from which we are getting the response is of version "Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production". Will the database link error arises even if we connect to Oracle Database?
Please could you advise me solutions to resolve this issue.
Thanks in advance.

You are using Non-XA because it means (among all others) that the commit issue can be handle by the DB as well.
The Emulate Two Phase property imitating the XA transaction in that way, that it allows you to manage a local db transaction.
You can stay with XA connection, but then you will have to use "AUTONOMOUS_TRANSACTION pragma" in your procedure.
Enter the following link to find good explanation about all of your questions:
http://docs.oracle.com/cd/E15523_01/integration.1111/e10231/adptr_db.htm#BGBIHCIJ
Arik

ORA:01013 with Duplicate Database - RMAN

Hi,
I havea demo database on server1 and am creating a clone database on server2 with RMAN duplicate command. I have the catalog on server1 itself. I created the backups of the database and executed RMAN command from server2 with
server1 in open status and server2 in nomount state.
the command i ran was:
duplicate target database to clonedb
until logseq 338 thread 1
pfile=/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora
logfile
'/u01/app/oracle/oradata/clonedb/redo01.log' size 1m,
'/u01/app/oracle/oradata/clonedb/redo02.log' size 1m;
Please let me know how to overcome this error..
Thanks,
Raj
This is the error i got along with the log it created...
Starting Duplicate Db at 28-OCT-04
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=14 devtype=DISK
printing stored script: Memory Script
set until scn 130734;
set newname for datafile 1 to
"/u02/oradata/clonedb/system01.dbf";
set newname for datafile 2 to
"/u03/oradata/clonedb/undotbs01.dbf";
set newname for datafile 3 to
"/u02/oradata/clonedb/testtbs_01.dbf";
set newname for datafile 4 to
"/u02/oradata/clonedb/system02.dbf";
set newname for datafile 5 to
"/u02/oradata/clonedb/rmantbs_01.dbf";
restore
check readonly
clone database
executing script: Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 28-OCT-04
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /u02/oradata/clonedb/system01.dbf restoring datafile 00002 to /u03/oradata/clonedb/undotbs01.dbf
restoring datafile 00003 to /u02/oradata/clonedb/testtbs_01.dbf
restoring datafile 00004 to /u02/oradata/clonedb/system02.dbf restoring datafile 00005 to /u02/oradata/clonedb/rmantbs_01.dbf
channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/full/DEMODB_20041027_05g3jeeq_1_1 tag=FULL params=NULL channel ORA_AUX_DISK_1: restore complete Finished restore at 28-OCT-04 sql statement: CREATE CONTROLFILE REUSE SET DATABASE "clonedb" RESETLOGS ARCHIVELOG
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 680
LOGFILE
GROUP 1 '/u01/app/oracle/oradata/clonedb/redo01.log' SIZE 1048576 ,
GROUP 2 '/u01/app/oracle/oradata/clonedb/redo02.log' SIZE 1048576
DATAFILE
'/u02/oradata/clonedb/system01.dbf'
CHARACTER SET WE8ISO8859P1
printing stored script: Memory Script
switch clone datafile all;
executing script: Memory Script
datafile 2 switched to datafile copy
input datafilecopy recid=1 stamp=540710832 filename=/u03/oradata/clonedb/undotbs01.dbf
datafile 3 switched to datafile copy
input datafilecopy recid=2 stamp=540710832 filename=/u02/oradata/clonedb/testtbs_01.dbf
datafile 4 switched to datafile copy
input datafilecopy recid=3 stamp=540710832 filename=/u02/oradata/clonedb/system02.dbf
datafile 5 switched to datafile copy
input datafilecopy recid=4 stamp=540710832 filename=/u02/oradata/clonedb/rmantbs_01.dbf
printing stored script: Memory Script
set until scn 130734;
recover
clone database
delete archivelog
executing script: Memory Script
executing command: SET until clause
Starting recover at 28-OCT-04
using channel ORA_AUX_DISK_1
starting media recovery
channel ORA_AUX_DISK_1: starting archive log restore to default destination channel ORA_AUX_DISK_1: restoring archive log archive log thread=1 sequence=337 channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/arch/arc_DEMODB_20041027_06g3jef2_1_1 tag=TAG20041027T134050 params=NULL channel ORA_AUX_DISK_1: restore complete archive log filename=/u02/oradata/clonedb/arch/1_337.arc thread=1 sequence=337 channel clone_default: deleting archive log(s) archive log filename=/u02/oradata/clonedb/arch/1_337.arc recid=1 stamp=540710834 media recovery complete Finished recover at 28-OCT-04
printing stored script: Memory Script
shutdown clone;
startup clone nomount pfile= '/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora';
executing script: Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/28/2004 06:28:26
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
Recovery Manager complete.

HI,
# STBY:
SQL> startup nomount
ORACLE instance started.
Total System Global Area 242208768 bytes
Fixed Size            2227176 bytes
Variable Size          184550424 bytes
Database Buffers       50331648 bytes
Redo Buffers            5099520 bytes
# PRIMARY:
RMAN> CONNECT TARGET sys/oracle@JOHN;
connected to target database: JOHN (DBID=1575580406)
RMAN> CONNECT AUXILIARY sys/oracle@JOHN_DB2;
Until this you did correct. now just in a run block, like
eg
run
allocate channel ....
allocate channel...
duplicate target database for standby from active database;

Oracle Error occured, while checking for Already Committed data

Hi,
In my 1 day old workspace I see more than 3000 errors logged in the owb_error_log_table with text as shown below , can someone from Oracle please advise what the problem seems to be ?
Oracle Error occured, while checking for Already Committed data : 76291.DBObject.TABLE_1.2.en_GB
Oracle Error occured, while checking for Already Committed data : 76291.DBObject.TABLE_1.1.en_GB
Oracle Error occured, while checking for Already Committed data : 42483.PlatformConfiguration.ORACLE.1.en_GB
Oracle Error occured, while checking for Already Committed data : 42483.PlatformConfiguration.ORACLE.2.en_GB
There are many more examples of other errors as well. Google returns nothing for these error....am I the first one to face these errors. We are using 11gRelease2 on RHEL.
They all have a error text of ORA-01403: no data found
tks in advance.

I haven't been able to pin it down to a specific action that causes these errors. I have been having various other problems when importing tables ...the screen just freezes and nothing happens. When I queried this table from sql developer to check if I can spot anything and I found these errors.
The screen freezes when I add a new oracle location - the test works fine - but when I click OK to the add oracle location screen it just freezes and nothing happens.

OCITransCommit() returns ORA-01013 for correctly committed transaction

Similar Messages

Maybe you are looking for