2.5

Table Of Contents
Otherwise, do not include an archive log in the backup. If the database is in nonarchive mode, the refresh
from external database feature does not support point in time refresh. The absolute path of any control
files, data files, redo log files, or temporary files of source database cannot contain any space, tab, carriage
return, asterisk, question mark, backslash, quote or line feed characters.
n
The database must be included in the backup. You cannot back up only the archive logs.
n
For golden clone ingestion and golden clone refresh, you must supply a LIST file containing information
about the backup operation. See next section for the name convention and format of LIST file.
n
For a one-time clone (in-place refresh), a full backup or one level 0 incremental backup plus several
optional level 1 subsequent incremental backups is required. You can optionallly do several subsequent
level 1 incremental backups (L0+nL1). For a point in time refresh, record the modify time so you can refresh
to the specified time. For a golden clone, a level 0 incremental backup is required for ingestion, and a level
0 or level 1 (either differential or cumulative) incremental backup is required for a refresh.
n
You must have an spfile in the control file backup set if you do not specify a pfile.
n
The database name must be the SID.
n
If network speed is limited or the database is very large, the ingestion-refresh process can take a long time.
If you use DHCP for the database virtual machine, ensure that the DHCP lease time is long enough so that
the IP address does not change during the ingestion and refresh process.
Additional Requirements
You must comply with the following additional requirements when backing up the source database.
n
The NFS server must be accessible to the DB Access Network or the Internal Network when ingestion and
refresh is running, and the backup files, LIST file and pfile must be readable.
n
You must allocate sufficient storage when ingesting, and estimate future expansion when ingesting a
golden clone.
Supported Oracle Features
The following Oracle features are supported.
n
Backup set.
n
Different block size for various data files.
n
BLOB data type.
n
Compressed backup.
Unsupported Oracle Features
The following Oracle features are not supported.
n
Image copy backup.
n
External file.
n
Encrypted backup.
n
OEM (Oracle Enterprise Manager) is not supported on ingested database.
Chapter 9 Managing Databases
VMware, Inc. 91