LETS HANDLE THE ERRRORS ORACLE TOP 10.......

LETS HANDLE THE ERRRORS ORACLE TOP 10.......

 Reference: Oracle Documentation 

1. Error Message: ORA-01839: date not valid for month specified

Cause of Error:You tried to enter a date value, but you specified an invalid day value.
Resolution:The option(s) to resolve this Oracle error are:
Option #1Check your DD value (ie: day of the month). This value must be between 1 and the number of days in the month.
·         January - 1 to 31
·         February - 1 to 28 (1 to 29, if a leap year)
·         March - 1 to 31
·         April - 1 to 30
·         May - 1 to 31
·         June - 1 to 30
·         July - 1 to 31
·         August - 1 to 31
·         September - 1 to 30
·         October - 1 to 31
·         November - 1 to 30
·         December - 1 to 31

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2. Error Message: ORA-01722: invalid number
Cause of Error:  The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates.
Resolution:  Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation

3. Error Message : ORA-12154: TNS:couldnot resolve the connect identifier specified
Cause of Error: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
Resolution: - If you are using local naming (TNSNAMES.ORA file):- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.- If you are using directory naming:- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).- Verify that the LDAP directory server is up and that it is accessible.- Verify that the net service name or database name used as the connect identifier is configured in the directory.- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier- If you are using easy connect naming:- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).- Make sure the host, port and service name specified are correct.- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

4. Error Message: ORA-00600 internal error code

ORA-00600 internal error code, arguments: 

[string], [string], [string], [string], [string], [string], [string], [string]

Cause of Error:

:  This is the generic internal error number for Oracle program exceptions. 

This indicates that a process has encountered a low-level, unexpected condition.

Causes of this message include:

 - timeouts

 - file corruption

 - failed data checks in memory

 - hardware, memory, or I/O errors

 - incorrectly restored files

Resolution: 

Report as a bug - the first argument is the internal error number

Description of ORA-00600: A typical ORA-00600 error does not include descriptive text. The message text can
be followed by up to six arguments, which indicate the origin and attributes of the
error. The first argument is the internal error number. Other arguments are various
numbers, names, and character strings. The numbers may change meanings betweendifferent versions of Oracle. Empty brackets may be ignored. In addition to being returned to the user, internal errors are also written to theAlert file along with additional information about the event. The Alert file alsolists any trace files that may have been generated because of an internal error.
 If you receive an ORA-00600 message, report it to Oracle Support Services. Troubleshooting ORA-00600:Assume we encounter following ORA-00600 exceptionORA-00600: internal error code, arguments: [17069],[18798616],[],[],[] Metalink provides a very useful ORA-00600 Troubleshooter tool (Metalink Note:153788.1)to allow you to get the description for an ORA-00600  error.In this web tool, we can enter the 17069 (first argument) for the 17069 error: Login into the Metalink account and search for doc id “153788.1? in the
Quick find search bar and open the document.
 Follow following steps to lookup by code:a. Select the correct Error code ORA-00600b. Provide first argument of ORA-00600c. Select the appropriate database versiond. Click Lookup Error button

------------------------------------------------------------------------------------------------------------ 

5.  Error Message:ORA-12560:TNS PROTOCOL ADAPTER ERROR
Cause of Error:  A generic protocol adapter error occurred. Resolution: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete and follw the steps:

1.     Go to the windows machine that hosts the Oracle database server

2.     Go to Start -> Run -> Services.msc in windows. Locate OracleService (here OracleServiceORCL) and click on "Start" to start the oracle database service (if not already running)

3.     Once it is up and running, from the command prompt run the following:

tnsping < tnsalias >

(tnsalias entry you can find it in tnsnames.ora file)

ALSO CHECK THIS:

Seems like database is not up. It might be due to restarting machine and the instance is not set to autostart and it so not started munually after starting from services Screen.

Just goto Command prompt

1.     Set Oracle SID 

2.     C:>set oracle_sid=ORCL

3.     Now run Net start command. 

4.     C:>net start oracleserviceORCL

---------------------------------------------------------------------------------------

6.Error Message: ORA-03113 error is an unexpected end-of-file that occurred which could not be handled by SQL*Net 

Cause of Error:

All connections between a client software and an Oracle Server are 

created and managed by Oracle Networking or Net8. This is a two 

way connection between a Net8 Server (Listener) and a Net8 

client. After a connection is established between the two, this error 

may occur when the net8 server is no longer available, or can not 

respond to Net8 client requests due to problems with the Oracle 

Server.It can also be due to a network failure. If it occurs at startup 

a configuration or installation problem is a likely cause. If it occurs 

after a shutdown some defunct processes may be running.

Resolution:

Oracle Server Errors

