ORA-00164 Autonomous Transactions in Distributed Env

Hi,
We are on 8.1.7 on AIX. We get ORA-00164 when we attempt to call an Autonomous transaction procedure whilst the main transaction has read a remote table.
In 8.1.6.0.0 this used to check us out with Ora-600, In 8.1.7 it gives error 164. I have read some postings stating that this limitation is expected to be fixed in Oracle server 8.2 or Oracle 9i Release 2.
Can somebody confirm this,
BTW what would 9i Release 2 mean - 9.2 or 9.0.2 ?
Also, is 8.2 out?
null

Is this question specific to Oracle9iAS Portal?

Similar Messages

ORA-00164: autonomous transaction disallowed within distributed transaction

I have been trying to solve this problem for weeks now, I have posted this question everywhere I can think of, but I havent really received and answer that has helped, so now I am going to post it here hoping for an answer.
We are running 9iAS on Solaris and when the following stuff is run we are getting ORA-00164 errors. If you refresh the page a bunch of time the problem goes away. But it comes back the next time you try to execute the procedure again. Here are the cases when the problem shows up.
Editing the style:
PROCEDURE : PORTAL30.wwpob_app_style.edit_style
Saving changes to the banner for a page
PROCEDURE : PORTAL30.wwptl_banner.savecustom
Logging out
PROCEDURE : PORTAL30.wwsec_app_priv.logout
After setting the default user group and applying the changes:
PROCEDURE : PORTAL30.wwsec_app_user_mgr.edit_user
Creating a new group:
PROCEDURE : PORTAL30.wwsec_app_group_mgr.create_group
Opening the add portlet screen:
PROCEDURE : PORTAL30.wwv_main.main
There are a few other places but I don't have them documented. In ALL cases the problem goes away once we start and stop the Apache using the following comands:
/app/oracle/n_portal/Apache/Apache/bin/apachectl stop
ps -ef | grep httpd | grep n_portal
/app/oracle/n_portal/Apache/Apache/bin/apachectl start
After starting and stopping Apache the problem is gone for a little while (20-30 mins) then it starts coming back slowly (sometimes the problem is there then it is not). Once the problem is back if you continually press refresh on the browser (5-10 times) the page might appear, if the page does not appear you will see the
ORA-00164: autonomous transaction disallowed within distributed transaction
The following error appears in apache log (50% of the time) when Autonomous Transaction error shows up on the screen:-
DSHttpSessionBindingListenerImpl.valueUnbound : closing DS session : DSSession id = 5225534324468880950975536484
215 PortalSession id = 521335001720MERAJ
DSHttpSessionBindingListenerImpl.valueUnbound : closing DS session : DSSession id = -638034231325135430097553725
8001 PortalSession id = 992335001711JDALGLIESH
These errors might be related to dynamic services but we were had the problem long before Dynamic services was installed.
We want to start pre-production user testing as we have just had 11 developers building portlets for the company, but we cant do much with this error popping up every time a user wants to test it. We have one of the Oracle consultants here and he has asked the oracle developer group what the problem could be, and they seem to think it might be related to our use of DB links however, we never get the problem when we try to run a portlet that uses a database link.
Please help.
Jeff Dalgliesh
null

Jay,
My name is Craig McCauley. I'm an Oracle Technical Manager working onsite at Unocal Indonesia. I'm with the Portal group in ATS.
When I got here the first thing we did was bump up init.ora parameters and apache confif parameters as suggested by the iPlatform group. We have thes sessions parameter (in init.ora) bumped up from 100 to 700. I'm watching v$session and the get these AT messages with as few as 70 total db sessions. Any help your group can give will be greatly appreciated.
Unocal is planning on implementing Oracle Portal globally - as a common interface. They have similar installs in Thailand and Houston and thus far have not seen the AT messages (although there has not been much development going on at those sites).
Thanks,
Craig

ORA-00164 Autonomous transaction when creating batch of users

Hi,
I ran the script posted earlier in this forum to create a batch of users, I got some errors, support people told me that is appears to be database errors :
ORA-00164 Autonomous transaction disallowed with distributed transaction.
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "PORTAL30.WWCTX_SSO", line 669 ORA-06502: PL/SQL: numeric or value error.
We use 8.1.7.2 database, Portal 3.0.9.8.
Anyone having a solution for that problem, I don't want to create 250 users manually.
Thank's

