v7.0 HP Intelligent Management Center Database Installation

Transcription

1 v7.0 HP Intelligent Management Center Database Installation Frequently Asked Questions Part number: Software version: IMC PLAT 7.0

2 Legal and notice information Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

3 HP IMC Installation FAQ This document contains the most frequently asked questions about HP IMC installation. Q. Why can't the component data in the Oracle database be deleted when I uninstall IMC in distributed mode from the master server? A. This is because the data in the Oracle database is in use. To solve this problem, restart the operating system or the Oracle database after uninstalling IMC. Q. How do I create my database when I deploy IMC components to use SQL Server 2008 R2 Express? A. Modify the security attribute of the IMC data folder after deploying IMC components by following these steps: 1. Right-click the IMC data folder (the default folder is IMCdata). 2. Select Properties on the shortcut menu. 3. On the Properties dialog box that appears, click the Security tab and allow Users to have full control of the folder. 4. Click OK. Q. How do I install the Java running environment on Linux so that I can access IMC properly through Firefox? A. To install the Java running environment, install JDK or JRE and then configure JDK or JRE for Firefox. JDK is taken for example in the following part: 1. Download JDK: Address: Make sure the correct version is downloaded. For example, you must download jdk-6u12-linux-i586-rpm.bin for x86-based Linux. 2. Install JDK: Upload the installation file jdk-6u12-linux-i586-rpm.bin to the server. Suppose the installation file is saved in directory /tmp, execute the following commands: cd /tmp sh jdk-6u12-linux-i586-rpm.bin After executing the commands, press the Space bar to view the copyright information, and then enter yes to finish the JDK installation. JDK is installed in directory /usr/java/jdk1.6.0_12. At the same time, a link /usr/java/default pointing to the directory /usr/java/jdk1.6.0_12 is generated automatically, equivalent to JDK installed in directory /usr/java/default. 3. Configure JDK for Firefox: On the Linux operating system, execute the following commands: cd /var/local/firefox/plugins/ ln -s /usr/java/default/jre/plugin/i386/ns7/libjavaplugin_oji.so After executing the commands, you can run /var/local/firefox/firefox to access IMC. 1

4 Q. In Linux, how do I get the current system time in IMC (such as the login time and operation log record time) to match the time on the server? A. The current time zone setting on the server is different from the setting when IMC was installed. Use the tzselect command to modify the time zone of the server. Q. How do I start the IMC background processes after IMC is installed in the Windows Server bit edition? A. Before installing IMC in Windows Server bit OS, you must install the WindowsServer2003-KB v4-x64.exe patch. Otherwise, part of the IMC processes cannot start after installation and deployment. To solve this problem, stop IMC, install the patch listed above, and then manually execute \deploy\components\server\vcredist.exe in the IMC installation path. Q. How do I resolve the abnormality that occurs during deployment when the IMC database is installed on a remote database server running Windows Server 2008 or Windows Server 2008 R2? A. An abnormality might occur because the user who enabled the SQL Server on the remote database server is not assigned write access to the IMCdata folder in the IMC installation path. To solve the problem, manually change the access right of the IMCdata folder on the remote database server. Q. During the component deployment process, "Deployment is stopped with error. For details, see the log." appears, and "Execute database script error!" is displayed in the system log. How do I resolve the discrepancy that, after checking the log file, only the error information (the object dbo.qv.id already exists) is displayed? A. Log in to the Query Analyzer of SQL Server as the sa user, and then execute the following commands: use model EXEC sp_droptype 'qv_id' Deploy the component again. Q. How do I continue installing IMC on a PC running Windows Server 2008 R2 when the system indicates that the Windows Installer cannot be installed, as shown in the following figure? 2

