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

DRG-10702: cannot create or modify preference in another user's schema

1 Answers  

---

ORA-24060: cannot convert QUEUE_TABLE, string already is compatible with release string

1 Answers  

---

ORA-25220: enqueue failed, signature not specified for a non-repudiable queue

1 Answers  

---

ORA-32577: username must be SYS or SYSTEM

1 Answers  

---

ORA-14013: duplicate partition name

1 Answers  

---

---

DRG-50904: weight string outside valid range 0.1 to 10.0

1 Answers  

---

NNO-00631: warning: forwarder number has invalid name "string", forwarder ignored

1 Answers  

---

LPX-00256: invalid element declaration

1 Answers  

---

SQL*Loader-00433: no attributes found for column object string in table string

1 Answers  

---

ORA-30158: The OCIFileWrite causes the file to exceed the maximum allowed size

1 Answers  

---

ORA-14288: index is not partitioned by Composite Range method

1 Answers  

---

ORA-25455: evaluation error for rule set: string.string, evaluation context: string.string

1 Answers  

---