Shulou(Shulou.com)06/01 Report--

First, background introduction

In the production environment of an enterprise, a Windows2008R2 physical server is used to install vCenter Server 5.5 and Oracle 11g databases, and VC uses a system account to connect to the Oracle database. At the beginning of the installation, there was no clear provision on password compliance, and the system account passwords of the server administrator and Oracle were set at will, and the passwords of these two accounts were required to be rectified in the later stage.

II. Problems and troubleshooting process

After changing the system account password of administrator and oracle, restart the server and find that the vcenter service cannot be started. A prompt appears to start manually.

View the system log to indicate that the second build is not installed or the installation is damaged, event ID1000

Recall that you chose to use the system account to launch vcenter when installing vcenter, and set the password of the system account connected to the oracle database during installation. Open the ODBC data source and test the connection with the changed new password. It is found that the connection can be normal, and it is not the problem with the database. However, it is found that the oracle service can be started normally (the oracle service is also started using the system account during installation), which means that the system starts the service normally after changing the administrator account password.

Use the sqlplus command in the run bar to prompt the system account to be locked when connecting to the database through the system account (the default oracle user will lock the user after 10 failed login attempts), and use it under the CMD interface:

Sqlplus / as sysdba; # login as password-free sysdba user

Alter user system account unlock; # unlock system account

Continue to look for the problem, after a while, when you use the sqlplus command to connect to the database through the system account again, you are prompted that the system account is locked again. It is estimated that the cause of the problem is: after changing the system account through sqlplus, even if the ODBC test connection is normal, VC still uses the old password to connect to oracle through the system account, and does not automatically change the password, so the lock will be triggered again. Check the log and find that the problem lies in the database in the VC C:\ ProgramData\ VMware\ VMwareViryualCenter\ Logs\ vpxd log

Log in and unlock the system account using sysdba again, and change the directory to C:\ ProgramFiles\ VMware\ Infrastructure\ VirtualCenter Server under the command line of the VC server. Execute: vpxd-P directly modify the password of the vCenter connection data; you can also execute: vpxd-p change the password interactively. Then restart the VC service, and the service starts normally.

III. Summary

After the 1.Oracle database modifies the password, the password saved in VC will not be changed synchronously, and the password will also need to be changed in VC (MSSQL has not been tested, not sure if this password also needs to be changed manually)

two。 Changing the administrator account password has no effect on starting the VC service using the oracle database, unlike using MSSQL. The reason why VC cannot start after changing the administrator password is that SQL server cannot start.

You need to reset the new password for the MSSQL service in the background service before the VC service can be started.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.