Here's a possibility: If you installed SAP-DB on linux from the RPM, the RPM already has a system area created. Attempts to create the system devspace will produce strange errors that don't give much clue as to what's wrong.
I did this through DBMCLI and spent some time trying to figure out the source of the error - It was really just through some lateral thinking that I came up with the hypothesis to test. The error messages were quite un- helpful. It's possible that this situation confuses the GUI tools, although I haven't tested this. Nigel. -----Original Message----- From: Mark Duckworth [mailto:[EMAIL PROTECTED] Sent: Monday, 10 March 2003 6:30 a.m. To: SAPDB General Subject: Delete Corrupted Database Hello everyone, I'm rather new to SAPDB but am a System Administator and not very new to computers in general. Under installation of SAPDB I chose the following steps under Redhat Linux 7.3. 1. Install SAPDB 2. Install webtools 3. Use webtool and sapdb system account (actual linux account) to start creation of new db through web interface. 4. Now this is where it is more complicated. I abandoned the creation of the database when I got to the point where it asks for paths and sizes of database and log files. This is because when I attempted to click either one and define information, after I defined those settings and I clicked okay nothing seemed to happen. Once I returned to the prior screen using the back button nothing was changed and there was no way for me to progress finishing the database! Okay, so I do what anyone would do grab the dbmgui and connect from a windows 2000 machine and proceed to try to "reinstall" the db. I get to the point where finalizing the db installation and I get some strange error code that I didn't write down (sorry developers :-/). At this point I use dbmgui to create a test db instance of a different name and different users to verify it works at all. It does. Okay so I'm irritated at this point but happy I found a way to create the db and continue, however I felt best to start fresh from the installation, so I proceed to delete sapdb by rm -rf /opt/sapdb and rm -rf /var/log/sapdb and rm -rf /var/opt/sapdb, userdel -r sapdb groupdel sapsys, etc. I literally deleted every trace I can find on the system, however when attempting to run SDBINST again I get: [EMAIL PROTECTED] sapdb-all-linux-32bit-i386-7_4_3_14]# ./SDBINST Installation of SAP DB Software ******************************** starting installation Su, Mar 09, 2003 at 12:20:00 operating system: Linux I386 2.4.18 19.7.xsmp GLIBC 2.2.4 callers working directory: /root/sapdb-all-linux-32bit-i386-7_4_3_14 install registry path "/var/opt/sapdb/indep_data/config/install" dont exist cannot create install registry file installation exited abnormally at Su, Mar 09, 2003 at 12:20:00 [EMAIL PROTECTED] sapdb-all-linux-32bit-i386-7_4_3_14]# If I restore sapdb user and groups and make that dir the install continues but.... The old db instances are broken and undeletable due to no dbm user login for them. - They're still there... where is their information being stored? I have no processes running or related files still on the system that I can find? So to make things short, I'm quite irritated that something is hiding somewhere in the system, a registry or whatnot that is not easy to find at all (or maybe it is and I'm just blind), there's no processes running and no files that I can find anywhere relating to sapdb left on the system yet somehow - it knows. I've also seen this question asked numerous times before as I've been searching for answers for several days. Most answers go along the lines of install new and register the db to a new instance. I want to know however, How do I delete *ALL TRACES* of sapdb from the system so that it has absolutely no idea that it was ever installed and the installation proceeds normally. I'm only stressing it because I'm asking for an answer that says something along the lines of rm /delete/this/path/and/file rather than load dbmcli and register and such and such. If the answer to my question is blatently obvious or I come off as sounding rude, I apologize for that, it isn't my intent... I just don't think things should be this difficult to handle. Thanks SAPDB guys for your hard work and effort in creating one nice enterprise DB. Thank you, Sincerely, -- Mark Duckworth <[EMAIL PROTECTED]> _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
