Verifying a database
With regular maintenance and proper database handling, Metrics Management database problems are uncommon. Nonetheless, database structures can become corrupted. If a problem or unusual behavior occurs with a database, perform a database verification. A database verification searches for logical errors in Metrics Management database tables. Completion of a database verification does not indicate whether or not the database is in a healthy state. Review the database verification reports to determine the health of the database. The verification process generates the following reports:
*Verification overview. Contains database statistics such as the number of measures and locations, and data points in the database, and provides an overview of orphaned objects and duplicated initiatives.
*Orphaned objects references. Contains information about orphaned objects. An orphaned object is a Metrics Management object that is no longer referenced by any other object.
*Duplicated initiative sequences. Contains information about duplicated initiative sequences. A duplicated initiative sequence is a sequence number which is incorrectly applied to more than one initiative at one level of an initiative hierarchy.
Table 10‑2 lists the report file name syntax for each verification report type.
Table 10‑2 Database verification report syntax
Report type
Report syntax
Verification overview
DbVerification.MachineName.DatabaseName.txt
Orphaned objects reference
DbVerification.MachineName.DatabaseName.Orphaned object references.txt
Duplicated initiative sequence
DbVerification.MachineName.DatabaseName.Duplicated initiative sequence.txt
In Table 10‑2:
*MachineName is the name of the machine on which Metrics Management runs.
*DatabaseName is the name of the database on which the verification is performed.
Reports generate in the user's application data folder, for example the Administrator\AppData\Roaming\Actuate folder on Microsoft Windows Server 2008. An orphan objects or duplicated initiative sequences report generates only on the Metrics Management Server machine if the report is larger than 50 MB and is merged into the overview report if the report is less than 5 KB.
How to verify a database
1 In Servers and Databases, select the database to verify.
2 Make the database unavailable.
3 Choose Verify Database. Metrics Management backs up the existing database and begins to verify.
4 A message appears to indicate that the verification completes successfully, as shown in Figure 10‑39. Choose OK.
Figure 10‑39 Verifying a database
5 To open the verification overview log file, in the dialog box shown in Figure 10‑40, choose Yes.
Figure 10‑40 Choosing whether to open the verification overview log file