Tuesday, July 17, 2012

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 -



Saturday, June 30, 2012

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 -

How to change user to root when using oracle user on Exadata

How to change user to root when using oracle user on Exadata?
When trying to su to "root" user as "oracle", eventhough the password is correct, always showing incorrect password.

[oracle@server ~]$ su - root
Password:
su: incorrect password
[oracle@server ~]$

This is because of the "oracle" user is not a member of wheel group and this was done purposely by the Oracle Exadata Team.

If we want to do su to "root" user, just try solution below:

Add the oracle user to the wheel group.
usermod -G wheel oracle


- wdanyant -