Oracle Sharding Known Bugs
These are the Oracle Sharding known bugs in Oracle Database 21c.
Parent topic: Open Bugs Affecting All Platforms
Bug 33156635
When running Oracle RAC or Oracle Restart in a role-separated environment, where the Oracle RAC or Oracle Restart account is different from the Oracle Database account, performing administrative operations for sharding or for Global Data Services (GDS) can result in error GSM-45029: SQL ERROR NO MORE DATA TO READ FROM SOCKET when connected through a listener that runs in the Oracle RAC or Oracle Restart account.
Workaround:
In order to mitigate this issue, start a listener in the Oracle Database account on the sharded catalog database, and on each shard, if one is not already running. This listener can be used to connect and perform administrative operations, and can also be used when providing an Oracle Database Transparent Network Substrate (TNS) address when one is required for administrative commands, such as add shard.
Parent topic: Oracle Sharding Known Bugs