This tab is available after a successful discovery operation and the fields are displayed as per the Relational Database Management System (RDBMS) with which the Docbase is created.
Prior to configuring the Documentum iDataAgent, the Oracle iDataAgent should be installed and configured if the database is not present on the primary Documentum Content Server host.
Use this tab to specify the Oracle database properties. The Oracle database contains the database and log files to be backed up by the Documentum iDataAgent.
Enter the name of the client computer on which the database has been installed. This could be the same or a different client computer on which the Documentum iDataAgent has been installed. Use the dropdown box and select from the list of client computers.
Displays the type of database iDataAgent that will be backed up by the Documentum iDataAgent. This is automatically populated after Discover has been selected in the General tab.
Enter the name of the Oracle instance that is created for the database.
Click Configure Password to specify the application User account used by the system to perform all Data Protection and Recovery operations for the Oracle instance.
The Documentum iDataAgent requires an Oracle user account to access the Oracle application and database. You may have separate user accounts to access these components.
The following tables illustrates the required privileges these user accounts should have.
- An operating system account with administrator privileges for the Oracle application.
The following table defines the user account requirements for each operating system:
Operating System User Account Windows
- The Local Administrator of the computer on which the Oracle database resides.
- The user must be part of the ora_dba group with read and write permissions on the SnapProtect folder.
Note: when using Oracle 12c, grant full control permission for the Oracle home user for the SnapProtect folder.
UNIX Member of the user group assigned during the Agent installation. The operating system user account can also be used.
- An Oracle user account with the SYSDBA or SYSBACKUP (in Oracle version 12 or higher) privilege can access the Oracle target database. Provide the account information as a connect string with the following connection details:
- The database user ID and password
- The Oracle Service Name (as defined in the tnsnames.ora file)
Use separate accounts to access the target database and the recovery catalog database. The recovery catalog database user account must have RECOVERY_CATALOG_OWNER privileges, which are not required for the target database user.
By default, the user account for the target database has administration privileges and must be established so the Oracle database administrator can configure additional accounts (except Impersonate User).
Initially, the user account credentials are provided during the instance configuration after the installation of the Agent. You can subsequently change the user account information to access the Oracle database and application at the Instance level whenever the credentials are updated.
Enter the path to the database installation Home directory. Click Browse to specify or change the designated path.
Specifies the database connect string. You can change the database connect string by entering 1) database user ID, 2) password for the user ID @ 3) Oracle service name in the three spaces provided. The user ID must have SYSDBA, ALTER SYSTEM and SELECT ANY TABLE system privileges.
Alternatively, instead of the SELECT ANY TABLE privilege, you can create less powerful user IDs with the following object privileges:
- SELECT ON "SYS"."V_$DATABASE"
- SELECT ON "SYS"."V_$DATAFILE"
- SELECT ON "SYS"."V_$SESSION"
- SELECT ON "SYS"."DBA_TABLESPACES"
- GRANT SELECT ON "SYS"."V_$ARCHIVE_DEST" TO "USER_NAME"
You can create a user ID with these privileges, or you can use the internal user ID.
Use Catalog Connect
When the check box is selected a connection is established between the target database and the Recovery Catalog database using the specified connect string, and the Recovery Catalog database will be used for backups. When the check box is cleared, there will be no connection between the target database and the Recovery Catalog database, and the target database Control Files will be used for backups.
The three fields are used to identify/create the connect string for the Recovery Catalog database. You can change the connect string by using entering 1) Recovery Catalog database user ID, 2) password for the user ID @ Recovery Catalog service name.
Ctrl File Autobackup
Specifies whether to configure the control file for AUTOBACKUP so that every time a BACKUP or COPY command is executed, an autobackup of the control file is performed. To change the configuration setting, select one of the following entries from the list:
- Not Configure - Disables autobackup of the control file.
- Configure Yes - If the backup includes a datafile, then the database will not automatically include the current control file in the datafile backupset, but will write the control file and server parameter file to a separate autobackup piece. If the backup does not include a datafile, the control file and server parameter file will be written to their own autobackup piece.
- Configure No - If the backup includes a datafile, then the database automatically includes the current control file and server parameter file in the datafile backupset. The database will not create a separate autobackup piece containing the control file and server parameter file.
Use this space to specify the block size for backup and restore operations on the selected instance. You can disable the block size specification by setting the value to 0. In such cases, the default block size value will be used for backup and restore operations.