5 A. On the Windows Installer dialog box, click Browse. On the dialog box for selecting a file, search any folder whose name contains digits and letters abcdef in the root directory, select file vc_red.msi in the folder, and click OK. Then, continue the installation. Q. In Linux, how do I solve the problem that the JavaService is closed when Xwindows is closed? A. Use service IMCdmsd start to start the JavaService. Q. How do I make the report work correctly in Linux when IMC service components are deployed on subordinate servers and the master server uses a remote Oracle database? A. To resolve this issue: 1. Check the configuration files in \common\conf\server-addr.xml of the IMC installation path and the database names of the components on the subordinate servers. Take the following environment for example: The master server is at , and the database server is at Deploy UAM component on server A at and WSM components on server B at address Run the server-addr.xml file to view the following information: <component address= id= IMC-PLAT > <db-config address= dbname= 192_168_0_100 oracle-sid= orcl password= type= Oracle username= IMC_config /> </component>... <component address= id= IMC-UAM > <db-config address= dbname= 192_168_0_2 oracle-sid= orcl password= type= Oracle username= ead /> </component>... <component address= id= IMC-WSM > <db-config address= dbname= 192_168_0_3 oracle-sid= orcl password= type= Oracle username= IMC_wsm /> </component> The configuration information shows that the database names of the components deployed on server A and server B are 192_168_0_2 and 192_168_0_3. 2. Check the $ORACLE_HOME/network/admin/tnsnames.ora file on the master server and the configuration of the databases 192_168_0_2 and 192_168_0_3. 192_168_0_2 = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = 1521)) (CONNECT_DATA = (SERVER = REMOTE) (SERVICE_NAME = orcl) ) ) _168_0_3 = 3

6 (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = orcl) ) ) 3. Use vi to run the $ORACLE_HOME/network/admin/tnsnames.ora file on the database server to check whether the above configuration exists. If not, add the above configuration to the file. Q. How do I start or stop IMC service processes in Windows after IMC has been running for a certain period of time? A. This problem is caused by insufficient virtual memory. Set the virtual memory to the system managed size on the server: 1. Open the Control Panel window and click the System icon. The System Properties dialog box appears. Figure 1 System properties 2. Click the Advanced tab and click Settings in the Performance area. The Performance Options dialog box appears. 4

7 Figure 2 Performance options 3. On the Performance Options dialog box, click the Advanced tab and click Change in the Virtual memory area. The Virtual Memory dialog box appears. Figure 3 Virtual memory 4. Select the System managed size option, click Set, and then click OK. 5

8 Q. How do I update the Deploying or Upgrading state of a component in the Intelligent Deployment Monitoring Agent on the master server after a deployment or upgrade error occurs? A. IMC does not actively refresh the component states when communication between the master and subordinate servers is interrupted. To view the latest state of the component: 1. Stop IMC in the Intelligent Deployment Monitoring Agent and quit the program. 2. Restart the IMC server service on the mater server. In Linux, restart the IMC server service by using the /imcdmsd restart command in the /etc/init.d directory. 3. Start IMC in the Intelligent Deployment Monitoring Agent on the server where the component is to be deployed. Q. How do I handle components deployed on the server when a subordinate server is faulty and cannot be rectified? A. You can undeploy the components from the faulty subordinate server and deploy them to an available subordinate server. To do that: 1. Launch the Intelligent Deployment Monitoring Agent on the master server and click the Deploy tab. 2. Right-click a target component and select Undeploy the Component (Master only) from the shortcut menu. This option appears only when the master server cannot connect to one or more subordinate servers. Repeat this step to undeploy more components. 3. Deploy the components to another subordinate server. The component data is deleted from the subordinate server when you undeploy the components. Make sure the subordinate server has a secure data backup or uses a remote database. Otherwise, the data will be lost. 6

