Jump to Navigation


ORA-xxxx error message.

302 - ORA-46267 DBMS_AUDIT_MGMT.init_cleanup

1. ORA-46267: Insufficient space in 'string' tablespace, cannot complete operation

Cause: Could not complete the operation because the DBMS_AUDIT_MGMT API involved movement of one
           or more audit tables and there was not enough space in the destination tablespace.
           Maybe it was SYSAUX or SYSTEM tablespace.

Action: You should extend it as enough space available to purge.


247 - ORA-27102: out of memory Linux-x86_64 Error

When trying to increase the SGA to approach half available RAM with an Oracle 64-bit
version on a Linux 64-bit operating system, even though shmmax is set to match half the amount of RAM,
you get the following error when trying to start the instance :

SQL> startup nomount

ORA-27102: out of memory
Linux-x86_64 Error: 28: No space left on device Changes


242 - ORA-00845 When Starting Up An 11g Instance With AMM Configured

On a Linux system, trying to start up an 11g instance could fail with the following error :

ORA-00845: MEMORY_TARGET not supported on this system

Iin terms of 11g, MEMORY_TARGET is used instead of SGA_TARGET and MEMORY_MAX_TARGET is used instead of
Also please confirm that ORACLE_HOME is set correctly, this error sometimes happens when it's not set correctly.

It uses /dev/shm on Linux. If max_target set over /dev/shm size, you get the error messages ORA-00845 as well.

1. Size on /dev/shm


231 - ORA-01033 when you login

When you try to login, you are getting the following error :

 ORA-01033: ORACLE initialization or shutdown in progress

It seems like one of the dbf files is broken or unreadable at this moment. You should check the recovery file.


221 - Fatal NI connect error 12170

You found an error 12170 in an alert.log.

1:23:41am -  Fatal NI connect error 12170
ns secondary err code: 12606
ns main err code: 12535



196 - ORA-01555: snapshot too old

ORA-01555 is caused by many reason. One of them is "fetch across commit" in PL/SQL sometimes.
Generally you should COMMIT less frequently within a PL/SQL loop to prevent ORA-1555 errors.
The higher frequency of commit, the sooner the extents in the undo/ rollback segments will be cleared for new transactions,
then it causes ORA-1555 errors.

To fix this problem, easy to rewrite code like this:


188 - ORA-28002: the password will expire within string days

It give you an error ORA-28002: the password will expire within string days.
You installed Oracle Database as it is, the default password policy is set to 180 days. You could not change
that default settings.

1. Check the profile for specific user


182 - Oracle exp bash: syntax error near unexpected token

When you excute the following Oracle Export command under Linux bash.

# exp user_id/password file=./tables.dmp tables=(table_a,table_b,table_c,table_d)

You could get the error :

bash: syntax error near unexpected token `('

Correct syntax is :


151 - ORA-12541 TNS no listener

An ORA-12541 error occurs when the listener for the destination server is down or unreachable.
This can be due to the listener not being started or being incorrectly configured, or it can be due to a network connection problem.

Two likely reasons for the error:

  • The database was briefly unavailable at the time when you tried to access.
  • The Oracle client application on your machine is not configured correctly.

        See: "ORA-12154 TNS could not resolve connect identifier specified", Oracle error message


126 - ORA-19602 cannot backup or copy active file in NOARCHIVELOG mode

You attempted to use RMAN to backup your database and received the following error message:

RMAN-03009: failure of backup command on ORA_DISK_1 channel
ORA-196602: cannot backup or copy active file in NOARCHIVELOG mode

This message indicates that before you can create an RMAN online backup. you need to place your database
into archivelog mode.

Enabling Archivelog Mode :



Subscribe to RSS - error

Main menu 2