SQL Anywhere Feedback - Database recovery log into text file

Author

Database recovery log into text file

Kjetil Valøy

2005-08-15, 7:23 am

I would like to have all select statements that are rollbacked during
database startup to be logged into a textfile. This would be very good
information so we can take actions before starting the rest of the
system. The name of the textfile should be the current timestamp of
the startup of the database.

The reason I want a textfile is that it's easyer for non database
persons to check without translating the log file.

As we are in a position with a lot of databases we will have to live
with version 9.0.x for some years. It would be good to have this
functionality in version 9.0.x.

Kjetil Valøy

Greg Fenton

2005-08-15, 11:23 am

Kjetil Valøy wrote:
> I would like to have all select statements that are rollbacked during
> database startup to be logged into a textfile.

Do you mean "SQL statements" rather than "select statements" ?

>
> The reason I want a textfile is that it's easyer for non database
> persons to check without translating the log file.
>

I'm not sure I follow. You want someone who is not a database person to
understand rollbacked instructions from a crash recovery?

I wonder if you might instead describe what it is you are hoping to gain
by having this text file. What do you expect it to contain that would
be of value to your "non-database end-users" ?

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Kjetil Valøy

2005-08-15, 8:23 pm

You are totaly right, I did not mean select statements but
the actual statements that have been rolled back.

We have several persons that understand SQL very good, but
they are not skilled in understending .log translation. Also
it would be easier to inspect a text file to see if there is
something important that have been rollbacked. With a normal
shutdown this file would bee empty in most cases.

We have a quite large system with several databases on
different servers on a lot of locations linced together with
EAServer/Jaguar transaction servers. On one occation SQL
Anywhere crashed with the consequence that a lot fo data
where rolled back in the central db. With a text file log
that logged the rollback under startup we would se strait
away if something needs our attention. Now the only way to
see what happend during startup is to translate the logfile
and then investigate that.

Hope you understood this better becaus this would really
help us in ease the maintainance.

--- Kjetil --

> Kjetil Val=f8y wrote:
> textfile.
>
> Do you mean "SQL statements" rather than "select
> statements" ?
>
>
> I'm not sure I follow. You want someone who is not a
> database person to understand rollbacked instructions
> from a crash recovery?
>
> I wonder if you might instead describe what it is you are
> hoping to gain by having this text file. What do you
> expect it to contain that would be of value to your
> "non-database end-users" ?
>
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/

Sponsored Links