AUTOPURGE INCIDENT DEFINE UPDATE
AUTOPURGE INCIDENT DEFINE MANUAL

This policy is not immediatly rdbms]$ adrciĪDRCI: Release 12.2.0.1.0 - Production on Fri Mar 15 08:07:49 2019Ĭopyright (c) 1982, 2017, Oracle and/or its affiliates. Now with Oracle Database 12.2 and onwards, there is another size based policy. This might fill up you filesystem leading to a database outage. This is a good starting point for housekeeping, but there might be situations were a lot of large traces are written in a short amount of time. If you are unsure which files are controlled by which policy, have a look at MOS Note “ Which Files Are Part Of SHORTP_POLICY And LONGP_POLICY In ADR? (Doc ID 975448.1)“, basically traces, core dumps and IPS have a short life, all others have a long life. You can read more on setting the policies in MOS Note “ Retention Policy for ADR (Doc ID 564269.1)“. The SHORTP_POLICY defaults to 720 hours which is roughly a month whilst the LONGP_POLICY defaults to 8760 hours which is roughly a year. So we also have two retention policies for these files, the SHORTP_POLICY and the LONGP_POLICY. All the files in ADR are put in two categories, files with a short life and files with a long life. This purging is based on the age of files. With the introduction of the Automatic Diagnostic Repository (ADR) we got some automatic purging of logs and traces too, at least for the database. And check your ADR schema version after you upgraded or patched your Grid Infrastructure installation. Be aware of that and monitor your housekeeping scripts.

AUTOPURGE INCIDENT DEFINE UPDATE

Since the bug is about the behaviour after upgrading from 12.1, this might apply to other upgrade or update paths too. Give it a try.Īnd voilà, now I can purge the Grid Inftrastructure ADR home again. Sounds like I do want to do exactly this. Purpose: Upgrades the relation or schema to the latest version But let’s check what “adrci” may can do for me. Unfortunately MOS has no workaround for this. In my case this is an Oracle Database Appliance, that has been patched from 18.3 to 18.5.

So I crosschecked that.Īnd indeed, the versions are different. When I put that message in MOS, I quickly found this bug: Bug 28375106 – ADRCI Purge of Grid Home Fails With “DIA-49803: Purge not possible due to incompatible schema version” After Upgrade from 12.1 (Doc ID 28375106.8). All rights reserved.ĭIA-49803: Purge not possible due to incompatible schema version.

AUTOPURGE INCIDENT DEFINE MANUAL

That’s maybe the reason, why “purgeLogs” tries different adrci’s to purge the RDBMS homes.īut what is wrong here? Let’s try the manual ~> adrciĪDRCI: Release 18.0.0.0.0 - Production on Fri Jun 21 13:53:17 2019Ĭopyright (c) 1982, 2018, Oracle and/or its affiliates. Typically this happens, when you use an “adrci” that does not match the ADR home you are trying to purge. 00:00:06: W Not able to purge ALERT, due to error: DIA-49803: Purge not possible due to incompatible schema version. 00:00:06: I adrci GI purging diagnostic destination diag/crs/oda圆m/crs But today I found an error in the output: It was intially designed for engineered systems but it works well on classic systems too. I typically use the “purgeLogs” script from MOS Doc-ID 2081655.1. The second blog post today is about housekeeping.

Autopurge incident define