Comments on: Unable to get exclusive access to VC repository http://www.vmwarewolf.com/unable-to-get-exclusive-access-to-vc-repository/ Surplus Verbiage from a VMware Employee Tue, 27 Apr 2010 19:20:40 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Geek http://www.vmwarewolf.com/unable-to-get-exclusive-access-to-vc-repository/comment-page-1/#comment-1110 Geek Thu, 15 Apr 2010 07:27:24 +0000 http://www.vmwarewolf.com/unable-to-get-exclusive-access-to-vc-repository/#comment-1110 I think VMware support is awesome. I think VMware support is awesome.

]]> By: Ralph Montgomery http://www.vmwarewolf.com/unable-to-get-exclusive-access-to-vc-repository/comment-page-1/#comment-1094 Ralph Montgomery Fri, 12 Mar 2010 16:19:36 +0000 http://www.vmwarewolf.com/unable-to-get-exclusive-access-to-vc-repository/#comment-1094 We are routinely experiencing this exact error. There are no known connections/user locks on the DB when the DB is engaged to look at the problem. We can easily resolve it by shutting down the DB instance and restarting it - that is the ONLY thing that resolves it. Setup: Oracle 10g Windows 2003 vSphere vCenter Server 4.0 U1 vSphere vCenter Update Manger 4.0 U1 Everything is Virtualized: vCenter Server is virtualized vCenter DB is a separate virtual System on Cent 5.4 Update DB is a separate virtual DB System on Cent 5.4 Research on the Web shows this exact issue has been re-occurring since VC 2.5 as early as Feb 2009, with SQL DB's as well (no one is complaining about Oracle?) We have ran vCenter since the 1.0 days utilizing a PHYSICAL SERVER and PHYSICAL DB SERVER with ORACLE, doing a FRESH install each time we revved up to a newer version so this instance is NOT an upgrade, but a fresh install on a separate system than vCenter itself. We have not ever experienced it prior to this past few weeks. No, I have not yet logged a case with VMware (from what I can find out, logging a case has not ever resolved the issue with any reporting it previously - yes; I WILL LOG ONE anyway!) So, what gives? We are routinely experiencing this exact error. There are no known connections/user locks on the DB when the DB is engaged to look at the problem. We can easily resolve it by shutting down the DB instance and restarting it – that is the ONLY thing that resolves it.

Setup:

Oracle 10g
Windows 2003
vSphere vCenter Server 4.0 U1
vSphere vCenter Update Manger 4.0 U1

Everything is Virtualized:

vCenter Server is virtualized
vCenter DB is a separate virtual System on Cent 5.4
Update DB is a separate virtual DB System on Cent 5.4

Research on the Web shows this exact issue has been re-occurring since VC 2.5 as early as Feb 2009, with SQL DB’s as well (no one is complaining about Oracle?)

We have ran vCenter since the 1.0 days utilizing a PHYSICAL SERVER and PHYSICAL DB SERVER with ORACLE, doing a FRESH install each time we revved up to a newer version so this instance is NOT an upgrade, but a fresh install on a separate system than vCenter itself. We have not ever experienced it prior to this past few weeks.

No, I have not yet logged a case with VMware (from what I can find out, logging a case has not ever resolved the issue with any reporting it previously – yes; I WILL LOG ONE anyway!)

So, what gives?

]]>