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

 Execute below query and check node status:

 SQL> select node_name, node_mode, support_cp, support_web, support_admin,support_forms from FND_NODES;

Steps:

1. Login to the primary node.
2. Source the run file system.
3. Execute 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=<host_name of the deleted node>  -logfile=delete.log.

check the log file for the node deletion.

Using orapki commands to create wallet csr and import certificate

Create a new wallet:

export PATH=$FMW_HOME/webtier/bin:$FMW_HOME/oracle_common/bin:$PATH

mkdir $NE_BASE/inst/$CONTEXT_NAME/certs/Apache/

orapki wallet create -wallet $NE_BASE/inst/$CONTEXT_NAME/certs/Apache/ -auto_login  -pwd Admin1234

Use below command for CSR

orapki wallet add -wallet $NE_BASE/inst/$CONTEXT_NAME/certs/Apache/ -pwd Admin1234 -validity 2000 -keysize 2048 -dn "CN=servername.domain, OU=IT, O=Company Name, L=CityName, ST=CityName, C=AE" 

Display wallet:

orapki wallet display -wallet $NE_BASE/inst/$CONTEXT_NAME/certs/Apache/

Export CSR to a file

orapki wallet export -wallet $NE_BASE/inst/$CONTEXT_NAME/certs/Apache/ -dn "CN=servername.domain, OU=IT, O=Company Name, L=CityName, ST=CityName, C=AE"  -request servername.csr

Import root 

orapki wallet add -wallet $NE_BASE/inst/$CONTEXT_NAME/certs/Apache/ -trusted_cert -cert /home/oracle/RootCA.crt -pwd Admin1234

Import Server/User/Signed certficate

orapki wallet add -wallet $NE_BASE/inst/$CONTEXT_NAME/certs/Apache/ -user_cert -cert /home/oracle/servername.crt -pwd Admin1234

12.2 ADOP Prepare Phase Issue : prepare failed with “Use of uninitialized value $result in split” in txkADOPValidations.error

 Error:

Validating configuration on node: [apps].
Log: /u01/install/APPS/fs_ne/EBSapps/log/adop/87/20210803_114127/prepare/validate/apps
[UNEXPECTED]Error occurred running “perl /u01/install/APPS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl -contextfile=/u01/install/APPS/fs2/inst/apps/ebsdb_apps/appl/admin/ebsdb_apps.xml -patchctxfile=/u01/install/APPS/fs1/inst/apps/ebsdb_apps/appl/admin/ebsdb_apps.xml -phase=prepare -logloc=/u01/install/APPS/fs_ne/EBSapps/log/adop/87/20210803_114127/prepare/validate/apps -promptmsg=hide”
[UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on apps

When looking at ADOP logs:

Error in adop logs,

vi /u01/install/APPS/fs_ne/EBSapps/log/adop/87/20210803_114127/prepare/validate/apps/txkADOPValidations.error

Use of uninitialized value $result in split at /u01/install/APPS/fs2/EBSapps/appl/au/12.0.0/perl/TXK/ADOPValidationUtils.pm line 1294.

Solution:

If you run the following query it should return no rows:

select distinct(PATH) from FND_OAM_CONTEXT_FILES where NAME not in (‘TEMPLATE’,’METADATA’,’config.txt’) and CTX_TYPE=’A’ and (status is null or upper(status) in (‘S’,’F’)) and EXTRACTVALUE(XMLType(TEXT),’//file_edition_type’) = ‘patch’;

Before proceeding with below steps, take a backup of your context file,

To fix this issue, follow the below steps to upload the missing PATCH context file to the database:

1. Get the value of your patch context file

1.1. Source your PATCH file system

1.2. Echo the value of $CONTEXT_FILE and take note of it. You will use this value in step #3

2. Source the RUN filesystem

3. Execute the following command on the run filesystem to upload the patch context file to the database

$ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer \
action=upload \
contextfile=<Enter Your Full Patch Context XML File Location> \
logfile=/tmp/patchctxupload.log

For Example:

$ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer \
action=upload \
contextfile=/u01/install/APPS/fs1/inst/apps/ebsdb_apps/appl/admin/ebsdb_apps.xml \
logfile=/home/oracle/patchctxupload.log

Note: the context file parameter should point to the physical location of the patch context file in your system

4. Run the following query and it should return one entry for the recently uploaded context file

select distinct(PATH) from FND_OAM_CONTEXT_FILES where NAME not in (‘TEMPLATE’,’METADATA’,’config.txt’) and CTX_TYPE=’A’ and (status is null or upper(status) in (‘S’,’F’)) and EXTRACTVALUE(XMLType(TEXT),’//file_edition_type’) = ‘patch’;

 

RC-50013: Fatal: Instantiate driver did not complete successfully

 

RC-50013: Fatal: Instantiate driver did not complete successfully

Problem:

While cloning recently upgraded EBS environment from [Release 11 to 12.1]
 using Rapid Clone with dbTechStack option, the following error occurs:

RC-50013: Fatal: Instantiate driver did not complete successfully

Contents of log file:

[AutoConfig Error Report] The following report lists errors AutoConfig encountered during each phase of its execution.  Errors are grouped by directory and phase. The report format is:       <filename>  <phase>  <return code where appropriate>   [APPLY PHASE]   AutoConfig could not successfully execute the following scripts:     Directory: /clone/oracle/product/12101/perl/bin/perl -I /clone/oracle/product/12101/perl/lib/5.14.1 -I /clone/oracle/product/12101/perl/lib/site_perl/5.14.1 -I /clone/oracle/product/12101/appsutil/perl /clone/oracle/product/12101/appsutil/clone       ouicli.pl               INSTE8_APPLY       255 AutoConfig is exiting with status 1 RC-50013: Fatal: Instantiate driver did not complete successfully. /clone/oracle/product/12101appsutil/driver/regclone.drv

Cause:

As the log file states that autoconfig failed as it could not execute the following perl script "ouicl.pl"

The possible reason could be:

1.     Either the script is not found at the location

2.     If the script is present, try to run the script manually.

3.     If it fails with the same error then the perl program "ouicli.pl" is unable to locate the JDK installation.

Solution:

·         If the script "ouicli.pl" is not found under clone directory, I would suggest to copy appsutil from source to target system and unzip appsutil under< ORACLE_HOME>

            $ unzip -o appsutil.zip

·         Check if the JDK/JRE installed under the "<RDBMS ORACLE_HOME>/appsutil/jre/bin" directory. If there is no "java" under "<RDBMS ORACLE_HOME>/appsutil/jre/bin", you will need to replace the "jre" directory and all sub-directories with a full JDK/JRE installation. Generally, you can find this under "$ORACLE_HOME/jdk"

                        $ cp -r $ORACLE_HOME/jdk/ $ORACLE_HOME/appsutil/jre/

·         Now check  that the java" executable under "<RDBMS ORACLE_HOME>/appsutil/jre/bin" is working fine.

·         If the java executable is working fine, make sure it is referenced directly in the Context File for DB tier. Check it with the below command:

                        $ cd $ORACLE_HOME/appsutil

                        $ grep s_adjvaprg< CONTEXT_NAME>.xml

                                    <ADJVAPRG oa_var="s_adjvaprg" osd="UNIX">/<ORACLE_HOME>/appsutil/jre/bin/java</ADJVAPRG>

·         Again run the cloning process,

                        perl adcfgclone.pl dbTechStack

                                    ApplyDatabase Completed Successfully.