topic Re: Oracle Performance Policy in Application Integration

Oracle Performance Policy

boerlowie42 — Fri, 14 Feb 2014 09:39:07 GMT

Hi,

we are setting up Oracle on Nimble.

The LUN layout will be seperate LUNs for DBF, FRA & Backup (backup won't be stored on the Nimble, so that won't be an issue here).

For DBF, the perf policy will be Oracle OLTP. But what do i pick for the FRA volume? For SQL & Exchange, log volumes don't have caching enabled because there are mostly writes happening to those volumes. Wouldn't this be the same for Oracle FRA volumes?

Thanks!

Re: Oracle Performance Policy

Nick_Dyer — Sat, 15 Feb 2014 14:24:57 GMT

Hi Sammy,

the FRA is a series of log volumes for Oracle ASM, and as such I would create a new Performance Policy with caching turned off (call it "Oracle-FRA" perhaps) - and my guess is the block size would be 4k. Compression turned on.

Interestingly, if you have any temp-db for Oracle you should also assign them a Performance Policy which doesn't cache - reason being Nimble will still read data back from NVRAM or DRAM if it's available even if caching's turned off by design!

Re: Oracle Performance Policy

boerlowie42 — Mon, 17 Feb 2014 08:52:26 GMT

I have set a Perf Policy with Caching disabled. However, i'm not sure about the block size as for the DB it is 8 KB. Not that familiar with Oracle what blocksizes it used, but our DBs are set to 8 KB, so i would guess the FRA volumes uses 8 KB as well?

Re: Oracle Performance Policy

Nick_Dyer — Mon, 17 Feb 2014 08:58:22 GMT

Morning Sammy,

The rule of thumb here is that if you do not know the block size always go for 4K, as it is divisible into 8, 16 and 32K blocks respectively.

Perhaps Tom Dau might be able to advise... Tom, any thoughts sir?

Re: Oracle Performance Policy

boerlowie42 — Mon, 17 Feb 2014 10:36:33 GMT

I just checked with our DBA and they use ASM for all Oracle volume and they set 8 KB as block size for both DBF & FRA. So the Nimble 8 KB block size should be fine then.

Gr,

Sammy

Re: Oracle Performance Policy

tdau98 — Mon, 17 Feb 2014 17:20:16 GMT

It depends on what FRA diskgroup is used for. If FRA is used for archive logs and other database logs such as flashback logs, then you can use 32K perf policy. If online redo logs also go to FRA then use 8K perf policy. The Oracle best practices guide has a table outlining which perf policy is used for certain Oracle files. Please let me know if you have any further question.

Thanks,

Tom

Re: Oracle Performance Policy

marktheblue45 — Sat, 19 Apr 2014 13:29:49 GMT

Still really confused here since I'm not a DBA. I'm thinking 3 iSCSI Nimble volumes (in guest connected) with all Nimble volumes at 8K since the page file on the 11g setup is 8K. Not sure what the NTFS CLUSTER/block size should be. Archive volume .... No cache. Any clues.

Re: Oracle Performance Policy

marktheblue45 — Sat, 19 Apr 2014 13:34:45 GMT

On RHEL it's suggested 8K for DB with caching on, 4K for Redo with caching on and 32 for Archive logs with no cache. No mention of O/S block size. If I followed that than the NTFS cluster size would be a max of 8k for DB, 4K for Redo and 32k for archive. Talking OLTP MODE.

Re: Oracle Performance Policy

marktheblue45 — Sat, 19 Apr 2014 13:37:31 GMT

I meant a minimum not max. The array block size should never be more than the formatted size of the volume to avoid misalignment.

Re: Oracle Performance Policy

gss200338 — Fri, 03 Apr 2015 17:30:37 GMT

I thought Nimble was working with a Vendor for the NVRAM capability and the YouTube video disscusses a proprietary NVRAM capability.