i'm getting the same thing, but i'm using hardcoded input,
so i have no dblinks or anything of the sort.
this is my entire exception line:
ORA-06502: PL/SQL: numeric or value error ORA-06512: at "SYS.OWA_UTIL", line 323 ORA-06512: at "SYS.HTP", line 859 ORA-06512: at "SYS.HTP", line 974 ORA-06512: at "SYS.HTP", line 992 ORA-06512: at "SYS.HTP", line 40 ORA-06512: at "PORTAL30_SSO.WWSEC_UI", line 568 ORA-06512: at "PORTAL30_SSO.WWSSO_APP_USER_MGR", line 576 ORA-06512: at line 1
any idea what is causing this?

ORA-00164 Autonomous and Distributed Transactions in Oracle 8i - Forms6i

Hi, in Forms6i I'm using Autonomous transactions (insert and update), and I want to use also a database link to make a query in a remote database (Distributed transaction). Even when this request are done in different PL/SQL within Forms6i, I get the error message ORA-00164 Distributed transactions disallowed within autonomous transactions. Is there a way to avoid this error message?
Thanx

Hello,
I had a similar Problem, when I tried to log errormessages while selecting by db-link.
I use pipes now to send the errormessages. The pipe is read at regular intervals and then I can Insert without using autonomous transactions.
I hope, this will help you
Marcus

ORA-00164 but I cant find an autonomous transaktion

Hello,
I have the following statement
SQL> create table tab2 as
2 select * from tab1@dblink;
and get the error
select * from tab1@dblink
ERROR at line 2:
ORA-00604: error occurred at recursive SQL level 1
ORA-00164: autonomous transaction disallowed within distributed transaction
where is the autonomous transaktion??
when the table exists and I do an 'insert into select' by dblink it works
The same statement worked before and I don't know about any changes in the db-parameters.
We work with 8.1.7
Thank you for any help

Thanks for the answer,
but I found out, that our DBA had installed a BigBrother package, because sometimes tables got 'lost' without anybody knowing anything. Started by a logon Trigger it used autonomous transaktions to write the log.
Now it runs with simple transactions and the error is gone.
Marcus

Autonomous transaction in Tuxedo

Our development team is using Bea Tuxedo as a middle tier in our transactions...we encountered a problem in using PRAGMA AUTONOMOUS_TRANSACTION in one of our services, 'ORA-00164: autonomous transaction disallowed within distributed transaction...'
of course my question would be... what is the solution to this? or is there a solution to this?
would really appreaciate if you could lend me a hand with this problem.

CREATE TABLE GOKHAN_DENEME (EMPNO NUMBER(4) NOT NULL,
ENAME VARCHAR2(10),
EJOB VARCHAR2(9),
DEPTNO NUMBER(2));
INSERT INTO GOKHAN_DENEME VALUES (7369, 'SMITH', 'CLERK', 20);
INSERT INTO GOKHAN_DENEME VALUES (7499, 'ALLEN', 'SALESMAN', 30);
INSERT INTO GOKHAN_DENEME VALUES (7521, 'WARD', 'SALESMAN', 30);
INSERT INTO GOKHAN_DENEME VALUES (7566, 'JONES', 'MANAGER', 20);
CREATE TABLE GOKHAN_DENEME_2 (MGR NUMBER(4) NOT NULL,
COMM NUMBER(7, 2));
INSERT INTO GOKHAN_DENEME_2 VALUES (7369, 20);
INSERT INTO GOKHAN_DENEME_2 VALUES (7499, 30);
INSERT INTO GOKHAN_DENEME_2 VALUES (7521, 30);
INSERT INTO GOKHAN_DENEME_2 VALUES (7566, 20);
create or replace
TRIGGER GOKHAN_DENEME_TRG1
AFTER DELETE ON GOKHAN_DENEME FOR EACH ROW
DECLARE
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
RAISE_APPLICATION_ERROR(-20000, 'ERRORRRRRR');
END;
create or replace
TRIGGER GOKHAN_DENEME_2_TRG1
AFTER DELETE ON GOKHAN_DENEME_2 FOR EACH ROW
DECLARE
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
DELETE FROM GOKHAN_DENEME WHERE EMPNO = :OLD.MGR;
COMMIT;
END;
the delete statement is:
DELETE FROM GOKHAN_DENEME_2 WHERE MGR = 7566;
the error mesage is:
Error starting at line 74 in command:
DELETE FROM GOKHAN_DENEME_2 WHERE MGR = 7566
Error report:
SQL Error: ORA-20000: ERRORRRRRR
ORA-06512: at "DBO.GOKHAN_DENEME_TRG1", line 49
ORA-04088: error during execution of trigger 'DBO.GOKHAN_DENEME_TRG1'
ORA-06512: at "DBO.GOKHAN_DENEME_2_TRG1", line 10
ORA-04088: error during execution of trigger 'DBO.GOKHAN_DENEME_2_TRG1'
20000. 00000 - "%s"
*Cause: The stored procedure 'raise_application_error'
was called which causes this error to be generated.
*Action: Correct the problem as described in the error message or contact
the application administrator or DBA for more information.

