Delete a node from application Tier in Oracle Apps R12.2

 

Delete a node from application Tier in Oracle Apps R12.2 in shared application file system.

.4 Deleting an Application Tier Node

Note: These steps are ONLY for deletion of secondary application tier nodes. The primary application tier node cannot be deleted using these steps.

The following steps should be performed to delete a secondary application tier node from an existing Oracle E-Business Suite Release 12.2 multi-node instance. The steps described in this section are applicable to secondary application tier nodes with shared and non-shared file systems.

Note: In case OHS is enabled only on the secondary node being deleted, OHS needs to first be enabled on some other node before starting with deletion of the node.

Before performing the following steps, ensure that the WebLogic administration server is running from both the Run and Patch Edition File Systems of the primary application tier node.

Note: Do not perform a 'delete node' operation when a patching cycle is active.

1. Delete the run file system and patch file system configuration of the secondary application tier node.
   
   
   
   Note: Deletion of nodes may need to be performed in two scenarios - when the node is still accessible (users are able to login to the node) and in the remote case when the node is not accessible due to some issues ( the node may not be physically present and/or login to the node is not possible).
   
   In the first scenario, all information related to the node has to be cleaned up altogether (including removal of references from the WebLogic domain and EBS topology as well as removal of the file system and inventory references). Case 1 describes the steps to be performed in this scenario.
   
   In the second scenario, references to the node can be cleaned up only from the WebLogic domain and the EBS topology. The steps for deletion of secondary nodes in this scenario are described in Case 2 below. Please note that this option has been introduced in R12.TXK.C.DELTA.6 and is not available in the earlier releases.
   
   In order to keep the E-Business Suite instance in a consistent state, steps should be followed strictly based on the scenario.
   
   
   Case 1: If the secondary node to be deleted is accessible, run the following steps:
   
   
   1. Login to the secondary node to be deleted.
      
      
   2. Source the run file system.
      
      
   3. Ensure that all application tier services from the run and patch file system for the node to be deleted are shut down.
      
      
   4. Run the ebs-delete-node option of the adProvisionEBS.pl script as follows:
      
      $ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl ebs-delete-node \
-contextfile=<CONTEXT_FILE> -logfile=<LOG_FILE>
      This will delete the managed servers, OHS instances and Node Manager on the current node from the run file system WebLogic domain.
      
      
   5. If the node is a non-shared node, verify and remove the following Oracle Home entries of both the Run and Patch file systems from the Oracle Inventory:
      
      
      • <FMW_HOME>/webtier
      • <FMW_HOME>/oracle_common
      • <FMW_HOME>/Oracle_EBS-app1
      
      If any of the above Oracle Home entries are already registered in Oracle Inventory, you can run the following command to de-register or detach that Oracle Home:
      $ cd <Oracle Home>/oui/bin
$ ./runInstaller -detachhome ORACLE_HOME=<Oracle Home Location> [-invPtrLoc <s_invPtrLoc>]
      Here,
-invPtrLoc argument needs to be specified only if the 'EBS installation central' inventory is being used.
      s_invPtrLoc is the context variable that stores the inventory pointer location.
      
      For example:
      $ cd /u02/r122/fs1/FMW_Home/oracle_common/oui/bin
$ ./runInstaller -detachhome \
ORACLE_HOME=/u02/r122/fs1/FMW_Home/oracle_common -silent
      Note: The Oracle Home <FMW_HOME>/webtier should be de-registered from the Oracle Inventory before trying to remove the Oracle Home <FMW_HOME>/oracle_common.
      
      
   6. If the node is a non-shared node, verify and remove the following Oracle Home entry from the Oracle Inventory:
      
<OracleAS Tools 10.1.2 ORACLE_HOME>
      
      If the above Oracle Home entry is registered in Oracle Inventory, you can run the following command to de-register the Oracle Home:
      
      $ ./runInstaller -removeHome ORACLE_HOME=<s_tools_oh> -silent
      Here,
-invPtrLoc argument needs to be specified only if the 'EBS installation central' inventory is being used.
      s_invPtrLoc is the context variable that stores the inventory pointer location.
      
      For example:
      
      $ cd /u02/r122/fs1/EBSapps/10.1.2/oui/bin
