OCI: 32bits VM provisioning for eBS 11i

eBS 11i supports only Linux 32bits on the middle tier. To deploy eBS 11i on OCI, a 32 bits custom image must be imported in the vmdk or qcow2 format.

OL5 images can be found as appliance from edelivery, but their format looks not compatible with OPC, VMware 12.x or VirtualBox 5.1. The solution is to create a custom image using virtual box:

 

#1 Download from edelivery Oracle Linux 5 Update 11 iso image

This is V47134-01.iso

 

#2 From VirtualBox, create a new VM using the iso image

 

#3 Export this VM in the OVF 2.0 format.

Give it a name, for example OL5u11.ova

 

#4 Move this appliance on Linux

 

#5 On this linux box, install the qemu-kvm utility

yum install qemu-kvm -y

 

#6 Unzip the appliance file and run the tar command

tar xvf OL5u11.ova
OL5u11-disk001.vmdk
OL5u11.mf
OL5u11.ovf

 

#7 Convert the disk file into the qcow2 format

qemu-img convert -O qcow2 OL5u11-disk001.vmdk OL5u11.qcow2

 

#8 Using Cyberduck, upload the OL5u11.qcow2 file into an object storage bucket on OCI.

 

#9 Import the custom image by referencing the image file from the object storage, for example:

https://objectstorage.eu-frankfurt--1.oraclecloud.com/n/<namespace>/b/EBS/o/OL5u11.qcow2

Give it a name, for example OL5_32bits. The import should last 1 hours

 

#10 Provision a compute with the OL5 custom image.

 

 

Advertisements

OCI(-c): Deploying EMCC 13cR2 and 13cR3 on DBcs 12.2 and 18.2 Extreme Performance

This note is about deploying EMCC 13cR2 or 13cR3 on either OCI or OCI Classic with the database running on DBcs 12.2 or 18.2 Extreme Edition

Due to some improper validation being executed, the solution for this topology is first to install the software, apply a quickfix to support EE, then configure the OMS.

 

Database setup

#1 Provision the DBcs or dbsystem

Provision an emccdb DBcs with an emcc PDB running 12.2 or 18.2 with 2 OCPU/15GB, 100GB data.

 

#2 Setup the access rules to allow the compute hosting the OMS to connect to the database.

On OCI-c, create an IP security list for example emccdb_listener_client 10.29.0.0/16 (when 10.29.0.0 would be the private subnet)

On OCI-c, create a security rules to allow dblister access between the IP security list emccdb_listener_client and the security_list emccdb/db01/ora_db

On OCI, create an ingress rules to allow all traffic from 10.0.0.0/23

 

#3 Setup the PDB

Setup the PDB with the following parameters

ALTER SESSION SET CONTAINER=emcc;
ALTER SYSTEM SET "_allow_insert_with_update_check"=TRUE SCOPE=BOTH;
ALTER SYSTEM SET session_cached_cursors=500 SCOPE=SPFILE; 
ALTER PROFILE DEFAULT LIMIT password_verify_function null;
SHUTDOWN IMMEDIATE;
STARTUP;

OMS setup

#1 OMS provisioning

Provision a compute with 2 OCPUs, 15GB memory, and 100GB disk space

 

#2 Setup the oracle UNIX user

Create the oracle user. Use this note as a guideline.

Copy the private key to the oracle user to allow ssh directly to ssh.

 

#3 Increase system parameters

Set the following parameter

On Classic and OL6.9, in /etc/security/limits.conf
oracle soft nofile 1024
oracle hard nofile 65536

On OCI and OL75 in /etc/security/limits.d/30-nofile.conf
oracle soft nofile 1024
oracle hard nofile 65536

 

#4 Prepare the product home directories

mkdir -p /u01/app/oracle/product/gc133
mkdir -p /u01/app/oracle/product/emagent
mkdir -p /u01/app/oracle/product/library 
mkdir -p /u01/app/oracle/product/gc_bip/config 
mkdir -p /u01/app/oracle/product/gc_bip/cluster
mkdir -p /u01/app/oraInventory 
chown -R oracle:oinstall /u01/app/oracle
chown -R oracle:oinstall /u01/app/oraInventory

Note that if the purpose is to deploy EMCC in HA mode, at this point, a shared directory may have to be setup for the library and BI Publisher

 

#5 Create the file /etc/oraInst.loc

Create the file /etc/oraInst.loc with the following content, owned by oracle:oinstall

inventory_loc=/u01/app/oraInventory
inst_group=oinstall

 

#6 Download em13cR3

Download the emcc 13cR3 software. Use this note as a guideline.

 

#7 Install the system prereq

Classic OL6.9:
yum install make binutils gcc libaio glibc-common libstdc++ libXtst sysstat glibc-devel.i686 glibc-devel glibc

Classic OL7.4:
sudo yum install make binutils gcc libaio glibc-common libstdc++ sysstat glibc-devel.i686 glibc-devel libXtst xdpyinfo wget xorg-x11-xauth

OCI OL7.5: sudo yum install gcc glibc-devel glibc-devel.i686

 

#8 Generate the response file to prepare for a silent install

ssh -X oracle@<opchost>
chmod +x em13300_linux64.bin
./em13300_linux64.bin -getResponseFileTemplates -outputLoc /home/oracle

 

#9 Configure the installation file

Edit the file software_only.rsp

 

#10 Run the installer in silent mode

./em13300_linux64.bin -silent -responseFile /home/oracle/software_only.rsp

 

#11 Change the prereq checking files

Edit the file /u01/app/oracle/product/gcXXX/install/requisites/properties/stopPrereqOnDemand.properties and make sure that the following property is set to TRUE

id_check_db_is_enterprise_edition=TRUE

If install in interactive, the same would be achieved by downloading the following file for EMCC 13.2: p25679612_132000_Generic.zip

 

#12 Run the configuration assistant

/u01/app/oracle/product/gc132/sysman/install/ConfigureGC.sh

 

At this point, if getting any issue with the DISPLAY settings, check out this note.

 

EM13c: agent install via rpm

Here is a script to install a the emcc agent automatically, via rpm.

As a prerequisite, the rpm must has been built and could be pulled from somewhere via http.

As root:

rm oracle-agt-13.2.0.0.0-1.0.x86_64.rpm*

wget http://where_do_i_can_pull_the_rpm/oracle-agt-13.2.0.0.0-1.0.x86_64.rpm

rpm -e oracle-agt-13.2.0.0.0-1.0.x86_64

