A NARESH NADHAN'S BLOG
Friday, November 26, 2021
Thursday, November 25, 2021
RC-50004: Fatal: Error occurred in ApplyAppsTechStack:Cannot proceed with ApplyAppsTechStack - the paths/ports in the context file are not valid.,RC-20403: The following port numbers are busy - please make sure the ports are available and try again.
ERROR INFO:
Log file located at
/Mount/oracle/nadhans/inst/apps/nadhans.com/admin/log/ApplyAppsTier_11252253.log
RC-50004: Fatal: Error occurred in ApplyAppsTechStack:
Cannot proceed with ApplyAppsTechStack - the paths/ports in the
context file are not valid.
ERROR while running Apply...
Thu Nov 25 22:53:33 2021
ERROR: Failed to execute
/Mount/oracle/nadhans/inst/apps/nadhans.com/apps/apps_st/comn/clone/bin/adclone.pl
Please check logfile.
Cannot proceed with ApplyApplTop - the paths/ports in the context
file are not valid.
RC-20403: The following port numbers are busy - please make sure
the ports are available and try again.
Raised by oracle.apps.ad.clone.ApplyAppsTechStack
s_metdataport : 9100
--------------------------------------
FIX:
Check and kill if any process are running with port 9100
Later change it to original value and run autoconfig or else you can run adcfgclone again.
Saturday, November 20, 2021
adop fails with "invalid username/password; logon denied" for custom schema
adop fails with "invalid username/password; logon denied" for custom schema XX*
Below error encountered in the txk delta level 10 patching . Please go through this post to fix this issue.
Error:
===========================================================
Done running adaaddlb.pls for YMS
sqlplus -s XXCUST/***** @/ut9001/nadhans/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/ut900/nadhans/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaddls.pls ***** XXCUST *****'
ERROR:
ORA-01017: invalid username/password; logon denied
An error occurred while running a SQL*Plus script.
***
Continue as if it were successful :
***
AutoPatch could not find a response to the above prompt
in the defaults file.
The patch has FAILED,
Please check the adpatch logs for more details.
Solution:
1. Validate and change the XXCUST password by using FNDCPASS.
FNDCPASS apps/apps 0 Y system/manager ORACLE XXCUST XXCUSTT
Above Solution will fix the issue .
If still its failing you can perform the below.
2. Validate and Correct the password in xxdprod.tx. (cd $APPL_TOP/admin).
Script location : $AD_TOP/patch/115/sql
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @adaddls.pls
Enter value for 1: *********** (System Password)
Connected.
Enter value for 2: XXCUST (Custom username)
old 1: grant create procedure to &&2
new 1: grant create procedure to XXCUST
Grant succeeded.
old 1: ALTER SESSION SET CURRENT_SCHEMA = &2
new 1: ALTER SESSION SET CURRENT_SCHEMA = XXCUST
Session altered.
old 2: execute immediate 'drop synonym &2..APPS_DDL';
new 2: execute immediate 'drop synonym XXAHQ.APPS_DDL';
PL/SQL procedure successfully completed.
Package created.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
bash-3.2$ sqlplus system
SQL*Plus: Release 10.1.0.5.0 - Production on Wed Sep 26 15:32:07 2018
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @adaddlb.pls
Enter value for 1: ********* (System password)
Connected.
Enter value for 2: XXCUST
old 8: where grantee='&2'
new 8: where grantee='XXCUST'
Enter value for 2: XXCUST
old 14: execute immediate 'grant execute on sys.dbms_sql to &&2';
new 14: execute immediate 'grant execute on sys.dbms_sql to XXCUST';
PL/SQL procedure successfully completed.
old 1: ALTER SESSION SET CURRENT_SCHEMA = &2
new 1: ALTER SESSION SET CURRENT_SCHEMA = XXCUST
Session altered.
Package body created.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Manually connect to the schema and confirm whether its working.
Retry the adop once again. you can use the below :
adop phase=apply patches=patch_number abandon=no restart=yes
If its failing you can perform the below.
As you can see the error above it was failing at the step below. So i ran the step below manually.
sqlplus -s XXCUST/XXCUST @/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaddls.pls opensys_33 XXCUST XXCUST'
I was able to run adop without any issue with autoskip flag option.
adop phase=apply patches=25828573 abandon=no restart=yes flags=autoskip
we can use the below to skip the failed adop session or if you manually performed the failed step.
abandon=no restart=yes flags=autoskip
This command will restart the patch once again from starting onwards and will skip all the failures if any comes. But make sure to review the log file at the end of the patch application that you have skipped the failures that you want to.
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @adaddls.pls
Enter value for 1: *********** (System Password)
Connected.
Enter value for 2: XXCUST (Custom username)
old 1: grant create procedure to &&2
new 1: grant create procedure to XXCUST
Grant succeeded.
old 1: ALTER SESSION SET CURRENT_SCHEMA = &2
new 1: ALTER SESSION SET CURRENT_SCHEMA = XXCUST
Session altered.
old 2: execute immediate 'drop synonym &2..APPS_DDL';
new 2: execute immediate 'drop synonym XXAHQ.APPS_DDL';
PL/SQL procedure successfully completed.
Package created.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
bash-3.2$ sqlplus system
SQL*Plus: Release 10.1.0.5.0 - Production on Wed Sep 26 15:32:07 2018
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @adaddlb.pls
Enter value for 1: ********* (System password)
Connected.
Enter value for 2: XXCUST
old 8: where grantee='&2'
new 8: where grantee='XXCUST'
Enter value for 2: XXCUST
old 14: execute immediate 'grant execute on sys.dbms_sql to &&2';
new 14: execute immediate 'grant execute on sys.dbms_sql to XXCUST';
PL/SQL procedure successfully completed.
old 1: ALTER SESSION SET CURRENT_SCHEMA = &2
new 1: ALTER SESSION SET CURRENT_SCHEMA = XXCUST
Session altered.
Package body created.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Manually connect to the schema and confirm whether its working.
Retry the adop once again. you can use the below :
adop phase=apply patches=patch_number abandon=no restart=yes
If its failing you can perform the below.
As you can see the error above it was failing at the step below. So i ran the step below manually.
sqlplus -s XXCUST/XXCUST @/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaddls.pls opensys_33 XXCUST XXCUST'
I was able to run adop without any issue with autoskip flag option.
adop phase=apply patches=25828573 abandon=no restart=yes flags=autoskip
we can use the below to skip the failed adop session or if you manually performed the failed step.
abandon=no restart=yes flags=autoskip
This command will restart the patch once again from starting onwards and will skip all the failures if any comes. But make sure to review the log file at the end of the patch application that you have skipped the failures that you want to.
Thursday, November 4, 2021
OPSS: PKI-02002: Unable to open the wallet. Check password. Caused By: java.io.IOException
ERROR INFO:
When attempting to start ADMIN server the following error occurs.
.Default (self-tuning)'> <<WLS Kernel>> <> <> <1635571086361> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password. >
####<Oct 30, 2021 12:18:06 AM CDT> <Critical> <WebLogicServer> <nadhans.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1635571086362> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:888)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
60,1-8 12%
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:888)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:189)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:378)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:193)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:177)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.lang.SecurityException: The jurisdiction policy files are not signed by the expected signer! (Policy files are specific per major JDK release.Ensure the correct version is installed.)
at javax.crypto.JarVerifier.verifyPolicySigned(JarVerifier.java:336)
at javax.crypto.JceSecurity.loadPolicies(JceSecurity.java:378)
at javax.crypto.JceSecurity.setupJurisdictionPolicies(JceSecurity.java:323)
at javax.crypto.JceSecurity.access$000(JceSecurity.java:50)
at javax.crypto.JceSecurity$1.run(JceSecurity.java:82)
Solution:
Issue with the JDK.
JDK in $FMW_HOME/webtier and $ORACLE_HOME locations should be compatible
with the JDK exists in $COMMON_TOP/util/.
Verify and copy JDK directory from $COMMON_TOP/util/ to $FMW_HOME/webtier and $ORACLE_HOME locations.
If JDK is compatible in all the locations .
Then
1.Removed the cwallet.sso in the /<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/config/fmwconfig/ directory.
2.left the one in /<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/config/fmwconfig/bootstrap and then the server started
Once server started copy the same files to the other host Where managed servers are running and start the Managedserver on other hosts.
Now start Admin server .
Subscribe to:
Posts (Atom)
ORACLE DATABASE CONTENT
ORACLE DATABASE 11gR2 & 12C CONTENT Pre-Requisite: UNIX, SQL Basics Introduction to Oracle Database § Introduction of Database ...
-
Script to check user availability: set lines 132 col USER_NAME format a50 select USER_ID,USER_NAME,START_DATE,END_DATE from FND_USER WHERE...
-
ERROR: Solution : 1. Telnet to the Application tier server from the Application tier operating system user. 2. Source application t...
-
Perform the following steps to set the target UTL_FILE_DIR values in the database. 1.Source the environment file $ source &l...
