Tweet
It often happens that DBMS statistics though do good for most queries can turn a best performing query into worse performing piece of SQL.
Here is a process I used to raise an Grid alert when a good query turns BAD.
I have a 2 Node RAC Standby database (STDBY) . I need to replicate it as a Load TEST database (LDTEST) in a read/write mode.
To prevent unauthorized access to the Grid Control console, Enterprise Manager will automatically log you out of the Grid Control console when there is no activity for a predefined period of time. For example, if you leave your browser open and leave your office, this default behavior prevents unauthorized users from using your Enterprise Manager administrator account.
By default, if the system is inactive for 45 minutes or more, and then you attempt to perform an Enterprise Manager action, you will be asked to log in to the Grid Control console again.
Here I am duplicating 11g RAC database from one RHEL Server to Another by old 10g method.
I could have used 11g “DUPLICATE TARGET DATABASE TO TARGET_DB FROM ACTIVE DATABASE” which doesn’t need previous rman backup at source. But it may not be a good option for large databases or at places with narrow network bandwidth.
DGMGRL> show database PROD;
Object “prod” was not found
** 11.2.0.2 – You may see errors at dgmgrl if you don’t include database name in quotes
Here I will be deleting everything from a 2 node 11g RAC cluster
Although, I can use grid to carry my RMAN backups I am not entirely convinced about it’s transparency. As a DBA I like to have more control to myself and I trust my custom scripts used for years more than anything else. Here is a small process I added to raise alert for failed rman backups.
I have number of systems on grid and I want to keep grid working as smoothly as I can.
Since there are many alerts/notificatins raised & inserts/deletes happening every single minute, often repository tables will need rebuild to gain EM performance.
I have SQL script to track tables in need of a rebuild. Read more…
Often you will come across a failed Agent installation or old agent to be removed before installing new one. Here is a porocess ..
What is IBM Web Server Plug-in Analyzer for WebSphere Application Server?
Plug-in Analyzer for helps discover potential problems with trace and configuration files during use of WebSphere Application Server. The tool parses both plug-in configuration and corresponding trace files and then applies pattern recognition algorithms in order to alert users of possible inconsistencies.
Here , I wish to locate disk space acquired by a Remote target Host using df command
Please read post Using EMCLI , A command line Grid Control Interface to understand how EMCLI is used
The Enterprise Manager Command Line Interface (EM CLI) enables you to access Enterprise Manager Grid Control functionality from text-based consoles (shells and command windows) for a variety of operating systems. You can call Enterprise Manager functionality using custom scripts, such as SQL*Plus, OS shell, Perl, or Tcl, thus easily integrating Enterprise Manager functionality with a company’s business process.
Stop OMS Services
[oracle@OMS_HOST bin]$ $OMS_HOME/bin/emctl stop oms
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Stopping WebTier…
WebTier Successfully Stopped
Stopping Oracle Management Server…
Oracle Management Server Successfully Stopped
Oracle Management Server is Down
Generally we use grid for performance and availability monitoring . I have a NON- DBA user configured at a grid preferred credential. Sometimes I have to use grid to carry DBA tasks and here is a way to switch database preferred credentials & become a DBA
Navigate to TARGETs -> Select Databases you wish to run AWR reports at -> Server TAB
Oracle grid can display number of processes for a host. But I have a odd requirement where I need to keep track of oracle/java processes on the server.
By its very nature, WebSphere Application Server Network Deployment is a distributed system ranging across many machines. While few things are more stressful and frustrating than an unplanned outage, there are ways you can lessen the impact. The goal of this article is to show how you can harness deployment manger system and make recovery a quick and simple task.
To get AGENT working with OMS Grid , you will need ports 3872,4889/4900 accessible between machines.
If you wish to delete host from OMS Grid then delete Targets/Host at grid control first. Now use following SQL script to make sure it’s not exisitng at OMS repository . It will save you lot of frustration. Read more…
Following Jython script will return port listings as below. Read more…
While integrating SSO (Single Sign on) we decided to separate internal & external users. The idea was to use 2 separate URLs (internal/external) with different virtualhosts but I wanted independent control on HTTP server instances so went ahead with adding 2 separate HTTP servers. One at port 80 for internal users and another at port 8000 for external users.
I have HTTP server running at port 80 working with 2 JVMs on Websphere 6.1 vertical cluster. I will now explain process to create & link new instance of IBM HTTP server at port 8000 with existing websphere JVMs.
If you are fortunate enough to have IBM support , often you will be raising a PMR – Problem Record (IBM).
The collector tool gathers information about your WebSphere Application Server installation and packages it in a Java archive (JAR) file that you can send to IBM Customer Support to assist in determining and analyzing your problem. Information in the JAR file includes logs, property files, configuration files, operating system and Java data, and the presence and level of each software prerequisite.
We have a 2 node clustered websphere 6.x vertical cluster . Number of times we see the system going down and coming back up in less than 5 mins.