$ ./runInstaller -removeHome \
ORACLE_HOME=/u02/r122/fs1/EBSapps/10.1.2 -silent
      
      
   
   Case 2: If the secondary node to be deleted is not accessible, run the following steps to remove the node from the FND topology and the EBS domain:
   
   
   1. Login to the primary node.
      
      
   2. Source the run file system.
      
      
   3. Run the ebs-delete-node option of the adProvisionEBS.pl script as follows:
      
      $ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl ebs-delete-node \
-contextfile=<CONTEXT_FILE> -hostname=<HOSTNAME OF NODE TO BE DELETED> -logfile=<LOG_FILE>
      This will delete all information corresponding to the specified node from the Weblogic domain like the managed servers, OHS instances and Node Manager of the specified node from both the run and patch file system WebLogic domain. In addition, it will also remove the node from the list of active nodes registered in the topology.
      
      
      
      Note: Since the steps mentioned in Case 2 take care of only partial cleanup of the node, these steps should be performed only in case the node to be deleted is not accessible due to some issues. In all other scenarios, the nodes should be deleted by following steps mentioned in Case1. Otherwise, this may lead to the E-Business Suite instance being in an inconsistent state.
      
      
   
   
2. Sync the OHS configuration on the other nodes to remove references of the deleted node.
   
   Perform the following steps on the other nodes:
   
   1. Source the run file system.
      
      
   2. If any of the managed servers from the deleted node are part of the cluster configuration defined on the current node, run the following command to delete details of these managed servers 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, if the deleted node was on host 'testserver1' and domain 'example.com' and it contained managed servers oacore_server3 and oafm_server3 with ports 7205 and 7605 respectively, the following command should be run to remove references to these managed servers:
      $ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl -contextfile=<CONTEXT_FILE>
-configoption=removeMS -oacore=testserver1.example.com:7205 -oafm=testserver1.example.com:7605
3. Review and update the value of the context variable 's_shared_file_system' on the primary node (required only while deleting a shared file system node).
   
   If the deleted node was the only node sharing the file system with a primary application tier node, run the following steps on the primary node:
   
   
   1. Set the value of the context variable 's_shared_file_system' in the run context file of the primary node to 'false' via the Oracle Applications Manager.
      
      
   2. Login to the primary node.
      
      
   3. Source the run file system.
      
      
   4. Run AutoConfig as follows:
      
      On UNIX:
      
      
      $ sh <ADMIN_SCRIPTS_HOME>/adautocfg.sh
      On Windows:
      
      
      C:\> <ADMIN_SCRIPTS_HOME>\adautocfg.cmd
      
      
4. Run AutoConfig on the database tier.
   
   
   1. Log in to the database tier node.
      
      
   2. Run AutoConfig on the database tier by running the following command:
      
      For UNIX:
      
      $ <RDBMS_OH>/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh
      For Windows:
      
      C:>\ <RDBMS_OH>\appsutil\scripts\<CONTEXT_NAME>\adautocfg.cmd
      This step is required to sync-up the tcp.invited_nodes attribute in sqlnet.ora to remove the deleted node from the value of this attribute.
       
   3. Restart the database listener by running the following command:
       
      For UNIX:
      $ sh <RDBMS_OH>/appsutil/scripts/<CONTEXT_NAME>/addlnctl.sh stop <ORACLE_SID>
$ sh <RDBMS_OH>/appsutil/scripts/<CONTEXT_NAME>/addlnctl.sh start <ORACLE_SID>
      For Windows:
      C:\> <RDBMS_OH>\appsutil\scripts\<CONTEXT_NAME>\addlnctl.cmd stop <ORACLE_SID>
C:\> <RDBMS_OH>\appsutil\scripts\<CONTEXT_NAME>\addlnctl.cmd start <ORACLE_SID>

Notes:

• Using the ebs-delete-node option as mentioned above will not delete the contents of the file system. This has to be done manually by the customer once the above steps to delete the node are completed successfully.
  
  For non-shared node, the following directories can be deleted:
  
  
  • <NE_BASE>
  • <RUN_BASE>
  • <PATCH_BASE>
  • EBSapps.env
  
  For a shared file system node, only the <INST_TOP> directory of the Run Edition File System and the Patch Edition File System should be deleted.
  
  
• On all OHS enabled nodes, patch file system OHS configuration will automatically be synced up during next adop prepare phase.

Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)