FNDREVIVER, also recognized as reviver.sh, is normally used to the Internal Concurrent
Manager (ICM) when it fails. When ICM cannot connect to database, it kills itself and spawns
the reviver. Reviver loops for every 30 seconds, try to check if ICM can logon to the database as
apps user. When it does, it starts up the ICM again.
If the failure is due to network outage, or database issue, the managers are restarted
automatically.
Reviver is the recovery mechanism that is come with ATG RUP4, patch 4676589, and runs in the
background. In a Real Applications Cluster (RAC) environment, when the primary node goes
down and ICM is set to migrate to the secondary node, the reviver parameter will be passed to
the secondary node.
The way to determine whether reviver.sh exists or not, is by checking the $FND_TOP/bin
directory. The variable in the context file is ‘s_cp_reviver’ and should be set to “enabled” or
“disabled” which creates AFCPDNR and sets it to “enabled” or “disabled” based on the value of
s_cp_reviver.
The reviver is started by/when ICM starts by passing a parameter reviver=”enabled”. We do this
on the nodem, where we start the manager. If the ICM is set to migrate to the second node,
this parameter will be passed to the second node.
Please Note : Reviver will be automatically enabled when REVIVER_PROCESS=”enabled” is
passed through adcmctl.sh concurrent manager startup script.
On a single concurrent processing node, this is an only way to recover from a database
connection loss.
On a two-node system, here we have the Internal Monitor (FNDIMON). The FNDIMON will
restart the internal manager and by the time the reviver comes up it will likely see that the ICM
is already running and will exit.
FNDIMON depends on its ability to connect to the database to determine if the ICM is running ,
so if the database connection is not available , it will not work and kills itself, whereas reviver is
a shell script that loops until a connection is obtained and starts the manager . The FNDIMON
only works when the database connection is available.
In case if the ICM goes down due to the network problem, then the reviver would be needed to
bring the ICM back up.
The following parameters should be set in the autoconfig file ,and then autoconfig should be rerun to enable reviver.
Concurrent Processing Reviver Process (s_cp_reviver)
Allowed values are {enabled, disabled}.
