Troubleshooting › Oracle Locks Can Occur If You Do Not Shut Down Running Processes Before Starting an Upgrade

Oracle Locks Can Occur If You Do Not Shut Down Running Processes Before Starting an Upgrade

For a smooth upgrade to Release 4.2, verify that there are no running instances before starting the upgrade.

Symptom:

If you start an upgrade where processes are running and the Runtime database is on an Oracle database server, you can experience issues with a lock not being released. After the upgrade, when the server tries to adjust the database, an exception similar to the following can occur:

ORA-01591 lock held by in-doubt distributed transaction

This causes the environment to fail functionally after the upgrade.

Note: This situation rarely occurs.

Solution:

Resolve transactions noted by "ORA-01591 lock held by in-doubt distributed transaction" in the following cases:

• The in-doubt transaction has locks on critical data or undo segments.
• The cause of the machine, network or software failure cannot be repaired quickly.

To correct this problem, manually execute the ROLLBACK on the Oracle database.

Follow these steps:

1. Identify the transaction identification number for the in-doubt transaction by querying DBA_2PC_PENDING views. Execute following query for the same:

   select * from DBA_2PC_PENDING
   

2. Check the state of the transaction. If state is PREPARED then either:
   • Force a commit using the COMMIT FORCE statement
   • Force a rollback using the ROLLBACK FORCE statement.

     ROLLBACK FORCE 'your local transactionID on this node'
     

     For example:

     ROLLBACK FORCE '1.13.5197';