Subject | Re: [firebird-support] re-occoring problem |
---|---|
Author | Helen Borrie |
Post date | 2006-06-26T08:35:53Z |
At 05:17 PM 26/06/2006, you wrote:
operating system level, e.g. an I/O error, a call to a system-level
function that isn't supported on the operating system, an
out-of-memory error, etc. It means the OS has sent a message to the
DB engine saying "No can do" and the engine can't proceed with
whatever task it needed that call for.
something wrong with the resources it depends on. Take it as a
warning of something bad that you need to investigate to save your
database from corruption. You're using IB 5.6, as I recall, so let's
hope you are not encountering one of the two best-known corruption
conditions in IB 5.6 - overflowing the 2 Gb file size limit on a
FAT32 partition or else the dreaded "Windows Path Bug". See the
notes in the Firebird Quick Start Guide on "How to corrupt a database".
Would you please do something about the automatic footers in your
emails. It's totally pointless putting your company's security
message in an email that you are posting to a public forum.
^ heLen
>Good day all"A system error" generally means something gone wrong at the
>=0-=0=-0=-0-=
>
>We have a funny problem that is coming over and over again back and
>we cant pinpoint where it comes from
>
>We have seen that it does come from the interabase.msg file. Thus it
>is at db level (or client libarary) that we
>get this error
>
>Unsuccessful execution caused by a system error that precludes
>successful execution of subsequent statements
>
>BUT we cannot really see why. What can the reasons for this error be ?
operating system level, e.g. an I/O error, a call to a system-level
function that isn't supported on the operating system, an
out-of-memory error, etc. It means the OS has sent a message to the
DB engine saying "No can do" and the engine can't proceed with
whatever task it needed that call for.
>It sounds asif a statement inside the transaction failed and then asIt's not so odd. The engine won't go on blindly if it knows there is
>we go on all statements after that
>is rejected somehow.But we do rollback after errors. This very odd.
something wrong with the resources it depends on. Take it as a
warning of something bad that you need to investigate to save your
database from corruption. You're using IB 5.6, as I recall, so let's
hope you are not encountering one of the two best-known corruption
conditions in IB 5.6 - overflowing the 2 Gb file size limit on a
FAT32 partition or else the dreaded "Windows Path Bug". See the
notes in the Firebird Quick Start Guide on "How to corrupt a database".
Would you please do something about the automatic footers in your
emails. It's totally pointless putting your company's security
message in an email that you are posting to a public forum.
^ heLen