1. Connecting Oracle Analytics Cloud to Your Data
  2. Reference
  3. Troubleshoot
  4. Troubleshoot Private Access Channel Connectivity Issues

Troubleshoot Private Access Channel Connectivity Issues

This topic describes common problems that you might encounter and explains how to solve them.

Troubleshoot connectivity to an on-premises Oracle Database

Complete the following configuration in your on-premises for single node Oracle Database environment:
  1. On the firewall, open the Oracle Database port e.g. 1521.
  2. Set up a direct connection between your on-premises network and Oracle Cloud Infrastructure VCN.
  3. Create a private DNS view, and then add a zone (in the view) for your custom domain. For example, ocivcn.companyabc.com.

Create a temporary Compute instance in the PAC subnet and then verify that you can resolve the on-premises database hostname and port, and ping the private IP address.

Hostname resolution check command:

$ nslookup <On-premises database hostname>

If you can’t resolve the on-premises single node Oracle database hostname, it means the DNS servers configured in the subnet DHCP option can't resolve the hostname or the DNS zone configuration is invalid.

Connection check command:

nc -zv <On-premises database hostname> <port>

For example: nc -zv onprem.db.xyz.com 1521.

Note: If the nc package isn’t available, use yum install nc*.

If you can’t establish a connection, check VPN or FastConnect network connectivity between Oracle Cloud Infrastructure VCN and on-premises network.

Troubleshoot connectivity to an on-premises Oracle Essbase data source

Complete the following configuration in your on-premises Essbase environment:
  1. On the firewall, open Essbase port ranges 32768-33768 and 1423.

    Check your essbase.cfg file for any valid ports that Essbase is currently using.

    Note: If you are using Palo Alto Networks firewall, don’t create a rule on App-ID that is, oracle-essbase. Instead, create a firewall rule that includes the Essbase port ranges.

  2. Set up a direct connection between your on-premises network and Oracle Cloud Infrastructure VCN.
  3. Create a private DNS view, and then add a zone (in the view) for your custom domain. For example, ocivcn.companyabc.com.

Hostname resolution check command:

$ nslookup <On-premises Essbase hostname>

If you can’t resolve the on-premises Essbase hostname, it means the DNS servers configured in the subnet DHCP option isn’t able to resolve the hostname or the DNS zone configuration is invalid.

Connection check command:

nc -zv <On-premises Essbase hostname> <essbase port>

For example:

nc -zv onprem.essbase.xyz.com 1423

nc -zv onprem.essbase.xyz.com 33767

Note: If the nc package isn’t available, use yum install nc*.

If you can’t establish socket connection, check the following:

- VPN or FastConnect network connectivity between your Oracle Cloud Infrastructure VCN and on-premises network.

- Firewall rule exists for the entire Essbase port range 32768-33768.

Troubleshoot the maximum amount of query execution time in Planning and Budgeting Cloud Service

Oracle's Planning and Budgeting Cloud Service is one such cloud-based technology that provides businesses with an integrated solution for budgeting, forecasting, and planning. To ensure stability, it is crucial to set query execution time (QRYGOVEXECTIME) in Planning and Budgeting Cloud Service (Essbase). In this section, we will discuss the importance of setting QRYGOVEXECTIME.

What is QRYGOVEXECTIME?

QRYGOVEXECTIME is a parameter that controls the maximum amount of time that a query can run in Essbase.

Why is QRYGOVEXECTIME important?

QRYGOVEXECTIME is essential in Planning and Budgeting Cloud Service because it helps ensure the stability of both Oracle Analytics Cloud and Planning and Budgeting Cloud Service. Here are a few reasons why:

  • Prevents long-running queries: Long-running queries can cause system instability, leading to performance issues and even system crashes. By setting QRYGOVEXECTIME (in PBCS), businesses can prevent long-running queries from executing, which can help ensure system stability.
  • Limits resource consumption: Queries that run for an extended period can consume significant system resources, leading to performance degradation. By setting QRYGOVEXECTIME, businesses can limit resource consumption by preventing queries from running indefinitely.
  • Improves user experience: When users run a query that takes a long time to complete, it can lead to frustration and dissatisfaction. By limiting the maximum query execution time, businesses can improve the user experience by ensuring that queries run in a timely manner.

In conclusion, setting QRYGOVEXECTIME in PBCS / Essbase is an important step in safeguarding the stability of both Oracle Analytics Cloud and Essbase. By limiting query execution times, you can prevent resource contention, improve system stability, and improve overall performance. So, take the time to adjust this parameter to an appropriate value for your environment.

To implement this query execution time limits raise an SR with Oracle Support for Oracle Planning and Budgeting Cloud.