The problems summarised on this page have been divided into two categories:
- Numbered Errors - those errors that have an error number associated with them.
- Symptomatic Problems - those errors that do not have an error number associated with them.
Everything on these pages represents a problem that I have previously encountered and the solution at that time. I believe the information to be complete and correct, but if you find any errors or omissions then please let me know (email@example.com).
Because every system is different, please review the advice on these pages carefully. My experience of Oracle is limited to Windows NT - there may be differences on other platforms. If in doubt, Oracle support should always be regarded as the final authority for any problem.
- DBV-00100: Specified file (XXXX) not accessible
- LRM-00109: Could not open parameter file
- ORA-00001: unique constraint violated
- ORA-00942: table or view does not exist
- ORA-01000: Maximum open cursors exceeded
- ORA-01004: default username feature not supported
- ORA-01013: user requested cancel of current operation
- ORA-01017: Invalid username/password
- ORA-01034: ORACLE not available
- ORA-01078: failure in processing system parameters
- ORA-01102: cannot mount database in exclusive mode
- ORA-01113: file n needs media recovery
- ORA-01418: specified index does not exist
- ORA-01466: unable to read data - table definition has changed
- ORA-01555: Snapshot too old
- ORA-01631: max # of extents nnn reached in table xxxx
- ORA-01691: unable to extend lob segment ...
- ORA-01843: not a valid month
- ORA-01990: Error opening password file ...
- ORA-01991: Invalid password file ...
- ORA-02170: FREELIST GROUPS storage option not allowed
- ORA-03121: no interface driver connected
- ORA-04030: out of process memory
- ORA-04031: unable to allocate ... shared memory
- ORA-04043: object SSS.NNN does not exist
- ORA-09352: OracleService(SID) has not been started
- ORA-12154: TNS:could not resolve service name
- ORA-12203: TNS: unable to connect to destination
- ORA-12224: TNS: no listener
- ORA-12505: TNS: listener could not resolve SID given in connection description
- ORA-12516: TNS:listener could not find available handler with matching protocol stack
- ORA-12541: TNS: no listener
- ORA-12545: Connect failed because target host or object does not exist
- ORA-12560: TNS:protocol adapter error
- ORA-12571: TNS:packet writer failure
- ORA-27102: out of memory
- RMAN-06089: archive log XXX not found or out of sync with catalog
- TNS-01169: The Listener has not recognised the password
Note: Some TNS related errors may be reported as ‘TNS-nnnnn’ rather than ‘ORA-nnnnn’. This seems to vary according to the tool that is reporting the error. They are listed above according to how I first encountered the error.
I also have a small collection of errors that I've either not had time to write up or have not been able to investigate thoroughly. My notes for these are available here: "Other errors"
- Checkpoint intervals are more than LOG_CHECKPOINT_TIMEOUT
- Database instance failure
- Database instance locks up
- Datafile recovery needed
- Excessive disk activity
- Oracle Instance NNNN - Cannot allocate log. Archival required
- Oracle will not start-up automatically
- Oracle will not shut down
- Thread N cannot allocate log
This page represents one page of many pages of notes I made whilst working with Oracle 7 through to 10i. I now no longer work with Oracle databases, but hope that these notes will continue to be of benefit to others.
About the author: Brian Cryer is a dedicated software developer and webmaster. For his day job he develops websites and desktop applications as well as providing IT services. He moonlights as a technical author and consultant.