Oracle EBS R12.2.7 on Virtual Box

Oracle EBS R12.2.7 on Virtual Box

Go to the download folder of 12.2.7 and execute below command:

copy /b Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.00 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.01 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.02 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.03 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.04 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.05 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.06 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.07 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.08 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.09 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.10 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.11 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.12 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.13 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.14 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.15 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.16 + Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova.17 Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova

It will create one single Oracle-E-Business-Suite-12.2.7_VISION_INSTALL.ova file, which need to be import from Vmbox:

Start Virtual Box and navigate to File -> Import Appliance

Click on ‘Expert Mode’ and edit the ‘Virtual Disk Image’ path to a location with adequate space (~500GB), in this example I am using my Samsung Portable SSD T1 1TB dive mounted at ‘/Volumes/Samsung_T1’

Click ‘Import’, go to lunch or grab a coffee and watch the progress bar if you prefer, the remaining time will re-calulate periodically. Once complete, start up your new Oracle EBS R12.2.6 VM from within Oracle VirtualBox

The initial boot will prompt you to change the ‘root’, ‘oracle’ and ‘applmgr’ passwords, the process will continue to start and configure an Oracle 12.1.0.2 database called ‘EBSDB’.

Use ‘ifconfig -a’ to determine your VM’s IP address from you VirtualBox console before using SSH from your host to connect using your preferred client.
Add the IP address to your local ‘/etc/host’ file so your browser can resolve your Oracle EBS VISION sandbox environment. e.g. #
192.168.0.23 apps.example.com apps
#

Change directory to ‘/u01/install/APPS/scripts’ to access the database and application stop / start scripts and run ‘startdb.sh’ and
‘startapps.sh’

startdb.sh stopdb.sh startapps.sh stopapps.sh

[oracle@apps scripts]$ ./startdb.sh
Logfile: /u01/install/APPS/12.1.0/appsutil/log/EBSDB_apps/addlnctl.txt

You are running addlnctl.sh version 120.4

Starting listener process EBSDB …

LSNRCTL for Linux: Version 12.1.0.2.0 – Production on 15-AUG-2017 07:42:19 Copyright (c) 1991, 2014, Oracle. All rights reserved.
Starting /u01/install/APPS/12.1.0/bin/tnslsnr: please wait…

TNSLSNR for Linux: Version 12.1.0.2.0 – Production
System parameter file is /u01/install/APPS/12.1.0/network/admin/EBSDB_apps/listener.ora
Log messages writen to /u01/install/APPS/12.1.0/admin/EBSDB_apps/diag/tnslsnr/apps/ebsdb/alert/log.xml Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=apps.example.com)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=apps.example.com)(PORT=1521))) STATUS of the LISTENER
————————
Alias EBSDB
Version TNSLSNR for Linux: Version 12.1.0.2.0 – Production Start Date 15-AUG-2017 07:42:19
Uptime 0 days 0 hr. 0 min. 0 sec Trace Level off
Security ON: Local OS Authentication SNMP OFF
Listener Parameter File /u01/install/APPS/12.1.0/network/admin/EBSDB_apps/listener.ora
Listener Log File /u01/install/APPS/12.1.0/admin/EBSDB_apps/diag/tnslsnr/apps/ebsdb/alert/log.xml Listening Endpoints Summary… (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=apps.example.com)(PORT=1521)))
Services Summary…
Service “EBSDB” has 1 instance(s).
Instance “EBSDB”, status UNKNOWN, has 1 handler(s) for this service… The command completed successfully

addlnctl.sh: exiting with status 0

addlnctl.sh: check the logfile /u01/install/APPS/12.1.0/appsutil/log/EBSDB_apps/addlnctl.txt for more information …

You are running addbctl.sh version 120.1 Starting the database EBSDB …
SQL*Plus: Release 12.1.0.2.0 Production on Tue Aug 15 07:42:19 2017 Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to an idle instance.
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance ORACLE instance started.

Total System Global Area 2147483648 bytes Fixed Size 2926472 bytes
Variable Size 1308625016 bytes Database Buffers 822083584 bytes Redo Buffers 13848576 bytes Database mounted.
Database opened.
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

addbctl.sh: exiting with status 0