9 MySQL 5.5 (Linux) FAQ This document contains the most frequently asked questions about MySQL 5.5 for IMC on Linux. Q. Why do garbled characters appear in the database table? A. Garbled characters can appear in the database table if the character set is not correctly configured during installation of the MySQL server and client. Q. How do I update database passwords for IMC? A. The usernames and passwords used by the IMC modules are stored in cipher text in file \common\conf\ server-addr.xml in the installation path. You can use the./pwdmgr command to obtain passwords in plain text or update the latest passwords to the file. Typically, a user can use the database management tool to change the database password of a certain IMC module. To ensure communication between IMC and the database, use the./pwdmgr command to update the corresponding password in file server-addr.xml. If IMC is deployed in distributed mode, you must update the password for every IMC server by using the following commands: [root@daemon8829 IMC]# cd deploy/ [root@daemon8829 IMC]#./pwdmgr.sh modify config_db IMC_config dbpasswd Change password successfully In the preceding commands, dbpasswd represents the latest database password of the IMC_config user, config_db represents the database name, and represents the IP address of the database. To obtain the IP address and name of a MySQL database, view the settings of the corresponding user in file $IMCROOT/common/conf/server-addr.xml. 1

10 MySQL 5.5 (Windows) FAQ This document contains the most frequently asked questions about MySQL 5.5 for IMC on Windows. Q. Why do garbled characters appear in the database table? A. Garbled characters appear in the database table when the character set has not been set correctly during installation of the MySQL server. The character set for the English language in MySQL is latin1. Q. How do I update database passwords for IMC? A. The usernames and passwords used by the IMC modules are stored in cipher text in file \common\conf\ server-addr.xml in the installation path. You can use the pwdmgr.bat command to obtain passwords in plain text or update the latest passwords to the file. Typically, a user can use the database management tool to change the database password of a certain IMC module. To ensure communication between IMC and the database, use the pwdmgr.bat command to update the corresponding password in file server-addr.xml. If IMC is deployed in distributed mode, you must update the password for every IMC server. Figure 1 Updating database passwords for IMC In the preceding commands, dbpasswd represents the latest database password of the user, IMC_config; config_db represents the database name; and represents the IP address of the database. To obtain the IP address and name of a MySQL database, view the settings of the corresponding user in file $IMCROOT/common/conf/server-addr.xml. 1

11 Oracle 11g FAQ This document contains the most frequently asked questions about Oracle 11g for IMC. Q. How do I handle the case where the system displays that the space is not enough when I create the database instance? A. Check whether you have correctly configured the configuration file sysctl.conf in the /etc directory. Make sure the kernel parameters have the same or larger values than the following recommended values: kernel.shmall= kernel.shmmax= kernel.shmmni=4096 kernel.sem= fs.file-max=65536 net.ipv4.ip_local_port_range= net.core.rmem_default= net.core.rmem_max= net.core.wmem_default= net.core.wmem_max= Q. How do I handle garbled characters displayed on IMC? A. Garbled characters might be caused by the following reasons: Incorrect character set for the database. Garbled characters might appear if the character set is incompatible with IMC. For example, the English character set has been set for the Chinese IMC system. To solve this problem, reinstall the Oracle database and select the correct character set. Incorrect character set for the clients. Garbled characters might appear when NLS_LANG is not correctly set or modified during IMC operation. To solve this problem, correct the environment variable and restart the server and IMC. Incorrect environment variables for the server and the default installation of the Oracle database. If the Oracle database was installed by using the default mode, the Oracle database is set with the default character set according to the LANG environment variables, which might not have been set correctly. For example, if the default installation, where LANG is C, was used to install a database of Japanese character set, WE8ISO8859P1 is set as the character set, so garbled characters appear. To solve this problem, reinstall the Oracle database. For more information about setting the database and client character sets, see Oracle Database Globalization Support Guide at 1

12 Q. How do I verify that the environment variables have taken effect? A. Execute the command echo $variable name to verify that the home directory, Oracle LIB, and Oracle instance configurations have taken effect. For example: #echo $ORACLE_HOME /u01/app/oracle/product/11.1.0/db_1 #echo $LD_LIBRARY_PATH /u01/app/oracle/product/11.1.0/db_1/lib #echo $ORACLE_SID Orcl 2

