how to check archive log destination size in oracle

We all know that the controlfile records information about each archivelog. Of course, after deleting these physical files in the OS We all know that the controlfile records information about each archivelog. Of course, after deleting these physical files in the OS We all know that each archivelog information is recorded in controlfile. Of course, after deleting these physical files under OS, the archivelog information is still recorded in our controlfile, the

Recently deleted the archive log of DG, [oracle@.local logs]crontab -l* 8 * * * sh /home/oracle/dbscripts/del_arc.sh This script calls the three scripts that generate the delete verification respectively. cat del_arc.sh#! /bin/bashsource /home/oracle/.bash_profilesh /home/

writes a trace file, it overwrites the existing archive file by mistake, and finally causes archive log corruption, wonderful, never seen. My final judgment is that this fault should be caused by a problem in the operating system writing, and the space of the file is still considered writable, which leads to a write conflict, in this case,

Enter the machine and set the environment variables, such as:Export oracle_home=/main/app/oracle/product/11.2. 0/db_1export oracle_sid=devdbThen switch Oracle user, admin mode login Sqlplussu - oracle[[email protected]~]$ sqlplus/nologsql> Connect/as sysdbaCheck the use of Flash recovery area, you can see the archivelog is very large, up to 99.94SQL>Select* from

Label:One set to archive mode [XHTML]View Plaincopyprint? 1 SQL> Archive log list; #查看是不是归档方式 2 SQL> alter system set log_archive_start=true scope=spfile; #启用主动归档 SQL> Alter system set log_archive_dest=' location=/oracle/ora9/oradata/arch ' scope=spfile; #设置归档路径 SQL> Alter system set log_archive_d

When this problem encountered, I did not look at the alarm log, always thought that the database lock blocking affects performance. Know that the archive log is full when the view log is found. To cause this problem to occur:Errors in File/dbbk/oracle/diag/rdbms/orcl/orcl/tr

The restoration method for a database that loses archive log files is to extract data from a database that cannot be opened normally (because one or more database files are inconsistent with other files. Scenario: A disk is damaged and a database file is lost. Unfortunately, several archive log files are lost when a da

Show parameter recover -- view the path for storing archived log files Alter database archive -- change the database to archive Mode Archive log list/SQL> select name, log_mode from v $ database; view the current status of the database Modify the path of an archived

In Oracle, data is generally stored in data files, but one of the biggest differences between the database and Oracle is that the database can be restored when data errors occur. This is our common redo file function in Oracle. The redo log is divided into two parts: Online redo lo