ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be
resynced without modified object workspace object because
they share a modified composite dimension.
- 1 Answers
- 2978 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-06909: CMX: error during acknowledge of ORACLE_SID
IMG-00806: invalid input image
ORA-00163: internal database name length string is greater than maximum (string)
LPX-00224: multiple occurrences of attribute "~S" found
ORA-38771: unnamed datafile(s) added to controlfile by flashback recovery
ORA-24758: not attached to the requested transaction
PLS-00424: RPC defaults cannot include Package State
PLS-00536: Navigation through REF variables is not supported in PL/SQL.
ORA-24307: invalid length for piece
PCC-01003: Invalid continuation at line number in file string
ORA-12845: failed to receive interinstance parallel execution message
PCC-02394: Input file name and output filename are identical
Oracle Errors 
