If you have a large number of collections and are working with pre-12.2 clients, you need a larger object cache, due to a change in snapshot size and thus a need for collection image conversion.

Workaround:

The object cache size can be set 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)

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. The data-dependent caching does not work in the case of service relocation if there are no data block reads or transfers in the recent past. 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.

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 any symbolic link is found:

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

Workaround:

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

Software-only images are the only type of images supported with persistent home paths 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.

During the Oracle Scheduler agent register database process (schagent -registerdatabase), the following warning message might be issued:

"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.