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
- 3537 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 |
NID-00137: All datafiles that are not dropped should be readable
ORA-07480: snchmod: cannot change permissions on ?/dbs/sgalm.dbf.
ORA-14116: partition bound of partition "string" is too long
PLS-01454: No operator may be used with values of data type CHAR
ORA-23336: priority group string does not exist
PLS-01702: Illegal syntax in COMMIT WORK statement
ORA-28174: Kerberos ticket not provided by proxy
PLS-01418: Subquery cannot include set operators in ANSI's grammar
ORA-13611: The command string is not a valid advisor command.
ORA-38485: invalid object type for the user-defined function
DRG-50907: score threshold string outside valid range 1 to 100
QSM-02150: select lists must be identical across the UNION operator
Oracle Errors 
