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
- 3361 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 |
LFI-01519: llseek() failed(OSD return value = string) in string.
ORA-02456: The HASH IS column specification must be NUMBER(*,0)
KUP-04075: no read access to directory object string
ORA-12675: External user name not available yet
ORA-07492: scgrcl: cannot close lock.
ORA-31089: schema "string" does not target namespace "string"
ORA-02801: Operations timed out
AMD-00134: measure #string: RDBMS measure column name not specified
ORA-16796: One or more properties could not be imported from the database.
NNL-00546: Displays delete request statistics
RMAN-20005: target database name is ambiguous
PLS-00500: invalid operator binding
Oracle Errors 
