This content has been marked as final. Show 4 replies
More info. So I thought maybe I entered some setup data wrong. Where could PTCH1 be specified in my configuration and maybe it needs to be changed to PTCH for the adpatch defaultsfile issue to be fixed.
On the database node attributes screen, I found that I had database sid/service_name was set to PTCH1. Since I have RAC, maybe that should be PTCH (the service name). However, I tested changing this value to PTCH and then a configuration step that creates a a remote database link doesn't work.
Test of the REMOTE alias was successful.
Dropping old database link named REMOTE_1703
Creating new database link named REMOTE_1703
Successfully created a database link named REMOTE_1703
Testing it now...
ERROR: Link exists, but connection failed!
Querying the lnik definition shows why it fails, because the SID value is wrong and probably should be SERVICE_NAME= instead.
SQL> select * from dba_db_links;
So in RAC a environment, what should the MW database node screen attribute value for data sid/service_name be? the service name or the rac instance name?
Can I recreate the link myself to say SERVICE_NAME=PTCH, test the link manually and then say this step has succeeded (so I can move forward)?
Will the adpatch defaults file issue be resolved then?
Thanks for the link. I'm past the adpatch defaults file not working issue.
But what about RAC is not supported in MW?
How will I know what steps I manually need to run on the other DB nodes?
Oracle recommends disabling RAC for your upgrade. When you re-enable RAC and synchronize the nodes, you should be fine.