Answer / guest

Cause: When one resyncs an object that is dimensioned by a
composite dimension, the composite dimension is resynced
automatically, dropping all new tuples. This cannot be done,
however, if the automatic resync of the composite dimension
might cause data in an object that shares the composite
dimension to become NA.

Action: Resync both objects together. ALternatively, you can
try to acquire the other object (that will ensure that the
composite dimension is locked in the latest generation and
will not be resynced when resyncning the first object),
resync the first object, and release the other object.

Please add more information about this Error

ORA-10647: Tablespace other than SYSTEM, string, string not found in read only mode

1 Answers  

---

ORA-25959: join index must be of the bitmap type

1 Answers  

---

UDI-00003: all allowable logon attempts failed

1 Answers  

---

NNL-00529: set|show default_domain [<domain_name>] : set|show the current default domain

1 Answers  

---

ORA-01639: instance string has no thread assigned to it

1 Answers  

---

ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires

1 Answers  

---

PCC-02446: FOR clause not allowed in a DEALLOCATE statement

1 Answers  

---

ORA-12704: character set mismatch

1 Answers  

---

ORA-16571: Data Guard configuration file creation failure

1 Answers  

---

ORA-02183: valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }

1 Answers  

---

PCC-02427: Expression is not of the correct character string type

1 Answers  

---

ORA-30682: improper value for argument OPTION_FLAGS

1 Answers  

---