Veritas Velocity™ User's Guide
- Getting to know Velocity
- Setting up Velocity
- How to set up the Velocity Storage Server
- How to set up the Velocity Client
- Setting up the Velocity on-premises management server
- Upgrading Velocity
- Velocity Storage Server
- Users and roles
- Oracle database ingestion using Velocity
- How to use copy preparation to mask or sanitize sensitive data
- Oracle database ingestion using NetBackup CoPilot
- Microsoft SQL Server database ingestion using Velocity
- Database sources and copies
- About scheduling ingestions for a database source
- Retention periods for database sources and copies
- Sandboxes
- Database recovery
- Alerts and logs
- Managing the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- About WAN optimization on the Velocity physical appliance
- About the Veritas Remote Management Console on the Velocity physical appliance
- About Velocity physical appliance storage
- About users on the Velocity physical appliance
- About Velocity physical appliance checkpoints
- About factory reset on the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- Monitoring the Velocity physical appliance
- Velocity physical appliance security
- About Velocity physical appliance user account privileges
- About the Velocity physical appliance intrusion detection system
- About Velocity physical appliance operating system security
- Recommended IPMI settings on the Velocity physical appliance
- Best practices
- Troubleshooting
- Glossary
- Context-sensitive topics
- Section I. Velocity shell menu commands
- Introduction
- Appendix A. Main > Manage > Storage
- Appendix B. Main > Manage > Cloud
- Appendix C. Main > Manage > Software
- Appendix D. Main > Monitor
- Appendix E. Main > Network
- Appendix F. Main > Settings
- Appendix G. Main > Support
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.
Note:
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
Exception to the custom parameter file | Parameter used |
---|---|
audit_file_dest | This parameter is specified in when a sandbox is created. |
control_files | This parameter is specified in when a sandbox is created. |
db_create_file_dest | This parameter is specified in when a sandbox is created. |
db_name | This parameter is specified in when a sandbox is created. |
db_recovery_file_dest | This parameter is specified in when a sandbox is created. |
db_recovery_file_dest_size | This parameter is controlled by Velocity. |
diagnostic_dest | This parameter is specified in when a sandbox is created. |
dispatchers='(PROTOCOL=) (SERVICE=)' | This parameter is controlled by Velocity |
log_archive_dest_1='LOCATION=' | This parameter is specified in when a sandbox is created. |
memory_max_target | This parameter is specified in when a sandbox is created. |
memory_target | This parameter is specified in when a sandbox is created. |
pga_aggregate_target | This parameter is controlled by Velocity. |
sga_target | This parameter is controlled by Velocity. |