Error in phase 11-Sneak Preview SAP NetWeaver 04s - Full ABAP Edition with

[Former Member]

I install Sneak Preview 2004s Full ABAP Edition and get stuck in phase 11 with following errors :

ERROR 2006-01-29 20:42:09

CJSlibModule::writeError_impl()

The dbmcli call for action ACTIVATE failed. Check the logfile XCMDOUT.LOG.

ERROR 2006-01-29 20:42:09

CJSlibModule::writeError_impl()

The dbmcli call for action ACTIVATE failed. Check the logfile XCMDOUT.LOG.

ERROR 2006-01-29 20:42:09

FCO-00011 The step sdb_instance_activate with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_CreateDB|ind|ind|ind|ind|9|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|2|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_instance_activate was executed with status ERROR .

and this the last step info i got from XCMDOUT.txt in C:\Program Files\sapinst_instdir\NW04S\LM\COPY\ADA\SYSTEM\CENTRAL\AS-ABAP :

> Subprocess starts at 20060129204205

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n personal -d NSP -u CONTROL,********

Execute Session Command : util_connect

Execute Session Command : db_activate SUPERDBA,********

Execute Session Command : exit

> Subprocess stops at 20060129204209

OK

ERR

-24988,ERR_SQL: Sql error

-2014,Identifier too long

Does anybody can help to solve this error ?

Thanks in advance

Sukiman

[Former Member]

fortunately i have installed my system successfully.

the problem is probably the password for maxDB.

give your password : admin for all the requested password during setup dialog.

my computer used 1 GB memory, but for 256 MB as your question, i think it's absolutely not sufficient, since

the system load is heavy. for mine, it's took about 5 hour to install.

[Former Member]

I have a second question?

are they 1 GB RAM compulsory necessary?

Or suffice 256 MB RAM?

[Former Member]

I have a problemm, too in Phase 11 "Database Instance Creation"

I get following Error:

ERROR 2006-01-30 17:54:37

The dbmcli call for action ACTIVATE failed. Check the logfile XCMDOUT.LOG.

ERROR 2006-01-30 17:54:37

The dbmcli call for action ACTIVATE failed. Check the logfile XCMDOUT.LOG.

ERROR 2006-01-30 17:54:37

FCO-00011 The step sdb_instance_activate with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_CreateDB|ind|ind|ind|ind|9|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|2|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_instance_activate was executed with status ERROR .

I hope anybody can help me

greetings

Florian

[Former Member]

i have checked as your solution,and i see sapdb : NSP service already start, but i still get stuck with this phase. i try to execute below command directly from MaxDB console (by running dbmcli.exe) :

db_activate SUPERDBA,********

and i got this error msg : 2014,Identifier too long

it seems NSP db can't be activate, but still just don't know how to correct this error.

any other suggestion pls ?

thanks in advance

Sukiman

[athavanraja]

check in windows services whether SAPDB:NSP services are running.

Regards

Raja