Table of Contents
- Supported Browsers
-
Known Issues
-
Cannot add ingress rules to a service instance that is assigned to a subnet in
svc-vcn
- Provisioning fails with a Dedicated Deployment Autonomous Database
- Provisioning fails with an Oracle Cloud Infrastructure 1-node virtual machine DB system
- Sample application does not launch if the cluster has a custom path prefix
- Provisioning fails for a service instance on WebLogic Server 11g if the database is Oracle Cloud Infrastructure Database 12c
- Provisioning with Oracle Exadata 12c database fails if PDB name not specified
- Restrictions for using Oracle databases for an Oracle Java Cloud Service instance
- Cloning fails for service instances associated with an Oracle Autonomous Transaction Processing database or Oracle Cloud Infrastructure Database
- Oracle Java Cloud Service web console does not display unique Oracle Cloud Infrastructure Database names
- Provisioning with Oracle Cloud Infrastructure databases on bare metal fails
- Cloning might fail if the selected load balancer type is different from the source load balancer type
- The 18.3.6 Oracle Java Cloud Service API Catalog contains snapshots features unsupported in release 18.3.6
- Oracle Identity Cloud Service users cannot access the WebLogic Administration Console
-
Patching not supported for instances where products that modify
MW_HOME
are installed - Patching, backup, and restoration can fail for service instances created with Oracle WebLogic Server 11g
- Deployment to a Service Instance Based on WebLogic Server 11g Created After May 2017 Requires a Patch for WebLogic Server 11g Deployment Clients
- Limited support for managing resources using the Oracle Cloud Infrastructure Compute Classic web console
- JDK version not updated during upgrade of WebLogic Server
-
Cannot add ingress rules to a service instance that is assigned to a subnet in
- Documentation Accessibility