SQL> shutdown immediateDatabase closed.SQL> startup mountORACLE instance started. #ALTER SYSTEM DB RECOVERY FILE DEST SIZE ARCHIVE#SQL> alter system set db_recovery_file_dest_size=1500GB sid='*' scope=both Īlter system set db_recovery_file_dest_size=1500GB sid='*' scope=both 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. Modify the archive log to the default storage path of the database Repeat the above operation to confirm whether the path of the archive log is the path of the flashback area. When we tried to increase the size of Fast Recovery Area (FRA), we got ORA-02065. I have talked about it in the post: ALTER SYSTEM SWITCH LOGFILE vs ARCHIVE LOG CURRENT. You must set this parameter for every instance, and multiple instances must have the same value. To make current redo log archive and switch to the next redo, we can explicitly perform an archival. 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. Not all archived log related operations are invalid at system-level, at least, there's one operation on archived log is valid to use ALTER SYSTEM. Actually, you should enable archivelog mode at database-level which uses ALTER DATABASE. ORA-02065 means that the operation at system-level is not valid, which means your ALTER SYSTEM statement is illegal syntactically. ORA-02065: illegal option for ALTER SYSTEM Some may try to enable archivelog mode like the followings, but it failed with ORA-02065: SQL> alter system archivelog To make archivelog destination same as FRA execute below command.Īlter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST' scope=both sid='*' STEP 3: Stop database and start in mount ~]$ srvctl status database -d ~]$ srvctl stop database -d ~]$ srvctl start database -d orahow2c -o ~]$ srvctl status database -d orahow2c STEP 4: Enable Archiving of RAC Database.There're 2 error patterns of ORA-02065 in this post. NOTE: You can also set db_recovery_file_dest path to local file system or Linux directory. SQL> alter system set db_recovery_file_dest='+RE_QTR4' scope=both sid='*' SQL> alter system set db_recovery_file_dest_size=80G scope=both sid='*' If you exceed the size of your flashback recovery area, the offending task. SQL> alter system set dbflashbackretentiontarget 2880 How far back you can flash back also depends on how much flashback data Oracle has kept in the flashback recovery area. Here we can see it is already set, if not then set it using below command. The following statement changes the flashback time from the default of 1 day to two days. db_recovery_file_dest is the location and db_recovery_file_dest_size is the quota/size for FRAĭb_recovery_file_dest_size big integer 80G So first we need to configure FRA as archiving destination if it is not set.ĭb_recovery_file_dest and db_recovery_file_dest_size parameter need to be set for FRA. SQL> show parameter DB_RECOVERY_FILE_DESTĭb_recovery_file_dest_size big integer 80G STEP 2: Configure archive destination for archiving redo logs.įrom the above output we can see that database is using Flash recovery area – FRA (DB_RECOVERY_FILE_DEST) for archive destination which is the default Oracle managed location for centralized backup and recovery files. STEP 1: Check archivelog mode SQL> select log_mode,name from v$database Īrchive destination USE_DB_RECOVERY_FILE_DEST Steps to Enable / Disable Archivelog Mode in 19c
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |