Forgot WebLogic Password | Reset WebLogic Password

If you forgot / doesn't aware of Weblogic Console password. Want to Reset it? 

1. Shut down all running services. 

Since the Admin Server password is not known, the servers cannot be stopped from the console and so must be killed in command mode as follows.
Connect to the Oracle E-Business Suite instance and source the application tier environment file.

2. Identify the PIDs of Node Manager, Admin Server, and all running Managed Servers:
$ ps -ef | grep “NodeManager”
$ ps -ef | grep “weblogic.Name=AdminServer”
$ ps -ef | grep “weblogic.Name=forms-c4ws_server”
$ ps -ef | grep “weblogic.Name=forms_server”
$ ps -ef | grep “weblogic.Name=oafm_server”
$ ps -ef | grep “weblogic.Name=oacore_server”

   Kill all these processes, starting with Node Manager and followed by the Managed Servers.

           Back up these folders of all the services under          

           $EBS_DOMAIN_HOME

(You can delete these files once you reset the password):

<EBS_DOMAIN_HOME>/security/ DefaultAuthenticatorInit.ldift
<EBS_DOMAIN_HOME>/servers/<server_name>/data/ldap
<EBS_DOMAIN_HOME>/servers/<server_name>/security/boot.prope

ties
<EBS_DOMAIN_HOME>/servers/<server_name>/data/nodemanager/boot.properties

Where:
<EBS_DOMAIN_HOME> is the absolute path of the EBS WebLogic domain
<server_name> is the name of the server directory under <EBS_DOMAIN_HOME>.
If the password is not reset correctly, the backed up files and folders can be restored.

Ø  Set up a new environment to change the WLS AdminServer password.
a) Start a new session and connect to the Oracle E-Business Suite instance.
b) Do not source the application tier environment file.
c) Run the following command to source the WebLogic Server domain environment:
$ cd <EBS_DOMAIN_HOME>/bin
$ source setDomainEnv.sh

d) Run the following commands:

$ cd <EBS_DOMAIN_HOME>/security
$java weblogic.security.utils.AdminAccount <wls_adminuser> <wls_admin_new_password> .
Where:
<wls_adminuser> is the same as the value of context variable s_wls_admin_user
<wls_admin_new_password> is the new WLS AdminServer password you wish to set.
Note: Do not neglect the dot (‘.’) in the above command: it is needed to specify the current domain directory.

1.                 Start AdminServer from the command line. You will be prompted for the WebLogic Server username and password, so that the AdminServer boot.properties file can be generated.
a) Go to the EBS Domain Home:
$ cd <EBS_DOMAIN_HOME>

b) Start AdminServer:
$ java <s_nm_jvm_startup_properties> -Dweblogic.system.StoreBootIdentity=true   -Dweblogic.Name=AdminServer weblogic.Server
Where:
<s_nm_jvm_startup_properties> is the same as the value of context variable   ss_nm_jvm_startup_properties

Find s_nm_jvm_startup_properties in:

In application contextfile

$INST_TOP/appl/admin search for parameter "nm_jvm_startup_properties"

grep nm_jvm_startup_properties context_file.xml

-XX:PermSize=128m -XX:MaxPermSize=384m -Xms512m -Xmx512m -Djava.security.policy=/app01/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.policy -Djava.security.egd=file:/dev/./urandom -Dweblogic.ProductionModeEnabled=true -da

 -Dplatform.home=/app01/applmgr/fs1/FMW_Home/wlserver_10.3 -Dwls.home=/app01/applmgr/fs1/FMW_Home/wlserver_10.3/server -Dweblogic.home=/app01/applmgr/fs1/FMW_Home/wlserver_10.3/server

-Dcommon.components.home=/app01/applmgr/fs1/FMW_Home/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger

-Ddomain.home=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS -Doracle.server.config.dir=

/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig

-Digf.arisidbeans.carmlloc=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig/carml -Digf.arisidstack.home=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig/arisidprovider

-Doracle.security.jps.config=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/servers/AdminServer/tmp/_WL_user

-Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/app01/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.ossoiap_11.1.1,/app01/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.oamprovider_11.1.1

-Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dportlet.oracle.home=/app01/applmgr/fs1/FMW_Home/oracle_common -Dem.oracle.home=/app01/applmgr/fs1/FMW_Home/oracle_common

-Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app01/applmgr/fs1/FMW_Home/patch_wls1036/profiles/default/sysext_manifest_classpath

Example:

