ORA-01188: Block size string in header does not match
physical block size string
- 1 Answers
- 2154 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: A log file member given to CREATE CONTROLFILE is on a
physical device that has a different block size than the
device originally used to create the log.
Action: Move the file to a device with the correct block
size or use the RESETLOGS option to CREATE CONTROLFILE.
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.
ORA-16516: The current state is invalid for the attempted operation.
ORA-26084: direct path context already finished
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26095: unprocessed stream data exists
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-16626: failed to enable specified object
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...
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-26094: stream format error: input column overflow
ORA-26032: index string.string loading aborted after string keys
ORA-26027: unique index string.string partition string initially in unusable state
NZE-28890: Entrust Login Failed
ORA-26029: index string.string partition string initially in unusable state
ORA-26082: load of overlapping segments on table string.string is not allowed
