ORA-03113: communication channel at the end of the file process ID4781 view alter. log found that the online log file has problems online method to see is not very familiar with, see a lot of errors or
ORA-03113: communication channel at the end of the file process ID4781 view alter. log found that the online log file has problems online method to see is not very familiar with, see a lot of errors or
ORA-03113: The file End Process ID4781 of the communication channel
View alter. log
An error occurred while prompting the online log file.
I am not very familiar with the methods on the Internet. I see many errors.
Ora-16038: logs cannot be archived
Ora-00312
ORA-19809: limit exceeded for recovery files
Ora-19804: cannot recycle... Disk Space
By default, the original Oracle11g archive logs are stored in the Flash recovery area, and the size of the flash recovery area is 2 GB by default. Once the space is full, there is no way to archive the files.
Start the database to the mount state, change the size of the recovery files space in statup mount, and delete the expired backup, specify the backup policy, and regularly Delete the backup.
Recommended reading:
ORA-01172, ORA-01151 error handling
ORA-00600 [2662] troubleshooting
Troubleshooting for ORA-01078 and LRM-00109
Notes on ORA-00471 Processing Methods
ORA-00314, redolog corruption, or missing Handling Methods
Solution to ORA-00257 archive logs being too large to store
SQL> show parameter db_recovery_file_dest
NAME TYPE VALUE
-----------------------------------------------------------------------------
Db_recovery_file_dest string d: \ app \ qiao \ flash_recovery
_ Area
Db_recovery_file_dest_size big integer 2G
There are three solutions:
1. Increase the flash recovery zone.
Alter system set db_recovery_file_dest_size = 50g scope = both;
2. Set the archive path to another place.
Alter system set log_archive_dest = Other paths
3. delete or transfer archived logs.
Open RMAN
Rman target/
RMAN> crosscheck archivelog all; -- run this command to mark the invalid expired archivelog.
RMAN> delete expired archivelog all; -- delete all expired archived logs directly.
RMAN> delete noprompt archivelog until time "sysdate-3"; -- delete the archive three days before the current date of the system without prompt or direct deletion. Or (delete archivelog all completed before 'sysdate-7 ')
Specify the retention policy (RMAN's backup retention policy) so that archivelog does not add this
Command Format:
Configure retention policy clear --------------- use the default value for the backup retention policy
Configure retention policy to none ------------ no backup retention policy is used
Configure retention policy to recover window of integer days ------------ a time-based backup retention policy that retains the backup files a few days ago
Configure retention policy to redundancy integer ------- Based on the backup retention policy of redundant backup, retain several redundant backup files
Run the report obsolete command to view the backup files in the OBSOLETE state.
The delete obsolet command can immediately DELETE files (discarded files) that are not required by the backup retention policy ).
RMAN> configure retention policy to recovery window of 7 days; all backups within seven days are retained.
RMAN> configure retention policy to redundancy 3; 3 redundant backups are retained for each data file.
SQL> alter system db_recovery_file_dest_size = 4G scope = both;
Of course, we can write a simple shell script to manage archived logs.
#! /Bin/bash
# Confirm oracle runing environment
./Home/oracle/. bash_profile
Ps-ef | grep dbw0 _ $ ORACLE_SID | grep-v grep>/dev/null
If [$? -Eq 0]; then
Rman target/log =/orabackup/delarch 'date + % Y % m % D'. log < Crosscheck archivelog all;
Delete noprompt expired archivelog all;
Backup as compressed backupset archivelog all format'/orabackup/cron-archlog _ % U _ % d _ % T _ % s _ % P' delete input;
Exit;
EOF
Fi
The preceding script backs up and deletes the oracle archive, modifies it as needed, and adds it to crontab.