RedHat Linux 8.0. Only one database, TST74. Steps:
dbmcli -d <dbname> -u <dbm user>,<dbm passwd>
db_offline
db_cold
util_connect
backup_start <medium>
util_release
exit
x_server stop
rpm -Uhv sapdb-srv74-7.4.3.25-1.i386.rpm
The rpm command first unpacked (??) 100%, then died with a segmentation
fault at about 30%
copy (??). After some further work, both steps completed to 100% but cpio
reported insufficient
disk space, apparently in /opt where the sapdb lives. Fortunately we set
this box up with LVM so
that we can expand filespace.
On umount /opt, we got:
umount: /opt: device is busy
ps -x | grep opt returned:
17119 ? S 0:01 /opt/sapdb/depend74/pgm/kernel TST74
17121 ? S 0:01 /opt/sapdb/depend74/pgm/kernel TST74
Apparently we still have a couple processes running against TST74. Why?
What steps did I leave
out of my process? Can I just:
kill 17119 17121
since I no longer have a complete install, or will I destroy my database?
> This correspondence is for the named person's use only. It may contain
> confidential or legally privileged information and is intended solely for
> the named addressee. If you receive this correspondence in error, please
> notify the sender and delete it from your system . You must not disclose,
> copy or rely on any part of this correspondence if you are not the
> intended recipient.
>
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
