Latest Product Updates

Here’s an overview of new product deployment options for Oracle Analytics Server on Oracle Cloud Infrastructure using Oracle Cloud Marketplace.

April 2025

Update Description
Oracle Autonomous Transaction Processing

Use Oracle Autonomous Transaction Processing (ATP) 19+ to host schemas for Oracle Analytics Server 2025 and Oracle Analytics Server 2024.

March 2025

Update Description
Oracle Analytics Server 2025

Use Oracle Cloud Marketplace to quickly deploy Oracle Analytics Server 2025 on Oracle Cloud Infrastructure.

March 2024

Update Description
Oracle Analytics Server 2024

Use Oracle Cloud Marketplace to quickly deploy Oracle Analytics Server 2024 on Oracle Cloud Infrastructure.

June 2023

Update Description
Oracle Roving Edge Infrastructure

Oracle's Roving Edge Infrastructure enables you to deploy cloud workloads outside the data center where data is generated and consumed, regardless of network connectivity.

Use Oracle Cloud Marketplace to quickly deploy Oracle Analytics Server 2023 on Oracle Roving Edge Infrastructure. Export Oracle Analytics Server 2023 workloads from Oracle Cloud Marketplace to your Oracle Roving Edge Devices (RED).

See Oracle Analytics Server Image for Roving Edge Infrastructure - BYOL.

July 2022

Update Description
Subnet compartment

The Virtual Cloud Network (VCN) and subnet where you deploy the compute instance for Oracle Analytics Server can now be located in different compartments.

In the Network Configuration section, there's a new option Subnet Compartment so you can select the compartment containing your subnet. See Deploy Oracle Analytics Server Using Oracle Cloud Marketplace.

April 2022

Update Description
Folder structure
The folder structure for files deployed during Oracle Analytics Server installation and domain configuration has changed. Here is the updated folder structure and the location of some key files:

  • /u01/app: Oracle Analytics Server product and binaries, including files such as config.sh, oraInst.loc.

  • /u01/app/oas-scripts: Oracle Analytics Server scripts such as biconfigcleaner.sh, createDataPartition.sh, create_oas_domain.sh, DefaultSingleNodeOASFirewallPorts.xml, generate_biconfig.sh oas_installer.sh, open_oas_firewall_ports.sh, oas_install.finish.

  • /u01/data: Oracle Analytics Server domain directories and files such as biconfig.rsp.

    This partition also includes all the requested boot volume space beyond what is needed for the core Oracle Analytics Server binaries.

  • /u01/data/domains/bi/bitools/bin: Oracle Analytics Server domain tools such as status.sh, start.sh, and other scripts.

  • /var/log: Oracle Analytics Server logs such as oas_cloudinit.log, oas_create_domain.log.

Previously these files were deployed under folders named /tmp and /oas/oas_install.

Log file changes

Deployment log files are now available under the /var/log folder (previously under /tmp). The names of the log files have changed too.

  • oas_cloudinit.log (previous name oas_install.log)

  • oas_create_domain.log ( previous name create_domain.log)

Only the required firewall ports open by default

When you use Oracle Cloud Marketplace to deploy Oracle Analytics Server and create the domain, only ports required for a single-node install are open by default. Post deployment, you can use the script open_oas_firewall_ports.sh to open other ports and change the default port values to suit your environment. For details, see Manage Firewall Ports for Oracle Analytics Server on Oracle Cloud.

If you create the domain manually using config.sh, you can use the same script (open_oas_firewall_ports.sh) to modify your firewall port configuration.

If you scale-out your Oracle Analytics Server environment, you must open some additional ports. For details, see Scaled-out, Multi-node Environment - Additional Required Ports.

Built-in user for administrative tasks (oracle)

When you use Oracle Cloud Marketplace to deploy Oracle Analytics Server and create the domain, the Oracle Analytics Server compute instance and the domain is created and owned by the oracle user.

After connecting to your Oracle Analytics Server compute instance as the opc user, you must switch to the oracle user to complete administrative tasks. For example, you must use the built-in oracle user to access Oracle Analytics Server logs, manage firewall ports, scale out, create a domain manually, and so on. See Manage the Compute Instance for Oracle Analytics Server Using the Built-in oracle User.