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
- 3343 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-16199: Terminal recovery failed to recover to a consistent point
RMAN-06512: copy will be obsolete on date string
ORA-09241: smsalo: error allocating SGA memory
ORA-38700: Limit of string flashback database logs has been exceeded.
IMP-00033: Warning: Table "string" not found in export file
SQL*Loader-00602: Maximum converted length number of column string is too big for bind array
ORA-21615: copy of an OTS (named or simple) instance failed
RMAN-06412: no proxy copy channel found
ORA-06119: NETTCP: spurious client request
NZE-29137: The global context is incorrect.
PCC-00068: Host and indicator variables may not have the same name.
ORA-28539: gateway does not support result sets
Oracle Errors 
