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 

-----Urspr�ngliche Nachricht-----
Von: Arne Gehlhaar [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 24. Februar 2003 15:00
An: [EMAIL PROTECTED]
Betreff: Re: Why are 7.4 upgrade problems and questions being ignored?


Hi,

I just tried to update. Here's what happened:

> [EMAIL PROTECTED] sapdb-all-linux-32bit-i386-7_4_3_10]# ./SDBUPD
> 
> 
>         SAP DB INSTANCE UPDATE
>         **********************
> 
> 
> starting installation Mo, Feb 24, 2003 at 13:56:09
> operating system: Linux I386 2.4.18 18.7.x GLIBC 2.2.5
> callers working directory: /usr/install/sapdb-all-linux-32bit-i386-7_4_3_10
> 
> 
> beginning to check sap db instances
> existing instance:
> 0:  CODABA  "/usr/sapdb/depend"  7.4.3.10
> 1:  none
> please enter instance id: 0
> please enter database manager operators name: DBM
> please enter database manager operators password:
> start new instance update
> finding instance type...
> finding starting release...
> finding migration strategy...
> looking for running instances...
> checking paramfile modifications...
> switch to offline
> switch to online
> sap db instance "CODABA" not ready to update
> switch to offline
> switch to online
> cannot switch database mode, error during dbm command:
> db_online
> ERR
> -24988,ERR_SQL: sql error
> -8888,connection broken
> 
> looking for error messages in knldiag
> ...
[knldiag]
> ...
> end of knldiag
> 
> SAP DB instance update exited abnormally at Mo, Feb 24, 2003 at 13:56:54


what happened?

knldiag attached...

Thanks
Arne

-- 
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

Reply via email to