1 Week = 168 Hours

2 Weeks = 336 Hours

3 Weeks = 504 Hours
4 Weeks = 672 Hours
5 Weeks = 840 Hours
6 Weeks = 1008 Hours
7 Weeks = 1176 Hours

1 Week, 7 Days, 168 Hours, 10,080 Minutes and 604,800 Seconds

1 day= 1440 minutes

1 month= 43800 mins

1 month = 730 hours

There are two time attributes which are used to manage the retention of
informations in ADR.
Both attributes correspond to a number of hours after which the MMON (Memory
Monitor) background process removes the expired ADR data:

- SHORTP_POLICY : used to purge informations that have a short life.

Default is 720 which corresponds to 30 days - approximately 1 month.

- LONGP_POLICY: to purge ADR contents that have a long life.

Default is 8760 = 365 days = 1 year.

To check the current values of SHORTP_POLICY and LONGP_POLICY :

adrci> show control

To set the retention policy values :

adrci> set control (SHORTP_POLICY = 168)

To get help on the set control command :

adrci> help set control

LONGP_POLICY is used to purge information that have long life. Default value is 365
days.

This policy is used by :

ALERT
INCIDENT
SWEEP
STAGE
HM

SHORTP_POLICY is used to purge the information that have short life. Default value
is 30 days.
This policy is used by :

TRACE
CDUMP
UTSCDMP
IPS

PURGE
Purges diagnostic data in the current ADR home, according to current purging
policies. Only ADR contents that are due to be purged are purged.

Diagnostic data in the ADR has a default lifecycle. For example, information about
incidents and problems is subject to purging after one year, whereas the associated
dump files (dumps) are subject to purging after only 30 days.

Some Oracle products, such as Oracle Database, automatically purge diagnostic data
at the end of its life cycle. Other products and components require you to purge
diagnostic data manually with this command. You can also use this command to purge
data that is due to be automatically purged.

Purging Older Data

Example:
purge -age 43800 -type trace

-age mins = Purges only data older than mins minutes.

-type = ALERT|INCIDENT|TRACE|CDUMP|HM

purge -age 10080 -type incident/trace

purge -age 1440 -type incident/trace

adrci> help purge

Usage: PURGE [[-i <id1> | <id1> <id2>] |

[-age <mins> [-type ALERT|INCIDENT|TRACE|CDUMP|HM|UTSCDMP]]]:

Purpose: Purge the diagnostic data in the current ADR home. If no

option is specified, the default purging policy will be used.

Options:
[-i id1 | id1 id2]: Users can input a single incident ID, or a
range of incidents to purge.

[-age <mins>]: Users can specify the purging policy either to all
the diagnostic data or the specified type. The data older than <mins>
ago will be purged

[-type ALERT|INCIDENT|TRACE|CDUMP|HM|UTSCDMP]: Users can specify what type of

data to be purged.
Examples:
purge
purge -i 123 456
purge -age 60 -type incident

Reference metalink Doc ID 564269.1

fuser log.xml/alert.PROD.LOG
Or lsof log.xml

This command will show file is in use or not

And if it shows any process I'd then don't delete it

If it's not showing any processes then do what ever u want