Oracle Database ORA-00257 Solutions

Today Oracle Database suddenly cannot connect, reported ORA-00257 error (insufficient space error), by looking for information, the vast majority of said this is because the Archivelog archiving log too much, accounting

Today Oracle Database suddenly cannot connect, reported ORA-00257 error (insufficient space error), by looking for information, the vast majority of said this is because the Archivelog archiving log too much, accounting

Today Oracle Database suddenly couldn't connect, reported ORA-00257 error (insufficient space error), by looking for information, the vast majority of said this is because Archivelog archiving log too much, occupying all the hard disk space caused, you can simply delete logs or increase storage space.

First, go to the oracle user and run the command rman target /:

Oracle $ test-idm-db01 $ rman target/

Recovery Manager: Release 11.2.0.1.0-Production on Wed May 15 09:29:06 2013

Copyright (c) 1982,200 9, Oracle and/or its affiliates. All rights reserved.
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges

An error is reported. If you have no space available for 100%, this error will be reported. You can only find a way to free up some space for your system, even a few hundred megabytes! Then restart the database to log on to dba.

Restart the database and run rman again.

Oracle $ test-idm-db01 $ rman target/

Recovery Manager: Release 11.2.0.1.0-Production on Wed May 15 09:29:40 2013

Copyright (c) 1982,200 9, Oracle and/or its affiliates. All rights reserved.

Connected to target database: IDM_TEST (DBID = 4064060693)

Now delete the Archivelog archive file and run the following command to delete the archive in the last seven days:

RMAN> delete archivelog from time 'sysdate-7 ';

You can also retain only the last 7 days, and delete the rest:

RMAN> delete archivelog all completed before 'sysdate-7 ';

However, after a while your logs are still full, there is no need for archiving functions like the development environment. The complete solution is to disable this function and log on to oracle using dba:

Sqlplus/as sysdba;

Then run the following command:

SQL> alter database flashback off;

Then restart the database!

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian