Message Logging
Pervasive PSQL now supports various logging repositories for messages. The logging falls into two broad categories:
The following table summarizes the repositories.
Licensing Messages
As the table above shows, several of the logging repositories emphasize licensing messages. The reason is that the Pervasive PSQL licensing components periodically verify that the key for the database engine is still valid. If a key is determined to be invalid, the key changes state from “active” to “failed validation.” The database engine functions normally for a certain number of days so that you have ample time to correct the failures.
If you do not correct the causes of the failed validation before the number of days ends, the key changes state again to “disabled.” The key is no longer valid and the database engine cannot access data files.
Because you need to attend to a failed validation in a timely manner, the state change of the key is brought to your attention as soon as possible through the various logging repositories.
Note that message logging follows a one-way hierarchy: any licensing message logged to Pervasive Notification Viewer is also logged to the Operating System Event Log and to the Pervasive PSQL Event Log. Similarly, any licensing message logged to the Operating System Event Log is also logged to the Pervasive PSQL Event Log.
Pervasive Notification Viewer
The Pervasive Notification Viewer is an application utility for displaying messages logged by the licensing components. The purpose of the utility is to inform you of noteworthy licensing messages in a noticeable but unobtrusive manner.
Pervasive Notification Viewer is installed by default with Pervasive PSQL Server, 32-bit and 64-bit, on Windows and Linux, and with Pervasive PSQL Workgroup.
On Windows platforms, the executable is named notifyviewer.exe. The Pervasive PSQL installation adds the utility to the Start Menu so that it re-starts when you restart Windows.
On Linux distributions, the utility is a shell script named notifyviewer. If you restart Linux, you must restart Pervasive Notification Viewer. The shell script is not automatically executed when Linux is restarted.
Pervasive Notification Viewer provides two interfaces: system tray icons and a graphical user interface (GUI).
See Pervasive Notification Viewer in Pervasive PSQL User's Guide for details.
Operating System Event Log
The Pervasive PSQL license administration components write messages to the operating system event log on Windows platforms. All Pervasive PSQL components write messages to the operating system event log on Linux distributions.
Any licensing message categorized as an “error” or “warning” is logged. In addition, certain information messages are logged.
On Windows platforms, Pervasive PSQL logs licensing messages to the Windows Application Event Log. They are a subset of the licensing messages written to PVSW.LOG. Pervasive PSQL Server, Workgroup, and Client 32-bit currently log messages; Pervasive PSQL Client 64-bit does not. See Windows Platforms Event Logs in Pervasive PSQL User's Guide for details.
On Linux distributions, all Pervasive PSQL components write messages to the standard Linux logging system, syslog. See Linux Distributions Event Logs in Pervasive PSQL User's Guide for details.
Pervasive PSQL Event Log
On Windows platforms, all Pervasive PSQL components write status, error, warning, and information messages to the Pervasive PSQL event log, PVSW.LOG. Any licensing message categorized as an “error” or “warning” is logged. In addition, certain information messages are logged. See Pervasive PSQL Event Log in Pervasive PSQL User's Guide for details.
Related Topics
See also Utilities and SDK Access Methods.