|
Home > Archive > SQL Anywhere database replication > August 2005 > Lost my transaction log file location...HELP!
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 |
Lost my transaction log file location...HELP!
|
|
| Tasha Travis 2005-08-02, 11:23 am |
| I attempted to change the location of my log file for my consolidated
database, but inadvertently created a new one (I opened the DB file and it
created a new log file within the same subdirectory). Will this affect my
remote databases when they replicate? If so, how?
| |
| Jim Diaz 2005-08-02, 1:23 pm |
| This shouldn't be a problem. Rename the old log file and place in the same
directory as the new log file dbremote will automatically search all log
files. To test the files to see if the offsets are contiguous from the
command prompt dblog [Log file name and path]
this should give you an output like -
Adaptive Server Anywhere Transaction Log Utility Version 9.0.1.1751
File "logbook.log" is a transaction log file
File version is 41
Log starts at offset 0002097681
Log ends at offset 0002101823
Log contains 48 pages with a page size of 4096 bytes
4142 bytes in use (2.11%), 192466 bytes free (97.89%)
Do this for each file and make sure the end offset of one is the start
offset of the next.
Jim
"Tasha Travis" < ltravis@crmanagement
.com> wrote in message
news:42ef8afa$1@foru
ms-2-dub...
>I attempted to change the location of my log file for my consolidated
> database, but inadvertently created a new one (I opened the DB file and
> it
> created a new log file within the same subdirectory). Will this affect my
> remote databases when they replicate? If so, how?
>
>
| |
| Tasha Travis 2005-08-02, 1:23 pm |
| Does this mean that if the offset of the newly created log file is the same
as the original, the new one can be used in its place? When I attempt to
use the old log file I get an error message stating that the DB file is
newer than the log, so it can't be used.
Tasha
"Tasha Travis" < ltravis@crmanagement
.com> wrote in message
news:42ef8afa$1@foru
ms-2-dub...
> I attempted to change the location of my log file for my consolidated
> database, but inadvertently created a new one (I opened the DB file and
it
> created a new log file within the same subdirectory). Will this affect my
> remote databases when they replicate? If so, how?
>
>
| |
| Jim Diaz 2005-08-02, 1:23 pm |
| No, the database will want to use the log file you inadvertantly created,
but dbremote will use both the new and the old log files. Lets assume you
originally had a single directory which contained both the database file and
the log file
DatabaseFiles\xxx.db
DatabaseFiles\xxx.log
Now as I understand it you changed the location of the log file lets say you
changed to DatabaseLogFiles\xxx
.log. You started the database and it
created DatabaseLogFiles\xxx
.log. Now you have two log files, rename the
original DatabaseFiles\xxx.log to DatabaseFiles\050802
00.log then copy this
file to the new log location. The new log file location will now have two
log files DatabaseLogFiles\xxx
.log and DatabaseLogFiles\050
80200.log. When
you start the database it will use DatabaseLogFiles\xxx
.log but when you run
dbRemote it will scan and use both log files. To confirm that the starting
and ending offsets of the two log files are contiguous you can run the dbLog
command I refered to earlier.
Jim
"Tasha Travis" < ltravis@crmanagement
.com> wrote in message
news:42efb290$1@foru
ms-2-dub...
> Does this mean that if the offset of the newly created log file is the
> same
> as the original, the new one can be used in its place? When I attempt to
> use the old log file I get an error message stating that the DB file is
> newer than the log, so it can't be used.
>
> Tasha
> "Tasha Travis" < ltravis@crmanagement
.com> wrote in message
> news:42ef8afa$1@foru
ms-2-dub...
> it
>
>
| |
| Tasha Travis 2005-08-03, 11:23 am |
| Thanks Jim! That worked!
Tasha
"Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
news:42efb972$1@foru
ms-2-dub...
> No, the database will want to use the log file you inadvertantly created,
> but dbremote will use both the new and the old log files. Lets assume you
> originally had a single directory which contained both the database file
and
> the log file
>
> DatabaseFiles\xxx.db
> DatabaseFiles\xxx.log
>
> Now as I understand it you changed the location of the log file lets say
you
> changed to DatabaseLogFiles\xxx
.log. You started the database and it
> created DatabaseLogFiles\xxx
.log. Now you have two log files, rename the
> original DatabaseFiles\xxx.log to DatabaseFiles\050802
00.log then copy
this
> file to the new log location. The new log file location will now have two
> log files DatabaseLogFiles\xxx
.log and DatabaseLogFiles\050
80200.log.
When
> you start the database it will use DatabaseLogFiles\xxx
.log but when you
run
> dbRemote it will scan and use both log files. To confirm that the
starting
> and ending offsets of the two log files are contiguous you can run the
dbLog
> command I refered to earlier.
>
> Jim
>
> "Tasha Travis" < ltravis@crmanagement
.com> wrote in message
> news:42efb290$1@foru
ms-2-dub...
to[color=darkred]
and[color=darkred]
>
>
|
|
|
|
|