Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Unable to get an exclusive access to the vCenter Server repository (1006369)

Last Updated: 9/18/2019Categories: TroubleshootingTotal Views: 51164Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You are unable to start the VMware VirtualCenter Server service.

The VMware VirtualCenter Server service fails to start.

vSphere Client locks up after loading.

You cannot get exclusive access to the vCenter Server repository.

vCenter Server shuts down.

This error appears in the vpxd logs on the vCenter Server:

Unable to get exclusive access to VC repository. Please check if another VirtualCenter instance is running against the same database schema

This issue can occur when vCenter Server is backed by a Microsoft SQL or Oracle database

The vpxd.log file contains entries similar to:

[08:29:33.211 01760 error 'App'] [Vdb::LockRepositoryHelper] SQLExecDirect failed: HY000:6550:ODBC error: (HY000) - [Oracle][ODBC][Ora]ORA-06550: line 1, column 203:
PLS-00201: identifier 'DBMS_LOCK' must be declared
ORA-06550: line 1, column 203:
PL/SQL: Statement ignored
ORA-06550: line 1, column 277:
PLS-00201: identifier 'DBMS_LOCK' must be declared
ORA-06550: line 1, column 260:
PL/SQL: Statement ignored
[08:29:33.227 01760 error 'App'] Unable to get exclusive access to VC repository. Please check if another VirtualCenter instance is running against the same database schema.

If vCenter Server is backed by an Oracle 10g or 11g database:
The vpxd log contains the entry:

SQLExecDirect failed: HYT00:1013:ODBC error: (HYT00) - [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operationORA-06512: at "SYS.DBMS_LOCK", line 209ORA-06512 at "SYS.DBMS_LOCK", line 214ORA-06512

Prior to this issue, database performance slows and the database stops accepting connections. The vpxd log contains entries similar to:

[23:42:49.743 14116 warning 'VpxdMoLock' opID=HB-host-99760@6254 ] ***WARNING*** Lock domain-XXXXX mode EXCLUSIVE held for 21307 ms
[23:42:49.743 14116 warning 'VpxdMoLock' opID=HB-host-99760@6254 ] ***WARNING*** Lock host-XXXXX mode EXCLUSIVEALL held for 21307 ms
[04:01:39.827 04780 error 'App'] [HttpUtil::ExecuteRequest] Error in sending request - No connection could be made because the target machine actively refused it.
[08:00:01.186 20008 warning 'ProxySvc Req05432'] Error reading from client while waiting for header: class Vmacore::SystemException(The specified
network name is no longer available. )

Note: For more information on the location of the vpxd.log file, see Location of vCenter Server log files (1021804)

Resolution

This issue can occur if open connections to the database prevent the exclusive access that vCenter Server requires on the entire database when it starts or fails to start.

To clear open connections to the database:

Verify that only one instance of vCenter Server is trying to access the vCenter Server database. You see this error if vpxd.exe is run from the command line and you try to start the service from services.msc.

Using the vendor's database management tools, check for any connections to the vCenter Server database. If any are found, your DBA can terminate them.

If you do not have a DBA, you can stop and restart database server. This clears any connections.

Warning: Stopping and starting the database server terminates all connections to all databases being hosted on that server. Perform this action with extreme caution.

Note: For information on killing Oracle sessions, see Killing Oracle Sessions.

Note: The preceding link was correct as of September 30, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.

Related Information

Many issues with Oracle database connectivity are resolved in vCenter Server 4.1 Update 1. VMware recommend that Oracle users upgrade the vCenter Server 4.1 Update 1 to ensure compatibility in your environments. You can download the latest release from the VMware Download Center.Location of vCenter Server log files
vCenter Server リポジトリに排他的にアクセスできない
无法独占访问 vCenter Server 存储库

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
对使用 vCenter Converter 时在准备过程中失败的虚拟机进行故障排除 (1006285)

KB
•
Não é possível conectar a um host ESX usando o Secure Shell (SSH) (1003807)

KB
•
Como usar o vSphere Management Assistant (vMA) para coletar logs do ESX e do ESXi (1024122)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant