After upgrading Oracle SOA Suite 10g (10.1.3.1) to either 10.1.3.4 or 10.1.3.5, you may get the following error upon logging in to the BPEL Console, even though you followed the pre and post-installation instructions to the letter:
No domains accessible to the user logged in.
To over come this issue.
Shutdown Your SOA SErver.
Locate the upgrade script directory from the extracted upgrade software. For example, the 10.1.3.4 patchset for Windows is in filename ias_windows_x86_101340.zip and the example below shows where it might be:
cd c:\soa_upgrade\Disk1\install\soa_schema_upgrade\bpel\scripts
sqlplus orabpel/orabpel @upgrade_10131_101354_oracle.sql
c:\oracle\soa_upgrade\Disk1\install\soa_schema_upgrade\esb\sql\oracle
sqlplus oraesb/oraesb @upgrade_10131_10134_oracle.sql
The things that you need to take care of is that you must run these script for the corresponding user ORABPEL And ORAESB.
It is quite possible that even after using these script you may get the same error.
I have faced this issue while i was upgrading my 10.1.3.1 to 10.1.3.4
i ran the script @upgrade_10131_101354_oracle.sql but still i was getting the similar issue at my end.
I than again ran one more script as ORABPEL user
upgrade_10133_10134_oracle.sql
and it worked for me.
1 comment:
This is a workaround and even I have faced the same issue but we need to identify the correct solution for this problem since we need to run upgrade script from 10.1.3.1 to 10.1.3.4 and not from 10.1.3.3 to 10.1.3.4 , you can check with the product developers and raise a bug as this seems a quite frequent problem when upgrading in windows.
Post a Comment