This content has been marked as final. Show 6 replies
ORA-01114: IO error writing block to file string (block # string)
Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.
Action: Restore access to the device or remove unnecessary files to free up space.
So, did you take a look at v$tempfile dynamic performance view?
yes i did
SQL> select file# from v$tempfile;
In which O/S Oracle has been installed? Have you already take a look at alert log file and/or correspondent trace files in order to get more information?
If the value of your init.ora parameter "db_files" is 200 then file#201 is actually
the first tempfile . You would not see it in v$datafile (dba_data_files) but v$tempfile.
It is most likely that the filesystem holding your tempfile is full .
For example if the filesystem is something like a NetApp filer which keeps blocks
for snapshot space, it prevents further writes when it is 100% full as it is no longer
able to maintain updated blocks.
thank you all
it is actually the first tempfile (the init file db_files parameter is 200)
I got the same error after migrating the db from EMC to NetApp.
My error complains about file# 1026. And, the max file# is 1024. So, does it refer to the second temp file of the temporary tablespace? But, there is only 1 temp file in NetApp.
When the database originally located in the EMC disk storage, there was 24G of temporary tablespace, spread between 4 temp files. After migrating to NetApp, the temporary tablespace has been changed from 24G to 4 G in size, with only 1 temp file associated with it. This has been verified with v$tempfile. So, how come Oracle reports error on file#1026?
thanks in advance