My Oracle Support Banner

RDBPROD: INTEGRATE... ALTER FILES can cause loss of metadata (Doc ID 1072469.1)

Last updated on DECEMBER 19, 2019

Applies to:

Oracle CDD/Repository - Version 7.0 and later
Oracle Rdb Server on OpenVMS - Version 7.0 and later
HP OpenVMS VAX
HP OpenVMS Itanium
HP OpenVMS Alpha

Symptoms

Re-integrating an Rdb database using definitions from CDD (INTEGRATE with ALTER FILES) may result in the loss of some definitions in the database and possible data loss. Metadata, such as tables, indexes, and views, defined in the database while attached by filename rather than pathname could disappear, as well as the data in such a table. Errors during the integrate can also cause loss of metadata.

Note: Oracle strongly recommends a full RMU/BACKUP of the database be made prior to any metadata changes, including INTEGRATE with ALTER FILES.

Changes

Examples:

1. Tables and views
2. Indexes
3. Indexes used in storage maps

1. Tables and views.

Define a new table and a view on a table that is fully integrated in the CDD and the database while attached by filename rather than pathname. After defining the view, perform an INTEGRATE... ALTER FILES. The view no longer exists in the database.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.