My Oracle Support Banner

Bug Found In Cleandblogs.pl In Dbaas Tooling On Exacc Gen1 (Doc ID 2831285.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Information in this document applies to any platform.

Symptoms

On : NA version, Patching and Tool Issues (DomU)

Bug found in cleandblogs.pl in dbaas tooling on exacc gen1

the cleandblogs.pl script is looping through each home in ADR Base and purging logs, but it does the same thing for each DB on the server, who all have the same ADR Base (/acfs_diag/diag).

# rpm -qa | grep dbaas
dbaastools_exa-1.0-1+19.1.1.1.0_210521.0729.x86_64

Core function gets a list of DB's, and for each DB call the PurgeADRLogFiles function for that DB:
  if (defined $dbref) {
  foreach my $db(keys %{$dbref}) {
  $log->logprt("\nLog file for db $db is " . $logf . "\n");
  PurgeADRLogFiles($db);
  }

The function then finds the ADRbase (which is /acfs_diag/diag, used by all databases on the server). It then proceeds to list ALL homes under the base, and purge them.

  #
  # locate adrci homes and cycle through them
  #
  my @homes = (`${ADRCI} exec="set base ${ADRbase};show homes"|grep -v :|grep -v slc01qnv`);
  foreach my $adrci_home (@homes) {
  chomp $adrci_home;

So in effect, you run the function for each database, cleaning all ADR homes each time. On a server with 30 databases, that means cleaning all ADR homes 30 times...rather than cleaning the homes related to the $db. Perhaps you only want to run once for ALL DB's or only ADR homes related to the DB?

On my sandpit I have 3 databases, an 11.2, 12.1 and an 18. Therefore, cleandblogs ran the below for each db...
Log file for db cdbas5 is /var/opt/oracle/log/cleandblogs/cleandblogs_2021-05-28_10:47:02.150869318862.log
2021-05-28 10:47:10.292147 - Diagnostic destination is diag/rdbms/cdbas6_dcb/cdbas61.
2021-05-28 10:47:23.799606 - Diagnostic destination is diag/rdbms/cdbas6_dcb/cdbas62.
2021-05-28 10:47:44.150594 - Diagnostic destination is diag/rdbms/cdbas5_dcb/cdbas51.
2021-05-28 10:47:48.144623 - Diagnostic destination is diag/rdbms/cdbas5_dcb/cdbas52.
2021-05-28 10:47:51.795098 - Diagnostic destination is diag/rdbms/dbas4_dcb/dbas41.
2021-05-28 10:48:16.519562 - Diagnostic destination is diag/rdbms/dbas4_dcb/dbas42.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.