![]() All rights reserved.Ĭonnected to target database: XE (DBID=2578577487) I'll do that with RMAN as best way for that: So you have two (three) solutions to overcome this.ġ) Enlarge db_recovery_file_dest_size (from 2 to 3 GB in our case)Īlter system set db_recovery_file_dest_size=3G scope=both īackup archivelog all delete input format ' /arch_%d_%u_%s' ģ) Just delete archive logs (what I'll show as easiest way but I prefer previous two options on any production installations). SQL> show parameter db_recovery_file_dest_size ĭb_recovery_file_dest_size big integer 2GĢ, floor(space_limit / 1024 / 1024) "Size MB"ģ, ceil(space_used / 1024 / 1024) "Used MB"Ĭ:\oracle\product\flash_recovery_area 2048 2007īecause Oracle has no space to create new archived log file it freeze all operations and could wait in this state until eternity if you do not help him! ResolutionAll looks that your db_recovery_file_dest_size is full with archive logs. System command was used to delete files, then use RMAN CROSSCHECK and Delete unnecessary files using RMAN DELETE command. Add disk space and increase db_recovery_file_dest_size parameter toĤ. Back up files to tertiary device such as tape using RMANģ. ![]() Then consider changing RMAN ARCHIVELOG DELETION POLICY.Ģ. You have following choices to free up space from flash recovery area:ġ. ![]() ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 100.00% used, and has 0 remaining bytes available. In this case at the end of alert log file there are significant number of messages which will explain what goes wrong. SQL> select value from v$parameter where name = 'background_dump_dest' ĭisconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit ProductionĬ:\Users\DamirV>dir c:\oracle\product\diag\rdbms\xe\xe\trace\al*.logĭirectory of c:\oracle\product\diag\rdbms\xe\xe\trace If you do not know where is it(!?) then perform next two steps: Or worse situation when you get from users (help desk):Īlert logAs always, first step in troubleshooting Oracle is to check an alert.log. Warning: You are no longer connected to ORACLE. With the Partitioning, OLAP, Data Mining and Real Application Testing options Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production It is then necessary to restart the database instance.If you work on any Oracle database you might get in situation like this: SQL> ALTER SYSTEM SET db_recovery_file_dest=’/db02/logs’ SCOPE=spfile If you do not have additional space available to increase the size of the recovery destination then it will be necessary to move the archive logs to a new location. ![]() SQL> alter system set db_recovery_file_dest_size = 180G SCOPE=both Ĭhecking the system again confirms that the space is now available: In my case I had sufficient space available so I increased the size: This shows me that I have allocated 150G to the recovery area.īy checking the available space on the mountpoint where the destination is you are able to determine whether there is sufficient space to increase the size of the recovery destination. So, /db03/OraFlash is where the problem is and we can see that the SPACE_USED is the same as SPACE_LIMIT.ĭb_recovery_file_dest string /db03/OraFlashĭb_recovery_file_dest_size big integer 150G SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES Here we can see that the archive destination is set to USE_DB_RECOVERY_FILE_DEST so we can find this by checking the system parameter. The area used as the Archive Destination is out of space.Īrchive destination USE_DB_RECOVERY_FILE_DEST When connecting to a database via SQL*Plus (similar error would be displayed via other products) the following error is thrown: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |