when i start
dbv FILE=/dbaS1/oradata/NTEL/system01.dbf BLOCKSIZE=4096
on my online-db i get the error-message:
DBV-00102: File I/O error on FILE
/dbaS1/oradata/NTEL/system01.dbf) during end read operation (-1)
when i start in on my backup-file, i get the same message.
what can i do ?
thnaks
marcus
--
Posted via http://dbforums.com
You can do the following :
1) Provide us with O/S platform and Oracle Version. That's simple necessity. Always.
2) Tell if your database has ever been migrated from 7.x to 8.x.
3) Tell if 'dbaS1/oradata/NTEL/system01.dbf' is > 2Gb.
4) Run dbv on another datafile of the DB and give result here.
- Kenneth Koenraadt
mkoster <mem...@dbforums.com> wrote in message news:<2320582.1...@dbforums.com>...
Hi Marcus,
You can do the following :
1) Provide us with O/S platform and Oracle Version. That's simple
necessity. Always.
unix aix 4.3.3 oracle 8.1.7
2) Tell if your database has ever been migrated from 7.x to 8.x.
no
3) Tell if 'dbaS1/oradata/NTEL/system01.dbf' is > 2Gb.
no, 500 MB
4) Run dbv on another datafile of the DB and give result here.
all other datafile give result
thanks
Hi Marcus,
"all other datafile give result".....do you mean that they give
dbv-00102 or no error ?!
- Kenneth Koenraadt
>>>>>
example:
DBVERIFY: Release 8.1.7.0.0 - Production on Fri Dec 27 11:40:41 2002
(c) Copyright 2000 Oracle Corporation. All rights reserved.
DBVERIFY - Verification starting : FILE =
/dbaU1/oradata/NTEL/ts_users04.dbf
DBVERIFY - Verification complete
Total Pages Examined : 256000
Total Pages Processed (Data) : 1166
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 65
Total Pages Failing (Index): 0
Total Pages Processed (Other): 2
Total Pages Empty : 254767
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Then the question is whether
a) Your SYSTEM tablespace datafile is really corrupt OR
b) Something is wrong with dbv.
To check a) you can do the following :
1) View the alert log for info.
2) execute "analyze table <table-name> validate structure cascade"
for all
tables in SYSTEM tablespace. That will show if any (used) blocks
are
corrupt.
3) Make a full export of the DB. If it completes succesfully, you
can save
your DB this way, because then the (possible) damaged blocks
were not in
use.
Regarding b), I have no other idea than dbv is known not to work on
raw devices on some platforms.
- Kenneth Koenraadt
mkoster <mem...@dbforums.com> wrote in message news:<2326186.1...@dbforums.com>...
after i increases the tablespace dbv give no error.
who can explain that ???
plov...@mail-online.dk (Kenneth Koenraadt) wrote in message news:<25fb645f.02122...@posting.google.com>...
I ran into this same error doing a dbv.
I re-run it on the datafile and again got the IO error.
Same AIX and Oracle version to yours.
I then used the 'alter database...resize' command but did not
increase/decrease the datafile. I set it to exactly the same size it was
previously.
Re-run the dbv and the problem was fixed.
Any idea what fixed it?
L. du Toit