Errors ORA-01115 ORA-17507 ORA-01410

Question

Hi i was using Oracle Data Integrator for loading data from one database to another, i programmed a package that loads data with a cycle in monthly intervals, it rans ok the first ten months since 2007/11 but then i got this errors
java.sql.SQLException: ORA-01115: IO error reading block from file 286 (block # 184745)
ORA-17507: I/O request size is not a multiple of logical block size
ORA-01410: invalid ROWID
Does anyone have any idea why this happened?.

Answer 1

oracle error ORA-01115
1. Try to assess the cause and extent of the problem.
Examine the alert.log file for this instance. Scan the last few
days' entries for other occurrences of ORA-01115. If you find them,
A) Do they reference files in different disks?
If so, it is likely that there you have controller problems.
Move on to Scenario II.A below.
B) Do they reference different files in the same disk?
If so, it is likely that there are problems with that disk.
Move on to Scenario II.B below.
C) Do they always reference the same datafile?
If so, it is likely that the datafile contains bad blocks.
Move on to Scenario II.C below. If the file is bigger
than 2GB and you are running 7.1.4 or lower on a Solaris
platform, see Scenario II.D below.
D) If none of the above applies, move on to Step 2.
2. If the datafile is in the SYSTEM tablespace, or the database is in
NOARCHIVELOG mode, shut the database down. Move on to Step 4.
If shutdown immediate fails, do a shutdown abort.
3. If the database is in ARCHIVELOG mode, you should still shut the
database down. If the database cannot be shut down, offline the
datafile.
ALTER DATABASE DATAFILE '<full_path_file_name>' OFFLINE;
4. Try to copy the datafile to another disk (managed by a different
controller, if possible).
5. If the copy fails, even after you retry, the datafile must be considered
lost at this point. The next action depends on the tablespace to
which the lost file belongs. See the following Solution References to
PR entries, according to the different types of tablespaces,
for instructions on how to proceed.
IMPORTANT: While going through the references below, keep in mind that
if you restore the datafile from backup, you need to place it in another
disk, preferably under a different controller, and rename it inside Oracle
(see Note 115424.1 for details). If you recreate any tablespace, make
sure its datafiles are created in another disk, preferably under a
different controller.
Reference for Lost datafile scenarios : Note 198640.1
6. If the database is down, mount it.
7. Rename the datafile that you succeeded in copying inside Oracle.
ALTER DATABASE RENAME FILE '<old_full_path_file_name>'
TO '<new_full_path_file_name>';
8. If the database is mounted, open it. If you offlined the datafile,
perform media recovery on it, and then bring it online.
RECOVER DATAFILE '<full_path_file_name>';
ALTER DATABASE DATAFILE '<full_path_file_name>' ONLINE;