ORA-02322: failure in accessing storage table of the nested
table column
Answer Posted / guest
Cause: An error occured while performing DML on the storage
table of the nested table column.
Action: If the situation described in the following messages
can be corrected, do so; otherwise contact Oracle Support.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-26084: direct path context already finished
ORA-26079: file "string" is not part of table string.string
IMP-00070: Lob definitions in dump file are inconsistent with database.
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-16516: The current state is invalid for the attempted operation.
ORA-16626: failed to enable specified object
RMAN-05017: no copy of datafile number found to recover
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26029: index string.string partition string initially in unusable state
[ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) Unsuccessful: alter table user.CEN_USER_MASTER add constraint FKF4EDEDC3D0BAAE75 foreign key (ROLE_ID) references user.CEN_ROLE_MASTER [ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) ORA-02275: such a referential constraint already exists in the table