|
Home > Archive > SQL Anywhere for Linux > May 2005 > Move transaction log file
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 |
Move transaction log file
|
|
| Marcelo Hille 2005-05-13, 1:23 pm |
| Hi everybody,
I'm trying to put the transaction log file in different partitions (on
different disks / controller) but I'm getting some problems.
First of all, I created the database with dbinit with -t flag, putting the
transaction log file in another path.
Started server with these options: dbsrv9 -x tcpip -p 8192 -ud -n [server
name] [/path/database.db]
Everthing looks great, but if I restart the server, the transaction log
appears on the same database file path again.
(Sybase version: 9.0.2.2452 on a RedHat enterprise 3, kernel:
2.4.21-27.0.2.ELsmp.)
What am I doing wrong?
Marcelo Hille.
| |
| David Kerber 2005-05-13, 1:23 pm |
| In article <4284def4$1@forums-2-dub>, marcelo.cpd@sankoespumas.com.br
says...
> Hi everybody,
>
>
>
> I'm trying to put the transaction log file in different partitions (on
> different disks / controller) but I'm getting some problems.
>
>
>
> First of all, I created the database with dbinit with -t flag, putting the
> transaction log file in another path.
>
> Started server with these options: dbsrv9 -x tcpip -p 8192 -ud -n [server
> name] [/path/database.db]
>
> Everthing looks great, but if I restart the server, the transaction log
> appears on the same database file path again.
>
>
>
> (Sybase version: 9.0.2.2452 on a RedHat enterprise 3, kernel:
> 2.4.21-27.0.2.ELsmp.)
>
>
>
> What am I doing wrong?
Use the dblog utility to change the location of the log file.
--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
| |
| Greg Fenton 2005-05-14, 3:23 am |
| Marcelo Hille wrote:
>
> First of all, I created the database with dbinit with -t flag, putting the
> transaction log file in another path.
>
As David points out, dblog is the utility you want to be using. To find
out what the database's current transaction log is set to try:
dblog your_database_file.db
To set it to another value:
dblog -t /path/to/some_file.log your_database_file.db
Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|
|
|
|
|