instance was executed with status ERROR NW_DB6_CreateDB2Instance

[Former Member]

Hi ,

While doing Database instance installation in HACMP , we are getting following errors.

Can u pls help me .

INFO 2008-09-21 20:52:30

Execute step CreateInstance of component |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_Cr

eateDB|ind|ind|ind|ind|0|0|NW_DB6_DB|ind|ind|ind|ind|1|0|NW_DB6_CreateDB2Instance|ind|ind|ind|ind|2|0.

INFO 2008-09-21 20:52:38

Working directory changed to /tmp/sapinst_exe.336070.1222010490.

INFO 2008-09-21 20:52:38

Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/DB6/HA/ABAP/DB.

INFO 2008-09-21 20:52:38

Working directory changed to /tmp/sapinst_exe.336070.1222010490.

INFO 2008-09-21 20:52:38

Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/DB6/HA/ABAP/DB.

INFO 2008-09-21 20:52:39

Working directory changed to /tmp/sapinst_exe.336070.1222010490.

INFO 2008-09-21 20:52:39

Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/DB6/HA/ABAP/DB.

ERROR 2008-09-21 20:52:39

MDB-01006 DBI1001I Usage:

db2icrt [-h|-?]

[-d]

[-a AuthType]

[-p PortName]

[-s InstType]

-u FencedID InstName

Explanation:

An invalid argument was entered for the db2icrt command. Valid arguments

for this command are:

-h|-? display the usage information.

-d turn debug mode on.

-a AuthType

is the authentication type (SERVER, CLIENT, or SERVER_ENCRYPT)

for the instance.

-p PortName

is the port name or port number to be used by this instance.

-s InstType is the type of instance to be created (ese,wse,

standalone, or client).

ese used to create an instance for a DB2 database server

with local and remote clients with DPF support. This

type is the default instance type for DB2 Enterprise

Server Edition.

wse used to create an instance for a DB2 database server

with local and remote clients. This type is the

default instance type for DB2 Workgroup Edition, DB2

Express or Express-C Edition, and DB2 Connect

Enterprise Edition.

standalone

used to create an instance for a DB2 database server

with local clients. This type is the default instance

type for DB2 Personal Edition.

client used to create an instance for a IBM Data Server

Client. This type is the default instance type for IBM

Data Server Client products and DB2 Connect Personal

Edition.

DB2 products support their default instance types and the

instance types lower than their default ones. For instance, DB2

Enterprise Edition supports the instance types of 'ese', 'wse',

'standalone' and 'client'.

-u FencedID

is the name of the user under which fenced UDFs and fenced

stored procedures will be run. This flag is not required if

only a IBM Data Server Client is installed.

InstName is the name of the instance.

User response:

Confirm that user IDs and group names used to create the DB2 instance

are valid. For information about naming rules, see the topic called

"User, user ID and group naming rules" in the DB2 Information Center.

Refer to the DB2 Information Center for a detailed description of the

command. Correct the syntax and reissue the command.

ERROR 2008-09-21 20:52:39

|NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8

|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_DB6_DB|ind|ind|ind|ind|1|0|NW_DB6_CreateDB2Instance|ind|ind|ind|ind|2|0|CreateI

instance was executed with status ERROR .

[Former Member · Accepted solution]

Hi ,

On 64 bit platforms for DB2 V9.1 and V9.5 you may face the problem of creating the instance. if you get this kind of problem you can check whether an instance is created and if not you can create the instance manually.

you can create the instance using the following command as the user root.

"<DB2 9.5 path>/instance/db2icrt -a SERVER_ENCRYPT -u <db2sid> <db2sid>"

after doing this you have to edit the keydb.xml for the phase NW_DB6_CreateDB2Instance change STATUS=ERROR to OK and restart the sapinst.

Hope this helps.

Thanks,

venkat.

[Thomas_Matthä]

Hi,

to me, there are two known problems when using the wrong (db2 9) XML file level with DB2 9.5 !

One is the problem with the -w parameter of db2icrt you had !

The other, I would assume that you will get this one also, is that a DB CFG parameter cannot be set to the desired value because the desired value is out of range according to for DB2 9.5

The problem you have now seems not to be related to the version mismatch.

I would suggest to determine the correct (9.5 complaint) xml files for the install and start from scratch!

Of cause you can also try to determine that dscdb6up statement SAPinst tries to execute, find out the reason for the problem, fix, execute sdcdb6up manually and set the step to OK.

kind regards

Thomas

[Former Member]

Dear Sergiy Malikov,

U r absolutely right we are using SR2 with 9.5FP1 for our installation.

Dear venkat.,

Thanks for your helpful reply.Can u pls provide u r cell number if u don't mind.

As per advise we did and success also but now we stuck up in Create database file system stage.And getting following error

ERROR 2008-09-23 20:24:37

MDB-01000 Unexpected exception caught. Cannot continue.

ERROR 2008-09-23 20:24:37

FCO-00011 The step ExecuteDscdb6up with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_D

B6_DB|ind|ind|ind|ind|1|0|NW_DB6_CreatePasswordFile|ind|ind|ind|ind|7|0|ExecuteDscdb6up was executed with status ERROR .

Please advice us how proceed .

Thanks

Partha

[Former Member]

Hello,

the most common reason for this error is the mismatch between SAP release and DB2 release which is supposed to be installed with SAP.

For example, if you are trying to install DB2 V9.5 with the SAP software which expects DB2 V9.1, such error may occur:

in newer DB2 releases, the " -w " parameter (which defines whether the instance will be 32-bit or 64-bit ) for the db2icrt command is deprecated and not supported anymore.

However, SAPInst generates the instance creation command with the " -w " parameter (which is perfectly normal for DB2 V9.1, but not for V9.5), and the installation terminates.

It is possible to avoid this error by manually creating an instance, but the occurrence of the error indicates that you are probably using the wrong DB2 release with SAP installation - so it's better to double-check the software level.

Info about the discontinued "-w" parameter:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.wn.doc/doc/i0052279.html

Kind regards,

Sergiy Malikov.

[malte_schuenemann]

Can you please tell me

o which database version you are using

o which product and version (including basis and kernel release) you intend to install

Also, can you provide the files sapinst_dev.log and control.xml ?