Hi,
ok, if you are using at least MaxDB 7.7.02.06, version 7.8 or version 7.9, you can simply:
- bring the database to 'admin' state
- and then use dbmcli from the command line to recreate and format the log area with 'util_execute clear log'
You would loose any redo information kept on the log volumes, but as you deleted those volumes, there is nothing left to help you with that. However, if the database was stopped without any transactions left open, you would not loose anything. The 'undo' information is kept on the Data Volumes, which is good for you. Worst case would be a long running transaction which could not be redone because of the missing log info.
Keep in ming to start a full data backup afterwards, because this is mandatory to be able to perform log backups.
If you are using MaxDB 7.6, please try to go to 'admin' state and perform a full backup (make space for that backup, there is no other option besides manual patching the log volume). Then, recover your database using that backup with the option to initialize the database, that is all data and log volumes are formatted before the recovery starts.
Thorsten