Oracle BI Applications On Platform As A Service PaaS - Best Practices
Oracle BI Applications On Platform As A Service PaaS - Best Practices
Best Practices
ORACL E WHIT E PAPER | AUGUST 2 0 2 2
Disclaimer
The following is intended to outline our general product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code,
or functionality, and should not be relied upon in making purchasing decisions. The development, release,
and timing of any features or functionality described for Oracle’s products remains at the sole discretion
of Oracle.
TABLE OF CONTENTS
Disclaimer ..................................................................................................................... 2
Disclaimer 2......................................................................................................... 3
INTRODUCTION .................................................................................................. 4
This whitepaper provides Oracle’s Best Practices for deploying Oracle BI Applications on Oracle Cloud
Platform as a Service (PaaS), which include Compute, Database Cloud (DBCS), and Oracle Analytics
Cloud (OAC) services. The following best practice configurations are based on our real world
experiences with installing and configuring Oracle BI Applications and Oracle Business Intelligence on
Oracle® Cloud Platform as a Service (PaaS) for key Oracle customers.
Some key configurations that you must follow while creating the Compute Instances that includes Storage
on Oracle Cloud (PaaS) are discussed in this section.
Apply these configurations on the following layers while creating Compute Instances:
Make the following changes to the newly created install user. For example, “oracle” user
/etc/security/limits.conf file:
oracle soft nofile 999999
oracle hard nofile 999999
oracle soft nproc 131072
oracle hard nproc 131072
oracle soft core unlimited
oracle hard code unlimited
It is recommended to implement above ulimits settings to avoid following potential Oracle BI Applications
system issues:
- If file descriptors (open files - nofile) is set to low value, then the Oracle BI Applications processes
(sawserver, nqsserver) stop responding and throw too many “Open Files” error messages in the
BI logs. You can check current open files value using the "ulimit -n" command.
If a max user processes (nproc) value is low (default is 1024), then the exception
“java.lang.OutOfMemoryError: unable to create new native thread” occurs for bi_serverN/JavaHost
processes or fork failed error message is logged in the system/BI logs. Linux has a maximum allowed
process per user limit. You can check this value using the "ulimit -u" command.
Note: Don’t attach Storage Volume to store BI Apps/OAS files while creating the Compute instance. You
can’t detach Storage Volume for storing BI Apps/OAS files if you attached this Storage Volume while
creating the Compute instance.
It is recommended to attach a Storage Volume for storing BI Apps/OAS files after the Compute instance
is successfully created. See Updating an Instance in Using Oracle Compute Cloud Service (for PaaS).
Note: Select file system EXT4 and add /dev/xvdd /u01 ext4 defaults 0 0 in /etc/fstab to ensure mount isn’t
deleted when you reboot the box.
Reduced network traffic/latency between the Compute instance and DBaaS node can improve the
performance of queries. Since network latency is critical for query performance, it is recommended to
place all services (Compute, DBaaS) in the same data center, if your account allows.
For example, for Oracle BI Application/Business Intelligence and the database mustn’t be in two different
data centers.
2.0 DATABASE as a Service (DBaaS) FOR ORACLE CLOUD PLATFORM AS A SERVICE
(PaaS)
Some key configurations that you must follow while creating Database as a Service (DBaaS) on Oracle
Cloud (PaaS) are discussed in this section.
Note: If AES 256 encryption is done after the fact, then you must export the TableSpaces through
datapump, drop existing TableSpace, recreate the TableSpaces using AES 256 encryption, and then
import the TableSpaces through datapump.
Example: Append the AES 256 encryption notation to the bottom of the DDL such as:
CREATE TABLESPACE "TEST_BIPLATFORM" DATAFILE
'/u02/app/oracle/oradata/TEST_biplatform.dbf' SIZE 67108864
AUTOEXTEND ON NEXT 16777216 MAXSIZE 1073741824
LOGGING ONLINE PERMANENT BLOCKSIZE 8192
EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
ENCRYPTION USING 'AES256' DEFAULT STORAGE (ENCRYPT);
blogs.oracle.com/oracle
facebook.com/oracle Copyright © 2022, Oracle and/or its affiliates. All rights reserved. This
document is provided for information purposes only, and the contents
twitter.com/oracle
hereof are subject to change without notice. This document is not
oracle.com warranted to be error-free, nor subject to any other warranties or
conditions, whether expressed orally or implied in law, including implied
warranties and conditions of merchantability or fitness for a particular
purpose. We specifically disclaim any liability with respect to this
document, and no contractual obligations are formed either directly or
indirectly by this document. This document may not be reproduced or
transmitted in any form or by any means, electronic or mechanical, for
any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Other names may be trademarks of their respective owners.