13 Oracle 11g R2 FAQ This document contains the most frequently asked questions about Oracle 11g R2 for IMC. Q. How do I handle the case where the system displays that the space is not enough when I create the database instance? A. Check whether the file sysctl.conf in the etc directory is correctly configured. For more information, see Oracle 11g R2 Installation and Configuration Guide. Q. How do I handle garbled characters displayed on IMC? A. Garbled characters might be caused by the following reasons: Incorrect character set for the database. Garbled characters might appear if the character set is incompatible with IMC. For example, the English character set has been set for the Chinese IMC system. To solve this problem, reinstall the Oracle database and select the correct character set. Incorrect character set for the clients. Garbled characters might appear when NLS_LANG is not correctly set or modified during IMC operation. To solve this problem, correct the environment variable and restart the server and IMC. Incorrect environment variables for the server and the default installation of the Oracle database. If the Oracle database was installed by using the default mode, the Oracle database is set with the default character set according to the LANG environment variables, which might not have been set correctly. For example, if the default installation, where LANG is C, was used to install a database of Japanese character set, WE8ISO8859P1 is set as the character set, so garbled characters appear. To solve this problem, reinstall the Oracle database. For more information about setting the database and client character sets, see the Oracle Database Globalization Support Guide at Q. How do I verify that the environment variables have taken effect? A. Execute the command echo $variable name to verify that the home directory, Oracle LIB, and Oracle instance configurations have taken effect. For example: #echo $ORACLE_HOME /u01/app/oracle/product/11.1.0/db_1 #echo $LD_LIBRARY_PATH :/u01/app/oracle/product/11.1.0/db_1/lib #echo $ORACLE_SID orcl 1

14 Q. How do I update database passwords for IMC? A. The usernames and passwords used by the IMC modules are stored in cipher text in file \common\conf\ server-addr.xml in the installation path. You can use the./pwdmgr command to obtain passwords in plain text or update the latest passwords to the file. Typically, a user can use the database management tool to change the database password of a certain IMC module. To ensure communication between IMC and the database, use the./pwdmgr command to update the corresponding password in file server-addr.xml. If IMC is deployed in distributed mode, you must update the password for every IMC server by using the following commands: [root@daemon8829 IMC]# cd deploy/ [root@daemon8829 IMC]#./pwdmgr.sh modify config_db IMC_config dbpasswd Change password successfully In the preceding commands, dbpasswd represents the latest database password of the IMC_config user; config_db represents the database name; and represents the IP address of the database. To obtain the IP address and name of an Oracle database, view the settings of the corresponding user in file $IMCROOT/common/conf/server-addr.xml. Q. What do I do if the database server connection is very slow? A. Use vi to open file resolv.conf in the /etc directory and make sure the DNS configuration is the same as the following: cd /etc vi resolv.conf serch rhel55x64.imc nameserver nameserver

15 SQL Server 2005 FAQ This document contains the most frequently asked questions about SQL Server 2005 for IMC. Q. Will changing the computer name affect the database? A. Changing a computer name might cause some failures to operate the SQL Server database. Q. How do I restore the database if I have changed the computer name? A. Perform the following operations to update the computer name saved in the database: For example, the previous computer name is SERVER_1 and the new computer name is SERVER_2. Open cmd.exe of Windows and execute the following scripts (assuming that the login user name is sa and the password is IMCpass): osql -Usa PIMCpass osql -Usa PIMCpass go The previous computer name SERVER_1 is displayed on the interface. Execute the following commands to modify the computer name saved in the @duplicate_ok= 'duplicate_ok' go exit The commands above delete the previous computer name SERVER_1 and add a new one SERVER_2. After the modification, you must restart the SQL Server service in the Windows Service Manager to restore the database. Q. What do I do if I see the error message "MS SQLServer is not Installed Correctly, MSSQLSERVER Service Does not Exist" during the IMC installation? A. MSSQLSERVER is the default instance name of the Microsoft SQL Server. This error message appears if the default instance you have selected during the IMC installation does not exist in the SQL Server Configuration Manager. Similarly, if you have specified a non-existent instance named ABC during the IMC installation, the error message displays the MSSQL$ABC service does not exist. Q. What do I do if I see the error message "Database Service MSSQLSERVER Is not Configured to Be Started with Local System" during the IMC installation? A. To create database files for IMC, the MSSQLSERVER service must be started with the Local System account. Otherwise, IMC might fail to install because of a disk access denied error. To configure the service to be started with the Local System account: 1. Select Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager. 1

