知识大全 OracleDBA新手经常碰到的10个Oracle错误

Posted 2022-07-15 知

篇首语：男人无志，钝铁无钢，女人无志，乱草无秧。本文由小常识网(cha138.com)小编为大家整理，主要介绍了知识大全 OracleDBA新手经常碰到的10个Oracle错误相关的知识，希望对你有一定的参考价值。

OracleDBA新手经常碰到的10个Oracle错误 以下文字资料是由(全榜网网www.cha138.com)小编为大家搜集整理后发布的内容，让我们赶快一起来看一下吧！

　　This document contains information about errors frequently encountered by 　　new DBAs along with appropriate actions to be taken in each circumstance 　　　　+==+ 　　　　Summary: 　　 MON RDBMS ERRORS 　　　　+=+ 　　　　 ) ORA 　　　　a) on Rollback segment when importing 　　　　Specify mit=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 isn t 　　　　 ) 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 aren t 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 catalog sql and expvew sql (renamed catexp sql in v ) as sys before 　　the import Both files are in $ORACLE_HOME/rdbms/admin (UNIX) 　　　　 ) ORA Invalid column name on import 　　　　Run expvew sql (catexp sql) before the import 　　　　 ) ORA Oracle not available 　　　　Startup the DB first if 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 sys dba_extents where file_id = filenum and blocknum 　　beeen 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 　　(i e table and its name) 　　In order to salvage the uncorrupted part of the table you can add 　　an entry to the init ora: 　　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 es with another error such as if it can t be found 　　in any of the trace files try setting the following event in init ora 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 init ora 　　　　 ) My create database is failing with ORA : error while processing file 　　　　Take out the INIT_SQL_FILES param out of init ora run the scripts 　　by hand after the database is created 　　　　 ) Out of shared memory (ORA ) 　　　　Try de fragmenting the shared pool by running an alter system flush 　　shared_pool If that is not enough increase the shared_pool_size 　　parameter 　　　　+==+ 　　 cha138/Article/program/Oracle/201311/17894