Skip to Main Content
  • Questions
  • ORA-01115: IO error reading block from file 1 (block # 93463) ORA-01110: data file 1: '/ORADATA/DATA/system_01.dbf'

Breadcrumb

May 4th

Question and Answer

Chris Saxon

Thanks for the question, Vicente.

Asked: January 23, 2016 - 6:35 am UTC

Last updated: January 26, 2016 - 12:54 am UTC

Version: Oracle 9i (9.2.0.6.0)

Viewed 10K+ times! This question is

You Asked

Operating system AIX 5.2 64bits

Hello there.

I have tried to uninstall/install JAVAVM because I have obtain the following error when I was doing a full database export:

Connected to: Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.6.0 - Production Export done in US7ASCII character set and AL16UTF16 NCHAR character set

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions . exporting database links . exporting sequence numbers . exporting directory aliases . exporting context namespaces . exporting foreign function library names . exporting PUBLIC type synonyms
EXP-00008: ORACLE error 29516 encountered
ORA-29516: Aurora assertion failure: Assertion failure at joevm.c:3129 Unable to locate well known object: 22
EXP-00000: Export terminated unsuccessfully

Trying to uninstall/install the JAVAVM I have the following error:

DOC>#######################################################################
DOC>#######################################################################
DOC> The following statement may cause an
DOC> ORA-29554: unhandled Java out of memory condition
DOC> error, and thereby terminate the sqlplus connection.
DOC> If so, this is because there is insufficient system tablespace,
DOC> shared or java pool size, or some other resource value is too small.
DOC> An additional message describing the problem will be output by
DOC> the statement.
DOC>#######################################################################
DOC>#######################################################################
DOC>*/
SQL> execute initjvmaux.check_sizes_for_cjs;
alter system flush shared_pool
BEGIN initjvmaux.check_sizes_for_cjs; END;

*
ERROR at line 1:
ORA-01115: IO error reading block from file 1 (block # 93463)
ORA-01110: data file 1: '/ORADATA/DATA/system_01.dbf'
ORA-27091: skgfqio: unable to queue I/O
ORA-27072: skgfdisp: I/O error

BIG PROBLEEEEMMMMMMM

Then I have executed:
SELECT segment_name , segment_type , owner , tablespace_name
FROM sys.dba_extents
WHERE file_id = 1 AND 93463 BETWEEN block_id and block_id + blocks -1
/

To identify segment with bad block.

obtaining:

IDL_UB1$ TABLE SYS SYSTEM

Then run To fix use:
BEGIN
num_fix := 0;
DBMS_REPAIR.FIX_CORRUPT_BLOCKS (
SCHEMA_NAME => 'SYS',
OBJECT_NAME=> 'IDL_UB1$',
OBJECT_TYPE => dbms_repair.table_object,
REPAIR_TABLE_NAME => 'REPAIR_TABLE',
FIX_COUNT=> num_fix);
DBMS_OUTPUT.PUT_LINE('num fix: ' || TO_CHAR(num_fix));
END;
/

num_fix=0

But nothing.

I have changed the size of the file and nothing.

I have moved the majority of the objects from the system tablespace to another new one in different disk but I have still more objects couldn't move.

I'm in a complete dead end, please I need help desperately. I have a full export from the last Wednesday before I started to uninstall/intall JAVAVM.

Any suggestion what could I do Please.

Thank you so much.

Vinny.

and Connor said...

I think you're in a bad spot here. Looks to me like you've either got a corrupted system tablespace, or perhaps an underlying OS level I/O issue.

There will always be objects that cannot be moved from SYSTEM (because it holds all the dictionary tables). IDL_UB1$ is one of those tables.

This is table is used for PLSQL, so you could chat with Oracle Support - they can give you instructions on how to mark every object invalid and then recompile them, which might refresh those blocks. But often when you have 1 corrupt block...you've actually got many :-(

You probably also want to do a dbverify to check the whole database.

But dont lose that export from last week... you might need it !

Chat with Support before doing anything.

Rating

  (2 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

ORA-01115: IO error reading block from file 1 (block # 93463)

Vicente, January 25, 2016 - 11:29 am UTC

It wasn't a really useful answer telling me to go to Oracle support.
Connor McDonald
January 26, 2016 - 12:52 am UTC

It probably wasnt a useful step to charge ahead and try deinstall the JVM either, but we are where we are...

Um - you asked for help and got it?

Bill S., January 25, 2016 - 4:36 pm UTC

Telling you to work with support on this issue is actually the best answer these guys could give you.

See, you have a situation where you may have a corrupt file that contains your SYSTEM tablespace.

You really NEED to work with support on that, because this is exactly the reason why you PAY for support.

Take their advice - contact support at once.
Chris Saxon
January 26, 2016 - 12:54 am UTC

There is that urge to respond with a list of undocumented parameters to let the database *appear* to work fine whilst be corrupted beyond repair. Sometimes I wonder if people think thats the best option :-)

More to Explore

VLDB

If you are new to partitioning, check out Connor McDonald's introduction series here.

VLDB

Documentation set on VLDB and Partitioning.