Re: Oracle Financials

In article <3lpb92$bad_at_kiki.icd.teradyne.com>, bill.pierce_at_teradyne.com says...
>
>I am interested in any comments of users running oracle financial(s);
>Particularily the "HARD KNOCKS" lessons learned. How did you design
>your database(s)? How did you tune them? Any special software or hardware
>used to assist in the management of your databases? How did you tune
>the SQL? Init.ora parms? Space management techniques? Any comments are
>welcome, including general observations. Finally what are the positive
>or negative consequences of running the products on several separate
>databases, rather than one instance?

Here are a few things off the top of my head:

Separate your hot tables and keep them in their own tablespaces. For GL, GL_INTERFACE and GL_JE_LINES should reside in their own tablespaces.

$FND_TOP and $GL_TOP should reside on their own mount points. If you're luxurious, isolate as many top directories onto their own mount points and/or disks as you can. Watch for $GL_TOP/out and $GL_TOP/log, which will grow whenever users issue reports.

I don't think there's much of any SQL tuning you can do with Financials.

Your init.ora parmeters depend on the size of your database. Be sure not to underestimate your db_files upon database creation, because increasing it is a pain (either recreate control files or export, recreate the database, then import).

The concurrent managers can consume significant CPU, especially with Release 10. Be sure to configure enough concurrent managers to handle the number of users and total reports.

Be sure to size for peak demand. That is, size for the end of the month or quarter or whatever posting period you use. The better you know your users and your expected workload, the more accurately you can size your hardware and datafiles, and the more predictable your performance will be during peak periods.

-- 
Lisa Roderick
Applications Systems Engineering Performance Group
Digital Equipment Corporation
Merrimack, NH
lisa.roderick._at_mko.mts.dec.com