|
por este dispositivo também tem outras instruções :
Facilidade de uso
Bug ID
Description
Solution
This is because some of the Oracle memory related
parameters are incorrectly removed from the clone
database’s parameter file.
65364
Creating (rmora_create) virtual copy failed if
The ascii controlfile is now generated with a fixed name
tracefile_identifier parameter is set in Oracle
regardless of the tracefile_identifier
parameter file.
parameter’s value.
The command failed to find the generated ascii
controlfile because its name is appended with the value
of the tracefile_identifier parameter.
65370
Database cloning (rmora_createdb) failed with error The Oracle parameter value is now merged into one
message “ORA-01078: failure in processing system
line before parsing.
parameters".
The command failed to parse Oracle parameters in
which their values span multiple lines.
For example: log_archive_dest='service=sdb
LGWR SYNC AFFIRM
nl
db_unique_name=sdb
nl
valid_for=(online_logfiles,primary_role)'
65761
Mounting a virtual copy (rmora_mount) failed with the The VxVM snapshot disk group is now explicitly imported
error message “VxVM vxdg ERROR V-5-1-10978 Disk
only if it was not imported implicitly when vxdctl
group archdg: import failed: Disk group exists and is
enable is executed.
imported”.
The error occurs if the snapshot VxVM disk group is a
non-cluster (non-shared) disk group. During the mount,
the snapshot VxVM disk group is imported twice. The
first import occurs automatically when the VxVM vxdctl
enable command is executed. The second import
occurs when the VxVM vxdg import command is
executed.
65871
Database cloning (rmora_createdb) failed with error Explicitly set the permission of the temporary script file,
message "SP2-0310: unable to open file" when running which was generated by root to 644, so the script file
as root user.
can be executed by the Oracle user.
The error occurs if the root user’s umask is not set to
0022. The controlfile creation script (to create the clone
database’s binary controlfile) is generated by root user,
but is executed by Oracle user. If the umask is not set
to 0022, the Oracle user does not have the permission
to execute the created script, hence the error.
66216
The user ID and group ID equivalent of Oracle and ASM The same Oracle and ASM user ID and group ID
users between the database server and the backup
requirement is now removed. It is still required that the
server is not necessary.
Oracle and ASM user names must be the same between
This requirement is not necessary, and causes
database server and the backup server, and if
unnecessary restriction on RMO for the users.
applicable, the Semantec NetBackup master server.
67272
The Remote Copy row in the table displayed by the GUI The GUI no longer displays the count for the Remote
for a selected database instance tree node has been
Copy row because the value should always be 0 and
removed because the count for that row is always 0.
the information is therefore not useful.
67758
Database cloning (rmora_createdb) failed if one set The command now parses the redo log values correctly.
of redo logs span multiple file systems or ASM disk
groups.
The command fails to parse the redo log values from
virtual copy’s Oracle parameter file as it expects that
one set of redo logs would reside on one file system or
ASM disk group.
4
Bugs Fixed in Recovery Manager
... Este manual também é adequado para os modelos :
Software - HP 3PAR 10400 Application Software Suite for Oracle Media LTU (118.13 kb)
Software - HP 3PAR Application Software Suite for Oracle (118.13 kb)
Software - HP 3PAR StoreServ Application Suite for Oracle E-Media (118.13 kb)
Software - HP 3PAR StoreServ Application Suite for Oracle Media (118.13 kb)