Operating System - HP-UX
1748216 Members
3315 Online
108759 Solutions
New Discussion юеВ

Re: HP SE database ARC file is occupying space

 
SOLVED
Go to solution
Ravi_Shankar
Frequent Advisor

HP SE database ARC file is occupying space

Oracle database is creating archive file in every 15 minute and each file size is 500 MB . Is there any way we can decrease the frequecy of ARC file so that will not run out of space.

We are using RMAN and TSM for backup. Please sugest
4 REPLIES 4
T G Manikandan
Honored Contributor
Solution

Re: HP SE database ARC file is occupying space

your oracle database is running on ARCHIVELOG mode and this is creating the arc files.

this is enabled with the init.ora file for parameter

log_archive_dest=

There is no way you can reduce the frequency of these files as once the redo logs gets filled up they are rotated and moved as archive log files.

The one way is to delete these files. If you are using RMAN you can use the "delete input" clause with the backup so that these files will be deleted as they are backed up.
T G Manikandan
Honored Contributor

Re: HP SE database ARC file is occupying space

Sample RMAN script would be something like

RMAN> run {
2> allocate channel dev1 type disk;
3> backup
4> format '/app/oracle/archback/log_%t_%sp%p'
5> (archivelog all delete input);
6> release channel dev1;
7> }

Check with your DBA.
Ravi_Shankar
Frequent Advisor

Re: HP SE database ARC file is occupying space

Can we set arc file size, database size is only 17 GB and its creating 500 MB arc file in every 15 Minutes, this does not sound good. Its seems something is wrong with the database.

Is there anyway we can set archive file size , its should not create 500 MB archive file everey 15 Minutes.

TSM client is installed on SE server to take full backup. Could you please suggest if we fix this issue by modifying Oracle configuration and will see if anything can be done from TSM side.
Sivakumar MJ._1
Respected Contributor

Re: HP SE database ARC file is occupying space

Hi Manikandan,

For the above issue, can we try in disable /enable the RMAN... It would clean it's archive logs.

Will DBADMIN will help somewhere..