Oracle Agile doesn’t follow Oracle best practices

So right now I’m doing an upgrade of one of our test systems from Agile Advantage SP4 on Windows to Agile 9.3.0.1 on Linux. It’s quite the involved process and I’ll post more at length about it later. However, two things I just finished fixing that saddens me:

Oracle doesn’t follow Oracle’s own best practices with the seeded Agile 9.3 database. I have no idea why they did this. It’s not because this best practice is new – it’s been the recommendation since I learned it back in 1997 with Oracle 7.3.

Agile 9.3.0.1 lays down a database with 4 redo log file groups, each with 1 200MB member. Oracle best practices with redo logs is 3 redo log file groups each with 2 members. Depending on the system I/O characteristics you may add more redo log groups and the size is highly dependent on the I/O characteristics. All Oracle databases should at least have 2 redo log groups each with 2 members. So instead of the minimum 2×2 or best practice 3×2 configuration, Oracle provides one of their products with a 4×1 configuration which is just asking for issues.

On a related note, the Oracle Agile 9.3.0.1 database also came with an UNDO tablespace that’s sized to autoextend automatically until it fills up the file system. Best practice is to NEVER set an UNDO tablespace to autoextend because a poorly written query can possibly use all the disk space on the system.

Seriously Oracle, what were you thinking?

One thought on “Oracle Agile doesn’t follow Oracle best practices

  1. I’d guess that when Oracle acquired Agile they didn’t bother to assess how Agile had defined their default database setup, and have just been carrying forward questionable practices. I’ve seen similarly scary things in other 3rd-party apps. Still, after 3 years, you’d think *someone* would have had a look. Given Oracle’s voracious acquisition spree over those years, though, the “modify Agile database definition script to fit defined standards” task has probably been on someone’s important-not-urgent list for a while.

    And we all know what happens to the important-not-urgent quadrant…it gets done on some random, really boring weekend or not at all. 😉

Leave a Reply

Your email address will not be published. Required fields are marked *