Re: Unable to start srvctl on RAC Nodes
- From: Ashwin <ashdbablog@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 6 Nov 2008 12:22:48 -0800
I found out one more thing which might be the issue
when i set SRVM_TRACE=TRUE
i see the DB compatible version 10.2.0.0
but in my spfile and controlfile the version is 10.2.0.4
Can this be a problem?
I was thinking that since i've upgraded my CRS and ASM to 10.2.0.4 this
should not be a problem ideally or maybe I am wrong.
I tried to reset the compatibility to 10.2.0.0 and start the database but it
wouldnt come up
Regards,
Ashwin
On Thu, Nov 6, 2008 at 11:37 AM, Ashwin <ashdbablog@xxxxxxxxx> wrote:
> Hi,
>
> I performed the following steps: -
>
> Installed 10.2.0.1 CRS, ASM and DB (all three are in seperate homes)
> - Verified that CRS and ASM are up and running on both nodes
> - Upgraded to 10.2.0.4 on all homes
> - Verified that CRS and ASM are up and running on both nodes
> - Made the 10g DB home non-rac on node 1
> - Upgraded the 9i database (9.2.0.6) to 10.2.0.4 using Note: 316889.1
> - Converted the upgraded database to ASM using RMAN
> - Made the 10g DB home rac enabled on node 1
> - Followed section 3.8 in ML Note: 361235.1
> - NETCA failed so deleted the listeners running out of ASM home
> - Recreated listeners both local and remote
> - Ran rconfig in verify only mode (it succeeded)
> - Ran rconfig and it failed on listener execution
> Both the rac instances are up and running but not registered with CRS.
>
> [orasup@ustorldbs01 ~]$ srvctl config
> SID
> [orasup@ustorldbs01 ~]$ srvctl config database -d SID
> PRKR-1001 : cluster database SID does not exist
> PRKO-2005 : Application error: Failure in getting Cluster Database
> Configuration for SID
>
> when i set SRVM_TRACE=TRUE
>
> i get the following error: -
>
> [main] [10:47:1:470] [RawDeviceConfig.getConfiguration:203] throwing
> rawdeviceexception: PRKR-1078 : Database SID cannot be administered using
> current version of srvctl
> O/S is RHEL 5.1 64-bit
>
> I deregistered the service from CRS for both the instances and can
> re-register the instances but not the database
> Right now i have logged an SR.
>
> Any suggestions please?
>
> Regards,
> Ashwin
>
Other related posts:
