ORA-01041: internal error. hostdef extension doesn't exist. Change oracle to run in NOARCHIVEMODE

=================

Error
=================
SQL> SHUTDOWN IMMEDIATE;
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL>

=================

Issue

=================

Oracle cannot be started.

It was created in ARCHIVEMODE by mistake, with archive log dest folder missing.

Purpose: Change database to be NOARCHIVEMODE

SQL> STARTUP NOMOUNT;

SP2-0642: SQL*Plus internal error state 2133, context 3114:0:0

Unsafe to proceed

ORA-03114: not connected to ORACLE

SQL> SHUTDOWN ABORT;

ORA-24324: service handle not initialized

ORA-01041: internal error. hostdef extension doesn't exist

SQL> exit

=================

Solution
=================

Stop listener, which is preventing proper shutdown and start in NOMOUNT mode.

~> ps -ef | grep ora

oracle      1760       1  0 08:09 ?        00:00:00 /software/oracle/19c/bin/tnslsnr LISTENER -inherit

~> lsnrctl stop

~>  sqlplus / as sysdba

SQL> STARTUP NOMOUNT;

ORACLE instance started.

Total System Global Area 8589930736 bytes

Fixed Size                 13693168 bytes

Variable Size            4412407808 bytes

Database Buffers         4143972352 bytes

Redo Buffers               19857408 bytes

SQL> create pfile='/software/oracle/admin/igt/pfile/pfile.ora'

from spfile='/software/oracle/admin/igt/pfile/spfileigt.ora';

File created.

SQL> !cp /software/oracle/admin/igt/pfile/spfileigt.ora /software/oracle/admin/igt/pfile/spfileigt.ora_orig

SQL> !cp /software/oracle/admin/igt/pfile/pfile.ora /software/oracle/admin/igt/pfile/pfile.ora_orig

SQL> !vi /software/oracle/admin/igt/pfile/pfile.ora

Set log_archive_dest_1 to some valid path.

*.log_archive_dest_1='location=/some/valid/path'

SQL> CREATE SPFILE='/software/oracle/admin/igt/pfile/spfileigt.ora_new' FROM PFILE='/software/oracle/admin/igt/pfile/orig_pfile.ora';

File created.

SQL> SHUTDOWN IMMEDIATE;

ORA-01507: database not mounted

ORACLE instance shut down.

SQL> !mv /software/oracle/admin/igt/pfile/spfileigt.ora_new /software/oracle/admin/igt/pfile/spfileigt.ora

SQL>  STARTUP NOMOUNT;

ORACLE instance started.

Total System Global Area 8589930736 bytes

Fixed Size                 13693168 bytes

Variable Size            4412407808 bytes

Database Buffers         4143972352 bytes

Redo Buffers               19857408 bytes

SQL> ALTER DATABASE MOUNT;

Database altered.

SQL> ALTER DATABASE NOARCHIVELOG;

Database altered.

SQL> SHUTDOWN IMMEDIATE;

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

SQL> STARTUP;

ORACLE instance started.

Total System Global Area 8589930736 bytes

Fixed Size                 13693168 bytes

Variable Size            4412407808 bytes

Database Buffers         4143972352 bytes

Redo Buffers               19857408 bytes

Database mounted.

Database opened.

SQL> SELECT LOG_MODE FROM V$DATABASE;

LOG_MODE

---------------------

NOARCHIVELOG

SQL> exit

Toyota Aygo Tyres Specs

Toyota Aygo The Tires Spec

155/65 R14 75 T

155 - The width of your tire in millimeters from sidewall to sidewall.

65 - The tire “profile”. The aspect ratio is a percentage that indicates the tire’s height vs. its width. 65, meaning that this tire’s height is 65% of its width

A lower aspect ratio is often indicative of a sportier, more performance-oriented tire.

A higher aspect ratio tends to indicate the tire was designed for other priorities like comfort or rugged durability.

R - Next you will find a single letter, either a “D”, a “B”, or an “R” which indicates the construction type for the tire. 

“R” indicates that the tire is a Radial tire 

“D” is a Diagonal (also known as “Bias”) ply tire 

“B” means it is a Belted-Bias ply tire.

