nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Warning after OAC Nov 2023 update -Repository contains data created by newer AdminTool Version

Jahnavi-Oracle

Hi,

I am getting the below warning after the OAC Nov 2023 update when I am trying to save the rpd.

"Repository contains data created by newer AdminTool Version."

I have tried to install the latest admin tool but still the warning persists.

Please advise if you have seen the same warning or were able to do something about it.

Find more posts tagged with

Analysis and Data Visualization

Accepted answers

All comments

Madasamy -Oracle

I tried with the Sep 2023 release admin tool with Sep 2023 and i dont see any issues, i think it maybe specific to Nov 2023.

Is the use-case such that you are using "Open in the cloud " to connect to OAC nov 2023 and try to save the RPD local and that causes the warning? and whats the admintool version you are using?

And do you have any consent button in the warning like "OK " or something and that let you save the RPD to local. Please clarify more!

Jahnavi-Oracle

Hi @Madasamy - Oracle-Oracle

The use case is same as you have suggested. I am using the below version

So when I open the rpd in cloud mode and then try to save it in local it gives the below warning. And I do have the option to click 'Yes' and continue but wasn't sure if that is recommended or not.

User448972-OC

Hi @Madasamy - Oracle-Oracle

My team is running into the same issue and we are using the following version from May 2023

OAC admin tool

Version 12.3.8.0.0

Package: 230512.1902.000

Repository Version: 356

MUD version: 11

I found that not all of my non-prod instances in our cloud tenancy were updated and can confirm I only get this warning on the OAC November 2023.

Major concern is deploying repository from November 2023 into production instance still on September 2023.

Also can someone confirm the September 2023 admin tool version? When downloading and installing the September 2023 client details are as follows

Version 12.2.4.0.0

Package: 230917.1954.000

Repository version: 356

MUD version: 11

Is this correct for the September 2023 version? Even with this version I still got this warning on November 2023 and it also seems strange because I have never seen the admin tool version go down like this.

Madasamy -Oracle

hello,

we tested this internally and we are able to see the behavior internally as well with the nov 2023 server and sep 2023 clients.

we are able to download rpd and use the rpd after consenting to the earning without any issues , same goes with upload rpd.

regarding the reasoning and impact of the warning, we may need bit more time to come back on, as it's been discussed internally

Jahnavi-Oracle

Hi @Madasamy - Oracle-Oracle ,

When I installed the Sep 2023 version admin tool it gave the below version same as you have mentioned.

Version 12.2.4.0.0

And even with the Sep 2023 Admin tool we get the same warning.

Good to know that the consent to warning does not raise any issue. But do let me know if any issues.

Thank you.

Madasamy -Oracle

Yes @Jahnavi-Oracle

We are working internally to fix this on a newer version of the client tools. But I do not have an ETA that could be shared. You may raise an SR if you'd like to know more updates.

Thanks,

Steve F-2

To add a few more details:

The metadata feature check and message is part of a legacy feature. It is rare for new metadata flags to be introduced. There is no backward compatibility impact with this new metadata feature flag introduced in the November 2023 release. So you can click 'Yes' to proceed to ignore this message.

Teams are looking to improve the messaging.

Jahnavi-Oracle

Thanks @SteveF-Oracle . I am doing the same now after the same confirmation from the SR.

Debadrita Ghosh-Oracle

Hi @User448972-OC,

Did you get any reason or resolution for your issue, wherein the Prod and some of the non-prod instances were still on the September 2023 release? I'm facing the same issue and the snapshot migration form Nov 2023 to Sep 2023 instance is failing due to this. I haven't received any response from Support yet.

Thanks

Debadrita Ghosh