Answer / guest

Cause: When one resyncs an object that is dimensioned by a
dimension map, the dimension map is resynced automatically,
dropping all changes. This cannot be done, however, if the
automatic resync of the dimension map might cause data in an
object that shares the dimension map to become NA.

Action: Resync both objects together. ALternatively, you can
try to acquire the other object (that will ensure that the
dimensions map 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

SQL*Loader-00468: OID directive expects 1 argument, number found.

1 Answers  

---

ORA-15150: instance lock mode 'string' conflicts with other ASM instance(s)

1 Answers  

---

ORA-09822: Translation of audit file name failed.

1 Answers  

---

ORA-30365: left relation in the JOIN KEY clause cannot be same as right

1 Answers  

---

ORA-26669: parameter string inconsistent with parameter string

1 Answers  

---

---

ORA-13300: single point transform error

1 Answers  

---

ORA-29557: Java system class string cannot be modified

1 Answers  

---

ORA-16586: Could not edit database property through instance.

1 Answers  

---

ORA-29534: referenced object string.string could not be resolved

1 Answers  

---

ORA-00340: IO error processing online log string of thread string

2 Answers   ABC,

---

AMD-00122: dimension #string: analytic workspace hierarchy dimension not specified

1 Answers  

---

ORA-26031: index maintenance error, the load cannot continue

1 Answers  

---