Sponsored Content
Operating Systems AIX HACMP does not start db2 after failover (db2nodes not getting modified by hacmp) Post 302517094 by funksen on Tuesday 26th of April 2011 04:41:49 AM
Old 04-26-2011
the modification is not built in, so you manually have to make it

there must be an application server configured on your cluster, search for that script, and try to add my lines, with your paths of course

db2 checks, if the local hostname is equal with the hostname in db2nodes.cfg

if not, the database wont come up


maybe there is another method to achive this, but simply editing db2nodes.cfg worked fine for me for years now


changing the hostname in the cluster is another solution to solve this problem, but this may lead to problems with other applications

Last edited by funksen; 04-26-2011 at 06:42 AM..
 

10 More Discussions You Might Find Interesting

1. AIX

Hacmp

(0 Replies)
Discussion started by: mhenryj
0 Replies

2. AIX

HACMP (Again)

Hello I am a noobie to HACMP I have 2 55A servers and a 7031 disk subsystem For HACMP to work, do I need to have the hdisks on both servers to match the same drives?? The hdisks on each box are currently different: hdisk0 and hdisk1 are the internal disks and hdisk2-5 are on the D24 on... (1 Reply)
Discussion started by: mhenryj
1 Replies

3. AIX

Can anyone shed some light on this HACMP failover?

Hello All, Here is a snipet from our cluster.log, I was wondering if anyone could shed some light on what may have caused the failover. The first two lines indicate a possible memory issue which I am currently looking into. Thanks. (0 Replies)
Discussion started by: Wez
0 Replies

4. HP-UX

HACMP in HP-UX

Hi, Can anybody advice whether it is possible to configure HACMP in HP-UX Server. To my knowledge HACMP is IBM Solution. Thanks && Regards, N. Poorna Chandra Rao. (2 Replies)
Discussion started by: npcrao
2 Replies

5. AIX

failover on 4.5 hacmp

Hi All, How do I trigger the failover on the second hacmp server? Please give me idea and I will do the rest. Thanks, itik (2 Replies)
Discussion started by: itik
2 Replies

6. AIX

hacmp upgrade with db2

Hi All, My company is going to upgrade the db2 on the one node hacmp, I think there's one backup. After the upgrade of the db2. Do I need to restart cluster and server? I mean, do a graceful shutdown of the cluster, reboot the server and do a cluster start. Is that it? Do I need to reboot... (1 Reply)
Discussion started by: itik
1 Replies

7. AIX

hacmp ip load balancer failover

Hi All, How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive). Any idea, please. Thanks in advance. (0 Replies)
Discussion started by: itik
0 Replies

8. AIX

NFS won't work till I start HACMP

Hi, My NFS does not work till I start HACMP. The NFS service is indeed started when server starts. But it is not in active state, when I use lssrc to check NFS services' status I find they are all in inoperative status. But after I start HACMP (smitty clstart), all NFS services become active... (4 Replies)
Discussion started by: qiulang
4 Replies

9. AIX

HACMP with VIO, service IP failover

Would anyone please kindly help to solve this problem... An LPAR with the below network configuration. ent0 and ent1 are logical lan (virtual ethernet) from VIO SEA. en0 1.2.3.4 <- boot ip 192.168.1.1 <- persistent ip 192.168.1.10 <- service ip en1 11.22.33.44 <- boot ip When I... (6 Replies)
Discussion started by: skeyeung
6 Replies

10. AIX

Thoughts on HACMP: Automatic start of cluster services

Hi all, I remember way back in some old environment, having the HA cluster services not being started automatically at startup, ie. no entry in /etc/inittab. I remember reason was (taken a 2 node active/passive cluster), to avoid having a backup node being booted, so that it will not... (4 Replies)
Discussion started by: zaxxon
4 Replies
BOOTSTRAP(5)						   Sun Grid Engine File Formats 					      BOOTSTRAP(5)

