Answer Posted / guest
Cause: In the INDEX BY clause of a PL/SQL table declaration,
a composite primary key was specified. PL/SQL tables must
have a simple, unnamed primary key of a binary integer or
VARCHAR2 type.
Action: Use one of the supported key types in the INDEX BY
clause.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
RMAN-05017: no copy of datafile number found to recover
NZE-28868: Peer certificate chain check failed.
ORA-16626: failed to enable specified object
ORA-16516: The current state is invalid for the attempted operation.
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26084: direct path context already finished
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-26029: index string.string partition string initially in unusable state
ORA-26032: index string.string loading aborted after string keys
NZE-28890: Entrust Login Failed
ORA-26027: unique index string.string partition string initially in unusable state
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-16627: No standby databases support the overall protection mode.
ORA-26030: index string.string had string partitions made unusable due to:
