Oracle Virtual Machine Images - Miscellaneous Considerations
This topic covers considerations for Oracle virtual machines on Azure, which are based on Oracle software images provided by Microsoft, with Windows Server as the operating system.
Oracle Database Virtual Machine Images
Oracle WebLogic Server Virtual Machine Images
Oracle JDK Virtual Machine Images
Azure does not currently support Oracle Database clustering. Only standalone Oracle Database instances are possible. This is because Azure currently does not support virtual disk-sharing in a read/write manner among multiple VM instances. UDP multicast is also not supported.
Azure assigns each virtual machine an internal IP address. Unless the VM is part of a virtual network, the IP address of the VM is dynamic and may change after the VM restarts. This can cause issues because the Oracle Database expects the IP address to be static. To avoid the issue, consider adding the VM to an Azure Virtual Network. See Virtual Network and Create a Virtual Network in Azure for more information.
You can place data files on either the operating system (OS) disk of the VM or on attached disks, also known as data disks. Attached disks may offer better performance and size flexibility than the OS disk. The OS disk may be preferable only for databases under 10 GB.
Attached disks rely on the Azure Blob Storage service. Each disk is capable of a theoretical maximum of approximately 500 input/output operations per second (IOPS). The performance of attached disks may not be optimal initially, and IOPS performance may improve considerably after a “burn-in” period of approximately 60-90 minutes of continuous operation. If a disk subsequently remains idle, IOPS performance may diminish until another burn-in period of continuous operation. In short, the more active a disk, the more likely it is to approach optimal IOPS performance.
Although the simplest approach is to attach a single disk to the VM and put database files on that disk, this approach is also the most limiting in terms of performance. Instead, you can often improve the effective IOPS performance if you use multiple attached disks, spread database data across them, and then use Oracle Automatic Storage Management (ASM). See Oracle Automatic Storage Overview for more information. Although it is possible to use OS-level striping of multiple disks, that approach is discouraged because it is not known to improve IOPS performance.
Consider two different approaches for attaching multiple disks based on whether you want to prioritize the performance of read operations or write operations for your database:
Oracle ASM on its own is likely to result in better write operation performance, but worse IOPS for read operations as compared to the approach using Windows Server 2012 storage pools. The following illustration logically depicts this arrangement.
Oracle ASM with Windows Server 2012 storage pools is likely to result in better read operation IOPS performance if your database primarily performs read operations, or if you value the performance of read operations over write operations. An image based on the Windows Server 2012 operating system is required. See Deploy Storage Spaces on a Stand-Alone Server for more information about storage pools. In this arrangement, two equal subsets of attached disks are first “striped” together as physical disks in two storage pool volumes, and then the volumes are added to an ASM disk group. The following illustration logically depicts this arrangement.
|Evaluate the tradeoff between write performance and read performance on a case-by-case basis. Your actual results when using these approaches may vary.|
When using Oracle Database in Azure Virtual Machines, you are responsible for implementing a high availability and disaster recovery solution to avoid any downtime. You are also responsible for backing up your own data and application.
High availability and disaster recovery for Oracle Database Enterprise Edition (without RAC) on Azure can be achieved using Oracle Active Data Guard or Oracle GoldenGate, with two databases in two separate virtual machines (VMs). Both virtual machines should be in the same cloud service and the same virtual network to ensure they can access each other over the private persistent IP address. Additionally, it is recommended to place the VMs in the same availability set to allow Azure to place them into separate fault domains and upgrade domains. Note that only VMs in the same cloud service can participate in the same availability set. Each VM must have at least 2 GB of memory and 5 GB of disk space.
With Oracle Active Data Guard, high availability can be achieved with a primary database in one VM, a secondary (standby) database in another VM, and one-way replication set up between them. With Oracle GoldenGate, you can configure bi-directional replication between the two databases. To learn how to setup a high availability solution for your databases using these tools, see Active Data Guard and GoldenGate documentation at Oracle web site.
Clustering is supported on Enterprise Edition only. If you are using Microsoft-licensed images of WebLogic Server (specifically, those with Windows Server as the operating system), you are licensed to use WebLogic clustering only when using the Enterprise Edition of WebLogic Server. Do not use clustering with WebLogic Server Standard Edition.
Connection timeouts If your application relies on connections to public endpoints of another Azure cloud service (for example, a database tier service), note that Azure may close these open connections after 4 minutes of inactivity. This may affect features and applications relying on connection pools, since connections that are inactive for more than that limit may no longer remain valid. If this affects your application, consider enabling "keep-alive" logic on your connection pools.
Note that if an endpoint is internal to your Azure cloud service deployment (such as a standalone database virtual machine within the same cloud service as your WebLogic virtual machines), then the connection is direct and does not rely on the Azure load balancer, and therefore is not subject to a connection timeout.
UDP multicast is not supported. Azure supports UDP unicasting, but neither multicasting nor broadcasting is supported. WebLogic Server is able to rely on Azure’s UDP unicast capabilities. For best results relying on UDP unicast, it is recommended that the WebLogic cluster size be kept static, or with no more than 10 managed servers included in the cluster.
WebLogic Server expects public and private ports to be the same for T3 access (for example, when using Enterprise JavaBeans). Consider a multi-tier scenario where a service layer (EJB) application is running on a WebLogic Server cluster consisting of two or more managed servers, in a cloud service named SLWLS. The client tier is in a different cloud service, running a simple Java program trying to call EJB in the service layer. Since it is necessary to load balance the service layer, a public load-balanced endpoint needs to be created for the virtual machines in the WebLogic Server cluster. If the private port you specify for that endpoint is different from the public port (for example, 7006:7008), an error such as the following will occur:
[java] javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://example.cloudapp.net:7006:
Bootstrap to: example.cloudapp.net/22.214.171.124:7006' over: 't3' got an error or timed out]
This is because for any remote T3 access, WebLogic Server expects the load balancer port and the WebLogic managed server port to be the same. In the above case, the client is accessing port 7006 (the load balancer port) and the managed server is listening on 7008 (the private port). Note that this restriction is applicable only for T3 access, not HTTP.
To avoid this issue, use one of the following workarounds:
Use the same private and public port numbers for load balanced endpoints dedicated to T3 access.
Include the following JVM parameter when starting WebLogic Server:
- Use the same private and public port numbers for load balanced endpoints dedicated to T3 access.
Dynamic clustering and load balancing limitations. Suppose you want to use a dynamic cluster in WebLogic Server and expose it through a single, public load balanced endpoint in Azure. This can be done as long as you use a fixed port number for each of the managed servers (not dynamically assigned from a range) and do not start more managed servers than there are machines the admin is tracking (that is, no more than one managed server per virtual machine). If your configuration results in more WebLogic servers being started than there are VMs (that is, where multiple WebLogic Server instances will share the same VM), then it will not be possible for more than one of those WebLogic Server instances servers to bind to a given port number – the others on that VM will fail.
On the other hand, if you configure the admin server to automatically assign unique port numbers to its managed servers, then load balancing will not be possible because Azure does not support mapping from a single public port to multiple private ports, as would be required for this configuration.
Multiple WebLogic instances on a single VM. Depending on your deployment’s requirements, you may consider the option of running multiple instances of WebLogic Server on the same virtual machine, if the VM is large enough. For example, on a Medium size VM, which contains 2 cores, you could choose to run two instances of WebLogic Server. Note however that it is still recommended that you avoid introducing single points of failure into your architecture, as would be the case if you used just one VM that is running multiple instances of WebLogic Server. Using at least two VMs could be a better approach, and each of those VMs could then run multiple WebLogic Server instances. Each of these WebLogic Server instances could still be part of the same cluster. Note, however, it is currently not possible to use Azure to load balance endpoints exposed by such WebLogic Server deployments within the same VM, as Azure load balancer requires the load balanced servers to be distributed among unique VMs.
JDK 6 latest update. While it is recommended to use the latest public supported version of Java (currently Java 7), Azure also makes a JDK 6 image available. This is intended for legacy applications that are not yet ready to be upgraded to JDK 7. While updates to JDK 6 are no longer available to the general public, given Microsoft’s partnership with Oracle, the JDK 6 image provided by Azure is intended to contain a more recent non-public update of JDK 6 that is normally offered by Oracle to only a select group of Oracle’s supported customers. New versions of the JDK 6 image will be made available over time with updated releases of JDK 6.
Note that the JDK available in this JDK 6 image, and the virtual machines and images derived from it, may only be used within Azure.
64-bit JDK. The Oracle WebLogic Server virtual machine images and the Oracle JDK virtual machine images provided by Azure contain the 64-bit versions of both Windows Server and the JDK.