Re: Pervasive 2000i data recovery question

If the failure was a SQL-level INSERT statement, then the data changes
never made it to the Microkernel level, which is what the MKDE Logs are
there for. Since the data inserts were never made, the MKDE never saw
the changes, and they are lost. It is up to the application to
properly detect such limitations and fail properly.

The only way in which this information could have been trapped is with
the use of an external auditing tool, something like Pervasive's
AuditMaster tool. However, AuditMaster does not work with the older
PSQL2000i engine.

Since it is your own application, the best bet is to log the data into
a running log file in text format as a backup to the database. If the
data is valuable, the ability to archive all data on a daily basis will
provide a lot of added value, with little extra overhead.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Sydney: Pervasive.SQL Service & Support Class - 02/27/06 ***
*** Chicago: Pervasive.SQL Service & Support Class - 03/27/06 ***

Kelly W. Zini wrote:

> My application uses an ODBC connection to insert data into a 2000i SP4
> database table acquired from external industrial equipment. A
> totalizer register in one field device exceeded 32767 for a column
> defined as a real value and the inserts began to fail with a column
> data range exceeded type error. This occurred over a weekend and the
> plant personal did not catch the error for 2 days. After poking
> around a bit, I found a series of log files in the pvsw\bin\mkde\log
> folder. Browsing these files with a text editor shows several
> entries for the table but the data is represented in binary and
> therefore is not readable. We desperately need to view certain table
> column values from the missing days for governmental reporting
> purposes. I understand that the logs are associated with the
> Transaction Durability feature, but if a column data type value is
> exceeded, restarting the database engine would not allow the records
> to be rolled into the table.
>
> My questions are:
>
> 1. Would an SQL insert failure, due to an exceeded column value,
> result in the data being written to the mentioned logs?

> 2. If the data is in the logs, is there any browser utility that can
> display the log contents in readable format?
>
> 3. If the logs cannot be viewed, can anyone provide a layout of
> these logs so I could access them programmatically?
>
> 4. If there is no way to access the logs external from Pervasive,
> can I alter the table column from a real data type to a long integer
> and force a Pervasive recovery?
>
> My environment is:
> WinXP, SP1
> 2000i SP4 Workgroup license.
>
> Thanks to anyone that can assist us with the recovery of this
> critical data.
>
> Kelly W. Zini
> Control Products Unlimited, Inc.

.

Relevant Pages

  • Re: disaster recovery log file question
    ... We recently had an exchange failure here due to faulty drives. ... backup and server is running fine now. ... Transaction logs are not committed during a backup, ...
    (microsoft.public.exchange.admin)
  • Re: Sudden shutdown
    ... Same type failure also does not display any useful BSOD ... failure long ago that would eventually start causing shutdowns today. ... around' long ago while also stored in the system logs. ... Dust causing a crash in a one year old computer in a 70 degree room ...
    (microsoft.public.windows.vista.general)
  • Re: NTLM Proxy locking user account
    ... You may not have failure auditing turned on for the domain controllers. ... may just be missing them in the dc logs. ... you may want to verify that you're getting failure audit logs for various ... every so often users get prompted to login into NTLM proxy ...
    (microsoft.public.windows.server.active_directory)
  • Re: LDAP Lookup failure
    ... I thought that was incorrect as well, I think this must be incorrect logging ... I have failure auditing on on the DC policy, but no entries appear from the ... > Did you enable failure audits on the DC and check the logs? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Web site cant be browsed when logging out from IISv6.0 Server
    ... Your logs show that there is a failure to instance some object ... but that it lack sufficient permissions to instance whatever ... browse the website. ...
    (microsoft.public.inetserver.iis.security)