R12.1: GLPURGE Is Not Running or Staying Pending And Left in The Phase Inactive with Status No Manager
(Doc ID 2243107.1)
Last updated on DECEMBER 16, 2020
Applies to:
Oracle General Ledger - Version 12.1 and laterInformation in this document applies to any platform.
Symptoms
After running GLPURGE the request is not running or staying pending and left in the phase Inactive with status No Manager,
however several other processes are running fine.
The GL Archive and Purge Program (GLPURGE) shows the following error message:
The Manger log file shows the following statement causing No Manger issue.
+-----------------------------------------------------------------+
Application Object Library: Concurrent Processing version XX.X
Copyright (c) YYYY, YYYY, Oracle Corporation. All rights reserved.
STANDARD Concurrent Manager started : DD-MON-YEAR HH:DD:SS
+-----------------------------------------------------------------+
Shutting down Concurrent Manager : DD-MON-YEAR HH:DD:SS
List of errors encountered:
-----START----
_ 1 _
Routine AFPESA cannot construct the name of an executable file for
your concurrent request 9999999.
Check that the file name components are correct and valid on your
system. Check that the environment for the person who started the
concurrent manager
---END---
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |