Installation error on solution manager 7.1 at phase 17

[former_member1334776]

Dear Experts,

I am facing error while installation error in phase 17 i had attached trace files for your referance

OS:Linux 11

DB:DB2

ERROR;

An error occurred while processing option SAP Solution Manager 7.1 SR1 > SAP Systems > IBM DB2 for Linux, UNIX, and Windows > Central System > Central System( Last error reported by the step: Error occured, first error is:  ). You can now:

Choose Retry to repeat the current step.

Choose Log Files to get more information about the error.

Stop the option and continue with it later.

Log files are written to /tmp/sapinst_instdir/SOLMAN71SR1/SYSTEM/DB6/CENTRAL/AS.

Trace File :

TRACE

2012-11-08 03:03:51.934

SAPinst was started using commandline: /tmp/sapinst_exe.5872.1352323964/sapinstexe

TRACE

2012-11-08 03:03:51.934

SAPinst properties are :

GUISERVER_DIALOG_PORT=21211

GUISERVER_HTTP_PORT=4238

SAPINST_CHECK_PACKAGES=false

SAPINST_CONTROL_URL=control.xml

SAPINST_DIALOG_PORT=21201

SAPINST_DIALOG_URL=dialog.xml

SAPINST_EXE=SAPINST_EXE

SAPINST_JSLIB_TRACE=NW,NWUsers,OraCom,NWCTC,ClusterMgt,SystemIdentity

SAPINST_KEYDB_URL=keydb.xml

SAPINST_MESSAGE_CONSOLE_THRESHOLD=info

SAPINST_MESSAGE_URL=.

SAPINST_PACKAGES_URL=packages.xml

SAPINST_RESOURCE_URL=resourcepool.xml

SAPINST_SAVE_INPUT=true

SAPINST_SCAN_DEVICES=false

SAPINST_SKIP_DIALOGS=false

SAPINST_TOPLEVEL_URL=toplevel.xml

SAPINST_USE_ADVANCED_JS_HANDLING=true

SELFEXTRACTOR_EXECUTABLE_NAME=/dump/inst_masters/DATA_UNITS/SM71SR1_IM_LINUX_X86_64/./sapinst

Pls Guide me how to proceed furture.

Thanks,

Thamu.

[Former Member]

Hi,

Please check the directory /tmp/sapinst_instdir/SOLMAN71SR1/SYSTEM/DB6/CENTRAL/AS

sapinst.log and sapinst_dev.log would have got updated with the error details. At which phase you get the error? Is it after giving the input parameters and during installation?

Regards,

Srikishan

[former_member1334776]

Dear Krishna,

Thanks for your help........

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

[Former Member]

Hello Thamu,

Log says:

<SQL1032N  No start database manager command was issued.  SQLSTATE=57019>).

Try from your OS as db2<SID> run the command db2start  and trigger again installation.

BR,

SAPFan

[former_member1334776]

Dear BR,

I tried in same and now it is fine i am facing now error as said below

RROR 2012-11-09 00:12:17.571

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: <SQL1762N  Unable to connect to database because there is not enough space to >).

INFO 2012-11-09 00:12:18.137

Creating file /tmp/sapinst_instdir/SOLMAN71SR1/SYSTEM/DB6/CENTRAL/AS/__instana_tmp.xml.

INFO 2012-11-09 00:21:53.824

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".

Thanks,

Thamu.

[Former Member]

Hello Thamu,

Log clearly says:

<SQL1762N  Unable to connect to database because there is not enough space to >).

Please check frOm OS level command df -k and df -g. I suppose you don`t have free space for SAPDATA`S.

BR,

SAPFan

[former_member1334776]

hi BR,

I checked all requried space are availale........

Pls find the elow logs

solman:db2ksm 51> db2 get db cfg for KSM | grep -i log

Log retain for recovery status                          = NO

User exit for logging status                            = NO

Catalog cache size (4KB)              (CATALOGCACHE_SZ) = 2560

Log buffer size (4KB)                        (LOGBUFSZ) = 512

Log file size (4KB)                         (LOGFILSIZ) = 16380

Number of primary log files                (LOGPRIMARY) = 60

Number of secondary log files               (LOGSECOND) = 0

Changed path to log files                  (NEWLOGPATH) =

Path to log files                                       = /db2/KSM/log_dir/NODE0000/

Overflow log path                     (OVERFLOWLOGPATH) =

