NAME TYPE VALUE-db_recovery_file_dest stringdb_recovery_file_dest_size big integer 90MSQL> Alter system set db_recovery_file_dest='D:\oracle\product\10.2.0\myflash' scope=both NAME TYPE VALUE-db_recovery_file_dest_size big integer 90MSQL> sho parameter db_recovery_file_dest SQL> sho parameter db_recovery_file_dest_size SQL> alter database flashback on alter database flashback on*ERROR at line 1:ORA-38706: Cannot turn on FLASHBACK DATABASE logging.ORA-38709: Recovery Area is not enabled. Total System Global Area 167772160 bytesFixed Size 1247900 bytesVariable Size 75498852 bytesDatabase Buffers 88080384 bytesRedo Buffers 2945024 bytesDatabase mounted.SQL> alter database flashback off SQL> alter system set db_recovery_file_dest_size=80m - i reset it from 12oM to 80M. SQL> Alter system set db_recovery_file_dest='D:\oracle\product\10.2.0\newFLASH' -the reason i can specify a destination is that the size is SQL> Alter system set db_recovery_file_dest=' ' scope=both To effectively reset the db_recovery_file_dest_size parameter,so that it has an effect on the way oracle calculates the space used forįlashbacks and arcivelogs,perform the following actions,you need to turn of flashback and disable the flash recovery area by resetting the ORA-00312: online log 2 thread 1: 'D:\ORACLE\PRODUCT\ORADAT\AFINI\REDO02.LOG' ORA-19809: limit exceeded for recovery files ORA-16038: log 2 sequence# 18 cannot be archived SQL> alter system set db_recovery_file_dest_size=120M ORA-38708: not enough space for first flashback database log file ORA-38706: Cannot turn on FLASHBACK DATABASE logging. Clear the redo log files having issue due to power failure or unclean shutdown of database.Cannot turn on FLASHBACK DATABASE logging,Not enough space. Total System Global Area 2147483648 bytesģ. Redo log file seems inactive or corrupted. RMAN> backup archivelog all delete input Show parameter db_recovery_file_dest_sizeĪlter system set db_recovery_file_dest_size = 75G scope=both Check and increase the parameter current value: ORA-19815: WARNING: db_recovery_file_dest_size of 2456687415514 bytes is 100.00% used, and has 0 remaining bytes available.ģ.
#Alter system db recovery file dest size full
Checked the alert log find, we find the db_recovery_file_dest is full and alert log is giving following warning:
Total System Global Area 23584982528 bytesġ. If you are going to start the database and your Recovery file destination is full then you will also get the following error on db_recovery_file_dest is full. Reconnect with SQLPLUS and run the command again.
If you working on one SQLPLUS session and from another session DBA shutdown the database then on executing query from your session will give the error as follows: In Research found following reasons of error: My first step is looking into the alert log file which helps us to find cause of error. When we are going to start the Oracle database, i am getting the ORA-03113 error during the startup command. This may be an indication that the communications link may have gone down at least temporarily, or it may indicate that the server has gone down. ORA-03113: end-of-file on communication channelĬause: The connection between Client and Server process was broken.Īction: There was a communication error that requires further investigation.Ĭheck the alert_sid.log file on the server.
0 kommentar(er)
