Answer / guest

Cause: The Data Guard broker determined that an instance has
successfully found its database profile within the broker
configuration file, but yet lacks an instance-specific
profile. The broker automatically creates an
instance-specific profile and associates the instance with
its database profile.

Action: No user action is required. The broker will
automatically associate the instance with its database
profile and incorporate the instance in broker activity.

Please add more information about this Error

ORA-12923: tablespace string is in force logging mode

1 Answers  

---

ORA-14316: table is not partitioned by List method

1 Answers  

---

ORA-36774: (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.

1 Answers  

---

DRG-50939: parser not set

1 Answers  

---

ORA-28665: table and partition must have same compression attribute

1 Answers  

---

ORA-26097: unsupported conversion for column string (from type number to type number)

1 Answers  

---

ORA-16801: Some log transport related property is inconsistent.

1 Answers  

---

ORA-30088: datetime/interval precision is out of range

1 Answers  

---

ORA-30002: SYS_CONNECT_BY_PATH function is not allowed here

1 Answers  

---

QSM-02135: agg(expr) requires correspondng AVG(expr) function

1 Answers  

---

ORA-02160: index-organized table can not contain columns of type LONG

1 Answers  

---

RMAN-06733: database unregistered from the recovery catalog

2 Answers  

---