Oracle Database Error Codes 11g
Contents |
Operating System-Specific Messages Accuracy of Messages Message Format Recognizing Variable Text in Messages Message Stacks Contacting Oracle Support Services Oracle Exception Messages Trace Files The Alert File 2 ACFS-00501 to ACFS-11111 3 ACFSK-00004 to ACFSK-00091 4 ADVM-00501 to oracle 11g error codes pdf ADVM-11111 5 ADVMK-00001 to ADVMK-00028 6 AMDU-00200 to AMDU-00503 7 ASMCMD-08001 to ASMCMD-09529 8
Oracle Error Handling
AUD-00611 to AUD-00809 9 CLSCH-01001 to CLSCH-03718 10 CLSDNSSD-00000 to CLSDNSSD-03999 11 CLSGN-00000 to CLSGN-32767 12 CLSMDNS-00000 to CLSMDNS-02255 13 ora error 12154 CLSNS-00000 to CLSNS-00035 14 CLSR-00001 to CLSR-06507 15 CLSRSC-00001 to CLSRSC-04015 16 CLSS-00001 to CLSS-03202 17 CLST-01101 to CLST-03203 18 CLSU-00100 to CLSU-00912 19 CLSW-00001 to CLSW-01000 20 CRS-00001 to CRS-29006 21 DBV-00200 https://docs.oracle.com/cd/B28359_01/nav/lookup.htm?id=ERRMG to DBV-00201 22 DGM-16900 to DGM-17032 23 DIA-48001 to DIA-51705 24 DRG-10000 to DRG-52403 25 EVM-00001 to EVM-00901 26 EXP-00000 to EXP-00114 27 GIPC-00000 to GIPC-00020 28 IMG-00001 to IMG-02014 29 IMP-00000 to IMP-00402 30 JMS-00101 to JMS-00256 31 JMS-00400 to JMS-00448 32 KFED-00400 to KFED-00403 33 KFNDG-00200 to KFNDG-00701 34 KFOD-00316 to KFOD-00403 35 KUP-00552 to KUP-11602 36 LCD-00100 to LCD-00219 37 LFI-00002 to LFI-01525 https://docs.oracle.com/database/121/ERRMG/toc.htm 38 LPX-00000 to LPX-01160 39 LRM-00100 to LRM-00123 40 LSX-00001 to LSX-00345 41 MGTCA-01001 to MGTCA-01117 42 NCR-00001 to NCR-04028 43 NID-00001 to NID-00604 44 NDFN-00020 to NDFN-00025 45 NMP-00001 to NMP-00011 46 NNC-00001 to NNC-00501 47 NNF-00001 to NNF-04009 48 NNL-00001 to NNL-01078 49 NNO-00050 to NNO-00854 50 NPL-00100 to NPL-00420 51 NZE-28750 to NZE-29249 52 NZE-43000 to NZE-43021 53 O2F-00301 to O2F-00341 54 O2I-00101 to O2I-00133 55 O2U-00200 to O2U-00212 56 OCI-00601 to OCI-31199 57 OKSK-00000 to OKSK-00029 58 ORA-00000 to ORA-00877 59 ORA-00900 to ORA-01499 60 ORA-01500 to ORA-02098 61 ORA-02100 to ORA-04099 62 ORA-04930 to ORA-07499 63 ORA-07500 to ORA-09859 64 ORA-09870 to ORA-12100 65 ORA-12150 to ORA-12236 66 ORA-12315 to ORA-12354 67 ORA-12400 to ORA-12498 68 ORA-12500 to ORA-12699 69 ORA-12700 to ORA-19400 70 ORA-19500 to ORA-19997 71 ORA-19999 to ORA-24279 72 ORA-24280 to ORA-28709 73 ORA-29250 to ORA-32799 74 ORA-32800 to ORA-32857 75 ORA-33000 to ORA-37999 76 ORA-38001 to ORA-39965 77 ORA-40001 to ORA-40570 78 ORA-41001 to ORA-42804 79 ORA-43750 to ORA-45907 80 ORA-46000 to ORA-46900 81 ORA-47000 to ORA-47999 82 ORA-48001 to ORA-51705 83 ORA-53000 to ORA-54047 84 ORA-54500 to ORA-56974 85 ORA-57000 to ORA-57000 86 ORA-60001 to ORA-65535 87 PCC-020
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 through the books http://allthingsoracle.com/the-40-most-common-oracle-errors/ 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 http://kb.tableau.com/articles/knowledgebase/oracle-connection-errors 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 Top 40 Chart at the bottom of error codes 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 trying to establish a connection to your database. Simply put, it oracle error codes 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: Invalid Number (#3) You get this error when your SQL tries to convert a non-numeric string into a number. This conversion mig
a unique format. Though the TNSNames.ora file may not always be required. For instance, if you have installed only the Tableau-provided Oracle files and do not have a stand-alone Oracle client. The Oracle error messages refer to the TNSNames.ora file. Typically, correcting route or naming syntax in the Advanced Oracle Connection dialog box or using your full .WORLD database name resolves most Oracle connection issues. If your connection error requires more troubleshooting, refer to the four common connection errors listed below. ORA-03113: end-of-file on communication channelORA-12154: TNS: could not resolve the connect identifier specified HOST value incorrect or Global name incorrect or unknownORA-12514: TNS listener does not currently know of service requested in connect descriptorSERVICE value incorrectORA-12541: TNS: no listenerPORT value incorrectORA-00932: inconsistent data types ORA-03113: end-of-file on communication channel ORA-03113 is a catch-all type error for any problem interrupting an Oracle session. There can be numerous causes for this error. Please refer to the list below for some troubleshooting guidance. Refer to Oracle documentation specific to this error: My Oracle Support.Refer to Oracle's B Troubleshooting Common Errors page.Oracle recommends that you check for network problems and review the SQL*Net setup.If you're connecting to Oracle 9.2.0.5, in many cases the primary cause of this error is Oracle bug 3010227. Ask your Oracle database administrator to apply Oracle patch 9.2.0.6 or another patch appropriate for your server. Set the Oracle initialization parameter 'STAR_TRANSFORMATION_ENABLED' to FALSE.Alternatively, if you would like to test this issue further follow the optional procedure listed below. Step 1 From the Tableau Desktop start page, select Connect to Data. Step 2 For Tableau Desktop 8.2 and later, on the Connec