oracle 体系架构 - （绝对原创） （二）

This I will continue to intruduce Instance and Media recovery structure:

Step1:
  The Oracle server provide a number of standard views to obtain information on the database
  and instance, These views include:
 
  1: v$sga:
    queries the size of the instance for the shared pool, log buffer, data buffer cache, and fixed
    memory sizes(operating system-dependent).
  
  2: v$instance:
    Queries the status of the instance, such as the instance mode, instance name, startup time, and hostname.
   
  3: v$process:
    Queries the background and server process created for the instance
   
  4: v$bgprocess:
    Qeries the background process created for the instance.
   
  5: v$Database:
    List the status and recovery information about the database.
    It includes information on the database name, the unique database identifier,
    creation date, the control file creation date and time, the latest database checkpoint
    and other information.
   
  6: v$datafile:
    List the location and names of the datafiles that are contained in the database.
    It includes information relating to the file number and name, creation date,
    status (online or offline), enabled (read-only, read-write), last datafile checkpoint,
    size, and other information.
   
   
Step2:
  This step, I will describe the detailed infomation about "Large pool":
 
  Large Pool:
    1: Can be configured as as separate memory area in the SGA to be used for:
      Oracle backup and restore operations.
      I/O server processes.
      Session menory for the shared servers.
     
     2: Is sized by the LARGE_POOL_SIZE parameter.
    
   Detailed:
     1: Configuring the large pool prevents RMAN from completing with other subsystem for the same
     memory.
    
     2: RMAN uses the large pool for backup and restore when you use the DBWR_IO_SLAVES or BACKUP_TAPE_SLAVES
     to simulate asyncronous I/O.
    
     3: If the LARGE_POOL_SIZE initialzation parameter is not set, the Oracle server attempets to
     allocate shared memory buffers from the shared spool in the SGA.
    
     4: If the Oracle can not get enough memory, then it obtains I/O buffer from local process memory
     and write message to the alert.log file indicating that synchronous I/O is used for the backup.
    
     5: If you want to see the large pool size:
     select * from v$sgastat; (free large spool)
     show parameter large_pool_size
    
     you can use below command to set large_pool_size:
     alter system set large_pool_size=8888888 scope=both;
    
Step3:
    Configuring tablespace:
   
    Tablespaces contain one or more datafiles. It is important that tablespaces are
    created carefully to provide a flexible and manageable backup and recovery strategy.
    Here is a typical configuration of tablespace, taking into account requirements for
    backup and recovery operations:
   
    1: System:
      Backup and recovery is more flexible if the system and user data is contained in diffent
    talespaces.
   
    2: Temporary:
      If the tablespace containing temporary segments(used in sort,and so on) is lost, it can
     be re-created, rather than recovered.
    
    3: Undo:
      The procedures for backing up undo tablespace are exactly the same as for backing up any
      other read/write tablespace. Because the automatic undo tablespace is so important for
      recovery and fro read consistency, you should backup it up frequently.