ActiveGate version vs Oracle Extension version

[mn_24]

Hello,

from where we could first check which version of ActiveGate should we have in place in order to upgrade the Oracle Extension? We've found the answer on the hard way and try to avoid this in future. 

For example the last Oracle Extension version is 2.4.3 which requires ActiveGate 1.90 or later but from where we could check that as a pre-requisite to upgrade?

[rastislav_danis]

Check Deployment status / ActiveGates, in filter select Group and pick group you used for extension configuration.

[mn_24]

I saw that there is a new version for upgrade for the Oracle Extension and just did it however it required a newer ActiveGate version but I didn't know that and at the end I had to re-configure the extension...
So my question is from where to check first as a pre-requsite which ActiveGate version should I have in place in order not to have any problems with the Oracle Extension?

[rastislav_danis · Accepted solution]

If there is a requirement for extension, it should be mentioned in release notes. If there is nothing mentioned it's probably fault of developers.

[mn_24]

Since the last two versions I could see this - accept as an improvement 🙂

[rastislav_danis · Accepted solution]

You can check required version via hub page (f.e. https://www.dynatrace.com/hub/detail/oracle-database/?query=oracle&filter=all#release-notes), but you have to download extension and look into extension.yaml file (in extension.zip file).

In top of file there is a required Dyna versions info, f.e. (for Oracle DB Extension 2.4.3):

name: com.dynatrace.extension.sql-oracle
version: 2.4.3
minDynatraceVersion: 1.290.0
minEECVersion: 1.290.0

[mn_24]

Thank you! That is an option!

[mn_24]

Hi,

I'd like to continue asking in this topic here and not open a new one.

I would really appreciate to correct me with the proper terms here a little bit. In general what I am trying is to apply some kind of a best practice.

So we have two tenants - one for the ActiveGates and one for the Oracle Extension where also the database servers are added.

When it comes to updating the versions needed for a particular Extension's version we first start by checking the needed AG one from here(or from the yml file as in the last 3.3.3 version it is not clearly stated):

OK so I need 1.301.0 or higher. Fine.

And so we've begun with updating the version of the OneAgent on the database server also on the ActiveGate host.

Now my question is do we need to update the version in the other tenant where the Extension configuration is - let's call it ActiveGate app version? Must both be on equal version BEFORE proceeding with Extension update?

@TomásSeroteRoos 

[TomásSeroteRoos]

I'm a bit confused by what you are trying to do.

To run the extension from a certain tenant, you need to have ActiveGates on that tenant. If you have two tenants you need to have both the AGs and the extension running on the same tenant. And in that case, you need to have an ActiveGate with version greater or equal to 1.301.

The extension doesn't care about any OneAgents you might have on the database servers (or OneAgents on the ActiveGate servers), so those can be any version and point to any tenant.

Do note that if you are monitoring your DB servers with OneAgents and they are not pointing to the same tenant your extension is running on, you will miss out on the relationship between the OneAgent detected host and the extension created Oracle DB Instance entities.

My recommendation is to consolidate as much as possible to a single tenant, to take advantage of having all the data in the same place.

[mn_24]

It is still a bit confusing for me too but anyway 🙂

So, yes our DB servers with OneAgents are pointing to the same tenant the extension is running on. From this let's call it "client's tenant" I see the db servers and the extension.

If I try to search for the ActiveGate host I don't see it in the "client's tenant".

I only see from "Deployment Status - ActiveGates - choose one of them(in my case two) - Settings - Update button"

also

I can download the ActiveGate logs from "Deployment Status - ActiveGates - choose one of them(in my case two) - Run ActiveGate Diagnostics - Advanced options - Start analysis".

In the other tenant to which I don't have access at all, I even can not log on the actual host where the ActiveGate is installed(due to internal security reasons, a separate team is taking care for the ActiveGates and the OneAgent on them also) so there if we search in the Host menu the real ActiveGate host it is visible of course. 

So you see I am quite half blind and that is why I don't understand but want to if there is a relationship between what I am seeing and should I push the "Update" button in the "client's tenant"... 

[TomásSeroteRoos · Accepted solution]

Oh I see. So you do have your ActiveGates pointing to the client's tenant -- they show up under Deployment Status, meaning the actual ActiveGate software is set to to the client's tenant.

So you have both the DB servers and the ActiveGates in the same tenant, so you're good. You should update those AGs to version 1.301 or higher (you can do to this from the Deployment status screen) and you're good to update the extension.

The fact that these AG servers have OneAgents installed on them pointing to another tenant (and thus showing on the host screen of another tenant) has no bearing on anything. They can be any version or point to any tenant. They don't even need to have OneAgents at all!

[mn_24]

OR actually now I was told that from the above described path - this is the second option to update the AG, the first one is form the backend ...

OK, I think it is finally more clear for me at least! 🙂