Administration Guide - Avaya Support

Operation History Viewer
Understanding Operation History Events
The tracing system includes the following storage areas:
! Transaction database This is a permanent storage area for voice mail
system activity. The Reporting Tool is used for extracting information from
this database. For more information, see Chapter 7, “Reporting Tool”.
! Operation history database This is a temporary storage area for events
that are generated by the voice mail system. The database is purged
periodically. The Operation History Viewer is used for viewing events in
this database. See Operation History Viewer Window on page 8-15.
Notes:
! For information on configuring this database, please refer to the
Avaya Modular Messaging Concepts and Planning Guide.
! For a 1523 application event, use the Microsoft ODBC tool to
repair the database (ophist.mdb). If it cannot be repaired,
replace the corrupt ophist.mdb with an empty ophist.mdb.
Procedures for Using the Operation History Viewer
! Before you can view events in the Operation History Viewer, you must
enable operation history collection for the voice mail domain. See Enabling
the Collection of Operation History Events on page 8-4.
! If the Operation History Viewer is installed on the tracing system machine,
a data source is created automatically. If not, you need to select a system
data source before you can use the Operation History Viewer. See
Selecting a Data Source & ODBC Tracing on page 8-5.
Note: If ODBC logging is enabled on the MAS, system performance
degrades. ODBC tracing should be enabled for debugging only.
! See Creating, Viewing & Exporting Sessions on page 8-9.
— “Procedure 1: Creating & Viewing a Live Session”.
— “Procedure 2: Creating & Viewing a Historical Session”.
— “Procedure 3: Saving a Session”.
— “Procedure 4: Opening a Session”.
— “Procedure 5: Changing Session Properties”.
— “Procedure 6: Exporting Operation History Events”.
Avaya Modular Messaging Release 3.1 with the Avaya MSS
February 2007 MAS Administration Guide
8–3