Skip to main content

How to verify whether a parameter changed required database bounce or not


In v$parameter we can find one column ie. ISSYS_MODIFIABLE. This column
contains three phases 1) Immediate 2) DEFERRED 3) False

1. Immediate : We can change the parameter in fly database ie Dynamic.(only need to change the value no need to bounce)

2. DEFERRED : We can change the parameter in fly database but this will effect
after restart the database only.(here we need to edit using spfile and bounce the database)

3. False : Compulsory we need to down the database ie Static.


Ex:-
select name ISSYS_MODIFIABLE from v$parameter;

Comments

Popular posts from this blog

CLSRSC-430: Failed to start rolling patch mode

############################################################ GRID PSU Failed on Node2: =========================== [root@server1 tmp]# /oracrs/oracle/product/12102/OPatch/opatchauto apply /path1/patches/23273629 -oh /oracrs/oracle/product/12102 -ocmrf /tmp/ocm.rsp OPatch Automation Tool Copyright (c)2014, Oracle Corporation. All rights reserved. OPatchauto Version : 12.1.0.1.10 OUI Version        : 12.1.0.2.0 Running from       : /oracrs/oracle/product/12102 opatchauto log file: /oracrs/oracle/product/12102/cfgtoollogs/opatchauto/23273629/opatch_gi_2016-11-25_06-13-44_deploy.log Parameter Validation: Successful Configuration Validation: Successful Patch Location: /path1/patches/23273629 Grid Infrastructure Patch(es): 21436941 23054246 23054327 23054341 DB Patch(es): 23054246 23054327 The following patch(es) are duplicate patches with patches installed in the Oracle Home.  [ 20299023] You hav...

ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device

Upon startup of Linux database get ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device (Doc ID 301830.1) Issue: ====== ORA-27102: out of memory Linux-x86_64 Error: 28: No space left on device Solution: ========= 1. Ask SA to increase "kernel.shmall" in /etc/sysctl.conf     Formula:     RAM * 1024 * 1024 * 1024 / page_size     Ex:-     RAM = 50GB     $getconf PAGE_SIZE ==> 4096     50*1024*1024*1024/4096 = 13107200 ==> kernel.shmall 2. After updating kernel.shmall, ask SA to do "sysctl -p" to activate changes. 3. Start the DB Note: ==== Kernel values will be set in below files 1. Updating below files doesn't require system reboot.     /proc/sys/kernel/shmmax     /proc/sys/kernel/shmall     /proc/sys/kernel/shmmni     Usage:  # echo "536870912" > /proc/sys/kernel/shmmax       ...