Answer Posted / guest
Cause: The polynomialModel specification had an incorrect
pType value.
Action: Check the documentation for supported polynomial types.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-16627: No standby databases support the overall protection mode.
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26028: index string.string initially in unusable state
NZE-28890: Entrust Login Failed
ORA-26032: index string.string loading aborted after string keys
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-16626: failed to enable specified object
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26076: cannot set or reset value after direct path structure is allocated
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?
ORA-26027: unique index string.string partition string initially in unusable state
RMAN-05017: no copy of datafile number found to recover
IMG-02003: 2FF03 - incorrect color histogram feature specification