ORA-02047: cannot join the distributed transaction in progress

Hi All,
My requirement is to do COMMIT Transactions in BULK like 100 rows. I am doing update in Oracle and SQL Server both. Following statement update the SQL Server side:
v_sqlstr :=
'update JDETAIL set interfacedate = getdate() where company ='
|| v_company
|| ' and Recordnumber= '
|| TO_NUMBER (v_recordNumber)
|| ' COMMIT TRANSACTION';
num_rows :=
DBMS_HS_PASSTHROUGH.execute_immediate@ex_test (v_sqlstr);
After this I am calling Oracle Update Procedure . In Oracle UPDATE Procedure when I write AUTONOMOUS TRANSACTIONS AND Commit then it works fine BUT when I don't COMMIT which I don't want because I want to COMMIT in BATCHES then following error is thrown
ORA-02047: cannot join the distributed transaction in progress
Thanks

you can't put the commit transaction into a pasthrough statement.
Oracle Gateway starts the transaction, so you need to write the code in a way that allows the gateway to perform the commit. When doing a commit in a passhrough statement the gateway has no control over the committed data. Thus you get the error unless you start an autonomous transaction.
Why do you need to call the update in a pasthrough statement? Why not in a PL/SQl code block with a counter that commits after 100 rows?

Ora 02290 when using qms_transaction_mgt and autonomous transactions

Hi all,
I'm using the qms procedures:
qms_transaction_mgt for openeing and closing transactions.
Somewhere in my procedure when the transaction is opened i call another procedure which contains a autonomous transaction.
The next time qms_transaction_mgt.close_transaction is called i get an ORA-02290: check constraint (HST65.QMS_NEED_TO_CLOSE_TRANSACTION) violated
When i debug the qms_transaction_mgt.close transaction the g_current_trans_id variable is empty, which indicates the transaction is allready closed.
When i remove the pragma autonomous_transaction statement and the commit statement from the procedure i call, the problem is resolved.
Version information:
Designer 9.0.2 with a with a Oracle 9i 9.2 database and Headstart 9i.
Does anybody know how i can resolve this or if this is a bug and how to fix it?
Thanks,
Yvon

Ian, Yvon,
It is unfortunately a know restriction that the CDM RuleFrame component of both Headstart for Designer 6i and Headstart for Designer 9i doesn't work in combination with autonomous transactions.
The reason is that the RuleFrame administration relies on information stored in 1. pl/sql package variables and 2. database tables. Using autonomous transactions (that involve CDM RuleFramed DML) causes this information to dissynchronize.
A year ago I investigated the possibilities to make autonomous transactions possible with RuleFrame but unfortunately this is fundamental problem: RuleFrame wants to combine multiple DML-actions into one logical transaction (gards this with the "need_to_close_transaction" constraint), while autonomous transactions intend to to the opposite: commit a part of a transaction while the rest of the transaction still is posted/not committed.
There is one exception: if you call an atonomous procedure that does DML on a non-ruleframe-enabled table (no TAPI triggers that intend to open/close the transaction, no CAPI etc), everything functions.
Problem explanation:
====================
1. Outer transaction is opened (by front end or TAPI triggers of first DML)
2. DML takes place
3. Autonomous transaction-procedure is called
4. Auto-transaction again tries (and succeeds!) to open the transaction, it doesn't see that the transaction is opened (db table qms_transactions is empty for the autonomous transaction on query)
5. DML within auto-transaction is posted
6. Auto-transaction closes transaction
7. Auto-transaction is committed
8. Outer transaction thinks the transaction is already closed, because the auto-transaction cleaned out the package variables when it closed the transaction.
9. Commit of the outer transaction fails as the deferred check constraint need_to_close_transaction avoids this to happen (rollback takes place because of this violation).
Hope this helps
Kind Regards
Marc Vahsen
Headstart Team Oracle NL

Pipeline function raised ORA-06519: active autonomous transaction detected

