SQL> show parameter dbrecoveryfile NAME TYPE VALUE - dbrecoveryfiledest string dbrecoveryfiledestsize big integer 0 SQL> select from VRECOVERYFILEDEST no rows selected SQL> 2) Enable Flash Recovery Area. Make sure to clean up overlapping parameters and use only 1 of them to avoid confusion. SID Basic: Yes: Real Application Clusters: You must set this parameter for every instance, and multiple instances must have the same value. 1)Check and confirm Flash Recovery Area is not enabled. * db_recovery_file_dest_size big integer 30G I may change it to whatever I want, it will not have effect: SQL> alter system set db_recovery_file_dest_size = 30G scope=spfile SQL> show parameter db_recovery_file_dest_sizeĭb_recovery_file_dest_size big integer 10G My instance is called MIN19, so even though 20G is set for *, it will start with 10G: SQL> startup force nomount MIN19 db_recovery_file_dest_size big integer 10G SQL> alter system set db_recovery_file_dest_size =10G sid='MIN19' scope=spfile DBRECOVERYFILEDESTSIZE specifies (in bytes) the hard limit on the total space to be used by target database recovery files created in the fast recovery area. * db_recovery_file_dest_size big integer 20G SQL> show spparameter db_recovery_file_dest_size But if you have another value set with the actual sid (instance name), that takes precedence over *, and the value remains unchanged.ĭemonstration: SQL> show parameter db_recoĭb_recovery_file_dest_size big integer 20G Where 250G is the size of the flash recovery area size, SCOPE to BOTH will make the. If you set a parameter without specifying sid, then it will create/modify the entry in spfile with sid=*. SQL> ALTER SYSTEM SET DBRECOVERYFILEDESTSIZE 250G SCOPEBOTH SID. If you have enough space on drive you may also increase the size from 20 GB to 50 Gb.This is normal. For example, to set the flash recovery area size to 20 gigabytes, enter the following command: ALTER SYSTEM SET DBRECOVERYFILEDESTSIZE 20G To change the. RMAN> delete archivelog all completed before 'SYSDATE-2'
RMAN> delete archivelog all completed before 'SYSDATE-1' SQL> ALTER SYSTEM SET DBRECOVERYFILEDESTSIZE 250G SCOPEBOTH SID'' Where 250G is the size of the flash recovery area size, SCOPE to BOTH will make the change to both memory and server parameter file, SID’’ has no effect in the single instance database where as in RAC database it causes the change to take effect across all instance.
#ALTER SYSTEM DB RECOVERY FILE DEST SIZE ARCHIVE#
Other wise you copy some needed archive in other location.then use the following command for delete archive up to specific date: You can check the location of archive log by connecting as SYS userĪfter delete some archive log which expired if some space released for sufficient work then you can continue.
Please check the location where archive log is configured. Error occurred due to archive log space is full. Oracle database is not open its give error in alert log. Set the dbrecoveryfiledestsize to an appropriate size for the. Show parameter dbrecoveryfiledestsize- add 10GB size more to this parameter alter system set dbrecoveryfiledestsize 75G scopeboth 4. This statement sets the disk limit for recovery area to 100 GB: SQL> ALTER SYSTEM SET DBRECOVERYFILEDESTSIZE 100G.
#ALTER SYSTEM DB RECOVERY FILE DEST SIZE FULL#
Archive log destination full raised error 19809 Set the dbrecoveryfiledest to an appropriate location for the flashback recovery files. The dbrecoveryfiledest sets the location for the recovery area.
0 kommentar(er)
