The patch also changed the apps password Or did some users changed it at database level?
The applsys has the same password.
I can not restart or skip the worker anymore.
I can not login APPS user using our old password and even using default APPS password.
I changed it back at database level as apps/apps
But my adctrl does not accept the password.
Error: The given ORACLE password is not the correct password.
Please re-enter the ORACLE username and password.
Enter the ORACLE username of Application Object Library [APPLSYS] : applsys
Enter the ORACLE password of Application Object Library [APPS] :
AD Controller is verifying your username/password....Unable to connect.
AD Controller error:
The following ORACLE error:
ORA-01017: invalid username/password; logon denied
occurred while executing the SQL statement:
You should check the file
Can I reset the APPS password using below command?
FNDCPASS <logon> 0 Y <SYSTEM username>/<SYSTEM password> SYSTEM APPLSYS <new_password>
Did you upgraded database to 12c?
Check show parameter sec
If case sensitive parameter is TRUE , change to FALSE and try
Yes, it was already upgraded ahead, month ago.
Although case sensitive is TRUE, but I can login to applsys/apps but not in apps/apps.
I checking the issue....brb
And also If EGO product not required , I think you can safely ignore when you do preinstall patches. Check with Oracle also
So I will not include it in preinstall so that I will not encounter errors next time? Or is it safe not to install ALL the add-ons preinstall patches? I just install it on demand after completing the upgrade?
you need to apply all the mandatory preinstall patches as listed .
1. Better check with Oracle
2.check If any invalid objects
3. Any issue was happened When you did database upgrade?
1) If you have not installed EGO product or if you are not using "Advanced Product Catalog" functionality, you can skip the failed job.
- Use the following note in order to check if EGO product is not installed (Status Inactive)
Note 550654.1 "How to Get The Patchset Level of Oracle Applications Products in R12"
- To know if "APC" is installed, you need to get the APC Diagnoctic for R12.1.1
- To skip a failed job, please raise a SR to get the content of the unpublished Note 399645.1 "How To Skip a adworker Job Using adctrl"
2) If you are using this product, Please raise a SR in order to get the detailed procedure to fix the issue listed in bug 8485942
The EGO pre-install patch should not have made the patch merger fail. Can you show the error.
Since you are sure you have not setup the EGO module, you can safely not use the EGO preinstall patch. That is fine.
I renamed apps password to apps at db level, then I was able to skip the EGO worker error, and the patching resume
But still taking very long time when when only 170 jobs to run from almost 60,000 jobs take more than 1 day?
Are you using the same capacity server as your production?
Have you tuned your database to have a larger SGA / PGA for the upgrade?
How many workers are you using - recommended value or did you modify it?
Is your disk on NFS mounted partitions - this is very slow
How much memory and CPU do you have on your Apps server and on your database server?
This is a VMware server, for test upgrade only.
Both apps & db server have 4 CPU
[applmgr@oraapps-2 ~]$ cat /proc/cpuinfo | grep processor | wc -l
Apps Memory = 8Gb
Db Memory= 32Gb
SQL> show parameter sga
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
lock_sga boolean FALSE
pre_page_sga boolean TRUE
sga_max_size big integer 31G
sga_target big integer 30G
unified_audit_sga_queue_size integer 1048576
You are running on the bare minimum memory. so yes your upgrade will run sloooooooooooooooooooooooow
PS: VMware is not a certified virtual product.