Answer / guest

Cause: An attempt was made to specify a VARRAY|OPAQUE column
to be stored as LOB at the partition/subpartition/template
level. However the VARRAY|OPAQUE column was not specified to
be stored as LOB at the table level when the table was created.

Action: Specify the VARRAY | OPAQUE column to be stored as
LOB at the table level when the table is created.
Alternatively, do not specify the VARRAY | OPAQUE column to
be stored as LOB at the partition/subpartition/template
level if it is not specified at the table level when the
table is created.

Please add more information about this Error

ORA-08341: On nCUBE, this command can only be executed from instance 1.

1 Answers  

---

RMAN-08052: cataloged controlfile copy

1 Answers  

---

RMAN-06002: command not allowed when not connected to a recovery catalog

1 Answers  

---

RMAN-06083: error when loading stored script string

1 Answers  

---

ORA-09793: szguns: length of user name is greater than buffer.

1 Answers  

---

ORA-00911: invalid character

1 Answers  

---

NNO-00253: administrative region parameter string length string exceeds maximum of string

1 Answers  

---

ORA-30647: error retrieving access parameters for external table string.string

1 Answers  

---

ORA-02159: installed DLM does not support releasable locking mode

1 Answers  

---

ORA-38955: Source platform string not cross platform compliant

1 Answers  

---

AMD-00153: error detaching workspace "string"

1 Answers  

---

SQL*Loader-00562: record too big

1 Answers  

---