The SMON spit out this error after the cycle of the db on the rollback of the huge insert into the largest table in one of our warehouse environments. I had serious concerns about a poor execution plan and wondered what we were going to be in for on the rollback and with good reason. The source to the performance hit was a combination of missing column statistics on the main table used for the joins from the staging table, but also fragmentation caused by a poor design choice, (yes, get exchange partition in there ASAP!) Here is the issue w/ fix with the…
-
-
Like Chet, from OracleNerd, I received my official Blogger Approval for Oracle Open World yesterday! This will be my first attendance, as something always came up before that kept me from going, so I am looking forward to the event. A number of people asked me why I didn’t submit a presentation, but I think I’m going to check out the event as a blogger for my first time out and see about presenting next year! 🙂