NAME
bootstrap - Sun Grid Engine bootstrap file DESCRIPTION
bootstrap contains parameters that are needed for the startup of Sun Grid Engine components. It is created during the sge_qmaster instal- lation. Modifying bootstrap in a running system is not supported. FORMAT
The paragraphs that follow provide brief descriptions of the individual parameters that compose the bootstrap configuration for a Sun Grid Engine cluster: admin_user Administrative user account used by Sun Grid Engine for all internal file handling (status spooling, message logging, etc.). Can be used in cases where the root account does not have the corresponding file access permissions (e.g. on a shared file system without global root read/write access). Being a parameter set at installation time changing admin_user in a running system is not supported. Changing it manually on a shut-down cluster is possible, but if access to the Sun Grid Engine spooling area is interrupted, this will result in unpredictable behavior. The admin_user parameter has no default value, but instead it is defined during the master installation procedure. default_domain Only needed if your Sun Grid Engine cluster covers hosts belonging to more than a single DNS domain. In this case it can be used if your hostname resolving yields both qualified and unqualified hostnames for the hosts in one of the DNS domains. The value of default_domain is appended to the unqualified hostname to define a fully qualified hostname. The default_domain parameter will have no effect if ignore_fqdn is set to "true". Being a parameter set at installation time changing default_domain in a running system is not supported. The default for default_domain is "none", in which case it will not be used. ignore_fqdn Ignore fully qualified domain name component of hostnames. Should be set if all hosts belonging to a Sun Grid Engine cluster are part of a single DNS domain. It is switched on if set to either "true" or "1". Switching it on may solve problems with load reports due to different hostname resolutions across the cluster. Being a parameter set at installation time changing ignore_fqdn in a running system is not supported. The default for ignore_fqdn is "true". spooling_method Defines how sge_qmaster(8) writes its configuration and the status information of a running cluster. The available spooling methods are berkeleydb and classic. spooling_lib The name of a shared library containing the spooling_method to be loaded at sge_qmaster(8) initialization time. The extension characteriz- ing a shared library (.so, .sl, .dylib etc.) is not contained in spooling_lib. If spooling_method was set to berkeleydb during installation, spooling_lib is set to libspoolb, if classic was chosen as spooling_method, spooling_lib is set to libspoolc. Not all operating systems allow the dynamic loading of libraries. On these platforms a certain spooling method (default: berkeleydb) is compiled into the binaries and the parameter spooling_lib will be ignored. spooling_params Defines parameters to the chosen spooling method. Parameters that are needed to initialize the spooling framework, e.g. to open database files or to connect to a certain database server. The spooling parameters value for spooling method berkeleydb is [rpc_server:]database directory, e.g. /sge_local/default/spool/qmas- ter/spooldb for spooling to a local filesystem, or myhost:sge for spooling over a Berkeley DB RPC server. For spooling method classic the spooling parameters take the form <common_dir>;<qmaster spool dir>, e.g. /sge/default/com- mon;/sge/default/spool/qmaster binary_path The directory path where the Sun Grid Engine binaries reside. It is used within Sun Grid Engine components to locate and startup other Sun Grid Engine programs. The path name given here is searched for binaries as well as any directory below with a directory name equal to the current operating sys- tem architecture. Therefore, /usr/SGE/bin will work for all architectures, if the corresponding binaries are located in subdirectories named aix43, cray, lx24-x86, hp11, irix65, tru64, sol-sparc, etc. The default location for the binary path is <sge_root>/bin qmaster_spool_dir The location where the master spool directory resides. Only the sge_qmaster(8) and sge_shadowd(8) need to have access to this directory. The master spool directory - in particular the job_scripts directory and the messages log file - may become quite large depending on the size of the cluster and the number of jobs. Be sure to allocate enough disk space and regularly clean off the log files, e.g. via a cron(8) job. Being a parameter set at installation time changing qmaster_spool_dir in a running system is not supported. The default location for the master spool directory is <sge_root>/<cell>/spool/qmaster. security_mode The security mode defines the set of security features the installed cluster is using. Possible security mode settings are none, afs, dce, kerberos, csp. (no additional security, AFS, DCE, KERBEROS, CSP security model). listener_threads The number of listener threads (defaults set by installation). worker_threads The number of worker threads (defaults set by installation). scheduler_threads The number of scheduler threads (allowed: 0-1, default set by installation: 1, off: 0). (see qconf(1) -kt/-at option) jvm_threads The number of jvm threads (allowed: 0-1, default set by installation, off: 0). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ BOOTSTRAP(5)
All times are GMT -4. The time now is 06:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy