Friday, December 11, 2020

Clone a Weblogic Instance

How To Replicate WebLogic 12c (12.2.1.3.0) Standalone Installation onto Remote Linux Server Without XServer? (Doc ID 2535666.1)

Friday, September 11, 2020

Thursday, July 23, 2020

Email Notification for Automatic Backups in OCI DB VM

How to Configure Email Notification for Automatic Backups in OCI Database Service Instance (Doc ID 2666093.1)

Thursday, July 2, 2020

Saturday, April 18, 2020

Reference Docs - Oracle E-Business Suite on OCI

Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure - 2517025.1

Deploying Oracle E-Business Suite Cloud Manager on Oracle Cloud Infrastructure - 2434500.1

Oracle By Example Tutorials for Oracle E-Business Suite on Oracle Cloud Infrastructure
https://docs.oracle.com/cd/E72030_01/infoportal/learning.html#liftshift

Managing Network Profiles in Oracle E-Business Suite Cloud Manager on Oracle Cloud Infrastructure (Doc ID 2434008.1)

https://apexapps.oracle.com/pls/apex/f?p=44785:141:107258786119558::::P141_PAGE_ID,P141_SECTION_ID:523,3680

https://apexapps.oracle.com/pls/apex/f?p=44785:141:6842618603832::::P141_PAGE_ID,P141_SECTION_ID:521,3649

Friday, October 18, 2019

Upload files to Oracle Object Storage Classic with FTM CLI

1. Download the FTM CLI  (File Transfer Manager command-line interface) from below URL.

https://www.oracle.com/downloads/cloud/storage-cloud-upload-cli-downloads.html

2. Upload the ftmcli-v2.4.3.zip to the cloud server.

3. Configure below parameters in the ftmcli.properties file.

rest-endpoint=
user=

4. Then copy the file required to upload to the same directory

5. Then upload the backup using below command.

$  ls
ftmcli.jar  ftmcli.log  ftmcli.properties  README.txt  test.tar

$  java -jar ftmcli.jar upload Apps_Backup test.tar
Enter your password:
Uploading file: test.tar to container: Apps_Backup
File successfully uploaded: test.tar
Estimated Transfer Rate: 26671KB/s

Thursday, January 17, 2019

Oracle DBCS Apex Reconfiguration

Error

DBCS APEX URL is not working.


Resolution Action Plan

Login to the DBCS and execute following as root user

cd /var/opt/oracle/ocde/assistants/ords
./ords –ords_action=reconfigure

Tuesday, January 15, 2019

Lift & Shift Oracle E-Business Suite From On-Premises to Oracle Cloud Infrastructure Classic Using EBS Cloud Tools


Oracle EBS Lift & Shift Phases
·        Phase I: Back up your on premises Oracle E-Business Suite environment to Oracle Cloud Infrastructure Object Storage Classic.
·        Phase II: Provision your desired topology on Oracle Cloud Infrastructure Classic, restoring your application tier to Compute Classic and your database tier to either Compute Classic, Oracle Database Cloud Service (DBCS), or Exadata Cloud Service (Exadata CS).

Pre-requisites of Oracle EBS Lift & Shift
·         On premises Oracle EBS database must be in ARCHIVELOG mode with versions 11.2.0.4 or 12.1.0.2 with latest database patches applied referring to My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes.
·         AD-TXK Delta 10 should be applied to the on premises Oracle EBS environment before taking the backup.
·         Even if your instance already has AD-TXK Delta 10 applied, refer to My Oracle Support Knowledge Document 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2, and ensure any additional one-off patches listed for AD and TXK are also applied on your instance.

Following minimum cloud services are required according to the topology chosen for lift & shift.

Description of Requirements
Number of Virtual Machines (VM)
OCPUs
Memory
Storage
External IPs
Oracle Cloud Infrastructure Object Storage Classic
(Conditional)
N/A
N/A
N/A
Size of application tier code + database (object)
N/A
EBS Cloud Admin Tool virtual machine (VM)
1
1
7.5 GB
Required: 20 GB (block) 
1
Oracle Traffic Director (OTD) VM
1
1
7.5 GB
25 GB (block)
1
Application tier VM
n (where 'n' is number of application tier nodes in the target environment)
n*m (where 'm' is the number of OCPUs in the shape selected for the application tier; the minimum for 'm' is 1)
Release 12.2 = 15 GB per VM
Release 12.1 = 7.5 GB per VM
Strictly dependent on your on-premises environment. The minimum requirements are shown below:
·         Shared application tier: 170 GB + 40 GB for each additional application tier (block)
·         Non-shared application tier: 170 GB x n (block)
·         Per language: 16 GB (block)
n
Database Tier
Oracle Cloud Infrastructure Compute Classic or DBCS Single-node database
1
2
15 GB
Dependent on the size of your database and backup options chosen
1
DBCS
Oracle RAC
2
4 x 2
15 GB x 2
Dependent on the size of your database and backup options chosen
2
Exadata CS
Oracle RAC
(See Footnote 3)
2
8 x 2
240 GB x 2
42 TB
2