Today, tires featuring Radial construction are by far the most common type. They are made with layers of fabric cords positioned at a 90’ angle to the center line of the tread. Radials became the dominant type of construction because of their superior fuel economy, traction, ride comfort and especially tread life when compared to earlier types of construction. 

14 - Rim diameter—sometimes also noted as the wheel diameter.  This measurement is in inches.

75 - Load index. The load index symbol indicates how much weight a tire can support.

   There is a table that translates code to weight.

    For example: 75 stands for 853 lbs / 387 kg

T - Speed Rating

   There is a table that translates code to speed.

   This indicates the top speed it’s safe to travel for a sustained amount of time. 

   A tire with a higher speed rating can handle heat better and provide more control at faster speeds. 

   T - Stands for 118 mph (189 kmh)

DBMS_SCHEDULER by example

==============================

Examples of using DBMS_SCHEDULER

==============================

Create Job

BEGIN 

 DBMS_SCHEDULER.CREATE_JOB ( 

  job_name => 'REFRESH_GSM_ROAMING_INFO_MV', 

  job_type => 'PLSQL_BLOCK', 

 job_action => 'BEGIN DBMS_MVIEW.REFRESH(''GSM_ROAMING_INFO_MV''); END;', 

 start_date => SYSDATE+1/1440, 

 repeat_interval => 'FREQ=HOURLY;INTERVAL=4', -- Run every 4 hours 

 enabled => TRUE, 

 comments => 'Refresh materialized view GSM_ROAMING_INFO_MV every 4 hours' ); 

END; 

/

Update Property

--Update job_action

BEGIN

    DBMS_SCHEDULER.SET_ATTRIBUTE(

        name      => 'MV_RF$J_0_S_326',

        attribute => 'job_action',

        value     => 'DBMS_REFRESH.REFRESH(''GSM_ROAMING_INFO_MV'');'

    );

END;

/

--Update repeat_interval

BEGIN

    DBMS_SCHEDULER.SET_ATTRIBUTE(

        name      => 'REFRESH_GSM_ROAMING_INFO_MV',

        attribute => 'repeat_interval',

        value     => 'FREQ=MINUTELY;INTERVAL=5'

    );

END;

/

Drop Job

DECLARE 

  CURSOR job_remove_cur IS

  SELECT job_name FROM USER_SCHEDULER_JOBS

   WHERE UPPER(job_action) LIKE '%GSM_ROAMING_INFO_MV%';

BEGIN

  FOR job_remove_rec IN job_remove_cur LOOP

    dbms_scheduler.drop_job(job_name => job_remove_rec.job_name);

    COMMIT;

  END LOOP;

END;

/

Monitor Job

SELECT job_action, 

       last_start_date,

       next_run_date, 

       failure_count, 

       run_count 

  FROM USER_SCHEDULER_JOBS 

 WHERE job_name = 'REFRESH_GSM_ROAMING_INFO_MV';

See difference in Oracle Profiles

==================

See current status

==================

COL default_profile FOR A10

COL app_prof_profile FOR A10

COL resource_name FOR A30

COL default_limit FOR A20

COL app_prof_limit FOR A40

set LINESIZE 160

SELECT DBA_PROFILES_DEFAULT.profile default_profile, 

       DBA_PROFILES_APP_PROF.profile app_prof_profile, 

       DBA_PROFILES_DEFAULT.resource_name resource_name,

       DBA_PROFILES_DEFAULT.limit default_limit, 

       DBA_PROFILES_APP_PROF.limit app_prof_limit

  FROM DBA_PROFILES DBA_PROFILES_DEFAULT,

       DBA_PROFILES DBA_PROFILES_APP_PROF

 WHERE DBA_PROFILES_DEFAULT.profile='DEFAULT'

   AND DBA_PROFILES_APP_PROF.profile='APP_PROF'

   AND DBA_PROFILES_DEFAULT.resource_name = DBA_PROFILES_APP_PROF.resource_name

   AND DBA_PROFILES_DEFAULT.limit <> DBA_PROFILES_APP_PROF.limit

ORDER BY 3,1,2;

DEFAULT_PR APP_PROF_P RESOURCE_NAME            DEFAULT_LIMI APP_PROF_LIMIT

---------- ---------- ------------------------ ------------ ---------------------------

