The CLONING section of the Tivoli® Storage FlashCopy® Manager profile
contains parameters used for cloning operations. The parameters are
independent of the storage device or application.
The following lists provide the parameters, a description
of each parameter, and default values for the CLONING section.
The
following parameters apply only to
DB2®, Oracle,
and
Oracle in an SAP environment databases:
- DEVICE_CLASS
- This required parameter identifies the device class to use when
cloning a database. The following code sample provides an example
of how to specify options for this parameter:
DEVICE_CLASS device class USE_FOR_CLONING list of clone database names
There
is an optional conditions statement that can be
used. The following code sample includes an example of how to use
the conditions statement:(partioned DB2 databases)
[ON_DBPARTITIONNUMS <list of partitions>]
- Default
- Not applicable.
- Advanced mode only
- No.
- FLASH_DIR_LIST
- This parameter is used to include files systems that are not part
of the database files in the FlashCopy operation.
For example, when cloning a SAP Advanced Business Application Programming
and Oracle Java™ system, the Java instance is not part of the
database files. A clone of the Java instance
is created along with the clone of the database. In this scenario,
use the FLASH_DIR_LIST parameter to include the Java instance directories.
Specify
a fully qualified directory name and file name. For example:
[ON DBPARTITIONNUM list of partitions] fully qualified file name
Inside
the file, specify one fully qualified file or directory on each line. FlashCopy Manager uses
the FlashCopy function
to flash copy the complete volume groups where the specified files
or directories reside.
In DB2 Data
Partitioning Feature environments that contain multiple partitions,
a different file name for each partition can be specified. In this
scenario, because different file names are specified for different
partitions, specify the ON DBPARTITIONNUM parameter.
Each partition number is separated by a space.
The default value
is an empty list. This value prevents additional files or directories
from participating in the FlashCopy operation.
- Default
- By default, no file name is specified.
- Advanced mode only
- Yes.
- DATABASE_SCHEMA
- When a clone database is created from the production database,
the database schema does not change. The clone database uses the database
schema used by the production database. The DATABASE_SCHEMA parameter
is used to specify the database schema. For DB2 and Oracle
databases, the DATABASE_SCHEMA parameter is required.
For Oracle in an SAP environment databases,
the DATABASE_SCHEMA parameter is optional. The
default database schema is determined by the following environment
variables. These environment variables are set on the production database
instance owner environment.
- DB2
- dbs_db6_schema
- Oracle
- dbs_ora_schema
If these environment variables are not set, the
default database schema value is
SAPR3.
When the
DATABASE_SCHEMA parameter is used for
a
Oracle in an SAP environment database,
the specified database schema value overrides all default database
schema values. The
DATABASE_SCHEMA parameter
is evaluated when the following conditions exist:
- A processing script is used with the preproc_clone or postproc_clone command.
- The refresh_clone command is issued with the -X or -Y cloning
parameter.
- The create_clone command is issued with the -Y cloning
parameter.
- Default
- The default value is determined by environment variables.
- Advanced mode only
- Yes.
- ENHANCED_PARTITIONING
- The ENHANCED_PARTITIONING parameter is used
to control processing when extra file systems that are not database
files are specified by the FLASH_DIR_LIST parameter
in a cloning operation. Tivoli Storage FlashCopy Manager fails,
when a file system that is specified by the FLASH_DIR_LIST parameter
contains symbolic links that point to a file system on a different
volume group that is not part of the FlashCopy operation. Set the ENHANCED_PARTITIONING parameter
to NO to ensure that symbolic links if present are not processed.
You must manually add this parameter to the Tivoli Storage FlashCopy Manager profile
file. The following list identifies the possible options:
- NO
- Use this option to ensure that Tivoli Storage FlashCopy Manager does
not process symbolic links of files or directories that are specified
in the FLASH_DIR_LIST profile parameter.
- YES
- Use this option to ensure that Tivoli Storage FlashCopy Manager processes
all symbolic links of files or directories that are specified in the FLASH_DIR_LIST profile
parameter.
- Default
- YES
- Advanced mode only
- Not applicable.
- NEGATIVE_LIST
- The NEGATIVE_LIST parameter is used to control
processing when files not associated with the database are stored
within the same file system used for the backup and restore operations.
This parameter is required. The following list identifies the options:
- NO_CHECK
- Use this option to not check for additional files. The operation
ignores any additional files that are identified. When you use this
option and data is restored, all files that reside on the file system
or volume group are overwritten.
- WARN
- Use this option to receive a warning message for each file that
is identified on the volume, but not part of the FlashCopy operation. The processing continues.
When you use this option and data is restored, all files that reside
on the file system or volume group are overwritten.
- ERROR
- Use this option to receive an error message for each file that
is discovered on the volume, but not part of the FlashCopy operation. The processing ends.
- filename
- Use this option to backup and restore files that are not part
of the database tablespace files. Using this options includes files
in the FlashCopy operations.
When you use this option, specify the fully-qualified names of the
files and directories. Use one line for each entry. When these files
are identified, processing continues. When other files are identified,
but not part of the database tablespace files or identified in the NEGATIVE_LIST file,
processing ends. Any directory listed in the NEGATIVE_LIST file
is processed recursively. For example, all files within the directory,
including subdirectories, are processed during a backup or restore
request.
- Default
- There is no default for this required parameter.
- Advanced mode only
- Yes.
- GLOBAL_SYSTEM_IDENTIFIER
- Use this parameter to specify a string to be used in the IBM® Tivoli Storage Manager for Enterprise Resource Planning Administration
Assistant that uniquely identifies a DB2 or
Oracle database in the system landscape. This parameter is only valid
when the ADMIN_ASSISTANT parameter is specified
in the ACSD section of the profile.
- Default
- Depending on the environment, the default value is either DB2_<DBname> or ORA_<DBname>.
- Advanced mode only
- Yes.
- TIMEOUT_FLASH
- This parameter specifies the maximum time, in seconds, that the
database agent waits for a response to the management agent call during
the flash phase. If the database agent does not
receive a response within the specified time, an error message is
displayed. This parameter allows the maximum time to be specified
for a database to be suspended. This parameter also implies the maximum
time when JFS2 file systems can be frozen. When the timeout is reached,
the file systems thaw, the database is resumed, and the backup operation
ends with an error. The minimum value for TIMEOUT_FLASH is 5 seconds.
- Default
- The default value is 120 seconds.
- Advanced mode only
- Yes
- TIMEOUT_<PHASE>
- Specify the maximum time (in seconds) that the database agent
waits for a response to the management agent call during the <phase> phase.
If the database agent does not receive a response within the specified
time, the backup or restore operation ends and an error message is
issued. The default value is 3600 seconds.
You
can specify one of these phase values for a FlashCopy backup. For example:
TIMEOUT_PREPARE- PARTITION
- PREPARE
- VERIFY
- CLOSE
You can specify one of these phase values for a FlashCopy restore. For example:
TIMEOUT_FLASHRESTORE- PREPARERESTORE
- FLASHRESTORE
- COMPLETERESTORE
- CLOSE
- Advanced mode only
- Yes.
The following parameters
apply only to Oracle and
Oracle in an SAP environment databases:
- OVERWRITE_DATABASE_PARAMETER_FILE
- This parameter is used only with Oracle and Oracle in an SAP environment databases.
This parameter is also included in the OFFLOAD section
of the configuration profile. The parameter specifies whether the
database configuration file on the backup server is overwritten with
the file from the production server. The parameter value in the OFFLOAD section
is not applicable to cloning operations and is ignored.
To copy
the database configuration file from the production system to the
clone system, specify this parameter in the CLONING section
of the configuration profile. The Tivoli Storage FlashCopy Manager software
requires two database configuration files to be available in the clone
instance on the clone system. The default database configuration file
name is ${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora
In
the scenario where the production system is
${ORACLE_SID}=P01 and
the clone system is
${ORACLE_SID}=C01, the following
database configuration files are required:
/oracle/C01/102_64/dbs/initP01.ora
/oracle/C01/102_64/dbs/initC01.ora
The initP01.ora file
is used during the cloning process to recover the database, used in
the FlashCopy operation,
on the clone system. The initC01.ora file is
used to rename and start the clone database.
Specify one of
the following values:
- YES
- Copy the database configuration file from the production system
to the clone system. The following processes occur:
- The clone database configuration file initP01.ora is
copied on the clone system. The existing file, /oracle/C01/102_64/dbs/initP01.ora,
is overwritten.
- The clone database configuration file /oracle/C01/102_64/dbs/initP01.ora is
copied to /oracle/C01/102_64/dbs/initC01.ora.
The existing file, /oracle/C01/102_64/dbs/initC01.ora,
is overwritten. All occurrences of P01 in this file
are renamed to C01.
- NO
- Do not copy the database configuration file from the production
system to the clone system. This value requires that the database
configuration files /oracle/C01/102_64/dbs/initP01.ora and /oracle/C01/102_64/dbs/initC01.ora are
available on the clone system. You must verify that these files are
available and are valid.
If the name of the database configuration file on
the production database is not the default file name,
${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora,
use the
TARGET_DATABASE_PARAMETER_FILE parameter,
in the
CLONING section, to specify the correct name.
In this scenario, the clone database configuration file name is created
by replacing the
${ORACLE_SID} value of the production
database with the name of the clone database.
- Default
- YES
- Advanced mode only
- No.
- TARGET_DATABASE_PARAMETER_FILE
- This parameter is used only with Oracle and Oracle in an SAP environment databases.
This parameter is also included in the ORACLE section
of the configuration profile.
The parameter specifies the database
configuration file name. The parameter value in the ORACLE section
is not applicable to cloning operations and is ignored.
Specify
this parameter in the CLONING section of the profile
to identify the name of the Oracle parameter file for the production
database. Enter the fully resolved path and file name of the Oracle
parameter file for the production database. By default, the file name
of the Oracle parameter file for the production database is initSID.ora.
This file must be a text-based Oracle parameter file (PFILE)
and not an Oracle server file. The default value is ${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora.
If the production database is configured to use an Oracle server file,
this parameter is ignored.
- Default
- ${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora
- Advanced mode only
- Yes.