Skip to Main Content

Core Infrastructure

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

leapp upgrade from OL7 to OL8 fails

ewesselSep 23 2024

Trying to upgrade several of our cloud instances from OL7 to OL8 using leapp, and I had mitigated the issues brought up when running leapp preupgrade --oci. After rerunning the preupgrade after the mitigation, getting the following errors and inhibitors

Risk Factor: high (error)
Title: Could not check for valid GPG keys
Summary: {"details": "No UsedTargetRepositories facts"}
Key: f61bcffa152743596cc0b18172fd42f05f042c02
----------------------------------------
Risk Factor: high (inhibitor)
Title: There are no enabled target repositories
Summary: This can happen when no custom repositories have been passed on the com
mand line.
Related links:

  • Preparing for the upgrade: https://docs.oracle.com/en/operating-systems/or
    acle-linux/8/leapp
    Remediation: [hint] Check that the --enablerepo option for leapp is set if the
    repositories are defined in any repofiles under the /etc/yum.repos.d/ directory.
    For more information on custom repository files, see the documentation. Finally
    , verify that the "/etc/leapp/files/repomap.json" file is up-to-date.
    Key: 8a43a658c16c3712bb325e5a26f22395ba360542

There were no changes to the repo files after the first preupgrade run, though I did have to remove all the osms-backup filename extensions on many of the repos. I'm not sure where it could be pulling the gpg keys from, and why it's can't get them. Any assistance would be appreciated.

Comments

MartinBach-Oracle Jan 8 2025

Hi Salomon,

please have a look at this blog post written by @ulrike-schwinn-oracle :

https://blogs.oracle.com/coretec/post/easy-sql-statement-tracking-in23c

I hope this answers your question, if not, please shout!

- Martin

Solomon Yakobson Jan 8 2025

@martinbach-oracle - No, it doesn't answer my question. Article you pointed to shows uses:

SQL> alter system set sql_history_enabled=true scope=both;

And in my post I said “Works fine when enabled on system level”. My question was about

SQL> ALTER SESSION SET SQL_HISTORY_ENABLED = TRUE;

where I showed SQL history was NOT captured even though it should be based on SQL_HISTORY_ENABLED:

Modifiable **ALTER SESSION**, ALTER SYSTEM

SY.

MartinBach-Oracle Jan 8 2025

As per the article I shared the situation is as follows at the moment

  • You must enable SQL history PDB-wide (only a DBA can do that) so there's a certain level of control over the feature
  • Your session has access to the SQL history
  • If you don't want to record anything, set sql_history_enabled to false.

I'm currently assessing if that's intended behaviour (in which case the documentation should be amended) or a feature not working as it should (in which case it needs fixing). The parameter is indeed session-modifyable, but not in the sense you expected.

We'll keep you posted.

- Martin

Solomon Yakobson Jan 8 2025

Do you mean it must be enabled on system level and not on session level and all session can do is disabe it for the session?

SY.

MartinBach-Oracle Jan 14 2025

Yes,

that's correct as of Oracle Database Free 23.6.

- Martin

Solomon Yakobson Jan 14 2025

Thanks Martin, I hope this will be added to 23AI docs soon.

SY.

1 - 6

Post Details

Added on Sep 23 2024
1 comment
567 views