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
- 3436 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-00301: error in adding log file 'string' - file cannot be created
ORA-06700: TLI Driver: incorrect message type from host
LPX-00227: entity "~S" is not a parsed entity
ORA-13413: null or invalid resampling parameter
ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
ORA-34360: (MXDSS15) number other users writing
ORA-00214: controlfile 'string' version string inconsistent with file 'string' version string
TNS-01414: "string", state string, established string, refused string, current string, max string
LFI-01007: Line is too long; encountered in function string.
ORA-12230: TNS:Severe Network error occurred in making this connection
ORA-31027: Path name or handle string does not point to a resource
ORA-01478: array bind may not include any LONG columns
Oracle Errors 
