Answer / guest
Cause: A proxy copy was started, but no allocated channel
supports proxy copy. This could be because the media
management software used by the target database does not
support proxy copy, or because all of the allocated channels
are of type DISK, which never support proxy copy.
Action: If this is a backup, then either allocate a non-disk
channel, or do not use the PROXY option. If this is a
restore, then a channel of the same type which created the
proxy backup was allocated, but now does not support proxy
copy. If proxy copy is no longer supported by the media
management software at the target database, the CROSSCHECK
or CHANGE commands should be used so that those backups will
not be considered for further restores.
Please add more information about this Error
|Is This Answer Correct ?||0 Yes||0 No|
PROC-00015: Failed to initialize the cluster registry successfully
ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.
ORA-12153: TNS:not connected
ORA-23365: site string does not exist
ORA-23358: invalid remote user
RMAN-08010: channel string: specifying datafile(s) in backupset
ORA-01194: file string needs more recovery to be consistent
ORA-22328: object "string"."string" has errors. string
ORA-22903: MULTISET expression not allowed
ORA-13213: failed to generate spatial index for window object
ORA-28271: No permission to read user entry in LDAP directory service.
ORA-13186: fixed tile size tessellation failed