ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be
resynced without modified object workspace object because
they share a modified composite dimension.
- 1 Answers
- 2718 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 |
NID-00400: DBNEWID - Completed with errors.
ORA-21526: initialization failed
RMAN-12000: execution layer initialization failed
TNS-01181: Internal registration connection limit reached
ORA-31091: empty string specified as a SQL name
ORA-06710: TLI Driver: send interrupt break message failed
ORA-01592: error converting Version 7 rollback segment (string) to Oracle 8 format
ORA-02750: osnfsmmap: cannot open shared memory file ?/dbs/ftt_<pid>.dbf
NZE-29193: no CRL found using CRLDP mechanism
O2I-00121: No value was specified for the CODE option
ORA-13349: polygon boundary crosses itself
ORA-03291: Invalid truncate option - missing STORAGE keyword
Oracle Errors 
