ORA-29855: error occurred in the execution of
ODCIINDEXCREATE routine
- 1 Answers
- 6758 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: Failed to successfully execute the ODCIIndexCreate
routine.
Action: Check to see if the routine has been coded correctly.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 8 No |
Post New Answer View All Answers
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
NZE-28890: Entrust Login Failed
NZE-28868: Peer certificate chain check failed.
ORA-26027: unique index string.string partition string initially in unusable state
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-16626: failed to enable specified object
RMAN-05017: no copy of datafile number found to recover
ORA-16516: The current state is invalid for the attempted operation.
Hi guys, I have four tables those are emp,dept,eliminate and uneliminate. i wrote small cursor..when i run, it display one error (ORA-01403 nodata found)... The query is: Declare cursor c1 is select e.ename emp_name from emp e,dept d where e.deptno=d.deptno group by deptno; r1 c1%rowtype; test_emp varchar2(200); begin for r1 in c1 loop begin select eliminate_emp into test_emp from eliminate t,uneliminate ut where t.number=ut.number and t.deptno=e.deptno and rownum<1; end; dbms_output.put_line(r1.emp_name); end loop; end; Thanks...
ORA-26032: index string.string loading aborted after string keys
ORA-26030: index string.string had string partitions made unusable due to:
ORA-16627: No standby databases support the overall protection mode.
ORA-26029: index string.string partition string initially in unusable state
