HP 3PAR Application Software Suite for Oracle - Manual (Page 212)

The LVM pvremove command, which is used to remove LVM physical volumes from a snapshot
volume group, has failed.
SOLUTION
See the preceding error message to determine the cause of failure.
MESSAGE ID
1320
MESSAGE
3PAR1320: ERROR: Could not remove LVM volume group <group>.
REASON
The LVM vgremove command, which is used to remove a snapshot volume group, has failed.
SOLUTION
See the preceding error message to determine the cause of failure.
MESSAGE ID
1331
SYMBOLIC NAME
RMO_ERROR_ORPHANED_VC
MESSAGE
3PAR1331: ERROR: The virtual volumes of Virtual Copy '%s' no longer belong to the current
database virtual volumes.
REASON
The Virtual Copy is orphaned because its parent volumes have been converted to THIN volumes
or FAT volumes.
SOLUTION
A database virtual copy can only be used to promote to its original parent virtual volumes. Since
one or more virtual volumes of the specified Virtual Copy no longer belong to the current database
virtual volumes, possibly because of FAT-to-THIN or THIN-to-FAT conversion, they cannot be used
to promote to the current database virtual volumes.
MESSAGE ID
1339
SYMBOLIC NAME
RMO_ERROR_STALED_VC
MESSAGE
3PAR1339: ERROR: One or more virtual volumes of Virtual Copy '%s' are stale.
REASON
A Virtual Copy becomes stale when snapshot space is running out.
SOLUTION
A stale Virtual Copy is no longer an application consistent copy of the database possibly due to
snapshot space running out, and it cannot be used to promote to the current database virtual
volumes.
MESSAGE ID
1341
SYMBOLIC NAME
RMO_ERROR_RETRIEVE_POLICY_CLIENT
212 Troubleshooting