Hallo Andrea, > Sorry, but I only have the knldiag files, because I did uninstall > 7.4 and got back to 7.3. I got two separate problems:
> * unable to upgrade following the instructions provided. The software upgrade > went apparently fine only when I did the following command sequence: > * x_server stop > * x_server remove > * reboot! > * sdbinst (now goes fine). > If I try the command sequence without rebooting the sbdinst command fails. It's really sorry that we cannot take a look at the log files. The program SDBINST should do the 'x_server remove' before it will update 'serv.exe'. May be the service was already in the state 'marked for deletion' when SDBINST was started. The only way to solve this situation is to reboot. You should !!! never !!! modify or delete 'serv.exe' without doing a 'x_server stop' and 'x_server remove' before to avoid this state of the service. The sequence has to be 'stop' -> 'remove' -> 'modify or delete'. > * after a successful upgrade, I tried sdbupd to update a database instance, > and kernel.exe crashed leaving me with an unusable db. The knldiag files > should contain informations about it. (btw, I sent this file also to > Martin Brunzema this morning) You can use either SDBINST or SDBUPD. Both programs are updating the software, but only SDBUPD is updating the database instance too. SDBUPD is doing the preparation of the database for migration, the software update and update of the database instance for you. If you are using SDBINST to update you database software from SAP DB 7.3 to SAP DB 7.4 you have to take care the all data are migrated. If you are using SDBINST you have to follow the steps in http://www.sapdb.org/7.4/pdf/migration73_74eng.pdf. > * just to give you an idea of the reboots I needed to perform, > I also tried to uninstall using sdbuninst -all after dropping all database > instances > and it was complaining that the db instances were still there... I had to > reboot again to make it realize that I had dropped them. After a good number of > reboot I could finally come back to 7.3... Dropping a database instance means you have to stop it using dbmcli command 'db_offline' and drop it using dbmcli command 'db_drop'. There are still database instances existing if the dbmcli command 'db_emun' shows them. Of cause it is not necessary to reboot after dropping a database. > Best regards > Andrea Aime regars, Christoph Bautz, SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
