Hi DBA_Mates,
We are back again. We would like to share “Concurrent Manager status “System Hold, Fix Manager” one of the most important issue
related to Concurrent Manager.
As we know how Concurrent Manager is important in our
Apps DBA’s life.
Recently, we faced such an issue that suddenly
Concurrent Manager was going down on Node-2 as we have PCP. The status of
Concurrent Manager Shows as “System Hold, Fix
Manager” and we didn’t find
useful in manager’s log also.
As per our earlier this
below post, we got some ideas:
As per these concepts we checked the Node name in front-end
and it was in small letter for the Concurrent Managers who was going down.
The Concurrent Manager on Node-1 was working fine as Node
name was in CAPS entry but in Node-2 Node name was in small and it was going
down suddenly.
When we bounced the application it was showing up but after
some time again it was going down.
This issue starts after purging the FND tables. So, from
now we should remember one thing always as whenever we do the FND table’s
purge, we should run Twice Autoconfig on all nodes.
i.e. EXEC
FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
After this we need to run AutoConfig, twice on all
tiers like first DB nodes then Apps Tiers. In this also, primary node should be
first and last.
Here can see the below changes if we ran once autoconfig:
Before:
Host and domain
values are missing in FND_NODES for MT nodes. Please run autoconfig in all
nodes to fix the issue and then check.
NODE_NAME SERVER_ADDRESS HOST DOMAIN CP WEB DB
VIRTUAL_IP
--------------------
------------------------------ --------------------
---------------------------------------- --- --- ---
----------------------------------------
AUTHENTICATION *
N N N
HOSTNAME IP:198.162.11.1 N Y N
HOSTNAME IP:198.162.11.1
N Y N
HOSTNAME IP:198.162.11.1
Y Y N
HOSTNAME IP:198.162.11.1
Y Y N
HOSTNAME hostname N N
Y hostname-vip
HOSTNAME hostname N N Y hostname-vip
HOSTNAME IP:198.162.11.1 N Y N
After running Autoconfig 2 times on
all MT nodes:
SQL> select
NODE_NAME,SERVER_ADDRESS,HOST,DOMAIN,SUPPORT_CP CP,SUPPORT_WEB WEB,SUPPORT_DB
DB,VIRTUAL_IP from fnd_nodes;
NODE_NAME SERVER_ADDRESS HOST DOMAIN C W D VIRTUAL_IP
------------------------------
------------------------------ --------------------
------------------------------ - - - -------------------------
AUTHENTICATION * N
N N
HOSTNAME IP:198.162.11.1
hostname hostname N Y N
HOSTNAME IP:198.162.11.1 hostname N Y N
HOSTNAME IP:198.162.11.1 hostname Y Y N
HOSTNAME IP:198.162.11.1 hostname Y Y N
HOSTNAME hostname N N
Y hostname-vip
HOSTNAME hostname N N
Y hostname-vip
HOSTNAME IP:198.162.11.1 hostname N Y N
8 rows selected.
Result: Since FND_CONC_CLONE.SETUP_CLEAN we ran, we need to run 2
cycles of autoconfig on all nodes to get the fnd_nodes populated.
When we ran the autoconfig in all MT nodes, we get
populated host and domain values in FND_NODES table.
Hope this may useful and helpful.
Some more
useful links:
I’m not that much of a internet reader to be honest but your sites really nice, keep it up!
ReplyDeleteI'll go ahead and bookmark your website to come back later on.
Cheers
Good write-up. I definiteⅼy appreciate this site.
ReplyDeleteKeep it up!
Hi to all, how is everything, I think every one
ReplyDeleteis getting more from this site, and your views are
pleasant designed for new viewers.
Thanks designed for sharing such a good thought, article is nice, thats why i have read it fully
ReplyDeleteIf you want to get much from this piece of writing then you have to apply these methods to your won webpage.
ReplyDelete