How To Troubleshoot Various Oracle Errors

By admin News

Published by admin on December 24, 2015

While handling your oracle database you may get stuck with some errors. Most of you don’t even know why this error has come to your screen and what will you do to fix it soon. Here is the list that will help you to know about such error and solution to fix theses error.

ORA-00904: string: invalid identifier

Cause:

This error comes if your entered column name is either missing or invalid.

Solution:
Enter a valid column name that begins with a letter, consist alphanumeric characters and $, _, and #. It must be enclosed within double quotation marks.

Oracle error 942 : table or view does not exist

Cause:

This error comes when entered table or view doesn’t exist. Certain privileges are required to access the table. If an application shows this message then it means the table that the application tried to access doesn’t exist in the database or the application doesn’t have access to it.

Solution: To fix out this error check out the following things: • Check out the spelling of the table or view name. • Is view is specified where a table is required.

Contact the database administrator if new table needs to be created or if user or application privileges are needed to access the table.

Oracle error 2291 : integrity constraint ( string . string ) violated – parent key not found

Cause:

foreign key value doesn’t matches with the primary key value.

Solution:
So to fix this error, delete the foreign key and add a matching primary key.

Oracle error 1034 : ORACLE not available

Causes:

possible reasons behind this error: • The SGA requires more space than that which is assigned for it.

• The operating system variable pointing to the instance is not properly defined.

Solution:

If oracle has been initialized then on some operating systems verify that oracle was linked correctly.

ORA-00022 invalid session ID; access denied

Cause:

May be the session that is specified is not exist or the caller doesn’t have the permission to access it.

Resolution: to fix this error you need to specify a valid session ID that you have permission to access.

Oracle error 3114 : not connected to ORACLE

Causes:

this may happen due to a call to oracle was attempted when no connection was established. It’s because a user written program has not logged on. The reason may also be when ALTER SESSION KILL SESSION or ALTER SYSTEM DISCONNECT SESSION were issued with the IMMEDIATE qualifier because in this case the client’s connection to the database is cutted off without waiting for the client to send a request.

solution:

Try to make connection again. If same error message occurs again and the program is user written then check the program.

Oracle error 12560 : TNS: protocol adapter error

Solution:

You need to check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level of transport errors. Turn on tracing and re-execute the operation. After complete operation, turn off tracing.

ORA-12170 TNS: Connect timeout occurred

Cause:

the server takes shut down because connection with the client failed to complete within the given time interval. This may happen because of the network or system delays. This indicates that a malicious client is trying to cause a Denial of service attack on the server.

Solution:
If the error occurs because of a slow network or system then reconfigure one or all the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If any malicious client suspected during this then use the address in sqlnet.log to identify the source and restrict access. But remember one thing that the logged address may not the reliable one as they can be easily forged.

These errors may lead your oracle database towards corruption and lastly you are inaccessible to use it. so if somehow due to any of these error your oracle database get corrupted then the best solution with which you can go is to make use of oracle repair tool which is a powerful and comprehensive recovery software that is mainly designed to recover corrupt or damaged Oracle database file.

Steps to use Oracle file repair tool to repair and restore Oracle dmp file

Step 1: Search Initial screen of Stellar Phoenix Oracle Recovery with a pop-up window showing options to select or search corrupt Oracle databases in your computer. 1-2444547

Step 2: Click Scan File to initiate the scan process after selecting the oracle database. The recoverable database objects get listed in left-side pane.

2-3147307

Step 3: Click an object to see its preview.

3-8730147

Step 4: : Click Start Repair in the icon bar to start the repair process. A pop-up window is displayed which show the steps needed to perform further. Click next and continue.

4-2154589