java -XX:PermSize=128m -XX:MaxPermSize=384m -Xms512m -Xmx512m -Djava.security.policy=/app01/applmgr/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.policy -Djava.security.egd=file:/dev/./urandom -Dweblogic.ProductionModeEnabled=true

-da -Dplatform.home=/app01/applmgr/fs1/FMW_Home/wlserver_10.3 -Dwls.home=/app01/applmgr/fs1/FMW_Home/wlserver_10.3/server -Dweblogic.home=/app01/applmgr/fs1/FMW_Home/wlserver_10.3/server -Dcommon.components.home=

/app01/applmgr/fs1/FMW_Home/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS

-Doracle.server.config.dir=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=

/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig -Digf.arisidbeans.carmlloc=/app01/applmgr/fs1/FMW_Home/user_projects/domains/

EBS_domain_VIS/config/fmwconfig/carml -Digf.arisidstack.home=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig/arisidprovider

-Doracle.security.jps.config=/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=

/app01/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS/servers/AdminServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=

/app01/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.ossoiap_11.1.1,/app01/applmgr/fs1/FMW_Home/oracle_common/modules/oracle.oamprovider_11.1.1

-Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dportlet.oracle.home=/app01/applmgr/fs1/FMW_Home/oracle_common

-Dem.oracle.home=/app01/applmgr/fs1/FMW_Home/oracle_common -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false

-Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app01/applmgr/fs1/FMW_Home/patch_wls1036/profiles/default/sysext_manifest_classpath

 -Dweblogic.system.StoreBootIdentity=true -Dweblogic.Name=AdminServer weblogic.Server

The above command prompts for the WebLogic Server username and  password:
Enter username to boot WebLogic server:
Enter password to boot WebLogic server:
Provide the same credentials as you provided in Step 3.

2.                 Change Node Manager password
a) Log in to the WebLogic Administration console.
b) Click the ‘Lock & Edit’ button.
c) In the left panel, click on the EBS Domain link.
d) Select the ‘Security’ tab.
e) Click on the ‘Advanced’ link.
f) Edit the ‘Node Manager password’ field and set it to the new WebLogic Server password. The password should be same as set in Step 3.
g) Edit the ‘Confirm Node Manager Password’ field and set it to the new WebLogic Server password. The password should be same as set in Step 3.
h) Save and activate the changes.

3.                 The first time, AdminServer has to be stopped from the Admin console. Follow  these steps:
a)Log in to the WebLogic Administration console.
b)Shut down AdminServer.

4.                 Set up your environment to start AdminServer again. AdminServer should now be started using the normal AD script, which will also start Node Manager using the new password.
a) Launch a new session and connect to the Oracle E-Business Suite instance.
b) Source the application tier environment file.
c) Start AdminServer with the following command:
$ $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

5.                 Start the Managed Servers. For the first time, all Managed Servers should be started  from theWebLogic Server Admin console. This step will create boot.properties files for the respective Managed Servers. Follow these steps:
a) Log in to the WebLogic Server Administration Console
b) Start all Managed Servers, one at a time (one by one)

9.Shut down all the Managed Servers. This is so the new credentials will be picked up at the next startup. Follow these steps:
a) Log in to the WebLogic AdminServer console.
b) Shut down all Managed Servers.
c)  Shut down AdminServer.

1.                 Shut down Node Manager using the normal AD script.
$ $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

2.                 Copy the boot.properties file for each Managed Server.WebLogic Server native scripts use the boot.properties file. The above steps have created the boot.properties file under <EBS_DOMAIN_HOME>/servers/<Managed Servername>/data/nodemanager, which is used by Node Manager. For each ManagedServer, copy the newly-generated boot.properties file from <EBS_DOMAIN_HOME>/servers/<Managed Server name>/data/nodemanager to <EBS_DOMAIN_HOME>/servers/<Managed Server name>/security.
The EBS WebLogic Server domain password has now been changed, and all servers can now be started using the normal AD scripts.
To start AdminServer:
$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
To start the Managed Servers:
$ $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start <managed_server_name>

3.The above steps have changed the Oracle WebLogic AdminServer password on the run file system. You now need to perform an fs_clone operation, to change the
WebLogic EBS Domain password on the patch file system:
a) Launch a new session and connect to the Oracle E-Business Suite instance.
b) Source the application tier environment file.
c) Run the command:
$ adop phase=fs_clone

XML Publisher / Applications Administration is not a valid responsibility for the current User

XML Publisher / Applications Administration is not a valid responsibility for the current User

