Supporting Hardware - Expert Consolidation in Oracle Database 12c - page 105

$ORACLE_HOME/bin/sqlplus / as sysdba > /dev/null <<EOF
spool $TESTNAME/awr_config.txt
select systimestamp as now from dual;
select * from DBA_HIST_WR_CONTROL;
exec DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS(interval=>360)
exit
EOF
# finally run the benchmark. Keep the output too
./runit.sh $NUM_SESSIONS 2>&1 | tee ${TESTNAME}/runit.sh.log
# preserve the generated files in $TESTNAME
for FILE in $FILES; do
[[ -f $FILE ]] && {
echo INFO: moving file $FILE to directory $TESTNAME
cp $FILE $TESTNAME 2> /dev/null
}
done
# create a copy of awr.txt for the use with awr_info.sh
cp ${TESTNAME}/awr.txt ${TESTNAME}/awr.txt.${NUM_SESSIONS}
# finally preserve all initialisation parameters
$ORACLE_HOME/bin/sqlplus / as sysdba 2> /dev/null <<EOF
create pfile='$(pwd)/${TESTNAME}/init.ora' from memory;
exit
EOF
echo INFO: done
Notes on SLOB usage
If you intend to run the Physical I/O or PIO test, you need a small SGA—which is easier said than done. With
multi-socket/multi-core servers, Oracle will automatically derive default values for initialization parameters, making
it difficult to get small buffer caches. Limiting the cpu_count to a low value—2 or 4—is usually a good starting point,
and you could also use manual SGA management, as we know it from Oracle 9i. The below is a sample initialization
file with manual SGA management, based on the previously mentioned “simple.ora” initialization file which you
should review and adapt if needed:
db_create_file_dest = '/u01/oradata/'
db_name = SLOB
compatible=12.1.0.1.0
UNDO_MANAGEMENT=AUTO
db_block_size = 8192
db_files = 300
processes = 500
control_files = /u01/oradata/SLOB/controlfile/o1_mf_812m3gj5_.ctl
shared_pool_size = 600M
large_pool_size = 16M
java_pool_size = 0