ADM505 Oracle Administration 1 notes

Teacher: Manfred Tietgen (freelancer) replacing a sick teacher (Ingo).

DB files:

DB profile files (init<sid>.ora,init<sid>.sap (br*tools), spfile*)
control file, at least 3 identical files (can be duplicated using a simple file copy)
data files
online redo logs (mirrored)
offline redo logs (archives)

In MCOD SAP uses te scema ID to access its part of the data.

For SAP only a redo logswitch will lead to a checkpoint!

The logbuffer is default 50MiB for SAP640.

Database file headers are updated with checkpoint info.

brarchive can get stuck if your offline redolog filesystem is full becaurse it starts with creating a lockfile. So when in need if removing offline redo logs you are stuck. The old sollution is you have a dummyfile you can delete, a newer variant is that you extend the filesystem online.

brbackup = backup data files
brarchive = backup offline redologs
brrestore/brrecover

data safety rules:

online redo must be mirrored (or in RAID)
archivelog-mode must be switched "on"
never store redo archives together with datafiles

redo log members:

origlog : LOG*M1*DBF
mirrlog : LOG*M2*DBF

Environment variable example:

  
export DISPLAY=<Xserver>:<port>
export ORACLE_BASE=/oracle 
export ORACLE_SID=<SID> 
export SAPDATA_HOME=$ORACLE_BASE/$ORACLE_SID
export ORACLE_HOME=$SAPDATA_HOME/102_64
export NLS_LANG=AMERICAN_AMERICA.UTF8 
export ORA_NLS10=$ORACLE_HOME/nls/data
export LIBPATH=$ORACLE_HOME/lib:$LIBPATH
export PATH=$ORACLE_HOME/bin:$PATH

Notes

  
brgui : 611493
brtools : 651812
brbackup/brarchive : 17163, 442395

Report parameters in batch mode: brspace -c force -p initDEV.sap -f dbshow -c dbparam.

Transaction db17 allows you to controll dbcheck activity.

  
                 backup mode (-m)   tape copy tool
                 ================   ==============
classical         all                dd, copio, rman
saptools+rman     full               dd, copio
rman (save set)   full               rman

Complete consistent online backup that includes the redo log files created during backup :

brbackup -m all -a -ssd
brbackup -t online_cons

See note 170013 for difference all and full backup.

rman incremental backups (level 1) need an level 0 backup, this can only be done by a "full" and not by "all" (or whole) backup! For level 0 it does not matter if you used rman or not.

help.sap.com - netweaver - search - oracle incremental backup

use locally managed for date and dictionary managed for system.

partitioned tables are often used in BW environment where you need 1-1 relationshop tables to build up a n-dimentional [star-shaped] pattern.