pat98's always & forever

공식적인 방법은 아니니 에디션별 기능 등을 quick 하게 테스트 해야 할 경우 해 볼수 있겠다.

- Enterprise -> Standard 로 변경. shutdown 후 relink

cd $ORACLE_HOME/rdbms/lib

make -f ins_rdbms.mk edition_standard ioracle

Connected to:

Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production

Version 19.3.0.0.0

select * from v$option where parameter='Partitioning';

PARAMETER            VALUE          CON_ID

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

Partitioning         FALSE                0

- Standard -> Enterprise 로 변경. shutdown 후 relink

cd $ORACLE_HOME/rdbms/lib

make -f ins_rdbms.mk edition_enterprise ioracle

Connected to:

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Version 19.3.0.0.0

PARAMETER            VALUE          CON_ID

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

Partitioning         TRUE                0

- 현재  ins_rdbms.mk 화일에 code 되어 있는 내용은 아래와 같음

grep -i edi /oracle/app/oracle/product/19.0.0/rdbms/lib/ins_rdbms.mk

edition_corestandard:

        $(SILENT)$(ECHO) "Deploying Oracle Database Core Standard Edition"

edition_coreenterprise:

        $(SILENT)$(ECHO) "Deploying Oracle Database Core Enterprise Edition"

edition_standard:

        $(SILENT)$(ECHO) "Deploying Oracle Database Standard Edition"

edition_enterprise:

        $(SILENT)$(ECHO) "Deploying Oracle Database Enterprise Edition"

edition_highperf:

        $(SILENT)$(ECHO) "Deploying Oracle Database Enterprise Edition High Performance"

edition_extremeperf:

        $(SILENT)$(ECHO) "Deploying Oracle Database Enterprise Edition Extreme Performance"

edition_express:

        $(SILENT)$(ECHO) "Deploying Oracle Database Express Edition"

시력을 잃어 가는 남자

청력을 잃어 말하지 못하는 여자

소설의 줄거리는 중요하지 않다. 두 사람이 만나는 이야기 이지만 사랑이라 부를수 있을까?

때로는 침묵이 더 효과적인 언어수단이며 고요한 적막이 우리에게 커다란 울림을 느끼게 한다. 

Exadata 이미지 업그레이드 작업 버그 하나 (22.1.17, 23.1.8)

Issue: During OS Image Upgrade, node gets into boot loop

Impacted releases: Direct upgrade from 21.2.10 or earlier to 22.1.17 / 22.1.18 / 22.1.19 / 23.1.8 /23.1.9 / 23.1.10

Root Cause :
There is a known bug in kernel-ueknano-4.14.35-2047.511.5.5.3.el7uek.x86_64 Kernel due to which FW update of Whitney+ card crashes Kernel.
Above Kernel is included in Nov-2023 releases (22.1.17, 23.1.8).
Bug 35844212/35848949 - bnxtnvm failed to update/downgrade whitneyplus firmware
Fix for above bug is included in uptrack-update that is also included in Nov-2023 releases.
While upgrading compute during firstboot, it comes up with new Kernel and FW updates are applied.
There is no issue if FW upgrade activity starts after botting up with new Kernel and uptrack update is effective.
Due to timing issues, if FW upgrade starts after booting up with new Kernel and before uptrack-update is effective, then kernel crashes and node gets rebooted.
During boot up time (firstboot), FW upgrade kicks in again causes Kernel to crash. This is happening in a loop forever.

Workaround:
• Disable FW updates during impacted upgrade path ( touch /opt/oracle.cellos/DISABLE_HARDWARE_FIRMWARE_CHECKS)
• Post upgrades, install FW upgrades
o rm /opt/oracle.cellos/DISABLE_HARDWARE_FIRMWARE_CHECKS
o /opt/oracle.cellos/CheckHWnFWProfile -action updatefw -mode exact
Next steps:
Kernel with fix is included in Feb-2024 releases (22.1.20, 23.1.11).