Startup and shutdown options for the Oracle agent

You can specify Startup and Shutdown options for the Oracle instances that are configured.

Note:

In case of the CDB or traditional database types, the use of the SRVCTLSTART or SRVCTLSTART_RO startup options along with the UseSystemD attribute is not supported.

In case of the PDB database types, the use of the UseSystemD attribute is not supported.

In either case, if the UseSystemD attribute is set, the agent reports the resource as UNKOWN and logs an appropriate message accordingly.

Table: Startup options for traditional database and container database lists the startup options that the agent supports for traditional database and container database.

Table: Startup options for traditional database and container database

Option

Description

STARTUP_FORCE

(Default)

Runs the command startup force pfile='location_of_pfile' if the pfile is configured.

If the pfile is not configured, the agent runs startup force. It picks up the default parameter files from their default locations.

STARTUP

Runs the command startup pfile='pfile_name_with_absolute _path' if the pfile is configured.

For example:

startup pfile = '</dbs/pfilename>'

If the pfile is not configured, the agent runs startup without pfile.

RESTRICTED

Starts the database in the RESTRICTED mode.

RECOVERDB

Performs a database recovery on instance startup.

CUSTOM

Uses a predefined SQL script (start_custom_$SID.sql) and runs custom startup options. The script must be in the /opt/VRTSagents/ha/bin/Oracle directory and must have access to the Oracle Owner OS user. If the file is not present, the agent logs an error message.

With a custom script, the agent takes the following action:

     sqlplus /nolog <<!
     connect / as sysdba;
     @start_custom_$SID.sql
     exit;
     !

SRVCTLSTART

Uses the srvctl utility to start an instance of the database.

For RAC clusters, you must manually set the default startup option as SRVCTLSTART.

With systemD enabled, Oracle single instance or RAC does not support SRVCTLSTART option on the SLES 12, RHEL 7, and supported RHEL-compatible distributions.

Note:

This is applicable only when an Oracle grid infrastructure is configured.

SRVCTLSTART_RO

Uses the srvctl utility to start an instance of the database with the -o 'read only' option.

With systemD enabled, Oracle single instance or RAC does not support SRVCTLSTART_RO option on the SLES 12, RHEL 7, and supported RHEL-compatible distributions.

Note:

This is applicable only when an Oracle grid infrastructure is configured.

Table: Shutdown options for traditional database and container database lists the shutdown options that the agent supports for traditional database and container database.

Table: Shutdown options for traditional database and container database

Option

Description

IMMEDIATE

(Default)

Shuts down the Oracle instance by running shutdown immediate.

TRANSACTIONAL

Runs the shutdown transactional command. This option is valid only for the database versions that support this option.

CUSTOM

Uses a predefined SQL script (shut_custom_$SID.sql) and runs custom shutdown options. The script must be in the /opt/VRTSagents/ha/bin/Oracle directory and must have access to the Oracle Owner OS user. If the file is not present, the agent shuts the agent down with the default option.

SRVCTLSTOP

Uses the srvctl utility to stop an instance of the database.

For RAC clusters, you must manually set the default option as SRVCTLSTOP.

Note:

This is applicable only when an Oracle grid infrastructure is configured.

SRVCTLSTOP_TRANSACT

Uses the srvctl utility to stop an instance of the database with the -o transactional option.

Note:

This is applicable only when an Oracle grid infrastructure is configured.

SRVCTLSTOP_ABORT

Uses the srvctl utility to stop an instance of the database with the -o abort. option

Note:

This is applicable only when an Oracle grid infrastructure is configured.

SRVCTLSTOP_IMMEDIATE

Uses the srvctl utility to stop an instance of the database with the -o immediate option.