This document describes the troubleshooting steps when Informix on CVP reporting server does not start because CVP reporting server is renamed.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and hardware versions:
CVP Reporting server version 11
CVP OAMP server version 11
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
The Informix IDS -cvp process in the reporting server is showing as down.
One of the symptoms related to this problem, if Courtesy Callback is implemented, is that you do not get a Courtesy callback offer when you place a call. In the Courtesy Callback scenario, when you place the call, you hear the message your courtesy callback is being cancelled, without giving the option to accept a courtesy Callback.
Another symptom is that reporting server shows in partial status and no information is stored in the reporting server.
When you look at the reporting server services via Windows services, Informix IDS – cvp is down:
Step 1. Attemp to start the Informix IDs - cvp process.
Step 2. Access the database using dbaccess from a command prompt. This error is reported:
Step 3. Collect CVP Callserver logs from the reporting server, after attempting to start the Infomix process.
Call server form the Reporting server does not show any information relevant to starting the Informix process.
Step 4. Collect all Informix logs from the reporting server, informix directory after attempting to start the infomix process.
In a good scenario, the cvp.log file is updated. However, no log file is updated this time, since the process did not start.
The next step is to check the way informix database was installed, by reviewing the IBM_Informix_Software_Bundle_Install.
This is what you can see in the install log file:
The install log file shows that the name of the reporting server is WIN-M6ILKLO8QR9 and that the username who installed the reporting server is the Administrator.
You can confirm this information by looking at the Reporting server installation logs:
Step 5. Identify the current name of the reporting Server, by opening Control Panel > System and Security > System.
The change of the reporting server name after the reporting server is installed is not supported. However, a recommendation is provided next which can be tested in a lab encvironment.
Since, the Informix database is linked to the previous hostname, the database hostname, the registry keys and the system variables need to be changed to the new hostname. The recommendation is to reinstall the Reporting server. However, if it is required to keep the current installation, here is the procedure to recover the system:
Step 1. Back up your configuration files (ONCONFIG file, sqlhosts file) under C:\db\Informix\etc directory.
The ONCONFIG configuration file and sqlhosts file that you must back up have these lines:
In this lab scenario, replace the following from the sqlhost:
cvp olsoctcp WIN-M6ILKLO8QR9 cvp
dr_cvp drsoctcp WIN-M6ILKLO8QR9 dr_cvp
cvp olsoctcp cvp cvp
dr_cvp drsoctcp cvp dr_cvp
Step 4. Change the REGMACHINE entry from C:\db\Informix\cvp.cmd to the new server name. In this scenario, cvp.
Step 5. Change the environment or user profile that had set the INFORMIXSERVER to the old instance name/alias, to export INFORMIXSERVER environment variable to the new instance name or alias.
In this scenario:
Step 6. Open Regedit, and replace all registry keys that has the old hostname with the new hostname.
Step 7. Start now the InformixIDS – CVP service.
Step 8. Restart the Cisco CVP CallServer process on the Reporting Server:
Step 9. With the service online, test the access and connection to the database.
From a command prompt, use dbaccess command, then Connection > Connect, next select the new Informix server name or alias, and enter user name and password (cvp_dbadmin or cvp_dbuser and the password).