16 Figure 1 Selecting the SQL Server Configuration Manager from the Start menu 2. Right-click SQL Server (MSSQLSERVER) in the SQL Server Configuration Manager window and select Properties. Figure 2 SQL Server Configuration Manager window 3. On the Log On tab, click Built-in account, select Local System from the list, and click OK. 2

17 Figure 3 SQL Server (MSSQLSERVER) Properties window 4. Restart the SQL Server (MSSQLSERVER) service on the SQL Server Configuration Manager window. Q. What do I do if I see the error message "The ADO1.5 Component Is not Found in Current System" during the IMC installation? A. IMC uses ADO 1.5 to connect the database. ADO 1.5 is provided by the operating system. This error indicates that ADO 1.5 is corrupted. To solve the problem, reinstall ADO. Q. What do I do when the error message "Provider Cannot Be Found" is displayed during the IMC installation? A. This error indicates that either MDAC is not installed on the server or your MDAC installation is corrupted. MDAC corruption typically occurs when application programs erroneously attempt to install a partial version of MDAC. To solve the problem, reinstall MDAC. You can download the installation program mdac_typ.exe from Microsoft's website. If MDAC installation fails, use the following method: 1. In Windows Explorer, open the C:\WINDOWS\inf folder. The folder might be hidden. 2. Right-click the mdac.inf file in the folder and select Install. During the installation, multiple files need to be located. You can select each file from Service Pack CD-ROM or from the current operating system: If you want to select files from Service Pack CD-ROM, locate the i386 directory from the CD-ROM drive. For example, if the CD-ROM drive is D:, select the D:\i386 directory. If you want to select files from the current operating system, click Browse to select files and click Retry. 3

18 3. MDAC is installed successfully if no error is displayed after you complete the installation. Files to be located during the installation and their locations are as follows: File name adcjavas.inc adojavas.inc msdadc.dll dao360.dll handler.reg oledbjvs.inc MDACRdMe.htm or MDACReadme.htm Location C:\Program Files\Common Files\System\msadc C:\Program Files\Common Files\System\ado C:\Program Files\Common Files\System\ole db C:\Program Files\Common Files\Microsoft shared\dao C:\Program Files\Common Files\System\msadc C:\Program Files\Common Files\System\ole db C:\Program Files\Common Files\System\ado 4. Reboot the operating system. If the problem is not solved, use the MDAC Component Checker provided by Microsoft to locate MDAC installation problems: 1. Download a free MDAC Component Checker cc_pkg.exe from the Microsoft website, decompress it to the C:\ComponentChecker directory, click the first radio button in the window as shown in Figure 4, and click OK. Figure 4 Component Checker window Information is displayed as shown in Figure 5. Pay attention to the information about MISMATCH under File Details. The MISMATCH information indicates the potential problems of the MDAC installation. 4

19 Figure 5 Information about MISMATCH under File Details 2. Click MISMATCH and view files in the right window. These file versions are different from the MDAC version. The Mismatch Field column displays expected file versions. The File Version column displays actual file versions. 3. If version mismatch cannot be solved through MDAC installation, copy files to the corresponding directories. Locate the mdacxpak.cab file from the depressed path of MDAC_TYPE.exe and use WinZip to decompress the mdacxpak.cab file. The file contains most of the important MDAC files. 4. Copy the depressed files to corresponding paths shown in MISMATCH. 5. Reboot the operating system after the previous operations. If you still cannot solve the problem, HP recommends reinstalling your operating system and database or contacting the technical support department. Q. What do I do if I see the error message "Failed to Run bcp.exe, Database Tools is not Installed or Windows is not Restarted after MS SQL Server is Installed" during the IMC installation? A. When you use a remote database server, IMC and database server are not deployed on the same server. IMC needs to use a tool such as bcp.exe to access the database. You must manually install the Connectivity Components client on the IMC server. For information about the installation procedure, see the Feature Selection dialog box. After installing the Connectivity Components client, restart Windows before using the client program bcp.exe. Otherwise, the client cannot be used. Q. How do I set SQL Server 2005 to automatically start in Windows Server 2008? A. In Windows Server 2008, SQL Server 2005 cannot automatically start if it failed to listen to IPv6 addresses of the NICs. To solve the problem, disable all IPv6 addresses on the IP Addresses tab of the TCP/IP properties. Q. How do I update database passwords for IMC? A. The usernames and passwords used by the IMC modules are stored in cipher text in file \common\conf\ server-addr.xml in the installation path. You can use the pwdmgr.bat command to obtain passwords in plain text or update the latest passwords to the file. Typically, a user can use the database management tool to change the database password of a certain IMC module. To ensure communication between IMC and the database, use the pwdmgr.bat command to update 5

