2.6.5 Oracle Database Enterprise Edition Known Bugs

These are the Oracle Database Enterprise Edition bugs in Oracle Database 18c.

• Bug 23569490
  
• Bug 23713504
  
• Bug 24291322
  
• Bug 24322363
  
• Bug 27254644
  

2.6.5.1 Bug 23569490

If you have a large number of collections and are working with clients earlier than Oracle Database 12c Release 2 (12.2), then you need a larger object cache, due to a change in snapshot size and thus a need for collection image conversion.

Workaround:

You can set the object cache size using the OBJECT_CACHE_OPTIMAL_SIZE initialization parameter. This is set to a low value by default.

Based on the number of collections and object types used in the application, the size required can be found by using this formula:

max(20K * Number of Collection Types, 5K * Object type)

2.6.5.2 Bug 23713504

The service-oriented buffer cache access optimization feature continuously monitors data block reads from disk or inter-node block transfers and performs data-dependent caching using this information. If there are no recent data block reads or transfers, then data-dependent caching does not work in the case of service relocation. This can happen if all of the blocks queried are already in the buffer cache and, therefore, no new blocks are read or transferred.

Workaround:

None.

2.6.5.3 Bug 24291322

Symbolic links are not allowed in the directory object paths or filenames when opening BFILEs. The entire directory path and filename is checked and the following error is returned if symbolic links are found:

ORA-22288: file or LOB operation FILEOPEN failed soft link in path

Workaround:

If the database directory object or filename that you are trying to open contains symbolic links, then change it to provide the real path and filename.

2.6.5.4 Bug 24322363

Software-only images are the only type of images supported with persistent home paths that are provisioned using Rapid Home Provisioning (RHP). Images created from existing working copies or homes are not supported for provisioning homes with a persistent home path.

Workaround:

Use images created from software-only installations.

2.6.5.5 Bug 27254644

During the Oracle Scheduler agent register database process (schagent -registerdatabase), you could encounter the following warning message:

"Warning: The JKS keystore uses a proprietary format. It is recommended to migrate 
to PKCS12 which is an industry standard format using..."

Workaround:

This warning message is due to a new Java runtime update. There is no change in the Oracle Scheduler agent usage of keystores (jks files). You can ignore this warning message.