To add an Oracle database to ingest into Velocity

1. From the Velocity Console, in the left pane, click Database Sources.

2. On the Database Sources window, click +, and then click Add Database to Ingest.

3. Select Ingest Oracle to ingest an Oracle database source into Velocity, select whether you want to use Velocity or NetBackup to ingest this database source, and then click Next.

   See Ingesting an Oracle database with NetBackup CoPilot

   See How to set up NetBackup CoPilot to ingest Oracle databases into Velocity

4. If you selected Use NetBackup as the ingestion method in step 3, select From NetBackup CoPilot under NetBackup Ingestion Method.

5. Enter the hostname or IP address of the Oracle database server that you want to add to Velocity.

6. Click + to add the server name or IP address to the Added Hosts list.

   To specify a database in a RAC environment, enter each node name or IP address one at a time. Then, click + to add each node to the Added Hosts list.

7. Enter the name of the Oracle database that you want to add to Velocity as a source.

   The database name must start with a letter, can contain only letters, numbers, underscores (_), number signs (#), and dollar signs ($), and cannot exceed 30 characters. Refer to your Oracle documentation for other database name requirements.

8. (Optional) For the option Enable Copy Preparation, click Yes if you want to change data in a database before users can access the database copies from their sandboxes.

9. (Optional) Enter a user-friendly name for the database.

10. (Optional) Enter a meaningful description of the Oracle database.

11. Enter an NFS mount path, if you do not want to use the default path.

    The NFS mount path is the path on the host server where the NFS share is mounted. The default path is /mnt/velocity.

12. Click Next.

13. (Optional) To create a recurring schedule for the ingestion, configure the scheduling options, and then click Next.

    If you do not want to create a recurring schedule, click Skip.

    If you selected the option to use NetBackup to ingest the database, the scheduling option is not available because scheduling is controlled within NetBackup.

    You may have to upgrade your Velocity Storage Server to enable scheduling.

14. (Optional) Select the amount of time you want to retain this database source and all of its subsequent copies.

    After the retention period ends, this database source and all of its copies are removed from the Velocity Storage Server.

    Setting a default retention period for a database source that NetBackup ingested is not supported.

    If you want to save this database source and its subsequent copies indefinitely, click Skip.

15. Click Next.

16. Do one of the following:

    To ingest from an Oracle database that is hosted on ASM to a regular file system that is hosted on the Velocity Storage Server:	Do the following: Click Save. Edit the ingest_options.json file and set the 'StorageType' option to 'FS'. See Editing default options for the ingest method for Oracle databases Save the ingest_options.json file. Click Ingest.
    To save the database information that you added, and then return to the Database Sources window without starting the ingest process:	Click Save. You can run the ingest any time after you have saved the database information. See Ingesting an Oracle database into Velocity for the first time See Ingesting an Oracle database with NetBackup CoPilot
    To save the database information and start the ingest process now: This option is available only if you selected the option to use Velocity to ingest this database source in step 3.	Click Ingest. After the database is successfully ingested, you can do any of the following: Create a sandbox. See Creating a sandbox from an Oracle database copy View the database copies. See Viewing database copies