cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Upgrade of Oracle Extension

mn_24
Organizer

Hello,

we've upgraded the Oracle Extension from 3.3.3 to 3.5.0.

Because we didn't want to receive any incidents during this activity , we've created an Automatic TAG and a Maintenance Window with a timeframe of 1 hour. Unfortunately we have received a couple of (not from each database) incidents not only in Dynatrace but also transfered in ServiceNow. Could anyone clarify - why this had happened?

mn_24_0-1749651530952.png

 

mn_24_1-1749651698130.png



mn_24_2-1749651733007.png

 

5 REPLIES 5

AntonPineiro
DynaMight Guru
DynaMight Guru

Hi,

I think maintenance window scope was not defined correctly. I would review which entities were defined in maintenance window and which entities have that tag.

Best regards

❤️ Emacs ❤️ Vim ❤️ Bash ❤️ Perl

Hi Anton,

I have just added some screenshots. But I checked and I am sure that the TAG was on each oracle process group.

Hi,

And which entity has gotten problem? Has that entity that tag?

Best regards

❤️ Emacs ❤️ Vim ❤️ Bash ❤️ Perl

rastislav_danis
DynaMight Pro
DynaMight Pro

You probably got problems about Oracle instance entities, if you had enabled some metric events based on extension data. You need to tag Oracle instances with your tag as well f.e. with this rule:

rastislav_danis_0-1750836976439.png

 

Alanata a.s.

Hi,

yes, as I thought using the Process groups will work but in fact in my case when I changed the logic and used "CUSTOM_DEVICES where Custom device port equals 1521" all worked as expected.

Featured Posts