![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
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). |
|
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 |
#4
| |||
| |||
|
|
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 -- |
![]() |
| Thread Tools | |
| Display Modes | |
| |