Answer / guest

Cause: The DB_UNIQUE_NAME attribute is required when
DG_CONFIG is enabled.

Action: Use the DB_UNIQUE_NAME attribute to specify a valid
Data Guard Name for the destination. The list of valid
DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.

Please add more information about this Error

ORA-14284: one or more of table's subpartitions reside in a read-only tablespace

1 Answers  

---

ORA-16123: transaction string string string is waiting for commit approval

1 Answers  

---

ORA-19715: invalid format string for generated name

1 Answers  

---

PLS-00491: numeric literal required

1 Answers  

---

ORA-27045: unable to close the file

1 Answers   Aomi,

---

ORA-02814: Unable to get shared memory

1 Answers  

---

ORA-16212: number processes specified for APPLY is too great

1 Answers  

---

AMD-00101: cannot create string "string"; metadata entity already exists

1 Answers  

---

QSM-01073: materialized view, string, has a join not found in query

1 Answers  

---

ORA-29382: validation of pending area failed

1 Answers  

---

ORA-23490: extension request "string" with status "string" not allowed in this operation

1 Answers  

---

ORA-15068: maximum number of diskgroups string already mounted

1 Answers  

---