HP 3PAR Recovery Manager 4.5.0 Software for Oracle Release Notes

Known Issues with Recovery Manager
WorkaroundDescriptionItem
In AIX, 32 bit applications can access only one segment
(256 MB) of program data by default. Increase the
Command rmora_display, may result in core dump
on AIX OS due to insufficient memory.
77953
amount of memory to 1.25GB (5 segments of 256 MB)
or appropriate value.
export LDR_CNTRL=MAXDATA=0x50000000
Add this entry in /etc/environment file to make this
setting parameter.
Move the Recovery Catalog to a server other than the
database server, and update the TNS service name for
the Recovery Catalog accordingly to reflect the change.
Oracle RMAN backup with HP Data Protector fails with
error "Backup of recovery catalog failed".
This occurs when the Oracle Recovery Catalog is
running on the same database server.
83976
It is possible that the /opt file system may not have
enough space. Increase the FSspace using appropriate
OS command.
The rmora_install.sh script does not check if
rpm/swinstall/pkgadd/installp fails due to
insufficient disk space.
84246
Approximate Disk Space requirements to install RMO:
• AIX : 320 MB
• Solaris: 280 MB
• RHEL : 270 MB
• HP-UX : 620 MB
Enter Abort at the OMNIB Command Mode prompt to
abort the backup and then allocate more disk space
If there is insufficient disk space for performing an HP
DP (Data Protector) backup when invoking
86537
before invoking rmora_backup again to attempt another
backup.
rmora_backup, a response to the following DP menu
prompt is required in order for the rmora_backup
command to complete:
or
OMNIB Command Mode ====================
Available are the following commands Abort - aborts
First allocate more disk space for the backup device and
then enter the Mount command as follows at the OMNIB
Command Mode prompt:
the session and all related actions Cancel <device> -
cancels the device and all Disk Agents working with the
Command:>Mount RMOBackup_Writer0
NOTE: Do not enter Disconnect at the Command
prompt; otherwise, RMO will not automatically remove
the cloned Database and unmount the corresponding
Virtual Copy, and the rmora_removedb and
rmora_umount commands will have to be manually
invoked before invoking rmora_backup again to
attempt another backup.
specified device Mount - informs the Session Manager
that a mount request has been satisfied Disconnect -
disconnects from the Session Manager Continue -
cancels command mode and enters monitor mode
Command:>
Use the HP Data Protector GUI to abort the backup
session. In the DP GUIs select Context List→Monitor
right-click the session and select Abort.
If there is insufficient disk space for performing an HP
DP (Data Protector) backup when the backup is initiated
from the RMO GUI, the RMO GUI will hang indefinitely.
86537
If the Configuration is built using GPFS on AIX or OCFS2
on Linux, then the RMO backup server must be
RMO operations will fail, if GPFS on AIX and OCFS2
on Linux is not installed and configured as a single node
cluster on the backup server.
88174
configured as a single node cluster to perform RMO
operations.
User has to rename the existing Logical Volume Group
or Logical Volume Name on the backup server and retry
mounting the virtual copy.
On AIX, mounting a virtual copy fails if duplicate Logical
Volume Group or Logical Volume names are found on
the backup server.
85782
To overcome this issue, user has to explicitly unmount
the Virtual Copy by issuing rmora_umount command
RMO44: cleanup does not happen when media backup
failed due to insufficient disk space.
If the NBU Storage Unit is 100% full and a user issues
rmora_backup command then the backup will fail and
93010
and remove the lock file .backup.lock in /etc/
Known Issues with Recovery Manager 5