Filter
Top Products
ANR4426W Recovery Log can no longer be Expanded by the Space Trigger.
Explanation: The Recovery Log Space Trigger was going to automatically expand
the recovery log. Expanding the recovery log would cause the recovery log’s size to
exceed 5GB, which is beyond the server maximum limit for the recovery log.
System Action: Server operation continues, but the recovery log is not
automatically expanded. No additional recovery log expansion will occur as a result
of the recovery log space trigger.
User Response: None. You may review the space trigger settings and use the
UPDATE SPACETRIGGER LOG command to adjust space trigger values. You may
also backup the data base and /or setup a data base backup trigger to cause the data
base to be backed up more often. Backing up the data base will decrease the
recovery log utilization and you then use the REDUCE LOG and DELETE
LOGVOLUME command to decrease the size of the recovery log.
ANR4427W One or more Recovery Log Volumes differ in number of copy volumes.
Explanation: The Recovery Log Space Trigger was in the processing of expanding
the recovery log by creating new volumes. . In doing so, copy volumes are created
for mirroring, and existing volumes are examined for mirroring. One or more
recovery log volumes was found to have a different number of copy volumes than
other volumes of the same type. It is recommended that the same number of copy
volumes be created for each volume of the same type ( data base or log ).
System Action: Server operation continues.
User Response: Use the QUERY LOGVOL command to determine if your volume
configuration is satisfactory. You may use the DEFINE LOGCOPY command to
define additional copy volumes, if necessary. You may use the DELETE LOGCOPY
command to delete unnecessary copy volumes.
ANR4428W One or more Data Base Volumes differs in number of copy volumes.
Explanation: The Data Base Space Trigger was in the processing of expanding the
data base by creating new volumes. . In doing so, copy volumes are created for
mirroring, and existing volumes are examined for mirroring. One or more data base
volumes was found to have a different number of copy volumes than other volumes
of the same type. It is recommended that the same number of copy volumes be
created for each volume of the same type ( data base or log ).
System Action: Server operation continues.
User Response: Use the Query DBVOL command to determine if your volume
configuration is satisfactory. You may use the DEFINE DBCOPY command to
define additional copy volumes, if necessary. You may use the DELETE DBCOPY
command to delete unnecessary copy volumes.
584
Version 3 Release 7