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

NCR-03018: NCRO: Failed to make RSLV connection

1 Answers  

---

ORA-01948: identifier's name length (string) exceeds maximum (string)

1 Answers  

---

ORA-29503: SCHEMA keyword not valid with NAMED keyword

1 Answers  

---

ORA-29964: missing ADD or DROP keyword

1 Answers  

---

IMG-02007: 2FF07 - positional color feature cannot be determined

1 Answers  

---

ORA-30732: table contains no user-visible columns

1 Answers  

---

ORA-01945: DEFAULT ROLE[S] already specified

1 Answers  

---

ORA-36712: (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.

1 Answers  

---

QSM-01069: summary join graph for, string, does not have table, string

1 Answers  

---

QSM-01123: self-join algorithm could not resolve multiple instances

1 Answers  

---

ORA-13216: failed to update spatial index

1 Answers  

---

PROC-00031: Storage device for the cluster registry is too small

1 Answers  

---