Error while creating database instance in installation of Netweaver 2004s

[Former Member]

Error in Installation-SAP Netweaver 2004s on AIX 5.3 usingMaxDB as database

I have pasted error log below.

Please Help.

ERROR 2007-03-09 13:48:53

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

ERROR 2007-03-09 13:48:53

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

ERROR 2007-03-09 13:48:53

FCO-00011 The step sdb_init_instance_type with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_init_instance_type was executed with status ERROR .

[andreas_herzog · Accepted solution]

-> what does logile "XCMDOUT.LOG" say?

-> any infos from the knldiag?

GreetZ, AH

[Former Member · Accepted solution]

Hi

Please help.

XCMDOUT.LOG shows the following things:

-

---

> Subprocess starts at 20070309134754

Execute Command : /sapdb/programs/bin/dbmcli -n punlparidm06 inst_enum

Start subprocess as user with uid: root

> Subprocess stops at 20070309134759

OK

7.6.00.35 /sapdb/IND/db

-

---

> Subprocess starts at 20070309134804

Execute Command : /sapdb/programs/bin/dbmcli -n punlparidm06 inst_enum

Start subprocess as user with uid: root

> Subprocess stops at 20070309134805

OK

7.6.00.35 /sapdb/IND/db

-

---

> Subprocess starts at 20070309134806

Execute Command : /sapdb/programs/bin/dbmcli -n punlparidm06 inst_enum

Start subprocess as user with uid: root

> Subprocess stops at 20070309134806

OK

7.6.00.35 /sapdb/IND/db

-

---

> Subprocess starts at 20070309134806

Execute Command : /sapdb/programs/bin/dbmcli -R /sapdb/IND/db dbm_version

Start subprocess as user with uid: root

> Subprocess stops at 20070309134807

OK

VERSION = 7.6.00

BUILD = DBMServer 7.6.00 Build 035-123-139-084

OS = UNIX

INSTROOT = /sapdb/IND/db

LOGON = True

CODE = ASCII

SWAP = normal

UNICODE = (unknown)

INSTANCE = (unknown)

SYSNAME = AIX

-

---

> Subprocess starts at 20070309134807

Execute Command : /sapdb/programs/bin/dbmcli -n punlparidm06 inst_enum

Start subprocess as user with uid: root

> Subprocess stops at 20070309134808

OK

7.6.00.35 /sapdb/IND/db

-

---

> Subprocess starts at 20070309134827

Execute Command : /sapdb/programs/bin/dbmcli -n punlparidm06 inst_enum

Start subprocess as user with uid: root

> Subprocess stops at 20070309134828

OK

7.6.00.35 /sapdb/IND/db

-

---

> Subprocess starts at 20070309134833

Execute Command : /sapdb/programs/bin/dbmcli -n punlparidm06 db_enum

Start subprocess as user with uid: root

> Subprocess stops at 20070309134836

OK

IND /sapdb/IND/db 7.6.00.35 fast running

IND /sapdb/IND/db 7.6.00.35 quick offline

IND /sapdb/IND/db 7.6.00.35 slow offline

IND /sapdb/IND/db 7.6.00.35 test offline

-

---

> Subprocess starts at 20070309134842

Execute Command : /sapdb/programs/bin/dbmcli -n punlparidm06 -d IND -u CONTROL,********

Start subprocess as user with uid: root

Execute Session Command : param_startsession

Execute Session Command : param_init OLTP

> Subprocess stops at 20070309134853

OK

ERR

-24976,ERR_PARAMEXIST: param file of database already exists

[andreas_herzog · Accepted solution]

"<i>A parameter file already exists for the specified database instance. The parameter file can be initialized only if no parameter file exists. This prevents the configuration from being lost.</i>"

-> "delete the parameter file either at file-system level or using the DBM command param_rmfile (this will mean that the current database instance configuration will be lost)"

SAP states:

"<i>Deleting the Database Parameter File

Use this command with great care.

With the command param_restore (Resetting the Parameter File to a Previous Version), you can restore the version of the parameter file that was valid before the deletion.

You have the server authorization InstallMgm.

<b>Syntax: param_rmfile</b>

The system displays an OK message.

In the event of errors, see Reply Format</i>"

GreetZ, AH

[Former Member · Accepted solution]

Will it work, if I'll change the name of existing parameter file?

So, it will keep back up of the file as well.

[andreas_herzog · Accepted solution]

yup..moving/renaming is always first choice gg

GreetZ, AH

[Former Member · Accepted solution]

Where does the parameter file gets stored?

Message was edited by:

login

[Former Member · Accepted solution]

Hi

I am not able to search the location of file ERR_PARAMEXIST.

Will you please tell me how can I find it.

Is there any command for searching file?

[Former Member · Accepted solution]

Which file should I rename?

1. pwd

/

1. find . -name "param"

./usr/sap/IND/DVEBMGS00/j2ee/JSPM/deploy/param

find: 0652-023 Cannot open file ./proc/315484.

1. cd /usr/sap/IND/DVEBMGS00/j2ee/JSPM/deploy/param/

2. ls

TroubleTicket.txt jspm_config.txt logging.properties phaselist_jspm.xml

#

Message was edited by:

login

[andreas_herzog · Accepted solution]

<b>ERR_PARAMEXIST is not a file...it's simply an error code...</b>

delete the parameter "file" using database manager...

GreetZ, AH

[Former Member · Accepted solution]

Hi,

The default parameter file is named "cserv.pcf", and must be in your DB path, into .../env/ directory.

Maybe taking a look at the MaxDB documentation will help you

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/maxdb">MaxDB doc.</a>

Best Regards,

JC Llanes.

[Former Member · Accepted solution]

Thanks a lot

I'll try this

Message was edited by:

login