If the failure occurs after a connection is established, a likely cause is a database server

 error. For example in my personal experiences all versions of Oracle server before 

8.1.6 are pretty unstable under Windows NT 4.0 with Service Pack 6.0 and frequent 

internal errors cause the server to discontinue its operation. In such cases one should 

see the alert log and will usually have to refer to Oracle Support. In the case mentioned 

above you should downgrade to Service Pack 5.

Net8 Server (Listener) Errors

This is when the listener fails to respond to Net8 client. The causes for such a failure are

numerous. Lack of memory on the server machine where the listener resides, or 

problems with the host operating system can cause the listener to fail. To make sure that

 the listener is working correctly one may use the Listener Control Utility (LSNRCTL). 

One may also restart listener using the host operating system facilities LSNRCTL or to 

recover from temporary errors.

The Network Connection Failure

This is when the network connection through the network protocol is no longer available. 

For example when using the TCP, a TCP/IP route must be available between the client 

machine and the server. This may be tested using the ping utility. There are also 

situations when a specified protocol is disabled for a machine, say when conflicting IP 

addresses occur or a router device or software fails. In such cases it may be possible to 

reach the listener through other protocols like Named Pipes. In such cases you should

 call for the network administrator to fix the problem or you can change the protocol in 

use. To change the protocol, change the protocol entry and the parameters for the 

connection string in use, in TNSNAMES.ORA or for the method in use (Oracle Names or 

external naming services.) Say in the TNSNAMES.ORA one may start using conn_nmp 

(Named Pipes) after conn_tcp fails. However bear in mind that in this case the listener 

must support NMP too for a connection to be established. To have listener support a 

new protocol one may use Net8 Assistant, LSNRCTL or edit listener.ora manually and

 restart the listener using the host operating system facilities.

7.Error Message:  ORA-00936 Error missing expression

Cause of Error:

You tried to execute an SQL statement but you omitted a part of the syntax.

Resolution

The option(s) to resolve this Oracle error are:

Option #1

This error most commonly occurs when you try to execute an SQL SELECT statement and forget to the list of the columns in the SELECT statement.

For example, you tried to execute the following SELECT statement:

select

from suppliers;

You would receive the following error message.

You can correct the SELECT statement by including columns after the SELECT keyword. For example:

select supplier_id, supplier_name

from suppliers;

8.Error Message:  ORA-00604 :error occurred at recursive SQL level string

Cause of Error:

 An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).

Resolution

 If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.Many users of the new Oracle 11i find themselves being confronted by ORA-00604.   Oracle MOSC offers exceptional information regarding ORA-00604 in regards to the generate preventive maintenance work orders within 11.5.9 on all platforms.    It is explained that ORA-00604 occurs in Oracle Enterprise Asset Management, within the Generate Work Orders program as part of the bug 42325313.  In version 115.10.1159.5, this issue of ORA-00604 is filed within  PMEngine.java .   In order to fully resolve ORA-00604 , use the following steps provided to properly apply Patch 4232513 by MOSC:
1. Download and read the readme and pre-requisites
2. Apply Patch 4232513, but in a test environment
3. Confirm these file versions:

• PMEngine.java 115.10.1159.5

4. try re-testing
5. Upon resolution, migrate the solution to the other environments as you see appropriate

 

9.Error Message:  ORA-00257: archiver is stuck. CONNECT INTERNAL only, until freed

Cause of Error:

While trying to archive a redo log file, the ARCH process encountered an error.

Resolution

The option(s) to resolve this Oracle error are:

Option #1

This error can be caused when the destination device does not have enough storage space to store the redo log file.

Option #2

Check that the initialization parameter ARCHIVE_LOG_DEST in the initialization file is set correctly.

It may be helpful to check the archiver trace file for more details on the problem.

Note: If this problem is not resolved, Oracle will stop executing transactions.

10.Error Message:  ORA-01555: snapshot too old (rollback segment too small)

Cause of Error:This error can be caused by one of the problems, as described below.

Resolution :

The option(s) to resolve this Oracle error are:
Option #1
This error can be the result of there being insufficient rollback segments.
A query may not be able to create the snapshot because the rollback data is not available. This can happen when there are many transactions that are modifying data, and performing commits and rollbacks. Rollback data is overwritten when the rollback segments are too small for the size and number of changes that are being performed.
To correct this problem, make more larger rollback segments available. Your rollback data for completed transactions will be kept longer.
Option #2
This error can be the result of programs not closing cursors after repeated FETCH and UPDATE statements.
To correct this problem, make sure that you are closing cursors when you no longer require them.
Option #3
This error can occur if a FETCH is executed after a COMMIT is issued.
The number of rollback records created since the last CLOSE of your cursor will fill the rollback segments and you will begin overwriting earlier records

Wait For MOre .....................................