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

---

...

Dieses Handbuch ist für folgende Modelle:
Software - HP 3PAR StoreServ Application Suite for Oracle Media (114.61 kb)
Media Storage - HP 3PAR 7450 Application Software Suite Oracle Media LTU (114.61 kb)
Media Storage - HP 3PAR 10400 Application Software Suite for Oracle Media LTU (114.61 kb)
Media Storage - HP 3PAR Application Software Suite for Oracle (114.61 kb)