Re: [Info-ingres] File Corruptions
- From: Andy X Keadell <akeadell@xxxxxxx>
- Date: Tue, 13 Dec 2005 11:32:13 -0500
Had exactly this kind of problem a few years ago - on a VMS cluster. We
had corrupt checkpoints - which we found out about when rolling them
into the reporting databases. We were told over and over that Ingres was
causing the problem. As we all know, that was complete and utter
garbage - the file corruptions were caused by having the wrong rev on the
storage works boxes - hardware problem. Upgraded the sims
and the problem went away - what a shock .......
----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
Karl & Betty
Schendel To: info-ingres@xxxxxxxxxxxxxxx
<schendel cc:
@kbcomputer.com> Subject: Re: [Info-ingres] File Corruptions
Sent by:
info-ingres-admi
n
12/13/2005 11:15
AM
At 7:25 AM -0800 12/13/2005, Nabil wrote:
>Our database reported table corruptions. When we tried to recover from
>back up, which was a compressed tar file of several database data
>files, the uncompress command reported the error - "uncompress: corrupt
>input", when consulting with our system administrators, they quickly
>pointed in the direction of the database since it reported the
>corruption first.
That's baloney.
I could make some incisive comments about your sysadmins, but let's
charitably assume that they are simply untutored and uninformed.
>Our (DBAs) argument is that true database
>corruptions are logical and can only be visible to the database engine,
>the OS would never know about true database corruptions such as (bad
>leaf pages, dangling pointers, etc..) and the OS utilities would never
>know about a native database corruption. Hence we are convinced that
>the corruption which was firstly reported by the database was a
>physical file corruption due the the I/O subsystem and was *NOT* a
>native database corruption and that is why the uncompress also sees it
>as a corrupted file.
I agree 100% with you.
Uncompress and Ingres interpret files in totally different ways.
Compress/uncompress merely operate on a byte stream. If you feed a
byte stream into compress, and uncompress says "corrupt input", than
something went wrong with the compressed file. That has squat to do
with Ingres.
Assuming you didn't FTP the file around in ascii mode, I'd say you
have some broken hardware.
>
>Also files that we are able to uncompress, we are not able to extract
>the datafiles from the uncompressed tar files, in this case, the 'tar
>xvf' starts extracting several files then bails out with an error "This
>does not look like a tar file, blah blah blah".
More of the same.
Karl
_______________________________________________
Info-ingres mailing list
Info-ingres@xxxxxxxxxxxxxxx
http://mailman.cariboulake.com/mailman/listinfo.py/info-ingres
.
- Prev by Date: Re: [Info-ingres] File Corruptions
- Next by Date: Re: [Info-ingres] Re: What animal should Ingres be?
- Previous by thread: Re: [Info-ingres] File Corruptions
- Index(es):
Relevant Pages
|
