This content has been marked as final. Show 8 replies
These are the parameters that require restart of the instance.
alter system set bitmap_merge_area_size =0
alter system set commit_point_strength =0
alter system set db_block_checksum =typical
alter system set db_flashback_retention_target =0
alter system set db_writer_processes =2
alter system set remote_login_passwordfile =EXCLUSIVE
alter system set replication_dependency_tracking =FALSE
alter system set session_cached_cursors =75
alter system set streams_pool_size =0
alter system set processes =1000
alter system set sga_max_size=0
alter system set memory_max_target=2000M
alter system set memory_target=2000M
Krishna Nazare wrote:provide pfile with any/all non-default parameter values & then do as below
For our product's backend database (oracle 11g r2), we have to set several tuning parameters. Some of these parameters will be in effect only after the instance is restarted. Is there a way these parameters can be set/preset during instance creation itself, or some other means, so that the additional restart can be avoided.
CREATE SPFILE FROM PFILE='/absolute/path/to/custom_pfile';
Login to sqlplus and share the output of below :
If this gives a value , good enough you surely need to bounce the db.. otherwise , if this gives a blank output , then do as what sir SB has suggested in the above post. Create a spfile from your pfile and then stop and start.
show parameter spfile
ALso , if the parameters require mandatory downtime to reflect, take approvals in off peak hours and do the needful. It sould take more than 20mins max for both app and db to bounce.
Krishna Nazare wrote:What I'm missing is WHY?
This was useful. What i tried was that during instance creation i can run custom script. As part of custom script, i set the parameters and the script restarts the database instance. With that i am able to set the parameters and get the values set.
Why are you concerned with not restarting the database? You are creating a database. That means there is no pre-existing database, no pre-existing application, no users. No one to care if you bounce it. So why is it important to NOT have to bounce it one last time after you have created it?
I'm glad you found a solution, but it appears to be a solution in search of a problem.
We are trying to automate and create the instance without manual intervention in cloud deployment. These two steps had to be carried out manually after creating the instance. With this, there is no need for additional manual steps.You can add all parameters to init or pfile.ora file you are using to create the instance.