FRA's size
Hi gurus,
I want to take backup with RMAN. I'm gonna use FRA. Now FRA size is 21 GB and i think and guess it's not enough. So want to change FRA's_dest and size coz another logical disk has much space then current. I have several questions:
1) i will change FRA destination does old FRA_dest_size leave space? or will continue use them on previouse logical disk?
2) How much will be backup set if i use compress. App database's datafiles size are 150Gb.
3) are these right commands for changing destination and size of FRA?
In open mode:
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10G SCOPE=BOTH;
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = '/disk1/flash_recovery_area' SCOPE=BOTH;
4) i use differ location for archivelogs. i want to keep only backup sets in FRA.
Regards,
rustam_tj
1) Subsequent backups will go to the new FRA. However, you have to check how your log_archive_dest/log_archive_dest_% is configured to confirm where the archivelogs will be written to.
1b) Old backups in the FRA will be obsoleted as per your RMAN Retention Policy. Till the obsolescence is due, the Backups will be "available" (i.e. for Recovery, RMAN will expect them to be present)
2) What level of compression is achieved really depends on the data. You have to run a compressed backup with your current database to determine the compressed size. Typically it would be 1/3rd of the backup. But the actual size depends on your data.
3)Yes the commands are correct
4) See my answer 1a)
Hemant K Chitale
http://hemantoracledba.blogspot.com
Similar Messages
-
Bottleneck when switching the redo log files.
Hello All,
I am using Oracle 11.2.0.3.
The application team reported that they are facing slowness at certain time.
I monitored the database and I found that at some switching of the redo log files (not always) I am facing a slowness at the application level.
I have 2 threads since my database is RAC, each thread have 3 redo log groups multiplexed to the FRA, with size 300 MB each.
Is there any way to optimize the switch of redo log files? knowing that my database is running in ARCHIVELOG mode.
Regards,Hello Nikolay,
Thanks for your input I am sharing with you the below information. I have 2 instances so I will provide the info from each instance
Instance 1:
Load Profile Per Second Per Transaction Per Exec Per Call
~~~~~~~~~~~~ --------------- --------------- ---------- ----------
DB Time(s): 4.9 0.0 0.00 0.00
DB CPU(s): 1.1 0.0 0.00 0.00
Redo size: 3,014,876.2 3,660.4
Logical reads: 32,619.3 39.6
Block changes: 7,969.0 9.7
Physical reads: 0.2 0.0
Physical writes: 164.0 0.2
User calls: 7,955.4 9.7
Parses: 288.9 0.4
Hard parses: 96.0 0.1
W/A MB processed: 0.2 0.0
Logons: 0.9 0.0
Executes: 2,909.4 3.5
Rollbacks: 0.0 0.0
Instance 2:
Load Profile Per Second Per Transaction Per Exec Per Call
~~~~~~~~~~~~ --------------- --------------- ---------- ----------
DB Time(s): 5.5 0.0 0.00 0.00
DB CPU(s): 1.4 0.0 0.00 0.00
Redo size: 3,527,737.9 3,705.7
Logical reads: 29,916.5 31.4
Block changes: 8,893.7 9.3
Physical reads: 0.2 0.0
Physical writes: 194.0 0.2
User calls: 7,742.8 8.1
Parses: 262.7 0.3
Hard parses: 99.5 0.1
W/A MB processed: 0.4 0.0
Logons: 1.0 0.0
Executes: 2,822.5 3.0
Rollbacks: 0.0 0.0
Transactions: 952.0
Instance 1:
Top 5 Timed Foreground Events
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Avg
wait % DB
Event Waits Time(s) (ms) time Wait Class
DB CPU 1,043 21.5
log file sync 815,334 915 1 18.9 Commit
gc buffer busy acquire 323,759 600 2 12.4 Cluster
gc current block busy 215,132 585 3 12.1 Cluster
enq: TX - row lock contention 23,284 264 11 5.5 Applicatio
Instance 2:
Top 5 Timed Foreground Events
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Avg
wait % DB
Event Waits Time(s) (ms) time Wait Class
DB CPU 1,340 24.9
log file sync 942,962 1,125 1 20.9 Commit
gc buffer busy acquire 377,812 594 2 11.0 Cluster
gc current block busy 211,270 488 2 9.1 Cluster
enq: TX - row lock contention 30,094 299 10 5.5 Applicatio
Instance 1:
Operating System Statistics Snaps: 1016-1017
-> *TIME statistic values are diffed.
All others display actual values. End Value is displayed if different
-> ordered by statistic type (CPU Use, Virtual Memory, Hardware Config), Name
Statistic Value End Value
AVG_BUSY_TIME 17,451
AVG_IDLE_TIME 81,268
AVG_IOWAIT_TIME 1
AVG_SYS_TIME 6,854
AVG_USER_TIME 10,548
BUSY_TIME 420,031
IDLE_TIME 1,951,741
IOWAIT_TIME 288
SYS_TIME 165,709
USER_TIME 254,322
LOAD 3 6
OS_CPU_WAIT_TIME 523,000
RSRC_MGR_CPU_WAIT_TIME 0
VM_IN_BYTES 311,280
VM_OUT_BYTES 75,862,008
PHYSICAL_MEMORY_BYTES 62,813,896,704
NUM_CPUS 24
NUM_CPU_CORES 6
NUM_LCPUS 24
NUM_VCPUS 6
GLOBAL_RECEIVE_SIZE_MAX 4,194,304
GLOBAL_SEND_SIZE_MAX 4,194,304
TCP_RECEIVE_SIZE_DEFAULT 16,384
TCP_RECEIVE_SIZE_MAX 9.2233720368547758E+18
TCP_RECEIVE_SIZE_MIN 4,096
TCP_SEND_SIZE_DEFAULT 16,384
TCP_SEND_SIZE_MAX 9.2233720368547758E+18
TCP_SEND_SIZE_MIN 4,096
Operating System Statistics - Detail Snaps: 1016-101
Snap Time Load %busy %user %sys %idle %iowait
22-Aug 11:33:55 2.7 N/A N/A N/A N/A N/A
22-Aug 11:50:23 6.2 17.7 10.7 7.0 82.3 0.0
Instance 2:
Operating System Statistics Snaps: 1016-1017
-> *TIME statistic values are diffed.
All others display actual values. End Value is displayed if different
-> ordered by statistic type (CPU Use, Virtual Memory, Hardware Config), Name
Statistic Value End Value
AVG_BUSY_TIME 11,823
AVG_IDLE_TIME 86,923
AVG_IOWAIT_TIME 0
AVG_SYS_TIME 4,791
AVG_USER_TIME 6,991
BUSY_TIME 475,210
IDLE_TIME 3,479,382
IOWAIT_TIME 410
SYS_TIME 193,602
USER_TIME 281,608
LOAD 3 6
OS_CPU_WAIT_TIME 615,400
RSRC_MGR_CPU_WAIT_TIME 0
VM_IN_BYTES 16,360
VM_OUT_BYTES 72,699,920
PHYSICAL_MEMORY_BYTES 62,813,896,704
NUM_CPUS 40
NUM_CPU_CORES 10
NUM_LCPUS 40
NUM_VCPUS 10
GLOBAL_RECEIVE_SIZE_MAX 4,194,304
GLOBAL_SEND_SIZE_MAX 4,194,304
TCP_RECEIVE_SIZE_DEFAULT 16,384
TCP_RECEIVE_SIZE_MAX 9.2233720368547758E+18
TCP_RECEIVE_SIZE_MIN 4,096
TCP_SEND_SIZE_DEFAULT 16,384
TCP_SEND_SIZE_MAX 9.2233720368547758E+18
TCP_SEND_SIZE_MIN 4,096
Operating System Statistics - Detail Snaps: 1016-101
Snap Time Load %busy %user %sys %idle %iowait
22-Aug 11:33:55 2.6 N/A N/A N/A N/A N/A
22-Aug 11:50:23 5.6 12.0 7.1 4.9 88.0 0.0
------------------------------------------------------------- -
Hello All,
I am using Oracle RAC 11.2.0.3 with ASM.
I need you help to re size my redo logs. I know how to do that with Oracle single instance, but my question concerning Oracle RAC and ASM with Oracle Managed Files.
Below are some info based on the result returned by this query:
select l.group#,l.thread#, f.member, l.archived, l.status, (bytes / 1024 / 1024) fsize
from v$log l, v$logfile f where f.group# = l.group#
order by 1, 2
1 1 +FRA/istprod/onlinelog/group_1.257.787008381 NO CURRENT 50
1 1 +DATA/istprod/onlinelog/group_1.261.787008381 NO CURRENT 50
2 1 +FRA/istprod/onlinelog/group_2.258.787008383 YES INACTIVE 50
2 1 +DATA/istprod/onlinelog/group_2.262.787008381 YES INACTIVE 50
3 2 +DATA/istprod/onlinelog/group_3.265.787008427 NO CURRENT 50
3 2 +FRA/istprod/onlinelog/group_3.259.787008427 NO CURRENT 50
4 2 +DATA/istprod/onlinelog/group_4.266.787008427 YES INACTIVE 50
4 2 +FRA/istprod/onlinelog/group_4.260.787008429 YES INACTIVE 50I have the below question since I have RAC and ASM with Oracle Managed Files.
1. Should i be connected first to Instance 1 and do the resizing for thread 1 and then connect to instance 2 and do the resizing for instance 2?
2. Because of ASM should I use the below syntax when adding a redo log?
alter database add logfile THREAD 1 group 4 ('+DATA(ONLINELOG)','+FRA(ONLINELOG)') SIZE 100M;3. When forcing a check point a check I should use the "global" syntax as below ?
ALTER SYSTEM CHECKPOINT GLOBAL;4. Any other notes to take it into consideration ? Is there any document that help resize reo logs in my case, RAC + ASM + oracle managed files?
Regards,NB wrote:
Hello All,
I am using Oracle RAC 11.2.0.3 with ASM.
I need you help to re size my redo logs. I know how to do that with Oracle single instance, but my question concerning Oracle RAC and ASM with Oracle Managed Files.
Below are some info based on the result returned by this query:
select l.group#,l.thread#, f.member, l.archived, l.status, (bytes / 1024 / 1024) fsize
from v$log l, v$logfile f where f.group# = l.group#
order by 1, 2
1 1 +FRA/istprod/onlinelog/group_1.257.787008381 NO CURRENT 50
1 1 +DATA/istprod/onlinelog/group_1.261.787008381 NO CURRENT 50
2 1 +FRA/istprod/onlinelog/group_2.258.787008383 YES INACTIVE 50
2 1 +DATA/istprod/onlinelog/group_2.262.787008381 YES INACTIVE 50
3 2 +DATA/istprod/onlinelog/group_3.265.787008427 NO CURRENT 50
3 2 +FRA/istprod/onlinelog/group_3.259.787008427 NO CURRENT 50
4 2 +DATA/istprod/onlinelog/group_4.266.787008427 YES INACTIVE 50
4 2 +FRA/istprod/onlinelog/group_4.260.787008429 YES INACTIVE 50I have the below question since I have RAC and ASM with Oracle Managed Files.
1. Should i be connected first to Instance 1 and do the resizing for thread 1 and then connect to instance 2 and do the resizing for instance 2?Yes, that would be appropriate.
2. Because of ASM should I use the below syntax when adding a redo log?
alter database add logfile THREAD 1 group 4 ('+DATA(ONLINELOG)','+FRA(ONLINELOG)') SIZE 100M;
Yes.
3. When forcing a check point a check I should use the "global" syntax as below ?
ALTER SYSTEM CHECKPOINT GLOBAL;
Yes.
>
4. Any other notes to take it into consideration ? Is there any document that help resize reo logs in my case, RAC + ASM + oracle managed files?Not really something that comes to mind right away. But you have very small sized log files at the moment and you are adding (or planning) now too about 100M. You may want to check that the size chosen by you is adequate enough not to cause you any checkpointing issues in the later run.
HTH
Aman.... -
I need a script to reduce the size of the Fra which has used 34 gb in space
I need an rman script to reduce the size of the Fra:
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROL FILE 0 0 0
REDO LOG 0 0 0
ARCHIVED LOG 0 0 0
BACKUP PIECE 0 0 0
IMAGE COPY 0 0 0
FLASHBACK LOG 69.99 19.33 2357
FOREIGN ARCHIVED LOG 0 0 0
7 rows selected.
SQL> SELECT
2 ROUND((A.SPACE_LIMIT / 1024 / 1024 / 1024), 2) AS FLASH_IN_GB,
3 ROUND((A.SPACE_USED / 1024 / 1024 / 1024), 2) AS FLASH_USED_IN_GB,
4 ROUND((A.SPACE_RECLAIMABLE / 1024 / 1024 / 1024), 2) AS FLASH_RECLAIMABLE_GB,
5 SUM(B.PERCENT_SPACE_USED) AS PERCENT_OF_SPACE_USED FROM
6 V$RECOVERY_FILE_DEST A,
7 V$FLASH_RECOVERY_AREA_USAGE B
8 GROUP BY
9 SPACE_LIMIT,
10 SPACE_USED ,
11 SPACE_RECLAIMABLE ;
FLASH_IN_GB FLASH_USED_IN_GB FLASH_RECLAIMABLE_GB PERCENT_OF_SPACE_USED
50 34.99 11.14 69.99In /gateprd/ARCHIVE/*.arc
This is the script to remove the archives after it has been backup by the netbackup policy named Archive. This policy removes the archives that have been backed up.
/home/oracle/dba/scripts> more rmovarch.sh
#!/bin/ksh
# compress /gateprd/ARCHIVE/*.arc
find /gateprd/ARCHIVE/*.arc -type f ! -exec echo {} > /home/oracl
e/dba/lists/ARCHIVElist \;
if test $(cat /home/oracle/dba/lists/ARCHIVElist|wc -l) -gt 0
then
echo "Hay archives. Se corre script de borrar"
/home/oracle/dba/scripts/ARCHIVE_BACKUP.sh ARCHIVE
else
echo "No archives!!"
fi -
Hi,
FRA is area which stores all the recovery file for backup and recovery purpose.
But How to estimate the FRA size If our database is 800GB
Do we need FRA size equal to database size?
Give some more details how to deal with FRA.
Thanks for you time.As FRA constitutes the backup files of your database so in a very generic answer,it should be atleast double of your db size.Than add the details of how much you are dml prone and than how many archive logs , flashback logs you create and all that and it will increase. Please have a look at the doc link given.
Aman.... -
FRA in use, backups written directly to a deduplication device
Oracle 11.1.0.7
An FRA is in use to store archive logs and flashback logs.
RMAN full and incremental backups write directly to EMC's Data Domain, a deduplication storage system, this appliance replicates to a secondary recovery location.
The Data Domain storage device is nfs-mounted to the database server, for our purposes it looks to be disk.
Before we nfs-mounted this storage area, we used NetBackUp SBT_TAPE.
Now that we are nfs-mounted we are removing NetBackUp and writing directly to DISK.
Storage conservation and reliability are the reasons behind the decision to move backup sets out of the FRA.
Sounds reasonable; we don't need duplicate storage of the backup in the FRA (in ASM) and then backing it up to the dedup location.
Also, the backup is immediately replicated to another location, so that intermediary time when the backup set resides only in the FRA is
eliminated, so the possibility of something happening goes away.
We are following a Best Practices document from EMC Data Domain. Another distinction this document makes is that archivelogs should be backed up separately and not with the backupset to take full advantage of dedupping rates.
While I understand the logic, from the Oracle perspective there are things that we give up by not fully utilizing the FRA. They may be a small number of things that are not impactfull, but I'm gathering a list of facts. Some things I think :
- BACKUP RECOVERY AREA can't be used
- more manual management of backup sets requiring different backup commands
- size management of the FRA considers all pieces of the backup, flashback and archivelogs
I'm sure there are things missing from this list. I am also sure that we will continue to span FRA and Dedup storage for Oracle backups, but I'd like to know all of the facts on what I'm losing by doing so.
Any insight would be appreciated.
SherrieOracle 11.1.0.7
An FRA is in use to store archive logs and flashback logs.
RMAN full and incremental backups write directly to EMC's Data Domain, a deduplication storage system, this appliance replicates to a secondary recovery location.
The Data Domain storage device is nfs-mounted to the database server, for our purposes it looks to be disk.
Before we nfs-mounted this storage area, we used NetBackUp SBT_TAPE.
Now that we are nfs-mounted we are removing NetBackUp and writing directly to DISK.
Storage conservation and reliability are the reasons behind the decision to move backup sets out of the FRA.
Sounds reasonable; we don't need duplicate storage of the backup in the FRA (in ASM) and then backing it up to the dedup location.
Also, the backup is immediately replicated to another location, so that intermediary time when the backup set resides only in the FRA is
eliminated, so the possibility of something happening goes away.
We are following a Best Practices document from EMC Data Domain. Another distinction this document makes is that archivelogs should be backed up separately and not with the backupset to take full advantage of dedupping rates.
While I understand the logic, from the Oracle perspective there are things that we give up by not fully utilizing the FRA. They may be a small number of things that are not impactfull, but I'm gathering a list of facts. Some things I think :
- BACKUP RECOVERY AREA can't be used
- more manual management of backup sets requiring different backup commands
- size management of the FRA considers all pieces of the backup, flashback and archivelogs
I'm sure there are things missing from this list. I am also sure that we will continue to span FRA and Dedup storage for Oracle backups, but I'd like to know all of the facts on what I'm losing by doing so.
Any insight would be appreciated.
Sherrie -
Why the flashback log'size smaller than the archived log ?
hi, all . why the flashback log'size smaller than the archived log ?
Lonion wrote:
hi, all . why the flashback log'size smaller than the archived log ?Both are different.
Flash logs size depends on parameter DB_FLASHBACK_RETENTION_TARGET , how much you want to keep.
Archive log files is dumped file of Online redo log files, It can be either size of Online redo log file size or less depending on online redo size when switch occurred.
Some more information:-
Flashback log files can be created only under the Flash Recovery Area (that must be configured before enabling the Flashback Database functionality). RVWR creates flashback log files into a directory named “FLASHBACK” under FRA. The size of every generated flashback log file is again under Oracle’s control. According to current Oracle environment – during normal database activity flashback log files have size of 8200192 bytes. It is very close value to the current redo log buffer size. The size of a generated flashback log file can differs during shutdown and startup database activities. Flashback log file sizes can differ during high intensive write activity as well.
Source:- http://dba-blog.blogspot.in/2006/05/flashback-database-feature.html
Edited by: CKPT on Jun 14, 2012 7:34 PM -
I was not sure this was the most appropriate forum for this question; if not, please feel free to make an alternative suggestion.
For those of us who run multiple databases on a box with shared disk for FRA, I am finding the extra layer of ASM and db_recovery_file_dest_size to be a minor inconvenience. The Best Practice white papers I have found so far say that you should use db_recovery_file_dest_size, but they do not specify how you should set it. Currently, we have been setting db_recovery_file_dest_size rather small, as the databases so far are small and even at 3x the database size, the parameter is still significantly smaller than the total disk available in that diskgroup.
So, my question; is there any downside to setting db_recovery_file_dest_size equal to the total size of the FRA diskgroup for all databases? Obviously, this means that the amount of free space in the diskgroup may be consumed even if db_recovery_file_dest_size is not yet full (as reflected in the instance V$RECOVERY_FILE_DEST). But is that really a big deal at all? Can we not simply monitor the FRA diskgroup, which we have to do anyway? This eliminates the need to worry about an additional level of disk management. I like to keep things simple.
The question is relevant to folks using other forms of volume management (yes, I know, ASM is "not a volume manager"), but seems germane to the ASM forum because most articles and DBAs that I have talked to are using ASM for FRA.
Most importantly, what ramifications does "over-sizing" db_recovery_file_dest_size have? Aside from the scenario above.
TIAAs a general rule, the larger the flash recovery area(db_recovery_file_dest_size ), the more useful it becomes. Ideally, the flash recovery area should be large enough to hold a copy of all of your datafiles and control files, the online redo logs, and the archived redo log files needed to recover your database using the datafile backups kept under your retention policy.
Setting the size of DB_FILE_RECOVERY_DEST_SIZE must be based on following factors.
1) your falshback retention target,
2) what all files you are storing in flashback and
3) if that inclueds backup then the retention policy for them or how often you move them to tape
The bigger the flash recovery area, the more useful it becomes. Setting it much larger or equal to you FRA disk group does not cause any [b]overhead that is not known to Oracle.
But there are reasons why Oracle lets you define a disk limit, which is the amount of space that Oracle can use in the flash recovery area out of your FRA disk group.
1) A disk limit lets you use the remaining disk space for other purposes and not to dedicate a complete disk for the flash recovery area.
2)Oracle does not delete eligible files from the Flash Recovery Area until the
space must be reclaimed for some other purpose. So even though your database size is 5GB your restention target is very small but if your recovery_dest_size is much larger it will just keep filling.
3)Say in my case I have one FRA disk group of 150GB shared by 3 different databases. Based on the nature and criticaly of the database I have different size requirement of flashback recovery area for these databases. So I use varrying db_file_recovery dest_size (30GB, 50GB,70GB) respectively for meeting my retention target or the kind of files and backup I want to store them in FRA for these databases.
Oracle Internal Space management mehcanism for Falshback recovery area itself is designed in such way that if you define your db_recovery_file_dest_size and DB_FLASHBACK_RETENTION_TARGET at a optimal value, you wont need any further administration or management. If a Flash Recovery Area is configured, then the database uses an internal algorithm to delete files from the Flash Recovery Area that are no longer needed because they are redundant, orphaned, and so forth. The backups with status OBSOLETE form a subset of the files deemed eligible for deletion by the disk quota rules. When space is required in the Flash Recovery Area, then the following files are deleted:
a) Any backups which have become obsolete as per the retention policy.
b) Any files in the Flash Recovery Area which has been already backed up
to a tertiary device such as tape.
c) Flashback logs may be deleted from the Flash Recovery Area to make space available for other required files.
NOTE: If your FRA is 100GB and 3 databases have thier DB_RECOVERY_FILE_DEST set FRA then logically the total of db_recovery_file_dest_size for these 3 databases should not exceed 100GB. Even though practically it allows you to cross this limit.
Hope this helps. -
RAC 11GR2 + ora-00206 after disable FRA
Hi all,
I had a diskgroup FRA_DATA with a size of 600Go and i want to reduce this diskgroup to 300Go.
I put the database RAC in noarchivelog mode and i have deactivate the FRA.
I reduce the size of this diskgroup to 300Go.
Then, when i restart the database, i have this problem :
Oracle want to find the controlfile of my FRA but it doesn't exist.
this is an extract of the init file :
control_files = "+RACDB_DATA/lpm/controlfile/current.256.756570549"
control_files = "+FRA_DATA/lpm/controlfile/current.256.756570549"
This is an extract of the alert.log :
ALTER DATABASE OPEN
This instance was first to open
Picked broadcast on commit scheme to generate SCNs
SUCCESS: diskgroup FRA_DATA was dismounted
SUCCESS: diskgroup FRA_DATA was dismounted
Wed Oct 12 13:49:27 2011
Errors in file /oracle/app/oracle/diag/rdbms/lpm/lpm1/trace/lpm1_ckpt_27957.trc:
ORA-00206: error in writing (block 3, # blocks 1) of control file
ORA-00202: control file: '+FRA_DATA/lpm/controlfile/current.256.756570549'
ORA-15078: ASM diskgroup was forcibly dismounted
ORA-15078: ASM diskgroup was forcibly dismounted
Errors in file /oracle/app/oracle/diag/rdbms/lpm/lpm1/trace/lpm1_ckpt_27957.trc:
ORA-00221: error on write to control file
ORA-00206: error in writing (block 3, # blocks 1) of control file
ORA-00202: control file: '+FRA_DATA/lpm/controlfile/current.256.756570549'
ORA-15078: ASM diskgroup was forcibly dismounted
ORA-15078: ASM diskgroup was forcibly dismounted
CKPT (ospid: 27957): terminating the instance due to error 221
Wed Oct 12 13:49:28 2011
System state dump is made for local instance
System State dumped to trace file /oracle/app/oracle/diag/rdbms/lpm/lpm1/trace/lpm1_diag_27743.trc
Wed Oct 12 13:49:28 2011
ORA-1092 : opitsk aborting process
Trace dumping is performing id=[cdmp_20111012134928]
Wed Oct 12 13:49:28 2011
License high water mark = 1
Instance terminated by CKPT, pid = 27957
USER (ospid: 28062): terminating the instance
Instance terminated by USER, pid = 28062
Could you help me plase ?
Thanks !!!
Edited by: user12064507 on 12 oct. 2011 05:14Please go to anyone one of the rac node where you have the "lpm" db instances available and start the instance as follows :
Assuming your NODE1 instance name is lpm1. Go to RDBMS home and export the sid lpm1 :
$ cd $ORACLE_HOME ---> oracle home is the rdbms home here
$ export ORACLE_SID=lpm1
$ sqlplus / as sysdba
SQL> startup nomount ;
sql> show parameter control_files ;
Please post the result of above parameter CONTROL_FILES ...
Regards,
IMRAN KHAN -
Oracle11gr2,solaris10.
how do i check the size of my daily rman lvl0 backup.
i do a backup as compresses level 0.
i find the sizes listed in rman>list backupset summary; but i wanted to get as a consolidated.
My fra gets filled up after backing up the database continuously for 4 days. I remove the oldest backupset folder to release fra. I wanted to get a trend of how much rman is using each day for its backup.
Thanks
San~SQL> select ctime "Date"
2 , decode(backup_type, 'L', 'Archive Log', 'D', 'Full', 'Incremental') backup_type
3 , bsize "Size MB"
4 from (select trunc(bp.completion_time) ctime
5 , backup_type
6 , round(sum(bp.bytes/1024/1024),2) bsize
7 from v$backup_set bs, v$backup_piece bp
8 where bs.set_stamp = bp.set_stamp
9 and bs.set_count = bp.set_count
10 and bp.status = 'A'
11 group by trunc(bp.completion_time), backup_type)
12 order by 1, 2;
Date BACKUP_TYPE Size MB
03-JUL-10 Archive Log 7.31
03-JUL-10 Full 29.81
03-JUL-10 Incremental 2853.85
04-JUL-10 Archive Log 3.59
04-JUL-10 Full 7.45
04-JUL-10 Incremental 3.05refer : How to find backupset sizes for full and incremental backups answered by ebrian
How to find backupset sizes for full and incremental backups
Total questions 45 (39 unresolved) : mark the question as answered if you get the answer for your questions.
Announcement: Forums Etiquette / Reward Points
Posters, please mind these common-sense rules when participating here:
- When asking a question, provide all the details that someone would need to answer it. Consulting documentation first is highly recommended.
- When answering a question, please be courteous and respectful; there are different levels of experience represented here. A poorly worded question is better ignored than flamed - or better yet, help the poster ask a better question.
- It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
- See more tips in the FAQ
Thanks for doing your part to make this community as valuable as possible for everyone!
- OTN Edited by: rajeysh on Jul 7, 2010 2:11 AM -
I am on 10.2.0.4 and DB size is 150gb. Each day I have about 20 redo log switches each of 1GB. I have my rman backup on tape/separate location. How do I calculate the FRA space for DB flash for 24 hours? This is just to flash back the DB to 24 hours if any logical corruption/garunteed retension.
Thanks,
Kalyan.Will you have both archivelog and flashback logs in the FRA ?
Really it all depends on your standards, budget, monitoring, tape drives, maintenance scripts etc.
How often do you backup the database ? How often do you backup archivelogs ? If you backup archives every 24 hours, then really you want to keep minimum 48 hours and preferably 72 hours on disk to allow for failed backups, bad tapes etc.
So ... rough estimate of 60GB for 3 days archivelog + 20GB for 24 hours flashback logs = 80GB.
You can reduce this by increasing archivelog backup frequency and reducing archivelog retention (backup archivelog all delete input). -
Hello members, hope you are having a good day.
Is it a good idea to back up FRA to tape in the same script as RMAN backup of database to FRA? This will backup RMAN to FRA and then backup FRA to tape. If not, I will create a separate script that will back up the FRA to tape. Thanks for all suggestions. I will greatly appreciate any scripts from you that I can reference. Thank you.
run {
delete noprompt obsolete;
crosscheck backup;
crosscheck archivelog all;
delete noprompt expired backup;
delete noprompt expired archivelog all;
backup as compressed backupset database plus archivelog;
backup flash recovery area;
exitAs Daniel says, it depends on the size of your backup.
Consider your Retention policy and how many full database backups you keep on-disk (in the FRA).
For example, if you have 7 days backups on disk, do you need all 7 backups to go to tape every day -- you will end up with 6 tape copies of each days backup). If your backups are small and you have the capacity and bandwidth, that would be good. -
Duplicating a database using FRA
Hello,
I'm trying to duplicate a database using a backupset stored in FRA.
However, I thought rman would go take the most recently backupset that I'd backed up but isn't what's happening.
It's trying read backup piece from tape and this is what I don't want to.
How can I do to rman read backupset stored in FRA ?
Here a excerpt from script I'm using:
[oracle@oradell01 scripts]$ rman target / rcvcat rman10g_pd01@sf01 auxiliary sys@bpd01
Recovery Manager: Release 10.2.0.4.0 - Production on Seg Fev 8 09:41:41 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PD01 (DBID=4238933412)
recovery catalog database Password:
connected to recovery catalog database
auxiliary database Password:
connected to auxiliary database: BPD01 (not mounted)
RMAN>
run {
allocate auxiliary channel c1 type sbt;
set newname for datafile 1 to '+DG1/bpd01/datafile/system.441.699983113';
set newname for datafile 2 to '+DG1/bpd01/datafile/undotbs1.442.699983125';
set newname for datafile 3 to '+DG1/bpd01/datafile/sysaux.443.699983133';
set newname for datafile 4 to '+DG1/bpd01/datafile/users.432.699983141';
set newname for datafile 5 to '+DG1/bpd01/datafile/drsys.430.699985041';
set newname for datafile 6 to '+DG1/bpd01/datafile/ifsdados.428.699985051';
set newname for datafile 7 to '+DG1/bpd01/datafile/ifsindex.429.699985179';
set newname for datafile 8 to '+DG1/bpd01/datafile/pergaindex.427.699985261';
set newname for datafile 9 to '+DG1/bpd01/datafile/pergamarc.426.699985397';
duplicate target database to bpd01
logfile
group 1 ('+DG1/bpd01/onlinelog/redo01a.log','+DG1/bpd01/onlinelog/redo01b.log') size 50m reuse,
group 2 ('+DG1/bpd01/onlinelog/redo02a.log','+DG1/bpd01/onlinelog/redo02b.log') size 50m reuse;
Thank you very much
Marcelo SinniIt's trying read backup piece from tape and this is what I don't want to.That's because you allocate manually a tape channel inside the RUN block:
allocate auxiliary channel c1 type sbt;For Duplicate use the same settings you used for the backup to the FRA.
Werner -
Hi oracle's guru!
I need some advices and directions to learn.
I'm going to use FRA.
1. can i specific file formats for database backup files and control files? I run backup database plus archivelogs and there are 5 files with random names (rman generates itself). Can i add any tag for them?
2. Why i have 4 files instead 2? my database is not big enough. XE with default schemas.
regards,
rustamHi Jörg,
that depends on several settings. Thanks, i got it now.
For example: If you use filesperset 1 than only 1 file will be included in a backupset.If you have 4 tablespaces it will > create 4 backupsets. XE per default has system, sysaux, undo, users - 4 tablespaces. In addition if you open > channels then 4 backupsets are generated.I didnt change this value so i think default value is 3, coz created new tablespace and even add new datafiles and always got 3 backupsets. I read in oracle document that:
Specifies the maximum number of input files in each backup set. If you set FILESPERSET = n, then RMAN never includes more than n files in a backup set. The default for FILESPERSET is the lesser of these two values: 64, number of input files divided by the number of channels. For example, if you back up 100 datafiles by using two channels, RMAN sets FILESPERSET to 50.
RMAN always attempts to create enough backup sets so that all allocated channels have work to do. An exception to the rule occurs when there are more channels than files to back up. For example, if RMAN backs up two datafiles+ when three channels are allocated and FILESPERSET = 1, then one channel is necessarily idle.+
So i can manage the number of backupsets, right? How much should i have? many files with min sizes or some files with big size?
Hi Hemant K Chitale,
Ok, thanks a lot. I didnt know that i can create controlfile in FRA. What is the benefit of this strategy?
controlfile backups / autobackups would be in BACKUPPIECE.but in another folder and not with backupsets folder, right? coz my database backupsets are in ...\FRA\XE\BACKUPSET\ and backupset of controlfiles are in ...\FRA\XE\AUTOBACKUP\
regards and thanks,
rustam -
Should FRA be placed in SAN/NAS?
DB Version:10g2 and up
OS: AIX 6.1, Solaris 10
We are configuring RMAN for few of our databases (around 1.5 TB each). Two questions:
1.Should FRA(or non-FRA backup location) be configured in a non-AIX filesystem like SAN/NAS? Is this the standard practice?
2. For DB Storage;which is better , SAN or NAS?Hi J.Kiechle,
1.Should FRA(or non-FRA backup location) be configured in a non-AIX filesystem like SAN/NAS? Is this the standard practice?It depends on the size of your database and your backup strategy. If it all fits on your internal disks.. why not. But you should also consider long term.
2. For DB Storage;which is better , SAN or NAS?It depends on your storage capacity and performance requirements.
- Karl Arao
karlarao.wordpress.com
karlarao.tiddlyspot.com
Maybe you are looking for
-
MacMini mid-2011/ Yosemite w Samsung Syncmaster monitor
Hello all. I have been happily working with my MacMini mid-2011 (2.3Ghz Intel Core i5, 8GB RAM) with a Samsung Syncmaster B2440 HDMI-connected to it for a long time. Since the upgrade to Mavericks and later to Yosemite, the following problem occurs:
-
Can't get my ipod to connect to itunes
ok so i updated my ipod touch 3rd generation two days ago and i tried to connect it to my itunes last night. it said i had to update my itunes to the newest version 7.1 so that my ipod could connect if not it just charges and i tried to update my itu
-
Have OSX 10.5.8 and need OSX 10.6.8 to update iTunes so I can synk my iPad. Is this possible? I can't afford to buy a new computer at this time.
-
Hi I am making up a time sheet calculator (example below), and need help figuring out how to calculate overtime. I figured out how to calculate total time for the day ( SUM=(B2-A2)+(D2-C2) ) and calculating over time is simple if the total time is gr
-
Hi, After selecting an item from Shopping Cart if am going to Commit the order then following Error Occurs: Server Error Transaction was rolled back: Error in ejbCreate: javax.ejb.EJBException: OrderDAOFactory.getDAO: Exception while getting DAO type