熱點推薦:
您现在的位置: 電腦知識網 >> 編程 >> Oracle >> 正文

OracleDBA新手經常碰到的10個Oracle錯誤

2013-11-13 16:08:54  來源: Oracle 

  This document contains information about errors frequently encountered by
  new DBAs along with appropriate actions to be taken in each circumstance
  
  +==+
  
  Summary:
   COMMON RDBMS ERRORS
  
  +=+
  
  ) ORA
  
  a) on Rollback segment when importing
  
  Specify commit=y and a large buffer on import This way the Rollback
  will be released after each array as opposed to each object
  
  b) when allocating an extent on a tablespace with alot of free space
  
  Select max(blocks) from DBA_FREE_SPACE You may have free space but it
  might not be contiguous Make sure it is greater than the extent it
  is trying to allocate You can reduce the storage parameters NEXT and
  PCTINCREASE if it isnt
  
  ) ORA max extents of exceeded when storage is set for maxextents
  of
  
  Most platforms have a max of even though it allows you to specify
   (see the readme for your platform)
  
  ) ORA shutdown in progress when starting up even after a shutdown was
  issued quite some time ago
  
  If the background processes arent running the SGA could have been left
  out there Issue a startup force open (which does a shutdown abort
  first)
  
  ) IMP ORA and IMP on import
  
  Run catalogsql and expvewsql (renamed catexpsql in v) as sys before
  the import Both files are in $ORACLE_HOME/rdbms/admin (UNIX)
  
  ) ORA Invalid column name on import
  
  Run expvewsql (catexpsql) before the import
  
  ) ORA Oracle not available
  
  Startup the DB firstif it is started check your searchpath
  Make sure that ORACLE_SID is set correctly For setuid issues see
  PRE
  
  ) ORA Oracle Data Block corrupted (file # num and block # num)
  
  To determine where the corruption is:
  select * from sysdba_extents where file_id = filenum and blocknum
  between block_id and (block_id + blocks );
  The filenum and blocknum are the numbers in the error
  This query should give the segment_name and segment_type
  (ie table and its name)
  In order to salvage the uncorrupted part of the table you can add
  an entry to the initora:
  event = trace name context forever
  This will skip the corrupted block on a table scan Export the table
  drop and recreate it from import
  
  ) ORA what does it mean?
  
  Usually it comes with another error such as if it cant be found
  in any of the trace files try setting the following event in initora and
  restarting the DB
  event= trace name errorstack forever
  for the output of this look in the trace files in the directory given by
  the USER_DUMP_DEST parameter in initora
  
  ) My create database is failing with ORA: error while processing file
  
  Take out the INIT_SQL_FILES param out of initora run the scripts
  by hand after the database is created
  
  ) Out of shared memory (ORA)
  
  Try defragmenting the shared pool by running an alter system flush
  shared_pool If that is not enough increase the shared_pool_size
  parameter
  
  +==+
  

From:http://tw.wingwit.com/Article/program/Oracle/201311/17894.html
    推薦文章
    Copyright © 2005-2013 電腦知識網 Computer Knowledge   All rights reserved.