Applies to: BI Publisher (formerly XML Publisher) - Version 11.5 to 11.5 [Release 11.5]    Information in this document applies to any platform.

Symptoms: When trying to access the XML Publisher Administrator Responsibility.

This may come after upgrading the XML Publisher version or in a new installation.

Getting error :
XML Publisher Administrator is not a valid responsibility for the current user

Solution: 

Login with System Administrator Responsibility
Navigate to Profile-->System, click on User and enter the user name
Search for profile 'Applications Start Page'. Delete the value set at user level and save
Go to Functional Administrator -> Clear Cache
Try logging into the account and try again

Posted by: Anil Bandi

Oracle DBA

ORA-01017: invalid username/password logon denied

When we are trying to connect database as

$sqlplus / as sysdba

Error:

ORA-01017: invalid username/password; logon denied

SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus

Solution:

We need to change the password file

Connect to oracle user and change directory to

$cd $ORACLE_HOME/dbs

$orapwd file=$ORACLE_HOME/dbs/oraSID password=xyz force=y

Here you have to enter your password instead of xyz and your DB name instead of SID.

Posted by: Anil Bandi

Oracle Apps DBA

How to Increase the Number of Concurrent Request Processes

Login to the application

Switch to System Administrator responsibility

Go to Concurrent Manager Define

Query “Standard Manager”  and click on workshifts

Increase the number (as per your requirement) in the Processes column

Posted by: Anil Bandi

Oracle Apps DBA

Encountered unrecognized patch ID

“Encountered unrecognized patch ID” Failures when trying to apply WLS Patch using bsu Smart Update

Applies to: Oracle Weblogic Server – Version 9.0 to 10.3.6

Information in this document applies to any platform.

Symptoms: When attempting to remove a patch currently  applied or apply a newly downloaded patch using the Smart Update tool in command line, the following error occurs:

Encountered unrecognized patch ID: XYZ  (OR)  Unable to locate the specified product directory [/wlserver_10.3]

Cause: This error may cause due to the wrong version  patch you are trying to apply

Solution:

1.Recheck the patch version of weblogic server you are using.

Choose the right version and unzip the patch recommended while running checkMTpatch.sh. Then unzip the patch in the PATCH_TOP dir.

2.Check the permissions for the patches and move the patches into $FMW_HOME/utils/bsu/cache_dir

After moving the patch we have to smart update the patch by running bsu.

$bsu.sh –install –patch download_dir=$FMW_HOME/utils/bsu/cache_dir  -patchlist=DN1F –prod_dir=$FMW_HOME/wlserver_10.3

If it throws any error like Unable to locate the specified product directory [/wlserver_10.3]

3. Give the full path instead of $FMW_HOME and try again.

Once all are set properly it will check for conflicts …

Checking for conflicts......

Conflict(s) detected - resolve conflict condition and execute patch installation again

Conflict condition details follow:

Patch DN1F is mutually exclusive and cannot coexist with patch(es): CIH8

Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded

        at java.util.HashMap.inflateTable(HashMap.java:316)

        at java.util.HashMap.put(HashMap.java:488)

        at com.bea.cie.common.dao.xbean.XBeanDataHandler.loadPropertyMap(XBeanDataHandler.java:778)

        at com.bea.cie.common.dao.xbean.XBeanDataHandler.<init>(XBeanDataHandler.java:99)

        at com.bea.cie.common.dao.xbean.XBeanDataHandler.createDataHandler(XBeanDataHandler.java:559)

        at com.bea.cie.common.dao.xbean.XBeanDataHandler.getComplexValue(XBeanDataHandler.java:455)

        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:442)

        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:464)

        at com.bea.plateng.patch.dao.cat.PatchCatalog.getPatchDependencies(PatchCatalog.java:56)

        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getInvalidatedPatchMap(PatchCatalogHelper.java:1621)

        at com.bea.plateng.patch.PatchSystem.updatePatchCatalog(PatchSystem.java:436)

        at com.bea.plateng.patch.PatchSystem.refresh(PatchSystem.java:130)

        at com.bea.plateng.patch.PatchSystem.setCacheDir(PatchSystem.java:201)

        at com.bea.plateng.patch.Patch.main(Patch.java:306)

If any conflicts occurs it recommends to remove the existing patch. In the above case it is suggesting to Remove CIH8 patch. Once we remove the conflict patch, then only it allows us to apply new patch Smart Update.

To remove the conflicted patches run the below command.

$bsu.sh –remove –patchlist=CIH8 –prod_dir=$FMW_HOME/wlserver_10.3

