To add another node to a RAC cluster simply clone the home
Golden Images
Fix Control underscore parameter
############################################################################# # FILENAME: .profile_env # PURPOSE: Custom environment variables or additions to the PATH may be # placed here. You can edit anything in this file, this file is # used to customize the environment. ############################################################################# # # # Revision History: # # # # REV DATE BY DESCRIPTION # # --- ------ -------------- ------------------------------------------- # # # ############################################################################# # You may change any of these values as needed for your environment # # /orgtools = can be setup for a standard place to put your organizations software tools export SUNWspro=/opt/SUNWspro # C compiler directory # export MAIL=/var/mail/oracle # Location of oracle mail file # export MAILMSG="You have mail." # Mail Message to display # export PBROKER=/orgtools/pbrun/3.2/bin # Location of PowerBroker # #export FGLHOME=/oracle/dba/foglight/4.2 # Current version of Foglight # export FGL_DIR=/oracle/dba/foglight/fgl_5/bin # export FGL_STOP_CMD="stop.sh" # export FGL_START_CMD="start.sh -d" # PATH=/opt/VRTSvmsa/bin/vmsa:$PBROKER # Additional PATH locations # umask 022 # Default permissions 744 # # ulimit -n 1024 # Number files opened at once # # resize # V1.2 Issue a "resize" if needed # ############################################################################# # Default ORACLE_SID. CHANGE THIS VALUE BELOW # # For application servers with no database, set to "no_db" and put an entry # ############################################################################# # # # FILENAME: .profile_env # # # # PURPOSE: Custom environment variables or additions to the PATH may be # # placed here. You can edit anything in this file, this file is # # used to customize the environment. # # # ############################################################################# # # # Revision History: # # # # REV DATE BY DESCRIPTION # # --- ------ -------------- ------------------------------------------- # # # ############################################################################# # You may change any of these values as needed for your environment # export SUNWspro=/opt/SUNWspro # C compiler directory # export MAIL=/var/mail/oracle # Location of oracle mail file # export MAILMSG="You have mail." # Mail Message to display # export PBROKER=/banktools/pbrun/3.2/bin # Location of PowerBroker # #export FGLHOME=/oracle/dba/foglight/4.2 # Current version of Foglight # export FGL_DIR=/oracle/dba/foglight/fgl_5/bin # export FGL_STOP_CMD="stop.sh" # export FGL_START_CMD="start.sh -d" # PATH=/opt/VRTSvmsa/bin/vmsa:$PBROKER # Additional PATH locations # umask 022 # Default permissions 744 # #ulimit -n 1024 # Number files opened at once # # resize # V1.2 Issue a "resize" if needed # ############################################################################# # Default ORACLE_SID. CHANGE THIS VALUE BELOW # # For application servers with no database, set to "no_db" and put an entry # # as follows in your oratab: no_db:<oracle_path>:N # if [[ ${NEW_ORACLE_SID:-0} = 0 ]]; then # If NEW_ORACLE_SID is not set export NEW_ORACLE_SID=SAMPLE_SID # Default ORACLE_SID fi ############################################################################# # You may add any other custom variables to this section as needed. # # Be aware that .profile WILL override if you choose the same variable names# export NLS_DATE_FORMAT='DD-MON-YYYY HH24:MI:SS' ############################################################################# # This was set in the .std_profile but is commented out there in favor of here export ORACLE_BASE=/oracle export RSP=/oracle/admin/scripts/rspfiles export TMPLT=/oracle/product/11.2.0.3/db_2/assistants/dbca/templates export ADMSCR=/oracle/admin/scripts export DIAG=/oracle/diag export TRCOUT=/oracle/diag/rdbms/dpodst01/DPODST011/trace alias admscr='cd $ADMSCR' alias tmplt='cd $TMPLT' alias rsp='cd $RSP' alias trcout='cd $TRCOUT' alias gi='cd /oracle_crs/product/11.2.0/crs_1/log/$SNAME' alias ocssd='cd /oracle_crs/product/11.2.0/crs_1/log/$SNAME/cssd' alias crsd='cd /oracle_crs/product/11.2.0/crs_1/log/$SNAME/crsd' alias vial='vi $ADMIN/$DB_NAME/bdump/alert_$DB_NAME.log' alias diag='cd $DIAG/rdbms/$DBNAME' alias lv='ls -v ' alias rd='rmdir ' alias md='mkdir ' alias pg='less -EF ' alias pgn='less -EFN ' ######### GOLDEN GATE SETUP ####################### export GGS_ORA_HOME=/ggate/ggs ulimit -c unlimited ulimit -s unlimited ######### Last Statement of: .profile_env #########
For any use of the BACKUP
command that creates backup sets, you can take advantage of RMAN support for binary compression of backup sets. Specify the AS COMPRESSED BACKUPSET
option to the BACKUP
command.
RMAN compresses the backup set contents before writing them to disk. The details of which binary compression level is used are automatically recorded in the backup set. There is no need to explicitly mention the type of compression used or how to decompress the backup set in the recovery operation.
Binary compression creates some performance overhead during backup and restore operations. Binary compression consumes CPU resources, so do not routinely schedule compressed backups when CPU usage is high. However, the following circumstances may warrant paying the performance penalty:
Here is a current version of the Oracle price list
The buffer exterminate wait event is caused when using Oracle's "automatic memory management" (AMM) when the MMON process shrinks the data buffer cache to re-allocate that RAM for another SGA region. AMM resize operations can hurt overall database performance especially the OLTP environments, and you may want to consider turning off AMM which will relieve the buffer exterminate waits, and manually adjust your SGA regions.
If you suspect AMM resize operations, you have to look into v$sga_resize_ops and v$memory_resize_ops and see how many times it is occurring and effecting the performance of your database. If one sees more events of these and especially during your peak times of database one has to turn of the feature adjusting manually the corresponding SGA and PGA sizes.
If you want to analyze Oracle's use of memory and look at various memory resizing operations you can use the v$memory_resize_ops view. This view contains a list of the last 800 SGA resize requests handled by Oracle. Here is an example:
select parameter ,initial_size ,target_size ,start_time from v\$memory_resize_ops where initial_size > = 0 and final_size > = 0 order by parameter, start_time;
Please find below the various tables that are related to AMM and their descriptions to check the information in the database.
v$memory_dynamic_components - displays information on the current size of all automatically tuned and static memory components, with the last operation (for example, grow or shrink) that occurred on each.
v$sga_dynamic_components -- displays the current sizes of all SGA components, and the last operation for each component.
v$sga_dynamic_free_memory -- displays information about the amount of SGA memory available for future dynamic SGA resize operations.
v$memory_current_resize_ops -- displays information about resize operations that are currently in progress. a resize operation is an enlargement or reduction of the SGA, the instance pPGAga, or a dynamic SGA component.
v$sga_current_resize_ops -- displays information about dynamic SGA component resize operations that are currently in progress.
v$memory_resize_ops -- displays information about the last 800 completed memory component resize operations, including automatic grow and shrink operations for sga_target and pga_aggregate_target.
v$sga_resize_ops -- Displays information about the last 800 completed SGA component resize operations.