8-13
User Guide for CiscoWorks Common Services
78-16571-01
Chapter 8 Diagnosing Problems With CiscoWorks Server
Frequently Asked Questions
Q.
What if the database is inaccessible?
A.
If the server is not able to connect to the database, the database might be
corrupt or inaccessible. This can occur if processes are not running. Try the
following:
Step 1
Log in to CiscoWorks as admin.
Step 2
Select Server > Admin > Process to get a list of CiscoWorks back-end processes
that have failed.
Step 3
Select Server > Admin > Self Test.
•
Click Create to create a report.
•
Click Display to display the report.
Step 4
Select Server > Admin > Collect Server Information.
Step 5
Click the Product Database Status link to get detailed database status.
Step 6
Contact the Cisco TAC or your customer support to get the information you need
to access the database and find out details about the problem. After you have the
required information, perform the following tasks for detecting and fixing
database errors.
Depending upon the degree of corruption, the database engine may or may not
start. For certain corruptions, such as bad indexes, the database can function
normally until the corrupt index is accessed.
Database corruptions, such as index corruptions, can be detected by the dbvalid
utility, which requires the database engine to be running.
To detect database corruption:
Step 1
Log on as root (UNIX) or with administrator privileges (Windows).
Step 2
Stop the Daemon manager if it is already running:
•
UNIX—
/etc/init.d/dmgtd stop
•
Windows—
net stop crmdmgtd
(enter this command in an MS-DOS window)
