Information

Title	Some databases do not autostart when the Adminserver starts

URL Name	P178964

Article Number	000133504

Environment	Product: OpenEdge Version: All supported versions OS: Windows

Question/Problem Description

Some databases do not autostart when the Adminserver starts
OE Console shows some databases as not running when they are configured to autostart
These databases that the OE Console shows as not running are running when queried with DBMAN -query and clients can connect and run application code on them

Steps to Reproduce

Clarifying Information

Some databases were upgraded the databases from 10.0B to 10.2B.

Error Message	Errors in admserv.log file [Property Manager] Data storage error -2 calling recGetIntValue(fieldID=25).: metric.vst.<dbname>._MstrBlk._mstrblk-misc [STDERR] java.io.EOFException [Database] getStatistics failed: Error processing schema for database <dbname> / table _Connect [STDERR] com.progress.juniper.admin.DatabasePluginComponent$SchemaParsingException: Error processing schema for database <dbname> / table _Connect [Fathom] Unable to retrieve statistics for database <dbname>. Error: Error processing schema for database <dbname> / table _Connect (12109)

Error Message

Errors in admserv.log file
[Property Manager]      Data storage error -2 calling recGetIntValue(fieldID=25).: metric.vst.<dbname>._MstrBlk._mstrblk-misc
[STDERR]                java.io.EOFException
[Database]              getStatistics failed: Error processing schema for database <dbname> / table _Connect
[STDERR]                com.progress.juniper.admin.DatabasePluginComponent$SchemaParsingException: Error processing schema for database <dbname> / table _Connect
[Fathom]                Unable to retrieve statistics for database <dbname>. Error: Error processing schema for database <dbname> / table _Connect (12109)

Defect Number

Enhancement Number

Cause

The DBAgent is used to communicate between the managed database and the AdminServer. Virtual System Tables (VSTs) are missing for some databases which the DBAgent needs, which is why these databases are showing as not running through the OE Console.

Resolution

At the next offline opportunity, update Virtual System Tables (VSTs) on the databases that were upgraded. Since this is a schema change, it is recommended to backup the database beforehand.

$ proutil <dbname> -C updatevst

Workaround

Notes

Progress Articles:

Must replication be disabled before running proutil updatevst?
Does UPDATEVST require ABL programs to be recompiled ?

Keyword Phrase

Last Modified Date	11/20/2020 7:37 AM