dbTalk Databases Forums  

Location of Transaction Log Directory

comp.databases.btrieve comp.databases.btrieve


Discuss Location of Transaction Log Directory in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Karl Friedrich
 
Posts: n/a

Default Location of Transaction Log Directory - 11-03-2003 , 06:47 AM






Hello NG

one of our customers wants to change the path for the Transaction Log
Directory from the standard SYS:SYSTEM/MKDE/LOG to another volume
(BILD1:MKDE/LOG, BILD1 is another volume of the same server as SYS).
They did it some years ago without problems but now with a new server
the directory does not change. In Setup32 (Win) they changed the
value, the new entry appears in system\bti.cfg but after a restart the
log files are still in sys:system\mkde\log. I tried it in my test
environment and everything worked fine. Where is the problem?

Environment:
Novell 5.0 SP6a
P.SQL 7.0 SP5


TIA
Karl
--

Reply With Quote
  #2  
Old   
Leonard
 
Posts: n/a

Default Re: Location of Transaction Log Directory - 11-03-2003 , 10:35 PM






Do they by any chance have a bti.lck file in the sys:system folder?
This is the only lock file that Pervasive uses and if it is still
there it does cause issues (not being able to change the settings or
settings ignored).

Leonard

On Mon, 03 Nov 2003 13:47:18 +0100, Karl Friedrich
<k.friedrich (AT) fus (DOT) de> wrote:

Quote:
Hello NG

one of our customers wants to change the path for the Transaction Log
Directory from the standard SYS:SYSTEM/MKDE/LOG to another volume
(BILD1:MKDE/LOG, BILD1 is another volume of the same server as SYS).
They did it some years ago without problems but now with a new server
the directory does not change. In Setup32 (Win) they changed the
value, the new entry appears in system\bti.cfg but after a restart the
log files are still in sys:system\mkde\log. I tried it in my test
environment and everything worked fine. Where is the problem?

Environment:
Novell 5.0 SP6a
P.SQL 7.0 SP5


TIA
Karl


Reply With Quote
  #3  
Old   
Karl Friedrich
 
Posts: n/a

Default Re: Location of Transaction Log Directory - 11-04-2003 , 02:23 AM



On Tue, 04 Nov 2003 04:35:20 GMT, Leonard <lharvey (AT) austin (DOT) rr.com>
wrote:

Quote:
Do they by any chance have a bti.lck file in the sys:system folder?
This is the only lock file that Pervasive uses and if it is still
there it does cause issues (not being able to change the settings or
settings ignored).
a search for bti.* over the whole SYS yields only in bti.cfg. In fact,
I think I have never seen a file bti.lck but I might be wrong.

Only to be sure: When I change settings in the Setup utility these
changes are written into bti.cfg. If I run Setup again, I still see
the actual settings, not the changed ones. bti.cfg is read at the next
restart of the server and the changes take effect.

Now what can I do?

Karl


Quote:
On Mon, 03 Nov 2003 13:47:18 +0100, Karl Friedrich
k.friedrich (AT) fus (DOT) de> wrote:

Hello NG

one of our customers wants to change the path for the Transaction Log
Directory from the standard SYS:SYSTEM/MKDE/LOG to another volume
(BILD1:MKDE/LOG, BILD1 is another volume of the same server as SYS).
They did it some years ago without problems but now with a new server
the directory does not change. In Setup32 (Win) they changed the
value, the new entry appears in system\bti.cfg but after a restart the
log files are still in sys:system\mkde\log. I tried it in my test
environment and everything worked fine. Where is the problem?

Environment:
Novell 5.0 SP6a
P.SQL 7.0 SP5


TIA
Karl
--


Reply With Quote
  #4  
Old   
Bill Bach
 
Posts: n/a

Default Re: Location of Transaction Log Directory - 11-08-2003 , 08:40 AM



Your problem is that Pervasive.SQL is loading on the server BEFORE you've
mounted the new volume, When the engine starts, it sees that the requested
volume is not there, and it corrects itself during the loading process.

Change your AUTOEXEC.NCF to MOUNT ALL drives BEFORE you start your
networking infrastructure, and this problem will go away.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: November 18-20: See our web site for details!


Karl Friedrich wrote:

Quote:
On Tue, 04 Nov 2003 04:35:20 GMT, Leonard <lharvey (AT) austin (DOT) rr.com
wrote:

Do they by any chance have a bti.lck file in the sys:system folder?
This is the only lock file that Pervasive uses and if it is still
there it does cause issues (not being able to change the settings or
settings ignored).

a search for bti.* over the whole SYS yields only in bti.cfg. In fact,
I think I have never seen a file bti.lck but I might be wrong.

Only to be sure: When I change settings in the Setup utility these
changes are written into bti.cfg. If I run Setup again, I still see
the actual settings, not the changed ones. bti.cfg is read at the next
restart of the server and the changes take effect.

Now what can I do?

Karl

On Mon, 03 Nov 2003 13:47:18 +0100, Karl Friedrich
k.friedrich (AT) fus (DOT) de> wrote:

Hello NG

one of our customers wants to change the path for the Transaction Log
Directory from the standard SYS:SYSTEM/MKDE/LOG to another volume
(BILD1:MKDE/LOG, BILD1 is another volume of the same server as SYS).
They did it some years ago without problems but now with a new server
the directory does not change. In Setup32 (Win) they changed the
value, the new entry appears in system\bti.cfg but after a restart the
log files are still in sys:system\mkde\log. I tried it in my test
environment and everything worked fine. Where is the problem?

Environment:
Novell 5.0 SP6a
P.SQL 7.0 SP5


TIA
Karl

--


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.