[oracle@apps scripts]$ ./startapps.sh
Starting the Oracle E-Business Suite Application Tier Services You are running adstrtal.sh version 120.24.12020000.11
…
All enabled services for this node are started. adstrtal.sh: Exiting with status 0
adstrtal.sh: check the logfile /u01/install/APPS/fs1/inst/apps/EBSDB_apps/logs/appl/admin/log/adstrtal.log for more information …

Before you can log on you will need to enable SYSADMIN and the Demo accounts, Oracle have provided scripts to do this e.g.

[oracle@apps scripts]$ ./enableSYSADMIN.sh

This script will let you set a new password for the SYSADMIN EBS Applications User, the default password most likely was “sysadmin”, so pick a different one now.

Enter new password for SYSADMIN: Re-enter password for SYSADMIN: Changing password for SYSADMIN Log filename : L7583909.log
Report filename : O7583909.out [oracle@apps scripts]$

[oracle@apps scripts]$ ./enableDEMOusers.sh

Enter a new password for the EBS Applications Users, the default password most likely was “welcome”, so pick a different one now…

Enter new password for DEMO users: Re-enter password for DEMO users: Seting password for DEMO users… Log filename : L7583911.log
…
[oracle@apps scripts]$

Oracle EBS R12 Dashboard

You should now be able to logon as ‘SYSADMIN’ or explore your Oracle EBS R12.2.6 VISION sandbox environment using the Demo users (see below) and the password defined above at: htp://apps.example.com:8000/ (htp://apps.example.com:8000/)

“AFENG”, “AMARLIN”, “AMILLER”, “APOTTER”, “BPALMER”, “BWEBB”
“CBROWN”, “CONMGR”, “CONTMGR”, “CSADM”, “DBAKER”, “EBUSINESS” “FBRAMER”, “HRMS”, “ILANG”, “ISUPPORTADMIN”, “JFROST”
“KJONES”, “LJONES”, “MFG”, “MGRMKT”, “MNT”, “OPERATIONS” “PHENRY”, “PIMMGR”, “PLMMGR”, “PROCESS_OPS”, “PROJMFG” “PSTOCK”, “RBATES”, “SCRIPTUSER”, “SERVICES”, “SFM” “SPAIN”, “SVYADMIN”, “TRADEMGR”

How to connect to DATABASE and ASM instance in RAC ?

How to connect to DATABASE and ASM instance in RAC ?

Database for 2 node RAC:

set the environment variable for rdbms.
export ORACLE_SID=ORCLPROD1
sqlplus '/as sysdba'

or

export ORACLE_SID=ORCLPROD2
sqlplus '/as sysdba'


ASM for 2 node RAC:

set the environment variable for ASM instance.
export ORACLE_SID=+ASM1
sqlplus / as sysasm

or

export ORACLE_SID=+ASM2
sqlplus /as sysasm

Unable to create Patch Object Exception occured : PatchObject constructor: Input file does not exist.

Unable to create Patch Object Exception occured : PatchObject constructor: Input file does not exist.

Version:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

Issue:
Error found on invoking patch conflict check using opatch for a PSU patch on database Home.

Error:
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail"not executed
Unable to create Patch Object.
Exception occured : PatchObject constructor: Input file "/u01/stage/etc/config/actions" or "/u01/stage/etc/config/inventory" does not exist.

OPatch succeeded.

Reason:

Error is due to the location (directory) given for the Patch folder given using -ph.

I used the command, "opatch prereq CheckConflictAgainstOHWithDetail -ph ./". Since I gave -ph . the command should have been executed from the directory where the patch was extracted.

In this case the patch folder after extraction was /u01/stage/14275605.

But I invoked the patch conflict check from /u01/stage and specified -ph ./ where it will look for patch files in the current directory and resulted in the error.

Fix:

Move to the folder created after extracting the patch zip file and execute the command again from there.

[oracle@node1 stage]$ cd  /u01/stage/14275605
[oracle@node1 14275605]$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./

or specify the full directory to -ph command from current directory

opatch prereq CheckConflictAgainstOHWithDetail -ph /u01/stage/14275605

Tell me about yourself ? (Weblogic Administrator)

Tell me about yourself ? (Weblogic Administrator)

This is ABC, Currently I'm working with XYZ technologies, I have around 4.8 years of experience as a Weblogic Administrator, from this company i started my career...... initially i started as Oracle Core dba, but later i got a chance to work with Weblogic.