It will take time to remove. Once the conflicted patch is removed we can apply the recommended patch.

Posted by: Anil Bandi

Oracle Apps DBA

      Oracle EBS 12.2 Opatch Utility error

  OPATCH lsinventory : bash : Command not found

Applies to: Oracle Apps DBA

Symptoms:

E-Business suite 12.2, DB patching opatch related issues

When you are applying a patch ensure that you verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, you have to run the following command.

$ opatch lsinventory

bash: opatch: command not found...

Similar command is: 'patch'

Solution:

You have to export the path

export PATH=$PATH:$ORACLE_HOME/OPatch:$ORACLE_HOME/bin

Posted by: Anil Bandi

Apps DBA

How to kill processes run by a User on Linux

     If you are a DBA, there are situations where you want to kill all processes belonging to a specific user, for example because the user is being removed or the user is forking malicious processes. It will take long time to kill individual processes of the user one by one manually. In this post I will show you how to kill all the process IDs at a time launched by a user.

     Here I use a command that kills all the processes owned by Linux user say "applfprd".

      To generate the process IDs, we use ps command

$ ps -ef | grep applfprd | awk {'print $2'}

Now we have to kill the process IDs which are generated above

$ ps -ef | grep applfprd | awk {'print $2'} | xargs kill -9

                                          (or)

$ sudo pkill -u applfprd

             

                                          (or)

$ pgrep -u applfprd | sudo xargs kill -9

                                           (or) 

$ sudo killall -u applfprd

Posted by: Anil Bandi

 Oracle Apps DBA

Oracle EBS 12.2 ADOP utility error

ADOP exiting with status = 255 (Fail)

In this Document

Symptoms 

Cause

Solution

Applies to:

Oracle Applications DBA - Version 12.2 and later. This can be applies to all platforms.

Symptoms

E-Business Suite 12.2, Online Patching ADOP Utility related issues

 $adop phase=apply patches=25820806,26720905 merge=yes hotpatch=yes

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Validating credentials.

Initializing.

Run Edition context  : /u02/ebsappl/SID/fs1/inst/apps/FRESH_test/appl/admin/SID_host.xml      Patch edition context: /u02/ebsappl/SID/fs2/inst/apps/FRESH_test/appl/admin/SID_host.xml 

                                           

Cause

An invalid server name was specified in the context file.

The applications context file, SID_host.xml, contains the following incorrect entries for parameters

s_apps_jdbc_connect_descriptor  and

s_apps_jdbc_patch_connect_descriptor

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=ora.<domain name>.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SID)))

 jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ora.<domain name>.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ebs_patch)(INSTANCE_NAME=SID)))

Solution

To resolve the issue test the following steps in a development instance and then migrate accordingly

1. The applications context file, SID_host.xml, contains the following incorrect entries for parameters

s_apps_jdbc_connect_descriptor   and

s_apps_jdbc_patch_connect_descriptor

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=ora12.<domain name>.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SID)))

 jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ora12.<domain name>.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ebs_patch)(INSTANCE_NAME=SID)))

Use the OAM context editor to remove the second host definition, which is incorrect.

The part to be removed from each is

  (ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>.com)(PORT=1521)).

2. Once the context file has been set correctly, run autoconfig on the apps tier and run 

adop phase=fs_clone

    Then stop and start the apps services, and log out / login as the applmgr user to ensure the new autoconfig environment variables are picked up by the system.

3. Test the adop utility again to confirm that the error has been resolved.

