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
- 3289 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-16047: DGID mismatch between destination setting and standby
ORA-30151: File already exists
QSM-01049: semi-join check failed for materialized view, string
ORA-30568: cannot drop log group - nonexistent log group
ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.
SQL*Loader-00255: Log file for error recovery not used by SQL*Loader
ORA-15018: diskgroup cannot be created
ORA-26017: global indexes not allowed for direct path load of table partition string
KUP-04038: internal error: string
ORA-38705: Expected block size string does not match string in log header.
RMAN-20298: DBMS_RCVCAT package not compatible with the recovery catalog
ORA-02315: incorrect number of arguments for default constructor
Oracle Errors 