1.I involved in creation and configuration of Domains.
2.Creation and configuration of clusters for providing load balancing and fail over support.
3.Creation and configuration of JDBC and Data sources and connection pools.
4.Deployment of applications.
5.Managing SSL certificates.

Day to day activities.

1.Taking shift handover from previous shifts.
2.Health status check-up of all weblogic server instances
3.Login to admin console and will check the all server status.
4. Make sure all server status should be running
5.If any of the server is failed, Bounse or restart the server manually.
3.Checking the webservices and applications.
4.Periodical deployment on Non prod and production servers.
5.Supporing and following ITIL concepts in Incidents,change and problem management.
6.Providing on call support of 24*7 Basis.
7.Giving shift hand over to next shift.

Working Environment

There are totaly 50 applications deployed on 10 domains.
Each domain contains of 1 horizantal cluster.
Each cluster contains 10-15 managed servers.
Currently we are working on Linux 4.0 and 5.0
Application server weblogic 11g and 12c
webserver Apache 2.0 and 2.2.
Backend DB is Oracle 11g

Weblogic Silent Installation

Weblogic Silent Installation 

1.To install the Bea in Silent mode, we need to specify the arguments as "-mode=silent"

2.and Specify the silent.xml path

3.Silent.xml contains, the BEA Home path,Installation Directory path,Need to specify which component need to install

4.Optionally we can specify the path for the temp directory for extracting the compressed jars

5.Optionally we can specify the log path which can be used for the Tracing the installation errors or exceptions.

6.The installation program does not display any configuration options during the installation process, So u must collect the Licence Agreement and terms & Conditions Documents in advance.

7.Silent Mode of Installation is not available for NetInstallers. So u can use only package Installers.

8.U can use any Package Installer according to your Operating System/Hardware Architecture like: “Jar Installer”   or “executable” Installers  (*.bin or *.exe)

9.Silent-mode installation requires the same amount of temporary disk space and uses the same temporary storage directories as a standard installation.

10.Incorrect entries in the silent.xml file can cause installation failures. So it is always recommend that you create a log file when you start the installation. using (-log option)

11.The XML definition (<?xml version=”1.0″ encoding=”UTF-8″?>) must be at the very beginning of the silent.xml template file, without any preceding space or line breakes in it.

New or Changed Features in WebLogic 12c R2 (12.1.2)

New or Changed Features in WebLogic 12c R2 (12.1.2)

1.WebLogic Server is now availbile in two formats only i.e. zip and jar version. (JDK is mandatory and must be installed prior to WebLogic installation)

2.JDK version 7 or higher (1.7) is recommended to install WebLogic 12.1.2 (though WebLogic 12.1.2 works JDK 1.6 as well)

3.Tool to apply patches in WebLogic has changed from BSU (BEA Smart Update) to opatch

4.Option to install WebLogic in silent mode is now -silent -responseFile [path_to_response_file] (Earlier option was -mode=silent -silent_xml=[path_to_silent.xml])

5.In previous versions of WebLogic upgrade of WebLogic Domain used to be done using Domain Upgrade Wizard but now (12.1.2 onwards) uses Reconfiguration Wizard

6.In earlier version of WebLogic, Node Manager is installed  at WebLogic Home ($WL_HOME) level but now Java Node Manager by default is installed at $DOMAIN level i.e. $DOMAIN_HOME/nodemanager (with an option to configure Node Manager at Server Level or Custom Location)

7.From 12.1.2 there is an option to configure Node Manager at Domain Level or Custom Location (as shown in above screenshot)

8.Offline Cloning of Managed Server is now possible using configuration wizard (config.sh) or WLST (clone) – In previous releases it was possible to clone a Managed Server from WebLogic Console only (Online Cloning)

9.Cluster in pre 12.1.2 version is now also called as Configured Cluster in WebLogic 12.1.2

10.Dynamic Cluster introduced in WebLogic 12c is a cluster with one or more Dynamic Servers (More on Dynamic Cluster and Dynamic Server in WebLogic later)

11.WebLogic 12c supports Database 12c including Application Continuity (AC) , Database Resistence Connection Pooling (DRCP), Global Data Services (GDS)

12.Diagnostics : Built-in Diagnostics Modules added that provides simple and easy mechanism for basic health check and performance monitoring of WebLogic Serve