cancel
Showing results for 
Search instead for 
Did you mean: 

Workplace Installation Error: DB instance not found

Former Member
0 Kudos

Hello all,

While installing our Developer Workplace SR2 on our workstation, we encountered an error indicating that the database instance is not found.

FYI, we were able to successfully install two without the problem . It appears that during the installation, it was able to access the database - dropping the said instance - but failed in creating the database instance afterward.

Will reward points for helpful answers.

The log is located below:

> Subprocess starts at 20080729165754

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n BASP-BMZMT1S-D -d J2E -u control,********

Execute Session Command : sql_connect superdba,********

Execute Session Command : sql_execute SELECT USERNAME FROM USERS

Execute Session Command : exit

> Subprocess stops at 20080729165754

OK

OK

END

'CONTROL'

'DBSERVICE'

'SUPERDBA'

-


> Subprocess starts at 20080729170435

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n BASP-BMZMT1S-D -d J2E -u CONTROL,******** db_state

Execute Session Command : exit

> Subprocess stops at 20080729170436

OK

State

ONLINE

-


> Subprocess starts at 20080729170436

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n BASP-BMZMT1S-D -d J2E -u CONTROL,******** db_offline

Execute Session Command : exit

> Subprocess stops at 20080729170440

OK

-


> Subprocess starts at 20080729170441

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -s -d J2E -u CONTROL,********

Execute Session Command : db_offline

Execute Session Command : db_drop

Execute Session Command : exit

> Subprocess stops at 20080729170442

OK

OK

-


> Subprocess starts at 20080729170444

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n BASP-BMZMT1S-D -d J2E -u CONTROL,********

Execute Session Command : param_startsession

> Subprocess stops at 20080729170444

> Subprocess call failed

Error! Connection failed to node BASP-BMZMT1S-D for database J2E: database instance not found

Accepted Solutions (0)

Answers (1)

Answers (1)

JPReyes
Active Contributor
0 Kudos

Well... I can't talk about the Workplace Installation because i never done one... but from looking at the logs, i can see...

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -s -d J2E -u CONTROL,********

Execute Session Command : db_offline

Execute Session Command : db_drop

Execute Session Command : exit

db_drop will delete the db instance and that's why you cant find it....

Review the installation process and try it again

Regards

Juan

Former Member
0 Kudos

Hello Juan,

Thanks for the prompt response.

As I reviewed the sequence of the installation, it appears that this could be an installation bug. The sequence does not make sense at all - it drops the database instance and starts a session after that - thus, resulting into the error.

The option I chose during installation is to recreate the default DB instance which is "J2E" that is made available during the MaxDB installation. Thus, it should recreate the "J2E" instance after the dropping of which -- this appears to be missing in the entire sequence.

The Resoultion/Workaround

Well, nothing amazing - but I just chose to make a different DB instance instead of using the existing J2E instance from MaxDB (i.e. DB1). In this approach, it does not have to drop the instance but instead create a NEW instance.

Not a definitive solution but a mere, common sense workaround. But I hope this helps those who has encountered the same issue through the same installation scenario.

Regards,

Jan