Try the command, db_addvolume. As a general rule, you should avoid useing param_addvolume after you install the instance. Use param_addvolume to add a mirrored log volume, for example, but not a data volume.
For example: (in admin operational state)
#dbmcli -d <dbname> -u <dbmuser,dbmpass> #db_addvolume DATA DAT_000X F <size in pages>
By default, when your logs become full, you must back them up. This will "clean" the transaction log as you say.
You might consider setting your database logs to "Auto Overwrite" --- this will make it impossible for the log to overflow.
Do this with the command: (in dbmcli)
#dbmcli -d <dbname> -u <dbmuser,dbmpass>
# db_admin
# util_connect
# util_execute SET LOG AUTO OVERWRITE ON
# util_release
Hope this helps, JLS
Mark Johnson wrote:
I have had this problem before and received a few suggestions, but have not solved this problem yet. Our database fills and, in addition, there are many transactions in the transaction log. This prevents the database from comming up into warm mode (it halts while moving transactions to from the transaction log to the database I think).
I can get the database to admin mode, but the utilities will not allow me to add a dev space while the database is in admin mode. So, I either need a way to add a dev space in admin (or cold mode), or be able to flush the transaction log and make all the records in the database appear "clean" again.
Thanks in advance for any help. Mark
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
