RE: use_large_pages parameter

If you set the parameter to ONLY and a clone doesn’t spawn up its memory instance then you don’t have enough huge pages.

If you plan on running the clone with the regular application and you know that running outside of huge pages can have performance issues why wouldn’t leave it set to ONLY and ensure you really have enough huge pages, unless you plan to immediately bounce and shrink the footprint so the clone (after cloning) can run under huge pages?    

From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of Adric Norris Sent: Friday, February 12, 2021 12:45 PM To: Jeff Chirco <backseatdba_at_gmail.com> Cc: oracle-l-freelist <oracle-l_at_freelists.org> Subject: Re: use_large_pages parameter  

I'm not familiar with Cohesity, but a quick search suggests that it uses RMAN. If so you may be able to override parameters used for the auxiliary instance during cloning, by placing your desired settings in $ORACLE_HOME/rdbms/admin/params_auxinst.ora.  

On Thu, Feb 11, 2021 at 4:27 PM Jeff Chirco <backseatdba_at_gmail.com <mailto:backseatdba_at_gmail.com> > wrote:

Wondering what everyone has set for this parameter. Are using ONLY to prevent the database from starting if there not enough lage pages available? This seems like the best practice to me as I have experience issues when not running on hugepages.

One of the reasons I ask is we are starting to use Cohesity to run our backups and it seems like there might be an issue with having this parameter set to ONLY when I want to create clones. If I use the default of TRUE then it works. You might ask that I might not enough hugepages available but I am pretty I do.

So I am hesitant to set this parameter to TRUE but maybe I am over thinking it.  

--
http://www.freelists.org/webpage/oracle-l