Following Script will display attributes for each configuration item/element displayed at each “level” Read more…
After successful websphere install one will see “first steps” page as below.
The first failure data capture (FFDC) feature preserves the information that is generated from a processing failure and returns control to the affected engines. The captured data is saved in a log file for analyzing the problem. FFDC is intended primarily for use by IBM Service.
When stopping and restarting application servers, it is important to consider the correlation with the Web server plug-in retry interval. This is especially important in an environment with only a few application servers. You need to understand the rate between starting and stopping application servers in a cluster and the retry interval so that you do not get HTTP request failures when you stop application servers in a cluster.
I had a working datagard configuration between 1 primary and 2 physical standby systems. Today I noticed my dataguard configuration files were missing from all servers (Primary/Standby).
Create .run_awr with following details :
"TNS-connect-string : recipient-list : hrs of AWR snapshot" [oracle@ ~]$ cat .run_awr prod:email@example.com:11 I added this script in my crontab for a daily emails:
In this post, I will show you how easy it is to fail-over on standby dataguard database when primary is not available. Read more…
This morning I moved my Standby database from Maxperformance to Maxprotection while it returned ORA-16826
Following post will give you an idea on Dataguard data protection mode in which you want configuration to run when configuration is enabled. The possible protection modes are: Read more…
|ADD DATABASE||Adds a new standby database profile to the existing broker configuration Read more…|
DGMGRL : ORA-16789: standby redo logs not configured/ORA-16826: apply service state is inconsistent with the DelayMins property
My DGMGRL configuration is returning warnings as below.
DGMGRL> show database primary;
Database – primary
Intended State: TRANSPORT-ON
ORA-16789: standby redo logs not configured
Generally you don’t have to set up Dataguard on a single machine. But there are occasions when you have to build test environment for destruction and this post is tuned for such opportunity.
Check if previous version installed by root
If WAS was previously installed as root, it would have created the temp dir /tmp/niflogs, owned by root. When you install as was61, it needs to write to this dir, so remember to chown / chmod this dir, or the install will fail in a very obscure way.
IBM’s JVM is written to meet the specs as documented by Sun. IBM runs the test suit against their JVM to make sure that what should occur does occur. They (IBM) feel that their code performs the requested functions more efficiently and thus performs better while still providing the same results. IBM may throw one error exception while Sun’s may throw another.
I have One Primary database and 2 Physical Standby Databases under RHEL 5. Here is a process to patch them with JULY CPU update “Critical Patch Update Release 10.2.0.4 for UNIX Released July 13, 2010″
The isAppReady command returns a value of true if the system is ready to start the application, or a value of false if the system is not ready to start the application, as the following examples display: Read more…
Currently I have number of websphere 6.1 instances under RHEL 5.3 but not a tool like hyperic, wily introscope to monitor them actively. I started using wsadmin scripts to pull out stats thru wsadmin.
p=$(lsof -t -i :1159); echo $p $(tr ‘\0′ ‘\n’ < /proc/$p/cmdline | tail -1)
Please use following process when you have PerfServelet (PervServletApp application ) generated offline XML files.
I will list here steps carried out to patch websphere 6.1. ND deployment (vertical cluster with 2 JVMs ) from 18.104.22.168 to 22.214.171.124
I was looking for a NAGIOS monitoring script which will list the archive gap between Primary and 2 of my Standby databases.
I have many websphere 6.x ND clustered servers and growing every single week. Lots of them are upgraded from previous websphere installations to ND 6.x now.