Skip to main content

[UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on

Error: During adop prepare phase error occurred on validation


Error log:
 cat txkADOPValidations.error
Use of uninitialized value $result in split at /u01/applprod/fs2/EBSapps/appl/au/12.0.0/perl/TXK/ADOPValidationUtils.pm line 1294.
No such file or directory at /u01/applprod/fs2/EBSapps/appl/au/12.0.0/perl/TXK/ADOPValidationUtils.pm line 230.


Solution:

SQL> 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';
SQL > no rows selected ( here not showing context_file)



To fix this issue test the following 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.


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=/u01/applprod/fs1/inst/apps/ETEST_etestapp/appl/admin/ETEST_etestapp.xml \
logfile=/tmp/patchctxupload.log





log shows:

[applprod@etestapp applprod]$ cat /tmp/patchctxupload.log
---------------------------------------------------------------
                   ADX Database Utility
---------------------------------------------------------------
getConnectionUsingAppsJDBCConnector() -->
    APPS_JDBC_URL='jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=epc-db-88888)(PORT=1526)))(CONNECT_DATA=(SERVICE_NAME=ETEST)))'
    Trying to connect using APPS_JDBC_URL
    Connection obtained.
-------------------ADX Database Utility Finished---------------

---------------------------------------------------------------
                   ADX Database Utility
---------------------------------------------------------------
getConnectionUsingAppsJDBCConnector() -->
    APPS_JDBC_URL='jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=epc-db-88888)(PORT=1526)))(CONNECT_DATA=(SERVICE_NAME=ETEST)))'
    Trying to connect using APPS_JDBC_URL
    Connection obtained.
-------------------ADX Database Utility Finished---------------

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



SQL> 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';
PATH
--------------------------------------------------------------------------------
/u01/applprod/fs1/inst/apps/ETEST_etestapp/appl/admin/ETEST_etestapp.xml


5. Re check issue by running adop phase.
adop prepare completed successfully after this  fixing.



Comments

Post a Comment

Popular posts from this blog

19c ORACLE HOME Cloning -Linux/Solaris

  Cloning an Oracle home involves creating a copy of the Oracle home and then configuring it for a new environment. If you are performing multiple Oracle Database installations, then you may want to use cloning to create each Oracle home, because copying files from an existing Oracle Database installation takes less time than creating a new version of them. This method is also useful if the Oracle home that you are cloning has had patches applied to it. When you clone the Oracle home, the new Oracle home has the patch updates which is already applied on oracle home. Steps to clone an Oracle home step 1 : Stop Services Stop all processes related to the Oracle home. Step 2 : Create a ZIP or TAR file with the Oracle home (/u01/app/oracle/product/19.0.0/dbhome_1)    Use ROOT user for ZIP and UNZIP  # zip -r dbhome_1.zip /u01/app/oracle/product/19.0.0/dbhome_1 TAR option: # tar -cvf dbhome_1.tar /u01/app/oracle/product/19.0.0/dbhome_1 Step 3: s cp zip/tar to target s...
Post a Comment
Read more

EBS Standby Role Tranistion using standby database and standby application Tier

 Role Transitions A database can operate in either a primary or standby role - these roles are mutually exclusive. Oracle Data Guard enables you to change these roles dynamically by issuing SQL commands, and supports the following transitions: Switchover Allows the primary database to switch roles with one of its standby databases. There is no data loss during a switchover. After a switchover, each database continues to participate in the Oracle Data Guard configuration with its new role. Failover Changes a standby database to the primary role in response to a primary database failure. The following role transitions are discussed: 6.1 Performing a Switchover 6.2 Performing a Failover 6.3 Performing a Switchback to the Primary Following A Switchover/Failover Each of these three transitions requires some application configuration to be performed. Most of the application configuration step...
1 comment
Read more

adgrants issue with 19c PDB database

 adgrant - system.fnd_oracle_userid ORA-06550: line 1094, column 17 SP2-0625: Error printing variable "result_set" adgrants issue with 19c PDB database  Connect to a multitenant 19c database and follow below steps to resolve ORA error 1- source the cdb env file  2-set the  ORACLE_PDB_SID=<PDB_NAME>   3- connect as  sqlplus / as sysdba 4- go to location of adgrant and execute cd /u01/app/oracle/product/19.0.0/dbhome_1/appsutil/sql    SQL>  @adgrants.sql APPS Note: ignore warnings during adgrant session a d.plsql.ad_zd_sys.GIVE_PRIVILEGE 
Post a Comment
Read more