Skip to Main Content

Oracle Database Discussions

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.

What is the solution/protocol to bypass installer issues (INS-*****) in a development environment?

user2660061May 7 2024 — edited May 7 2024

Hello all.

I am trying to install 19c x86-64 on RHEL 9 in a development environment, but am facing issues while running the Installer with a few INS errors. Here is what I have done so far:

Ran the pre-installer (oracle-database-preinstall-19c-1.0-1.el9.x86_64.rpm)

Downloaded the zip to a path inside /u01 (can't do rpm because VM was configured to install on /u01 partition)

As the oracle user, extracted the zip to /dbhome_1

Updated the CV file from OEL5 to OEL7.8 (INS-08101)

Ran the install as ./run installer -ignoreInternalDriverError to bypass INS-30060 Check for group existence failed.

Unfortunately now it is failing again with the error "Error in invoking target ‘libasm***’ of makefile ‘/u01/app/oracle/product/19.0.0/db home_1/rdbms/lib/ins_rdbms.mk’.

Could this be that I need to apply a relevant patch? This is a development environment, and I do not have the support credentials to see which patch or to download it. Please advise, and thank you for reading through this post.

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 May 7 2024
1 comment
456 views