20 the corresponding password in file server-addr.xml. If IMC is deployed in distributed mode, you must update the password for every IMC server. Figure 6 Updating database passwords for IMC In the preceding commands, dbpasswd represents the latest database password of the IMC_config user, config_db represents the database name, and represents the IP address of the database. To obtain the IP address and name of a SQL Server database, view the settings of the corresponding user in file $IMCROOT/common/conf/server-addr.xml. 6

21 SQL Server 2008/2008 R2/2012 FAQ This document contains the most frequently asked questions about SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 for IMC. Q. Will changing the computer name affect the database? A. Changing a computer name might cause some failures to operate the SQL Server database. Q. How do I restore the database if I have changed the computer name? A. Perform the following operations to update the computer name saved in the database: For example, the previous computer name is SERVER_1 and the new computer name is SERVER_2. Open cmd.exe of Windows and execute the following scripts (assuming that the login user name is sa and the password is IMCpass): osql -Usa -PIMCpass go The previous computer name SERVER_1 is displayed on the interface. Execute the following commands to modify the computer name saved in the @duplicate_ok= 'duplicate_ok' go exit The commands above delete the previous computer name SERVER_1 and add a new one SERVER_2. After the modification, you must restart the SQL Server service in the Windows Service Manager to restore the database. Q. What do I do if the error message "MS SQLServer is not Installed Correctly, MSSQLSERVER Service Does not Exist" is displayed during the IMC installation? A. MSSQLSERVER is the default instance name of the Microsoft SQL Server. This error message appears if the default instance you have selected during the IMC installation does not exist in the SQL Server Configuration Manager. Similarly, if you have specified a non-existent instance named ABC during the IMC installation, the error message displays the MSSQL$ABC service does not exist. Q. What do I do if the error message "Database Service MSSQLSERVER Is not Configured to Be Started with Local System" is displayed during the IMC installation? A. To create database files for IMC, the MSSQLSERVER service must be started with the Local System account. Otherwise, IMC might fail to install because of a disk access denied error. To configure the service to be started with the Local System account: 1. Select Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager. 1

22 Figure 1 Selecting the SQL Server Configuration Manager from the Start menu 2. Right-click SQL Server (MSSQLSERVER) in the SQL Server Configuration Manager window and select Properties. Figure 2 SQL Server Configuration Manager window 3. On the Log On tab, click Built-in account, select Local System from the list, and click OK. 2

23 Figure 3 SQL Server (MSSQLSERVER) Properties window 4. Restart the SQL Server (MSSQLSERVER) service on the SQL Server Configuration Manager window. Q. What do I do if the error message "The ADO1.5 Component Is not Found in Current System" is displayed during the IMC installation? A. IMC uses ADO 1.5 to connect the database. ADO 1.5 is provided by the operating system. This error indicates that ADO 1.5 is corrupted. To solve the problem, reinstall ADO. Q. What do I do if the error message "Provider Cannot Be Found" is displayed during the IMC installation? A. This error indicates that either MDAC is not installed on the server or your MDAC installation is corrupted. MDAC corruption typically occurs when application programs erroneously attempt to install a partial version of MDAC. To solve the problem, reinstall MDAC. You can download the installation program mdac_typ.exe from Microsoft's website. If MDAC installation fails, use the following method: 1. In Windows Explorer, open the C:\WINDOWS\inf folder. The folder might be hidden. 2. Right-click the mdac.inf file in the folder and select Install. During the installation, multiple files need to be located. You can select each file from Service Pack CD-ROM or from the current operating system: If you want to select files from Service Pack CD-ROM, locate the i386 directory from the CD-ROM drive. For example, if the CD-ROM drive is D:, select the D:\i386 directory. If you want to select files from the current operating system, click Browse to select files and click Retry. 3

