Hi,

No. db_user is just the placeholder. Before running the SQL commands I have replaced them with my actual DB user in database.

I was just wondering which DB credentials Arjuna is using to do the rollback. Could it be that the recovery manager is using some default annoynomous credentials

for which it is crying for priveleges.

Another thing I can see from logs is that it is calling handleOrphan() method which could be because it is not able to find any entry in ObjectStore although Oracle DB has entries in sys.dba_pending_transactions

table for recovery.

This situation could arise if someone clears the ObjectStore manually from the disk but DB has entries in the table. But even after that privelege exception should not come.

My Oracle DB table has following entries:

sys.dba_pending_transactions

select * from sys.pending_trans$

select * from sys.dba_2pc_pending

Regards,

Mayank

Hi Tom,

Thanks for the detailed reply.

Exact condition was --> Object store was manually deleted and Oracle transaction tables have the entries as mentioned before.

* I am able to run select queries from my XA-DataSource user from SQLPLus.

* I have removed the additional sys.dbms_system EXECUTE privilege from my user.

* My Oracle version is 10.2.0.5.0

* Only 1 XA datasource is configured. Apart from it hornet-ra adapter for JMS connection for MDB and direct JMS connection factories are also XA resources.

Even after this same exception comes after starting the server.

Insert the following as sysdba and start JBOSS7 server same exception is reproducible for a XA resource pointing to this DB user.

Insert into sys.pending_trans$ (LOCAL_TRAN_ID,GLOBAL_TRAN_FMT,GLOBAL_ORACLE_ID,GLOBAL_FOREIGN_ID,TRAN_COMMENT,STATE,STATUS,HEURISTIC_DFLT,SESSION_VECTOR,RECO_VECTOR,TYPE#,FAIL_TIME,HEURISTIC_TIME,RECO_TIME,TOP_DB_USER,TOP_OS_USER,TOP_OS_HOST,TOP_OS_TERMINAL,GLOBAL_COMMIT#,SPARE1,SPARE2,SPARE3,SPARE4) values ('8.20.23482',131077,null,'00000000000000000000FFFFC0A82DCA22C9BD23502E28340000247231',null,'prepared','P','','00000002','00000000',0,to_timestamp('17-AUG-12 16:56:43','DD-MON-RR HH24.MI.SSXFF'),null,to_timestamp('20-AUG-12 04:48:35','DD-MON-RR HH24.MI.SSXFF'),null,'Gupta.Mayank','mymachine-W7','unknown','64104005',null,null,null,null);

-Mayank

This exception keep on coming whenever PerodicRecoveryManager runs. Only way to stop is to delete the entry from sys.pending_trans$  table.

Hi Tom,

There is no helpful log in .trc files. I will need to install EM to check Oracle logs for error violation.

Delete privilege is not GRANTED to my XA resource user. OnlySelect is granted and that is executing fine.

I have double checked my db_user entry in SQLPlus and Standalone.xml and both are same.

Thanks,

Mayank

Hi Tom,

Yes you are correct, deletion must be performed by sys.dbms_xa package.

As far as bug number is concerned Oracle website says "The patch number for 10.2.0.5 is 8202632" which must be released after 5945463.

https://forums.oracle.com/forums/thread.jspa?messageID=9805416

Thanks,

Mayank

               <xa-datasource jndi-name="java:/com/xyz/datasources/XADataSource" pool-name="Tx_Pool" enabled="true" use-java-context="true" use-ccm="true">

                    <xa-datasource-property name="URL">

                        jdbc:oracle:thin:@localhost:1521:ORCLDB10

                    </xa-datasource-property>

                    <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>

                    <driver>oracle</driver>

                    <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>

                    <xa-pool>

                        <max-pool-size>40</max-pool-size>

                        <is-same-rm-override>false</is-same-rm-override>

                        <interleaving>true</interleaving>

                        <no-tx-separate-pools>true</no-tx-separate-pools>

                    </xa-pool>

                    <security>

                        <security-domain>DSDbRealm</security-domain>

                    </security>

                    <validation>

                        <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>

                        <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>

                    </validation>

                </xa-datasource>

and the referring security domain configuration is:

               <security-domain name="DSDbRealm" cache-type="default">

                    <authentication>

                        <login-module code="SecureIdentity" flag="required">

                            <module-option name="username" value="MAYANKG600"/>

                            <module-option name="password" value="-4af99cbc35f3adb65adfa9c3a34d9aac"/>

                        </login-module>

                    </authentication>

                </security-domain>

Thanks,

Mayank