HP 3PAR Recovery Manager 4.5.0 Software for Oracle Release Notes

SolutionDescriptionBug ID
warning message will be displayed if such change will
be made.
Fixed. To correctly retrieve the file systems used by a
database regardless of the parameter is a directory or
a file name prefix.
RMO: Support archive log destination containing a file
name prefix.
If og_archive_dest_nl parameter is a file instead of
an existing directory, Oracle treats the file as prefix for
94061
archive log file names. The CLI commands
rmora_create or rmora_rsync fails.
Fixed. This displays the correct space usage.RMO4.4: GUI does not display space information
correctly for large volumes.
94302
This is caused by integer overflow when calculating the
space usage.
Fixed. This returns the correct mount point.RMO: rmora_discdev retrieved wrong file system
mount points in some cases.
94357
Trying to retrieve the longer matching mount point returns
incorrect result.
Fixed. Some non-3PAR devices can have a much longer
vv WWN names. Fixed to check the length after
retrieval.
RMO: Memory fault when retrieved device WWN is
longer than defined value MAX_VVWWN_LEN.
94360
Fixed. This helps to change rmora_checkconfig to
ensure the same Oracle user and group exists on the
RMO: rmora_mount fails if no Oracle home on backup
server is provided during configuration.
94637
backup server, even if there is no Oracle home on the
backup server.
This is because the owner and group mismatch occurs
between database server and the backup server.
For file system configurations, rmora_mount should
run successfully even without the Oracle home on the
backup server.
Fixed. This helps to remove only the snapshots generated
by Recovery Manager for Oracle.
RMO: Umount snapshot fails, as there is an attempt to
delete the exported vv snapshot created by VSS.
95630
The rmora_umount operation fails, as it tries to
remove the snapshots created by other Recovery
Manager applications with the same timestamp.
Fixed. This sorts the physical device uniquely before
performing volume rollback.
RMO: rmora_rollback error 3PAR1047: ERROR:
Could not initiate rollback process for
Virtual Copy volume xxx.
97635
This occurs when two or more logical volumes contains
the same physical device.
Fixed. This ensures to keep the correct executable
permission.
RMO: Permissions changing after edit task in RMO GUI.
After modifying an existing task, the script generated
for the new task misses executable permission which
prevents cron job to start correctly.
98072
Fixed to display the original set time.RMOGUI: Hour field in Start Time always shows "00"
in view details and Edit task screen irrespective of time
set.
98281
Fixed to parse the redo log group name correctly.RMO: rmora_createdb fails when redo log disk
group has the word group in the name.
99615
The word group was used as a matching keyword when
parsing redo log files.
4 Bugs Fixed in Recovery Manager