10 Oracle errors that Oracledba frequently encounter (English)
This Document Contains Information About Errors Frequently Encountered by New DBAS, Along With ApproPriate Actions to Be Taken in Each Circumstance.
==
Summary: 10 Common RDBMS ErrorS
=
1) ORA-1547
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 is not.
2) ORA-1556 MAX EXTENTS OF 121 Exceeded When Storage IS set for maxExtents of 999.
Most Platforms Have A Max of 121 Even Though It Allows You To Specify 999. (See The Readme for Your Platform)
3) ORA-1090 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).
4) IMP-0003, ORA-942 and IMP-00023 ON Import.
Run catalog.sql and express .sql (renamed catexp.sql in v7) AS SYS BEFORE The Import. Both Files Are IN $ Oracle_Home / Rdbms / Admin (UNIX).
5) ORA-904 INVALID Column Name on Import.
Run ExpVew.sql (catexp.sql) Before the import.
6) ORA-1034 Oracle NOT AVAILABLE.
Startup the db first ... if it is started check your searchpath. Make sure what oracle_sid is set Correctly For Setuid Issues, See Pre 1006554.6.
7) ORA-1578 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 between block_id and (block_id blocks - 1); The filenum and blocknum are the numbers in the 1578 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 init.ora: event = "10231 trace name context forever" This will skip the corrupted block on a table scan Export. The Table, Drop and Recreate IT from Import.8) ORA-604 What Does it mean?
Usually It comes with another error Such as 1547 .... if it can't be bound in any of the trace file in init.ora and restarting the db. Event = "604 trace name errorstack forever" for ....................
9) My CREATE DATABASE IS FAILING WITH ORA-1519: Error While Processing File
Take out the init_sql_files param out of init.ora, run the scripts by hand after the database is create
10) Out of shared memory (ORA-4031).
.
==
