Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-34243: (MXDCL11) You can only use the string keyword
when defining a COMPOSITE.
- 1 Answers
- 3586 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: User supplied the COMPRESSED keyword when defining an
object that was not a COMPOSITE.
Action: If the intent is to create a compressed composite,
make sure that the object type is COMPOSITE. Otherwise,
remove the COMPRESSED keyword from the command string and rerun.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-14195: ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object
PLS-01714: ANSI expects a column name not a literal value here
ORA-06123: NETTCP: cannot set KEEPALIVE
LPX-00604: Invalid attribute value '~1S', for attribute '~2s'.
ORA-24099: operation not allowed for 8.0 compatible queues
ORA-31209: DBMS_LDAP: PL/SQL - LDAP count_entry error.
ORA-15133: instance recovery required for diskgroup string
ORA-00222: operation would reuse name of a currently mounted controlfile
RMAN-06187: controlfile copy string not found or out of sync with catalog
ORA-22060: argument [string] is an invalid or uninitialized number
ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
ORA-07685: sou2os: supervisor stack set error
Oracle Errors 
