Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

OSS Monitor Migration and Fallback Considerations
Consider the following key points about the OSS Monitor database to eliminate most migration
and fallback issues in the OSS environment:
• Records in the database are associated with a version of the OSS Monitor.
• After a migration to a newer RVU, records in the database are upgraded and new records
are added when a new version of the OSS Monitor first opens the database.
• If settings are altered and then a fallback to a previous RVU occurs, attribute settings will be
within the limits supported by the earlier OSS Monitor version in the fallback RVU—even if
the attributes had been altered to be outside of those limits.
• After an RVU fallback, objects and attributes added during the previous database upgrade
are not visible, but are retained for use when the system is again migrated to a newer version
of the OSS Monitor.
• After an RVU fallback, the database can be altered without the need for a second database
upgrade when the system is migrated again to a newer version of the OSS Monitor. After the
migration, new object attributes added as part of the earlier database upgrade retain their
settings.
394 Falling Back to a Previous Release Version Update or Upgrading to a New Release Version Update