Deploying or Updating the EBS Cloud Admin Tool
Deploy the EBS Cloud Admin Tool to your cloud domain, by following the Oracle by Example tutorial Deploying the EBS Cloud Admin Tool to Oracle Cloud Infrastructure Classic.

To deploy the EBS Cloud Admin Tool for the first time, you will use the Oracle Cloud Marketplace images listed in the following table:
Marketplace Listing Name
Application Machine Image Name Example
Comments
EBS Provisioning Tools Image
OPC_OL6_9_X86_64_EBS_ORCH_VM_<Date>
Includes the EBS Cloud Admin Tool
EBS OS-Only Image
OPC_OL6_9_X86_64_EBS_OS_VM_<Date>
Required for deploying EBS instances

If you have already deployed the EBS Cloud Admin Tool, you must ensure it is on the latest codeline by following the instructions in section "Update EBS Cloud Admin Tool to Latest Codeline" of the Oracle by Example tutorial Deploying the EBS Cloud Admin Tool to Oracle Cloud Infrastructure Classic.

Deploying and updating EBS Cloud Admin Tool as per the given documents is very important step to make the EBS lift & shift a success.

Installing the Oracle E-Business Suite Cloud Backup Module On-Premises

You must install the Oracle E-Business Suite Cloud Backup Module on an on-premises Linux server with at least 500 MB of free space and the wget libraries installed. The on-premises Linux server can be one of the Oracle E-Business Suite nodes or another server that resides in your intranet. This server will be referred to as the backup module server for the remainder of this tutorial.
1.       Download Patch 26725016 from My Oracle Support to the backup module server.
2.       Using the commands below, change to the directory where you downloaded the patch file and extract the downloaded patch.

$ cd <download folder>
$ unzip p26725016_R12_Generic.zip
Unzipping the patch zip file creates a directory named RemoteClone.
3.       Change to the RemoteClone directory and change the permission to “execute” for all the downloaded scripts.

