About setting custom initialization parameters for a sandbox for an Oracle database copy

By default, Velocity uses server parameters from the ingested database to set up an Oracle database copy in a sandbox. You can create a custom parameter file to override those server parameters and to control the startup behavior of a sandbox. When a database is ingested to Velocity, the custom parameter file is stored with the database copy. Then, the custom parameter file is automatically applied to a sandbox when it is created from the database copy.

Setting custom initialization parameters is not supported for ingestions that use the NetBackup method.

The custom parameter file must be located on the Oracle Database server from which a database is ingested.

The required naming convention of the custom parameter file is [dbName]_pfile.ora. The custom parameter file name is not case sensitive.

For example, for the ingestion of a database named basedb, the custom parameter file is named basedb_pfile.ora. The ingest process searches for the file named basedb_pfile.ora in the folder that you specify in the ingest_options.json file.

You can edit the ingest_options.json file to specify the name and the location of the custom parameter file on the Oracle Database server.

See Editing default options for the ingest method for Oracle databases

If a matching custom parameter file is available when a database is ingested, the parameters in the file are used.

Parameters in the custom parameter file are not used for some values that are specified when a sandbox is created. Exceptions to the custom parameter file are listed in the following table:

Table: Custom parameter file exceptions