Topic
No replies
SystemAdmin
SystemAdmin
17917 Posts
ACCEPTED ANSWER

Pinned topic Installation error database partion phase error in DB2 on SAP

‏2012-11-08T06:12:06Z |
Dear Experts,

We are facing a dataase partition phase error in DB2 9.7 LUW on SAP.

Pls find the logs for your reference

SAPINST.LOG::::::::::::::

WARNING 2012-11-08 06:26:06.058
Execution of the command "db2 -tvf createDatabasePartitionGroup.sql -r createDatabasePartitionGroup.res -z createDatabasePartitionGroup.out" finished with return code 4. Output:
UPDATE COMMAND OPTIONS USING S OFF
DB20000I The UPDATE COMMAND OPTIONS command completed successfully.

UPDATE COMMAND OPTIONS USING A OFF
DB20000I The UPDATE COMMAND OPTIONS command completed successfully.

UPDATE COMMAND OPTIONS USING X ON
DB20000I The UPDATE COMMAND OPTIONS command completed successfully.

UPDATE COMMAND OPTIONS USING O ON
DB20000I The UPDATE COMMAND OPTIONS command completed successfully.

UPDATE COMMAND OPTIONS USING N OFF
DB20000I The UPDATE COMMAND OPTIONS command completed successfully.

CREATE DATABASE PARTITION GROUP SAPNODEGRP_KSM ON DBPARTITIONNUMS( 0 )
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1032N No start database manager command was issued. SQLSTATE=57019

CREATE DATABASE PARTITION GROUP NGRP_FACT_KSM ON DBPARTITIONNUMS( 0 )
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1032N No start database manager command was issued. SQLSTATE=57019

CREATE DATABASE PARTITION GROUP NGRP_ODS_KSM ON DBPARTITIONNUMS( 0 )
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1032N No start database manager command was issued. SQLSTATE=57019

CREATE DATABASE PARTITION GROUP NGRP_DIM_KSM ON DBPARTITIONNUMS( 0 )
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1032N No start database manager command was issued. SQLSTATE=57019

TERMINATE
DB20000I The TERMINATE command completed successfully.

ERROR 2012-11-08 06:26:06.94
MDB-01999 Error occured, first error is: <SQL1032N No start database manager command was issued. SQLSTATE=57019>

ERROR 2012-11-08 06:26:06.095
MUT-03025 Caught ESAPinstException in module call: .

ERROR 2012-11-08 06:26:06.199
FCO-00011 The step CreateNodegroups with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_CreateDB|ind|ind|ind|ind|createdb|0|NW_DB6_DB|ind|ind|ind|ind|1|0|NW_DB6_CreateNodegroups|ind|ind|ind|ind|25|0|CreateNodegroups was executed with status ERROR ( Last error reported by the step: Error occured, first error is: <SQL1032N No start database manager command was issued. SQLSTATE=57019>).

INFO 2012-11-08 06:26:06.924
Creating file /tmp/sapinst_instdir/SOLMAN71SR1/SYSTEM/DB6/CENTRAL/AS/__instana_tmp.xml.

INFO 2012-11-08 07:11:44.572
An error occured and the user decided to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_CreateDB|ind|ind|ind|ind|createdb|0|NW_DB6_DB|ind|ind|ind|ind|1|0|NW_DB6_CreateNodegroups|ind|ind|ind|ind|25|0|CreateNodegroups".

INFO 2012-11-08 07:11:48.100
Working directory changed to /tmp/sapinst_instdir/SOLMAN71SR1/SYSTEM/DB6/CENTRAL/AS.

INFO 2012-11-08 07:11:48.124
Creating file /tmp/sapinst_instdir/.lastInstallationLocation.

INFO 2012-11-08 07:11:50.130
Cancelled task 0.

Thanks,
Thamu.