rm -fr /u01/app/emagent/*
rm -fr /u01/app/emagent/agent_inst/*

rpm -ivh oracle-agt-13.2.0.0.0-1.0.x86_64.rpm --relocate /usr/lib/oracle/agent=/u01/app/emagent

echo "
OMS_HOST=<my_oms_host>
OMS_PORT=443
AGENT_REGISTRATION_PASSWORD=<welcome1>
#-------------------------------------------------------------------------------
AGENT_USERNAME=emagent
AGENT_GROUP=dba
AGENT_PORT=3879
#-------------------------------------------------------------------------------
ORACLE_HOSTNAME=<myhost_where_the_agent_is_getting_deployed>
AGENT_INSTANCE_HOME=/01/app/emagent/agent_inst" >/u01/app/emagent/agent.properties

/etc/init.d/oracle-agt RESPONSE_FILE=/u01/app/emagent/agent.properties

/u01/app/emagent/agent_13.2.0.0.0/root.sh

OCI-c: ebs 12.1.3/11gR2 DR/standby 101

On Oracle Cloud Infrastructure classic, to setup a standby for eBS 12.1.3/11gR2 with a Vision demo environment.

  • Created the primary environment by provisioning eBS Vision 12.1.3/11.2.0.4. See this note.
  • Provision a Database cloud service to host the standby database
  • Provision a compute using the eBS OS-only image from the marketplace
  • Duplicate the database
  • Run a preclone on the primary environment (db+apps)
  • Run autoconfig on the db tier, to preconfigure the db tier. See this note.
  • Run autoconfig on the apps tier, to preconfigure the apps tier. See this note.

To execute a switchover/failover, check this note.

To synchronize the target file system, after a patch get applied on the primary, check this note.

Refer to the MOS 1070033.1 for generic guidelines.

OCI-c: Running autoconfig on a standby apps tier for eBS R12.1.3

Perform the following steps to prepare an apps tier node for eBS 12.1.3.

This note is written in the context of an eBS 12.1.3/11gR2 standby setup as described in this master note.

It is assumed that

  • preclone has already been run on the primary environment.
  • The primary db is called vis121p
  • The secondary db is called vis121s
  • The filetree to be preserved on the standby is /u01/install/APPS/

There are two steps to be executed to preconfigure the appstier for a future failover/switchover:

  1. create the new autoconfig file
  2. Run autoconfig to generate the $INST_TOP directory to manage the apps tier on the secondary

 

#1) Generate the context file:

cd <COMMON_TOP>/clone/bin
perl adclonectx.pl <INST_TOP>/appl/admin/<PRIMARY CONTEXT>.xml

Example:

cd /u01/install/APPS/apps_st/comn/clone/bin
perl adclonectx.pl /u01/install/APPS/inst/apps/vis121p_vis121papp01/appl/admin/vis121p_vis121papp01.xml

                    Copyright (c) 2002 Oracle Corporation                        Redwood Shores, California, USA
                        Oracle E-Business Suite Rapid Clone
                                 Version 12.0.0
                      adclonectx Version 120.23.12010000.3
Running: /u01/install/APPS/apps_st/comn/clone/bin/../jre/bin/java -Xmx600M -classpath /u01/install/APPS/apps_st/comn/clone/bin/../jlib/ojdbc14.jar:/u01/install/APPS/apps_st/comn/clone/bin/../jlib/xmlparserv2.jar:/u01/install/APPS/apps_st/comn/clone/bin/../jlib/java oracle.apps.ad.context .CloneContext  -e /u01/install/APPS/inst/apps/vis121p_vis121papp01/appl/admin/vis121p_vis121papp01.xmlEnter the APPS password : apps

Log file located at /u01/install/APPS/apps_st/comn/clone/bin/CloneContext_0424112647.log
Provide the values required for creation of the new APPL_TOP Context file.
Target System Hostname (virtual or normal) [vis121s-app01] : 
It is recommended that your inputs are validated by the program.However you might choose not to validate them under following circumstances:
 -If cloning a context on source system for a remote system. -If cloning a context on a machine where the ports are taken and you do not want to shutdown the services at this point. -If cloning a context but the database it needs to connect is not available.
Do you want the inputs to be validated (y/n) [n] ? : 
Target System Database SID : vis121s
Target System Database Server Node [vis121s-app01] : 
Target System Database Domain Name [compute-<domain>.oraclecloud.internal] : 
Target System Base Directory : /u01/install/APPS
Target System Tools ORACLE_HOME Directory [/u01/install/APPS/apps/tech_st/10.1.2] : /u01/install/APPS/tech_st/10.1.2
Target System Web ORACLE_HOME Directory [/u01/install/APPS/apps/tech_st/10.1.3] : /u01/install/APPS/tech_st/10.1.3
Target System APPL_TOP Directory [/u01/install/APPS/apps/apps_st/appl] : /u01/install/APPS/apps_st/appl
Target System COMMON_TOP Directory [/u01/install/APPS/apps/apps_st/comn] : /u01/install/APPS/apps_st/comn
Target System Instance Home Directory [/u01/install/APPS/inst] : 
Username for the Applications File System Owner [oracle] : 
Group for the Applications File System Owner [oinstall] : 
Target System Root Service [enabled] : 
Target System Web Entry Point Services [enabled] : 
Target System Web Application Services [enabled] : 
Target System Batch Processing Services [enabled] : 
Target System Other Services [enabled] : 
Do you want to preserve the Display [localhost:0.0] (y/n)  : 
Invalid input value. 'y' or 'n' required.

Do you want to preserve the Display [localhost:0.0] (y/n)  : n
Target System Display [vis121s-app01:0.0] : 
Do you want the the target system to have the same port values as the source system (y/n) [y] ? : yComplete port information available at /u01/install/APPS/apps_st/comn/clone/bin/out/vis121s_vis121s-app01/portpool.lst

RC-40201: Unable to connect to Database vis121s.
New context path and file name [/u01/install/APPS/inst/apps/vis121s_vis121s-app01/appl/admin/vis121s_vis121s-app01.xml] : 


Creating the new APPL_TOP Context file from :  /u01/install/APPS/apps_st/appl/ad/12.0.0/admin/template/adxmlctx.tmp


The new APPL_TOP context file has been created :  /u01/install/APPS/inst/apps/vis121s_vis121s-app01/appl/admin/vis121s_vis121s-app01.xml


Log file located at /u01/install/APPS/apps_st/comn/clone/bin/CloneContext_0424112647.logcontextfile=/u01/install/APPS/inst/apps/vis121s_vis121s-app01/appl/admin/vis121s_vis121s-app01.xmlCheck Clone Context logfile /u01/install/APPS/apps_st/comn/clone/bin/CloneContext_0424112647.log for details.

 

The new config file should now be created.

 

#2 Run autoconfig to generate all files and scripts:

cd /u01/install/APPS/apps_st/appl/ad/12.0.0/bin
perl adconfig.pl contextfile=/u01/install/APPS/inst/apps/vis121s_vis121s-app01/appl/admin/vis121s_vis121s-app01.xml run=INSTE8

OCI: Provisioning an eBS edelivery template as a custom image

To provision an eBS appliance, configured as a custom image, on the Oracle Cloud Infrastructure (OCI):

#1 Download the virtual appliance from edelivery, for example the Spare OS-only Virtual Appliance , available in the V46057.1.zip file

#2 Convert the appliance from the .ova format to the vdmk format

VMWare Workstation can be used to import the appliance, that it will convert automatically into the .vmdk format. Note that the .ova filesize is 720MB and the .vmdk file size is 2GB. This convert should take 5 minutes.

#3 From the OCI console, create a bucket ‘EBS’ in the Object Storage.

#4 Using Cyberduck, upload the 2GB file Oracle-E-Business-Suite-OS-12.1.3-disk1.vmdk into the EBS bucket.

#5 Import the custom image by referencing the image file from the object storage, for example:

https://objectstorage.eu-frankfurt--1.oraclecloud.com/n/<namespace>/b/EBS/o/Oracle-E-Business-Suite-OS-12.1.3-disk1.vmdk

Give it a name, for example ebs1213. The import should last 2-3 hours.

#6 Provision a new image by using the newly created ebs1213 custom image

#7 Login to the image as oracle/oracle then su – root to change its password.