Fixed: ORA-01722: invalid number

Fixed: ORA-01722: invalid number

I got this error while generating reports through an application from oracle 10g database. Finally I decided to post this article so that newbie database administrator can also get the benefits. Check out root cause and solution of this error. Oracle Error: ORA-01722: invalid number Root Cause of Error: You try to execute a SQL

Fixed – ORA-12518: TNS:listener could not hand off client connection

ORA-12518: TNS:listener could not hand off client connection

You tried to connect with Oracle Database and got "ORA-12518 listener could not hand off client connection" error. Now what action will you take to get rid of this error? Here is the answer: Error Message: ORA-12518: TNS: listener could not hand off client connection. Solution-1: First check your database whether it is in start

Fixed – ORA-12528: TNS:listener: all appropriate instances are blocking new connections error

Fixed - ORA-12528: TNS:listener: all appropriate instances are blocking new connections error

This article will help you to resolve "ORA-12528: TNS listener- all appropriate instances are blocking new connections" error while connecting with Oracle XE 11g database. Error Message: ORA-12528: TNS listener- all appropriate instances are blocking new connections. Resolution: Open insnames.ora file under server\network\ADMIN\ folder. My tnsnames.ora file was located on below path. C:\oraclexe\app\oracle\product\11.2.0\server\network\ADMIN\ XE = (DESCRIPTION

Fixed – ORA-12154: TNS:could not resolve the connect identifier specified

ORA-12154 TNS could not resolve the connect identifier specified

We have faced following  issue in some versions of oracle such as Oracle 10g and Oracle 11g Express edition. "ORA-12154: TNS: Could not resolve service name" When you try to connect to an Oracle Service via Oracle Networking SQL*Net, it looks up the connect data for the service. When this lookup fails, Oracle client show

Fixed: Oracle not started-ORA-16038, ORA-19809, ORA-00312 error

Oracle not started-ORA-16038, ORA-19809, ORA-00312 error

When you try to start your database and it fails with the error code ORA-16038, ORA-19809, ORA-00312. You can resolve this error with the help of this tutorial. Error Message: ORA-16038: log 3 sequence# 572 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 3 thread 1: '/oradata2/data1/dbase/redo03.log' Root Cause: SQL> startup

Fixed: ORA-28056: Writing audit records to Windows Event Log failed

ORA-28056 Writing audit records to Windows Event Log failed-01

If you get "ORA-28056: Writing audit records to Windows Event Log failed" error while connecting with Oracle Database 11g which was installed on Windows Server 2003, you can try following method to resolve the issue. Open command prompt and try to connect with SYS privileges. Go to START > RUN > type CMD and press Enter

Fixed – ORA-00844: Parameter not taking MEMORY_TARGET into account

ORA-00844: Parameter not taking MEMORY_TARGET into account

In our previous article you have seen how to resolve ORA-19809: limit exceeded for recovery files error. In this article we will show you step by step guide to resolve "ORA-00844: Parameter not taking MEMORY_TARGET into account" error. Error Message: ORA-01078: failure in processing system parameters ORA-00844: Parameter not taking MEMORY_TARGET into account ORA-00851: SGA_MAX_SIZE

Fixed – ORA-19809: limit exceeded for recovery files

ORA-19809 limit exceeded for recovery files

If you connect with Oracle Database and it throws an error message "ORA-19809: limit exceeded for recovery files", It means there is no free space available in oracle's archive destination (db_recovery_file_dest). Error Message: Following error will show you in alert log file if you try to shutdown a database or switch a log file: ORACLE