Recently, I was doing some performance analysis for one of our clients, using STATSPACK and found that they were not using a consistent method for control. STATSPACK was installed on most instances but some instances had scheduled cron jobs for STATSPACK gathering, while others had dba_jobs. In addition, there was no cleanup implemented for some of the instances. This situation led me to think about finding a consistent, integrated and simple way of setting up and configuring STATSPACK.
Today is SysAdmin day, don’t you know. Right up until last year, DBAs were included in this global movement to celebrate systems administrators. The Internet Wayback Machine gladly shows us how the site looked last year, clearly including DBAs right in the home page. This year? No mention of us!
A client asked me, “How can I move a table to another schema in Oracle?” The quick answer I gave him is, “not possible”. You have to rebuild it via “create table as select”. You might ask, justifiably, why would you want to do that anyway? His problem was that the application has been split into 2 parts, and he wanted to have separate schemas for each part, to ensure that there is no cross-schema table access.
I’ve been invited by new Pythian partner GridApp to co-host a webinar with their eminent chief scientist, Matt Zito. If you don’t know about GridApp, you certainly should. They offer a rapid-provisioning and configuration management system called Clarity that substantially streamlines repetitive database management chores while simultaneously providing visibility into inventory and configuration changes.
With the new dynamic performance views available in SQLserver 2005 you can run queries which allow you to determine these poor performers without much extra work. It is not statspack or Automatic Workload Repository (AWR) or V$ACTIVE_SESSION_HISTORY (more importantly) but it is a good start to determining what sql and what sessions are consuming the most resources in SQLserver 2005 instance.
It’s time for vacation for me.
I am off to Europe and then vising home – Sofia, Bulgaria. I will be back in 4 weeks. Yes I did earn to have a long vacation, and yes, Pythian is really nice in allowing me to have it all at once.
There’s always these little things that you discover when you read the manuals. For example the “duration” option for RMAN backup. It looks very neat, and is actually in RMAN from 10g Release 1.
James Foronda sent a link to his blog entry about silent data corruption in an Oracle-l discussion. He points out a new file system called ZFS that has self-healing features.I read all the slides and it really looks like something cool to try out. It has some features similar to Oracle’s ASM, such as dynamic adding of disks, self balancing etc. It’s fully transactional, supports snapshots, online everything. Auto striping (not sure how this would work). Very feature rich.
I was installing RAC, and during the clusterware install I picked up the wrong interfaces for public and private. What had happened was I had a 10.x.x.x IP on both eth0 and eth1, which was messing up the routing. The solution? Simply modify the VIP in the cluster configuration.
Finding duplicates with RANK – If you’ve made the mistake of forgetting a primary key on your table, it can be frustrating to find a way to delete all of the duplicate rows without deleting the initial instances. This query selects all of the ‘extra’ rowids and removes them.