thank you for the answer, but I'm still stuck.
In the migration manual it says as prerequisite for SDBUPD:
"The software version 7.4 is installed using the tgz package"
That sounds like:
"use SDBIST to install the software, *THEN* use SDBUPD to migrate..." hmm, maybe it means:
"unpack the tgz archive" ?!?
Anyway, I did have more than one database instances, therefore SDBUPD did not work. So I used SDBINST to install. It did not give me the chance to specify a target directory, so I guess 7.4 was installed on top of 7.3. Will that be a problem?
After the SDBINST I tried the "Interactive Migration" as mentioned in the migration guide:
>param_checkall OK >db_admin OK >util_execute migrate database ERR -24988,ERR_SQL: sql error -8049,Message not available
And I can't do a 'load_systab' because the database is not online...
So uninstall 7.4, reinstall 7.3, recover backup, migrate using SDBUPD, right? But what do I do with the second database instance??
Arne
Bautz, Christoph wrote:
Hallo Arne,
if you want to update a SAP DB database instance, you should use SDBUPD whenever it is possible. All productive SAP DB databases of version 7.4 are updated with SDBUPD.
SDBUPD is doing the software update and the database update. You can use SDBUPD if there is one database related to one <dependent> database kernel directory. SDBUPD will prepare your database, then it will update the software and then it will do some additional treatment to the database. You can
use SDBUPD to implemet a patch in SAP DB 7.3 or SAP DB 7.4, and you can use it to migrate from SAP DB 7.3 to 7.4.
If you migrating from 7.3 to 7.4 using SDBUPD, you have to stop the database using dbm command 'db_offline'. Then a complete data backup or an incremental and a log backup has to be made in COLD mode.
Then you call call SDBUPD. If you are using SDBUPD to implement patches, no backups are required by SDBUPD. Of course you always take care that you can recover your database by data and log backups before installing new software.
If you cannot use SDBUPD because there is more the one database related to one <dependent> database kernel directory, you can use SDBINST. SDBINST will only update your software and does not take care about databases. If your are implementing patches from 7.3 to 7.3 or from 7.4 to 7.4, you can use SDBINST without a risk, because data structures does not change from one SAP DB version to the other. The only thing you will have to do after SDBINST has finished is to log on to the database using the dbmcli and do a 'db_register' and a 'load_systab' to update your database.
If you want to go from SAP DB 7.3 to SAP DB 7.4, you have to take care because data structures have been changed. That means a SAP DB 7.4 software cannot read data from SAP DB 7.3 without migrating data. Therefore some preparation of the database is necessary, before you can use the new SAP DB software. That's why you must install your database kernel software in a separated directory and follow the step described in http://www.sapdb.org/7.4/pdf/migration73_74eng.pdf.
It seem's to me that you installed the database software of SAP DB version 7.4 to the directory, where your your SAP DB of version 7.3 was installed.
If if can recover your database, the easiest way would be to drop your database. Then you can uninstall the database server software. After that you can install the database server software of SAPDB 7.3 again an restore your database. Then you can use SDBUPD to update your database to 7.4.
To drop your database you can use the dbmcli command db_drop, to uninstall the database server software you must use 'sdbuninst -package "Database Kernel".
Regards,
Christoph Bautz, SAP Labs Berlin
-- Institute of Shipping Economics and Logistics http://www.isl.org/ Arne Gehlhaar mailto:[EMAIL PROTECTED] Universitaetsallee GW1 Block A phone:+49.421.22096.49 D-28359 Bremen, Germany fax:+49.421.22096.55
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