24 3. MDAC is installed successfully if no error is displayed after you complete the installation. Files to be located during the installation and their locations are as follows: File name adcjavas.inc adojavas.inc msdadc.dll dao360.dll handler.reg oledbjvs.inc MDACRdMe.htm or MDACReadme.htm Location C:\Program Files\Common Files\System\msadc C:\Program Files\Common Files\System\ado C:\Program Files\Common Files\System\ole db C:\Program Files\Common Files\Microsoft shared\dao C:\Program Files\Common Files\System\msadc C:\Program Files\Common Files\System\ole db C:\Program Files\Common Files\System\ado 4. After the installation, reboot the operating system. If the problem is not solved, use the MDAC Component Checker provided by Microsoft to locate MDAC installation problems: 1. Download a free MDAC Component Checker cc_pkg.exe from the Microsoft website, decompress it to the C:\ComponentChecker directory, click the first radio button in the window as shown in Figure 4, and click OK. Figure 4 Component Checker window Information is displayed as shown in Figure 5. Pay attention to the information about MISMATCH under File Details. The MISMATCH information indicates the potential problems of the MDAC installation. 4

25 Figure 5 Information about MISMATCH under File Details 2. Click MISMATCH and view files in the right window. These file versions are different from the MDAC version. The Mismatch Field column displays expected file versions. The File Version column displays actual file versions. 3. If version mismatch cannot be solved through MDAC installation, copy files to the corresponding directories. Locate the mdacxpak.cab file from the depressed path of MDAC_TYPE.exe and use WinZip to decompress the mdacxpak.cab file. The file contains most of the important MDAC files. 4. Copy the depressed files to corresponding paths shown in MISMATCH. 5. Reboot the operating system. If you still cannot solve the problem, HP recommends reinstalling your operating system and database or contacting the technical support department. Q. What do I do if the error message "Failed to Run bcp.exe, Database Tools is not Installed or Windows is not Restarted after MS SQL Server is Installed" is displayed during the IMC installation? A. When you use a remote database server, IMC and database server are not deployed on the same server. IMC needs to use a tool such as bcp.exe to access the database. You must manually install the Connectivity Components client on the IMC server. For information about the installation procedure, see the Feature Selection dialog box. After installing the Connectivity Components client, restart Windows before using the client program bcp.exe. Otherwise, the client cannot be used. Q. How do I update database passwords for IMC? A. The usernames and passwords used by the IMC modules are stored in cipher text in file \common\conf\ server-addr.xml in the installation path. You can use the pwdmgr.bat command to obtain passwords in plain text or update the latest passwords to the file. Typically, a user can use the database management tool to change the database password of a certain IMC module. To ensure communication between IMC and the database, use the pwdmgr.bat command to update the corresponding password in file server-addr.xml. If IMC is deployed in distributed mode, you must update the password for every IMC server. 5

26 Figure 6 Updating database passwords for IMC In the preceding commands, dbpasswd represents the latest database password of the IMC_config user, config_db represents the database name, and represents the IP address of the database. To obtain the IP address and name of a SQL Server database, view the settings of the corresponding user in file $IMCROOT/common/conf/server-addr.xml. Q. Why can't I install the SQL server on a Microsoft Gold Standard server? A. To install the SQL server on a Microsoft Gold Standard server, make sure you are a system user with the rights to install the SQL server. Table 1 User right list Local policy object display name Backup files and directories Debug Programs Manage auditing and security log User right SeBackupPrivilege SeDebugPrivilege SeSecurityPrivilege 6