DEFAULT    APP_PROF   IDLE_TIME                UNLIMITED    480

DEFAULT    APP_PROF   PASSWORD_LOCK_TIME       1            UNLIMITED

DEFAULT    APP_PROF   PASSWORD_ROLLOVER_TIME   0            DEFAULT

DEFAULT    APP_PROF   PASSWORD_VERIFY_FUNCTION NULL         ORA12C_STIG_VERIFY_FUNCTION

==================

Change settings:

==================

ALTER PROFILE APP_PROF LIMIT IDLE_TIME UNLIMITED;

ALTER PROFILE APP_PROF LIMIT PASSWORD_VERIFY_FUNCTION NULL;

Details:

PASSWORD_ROLLOVER_TIME - DEFAULT - Is same as zero

PASSWORD_LOCK_TIME - When user becomes unlocked, after the specified number of consecutive failed login attempts

==================

Theory

==================

Password-Specific Settings in the Default Profile

Parameter: INACTIVE_ACCOUNT_TIME 

Default Setting Description: UNLIMITED

Description: Locks the account of a database user who has not logged in to the database instance in a specified number of days.

Parameter: FAILED_LOGIN_ATTEMPTS

Default Setting Description: 10

Description: Sets the maximum times a user try to log in and to fail before locking the account.

Note: You can set limits on the number of times an unauthorized user (possibly an intruder) attempts to log in to Oracle Call Interface (OCI) applications by using the SEC_MAX_FAILED_LOGIN_ATTEMPTS initialization parameter.

Parameter: PASSWORD_GRACE_TIME

Default Setting Description: 7

Description: Sets the number of days that a user has to change their password before it expires.

Parameter: PASSWORD_LIFE_TIME

Default Setting Description: 180

Description: Sets the number of days the user can use their current password.

Parameter: PASSWORD_LOCK_TIME

Default Setting Description: 1

Description: Sets the number of days an account will be locked after the specified number of consecutive failed login attempts.

After the time passes, then the account becomes unlocked. 

This user's profile parameter is useful to help prevent brute force attacks on user passwords but not to increase the maintenance burden on administrators.

Even after the value set by PASSWORD_LOCK_TIME shows that the password has expired, the DBA_USERS data dictionary view will show that the account is locked. 

However, after the user connects, the information in DBA_USERS is updated with the correct OPEN status.

Parameter: PASSWORD_REUSE_MAX

Default Setting Description: UNLIMITED

Description: Sets the number of password changes required before the current password can be reused.

Parameter: PASSWORD_REUSE_TIME

Default Setting Description: UNLIMITED

Description: Sets the number of days before which a password cannot be reused.

Parameter: PASSWORD_ROLLOVER_TIME

Default Setting Description: 0

Description: Enables the gradual database password rollover time.

Unable to obtain current patch information, Latest xml inventory is not loaded into table, RawInventory gets null OracleHomeInfo

==================

Error

==================

Unable to obtain current patch information due to error: 20001, ORA-20001: Latest xml inventory is not loaded into table

ORA-06512: at "SYS.DBMS_QOPATCH", line 2327

ORA-06512: at "SYS.DBMS_QOPATCH", line 854

ORA-06512: at "SYS.DBMS_QOPATCH", line 937

ORA-06510: PL/SQL: unhandled user-defined exception

ORA-06512: at "SYS.DBMS_QOPATCH", line 932

ORA-29913: error in executing ODCIEXTTABLEFETCH callout

ORA-29400: data cartridge error

KUP-04095: preprocessor command /software/oracle/19c/QOpatch/qopiprep.bat encountered error "LsInventorySession failed: RawInventory gets null OracleHomeInfo

"

ORA-06512: at "SYS.DBMS_QOPATCH", line 919

ORA-06512: at "SYS.DBMS_QOPATCH", line 2286

ORA-06512: at "SYS.DBMS_QOPATCH", line 817

ORA-06512: at "SYS.DBMS_QOPATCH", line 2309

==================

Debug

==================

oracle@hostname:/software/oracle/19c/OPatch>%./opatch lsinventory

Oracle Interim Patch Installer version 12.2.0.1.41

Copyright (c) 2025, Oracle Corporation.  All rights reserved.

Oracle Home       : /software/oracle/19c

