Thanks!! This restore finally works! Oh wow... it took me over 2 weeks to figure out those several lines of commands... so I guess I'll just post the whole result here, for the potentially unhappy other folks who may try this at home:
db_connect db_activate recover burvis recover_start burvlog LOG 001 recover_replace burvlog /opt/sdb/data/wrk/BURVIS/BURVIS_LOG 002 recover_replace burvlog /opt/sdb/data/wrk/BURVIS/BURVIS_LOG 003 Thus I can restore as many log backups as I wish. ... and then log out of dbmcli and log back in again in "non-utility" (normal) mode to activate database: db_warm load_systab -u dba,dba Notes: --------- For all restore commands you must use utility mode. Either log in with -uUTL, or use db_connect when logged in. Data log must be restored by db_activate recover command. Using recover_start will produce errors later. First log backup must be restored by recover_start <logname> LOG 001. Next log backups must be restored by recover_replace <logname> <path> <nnn>. Note that the command format is different from recover_start. After restore, we need to put database into online state. Now get out of utility mode because db_warm does not work there! Don't use db_activate because this will clear all data! Use (1) db_warm (mandatory!) and then load_systab -u dba,dba (must include the user!). Eduard
