Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-14403: cursor invalidation detected after getting DML
partition lock
- 1 Answers
- 7669 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: cursor invalidation was detected after acquiring a
partition lock during an INSERT, UPDATE, DELETE statement.
This error is never returned to user, because is caught in
opiexe() and the DML statement is retried.
Action: nothing to be done, error should never be returned
to user
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 3 No |
SQL*Loader-00254: Cannot have DISCARDFILE specs here when multiple data files
PLS-01401: Identifier over 18 characters long
ORA-12221: TNS:illegal ADDRESS parameters
DRG-10504: primary key is required when using the DETAIL_DATASTORE
ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
ORA-02091: transaction rolled back
ORA-30087: Adding two datetime values is not allowed
ORA-34021: (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
ORA-02848: Asynchronous I/O package is not running
ORA-00603: ORACLE server session terminated by fatal error
ORA-16179: incremental changes to "string" not allowed with SPFILE
PLS-00374: illegal EXIT statement; it must appear inside the loop labeled 'string'
Oracle Errors 