Hi All,
My name is John and I've got a problem which I need to share with all of you guru and experts. I've created the following pipeline function under the Oracle user ABC:
CREATE OR replace FUNCTION SomeFunction(p_from_date DATE, p_to_date DATE) RETURN T_TAB_A pipelined
IS
PRAGMA autonomous_transaction;
BEGIN
DELETE FROM temp_rcm;
INSERT INTO temp_rcm
SELECT * FROM int.facility fd,
int.capacity co
WHERE co.resource_name = fd.resource_name
AND co.trade_date = fd.trade_date
AND co.trade_date BETWEEN p_from_date AND p_to_date;
COMMIT;
FOR rec IN (SELECT co.*
FROM temp_rcm co
left join int.outage o
ON ( o.flag = 'Y'
AND o.reason_flag = 'F'
AND o.INTERVAL = co.INTERVAL
AND co.resource_name = o.resource_name )
ORDER BY co.INTERVAL,
co.name) LOOP
pipe ROW (T_A( rec.INTERVAL, rec.trade_date,
rec.resource_name,rec.day_of_week_long, rec.working_day, rec.peak));
END LOOP;
RETURN;
END SomeFunction;
I was able to compile and create the SomeFunction function successfully but when I executed it using the following command:
select * from table(SomeFunction(to_date('01/01/2010',to_date('01/01/2010')));
I was returned with the Oracle error - ORA-06519: active autonomous transaction detected and rolled back
I have searched through the web, such Oracle error occurs whenever the function has a missing 'COMMIT' or 'ROLLBACK' command inside an autonomous_transaction. But the fact is I have already included the 'COMMIT;' in the function. I suspected that the error was caused by the tables which I queried against (like int.facility and int.capacity) were all views that belonged to another schema called int. Or is that something that I miss in the function? Thank you for your time and assistance.
Regards,
John

johnwanng wrote:
Hi Guys,
Thank you for all your feedback. In addition to your reply, Bill, can you spare some time and provide us a simple example of the steps involved to implement the 'correct' implementation based on the queries that I've used. As I do not understand your vanilla approach. Much appreciated and thank you for the time again.
Regards,
JohnIf I had to guess, Billy may have meant something like this (untested):
CREATE OR REPLACE FUNCTION SomeFunction
( p_from_date IN int.facility.trade_date%TYPE
, p_to_date   IN int.facility.trade_date%TYPE
RETURN SYS_REFCURSOR
AS
     rcur     SYS_REFCURSOR;
BEGIN
     OPEN rcur FOR
          SELECT co.interval
               , co.trade_date
               , co.resource_name
               , co.day_of_week_long
               , co.working_day
               , co.peak
          FROM   int.capacity co
          JOIN   int.facility fd        ON fd.resource_name = co.resource_name
                                       AND fd.trade_date    = co.trade_date
          LEFT OUTER JOIN int.outage o ON o.interval       = co.interval
                                       AND o.resource_name = co.resource_name
          WHERE co.trade_date BETWEEN p_from_date AND p_to_date
          AND    o.reason_flag = 'F'
          AND    o.flag        = 'Y'
          ORDER BY co.interval
                 , co.name
     RETURN rcur;
END;
/I made the following modifications:
1. I set the input parameter data types to match that of the table column you are checking against. A good practice to get into.
2. Removed the autonomous transaction and inserting into a temp table. In Oracle it's a good practice to perform everything in a single SQL statement if possible.
3. Changed the return data type to a SYS_REFCURSOR
Hope this helps and provides a good example.

ORA-06519: active autonomous transaction detected and rolled back

I am getting this error. when i am doing insert from my package Any solution to reslove this issue
ORA-06519: active autonomous transaction detected and rolled back . thanks
I am doing select - insert...

Also, if you have any exception handler sections in the code,
then you have to add a commit or rollback statement for
every exception that is handled.

Autonomous Transactions & error ORA-01002

Either there's a bug w/ Autonomous Transactions or the documentation is incomplete because the AT is not working when
called from within Cursor Loop.
here's the outline:
CURSOR acct_cur IS ...FOR UPDATE OF a.account_nm...
FOR acct_rec IN acct_cur LOOP
fis_rte_util.print_msg (...) ---autonomous transaction writes to a logging table
---w/ commit
UPDATE ca_account_t
SET account_nm = acct_rec.account_nm....
this update statement causes a ORA-01002: fetch out of sequence exception. if
i comment out the print_msg line it works just fine. its as if the commit in the
AT is causing the problem. according to the documention, there should be no
interference between these 2 blocks.
thanks for any info or insight,
swg
null

Tim,
Refer to the following:
ORA-01002: fetch out of sequence
Cause: This error means that a fetch has been attempted from a cursor which is no longer valid.
Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including:
1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned.
2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error.
3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.
Action:
1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch.
2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE.
3) Reexecute the statement after rebinding, then attempt to fetch again.
HTH,
Thierry
Edited by: Thierry H. on May 4, 2011 12:30 PM Reformatting

ORA-02048: attempt to begin distributed transaction without logging on

Hello,
I've got the error:
ORA-02048: attempt to begin distributed transaction without logging on
When calling OCITransStart
(The XID of the transaction to start is:
formatID = 11101, gtrid = 123, bqual = 1
I've already run several queries before trying to call
OCITransStart and the queries are successfull.
Could anyone help please ?
I'm running Oracle 10g on Linux.
Thanks a lot
Laurent Marzullo

I believe this is the error you see if the client database name is not set prior to calling OCISessionBegin. To set the client database name, use OCIAttrSet on the server handle with the OCI_ATTR_EXTERNAL_NAME and OCI_ATTR_INTERNAL_NAME attributes.
These attributes are discussed in chapter 8 of the OCI Programmer's Guide in the section "OCI Support for Transactions".

ORA-00164 Error

I am trying to execute a insert into a table A (located on a remote database) and has a trigger on it which logs on messages using autonomous transactions in the remote messages table.
Remote database 9.2.x.x.x
Current database 9.0.x.x.x
The operation is done using the db link.
insert into tableA@remote values (1, 'a') ;
I am getting an error ORA-00164
Is there any way to resolve this error/problem.
Thanks
Sanjay

You are correct,
Before 9.2 Oracle doesn't support Autonomous Transactions within a Distributed Transaction. As of version 9.2.0 of Oracle9i, this limitation has been removed to a limited extent.
Check this article,
Autonomous and Distributed Transactions in Oracle 8i/9i

ORA-00164: Why???

I get an ORA-00164 error message in this case:
A PL-SQL program update DB1 with data selected in DB2 through a DB-LINK.
For each data set, it does a commit or rollback depending on success or error and tries to log this information in a table of DB1 using a procedure with AUTONOMOUS_TRANSACTION PRAGMA.
When it enters in this function, it gets this message. Since It DOESN'T write in DB2, there should not be a distributed transaction, and there is no distributed query in this code.
I know I could turn around this by commiting/rollbacking around the log code, but this is not clean.
Can someone help?
Thanks.

As far as Oracle is concerned you are moving data across a database link, so it considers this situation a distributed transaction.
Your alternative is to upgrade to 9.2 which (I believe) does support AUTONOMOUS TRANSACTION PRAGMA across db links.
Cheers, APC

ORA-00164

Hello
I'm getting an "ORA-00164 distributed autonomous transaction disallowed within migratable distributed transaction" from the following section of a query...
SELECT
        BL.billing_list_id,
        P.group_id,
     bl.bill_date,
     f_billing_get_bill_no(     BL.billing_list_id,
                      f_css_unique_id('INVOICE_ID',1),
          Bl.bill_term_dt,
          'B',
          BL.billing_list_ps_flag,
          PP.first_payment_flag,
          PP.method
          ) AS bill_no
...The f_billing_get_bill_no, and f_css_unique_id functions are both set to use autonomous transactions and both commit their work before returning, but I still get this error. None of the tables are remote, and unless I get rid of the f_css_unique_id call, I get this error.
I've looked up the error text and it just says:
Cause: A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.
Action: Roll back or commit the current distributed transaction first.
The thing I don't understand is what a migratable transaction is and why this error is occurring when I've issued the relevant commits. Any ideas?
David

It seems that you cannot start another autonomous transaction when the application is already within an autonomous transactionUmm, up to a point Lord Copper.
SQL> CREATE OR REPLACE FUNCTION f1 RETURN NUMBER AS
2      PRAGMA autonomous_transaction;
3 BEGIN
4         UPDATE dept set deptno=deptno*1;
5         COMMIT;
6      RETURN 1;
7 END f1;
8 /
Function created.
SQL>
SQL> CREATE OR REPLACE FUNCTION f2 RETURN NUMBER AS
2      PRAGMA autonomous_transaction;
3   n NUMBER;
4 BEGIN
5      UPDATE bonus set comm=comm*1;
6   n := f1;
7     COMMIT;
8     RETURN n;
9 END f2;
10 /
Function created.
SQL> VAR x NUMBER
SQL> BEGIN
2    :x := f2;
3 END;
4 /
PL/SQL procedure successfully completed.
SQL> PRINT x
         X
         1
SQL> Perhaps this is a version thang. The above was run on 9iR2. I know there were some issues with AUTONOMOUS_TRANSACTION and distributed calls in 8i, but you say your transaction isn't distributed. Could it be a bug?
Cheers, APC

ORA-00164 Autonomous Transactions in Distributed Env

Similar Messages

Maybe you are looking for