|
Version 2.4/02 (Solaris)
March 17, 1999
New Features
DBAnalyzer now supports Ingres release 6.4/07.
Bug Fixes
ID: 980044 Ingres version.rel file format change
Some Ingres 6.4 patches alter the format of the Ingres version string
in the version.rel file. Version parsing has been enhanced to
understand both formats.
ID: 980045 dba_query sample time menu option fails
The variable used to store the sample interval was incorrectly declared
for 64 bit environments and generated an Ingres FRS data conversion
error message. The sample time could not be changed as a result. The
declaration has been fixed.
ID: 980023 alarm_history report missing
The alarm_history.rw file did not appear in the default distribution.
This has been added.
ID: 980026 sentinel alarm severities incorrect
Alarm severities for MODIFIED_PAGE_COUNT_HIGH and GROUP_FIXED_COUNT_HIGH
in dba_sentinel were not correct. The corrected severities are
INFORMATIONAL and URGENT.
ID: 980027 no help files for collector reports in dbamenu
dbamenu did not display collector report help files when the "RepInfo"
option was selected. This has been fixed.
ID: 980028 default begin time for collector reports incorrect
The default begin time for collector reports was 1900. This has been
changed to "yesterday".
ID: 980029 dba_daily defaults incorrect
The dba_daily script file had incorrect default values for data retention
period, process limit, and optimization. The corrected settings are
pdb_days = 15, process_limit = 1, and optimize_pdb = "Y".
ID: 980030 dbanalyzer_processes script missing
The dbanalyzer_processes.template script was not included in the default
distribution. This template file can be called from the system startup
procedure to start a default collectors and/or sentinels. A copy of the
template file should be customized for the execution environment.
ID: 980031 START_REPORT does not display command line arguments
The START_REPORT script file did not display command line arguments in
the log file. This has been fixed.
ID: 980032 sentinel fails with DBA_BADADDR message
This occurs in some cases while the sentinel is fetching the idle thread
session structure. If the type tag in the structure is not valid, the
sentinel will generate the error and terminate. The invalid tag is a
temporary state so the code will rebuild the structure up to 2 additional
times with a brief pause between each rebuild. If the structure is still
not valid after the rebuilds, the sentinel will generate the DBA_BADADDR
error and terminate.
ID: 980033 monitor QSF Pool display fails with memory allocation error
In some situations the Montior QSF Pool display fails with an error "unable
to allocate dynamic memory block". The QSF Pool objects are stored as
a double linked list. Whenever a new object is added or removed the list
is updated accordingly. If the Monitor attempts to traverse the list when
it is in an inconsistent state it may get stuck in a loop and eventually
consume all available stack space. To prevent this from happening we now
count the number of objects examined and when the count is greater than
twice the maximum object count the loop will terminate and try again.
ID: 980034 dbamenu start_daily and end_daily time adjustments
Each schedule has a daily start and end time that are stored in the
database as dates. When the timezone changes from standard to daylight
savings and vice versa the time is adjusted accordingly. This has the
effect of making these times incorrect as a result of the adjustment.
Since we are only using the time portion of the date the automatic
adjustment will be negated by the code leaving the start and end times
correct regardless of timezone.
|
Database Management Technology 
