Known Issues and Bugs for Standard Edition High Availability

This section contains information about issues related to Standard Edition High Availability:

• Bug 30821297
  
• Bug 30979062
  
• Bug 30992915
  
• Bug 31114977
  
• Bug 31128434
  
• Bug 31128452
  
• Bug 31146826
  
• Bug 31156506
  
• Bug 31188168
  
• Bug 31264160
  

Bug 30821297

Oracle Database Standard Edition 2 allows you to create more than one pluggable database (PDB) in a multitenant container database (CDB). However, when you use the Oracle Database Configuration Assistant (Oracle DBCA) to create a second PDB, you receive the following error:

[FATAL] [DBT-11506] Creation of more than one PDB requires Enterprise Edition license.

Workaround:

Create the additional PDB using the SQL statement CREATE PLUGGABLE DATABASE.

Bug 30979062

When you use the srvctl relocate database command to initiate the relocation of a database configured with Standard Edition High Availability, and if the destination-configured node does not have an available Oracle Database home, then the relocation fails as expected but with error messages that do not include the reason for the failure.

This issue will be fixed in a future Oracle Database 19c release update.

Workaround:

None.

Bug 30992915

When you use Oracle Database Configuration Assistant (Oracle DBCA) to create a single-instance database on an Oracle Clusterware node, the database is registered with Oracle Clusterware. However, the command output incorrectly says the following:

Registering database with Oracle Restart

Workaround:

None.

Bug 31114977

When you relocate Oracle Database configured with Standard Edition High Availability that has active database services, the srvctl status service command on that database displays a blank list of instance that has the services running. However, the services are running on the database instance.

Workaround:

None.

Bug 31128434

When you use the srvctl relocate database command to initiate the relocation of a database configured with Standard Edition High Availability, and if Oracle Database has a service registered, then the shutdown of the database instance is suspended for a period of time due to the mount lock being held.

The registered database services are not accessible when the database instance is suspended and the Oracle Database instance stops eventually on the current node and starts on the destination node.

Workaround:

  Use a sequence of srvctl stop database commands followed by the srvctl start database -node destination node commands to avoid shutdown suspension.  

Bug 31128452

When you run the srvctl config service command for an Oracle Database with Standard Edition High Availability configured and its services registered,  a Java NULL pointer exception occurs at the end of the output for the first service.

This issue will be fixed in a future Oracle Database 19c release update.

Workaround:

None.

Bug 31146826

When you configure Standard Edition High Availability for a single-instance Oracle Database 19c Release Update (RU) 19.7 that does not have any database services registered, you will observe a local restart when the instance is abnormally terminated. However, after a service is added to the database, you do not observe the local restart. Instead, the database fails over immediately when it is abnormally terminated.

This issue will be fixed in a future Oracle Database 19c release update.

Workaround:

None.

Bug 31156506

If Oracle base of the Oracle Database home is the same as Oracle base of the Oracle Grid Infrastructure home, then if the user adds a new node to the cluster, the Oracle Database home user loses access permissions to some of the subdirectories under Oraclebase of the Oracle Database home.

Workaround:

Use distinct directories as Oracle base for the Oracle Grid Infrastructure and Oracle Database installations.

Bug 31188168

When you use the srvctl relocate database -help command from a Standard Edition single-instance Oracle Database 19c home, the prompt incorrectly displays usage and help messages with the mention of Oracle Real Application Clusters One Node (Oracle RAC One Node). Starting with Oracle Database 19c Release Update (RU) 19.7, this command applies to Standard Edition High Availability and must contain the corresponding usage and help messages.

This issue will be fixed in a future Oracle Databse 19c release update.

Workaround:

Bug 31264160

Starting with Oracle Database 19c Release Update (RU) 19.7, you use the srvctl add or modify database commands to configure Standard Edition High Availability by specifying the -node option with a node list of more than one node. However, the usage messages from these commands, such as when running from an Oracle Database Standard Edition 2 database home with the -help option, do not show this usage.

This issue will be fixed in a future Oracle Database 19c release update.

Workaround: