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

TNS-01097: TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE

1 Answers  

---

PLS-00543: a PLSQL Table may not contain a nested table type or VARRAY.

1 Answers  

---

PCC-02154: Close file: string

1 Answers  

---

LRM-00102: 'string' is not in the legal range for 'string'

1 Answers  

---

ORA-12046: cannot use trusted constraints for refreshing remote MV

1 Answers  

---

ORA-04087: cannot change the value of ROWID reference variable

1 Answers  

---

ORA-07570: szrfc: $IDTOASC failure

1 Answers  

---

NNL-00891: Corrupted messages received: number

1 Answers  

---

NCR-01013: NCRS: Unvalid connection type.

1 Answers  

---

ORA-01370: Specified restart SCN is too old

1 Answers  

---

ORA-01563: rollback segment is PUBLIC, need to use the keyword PUBLIC

1 Answers  

---

RMAN-08550: autobackup search outside recovery area not attempted because DBID was not set

1 Answers  

---