- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Application Integration
- >
- Re: Oracle Performance Policy
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2014 01:39 AM
тАО02-14-2014 01:39 AM
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!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2014 06:24 AM
тАО02-15-2014 06:24 AM
Re: Oracle Performance Policy
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!
twitter: @nick_dyer_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2014 12:52 AM
тАО02-17-2014 12:52 AM
Re: Oracle Performance Policy
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2014 12:58 AM
тАО02-17-2014 12:58 AM
Re: Oracle Performance Policy
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?
twitter: @nick_dyer_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2014 02:36 AM
тАО02-17-2014 02:36 AM
Re: Oracle Performance Policy
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2014 09:20 AM
тАО02-17-2014 09:20 AM
SolutionIt 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2014 06:29 AM
тАО04-19-2014 06:29 AM
Re: Oracle Performance Policy
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2014 06:34 AM
тАО04-19-2014 06:34 AM
Re: Oracle Performance Policy
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2014 06:37 AM
тАО04-19-2014 06:37 AM
Re: Oracle Performance Policy
I meant a minimum not max. The array block size should never be more than the formatted size of the volume to avoid misalignment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-03-2015 10:30 AM
тАО04-03-2015 10:30 AM
Re: Oracle Performance Policy
I thought Nimble was working with a Vendor for the NVRAM capability and the YouTube video disscusses a proprietary NVRAM capability.