cancel
Showing results for 
Search instead for 
Did you mean: 

Can't drop a database that was 'partially' created

Former Member
0 Kudos

Hi,

I was creating a new database with the db studio. When it was creating the data and log files an error (permission denied) was raised and the creation script ended. I had no permission to write on the data file destination directory.

The problem is now I can't drop the partially created db because dba user/password is not accepted.

What can I do now ?

Thank you !!

Accepted Solutions (1)

Accepted Solutions (1)

former_member229109
Active Contributor
0 Kudos

Hello Andrea Vettori,

1. To drop the database instance connect as DBM user.

Check if you could connect with default user/password.

Login to the data base server & run the following commands:

dbmcli -d <SID> -u control,control db_state

dbmcli -d <SID> -u dbm,dbm db_state

2. Please update the thread with output of the following commands:

xinstinfo <SID>

dbmcli inst_enum

dbmcli db_enum

Thank you and best regards, Natalia Khlopina

Former Member
0 Kudos

Dear Natalia,

thanks for helping.

#dbmcli -d B2BZLOG -u control,control db_state
Error! Connection failed to node (local) for database B2BZLOG:
-24950,ERR_USRFAIL: User authorization failed

#dbmcli -d B2BZLOG -u dbm,dbm db_state
Error! Connection failed to node (local) for database B2BZLOG:
-24950,ERR_USRFAIL: User authorization failed

#xinstinfo B2BZLOG
IndepData           : /home/sdb/data
IndepPrograms       : /opt/sdb/programs
InstallationPath    : /opt/sdb/7706
Kernelversion       : KERNEL    7.7.06   BUILD 009-123-202-944
Rundirectory        : /home/sdb/data/wrk/B2BZLOG

#xinstinfo B2BZLOG
IndepData           : /home/sdb/data
IndepPrograms       : /opt/sdb/programs
InstallationPath    : /opt/sdb/7706
Kernelversion       : KERNEL    7.7.06   BUILD 009-123-202-944
Rundirectory        : /home/sdb/data/wrk/B2BZLOG

#dbmcli inst_enum
OK
7.7.06.09    /opt/sdb/7706

Former Member
0 Kudos
#dbmcli db_enum
OK
B2BALOG	/opt/sdb/7706                          	7.7.06.09	fast	running
B2BALOG	/opt/sdb/7706                          	7.7.06.09	quick	offline
B2BALOG	/opt/sdb/7706                          	7.7.06.09	slow	offline
B2BALOG	/opt/sdb/7706                          	7.7.06.09	test	offline
B2BZLOG	/opt/sdb/7706                          	7.7.06.09	fast	offline
B2BZLOG	/opt/sdb/7706                          	7.7.06.09	quick	offline
B2BZLOG	/opt/sdb/7706                          	7.7.06.09	slow	offline
B2BZLOG	/opt/sdb/7706                          	7.7.06.09	test	offline
ADVLKLOG	/opt/sdb/7706                          	7.7.06.09	fast	running
ADVLKLOG	/opt/sdb/7706                          	7.7.06.09	quick	offline
ADVLKLOG	/opt/sdb/7706                          	7.7.06.09	slow	offline
ADVLKLOG	/opt/sdb/7706                          	7.7.06.09	test	offline

ECF3	/opt/sdb/7706                          	7.7.06.09	fast	running
ECF3	/opt/sdb/7706                          	7.7.06.09	quick	offline
ECF3	/opt/sdb/7706                          	7.7.06.09	slow	offline
ECF3	/opt/sdb/7706                          	7.7.06.09	test	offline
B2BYLOG	/opt/sdb/7706                          	7.7.06.09	fast	running
B2BYLOG	/opt/sdb/7706                          	7.7.06.09	quick	offline
B2BYLOG	/opt/sdb/7706                          	7.7.06.09	slow	offline
B2BYLOG	/opt/sdb/7706                          	7.7.06.09	test	offline
UTIL	/opt/sdb/7706                          	7.7.06.09	fast	running
UTIL	/opt/sdb/7706                          	7.7.06.09	quick	offline
UTIL	/opt/sdb/7706                          	7.7.06.09	slow	offline
UTIL	/opt/sdb/7706                          	7.7.06.09	test	offline
PERS	/opt/sdb/7706                          	7.7.06.09	fast	running
PERS	/opt/sdb/7706                          	7.7.06.09	quick	offline
PERS	/opt/sdb/7706                          	7.7.06.09	slow	offline
PERS	/opt/sdb/7706                          	7.7.06.09	test	offline

