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
- 3366 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 |
IMG-00502: invalid scale value
ORA-22328: object "string"."string" has errors. string
ORA-34359: (MXDSS11) string appears twice in the alias list.
RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION
ORA-09923: Can't spawn process - user log directory not created properly
ORA-12441: policy string already exists
PCC-02210: C++ punctuation sequences are not permitted
DRG-10826: no document with the specified textkey is found
EXP-00037: Export views not compatible with database version
NZE-28819: No distinguished name provided.
PLS-00371: at most one declaration for 'string' is permitted in the declaration section
ORA-08315: sllfrb: Error reading file
Oracle Errors 