Central Inventory : /software/oracle/oraInventory

   from           : /software/oracle/19c/oraInst.loc

OPatch version    : 12.2.0.1.41

OUI version       : 12.2.0.7.0

Log file location : /software/oracle/19c/cfgtoollogs/opatch/opatch2025-05-25_08-12-01AM_1.log

List of Homes on this system:

  Home name= OraDB19Home1, Location= "/software/oracle/1910"

LsInventorySession failed: RawInventory gets null OracleHomeInfo

OPatch failed with error code 73

oracle@hostname:/software/oracle/19c/OPatch>%

==================

Fix

==================

Edit OraDB19Home1 to correct value /software/oracle/19c

vi /software/oracle/oraInventory/ContentsXML/inventory.xml

<HOME_LIST>

<HOME NAME="OraDB19Home1" LOC="/software/oracle/1910" TYPE="O" IDX="1"/>

</HOME_LIST>

<HOME_LIST>

<HOME NAME="OraDB19Home1" LOC="/software/oracle/19c" TYPE="O" IDX="1"/>

</HOME_LIST>

Oracle CVE by example

=============

Oracle CVE

=============

Oracle release CVE every 3 months

Start here

https://www.oracle.com/security-alerts/cpuoct2024.html#AppendixDB

Search for "Database"

For example:

Critical Patch Update (CPU) Program Oct 2024 Patch Availability Document (DB-only) (Doc ID 3036945.1)

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=278792132325204&id=3036945.1&_afrWindowMode=0&_adf.ctrl-state=emdrze40q_72

Search for the Oracle product + version + host and go to the patch page

This is patch page

https://support.oracle.com/epmos/faces/PatchSearchResults?_adf.ctrl-state=emdrze40q_121&_afrLoop=279344146946796

DATABASE RELEASE UPDATE 19.25.0.0.0 (Patch) for Linux x86-64

To download the patch, follow the URL from the patch page

Patch 36912597: DATABASE RELEASE UPDATE 19.25.0.0.0

Oracle ISV options

=====================

What is an Oracle ISV

=====================

Useful Abbreviations
ISV - Oracle Independent Software Vendor

ASFU - Oracle Application Specific Full Use

ESL - Oracle Embedded Software License

=====================

What is ISV

=====================

ISVs are third-party organizations that develop, market, and sell software applications that run on Oracle platforms.
Standard license models for ISVs are ASFU, ESL, Proprietary Application Hosting License

=====================
License models 

=====================
AFSU

The Oracle ASFU license is a comprehensive licensing model tailored for ISVs who wish to bundle Oracle technology with their proprietary applications for distribution to their end-users.
Key Characteristics:
- Bundling and Distribution: 
    Allows ISVs to include Oracle technology within their application packages, offering a unified solution to end-users.
- End-User Restrictions: 
    While end-users can fully utilize the Oracle technology as part of the ISV application, they are prohibited from leveraging it for any purposes beyond the scope of the ISV application itself.
- Versatility: 
    Suitable for ISVs looking to enhance their applications with Oracle’s advanced technology features while maintaining control over the application’s distribution and usage.

ESL

The Oracle ESL offers a more integrated approach for ISVs, permitting the embedding of Oracle software directly into their applications.
Under this model, Oracle software becomes a fundamental component of the ISV application, effectively making the Oracle software and the ISV application a single, indistinguishable product.

Key Characteristics:
- Deep Integration: 
  Oracle software is deeply integrated and indistinguishable from the ISV application, providing a seamless experience to the end-user.
- Inseparability: 
  The embedded Oracle software cannot be separated from the ISV application or used independently, ensuring that the value of the Oracle technology directly supports the ISV application’s functionality.
- Targeted Usage: 
  Ideal for ISVs whose applications require the robust functionality of Oracle technology to operate but wish to keep the Oracle components invisible to the end-user.
  
Proprietary Application Hosting License
While not as commonly referenced as ASFU or ESL, the Proprietary Application Hosting License is another important option for ISVs, particularly those offering Software as a Service (SaaS) or hosting their applications on behalf of their customers.
This license supports ISVs in leveraging Oracle technologies to host and manage their applications on Oracle platforms, providing a scalable and secure environment for application deployment.