- I was working on the R12.2 Test env and I was supposed to decrease the JVM for the oacore(delete the managed server)
- The procedure to increase or decrease JVM was quite simple in R12.1.X. In Oracle E-Business Suite Release 12, the oacore, oafm, forms, and forms-c4ws services were deployed as applications on OC4J instances and were managed by Oracle Process Manager (OPMN). So we just need to increase the numprocs in opmn.xml and start the services or run autoconfig with decreased numprocs in the Context file
- I came to know it is quite different in R12.2.X as Oracle WebLogic Server has replaced OC4J in Oracle E-Business Suite Release 12.2, these services are now deployed as applications on individual managed servers.
- Only part of the configuration of these applications and managed servers are still managed via AutoConfig.The rest of the things need to do quite differently
- I have already explained how to add a managed server in my previous post
- In the below, I would be explaining what I learned from that experience and How to delete the managed server in R12.2. I will particularly be taking the example of oacore
Steps on How to delete the manage server in R12.2
(1)Deletion of managed servers needs to be done on the run file system when there is no active ADOP cycle. During the next adop prepare, the Configuration Change Detector identifies that the addition has been made and the managed servers are automatically synced up from the run file system to the patch file system. The synchronization also gets done when fs_clone is executed.
2. If the managed server to be deleted is running, shut it down as follows:
On Unix:
$ sh <ADMIN_SCRIPTS_HOME>/admanagedsrvctl.sh stop <MANAGED SERVER NAME>
For example, before deleting a managed server ‘oacore_server2’, execute the following command to shut it down.
$ sh <ADMIN_SCRIPTS_HOME>/admanagedsrvctl.sh stop oacore_server2
3. Run the command below on the application tier node where the managed server resides. This will delete the managed server, and also update the respective context variables that contain references to the deleted managed server.
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile=<CONTEXT_FILE> -managedsrvname=<MANAGED_SERVER_NAME> \
-servicetype=<SERVICE_TYPE> -logfile=<LOGFILE>
For example, for deleting a managed server ‘oacore_server2’ of type ‘oacore’, execute the following command:
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile=<CONTEXT_FILE> -managedsrvname=oacore_server2 \
-servicetype=oacore -logfile=<APPLRGF>/TXK/delMS_oacoreserver2.log
It is possible to delete the managed server using the WebLogic console also. Steps are
(a) Login to weblogic Console
(b) Click on Lock and Edit
(c) Go to servers tab
(d) Select the server to be deleted
(e) Click on Delete
(d) Click on Release the configuration
4. Perform the following steps on all application tier nodes participating in the same cluster as the deleted managed server:
a.Source the run file system.
b.If the deleted managed server is part of the cluster configuration defined on the current node, execute the following command to delete details of the managed server from the OHS configuration files mod_wl_ohs.conf and apps. conf on the current node:
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl \
-contextfile=<CONTEXT_FILE> \
-configoption=removeMS \
-oacore=<host>.<domain>:<port> \
-oafm=<host>.<domain>:<port> \
-forms=<host>.<domain>:<port> \
-formsc4ws=<host>.<domain>:<port> \
-ekanban=<host>.<domain>:<port> \
-accessgate=<host>.<domain>:<port> \
-yms=<host>.<domain>:<port>
where
The argument contextfile accepts the complete path to the context file.
The arguments oacore, oafm, forms, formsc4ws, ekanban, accessgate and yms accept a comma-separated list of managed server details in the following format:
<host>.<domain>:<port>
host, domain, and port are the hostname, domain, and port of the managed server whose reference is to be deleted.
For example, to remove references of the deleted managed server oacore_server2 with port 9705 on host ‘myserver’ and domain ‘go.com’, the following command should be executed:
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl -contextfile=<CONTEXT_FILE> \
-configoption=removeMS -oacore=myserver.go.com:9705
c. If Oracle HTTP Server is enabled on the node, restart it as follows:
On UNIX:
$ sh <ADMIN_SCRIPTS_HOME>/adapcctl.sh stop
$ sh <ADMIN_SCRIPTS_HOME>/adapcctl.sh start
As I told you earlier, the steps are very different from R12.1.X in R12.2.X. I hope the steps are clear How to delete the managed server in R12.2. Please do let me know if any questions regarding the procedure. I will be happy to solve any issues with it. Weblogic inclusion in the tech stack has complicated the stuff and we need to be very careful with executing steps in R12.2
Articles you must read on R12.2
Login flow and basic troubleshooting for R12.2
Service Group changes in R12.2
adopmon and adopreports utility R12.2.5
R12.2 Online patching cycle Summary
Isolating post-upgrade concurrent programs to a separate manager queue in R12.2
R12.2 RapidWiz Installed Components and System Requirements
Top AWR useful queries for R12.2/R12.1 Upgrade
How to rollback the patch after failed cutover phase in R12.2
forward cross edition triggers R12.2
40 question you must know about R12.2