How To Enable The Metadata Database For Complex Objects
(Doc ID 2179858.1)
Last updated on SEPTEMBER 20, 2017
Applies to:Oracle DIVArchive - Version 6.5 and later
Information in this document applies to any platform.
This document is designed to assist a user in enabling a metadata database to support archiving complex objects. Complex objects are defined in the manager.conf file as being an object with over 1,000 components.
To be able to effectively operate with large volumes of files/folders and other metadata, DIVArchive stores this metadata separately from the Oracle database in what is called the DIVArchive Metadata Database. The DIVArchive Metadata Database contains files stored in a file system local to the DIVArchive Manager. The directory that contains these files is the Metadata Database Root Folder.
The DIVArchive Metadata Database has a very high performance, almost unlimited scalability and in the future can be used to store many different types of metadata obtained from various sources. The Metadata Database should be treated with the same caution as the Oracle database; it should be backed up at regular intervals via the DIVArchive Backup Service.
It is highly recommended that the Metadata Database Files be stored on a RAID Disk Array. The Metadata Database should not be on a standard disk due to decreased performance and the (real-time) backup functionality that a RAID Array offers the system.
Metadata Database Files stored on a standard disk will be vulnerable to data loss in the event of a single disk failure, until the information is replicated via the DIVArchive Backup Service. Storing the Metadata Database Files on a RAID Array isolates the data from this type of failure.
Note: The information stored in the Oracle Database is already stored on a RAID-1 Array and is not subject to data loss in the event of a single disk failure.
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