2. Creating a New Ingres Development Environment : How You Prepare for Development Installation Upgrade : Ingres Monitoring Tools and Scripts
 
Share this page                  
Ingres Monitoring Tools and Scripts
If there are tools or scripts that are used to monitor the Ingres installation (for example, Unicenter), they must be reviewed for compatibility with the new release of Ingres.
Check for these items, for example:
On the UNIX platform are I/O slaves still used?
OS-thread architectures such as Windows and Sun Solaris do not use I/O slaves.
Does the tool parse iimonitor, logstat, lockstat, or trace point output?
The detailed wording and positioning of logstat and lockstat output can change from release to release.
Have log file name changed?
For example, if upgrading from Ingres 6.4, the log files II_RCP.LOG and II_ACP.LOG are renamed to iircp.log and iiacp.log.
Does the tool parse Ingres parameters?
If upgrading from Ingres 6.4, the location of configuration parameters has changed and are now in config.dat and protect.dat.
Are the tools and scripts provided by a third party?
Contact the third party to find out if the tool or scripts must be upgraded to support the new version of Ingres.
Do the monitoring tools use IMA (Ingres Monitoring Architecture)?
There may have been changes to class IDs, which may affect the tools.