Database Servers are humming along, and the people who manage them, interact with them or are just in awe of them are busy in blogging about them. This inspires our next Log Buffer, Log Buffer #214. Oracle: Chet Justice, the Oracle Nerd breathes a sigh of relief as he gets to release some much needed [...]
Last year I have presented a couple of times about the result cache. You can download this presentation from my new Presentations and papers tabpage, by the way. After each of those sessions I received several good questions. To some questions I didn't know the answer, and for some other questions I did, but I hadn't tested it so I wasn't absolutely sure. I promised to address those questions
I had a question about how to quickly identify which Oracle process runs out of which ORACLE_HOME on Linux. I have uploaded a little script for that – it’s basically looking up all PMON process IDs and then using /proc/PID/exe link to find out where is the oracle binary of a running process located. You [...]
Today, I created Database Link on my New Database, and saw ORA-02085
SQL> create database link TESTDBLINK connect to username identified by "password" using 'TRGDB';
Database link created.
SQL> select * from tab@TESTDBLINK;
select * from tab@TESTDBLINK
ERROR at line 1:
I have already posted about an issue that required me to drop and recreate standby log files so I thought I would post the scripts I used. Resize Standby Redo Logs 1. On primary defer log shipping (dynamic change) alter system set log_archive_dest_state_2 = defer scope = memory; 2. On standby database cancel managed recovery alter database [...]
When we have a situation where the standby redo logs on the standby database are not the same size as the online redo logs on the primary database, there is a strange redo log switching behaviour on the primary database. The primary continually switched online redo logs every 2 minutes no matter how little activity [...]
I have a strange problem with my Grid Control 18.104.22.168 Management Server in a Solaris 10 zone. When restarted, the OMS will serve requests fine for about 2 to 4 hours and then “hang”. Checking the Admin Server console I can see that there are stuck threads. The same information is also recorded in the logs.
NB: the really confusing part about Grid Control 11.1 is the use of Weblogic-you thought you knew where the Grid Control logs where? Forget about what you knew about 10.2 and enter a different dimension :)
February 28, 2011 (Forward to the Next Post in the Series) Previously, I had written a couple of blog articles that showed how to build a reasonably usable Oracle Database Time Model Viewer using nothing more than a text file (containing a VBS script) and a dynamically generated web page that is displayed on a Windows [...]
As many companies judge a DBA’s worth on the uptime of a database, nothing tests a DBA’s mettle like database service outages where the cause is indeterminate at the time of the outage. The secondary challenge is that once the database is brought back up, the DBA must then take the necessary steps to analyze the data and figure out what caused the outage, hopefully resolving or reporting to ensure outages to not re-occur. The DBA’s goal should not just be to resolve the issue, but to provide a high level, clearly documented report of what occurred and what steps have been/scheduled to be