Mirror log path                         (MIRRORLOGPATH) =

First active log file                                   =

Block log on disk full                (BLK_LOG_DSK_FUL) = NO

Block non logged operations            (BLOCKNONLOGGED) = NO

Percent max primary log space by transaction  (MAX_LOG) = 0

Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0

Percent log file reclaimed before soft chckpt (SOFTMAX) = 200

Log retain for recovery enabled             (LOGRETAIN) = OFF

User exit for logging enabled                (USEREXIT) = OFF

HADR log write synchronization mode     (HADR_SYNCMODE) = NEARSYNC

First log archive method                 (LOGARCHMETH1) = OFF

Options for logarchmeth1                  (LOGARCHOPT1) =

Second log archive method                (LOGARCHMETH2) = OFF

Options for logarchmeth2                  (LOGARCHOPT2) =

Failover log archive path                (FAILARCHPATH) =

Number of log archive retries on error   (NUMARCHRETRY) = 5

Log archive retry Delay (secs)         (ARCHRETRYDELAY) = 20

Log pages during index build            (LOGINDEXBUILD) = OFF

Thanks,

Thamu.

[Former Member]

Hi Thamu,

Please read documentation about SQL error:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=%2Fcom.ibm.db2.luw.messages.sql...

Also check this post http://scn.sap.com/thread/2036794 error looks similiar to yours.

BR,

SAPFan

[former_member1334776]

hi BR,

I checked all requried space are availale........

Pls find the elow logs

solman:db2ksm 51> db2 get db cfg for KSM | grep -i log

Log retain for recovery status                          = NO

User exit for logging status                            = NO

Catalog cache size (4KB)              (CATALOGCACHE_SZ) = 2560

Log buffer size (4KB)                        (LOGBUFSZ) = 512

Log file size (4KB)                         (LOGFILSIZ) = 16380

Number of primary log files                (LOGPRIMARY) = 60

Number of secondary log files               (LOGSECOND) = 0

Changed path to log files                  (NEWLOGPATH) =

Path to log files                                       = /db2/KSM/log_dir/NODE0000/

Overflow log path                     (OVERFLOWLOGPATH) =

Mirror log path                         (MIRRORLOGPATH) =

First active log file                                   =

Block log on disk full                (BLK_LOG_DSK_FUL) = NO

Block non logged operations            (BLOCKNONLOGGED) = NO

Percent max primary log space by transaction  (MAX_LOG) = 0

Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0

Percent log file reclaimed before soft chckpt (SOFTMAX) = 200

Log retain for recovery enabled             (LOGRETAIN) = OFF

User exit for logging enabled                (USEREXIT) = OFF

HADR log write synchronization mode     (HADR_SYNCMODE) = NEARSYNC

First log archive method                 (LOGARCHMETH1) = OFF

Options for logarchmeth1                  (LOGARCHOPT1) =

Second log archive method                (LOGARCHMETH2) = OFF

Options for logarchmeth2                  (LOGARCHOPT2) =

Failover log archive path                (FAILARCHPATH) =

Number of log archive retries on error   (NUMARCHRETRY) = 5

Log archive retry Delay (secs)         (ARCHRETRYDELAY) = 20

Log pages during index build            (LOGINDEXBUILD) = OFF

Thanks,

Thamu.

[Former Member]

Hi,

Please increase this parameter Number of secondary log files (LOGSECOND) = 0 and check connection again.

command:

UPDATE DATABASE CONFIGURATION FOR KSM USING LOGSECOND 2

[former_member1334776]

Dear Team,

I tried with the same command before it throws again a error

Pls find the error

solman:db2ksm 52> db2 update db cfg  for KSM using LOGSECOND 50

SQL1762N  Unable to connect to database because there is not enough space to

allocate active log files.  SQLSTATE=08004

What i have to do to go head.

Thanks,

Thamu

[Former Member]

Hi,

Read this post http://www.dbforums.com/db2/1683494-not-enough-space-allocate-active-log-files-error-while-login.htm... There is command with chagning db2 parameters with new log:

db2 update db cfg for IMRM2 using NEWLOGPATH XXXXXXXXXXXXXXXX

and this resolution:

http://www.db2india.in/forum/topics/connect-to-db-throws-sql1762n

IMO there is no free space for DB2 log or sapdata`s. Please put command df -g or df -m printscreen.

BR,

SAPFan