Re: Modifying the log area of MAXDB 7.8

Hello Amit,

as Yashwanth has put it correctly: you cannot use dbmrelocate for moving volumes...

But let me add that the above referred Wiki section describes changing the volume path with the GUI Database Manager only. Very good GUI guide, but a bit outdated since for newer database releases we have switched to MaxDB Database Studio.

If you want to, you can always use the command line as an alternative approach:

1. establish a dbmcli session via 'dbmcli -d <database name>  -u <user,password>

2. bring the database to 'offline' state.

3. Identify the current location of the volume you want to move e.g. the path is part of the KnlMsg file or you can get it via the 'param_getvolsall' command.

4. Change the path via 'param_directput DataVolumeName...'.

Here is an example of moving data volume 1 from C: to F: (database is already in offline state):

dbmcli on tz79>param_getvolsall

OK

UseMirroredLog                   NO

MaxLogVolumes                    2

MaxDataVolumes                   64

LogVolumeName001                 6400       F  C:\sapdb\data\TZ79\volumes\log\DISKL0001  1

DataVolumeName0001               32000      F  C:\sapdb\data\TZ79\volumes\data\DISKD0001

dbmcli on tz79>param_getvalue DataVolumeName0001

OK

C:\sapdb\data\TZ79\volumes\data\DISKD0001

dbmcli on tz79>param_directput DataVolumeName0001 F:\sapdb\data\TZ79\volumes\data\DISKD0001

OK

dbmcli on tz79>param_getvolsall

OK

UseMirroredLog                   NO

MaxLogVolumes                    2

MaxDataVolumes                   64

LogVolumeName001                 6400       F  C:\sapdb\data\TZ79\volumes\log\DISKL0001  1

DataVolumeName0001               32000      F  F:\sapdb\data\TZ79\volumes\data\DISKD0001

Thorsten