[applmgr@xxxtest]$ sqlplus apps/xxxx
SQL*Plus: Release 10.1.0.5.0 - Production on Mon Dec 28 14:49:49 2020
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-20099: E-Business Suite Patch Edition does not exist.
ORA-06512: at line 29
The database patch edition was not active, where when attempting to connect to the database from the application-tier patch edition environment, it failed.
Due to a failed DB connection, it was unable to read Topology model for correct TNS config, so created tnsnames.ora from template "tnsnames_80.ora"
instead. As this "tnsnames_80.ora" template does not contain "_patch" alias entry you now have "ORA-12154: TNS:could not resolve the connect identifier specified" on the patch f/s.
For making autoconfig successful EBS_LOGON_TRIGGER needs to be disabled.
As seen from the provided inputs, autoconfig has failed in patch fllesystem with below error:
ORA-00604: error occurred at recursive SQL level 1
ORA-20099: E-Business Suite Patch Edition does not exist.
ORA-06512: at line 29
1.Source RUN File system environment.
. EBSapps.env Run
2. - As apps user disable logon trigger
exec ad_zd.ALTER_LOGON_TRIGGER('DISABLE');
commit;
or
3. - Source PATCH file system env
4. Run AutoConfig
5. Connect to run filesystem by sourcing run fs environment
6. . As apps user enable logon trigger
exec ad_zd.ALTER_LOGON_TRIGGER('ENABLE');
commit;
SQL> alter trigger ebs_logon enable;
7. Re-run AutoConfig in run fs once again.
For any failures kindly get back to us with the autoconfig logs for review.
No comments:
Post a Comment
Thanks for reading till end. I hope this will help you more to improve your knowledge.
Now it's your turn!
What do you think? Share your experience in the comments box and subscribe for more interesting post.