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-12220: a valid tag must be provided

1 Answers  

---

DRG-12016: The target document for this operation has moved - continue?

1 Answers  

---

ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table

1 Answers  

---

ORA-24032: object string exists, index could not be created for queue table string

1 Answers  

---

NNO-00705: warning: cannot open checkpoint file "string", checkpointing disabled

1 Answers  

---

ORA-12491: DBHIGH value does not dominate DBLOW

1 Answers  

---

ORA-38727: FLASHBACK DATABASE requires a current control file.

1 Answers  

---

TNS-00220: Pump Breakdown --------------

1 Answers  

---

ORA-31079: unable to resolve reference to string "string"

1 Answers  

---

ORA-27038: created file already exists

1 Answers  

---

ORA-01743: only pure functions can be indexed

1 Answers  

---

LRM-00111: no closing quote for value 'string'

1 Answers  

---