Former Member
0 Kudos
JMS	/opt/sdb/7706                          	7.7.06.09	fast	running
JMS	/opt/sdb/7706                          	7.7.06.09	quick	offline
JMS	/opt/sdb/7706                          	7.7.06.09	slow	offline
JMS	/opt/sdb/7706                          	7.7.06.09	test	offline
B2BLOG	/opt/sdb/7706                          	7.7.06.09	fast	running
B2BLOG	/opt/sdb/7706                          	7.7.06.09	quick	offline
B2BLOG	/opt/sdb/7706                          	7.7.06.09	slow	offline
B2BLOG	/opt/sdb/7706                          	7.7.06.09	test	offline
ETLOG	/opt/sdb/7706                          	7.7.06.09	fast	running
ETLOG	/opt/sdb/7706                          	7.7.06.09	quick	offline
ETLOG	/opt/sdb/7706                          	7.7.06.09	slow	offline
ETLOG	/opt/sdb/7706                          	7.7.06.09	test	offline
BTLOG	/opt/sdb/7706                          	7.7.06.09	fast	running
BTLOG	/opt/sdb/7706                          	7.7.06.09	quick	offline
BTLOG	/opt/sdb/7706                          	7.7.06.09	slow	offline
BTLOG	/opt/sdb/7706                          	7.7.06.09	test	offline
STLOG	/opt/sdb/7706                          	7.7.06.09	fast	running
STLOG	/opt/sdb/7706                          	7.7.06.09	quick	offline
STLOG	/opt/sdb/7706                          	7.7.06.09	slow	offline
STLOG	/opt/sdb/7706                          	7.7.06.09	test	offline

Sorry for the multiple post but it seems I can't put all info in a single post beacuse if I do it will not be formatted as code.

JPReyes
Active Contributor
0 Kudos

dbmcli -d B2BZLOG -u control,control db_state

Your DB SID is SDB and not B2BZLOG.

Regards

Juan

Former Member
0 Kudos

^^^

I'm sorry I don't understand.

Doesn't the -d option specify the db name ?

JPReyes
Active Contributor
0 Kudos

-d is the database instance or <SID>

Regards

Juan

Former Member
0 Kudos

^^^

I'm sorry but what's a <SID> ?

I tried to use SDB as you wrote above but it tells that the database SDB does not exist.

JPReyes
Active Contributor
0 Kudos

DB SID is the name of the DB instance.... how is that you installed this again?

Former Member
0 Kudos

sdb there is the folder name where database files are.

I've tried to run the suggested command

#dbmcli -d SDB -u control,control db_state
Error! Connection failed to node (local) for database SDB:
database instance not found
#dbmcli -d sdb -u dbm,dbm db_state
Error! Connection failed to node (local) for database sdb:
database instance not found

And the maxdb manual for version 7.7 does not mention this <SID> option :

http://maxdb.sap.com/doc/7_7/44/da42a7f3b34427e10000000a155369/content.htm

Edited by: Andrea Vettori on Nov 19, 2009 1:21 PM

former_member229109
Active Contributor
0 Kudos

Hello,

1)the database instance B2BZLOG was listed in output of 'dbmcli db_enum',

so it was created.

What user/pwd did you enter, when you created B2BZLOG database?

2) "dbmcli -d B2BZLOG -u control,control db_state

Error! Connection failed to node (local) for database B2BZLOG:

-24950,ERR_USRFAIL: User authorization failed"

The combination control/control and dbm/dbm for DBM user/password is incorrect.

Did you delete any database files manually on the server?

Please check if you have KnlMsg file in the database RUNDIRectory /home/sdb/data/wrk/B2BZLOG.

If you have KnlMsg file => what is the value of CONTROLUSERID?

3) Are you SAP customer?

Thank you and best regards, Natalia Khlopina

Former Member
0 Kudos

1) the administrator user used in the creation wizard was dba,dba but this user/password combination does not work too.

2) no I haven't deleted any file manually, BUT as I said in the first post, none of the data and log file was created because the disk folder didn't have the correct permission for the database to write in.

The CONTROLUSERID value in the KnlMsg file is DBM.

But :

# dbmcli -d B2BZLOG -u DBM,DBM db_state
Error! Connection failed to node (local) for database B2BZLOG:
-24950,ERR_USRFAIL: User authorization failed

3) we're not SAP customers, we're using MaxDB on our e-commerce platform and btw it's great

Thank you !!

Melanie
Advisor
Advisor
0 Kudos

Try user dbm with password dba.

I assume that you used the 'simple' installation mode in Database Studio (or SDBSETUP), which only asks for the SYSDBA user. As the database could not really be created because of the permission problems, this user was not created either. But before the permission problem occured, the dbm user was created implicitely (with the same password).

With this user you should be able to delete the database.

Best regards,

Melanie

Former Member
0 Kudos

Dear Melanie,

dbm,dba pair works.

Thank you !!

Answers (0)