PCC-02349: precision must be specified for this type
Answer Posted / guest
Cause: In a VAR or TYPE statement, certain Oracle types
require that the precision be specified. For example,
VARCHAR2 or CHAR.
Action: Indicate the precision.
Please add more information about this Error
|Is This Answer Correct ?||0 Yes||0 No|
ORA-26095: unprocessed stream data exists
ORA-26082: load of overlapping segments on table string.string is not allowed
IMP-00064: Definition of LOB was truncated by export
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
[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
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
IMP-00070: Lob definitions in dump file are inconsistent with database.
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?
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
NZE-28868: Peer certificate chain check failed.
ORA-16627: No standby databases support the overall protection mode.
ORA-26029: index string.string partition string initially in unusable state
ORA-26030: index string.string had string partitions made unusable due to:
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity