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

My Subscriptions

Loading

Knowledge Base

vCenter Server does not start when connecting to an Oracle database with the vpxd.log error: Unable to get exclusive access to VC repository (1021194)

Last Updated: 10/12/2015Categories: TroubleshootingTotal Views: 22338Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

When connecting to an Oracle database, vCenter Server fails to start.

The C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file contains error messages similar to:

[00336 error 'App'] [Vdb::LockRepositoryHelper] SQLExecDirect failed: HY000:6510:ODBC error: (HY000) - [Oracle][ODBC][Ora]ORA-06510: PL/SQL: unhandled user-defined exception ORA-06512: at line 10
[00336 error 'App'] Unable to get exclusive access to VC repository. Please check if another VirtualCenter instance is running against the same database schema.

In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file on vCenter Server 5.0, you see entries similar to:

2012-01-15T12:16:15.989+03:00 [04044 info 'Default'] [Vpxd::ServerApp::Init:841] Calling: VpxdCharacterizeThreadpool(ltud)
2012-01-15T12:16:15.989+03:00 [04044 info 'Default'] [Vpxd::ServerApp::Init:842] Calling: VpxdCertificate_Load(gDB, CERTIFICATE_VMDBPATH )
2012-01-15T12:16:15.989+03:00 [04044 info 'Default'] [Vpxd::ServerApp::Init:843] Calling: VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)
2012-01-15T12:16:15.989+03:00 [04044 info 'Default'] Registry Item DB 5 value is '50'
2012-01-15T12:16:20.145+03:00 [04044 error 'Default'] [Vdb::LockRepositoryHelper] SQLExecDirect failed: HY000:20001:ODBC error: (HY000) - [Oracle][ODBC][Ora]ORA-20001: Failed to Lock vCenter Repository!!
--> ORA-06512: at line 1
-->
2012-01-15T12:16:20.145+03:00 [04044 error 'Default'] Unable to get exclusive access to vCenter repository. Please check if another vCenter instance is running against the same database schema.
2012-01-15T12:16:20.177+03:00 [04044 error 'Default'] [Vpxd::ServerApp::Init] Init failed: VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)
2012-01-15T12:16:20.177+03:00 [04044 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 4188 ms
2012-01-15T12:16:20.177+03:00 [04044 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...
2012-01-15T12:16:20.192+03:00 [04044 info 'Default'] Wrote uptime information
2012-01-15T12:16:20.208+03:00 [04044 error 'Default'] Alert:false@ d:/build/ob/bora-455964/bora/vpx/vpxd/util/vpxdVdb.cpp:408
--> Backtrace:
--> backtrace[00] rip 000000018013d40a (no symbol)
--> backtrace[01] rip 00000001800ffa38 (no symbol)
--> backtrace[02] rip 00000001800fffee (no symbol)
--> backtrace[03] rip 0000000180094b8a (no symbol)
--> backtrace[04] rip 000000013f5b8763 (no symbol)
--> backtrace[05] rip 000000013feff5ce (no symbol)
--> backtrace[06] rip 000000013feff7b3 (no symbol)
--> backtrace[07] rip 000000014011dea7 (no symbol)
--> backtrace[08] rip 000007feff34a82d (no symbol)
--> backtrace[09] rip 000000007731652d (no symbol)
--> backtrace[10] rip 000000007744c521 (no symbol)
-->

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Solution

This issue can occur when VirtualCenter Server service has not exited gracefully when the operating system shuts down, or when other system events cause the VirtualCenter Server service to stop abruptly. Because of this, the Oracle network is not able to detect termination of a previous connection between the vCenter Server and the Oracle server. It then seems as though the previous session is still running, and the lock from the previous session is not released.

This issue is resolved in vCenter Server 5.5. You can download the latest vCenter Server release, available at VMware Downloads.

To avoid this problem, enable KeepAlive parameters on the Oracle server and on the vCenter Server machine.

Note: These parameters can also be used on a SQL server, to resolve locks with the database.

To enable the parameters on the Oracle server:

Configure TCP/IP KeepAlive parameters on the Oracle database.

On Windows, set these DWORD parameters in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters:

KeepAliveTime = 60000 (where the value is in milliseconds, so it is equal to 60 seconds or one minute)

KeepAliveInterval = 1000 (where the value is in milliseconds, so it is equal to 1 second)

TcpMaxDataRetransmissions = 5

On Linux, add these entries in the /etc/sysctl.conf file:

net.ipv4.tcp_keepalive_time=3000 (where the value is in seconds, so it is equal to 50 minutes)

net.ipv4.tcp_retries2=5

net.ipv4.tcp_syn_retries=1

To apply the new TCP/IP parameters, perform one of these options:

Reboot Windows.

On Linux, run sysctl -p.

Configure Dead Connection Detection (DCD) by adding this entry in the $ORACLE_HOME/network/admin/sqlnet.ora file:

SQLNET.EXPIRE_TIME = 1

To enable the parameters on the vCenter Server machine:

Configure TCP/IP KeepAlive parameters by adding these DWORD keys in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters:

KeepAliveTime = 60000 (where the value is in milliseconds, so it is equal to 60 seconds or one minute)

KeepAliveInterval = 1000 (where the value is in milliseconds, so it is equal to 1 second)

Shut down vCenter Server to close existing Oracle connections.

Restart the server to apply the new TCP/IP parameters.

As an alternative workaround, create a shutdown script that stops the vCenter Server service when Windows shuts down. This automatically releases the database connection.

Create a Windows command file (a text file ending in .cmd).

Open the file for editing, and add this command:

net stop /y vpxd
ping -n 61 127.0.0.1 > null

Save the changes and exit from the batch file.

Open the Windows Group Policy Editor, gpedit.msc.

Go to Computer Configuration > Windows Settings > Scripts (Startup/Shutdown).

Right-click Shutdown and click Properties.

Click Add.

Enter the name of the command file that you created in step 1.

Click OK twice to save the changes.

Exit the Windows Group Policy Editor.

Additional Information:

For translated versions of this article, see:

日本語: オラクルデータベース接続時に vCenter サーバーが起動しない (2032717)

简体中文: 连接到 Oracle 数据库时，vCenter Server 无法启动 (2091604)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server Appliance 5.0.x/5.1 から 5.5 へのアップグレード (2058441)

KB
•
Google Chrome 45 或更高版本中的 vSphere Web Client 集成插件失败 (2130672)

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 vCenter Server

Related Versions:

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant