How did “people you might know” find you on social software>>>
In the early morning, the program’s scheduled task was executed, and an error was reported: ora-00257: archiver error. Connect internal only, until free. Because of this problem, the timing task is wrong
Causes: ora-00257 error (insufficient space error) occurs. By searching for data, most of them say that it is caused by too many archived logs, which takes up all the remaining space of the hard disk. It can be solved by simply deleting logs or increasing storage space
Solution:
1. Secure CRT logs in to the server, switches users to Oracle, and connects to Oracle
[ root@userbeta ~]# su – oracle
[ oracle@userbeta ~]$ sqlplus /nolog
SQL> connect /as sysdba
2. Check the usage of flash recovery area. You can see that the archivelog is very large, reaching 99.94
SQL> select * from V$FLASH_ RECOVERY_ AREA_ USAGE;
3. Now let’s clean up the archivelog archive log. It is recommended to back up the production environment
Query log directory location
show parameter recover;
Similar Posts:
- [Solved] Linux Oracle bash: “sqlplus / as sysdba”: command not found
- How to Solve Error: ORA-27101: shared memory realm does not exist
- Oracle ORA-12162: TNS:net service name is incorrectly specified
- Oracle startup error ora-03113 solution
- [Solved] ORA-12012: error on auto execute of job “SYS”.”ORA$AT_OS_OPT_SY_363″
- [Solved] ORA-12162: TNS:net service name is incorrectly spe
- ORA-12518 TNSlistener could not hand off client connection [Solved]
- How to Solve ORA-01089 error: immediate shutdown in progress
- ORA-01033:ORACLE initialization or shutdown in …
- [Solved] Linux Start database Error: could not open parameter file init**.ora