$ cd RemoteClone
$ chmod +x *.pl
$ chmod +x lib/*.sh

Backing Up the Environment Using the Oracle E-Business Suite Cloud Backup Module

The Oracle E-Business Suite Cloud Backup Module, EBSCloudBackup.pl, is used to back up your Oracle E-Business Suite environment to Object Storage Classic. This module captures all the information and creates the cln.props file.
1.       Change to the RemoteClone directory on the backup module server if you have not already done so.
2.       Run EBSCloudBackup.pl using the following command:
$ 3pt/perl/bin/perl EBSCloudBackup.pl
3.       On the "Migrate Oracle E-Business Suite - Options" screen, select option 1 to create the backup and upload it to Object Storage Classic.
==============================================
Migrate Oracle E-Business Suite - Options
==============================================
 
Migrate Oracle E-Business Suite - Enter Selection:
1:   Create E-Business Suite Backup and Upload to Oracle Cloud Infrastructure Classic
2:   Create E-Business Suite Backup and Upload to Oracle Cloud Infrastructure
3:   Exit
Enter your choice from above list:  1

Next proceed with rest of the prompts according to the requirement.

Then object storage will be created with a backup as follows.



Create Oracle E-Business Suite Environment on Oracle Cloud From Your Backup

After you have backed up your environment using the Oracle E-Business Suite Cloud Backup Module, you will use the backup to create a new environment with your desired topology.
Refer to the these instructions in section "Creating a New Environment from a Backup" of the Managing Oracle E-Business Suite on Oracle Cloud Infrastructure Classic Using the EBS Cloud Admin Tool Oracle by Example tutorial.

1.       To create an environment from a backup stored on Oracle Cloud Infrastructure Object Storage Classic, choose "2: Oracle Storage Cloud Service (OSCS)" as the backup source:
=======================================================================
Create Oracle E-Business Suite Environment from Backup - Choose Source
=======================================================================

[Ctrl-B: Back, Ctrl-H: Main Menu]

1: Stage Area
2: Oracle Storage Cloud Service (OSCS)
3: Snapshot
4: EBS Snapshot Master
Enter your choice from above list: 2
2.       Next, enter your cloud credentials, including the cloud service endpoints obtained when you provisioned your Oracle E-Business Suite instance. The screen will show default values presented in brackets according to the values entered in the previous execution of the tool. If you do not enter a different response, the tool uses the default value.
===================================================================
Provision Oracle E-Business Suite - Enter Oracle Cloud Credentials
===================================================================

[Ctrl-B: Back, Ctrl-H: Main Menu]

Oracle Compute Cloud Service Endpoint [https://xxx.compute.us.oraclecloud.com/] :
Oracle Storage Cloud Service Endpoint [https://xxx.storage.oraclecloud.com/v1/Storage-xxx] :
Oracle Cloud Compute Service Instance ID [mycloudserviceid] :
Oracle Cloud Identity Domain [myclouddomain] :
Oracle Cloud Data Center Code (examples: em1, us2, ap3) [em1] :
Oracle Cloud User Name [john.smith@example.com] :
Oracle Cloud Password : <password>
Enter Oracle DBaaS Cloud Service Endpoint [https://dbaas.oraclecloud.com/] : 

Note: The REST endpoints are used to identify the location of services at the site level within a datacenter. These endpoints are required in order to create the security artifacts associated with Oracle Compute Cloud instances (VMs). If the provisioning VM is located at a different site from your application tier VM (identified by the Compute Classic endpoint), you will be prompted to provide the provisioning VM REST endpoint, as seen below:

Enter Oracle Compute Cloud Service Endpoint for Provisioning VM :
3.       Next, specify the backup.
===================
Select OSCS Backup
===================
 [Ctrl-B: Back, Ctrl-H: Main Menu]
 Available backups in OSCS:
 1: TEST1
2: TEST2
3: UAT
Choose backup from above list:  1

Next enter the required details for the restoration of Oracle EBS to cloud as the topology required.
After successful completion you will get a login URL like following.




Reference Documents





Managing Oracle E-Business Suite on Oracle Cloud at Customer Using the EBS Cloud Admin Tool (Doc ID 2485430.1)

Getting Started with Oracle E-Business Suite on Oracle Cloud (Doc ID 2066260.1)


Mandatory Information for OCI-C (Compute Classic) Cloud IaaS SRs (Doc ID 2392281.1)

Thursday, November 15, 2018

Re-Create Oracle EBS Inventory

Execute the recreation commands of Oracle EBS inventory as follows.

Database Tier

[oracle@ebis bin]$ /testfs/TEST/db/12.1.0/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/db/12.1.0" ORACLE_HOME_NAME="OraDb12c_home1"
Starting Oracle Universal Installer...
Checking swap space: must be greater than 500 MB.   Actual 98286 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
'AttachHome' was successful.

Application Tier fs1

[oracle@ebis bin]$ /testfs/TEST/fs1/EBSapps/10.1.2/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/fs1/EBSapps/10.1.2" ORACLE_HOME_NAME="TEST_TOOLS__testfs_TEST_fs1_EBSapps_10_1_2"
Starting Oracle Universal Installer...
No pre-requisite checks found in oraparam.ini, no system pre-requisite checks will be executed.
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2018-11-15_04-16-51PM. Please wait ...
'AttachHome' was successful.

[oracle@ebis bin]$ /testfs/TEST/fs1/FMW_Home/oracle_common/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/fs1/FMW_Home/oracle_common" ORACLE_HOME_NAME="OH_fs1_oracle_common"
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 98286 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2018-11-15_04-22-46PM. Please wait ...[oracle@ebis bin]$ The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /testfs/TEST/oraInventory
'AttachHome' was successful.

[oracle@ebis bin]$ /testfs/TEST/fs1/FMW_Home/webtier/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/fs1/FMW_Home/webtier" ORACLE_HOME_NAME="OH_fs1_webtier"
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 98286 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2018-11-15_04-33-54PM. Please wait ...[oracle@ebis bin]$
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /testfs/TEST/oraInventory
'AttachHome' was successful.

[oracle@ebis bin]$ /testfs/TEST/fs1/FMW_Home/Oracle_EBS-app1/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/fs1/FMW_Home/Oracle_EBS-app1" ORACLE_HOME_NAME="OH_fs1_Oracle_EBS_app1"
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 98286 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /testfs/TEST/oraInventory
'AttachHome' was successful.

Application Tier fs2

[oracle@ebis bin]$  /testfs/TEST/fs2/FMW_Home/oracle_common/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/fs2/FMW_Home/oracle_common" ORACLE_HOME_NAME="OH_fs2_oracle_common"
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 98286 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2018-11-15_04-48-03PM. Please wait ... The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /testfs/TEST/oraInventory
'AttachHome' was successful.

[oracle@ebis bin]$ /testfs/TEST/fs2/FMW_Home/webtier/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/fs2/FMW_Home/webtier" ORACLE_HOME_NAME="OH_fs2_webtier"
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 98286 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2018-11-15_04-55-46PM. Please wait ...[oracle@ebis bin]$ The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /testfs/TEST/oraInventory
'AttachHome' was successful.


[oracle@ebis bin]$ /testfs/TEST/fs2/EBSapps/10.1.2/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/fs2/EBSapps/10.1.2" ORACLE_HOME_NAME="TEST_TOOLS__testfs_TEST_fs2_EBSapps_10_1_2"
Starting Oracle Universal Installer...
No pre-requisite checks found in oraparam.ini, no system pre-requisite checks will be executed.
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2018-11-15_04-44-50PM. Please wait ...
'AttachHome' was successful.

[oracle@ebis bin]$ /testfs/TEST/fs2/FMW_Home/Oracle_EBS-app1/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/testfs/TEST/fs2/FMW_Home/Oracle_EBS-app1" ORACLE_HOME_NAME="OH_fs2_Oracle_EBS_app1"
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 98286 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /testfs/TEST/oraInventory
'AttachHome' was successful.


Reference

E-Business Suite Applications Manager Central Inventory & Local Inventory Details For System Administration Install, Clone, Upgrade and Maintenance (Doc ID 1550950.1)

Oracle JCS - Weblogic server Issue Resolution

Error/Issue

Admin server is working but other servers are not working in JCS weblogic server.
Below error is given in the weblogic server admin output.

WARNING: Can not connect DB with URL jdbc:oracle:thin:@//xxx:1526/TEST.5679382404.oraclecloud.internal
java.sql.SQLException: ORA-28001: the password has expired

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:391)
at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:1126)
at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:507)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:546)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:269)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:440)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:1025)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:682)
at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:793)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:614)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)

Root Cause

Database user passwords have been expired

Resolution

Connect to cdb using SQLPLUS <USERNAME>/<PASSWORD>

ALTER SESSION SET CONTAINER= <PDB1>;

SELECT username, account_status from CDB_USERS where ACCOUNT_STATUS like 'EXP%' and username like '%SP%';

SP549992516_STB
SP549992516_MDS
SP549992516_OPSS
SP549992516_IAU_APPEND
SP549992516_IAU_VIEWER

You will get output of all the users with account expired. Now follow one of the below solution.

1) One solution is to alter the OPSS database schema so the password is the same as specified when the Infrastructure domain was configured.

alter user <schema prefix>_OPSS identified by <original_pwd_here>;
By default the schema password is set to Weblogic Administrator password during the provisioning of the Oracle Java Cloud Service instance.
Altering the database user in this way will reactivate the account if it has expired. If the original password is used, no action is required to reconfigure JPS and the OPSS jdbc datasource (as shown below).

OR

2) You follow the note below to change the User password (only if you do not know the password):

<FMW 12c Infrastructure AdminServer / NodeManager Fail to Start : ORA-28001: password has expired or ORA-01017: invalid username/password; ( Note 1682942.1 )>

Reference 

https://docs.oracle.com/en/cloud/paas/java-cloud/jscug/changing-database-schema-password.html#GUID-3290C685-E975-460E-94AE-419406092FE0
https://docs.oracle.com/en/cloud/paas/java-cloud/jscug/problems-failure-running-service-when-schema-user-password-expires.html

Oracle DBCS Backup Error Resolution

Error

Below error is given when login to the DBCS.

login as: opc
Authenticating with public key "key"
Passphrase for key "key":
*** OBKUP::ERROR INFO ***
OBKUP::ERROR Cannot complete the Archivelogs Backup to Cloud Storage
OBKUP::ERROR KBHS-00715 HTTP CONNECTION ERROR
OBKUP::ERROR An http error was detected please verify your connectivity
*** OBKUP::ERROR END ***

Root Cause

Cloud account password of user xyz@yyyy.com has been changed.

Resolution

As root user, create a file to hold backup configuration:
# vi /tmp/bkp.conf

The contents of file should be:

bkup_cfg_files=yes
bkup_disk=yes
bkup_disk_recovery_window=7
bkup_oss=yes
bkup_oss_recovery_window=30
bkup_oss_url=https://xxx.storage.oraclecloud.com/v1/Storage-xxx/DBaaS
bkup_oss_user=xyz@yyyy.com
bkup_oss_passwd=actualPassword

(Replace actualPassword with correct password of user xyz@yyyy.com)

Change permission on this file as:
# chmod 0600 /tmp/bkp.conf

Now, execute the backup assistant as below
# /var/opt/oracle/ocde/assistants/bkup/bkup -cfg /tmp/bkp.conf

Tuesday, August 21, 2018

Updating EBS Cloud Admin Tool to Latest Version on Oracle Cloud Infrastructure Classic

[root@ff1daa opc]# cat /etc/ebscm.conf
version=18.2.1
previous_version=18.1.1
tf_version=0.10.8
ocirubysdk_version=1.2.4
ocicli_version=2.4.7
ocitfprovider_version=2.0.7
chefclient_version=12.16.42
chefdk_version=1.0.3
chefserver_version=12.17.5
remoteclone_version=1.7
otd_version=12.2.1.2.0
knife-oc_version=2.0.14
knife-ebs_version=1.0.0
knife-bmc_version=1.0.0
ebsinfra_version=1.0.0
provider=ocic
mode=upgrade
status=completed
[root@ff1daa opc]# su - oracle
[oracle@ff1daa ~]$ cd /u01/install/APPS/apps-unlimited-ebs
[oracle@ff1daa apps-unlimited-ebs]$
[oracle@ff1daa apps-unlimited-ebs]$ ls
bin            ebs_misc                  lib              README.md
build          EBS-New-Prov-backups.txt  LICENSE          RemoteClone
change_log     ebsoc                     local            resources
DBTargets.txt  ebs-unlimited.properties  out              self-update
EBS-METADATA   java                      ProvisionEBS.pl  summary
[oracle@ff1daa apps-unlimited-ebs]$ mkdir ~/ebs-orch-backup
[oracle@ff1daa apps-unlimited-ebs]$
[oracle@ff1daa apps-unlimited-ebs]$ cd EBS-METADATA/
[oracle@ff1daa EBS-METADATA]$
[oracle@ff1daa EBS-METADATA]$
[oracle@ff1daa EBS-METADATA]$ ls
ebsocmetadata.json  OCIClassicOSImage.json  psu_bp_label.json
[oracle@ff1daa EBS-METADATA]$ cp OCIClassicOSImage.json ~/ebs-orch-backup
[oracle@ff1daa EBS-METADATA]$ cd /u01/install/APPS/apps-unlimited-ebs/bin
[oracle@ff1daa bin]$ ls
createEBSChefServer.pl  job_scheduler.sh             selfUpdate.pl
DRSwitchOver.pl         ProvisionEBSBackup.pl        UpdateOplan.pl
ebsocMain.pl            ProvisionEBSOnBMCSBackup.pl  updatePrivateIP.sh
[oracle@ff1daa bin]$ perl selfUpdate.pl
Attempting to upgrade EBS Admin Tool to Version: 18.2.1.1 ..
Downloading the latest archive (EBSCloudAdminTools_v18.2.1.1.tgz)..
Extracting latest archive file..
Executing setup.sh
========================================================
Setting up Oracle EBS Cloud Admin Tool VM
Verify /tmp/EBSCloudAdminTools_v18.2.1.1/setup.out for complete details.
========================================================
Creating directory /u01/setupbkp.20180821024457
Moving /u01/install/APPS/apps-unlimited-ebs/bin to /u01/setupbkp.20180821024457
Moving /u01/install/APPS/apps-unlimited-ebs/lib to /u01/setupbkp.20180821024457
Moving /u01/install/APPS/apps-unlimited-ebs/resources to /u01/setupbkp.20180821024457
Current Chef Server version "12.17.5" is same as available version "12.17.5". No action performed.
Extracting apps-unlimited-ebs.zip to /u01/install/APPS
Copying chef-12.16.42-1.el6.x86_64.rpm
Un-installing gem knife-ebs
Un-installing gem knife-oc
Installing gem knife-oc
Installing gem knife-ebs
Extracting RemoteClone.zip to /u01/install/APPS/apps-unlimited-ebs
========================================================================
Oracle EBS Cloud Admin Tool VM is setup successfully
Version: 18.2.1.1
Mode: upgrade
Verify /tmp/EBSCloudAdminTools_v18.2.1.1/setup.out for complete details.
========================================================================
EBS Admin Tool Upgraded Successfully, Please restart the interview..
[oracle@ff1daa bin]$

[root@ff1daa opc]# cat /etc/ebscm.conf
version=18.2.1.1
previous_version=18.2.1
tf_version=0.10.8
ocirubysdk_version=1.2.4
ocicli_version=2.4.7
ocitfprovider_version=2.0.7
chefclient_version=12.16.42
chefdk_version=1.0.3
chefserver_version=12.17.5
remoteclone_version=1.7
otd_version=12.2.1.2.0
knife-oc_version=2.0.14
knife-ebs_version=1.0.0
knife-bmc_version=1.0.0
ebsinfra_version=1.0.0
provider=ocic
mode=upgrade
status=completed

Reference

http://www.oracle.com/webfolder/technetwork/tutorials/obe/cloud/compute-iaas/deploying_ebs_cloud_admin_tool/09admintool.html#section8

Tuesday, May 22, 2018

Oracle APEX, ORDS Deployment on Apache Tomcat

Steps of Oracle APEX, ORDS Deployment on Apache Tomcat

1. Install Oracle Database

2. Create a tablespace.

CREATE TABLESPACE APEX_DATA DATAFILE '/u01/APEX/db/data/apex_001.dbf' SIZE 500M AUTOEXTEND ON NEXT 1M;

3. Download Oracle appex and unzip ( Also ORACLE_HOME/apex directory can be used )

sqlplus / as sysda

SQL> -- @apexins.sql tablespace_apex tablespace_files tablespace_temp images
SQL>
SQL> @apexins.sql APEX_DATA APEX_DATA TEMP /i/

SQL> @apxchpwd.sql

SQL> @apex_rest_config.sql

SQL> @apex_epg_config.sql /u01/APEX/db/11.2.0

SQL> ALTER USER ANONYMOUS ACCOUNT UNLOCK;

Check the port setting for XML DB Protocol Server.

SQL> SELECT DBMS_XDB.gethttpport FROM DUAL;

GETHTTPPORT
-----------
          0

1 row selected.

SQL>

If it is set to "0", you will need to set it to a non-zero value to enable it.

SQL> EXEC DBMS_XDB.sethttpport(8080);

PL/SQL procedure successfully completed.

4. Check the APEX URL is working fine. http://<server-name>:<port>/apex

5. Download and unzip Apache Tomcat

# su - tomcat

export JAVA_HOME=/home/tomcat/jdk1.8.0_77
export CATALINA_HOME=/home/tomcat/apache-tomcat-7.0.68
export CATALINA_BASE=$CATALINA_HOME

Start and stop Tomcat using the following scripts.

$ $CATALINA_HOME/bin/startup.sh
$ $CATALINA_HOME/bin/shutdown.sh


6. Configure ORDS using following steps.

ALTER USER APEX_LISTENER IDENTIFIED BY manager#123 ACCOUNT UNLOCK;
ALTER USER APEX_PUBLIC_USER IDENTIFIED BY manager#123 ACCOUNT UNLOCK;
ALTER USER APEX_REST_PUBLIC_USER IDENTIFIED BY manager#123 ACCOUNT UNLOCK;

-- The next one will fail if you've never installed ORDS before. Ignore errors.
ALTER USER ORDS_PUBLIC_USER IDENTIFIED BY manager#123 ACCOUNT UNLOCK;

# su - tomcat
$ mkdir /home/tomcat/ords
$ cd /home/tomcat/ords
$ unzip /tmp/ords.3.0.11.180.12.34.zip /home/tomcat/ords

mkdir -p /home/tomcat/ords/conf

Edit the "/u01/ords/params/ords_params.properties

-------------------------------------------------------------------------------
db.hostname=oracle.test.com
db.port=1521
db.servicename=ords
#db.sid=
db.username=APEX_PUBLIC_USER
db.password=manager#123
migrate.apex.rest=false
rest.services.apex.add=true
rest.services.ords.add=true
schema.tablespace.default=APEX_DATA
schema.tablespace.temp=TEMP
standalone.mode=false
#standalone.use.https=true
#standalone.http.port=8080
#standalone.static.images=/home/oracle/apex/images
user.apex.listener.password=manager#123
user.apex.restpublic.password=manager#123
user.public.password=manager#123
user.tablespace.default=APEX_DATA
user.tablespace.temp=TEMP
sys.user=SYS
sys.password=manager#123
-------------------------------------------------------------------------------

$ $JAVA_HOME/bin/java -jar ords.war configdir /home/tomcat/ords/conf

$JAVA_HOME/bin/java -jar ords.war configdir /u01/ords/                                                                                        conf
Jun 15, 2018 5:21:32 PM
INFO: Set config.dir to /u01/ords/conf in: /u01/ords/ords.war

$ $JAVA_HOME/bin/java -jar ords.war

$ $JAVA_HOME/bin/java -jar ords.war
Enter 1 if you want to use PL/SQL Gateway or 2 to skip this step.
If using Oracle Application Express or migrating from mod_plsql then you must en                          ter 1 [1]:
Enter the database password for APEX_PUBLIC_USER:
Confirm password:
Jun 15, 2018 5:23:24 PM
INFO: Updated configurations: defaults, apex, apex_pu, apex_al, apex_rt
Installing Oracle REST Data Services version 3.0.12.263.15.32
... Log file written to /u01/ords/logs/ords_install_core_2018-06-15_172324_00763.log
... Verified database prerequisites
... Created Oracle REST Data Services schema
... Created Oracle REST Data Services proxy user
... Granted privileges to Oracle REST Data Services
... Created Oracle REST Data Services database objects
... Log file written to /u01/ords/logs/ords_install_datamodel_2018-06-15_172341_00566.log
Completed installation for Oracle REST Data Services version 3.0.12.263.15.32. Elapsed time: 00:00:18.614


7. Deploy on Tomcat using following steps.

Copy the APEX images to the Tomcat "webapps" directory.

$ mkdir $CATALINA_HOME/webapps/i/
$ cp -R /home/oraapex/apex/images/* $CATALINA_HOME/webapps/i/
Copy the "ords.war" file to the Tomcat "webapps" directory.

$ cd /u01/ords
$ cp ords.war $CATALINA_HOME/webapps/

8. ORDS should now be accessible using the following type of URL.

http://<server-name>:<port>/ords/

Thursday, April 19, 2018

ERP Cloud On-Site Printing Documents

How To Configure Printers In Fusion Applications (Doc ID 1447191.1)
Setup Instructions for Printing from Oracle Cloud (Doc ID 1964157.1)
How to Set Up Printer Configuration For Cloud/SaaS and Customer On-Site For Fusion Applications (Doc ID 1554333.1)
Oracle Fusion BI: How to Add the BI Administrator Role to a user in Release 12. (Doc ID 2238277.1)
Troubleshooting Guide For Cloud Printer (Doc ID 2140116.1)
How To Install End Point URL SSL Certificates In Default Fusion Truststore (Doc ID 2120300.1)

Saturday, April 7, 2018

Configure Oracle Database Backup Cloud Service

Download opc_installer.zip from OTN and unzip.

[oracle@db-cld-inst-001 opc]$ unzip opc_installer.zip
[oracle@db-cld-inst-001 opc]$ ls
opc_installer.zip  opc_install.jar  opc_readme.txt
[oracle@db-cld-inst-001 opc]$ mkdir lib
[oracle@db-cld-inst-001 opc]$ mkdir wallet
[oracle@db-cld-inst-001 opc]$ ls
lib  opc_installer.zip  opc_install.jar  opc_readme.txt  wallet

[oracle@db-cld-inst-001 opc]$ java -jar opc_install.jar -serviceName Storage -identityDomain gse00112591 -opcId 'your account id' -opcPass 'unFair@5FOrd' -walletDir /u01/app/oracle/opc/wallet -libDir /u01/app/oracle/opc/lib
Oracle Database Cloud Backup Module Install Tool, build 12.2.0.1.0DBBKPCSBP_2017-11-28
Oracle Database Cloud Backup Module credentials are valid.
Oracle Database Cloud Backup Module wallet created in directory /u01/app/oracle/opc/wallet.
Oracle Database Cloud Backup Module initialization file /u01/app/oracle/product/12.2.0/dbhome_1/dbs/opcKTSDB02.ora created.
Downloading Oracle Database Cloud Backup Module Software Library from file opc_linux64.zip.
Download complete.

[oracle@db-cld-inst-001 lib]$ rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Fri Apr 6 17:31:44 2018

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

connected to target database: KTSDB02 (DBID=2214310033)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name KTSDB02 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 5 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 2 G PARMS  'SBT_LIBRARY=libopc.so, ENV=(OPC_PFILE=/u01/app/oracle/product/12.2.0/dbhome_1/dbs/opcKTSDB02.ora)';
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 2 G;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE ON;
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/12.2.0/dbhome_1/dbs/snapcf_KTSDB02.f'; # default

RMAN> configure default device type to sbt;

old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
new RMAN configuration parameters are successfully stored


RMAN>  configure device type sbt parallelism 4;

old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 5 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters are successfully stored


RMAN> configure channel device type sbt parms='SBT_LIBRARY=/u01/app/oracle/opc/lib/libopc.so,SBT_PARMS=(OPC_PFILE=/u01/app/oracle/product/12.2.0/dbhome_1/dbs/opcKTSDB02.ora)';

old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 2 G PARMS  'SBT_LIBRARY=libopc.so, ENV=(OPC_PFILE=/u01/app/oracle/product/12.2.0/dbhome_1/dbs/opcKTSDB02.ora)';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=/u01/app/oracle/opc/lib/libopc.so,SBT_PARMS=(OPC_PFILE=/u01/app/oracle/product/12.2.0/dbhome_1/dbs/opcKTSDB02.ora)';
new RMAN configuration parameters are successfully stored


RMAN> configure compression algorithm 'MEDIUM';

new RMAN configuration parameters:
CONFIGURE COMPRESSION ALGORITHM 'MEDIUM' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
new RMAN configuration parameters are successfully stored

RMAN> set encryption on identified by "Manager#123" only;

executing command: SET encryption

RMAN> show all;

RMAN configuration parameters for database with db_unique_name KTSDB02 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=/u01/app/oracle/opc/lib/libopc.so,SBT_PARMS=(OPC_PFILE=/u01/app/oracle/product/12.2.0/dbhome_1/dbs/opcKTSDB02.ora)';
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 2 G;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE ON;
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'MEDIUM' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/12.2.0/dbhome_1/dbs/snapcf_KTSDB02.f'; # default

RMAN> backup database plus archivelog;

Starting backup at 07-APR-18
current log archived
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=40 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Oracle Database Backup Service Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_2: SID=252 device type=SBT_TAPE
channel ORA_SBT_TAPE_2: Oracle Database Backup Service Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_3
channel ORA_SBT_TAPE_3: SID=31 device type=SBT_TAPE
channel ORA_SBT_TAPE_3: Oracle Database Backup Service Library VER=12.2.0.1
allocated channel: ORA_SBT_TAPE_4
channel ORA_SBT_TAPE_4: SID=49 device type=SBT_TAPE
channel ORA_SBT_TAPE_4: Oracle Database Backup Service Library VER=12.2.0.1
skipping archived logs of thread 1 from sequence 1 to 50; already backed up
channel ORA_SBT_TAPE_1: starting archived log backup set
channel ORA_SBT_TAPE_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=51 RECID=51 STAMP=972812031
channel ORA_SBT_TAPE_1: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_1: finished piece 1 at 07-APR-18
piece handle=4hsvnrp0_1_1 tag=TAG20180407T093424 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:35
Finished backup at 07-APR-18

Starting backup at 07-APR-18
using channel ORA_SBT_TAPE_1
using channel ORA_SBT_TAPE_2
using channel ORA_SBT_TAPE_3
using channel ORA_SBT_TAPE_4
skipping datafile 5; already backed up 1 time(s)
skipping datafile 6; already backed up 1 time(s)
skipping datafile 8; already backed up 1 time(s)
channel ORA_SBT_TAPE_1: starting full datafile backup set
channel ORA_SBT_TAPE_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u02/app/oracle/oradata/KTSDB02/system01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_2: starting full datafile backup set
channel ORA_SBT_TAPE_2: specifying datafile(s) in backup set
input datafile file number=00013 name=/u02/app/oracle/oradata/KTSDB02/PDB1/sysaux01.dbf
channel ORA_SBT_TAPE_2: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_3: starting full datafile backup set
channel ORA_SBT_TAPE_3: specifying datafile(s) in backup set
input datafile file number=00003 name=/u02/app/oracle/oradata/KTSDB02/sysaux01.dbf
channel ORA_SBT_TAPE_3: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_4: starting full datafile backup set
channel ORA_SBT_TAPE_4: specifying datafile(s) in backup set
input datafile file number=00012 name=/u02/app/oracle/oradata/KTSDB02/PDB1/system01.dbf
input datafile file number=00015 name=/u02/app/oracle/oradata/KTSDB02/PDB1/PDB1_users01.dbf
input datafile file number=00019 name=/u02/app/oracle/oradata/SP390751824_svctbl.dbf
channel ORA_SBT_TAPE_4: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_4: finished piece 1 at 07-APR-18
piece handle=4lsvnrq5_1_1 tag=TAG20180407T093459 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_4: backup set complete, elapsed time: 00:00:55
channel ORA_SBT_TAPE_4: starting full datafile backup set
channel ORA_SBT_TAPE_4: specifying datafile(s) in backup set
input datafile file number=00014 name=/u02/app/oracle/oradata/KTSDB02/PDB1/undotbs01.dbf
input datafile file number=00018 name=/u02/app/oracle/oradata/SP390751824_wlsservices.dbf
input datafile file number=00020 name=/u02/app/oracle/oradata/SP390751824_ias_opss.dbf
channel ORA_SBT_TAPE_4: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_2: finished piece 1 at 07-APR-18
piece handle=4jsvnrq4_1_1 tag=TAG20180407T093459 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_2: backup set complete, elapsed time: 00:01:12
channel ORA_SBT_TAPE_2: starting full datafile backup set
channel ORA_SBT_TAPE_2: specifying datafile(s) in backup set
input datafile file number=00004 name=/u02/app/oracle/oradata/KTSDB02/undotbs01.dbf
channel ORA_SBT_TAPE_2: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_3: finished piece 1 at 07-APR-18
piece handle=4ksvnrq4_1_1 tag=TAG20180407T093459 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_3: backup set complete, elapsed time: 00:01:11
channel ORA_SBT_TAPE_3: starting full datafile backup set
channel ORA_SBT_TAPE_3: specifying datafile(s) in backup set
input datafile file number=00016 name=/u02/app/oracle/oradata/SP390751824_mds.dbf
input datafile file number=00021 name=/u02/app/oracle/oradata/SP390751824_UMS.dbf
input datafile file number=00017 name=/u02/app/oracle/oradata/SP390751824_iau.dbf
channel ORA_SBT_TAPE_3: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_1: finished piece 1 at 07-APR-18
piece handle=4isvnrq4_1_1 tag=TAG20180407T093459 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:01:15
channel ORA_SBT_TAPE_1: starting full datafile backup set
channel ORA_SBT_TAPE_1: specifying datafile(s) in backup set
input datafile file number=00007 name=/u02/app/oracle/oradata/KTSDB02/users01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_4: finished piece 1 at 07-APR-18
piece handle=4msvnrrt_1_1 tag=TAG20180407T093459 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_4: backup set complete, elapsed time: 00:00:25
channel ORA_SBT_TAPE_1: finished piece 1 at 07-APR-18
piece handle=4psvnrsf_1_1 tag=TAG20180407T093459 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:25
channel ORA_SBT_TAPE_2: finished piece 1 at 07-APR-18
piece handle=4nsvnrsc_1_1 tag=TAG20180407T093459 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_2: backup set complete, elapsed time: 00:00:28
channel ORA_SBT_TAPE_3: finished piece 1 at 07-APR-18
piece handle=4osvnrsc_1_1 tag=TAG20180407T093459 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_3: backup set complete, elapsed time: 00:00:28
Finished backup at 07-APR-18

Starting backup at 07-APR-18
current log archived
using channel ORA_SBT_TAPE_1
using channel ORA_SBT_TAPE_2
using channel ORA_SBT_TAPE_3
using channel ORA_SBT_TAPE_4
channel ORA_SBT_TAPE_1: starting archived log backup set
channel ORA_SBT_TAPE_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=52 RECID=52 STAMP=972812201
channel ORA_SBT_TAPE_1: starting piece 1 at 07-APR-18
channel ORA_SBT_TAPE_1: finished piece 1 at 07-APR-18
piece handle=4qsvnrt9_1_1 tag=TAG20180407T093641 comment=API Version 2.0,MMS Version 12.2.0.1
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:25
Finished backup at 07-APR-18

Starting Control File and SPFILE Autobackup at 07-APR-18
piece handle=c-2214310033-20180407-18 comment=API Version 2.0,MMS Version 12.2.0.1
Finished Control File and SPFILE Autobackup at 07-APR-18