DB2 10.1 High Availability Active Passive on RHEL 5 Update 8 with Tivoli SA MP and RSCT (Reliable Scalable Cluster Technology) Done

Below are the screenshot of the status of DB2 10.1 High Availability Active Passive on RHEL 5 Update 8 with Tivoli SA MP and RSCT (Reliable Scalable Cluster Technology).

Below is the status of DB2 Level and Cluster Manager integration in Instance Configuration:

next screenshot, I will try to Switch Role of Active/Passive Nodes (Current Active Node is rhel58n2 and Passive Node is rhel58n1):

See the Request=Move(Online:O)

We will wait again for few more seconds until the Pending Online status become Online for resource IBM.Application:db2_db2ap_0-rs and IBM.Application:db2_db2ap_0-rs:rhel58n1

And now the final status of the DB2 is Online at rhel58n1, it means that the switchover processes is success.

Finally we will check on rhel58n1 (Node 01 - Active one) the status of current DB2 Database named HADB:

Great..


Note: 
There's a lot of tricky part for doing this correctly, if you do have some problem configuring DB2 HA Active Passive, or wants to just asking questions, I would be glad to help or answer, if I do have time.


- wdanyant -

Error “DB2JAVIT : RC = 9505” when starting IBM DB2 Control Center on Windows 7 Platform

After installing IBM DB2 on Windows Platform especially on Windows 7 or Windows Vista Platform, when trying to launch Control Center or some of the IBM DB2 tools, usually you will meet this error “DB2JAVIT : RC = 9505” or don't seem to do anything or not showing at all.

Here is what you need to do to fix this:

Right Click on the launch shortcut and select “Run as administrator”

And then you will successfully run the IBM DB2 Tools such as Control Center:

If on every reboot after installation you get a "SQL5005C System Error", then you should add your user account to the local DB2ADMNS or to the local DB2USERS group. These groups are created during the DB2 installation, but left empty.

- wdanyant -

Removing 90 days password expiration and loosen password restriction on Exadata Machine

After ResecureMachine Step in Exadata run, password now are required to be reset/changed and must be complex and this password will expired in 90 days.

To avoid having to reset the passwords and also to avoid the password expiration interval of 90 days, you must run the following command for each user on the system including root (i.e. root, celladmin, cellmonitor on cells and root, oracle on DB nodes): 

chage -d 14000 -E -1 -m 0 -M -1 <username>

To loosen the password restrictions and lessen complexity, login to each node as root and modify /etc/pam.d/system-auth by modifying the string "min=disabled,disabled,16,12,8" to be "min=1,1,1,1,1". After that, reset the root password to whatever value you'd like (suggestion: welcome1 :). 

- wdanyant -