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
Managing sandboxes when you restart the host Oracle Database server
If you have to restart the Oracle Database server that hosts a sandbox, you must run some manual operations to manage the sandbox. Before you restart the host Oracle Database server, you must shut down the database instance of the sandbox from the host Oracle Database server. After you restart the host Oracle Database server on which a sandbox is located, you can manually start the database instance of the sandbox to begin using the sandbox again.
To manage sandboxes when you restart the host Oracle Database server
- Do one of the following to shut down the database instance of the sandbox:
To shut down a database instance of a sandbox in a non-RAC, non-ASM environment
On the host Oracle Database server, connect to the database instance with SYSDBA privilege using SQL*Plus, and then type the following command:
SHUTDOWN IMMEDIATE
To shut down a database instance of a sandbox in a RAC or ASM environment
On one of the host Oracle Database servers, type the following command:
srvctl stop database -d <database name>
- Do one of the following to start the database instance of the sandbox:
To start a database instance of a sandbox in a non-RAC, non-ASM environment
On the host Oracle Database server, connect to the database instance with SYSDBA privilege using SQL*Plus, and then type the following command:
startup
To start a database instance of a sandbox in a RAC or ASM environment
On one of the host Oracle Database servers, type the following command:
srvctl start database -d <database name>