2.1.5 Other Changes in This Release

Please note the following changes that take effect with Oracle Exadata System Software release 26.2.0:

• Important: Oracle Linux 9 Identity Lookup

  Starting with Oracle Linux 9, the default Name Service Switch (NSS) order for user and group lookups in /etc/nsswitch.conf places SSSD before local files (sss files rather than files sss). If LDAP or another SSSD-backed directory contains a UID or GID that conflicts with a local Exadata account or group, NSS can resolve the directory identity instead of the local Exadata identity.

  Such conflicts can cause dbmsrv service accounts on Oracle Exadata database servers, including dbmsvc, dbmadmin, and dbmmonitor, to use an unexpected identity or group membership. Resulting ownership or access-control failures can prevent Exadata management services from starting or operating correctly.

  Before configuring LDAP/SSSD on a new system, or upgrading an existing system to release 26.2.0, identify UID and GID conflicts between the directory service and local dbmsrv service users and groups. For details about the local dbmsrv service users and groups, including their corresponding UIDs and GIDs, see Overview of the dbmsrv Service.

  If conflicts exist, either change the conflicting directory entries or migrate the local dbmsrv user and group IDs by using /opt/oracle.SupportTools/migrate_ids.sh. See Changing User IDs and Group IDs for dbmsrv for the supported procedure and additional considerations.

  Do not manually change /etc/nsswitch.conf as a workaround because future updates can overwrite that change. The migrate_ids.sh procedure applies only to dbmsrv service users and groups on database servers, including bare-metal servers, KVM hosts, and guests.

  Identity conflicts on Oracle Exadata storage servers are unlikely because the predefined storage server groups use reserved GIDs below 1000 and the predefined user accounts use UIDs from 1000 through 1010. If an LDAP/SSSD identity conflict is identified on a storage server, contact Oracle Support for assistance.

• Patchmgr Bundling

  The Oracle Exadata update utility (patchmgr) is optimized for and paired with the update payload. Starting with this release, patchmgr is no longer provided as a separate download. You must always use the patchmgr version included with the Oracle Exadata System Software update.

  As part of this change, you no longer need to specify the --repo and --target_version options for database server updates when using the associated ISO file as the update repository.

  See also:

  • Obtaining Patchmgr
  • Patchmgr Syntax for Database Servers