ADOP Fails With Error: Unable to Find Appltop_id In this Document Symptoms Cause Solution Symptoms  When running ADOP with phase=apply, restart=yes it fails with following error: [UNEXPECTED]Unable to find appltop_id for host test in database Node registry is valid. [WARNING]   MTCC has not been run. Apply Patch 17537119 and run checkMTpatch.sh Checking for existing adop sessions.     [UNEXPECTED]Unable to find appltop_id for host test in database     [UNEXPECTED]Invalid APPL_TOP ID: "".     [UNEXPECTED]Unrecoverable error occurred. Exiting current adop session.     adop exiting with status = 2 (Fail) Cause  The SQL statement ADOP uses to get the admin node name is:    select node_name 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') = 'run'    and EXTRACTVALUE(XMLType(TEXT),'//oa_service_group_status[@oa_var=''s_web_admin_status'']')='enabled'    and EXTRACTVALUE(XMLType(TEXT),'//oa_service_list/oa_service[@type=''admin_server'']/oa_service_status')='enabled'; Execute above SQL statement manually, it returns: node_name appltest appltest The problem is due to the table FND_OAM_CONTEXT_FILES has duplicate entries. Solution Test the following steps in a non critical development instance where the issue can be reproduced and then migrate according if the problem is resolved: 1. Back up the table FND_OAM_CONTEXT_FILES table. 2. Delete the duplicate record in table FND_OAM_CONTEXT_FILES reflected in the following select: select node_name 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') = 'run'    and EXTRACTVALUE(XMLType(TEXT),'//oa_service_group_status[@oa_var=''s_web_admin_status'']')='enabled'    and EXTRACTVALUE(XMLType(TEXT),'//oa_service_list/oa_service[@type=''admin_server'']/oa_service_status')='enabled'; Please check the column "NAME" and "PATH" to identify the duplicate records. The duplicate record may come from the source environment. Then use statement "delete from FND_OAM_CONTEXT_FILES where <duplicate record conditions>" to delete the record and commit. Please note, the standard process to populate the table FND_OAM_CONTEXT_FILES  is to run autoconfig. Since in this case ADOP cycle is running, above action plan is a workaround. Please perform above action under Oracle support's instruction. 3. Re-run the select above to ensure it returns the correct value. 4. Retest the issue. 12.2 EBS Patch 25820806 (R12.AD.C.Delta.10) fails when merged and applied with Patch 26720905:R12.AD.C with ORA-01400: cannot insert NULL into ("APPLSYS"."AD_TIMESTAMPS"."ATTRIBUTE") error (Doc ID 2361013.1) To Bottom In this Document Symptoms Changes Cause Solution References Symptoms While applying the R12.AD.C.Delta.10 Patch 25820806 using the following command, it fails with error: adop phase=apply patches=25820806,26720905 merge=yes hotpatch=yes INSERT INTO fnd_install_processes (worker_id, control_code, status,  context, pdi_product, pdi_username, command, file_product, subdirectory,  filename, phase, install_group_num, arguments,  symbolic_arguments,machine_name) VALUES (1, 'W', 'W', 'UNDEF', 'UNDEF',  'UNDEF', 'UNDEF', 'UNDEF', 'UNDEF', 'UNDEF', 0, 0,  rpad('-',100,'-'),rpad('-',100,'-'),'UNDEF') Connecting to APPS......Connected successfully. AutoPatch error: Error while inserting row in AD_TIMESTAMPS AutoPatch error: ORA-01400: cannot insert NULL into ("APPLSYS"."AD_TIMESTAMPS"."ATTRIBUTE") AutoPatch error: aijhip(): Error calling aijmgrInsertHangingRowInAdTmStmp() AutoPatch error: Failed running aidinv() in adprim() AutoPatch error: Failed running Invoker's Rights maintanance logic Changes  Fresh Installation of 12.2 followed by latest AD/TXK Delta 10 patches Cause Patch 25525148 (Rapid Install consolidated one-off bundle on top of startCD51) was not used while installing the Oracle E-Business Suite Release 12.2 system Solution Test the following in development instance and migrate the solution accordingly: 1. Considering that the hotpatch has failed, there isn't a way to restore and abort cannot be run 2. If a backup prior to AD.C.Delta.10 is available, you may restire (OR) re-do the Fresh 12.2.0 installation and ensure all steps are complete to the point where AD.C.Delta.10 has to be applied. 3. If Patch 25525148 (Rapid Install consolidated one-off bundle on top of startCD51) was not used while installing your Oracle E-Business Suite Release 12.2 system, apply the patches in the following order: Apply Patch 25820806 (R12.AD.C.Delta.10) adop phase=apply patches=25820806 hotpatch=yes Apply Patch 26720905:R12.AD.C adop phase=apply patches=26720905 hotpatch=yes 4. Continue with the upgrade as per "Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)" References NOTE:1907419.1 - ADOP Fails With Error Unable to Find Appltop_id NOTE:1320300.1 - Oracle E-Business Suite Release Notes, Release 12.2 NOTE:1617461.1 - Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 NOTE:2064223.1 - How to Synchronize FND_NODES, ADOP_VALID_NODES, and FND_OAM_CONTEXT_FILES in 12.2 When ADOP Phase=Prepare Fails with Error 'not able to detect any valid application tier nodes in ADOP_VALID_NODES table. ' NOTE:1901242.1 - Script to Diagnose adop and Other AD-TXK Issues in Oracle E-Business Suite Release 12.2 Patch 19045166:R12.AD.C

Posted by: Anil Bandi
Oracle Apps DBA.