Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be
resynced without modified object workspace object because
they share a modified composite dimension.
- 1 Answers
- 3440 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-22996: NEXT extent size is smaller than LOB chunksize
ORA-01195: online backup of file string needs more recovery to be consistent
PLS-00150: found: string but expected : INTEGER
NPL-00303: uninitialized ASN.1 class attribute
ORA-01340: NLS error
ORA-22311: type for attribute "string" does not exist
ORA-03242: Tablespace migration retried 500 times
ORA-38409: invalid name or option for the attribute set: string
ORA-27548: Unable to unprepare IPC buffer
ORA-14257: cannot move partition other than a Range or Hash partition
NID-00308: Control File string - dbid changed
IMG-00922: location specified without feature
Oracle Errors 
