Error Installing on virtual host

[Former Member]

Hi all,

I try to install (system copy) CRM4.0 virtualized on 2 hosts, node_A (for Central Instance) and node_B (for Database Instance) on one physical box (AIX 5.3, DB2 Version 9.1 Fixpack 2).

For this i use the sapinst parameter SAPINST_USE_HOSTNAME=node_A. The Central Installation went through smoothly. Then i change the physical hostname of my AIX to node_B for the DB-installation, without SAPINST_USE_HOSTNAME.

In the step where i have to define the filesystem where my database export is (Software Package Check) i get this error:

ERROR 2007-11-06 09:18:42
CJSlibModule::writeError_impl()
MUT-03010 Execution of the command "db2 -tvf last_command.sql -r last_command.res -z last_command.out" finished with status TST_ERROR.

I think my installation has problems with cataloging the database in the database catalog...

thanks, günther

[Former Member]

Hi Günther

1. client/ese database instance

this is choosen according to sapinst parameters and hostnames . Usually when installing remote , an client instance is created and when installing on database server an ESE instance needs to be created .

I suppose , since you changed the hostname , sapinst did not detect , it was running on DB Host and created an client instance .

This will in fact cause problems later , when trying to install the database instance

For an proper analysis , what went wrong , we need to analyse the entire installation .

If you want to get this diagnosed , please open an OSS-message and provide the installation directories .

Best regards

dirk

[Former Member]

Hi Dirk,

I am facing one issue i have installed ASCS, SCS, CI,DB on Node A using virtual host name, and the server is running fine, i am trying to install DI on Node B should i use Virtual hostname of the physical hostname of Node B.

Please advise.

Regards,

Najeeb ..

[Former Member]

Mr.SharkMachine:

Are you doing a high-availability install?

[Former Member]

Hello Günther

please perform the following procedure :

1. logon as db2<db2sid> 
2. change to sapinst_instdir
3. run the following command
   db2 -tvf last_command.sql -r last_command.res -z last_command.out

please tell us your results or errors of step 3 .

Best regards

dirk

[Former Member]

Good morning,

sapinst is really weird. In the step where sapinst has to create the database instance (thats the first part of the installation, Central instance installation) i found this in sapinst_dev.log:

TRACE

CDB6Instance::executeCommand(iastring, iastring, iastring, ISyslibFactory*)

lib=iamoddb6 module=CDB6Instance

Executable: /db2/db2dcr/db2_software/instance/db2icrt

TRACE

CDB6Instance::executeCommand(iastring, iastring, iastring, ISyslibFactory*)

lib=iamoddb6 module=CDB6Instance Arguments : -a SERVER_ENCRYPT -s client -w 64 -u db2dcr db2dcr

TRACE

CSyTaskImpl::start(bool) lib=iamoddb6 module=CDB6Instance A child process has been started. Pid = 1110170

Explanation: (db2icrt creates db-instance) db2icrt -a SERVER_ENCRYPT -s client -w 64 -u db2dcr db2dcr

===> "-s client" = client installation ?
===> "-w 64" = unknown switch, old one...

Furthermore i have seen that also IBM has some strange entries in their scripts, for example in db2icrt (i installed V9 Fixpack 2)
db2licm -v
9.1

# NAME: db2icrt
#
1. FUNCTION: db2icrt - creates a DB2 V8 instance.
#

===> Version 8 ???

Back to your question:
When i run the script with -tvf then the script is able to start the database. but a connect is not possible:

db2start
DB20000I The DB2START command completed successfully.

connect to DCR
SQL1224N The database manager is not able to accept new requests, has
terminated all requests in progress, or has terminated your particular request
due to a problem with your request. SQLSTATE=55032

While he tries to open a connection to the database he forkes alot of db2agents

% db2_ps | grep db2agent | wc -l
200

% db2 get dbm cfg | grep -i agents
Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 400
Agent pool size (NUM_POOLAGENTS) = 200(calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0

Back to my assumption:
I guess the root cause has something to do with the uncorrect database instance creation above (central instance). sapinst is not able to create a proper db instance (...client, see above). so i do this step manually. then sapinst cataloges the database:

% db2 list db directory

System Database Directory

Number of entries in the directory = 1

Database 1 entry:

Database alias = DCR
Database name = DCR
Node name = NODEDCR
Database release level = b.00
Comment = Remote database DCR
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =

% db2 list node directory

Node Directory

Number of entries in the directory = 1

Node 1 entry:

Node name = NODEDCR
Comment = TCPIP Node for database DCR
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = sapdcr00
Service name = sapdb2DCR

...so long, günther