This configuration profile is located in the $ORACLE_HOME/dbs directory.
The .sap profile is described in
detail in the SAP® database guide for Oracle that is
provided by SAP®. It is possible that there is an existing .sap file
in your environment. The following information identifies the profile
parameters that are valid in the .sap profile.
The
following list contains parameters that you most likely need to add
or change in the existing .sap file.
This
configuration refers to the following keywords within that profile:
- backup_type
- Identifies the default type of the database backup. This parameter
is only used by brbackup (default
is offline).
- backup_mode
- Identifies the scope of the backup. This parameter is only used
by brbackup.
The default is all; however, if the parameter is
set to all and Oracle RMAN is used, an incremental
backup cannot be created. When the backup_mode parameter
is set to all, a backup of all data files is completed
using the backint interface.
For an incremental
backup of an Oracle in an SAP environment database
using Oracle RMAN, set the BR*Tools option
for the backup_mode parameter to full.
- backup_dev_type
- Determines the backup medium that is used (the default is tape).
To create a snapshot backup using Tivoli® Storage FlashCopy® Manager,
this parameter must be set to util_vol or to util_vol_online.
Minimize the time during which the database is degraded.
- util_par_file
- If you are running FlashCopy Manager with IBM® Tivoli Storage Manager for Enterprise Resource Planning, set this
parameter to the fully qualified path of the IBM Tivoli Storage Manager for Enterprise Resource Planning profile
(.utl file). This way FlashCopy Manager uses
the configuration that was added to the IBM Tivoli Storage Manager for Enterprise Resource Planning configuration
file (.utl file).
If you are running FlashCopy Manager in
an environment where IBM Tivoli Storage Manager for Enterprise Resource Planning is not
configured, set this parameter to the fully qualified path of the FlashCopy Manager profile.
This way FlashCopy Manager uses
the configuration that was added to the CLIENT section
of the FlashCopy Manager profile.
- util_path
- Specifies the path to the backint executable.
If
you are running FlashCopy Manager with IBM Tivoli Storage Manager for Enterprise Resource Planning, you do
not need to set this parameter.
If you are running FlashCopy Manager in
an environment where IBM Tivoli Storage Manager for Enterprise Resource Planning is not
available, set this parameter to the INSTANCE_DIR (<Instance
owner $HOME directory>/acs/).
- util_vol_unit
- Specifies the smallest unit that can be backed up with a snapshot
or clone, and also determines restore granularity. The possible values
are sap_data (finest restore granularity), all_data,
and all_dbf (not usually used).
Note: SAP requires
that the setting of this parameter correctly describes the disk layout
of your database.
If your disk layout consists of the following
volume groups, use
sap_data:
- At least one volume group for each sapdata directory
- At least one volume group for each origlog directory
- At least one volume group for each mirrlog directory
For sap_data, there must be exactly one
volume group for each sapdata directory, exactly
one volume group for each origlog directory,
and exactly one volume group for each mirrlog directory.
If one of the sap_data, origlog,
or mirrlog directories contains more than one
volume group, there is a fourth parameter value disk_vol that
must be used. The parameters disk_vol and all_dbf are
not recommended by SAP because they contradict the SAP recommendation
about the separation of data files and redo log files. The default
value set by SAP is sap_data.
If your disk
layout consists of the following volume groups, use
all_data:
- At least one volume group for sapdata
- At least one volume group for origlog
- At least one volume group for mirrlog
- util_vol_access
- Specifies the accessibility of snapshot backup volumes:
- none (required on the production system)
- copy (not supported)
- mount (required on the backup system if SAP® BR*Tools installed
on the backup system)
- both (not supported)
- util_vol_nlist = (<nfile_name1>, <nfile_name2>,
…) | no_check
- This parameter defines a list of non-database files or directories
that are located on the database disk volumes but do not need to appear
in the list of files to back up in the input file. These files are
automatically included in the backup, but are never reported in the BACKINT interface
messages, especially not in the #ERRFILE message. During a restore,
these files (and possibly fixed files) might be overwritten without
prior warning.
no_check deactivates the BACKINT check
of the backup volumes. This check makes sure that the backup volumes
do not contain either non-database files or database files that belong
to a database other than the database to be backed up. When no_check is
set, the user takes responsibility for making sure that the database
volumes (directories sapdata, origlog,
and mirrlog) only contain database files of the
database to be backed up. Or, if the database volumes contain either
non- database files or database files from a database other than the
database to be backed up, the user accepts that such files can be
overwritten without warning.
- util_options = <additional_backint_options>
- This parameter defines additional BACKINT options that BR*Tools places
after the standard command-line options when calling the BACKINT program.
With this parameter, the FlashCopy Manager backint options -O <TSM_BACKUP_FROM_SNAPSHOT
value> and -S <device class> can be specified.
See BR*TOOLS - User interface for Oracle in an SAP environment for more information
about these backint options.
Example:
util_options = "-O yes -S STANDARD"