Cause: OrA-00257 error (not enough space). By looking up the data, most of them say that it is caused by too many archived logs, which take up all the remaining space on the hard disk. This can be solved by simply deleting the logs or increasing the storage space.
Solutions:
1. SecureCRT log in to the server, switch user Oracle, and connect to Oracle
[root@userbeta~]# su – oracle
[oracle@userbeta~]$ sqlplus /nolog
SQL> connect /as sysdba
2. Check the use of Flash Recovery Area. It can be seen that ArchivelOG is already large, reaching 99.94
SQL> select * from V$FLASH_RECOVERY_AREA_USAGE;
3. Now clean up the archivelog archivelog and backup is recommended for production
Query the log directory location
show parameter recover;
4. Log out of SQLPLUS, log in with root, and delete the archive logs after backup
Enter a target address first; Create a new Oracle archive log backup directory
Mkdir Oracle archive log backup
Go to the archive log source directory (UPRR is the database instance name) :
cd /mnt/install/ora_11g/app/oracle/flash_recovery_area/UPRR/archivelog/
First go outside the Archivelog directory:
cd ..
Backup archivelog archive logs to the previously created oracle archivelog backup directory:
Cp-rf archivelog/MNT /oracle archivelog backup /
After waiting for the backup to complete, delete the archive logs that have been backed up
5. After the archive log is deleted, the control file must be maintained with RMAN, otherwise the space display will not be released
Log in to the server using Oracle user and enter RMAN maintenance:
rman target sys/pass
Check for some useless Archivelog
RMAN> crosscheck archivelog all;
Delete all Archivelog as of the previous day
RMAN> delete archivelog until time ‘sysdate-1’ ;
6. Query the use of Flash Recovery Area again:
Follow step 1 to enter the SQLPLUS environment, then use the following command to query the discovery, using only 0.66%, indicating that the archived logs have been cleared successfully!
SQL> select * from V$FLASH_RECOVERY_AREA_USAGE;
Solutions:
1. SecureCRT log in to the server, switch user Oracle, and connect to Oracle
[root@userbeta~]# su – oracle
[oracle@userbeta~]$ sqlplus /nolog
SQL> connect /as sysdba
2. Check the use of Flash Recovery Area. It can be seen that ArchivelOG is already large, reaching 99.94
SQL> select * from V$FLASH_RECOVERY_AREA_USAGE;
3. Now clean up the archivelog archivelog and backup is recommended for production
Query the log directory location
show parameter recover;
4. Log out of SQLPLUS, log in with root, and delete the archive logs after backup
Enter a target address first; Create a new Oracle archive log backup directory
Mkdir Oracle archive log backup
Go to the archive log source directory (UPRR is the database instance name) :
cd /mnt/install/ora_11g/app/oracle/flash_recovery_area/UPRR/archivelog/
First go outside the Archivelog directory:
cd ..
Backup archivelog archive logs to the previously created oracle archivelog backup directory:
Cp-rf archivelog/MNT /oracle archivelog backup /
After waiting for the backup to complete, delete the archive logs that have been backed up
5. After the archive log is deleted, the control file must be maintained with RMAN, otherwise the space display will not be released
Log in to the server using Oracle user and enter RMAN maintenance:
rman target sys/pass
Check for some useless Archivelog
RMAN> crosscheck archivelog all;
Delete all Archivelog as of the previous day
RMAN> delete archivelog until time ‘sysdate-1’ ;
6. Query the use of Flash Recovery Area again:
Follow step 1 to enter the SQLPLUS environment, then use the following command to query the discovery, using only 0.66%, indicating that the archived logs have been cleared successfully!
SQL> select * from V$FLASH_RECOVERY_AREA_USAGE;
Read More:
- Ora-00257: archiver error. Connect internal only, until free
- 【Oracle】 ORA-00257: archiver error. Connect internal only, until freed
- Unable to connect to MKS:Internal error
- Error when creating partitions in Linux: no free sectors available solution
- MongoNetworkError: failed to connect to server [localhost:27017] on first connect [Error: connect EC
- Error in `./a.out‘: free(): invalid next size (fast): 0x0000000001da8010
- How to Perfectly Uninstall ZoneAlarm Free Firewall
- Free dynamic screen capture drawing tool under MAC: KAP
- Solve to the cache because there was insufficient free space available after evict
- Free(): invalid pointer error when libtorch runs under Linux
- Tomcat Error: because there was insufficient free space available after evicting expired cache entries
- Barrier free click path source code to read
- RTMP_Connect0, failed to connect socket. 110 (Connection timed out)
- Insert datagram error: ISAM error: no free disk space
- When installing software in Ubuntu, it prompts: E: You don’t have enough free space in /var/cache/apt/archives/.
- Abnormal crash of APP startup — pointer being free was not allocated * * set a breakpoint in malloc_ error_ break to debug
- Apache service can’t be started under xampp, reporting port occupancy class error [error] Apache will not start without the configured ports free!
- JDBC connect to Sql Server to connect to the database–The TCP/IP connection to the host localhost, port 1433 has failed
- PING[ARC2]: Heartbeat failed to connect to standby ‘jzhddg’. Error is 16032.
- VMware reported an error: “internal error” internal error