Ora Error Messages Oracle
Contents |
MySQL MariaDB PostgreSQL SQLite MS Office Excel Access Word Web Development HTML CSS Color Picker
Ora Errors And Solutions
Languages C Language More ASCII Table Linux UNIX Java
Oracle Error Handling
Clipart Techie Humor Advertisement Oracle Basics Oracle Advanced Alter Table Alter Tablespace Change Password Check ora error 12154 Constraints Comments in SQL Create Schema Create Schema Statement Create Table Create Table As Create Tablespace Create User Data Types Declare Variables Drop Table https://docs.oracle.com/cd/B28359_01/nav/lookup.htm?id=ERRMG Drop Tablespace Drop User Error Messages Find Default Tablespace Find Users Find Users Logged In Find Version Information Functions Global Temporary Grant/Revoke Privileges Indexes Literals Local Temporary Primary Keys Procedures Roles Sequences Set Default Tablespace Synonyms System Tables Unique Constraints Views Oracle Cursors Oracle Exception Handling Oracle Foreign https://www.techonthenet.com/oracle/errors/ Keys Oracle Loops/Conditionals Oracle Transactions Oracle Triggers String/Char Functions Numeric/Math Functions Date/Time Functions Conversion Functions Analytic Functions Advanced Functions NEXT: TUTORIAL COMPLETE Oracle / PLSQL: Oracle Error Messages The following is a listing of Oracle Error Messages: 00001-00899 ORA-00001 ORA-00018 ORA-00020 ORA-00023 ORA-00028 ORA-00034 ORA-00051 ORA-00054 ORA-00057 ORA-00058 ORA-00060 ORA-00063 ORA-00068 ORA-00071 ORA-00078 ORA-00100 ORA-00107 ORA-00201 ORA-00257 ORA-00301 ORA-00304 ORA-00361 ORA-00401 00900-00999 ORA-00900 ORA-00902 ORA-00903 ORA-00904 ORA-00905 ORA-00906 ORA-00907 ORA-00908 ORA-00909 ORA-00910 ORA-00911 ORA-00913 ORA-00917 ORA-00918 ORA-00919 ORA-00920 ORA-00923 ORA-00924 ORA-00925 ORA-00926 ORA-00927 ORA-00928 ORA-00931 ORA-00932 ORA-00933 ORA-00934 ORA-00935 ORA-00936 ORA-00937 ORA-00938 ORA-00939 ORA-00942 ORA-00946 ORA-00947 ORA-00948 ORA-00955 ORA-00957 ORA-00960 ORA-00962 ORA-00971 ORA-00972 ORA-00975 ORA-00979 ORA-00980 ORA-00984 ORA-00985 ORA-00995 01000-01399 ORA-01000 ORA-01001 ORA-01002 ORA-01004 ORA-01005 ORA-01006 ORA-01007 ORA-01008 ORA-01012 ORA-01013 ORA-01014 ORA-01017 ORA-01023 ORA-01031 ORA-01033 ORA-01034 ORA-01035 ORA-01037 ORA-01039 ORA-01040 ORA-01042 ORA-01045 ORA-01052 ORA-01074 ORA-01089 ORA-01109 ORA-01113 ORA-01114 ORA-01133 ORA-01200 ORA-01234 0140
industry long enough to remember the bad old days, when every developer and DBA had a pile of dusty Oracle user guides on their desks and, every time their database or application coughed up an error, would thumb http://allthingsoracle.com/the-40-most-common-oracle-errors/ through the books with mounting desperation. Fortunately, the times have moved on and we now all outsource our memories to Google and Bing and Baidu. Our desks are clear, but our need for external help whenever we are ambushed by unexpected errors is just as strong. Using tools Google have made available, I have put together a list of the ORA messages we collectively searched for the most in the first month of 2012. These messages (see a Billboard-style oracle error Top 40 Chart at the bottom of this article) are a mix of those generic errors that can mean pretty much anything, the error messages we see most rarely, and those common error numbers that we never seem able to memorise. ORA-12154: TNS:could not resolve the connect identifier specified (#1) Coming in at number 1, and googled more than twice as often as any other error message, this error is, almost appropriately, often the very first one you get on oracle error codes trying to establish a connection to your database. Simply put, it means that you have named the database you wish to be connected to and Oracle doesn’t know who the heck you’re talking about. This error is often caused by typos, maybe in your connection string, but possibly in your tnsnames.ora file. It is also possible that the tnsnames.ora file is not accessible or does not even exist. If it does, ensure that it contains the service name you are using; also go over it with a fine toothcomb to make sure it doesn’t have any unpaired parentheses or such. ORA-00600: internal error code, arguments: [%s], [%s],[%s], [%s], [%s] (#2) Coming in at number 2 is a generic error; it means something serious has gone wrong and you are going to need to roll up your sleeves, dig in, and find out what. But you are not without clues. Your alert.log file will contain the path to your trace file. You will want to look in it, as a record is written to the trace file every time an ORA-00600 error occurs. Take the information you get from your trace file and the first argument in the square brackets (the internal message number), and head over to My Oracle Support (Metalink). There you will find a handy ORA-0600 lookup tool (Note 153788.1) that will direct you to additional information that will help you solve your problem. ORA-1722: