24
Dec

Transaction Managers Restarting

Symptoms:-


The following Concurrent Managers Do Not Start / Die After Restart:

Receiving Transaction Manager
FastFormula Transaction Manager
INV Remote Procedure Manager
PO Document Approval Manager



The following errors are reported in the Internal Concurrent Manager log file.

Routine AFPEIM encountered an error while starting concurrent manager FFTM.
The manager is not able to start properly.
The manager has been put on a SYSTEM HOLD to allow the system administrator to address the issue.
When addressed, the "Fixed" button on the Administer Managers screen can be pressed to restart the manager.

Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM.
The manager is not able to start properly.
The manager has been put on a SYSTEM HOLD to allow the system administrator to address the issue.
When addressed, the "Fixed" button on the Administer Managers screen can be pressed to restart the manager.

Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM.
The manager is not able to start properly.
The manager has been put on a SYSTEM HOLD to allow the system administrator to address the issue.
When addressed, the "Fixed" button on the Administer Managers screen can be pressed to restart the manager.

Solution:-


1. Stop the application services.

2. Confirm the following file versions:
afptm.lc 120.6.12010000.3
The file version can be checked with the following commands:
strings $FND_TOP/bin/FNDTMTST | grep afptm.lc | grep Header
OR
adident Header $FND_TOP/lib/afptm.*

3. If you have a lower version of the file, apply patch 12923944:R12.FND.B.

4. Run adrelink:
cd $PO_TOP/bin
adrelink.sh force=y ranlib=y "PO RCVOLTM"
adrelink.sh force=y ranlib=y "PO POXCON"

5. Bounce the database.

6. Start the application services.

7. Verify Issue.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to Top