Posts Categorized: Technical Blog
This post is addressed to all RAC SIG members who are planning to participate in the InSync11 conference this August in Sydney Australia! InSync11 is organized by Oracle Community for Oracle Community and is one of the biggest Oracle technology dedicated events in Australia and New Zealand region. This is a wonderful opportunity to learn from others, listen to experts from around the world and meet face to face people from your networks (including RAC SIG).
I’ve been so amazed by the community response to my requests over the past few days that I just HAD to blog about it. In this post I’ll cover Oracle MIX and Suggest-a-Session voting, my very first experience and approach to the event, and special thanks to those who showed their support.
Are you considering Oracle Exadata as a data warehousing or consolidation solution for your organization? Before you go any further, be sure to join Alex Gorbachev, Oracle ACE Director & Pythian CTO at noon tomorrow (EST) as he outlines where Oracle Exadata is the best fit.
I was reading my session evaluation results and came accross comment that said: “copy and paste coder.” I’ve been doing this specific presentation for almost 5 years now with a few tweaks every once in a while based on feedback. Yes, I live and breathe disaster recovery as part of my day-to-day job. However, there are several reasons why I do not type nor write code during my presentations. Here are a few of them.
In this follow up post: I’m going to provide notes and diagrams as well as answer questions from my web cast on Oracle 11G SCAN – RAC SIG. Let’s get into it….
While trying to move a schema from one MySQL server to another, I encountered a very odd issue. The schema to be moved contained both MyISAM and InnoDB tables, so the only option I had was to dump the schema using mysqldump on the source server and import it on the destination server. I did some digging and found that the problem was that the MyISAM engine silently changed the table definition without any indications. Here are some solutions.
No, this isn’t a re-post of my earlier blog about bug 1233183.1. We’ve found a fun new bug that seems to be specific to our poor standalone ASM instances when upgrading from Oracle Grid Infrastructure 22.214.171.124 to 126.96.36.199.
We have a client that runs an application that, for whatever reasons, does NOT like daylight saving time. For that reason, the Oracle server is kept in Eastern Standard Time and does not change with the rest of the eastern United States when DST begins and ends every year. They accomplish this with a custom /etc/localtime file. However, they left /etc/sysconfig/clock set to “TZ=America/New_York,” which would prove fateful as I shall point out.
Summer’s here, and that means it’s time to start thinking about Oracle OpenWorld 2011. Pythian’s plans are well underway. We have been busily planning since March, have submitted a number of abstracts on all sorts of topics: Exadata, ASM, GoldenGate, ADR, ASM, many based on real world experiences with Pythian clients. Some have been accepted, but we’re hoping for a few more and we’re asking Pythian fans to vote for our sessions on Oracle Mix.
I was working on a task where I had to confirm if the direct IO is in use or not. filesystem_io_option database parameter was set to “DIRECTIO” to make use of directio. Initially I was looking for same kind of memory structures in Solaris but could not find so ( bad luck :( ) and so used basic tracing using truss.First I logged into database and check the filesystem parameter ( Changed the name of the database and host :) )