|
Home > Archive > SQL Anywhere database > May 2005 > database log file dependancy
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
database log file dependancy
|
|
| Doug Stone 2005-05-13, 1:23 pm |
| Sometimes a customer will send their ASA8 or ASA9 database to me. When I
try to start ASA8/9 against the database, an error msg will report "cannot
open transaction log file -- No such file or directory".
If I select Change Log File Settings from SC, that utility can see that the
database file has a log file, but it is unable to remove the log file link.
Why is SC unable to remove the log file link? Is the database in an
unstable state without the log file?
Could SC be setup to report the name of the log file and in which directory
it is expected?
Could a change be made to dbbackup or the backup event so that the database
file is backed up in a state where it is not dependant on the log file?
Thanks,
Doug
| |
| Erik Anderson 2005-05-13, 1:23 pm |
| The transaction log is needed for a database file that has not been cleanly
shut down. During the live backup process the database is copied while it
is in use and is therefore not cleanly closed (the transaction log, which is
copied after the .db file is, may actually contain transactions that had not
been made to the copied .db file)
Starting and stopping the database engine on the backed up .db file will
close it off and allow it to start without the transaction log. However
please note that closed off databases cannot participate in many of the ASA
database recovery methodologies. I learned this the hard way, after I used
to dbunload the backup .db file on each backup (dbunload uses a database
engine and therefore closes off the .db file when it's done)
In your case, if you don't mind too much about losing recent transactions
you can use the -f parameter when starting the database. This will forcably
close off the .db file (losing any incomplete transactions) and then exit,
allowing you to start the database again normally.
"Doug Stone" <nospamdstoneatres-qdotcom> wrote in message
news:4284dba4$1@foru
ms-1-dub...
> Sometimes a customer will send their ASA8 or ASA9 database to me. When I
> try to start ASA8/9 against the database, an error msg will report "cannot
> open transaction log file -- No such file or directory".
>
> If I select Change Log File Settings from SC, that utility can see that
> the database file has a log file, but it is unable to remove the log file
> link.
>
> Why is SC unable to remove the log file link? Is the database in an
> unstable state without the log file?
> Could SC be setup to report the name of the log file and in which
> directory it is expected?
> Could a change be made to dbbackup or the backup event so that the
> database file is backed up in a state where it is not dependant on the log
> file?
>
> Thanks,
> Doug
>
>
|
|
|
|
|