Skip navigation.

Online Apps DBA

Syndicate content
Oracle Implementation & Training Experts
Updated: 17 hours 58 min ago

WebLogic 12.1.3 on CentOS vagrant

Fri, 2015-12-04 09:10

This post is related to Weblogic Vagrant from our Oracle Weblogic Administration Training (next batch starts on 12th Dec, 2015 – Register now for early bird discount, limited time only) where we cover Weblogic Installation, configuration, Clustering, Logging, Deployment, JDBC and JMS etc.

WebLogic VagrantThe WebLogic Vagrant project is a set of subprojects that will help you create virtual machines pretty easily, by using Vagrant to set up the VMs with VirtualBox, and Puppet to help creating the necessary logical infrastructure.

1. Getting Started: 

Download the following on your Windows host machine. Here I am working on Windows 8.1 platform.

  1. Vagrant latest version
  2. Oracle Virtual Box latest stable version
  3. Oracle JDK latest version
  4. Oracle WebLogic 12.1.3 generic version
  5. Git for Windows
  6. PuTTy for Windows

Install the Vagrant, Oracle VirtualBox, Git all are wizard based easy to install them.

2. Git Clone WebLogic-Vagrant:

You can get the puppet, shell scripts which are used to configure the WebLogic on CentOS VirtualBox.

git clone WebLogic-Vagrant

Sync folder guest CentOS with host Windows

Make all binaries available in Software folder, Here I have used ‘F:/Softwares’ contains binaries JDK, WebLogic 12c jar file.

3. Modifications in site.pp:

The puppet script which prepared according to the JDK1.7 available that time. Now latest JDK 1.8 and it varies. So you might need to modify these values on your machine as well according to young version of JDK.

Here I am sharing the part of site.pp file.

class java {
  require os

  $remove = [ "java-1.7.0-openjdk.x86_64", "java-1.6.0-openjdk.x86_64" ]

  package { $remove:
    ensure  => absent,
  }

  include jdk8

  jdk8::install7{ 'jdk1.8.0_45':
      version                   => "8u45" ,
      fullVersion               => "jdk1.8.0_45",
      alternativesPriority      => 18000,
      x64                       => true,
      downloadDir               => "/var/tmp/install",

      urandomJavaFix            => true,
      rsakeySizeFix             => true,
      cryptographyExtensionFile => "UnlimitedJCEPolicyJDK8.zip",
      sourcePath                => "/software",
  }
}

The most important one is first line where WebLogic domain template will be used to create new domain.

4. Changes in vagrantfile:

The vagrantfile contains a virtual machine definitions that contains WebLogic admin server, Further you can configure node1, node2 machines and have a production simulated environment.

# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.define "wls12cbox" , primary: true do |config|
  config.vm.box = "centos-6.5-x86_64"
  config.vm.box_url = "https://dl.dropboxusercontent.com/s/np39xdpw05wfmv4/centos-6.5-x86_64.box"
   config.vm.hostname = "vagrantcentos64.example.com"
  config.vm.network :forwarded_port, guest: 7001, host: 7001, auto_correct: true
  config.vm.network :private_network, ip: "192.168.33.10"
  config.vm.synced_folder "F:/Softwares", "/vagrant_data"

  config.vm.provider :virtualbox do |vb|
       vb.customize ["modifyvm", :id, "--memory", "3072"]
  end
  config.vm.provision :puppet do |puppet|
    puppet.manifests_path = "puppet/manifests"
    puppet.module_path = "puppet/modules"
    puppet.manifest_file  = "site.pp"
    puppet.options = "--verbose"
  end
  end
 end

Now this vagrant box is ready for execution.

vagrant up

WebLogic Vagrant box up

Vagrant Provision

There are many ways to provision the Virtual boxes we can even use Bash Shell scripts to ensure the required configurations made once boxes is launched.

After the VirtualBox creation we can apply the configuration tool such as puppet, Chef or Ansible etc to make a reusable environment within number of minutes. Whereas same was took places in the earlier versions for months. So this configuration procedure would greatly improves the team work, and focus on the targeted issues rather than configuration of infrastructure this way it is helps Agility for JEE projects.

vagrant provision some times requires reload the boxes reload will reapply the Vagrantfile changes. We can further develop this to give better box by editing the Vagrantfile and reloading it.

VagrantReloadProvision

Note that when the vagrant provision fails then we need to find the reasons and fix in the Vagrantfile. The vagrant reload command will help to reload the updated configuration for box.

5. Puppet Manifestation:

Puppet manifestation provisions that CentOS box must contain oracle user, WebLogic server required kernel parameters all OS level changes are configured and then install WebLogic with installwls.pp script. This provisioning uses silent mode installation where it required two files:

  1. responseFile which is provided in xml format silent_1213.xml.erb and
  2. oracle inventory defined by puppet.

Here is the silent.xml.erb that is required for WebLogic 12.1.3. In this script the ORACLE_HOME is substituted from the calling puppet script installWls.pp file.

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#The oracle home location. This can be an existing Oracle Home or a new Oracle Home 
ORACLE_HOME=<%= @mdwHome %>
 
#Set this variable value to the Installation Type selected. 
e.g. WebLogic Server, Coherence, Complete with Examples.
INSTALL_TYPE=WebLogic Server
 
#Provide the My Oracle Support Username. If you wish to ignore Oracle 
Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=
 
#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=
 
#Set this to true if you wish to decline the security updates. 
Setting this to true and providing empty string for My Oracle Support username will 
ignore the Oracle Configuration   Manager configuration
DECLINE_SECURITY_UPDATES=true
 
#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
 
#Provide the Proxy Host
PROXY_HOST=
 
#Provide the Proxy Port
PROXY_PORT=
 
#Provide the Proxy Username
PROXY_USER=
 
#Provide the Proxy Password
PROXY_PWD=
 
#Type String (URL format) Indicates the OCM Repeater URL which should be 
of the format [scheme[Http/Https]]://[repeater host]:[repeater port]
COLLECTOR_SUPPORTHUB_URL=

6. The nodemanager .pp configuration changes for WebLogic 12.1.3:

Here I have validating the $version value present in the nodemanager.pp file and executing the startNodeManager command with the existing value given error.

Whenever the server is booted immediately Nodemanager will be launched. If you use puppet provision that will ensure the WebLogic admin server running when the box is launched.

If you want to learn more issues like above or wish to discuss challenges you are hitting in Oracle Weblogic Server, register for our Oracle Weblogic Administration Training.

We are so confident on quality and value of our training that We provide 100% Money back guarantee so in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money.

Did you subscribe to our YouTube Channel (443 already subscribed) and Private FaceBook Group (666 Members) ?

 

Learn Oracle Weblogic Server Administration

 

Get 100 USD OFF + 100% Money Back Guarantee

Click here to get Early Bird Discounts

The post WebLogic 12.1.3 on CentOS vagrant appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

I am SO Sorry – our WebLogic Webinar blew up on us. But there’s good news…

Tue, 2015-12-01 08:15
This entry is part 2 of 3 in the series WebLogic Server

Webinar Replay

I’ve been dreading writing this post for the last 14 hour when I knew it was the only next step. You see that over 334 of you showed up for our Live Free  WebLogic webinar (We only catered for 250 seats which mean 84 of you couldn’t join or didn’t get invite) So we were looking  more forward to this live webinar than any other we host.

Here are few reason why we were so excited  for this webinar:

  1. We had Twice as many people registered as we’ve had in past.
  2. We have spent 20 of our past 25 working hours totally reworking the slides and adding our latest learning in presentation. So our attendee can get most out of our webinar.

But something which never happened-the damm thing blew up ! That moment was helpless for all of us. We know very small portion of our attendee got left hanging last time but  still  we wanted to share this with all of you for a couple of reason.
To say we’re sorry both to those who were waiting and everyone else. We don’t know the popularity of this topic and was not aware that so many people will registered so we hit this issue that many of you can’t join our webinar.We hope to never have the same twice.

We apologized sincerely to all of our attendee who try to join but can’t join webinar or registered by never received as we were full. Unfortunately we can’t go back in time and save the aggravation of attempting to join a frozen webinar.

But here is what we will do specially for all of you who can’t join:

  • Here are some free stuff: Find link for Presentation ebook that we used during webinar you can download same from here :)
  • Review Webinar Recording: You can watch webinar recording at no cost here!
  • That’s not enough: We will soon organizing again a new weblogic webinar with new topics and new information for you so keep your eye on our E-mail or either webinar registration Page
  • One more bonus for all of you Q & A from weblogic webinar: Atul and team spent 1 hour answering just question after Webinar , I’ll be posting these Q/A in my next post. If you have any question related to WebLogic come and join our weblogic Training

In the end it is an outright miserable situation to be in when technology impedes your ability to deliver quality program to your audience. But hopefully you can develop a human relationship with that audience.

Again offer you Apologies and your plan to improve forward and move forward .

Stay Tuned for our FREE Webinars !

 

Learn WebLogic with Early Bird Discounts

 

Get 100 USD OFF + 100% Money Back Guarantee

Click here to get Early Bird Discounts

 

The post I am SO Sorry – our WebLogic Webinar blew up on us. But there’s good news… appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

Running Oracle Weblogic Server on Linux ? Did you check Entropy

Sun, 2015-11-29 03:27
This entry is part 1 of 3 in the series WebLogic Server

This post covers performance issue (Admin Console taking ages while accessing) and is must read if you are running WebLogic Server on Linux.

We encountered this issue while managing Fusion Middleware (with WebLogic) for one of our customer where accessing Admin Console was very Slow and there were no errors in log (memory and CPU were just fine).

A Brief decsription about Entropy on linux Platform:

An Operating System performs cryptographic operations at every time (on ssh challenges, https connections, etc.) .
Linux has two devices to provide random data at any time: /dev/random and /dev/urandom so the /dev/random pool gets consumed quite fast with the cryptographic operations. This pool also gets consumed while performing I/O operations, mouse,keyboard etc. and since, the Java uses /dev/random by default as entropy generator device that runs out of random bits and Therefore, makes us waiting for more time.

To learn about issues like this Join our Oracle Weblogic Administration Training  (next batch starts on 12th December 2015) where we also cover Oracle Certification for WebLogic Administrators 1Z0-133.

 

Cause:

After starting the WebLogic server instance the available Entropy on the system was substantially decreasing.

Check the default system entropy using the command below:
# cat /proc/sys/kernel/random/poolsize
4096

Check the available entropy using th command below:
# cat /proc/sys/kernel/random/entropy_avail
125

Solution:

1. Temporary Fix:

a. Override the JAVA_OPTIONS environment variable before starting WebLogic Server via shell scripts (./startWeblogic.sh)

export JAVA_OPTIONS=”${JAVA_OPTIONS} -Djava.security.egd=file:/dev/./urandom”

b. Start Weblogic server instance
./startWeblogic.sh

 

2. Permanent Fix:

a. Edit the Java Security Properties file located in $JAVA_HOME/jre/lib/security/java.security and change the securerandom.source property which points to /dev/random (by default). set it as:

securerandom.source=file:/dev/./urandom

b. Save the changes and Start WebLogic server

 

If you want to learn more issues like above or wish to discuss challenges you are hitting in Oracle Weblogic Server, register for our Oracle Weblogic Administration Training.

We are so confident on quality and value of our training that We provide 100% Money back guarantee so in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money.

Did you subscribe to our YouTube Channel (435 already subscribed) and Private FaceBook Group (666 Members) ?

 

Learn Oracle Weblogic Server Administration

 

Get 100 USD OFF + 100% Money Back Guarantee

Click here to get Early Bird Discounts

The post Running Oracle Weblogic Server on Linux ? Did you check Entropy appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

Confused about Oracle Identity Management : See me #Sangam15 Hyderabad on 21/22 Nov 2015

Fri, 2015-11-13 05:36

Are you confused about so many Oracle Identity & Access Management (OAM, OIM, OID, OVD, OAG and the list goes on…) ?

Do you understand Identity Management Jargons like Authentication, Authorization (Fine-grained vs Coarse-grained), Provisioning, Reconciliation, SoD ?

Wish you could automatically creates Users and assign Roles/Responsibilities in Oracle E-Business Suite centrally ?

Interested in enhancing your skills and see my Journey from DBA/Apps DBA to Author of book on Oracle Identity & Access Management ?

I_M_Speaking_Sangam15

 

 

I am presenting two papers on Oracle Identity & Access Management at #Sangam15 on 22nd Nov 2015 at Hyderabad@India

 

 

First Presentation at 10 AM on 22nd Nov (Sunday) covers various Oracle Identity & Access Management products and basics functionality of each of those products .

 

Second Presentation at 2:40 PM on 22nd Nov (Sunday) covers Oracle Identity Management and Integration with Oracle E-Business Suite. This session also covers basic concepts like Provisioning, Reconciliation, User, Role, and Responsibility Management in Oracle E-Business Suite Apps R12/11i using OIM.

 

Seats are limited for my session at #Sangam15 so register for these two sessions early to avoid disappointment.

1. Overview of Oracle IAM for terminology and all the products that are part of Oracle IAM like OAM, OIM, OID, OVD, OIF, OAG, OWSM …..

Screen Shot 2015-11-13 at 11.24.48

 

2. Integrate Oracle E-Business Suite with OIM for User, Role and Responsibility Management

Screen Shot 2015-11-13 at 11.08.00

 

 

Special Bonus to those who attend presentation will get my “30 Day Apps DBA Challenge” absolutely FREE (more details during the session).

 

Did you subscribe to our Private Facebook Group and YouTube Channel ?

The post Confused about Oracle Identity Management : See me #Sangam15 Hyderabad on 21/22 Nov 2015 appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

Starting OAM Managed Server from Weblogic Console, Check This ?

Wed, 2015-11-11 10:03
This entry is part 2 of 2 in the series Oracle Access Manager

This post is related to OAM Managed server issue from our Oracle Access Manager Training (next batch starts on 29th Nov, 2015 – Register now for early bird discount, limited time only) where apart from Architecture, Installation, Configuration, Integration we also cover High Availability & Disaster Recovery.

As OAM is deployed on Weblogic Server, We cover  WebLogic Concepts like Domain, Admin & Managed Server and Clusters.

One of the trainee from our previous batch encountered issue while starting OAM Managed server (oam_server1) from WebLogic Administration Console (/console). When a server is started using Console, a utility called Node Manager is used in the background. Make sure that Node Manager is running and Machine is associated with Managed Server

If you see node manager is fine and still startup fails then check the Managed Server log file located at $DOMAIN_HOME/ servers/ [oam_server1]/ logs and in our case, it was showing below error messages:

Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]Security Provider service class name for IAMSuiteAgent is not specified.
at com.bea.common.engine. internal.ServiceEngineImpl. findOrStartService (ServiceEngineImpl.java:365)
at com.bea.common. engine.internal. ServiceEngineImpl. findOrStartService (ServiceEngineImpl.java:315)
at com.bea.common. engine.internal. ServiceEngineImpl. lookupService (ServiceEngineImpl.java:257)
at com.bea.common. engine.internal. ServicesImpl. getService(ServicesImpl.java:72)
at weblogic.security. service.internal. WLSIdentityServiceImpl. initialize(WLSIdentityServiceImpl.java:46)
at weblogic.security. service. CSSWLSDelegateImpl. initializeServiceEngine(CSSWLSDelegateImpl.java:299)
at weblogic. security.service. CSSWLSDelegateImpl. initialize(CSSWLSDelegateImpl.java:220)
at weblogic.security. service. CommonSecurityServiceManagerDelegateImpl. InitializeServiceEngine (CommonSecurity ServiceManagerDelegateImpl.java:1789)

Root Cause:

In the nodemanager.properties file (configuration file that is used to start node manager), the value of the flag StartScriptEnabled was set to false (by default) because of which the parameters that are provided in startWeblogic.sh was not provided to JVM and therefore, resulting in the error as specified above.

Fix:

1. Stop Node Manager: Exit from the terminal in which node manager started.

Note: there is no script to stop Node Manager so just kill the process

2. Run setNMProps.sh script located under $MW_HOME/oracle_common/common/bin
./setNMProps.sh (This will enable the StartScriptEnabled flag in nodemanager.properties)

You should get the output as:  “Appending required nodemanager.properties”

3. Start Node manager ./startNodeManager located under $WL_HOME/server/bin

./startNodeManager.sh

4. Start Managed Server using Administration Console. It should be RUNNING now.

If you want to learn more issues like above or wish to discuss challenges you are hitting in Oracle Access Manager Implementation, register for our Oracle Access Manager Training (next batch starts on 29th Nov, 2015 – Register now for early bird discount, limited time only).

We are so confident on quality and value of our training that We provide 100% Money back guarantee so in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money (or ask us from our happy trainees in our private Facebook Group).

Did you subscribe to our YouTube Channel (375 already subscribed) ?

The post Starting OAM Managed Server from Weblogic Console, Check This ? appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

Oracle E-Business Suite – R12.2 Post Install checks (HTTP, Help Page, Login Page, JSP) got failed

Mon, 2015-11-09 08:41

This post is from our Oracle Apps DBA (R12.2) Training for E-Business Suite  (In which we cover Architecture, Installation, File System, WebLogic Concepts, Patching, Cloning , Common Tasks and difference in 12.2 from previous version, Register here for Oracle Apps DBA 12.2 Training )

One of the trainee from our current batch, having an issue in Oracle E-Business Suite R12.2 (EBS) installation where some of the post-install checks (Help Page, Login Page, JSP, HTTP, Virtual Directory) was failed as shown below:

post_install_checks_failed

Click on X symbol, to know the error message for the issue as here I clicked on  X symbol beside HTTP and it display, below window with error message

error_message

After that I checked in EBS Installation logs /u01/oracle/PROD/fs1/inst/apps/PROD_iamdemo07/logs/08261229.log for the root cause of the issue and below are the error messages:

RW-50015: Error: – Http Server Virtual Directories is not responding. The service might not have started on the port yet. Please check the service and use the retry button.

JSP

—-

checking URL = http://<hostname>:8088/OA_HTML/jtfTestCookie.jsp

RW-50015: Error: – JSP is not responding. The service might not have started on the port yet. Please check the service and use the retry button.

Login Page

———–

RW-50015: Error: – Login Page is not responding. The service might not have started on the port yet. Please check the service and use the retry button.

WLS Domain Validation

———————

EBS Domain validation failed for RUN filesystem.

————————————————–

Check Domain deployment logs and re-deploy the RUN domain.

————————————————————

Log file at : /u01/oracle/PRD12288/fs1/EBSapps/appl/admin/PROD_iamdemo07/log .

——————————————————————————-

EBS Domain validation failed for PATCH filesystem.

————————————————-

Check Domain deployment logs and re-deploy the PATCH domain.

Log file at : /u01/oracle/PRD12288/fs2/EBSapps/appl/admin/PROD_iamdemo07/log .

Connecting AdminServer

======================

Connecting to t3://<hostname>:7090 with userid weblogic …

This Exception occurred at Thu Aug 27 05:03:07 BST 2015.

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://<hostname>:7090: Destination unreachable; nested exception is:

 java.net.ConnectException: Connection refused; No available router to destination]

Error while connecting Admin Server !!!

Exiting WebLogic Scripting Tool.

.end std out.

.end err out.

ERROR: Unable to add the loggers for oacore application

ERROR: Failed to create the EBS domain.

Failed to deploy the E-Business Suite domain

 Then I came to know that EBS domain was not created and deployed successfully and When  I checked on AdminServer log file /u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/EBS_domain_PROD55/servers/AdminServer/logs

It was showing below error message:

Caused By: java.io.FileNotFoundException: /tmp/.ovdlock.tmp (Permission denied)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:233)
at oracle.ods.virtualization.config.ConfigureAdapters.configure(ConfigureAdapters.java:512)
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.pushLdapNamesTolibOvd

(OvdIGFServiceProvider.java:312)
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.prepareDataPush2libOvd

(OvdIGFServiceProvider.java:370)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance

(LdapIdentityStoreProvider.java:339)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance

(LdapIdentityStoreProvider.java:118)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance

(LdapIdentityStoreProvider.java:74)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance

(ContextFactoryImpl.java:139)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext

(ContextFactoryImpl.java:170) 

Fix for this issue:

1. As /tmp/.ovdlock.tmp was not having permission Installation failed. So we have change the permission to 777 with below command:

chmod -R 777 /tmp/.ovdlock.tmp

2. Another is to run the adProvision.pl script which is located under $AD_TOP/patch/115/bin and delete failed EBS domain as

perl adProvisionEBS.pl ebs-delete-tech -contextfile=/u01/oracle/PROD55/fs1/inst/apps/PROD55_iamdemo07/

appl/admin/PROD55_iamdemo07.xml -techtype=wls

3. Then again run the adProvision.pl script which is located under $AD_TOP/patch/115/bin on both file system (RUN and Patch) and Create EBS domain as

a) Run adProvision.pl script on RUN file system (fs1)

perl adProvisionEBS.pl ebs-deploy-alltech -contextfile=/u01/oracle/PROD55/fs1/inst/apps/PROD55_iamdemo07/appl/

admin/PROD55_iamdemo07.xml 

You should see below output:

NMProcess: <Aug 19, 2015 2:22:57 PM> <INFO> <EBS_domain_PROD55> <AdminServer> <Rotated server output log to “/u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/EBS_domain_PROD55/

servers/AdminServer/logs/AdminServer.out00001″>
NMProcess: Aug 19, 2015 2:22:57 PM weblogic.nodemanager.server.LogFileRotationUtil log
NMProcess: INFO: Rotated server output log to “/u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/EBS_domain_PROD55/

servers/AdminServer/logs/AdminServer.out00001″
NMProcess: <Aug 19, 2015 2:22:57 PM> <INFO> <EBS_domain_PROD55> <AdminServer> <Server error log also redirected to server log>
NMProcess: Aug 19, 2015 2:22:57 PM weblogic.nodemanager.server.LogFileRotationUtil log
NMProcess: INFO: Server error log also redirected to server log
NMProcess: <Aug 19, 2015 2:22:57 PM> <INFO> <EBS_domain_PROD55> <AdminServer> <Server output log file is ‘/u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/EBS_domain_PROD55/servers/AdminServer/logs/AdminServer.out’>
NMProcess: Aug 19, 2015 2:22:57 PM weblogic.nodemanager.server.AbstractServerManager log
NMProcess: INFO: Server output log file is ‘/u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/

EBS_domain_PROD55/servers/AdminServer/logs/AdminServer.out’
Creation and deployment of E-Business Suite domain completed..
<Aug 19, 2015 2:30:18 PM BST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>

b) Run adProvision.pl script on Patch file system (fs2)

perl adProvisionEBS.pl ebs-deploy-alltech -contextfile=/u01/oracle/PROD55/fs2/inst/apps/PROD55_iamdemo07/appl/

admin/PROD55_iamdemo07.xml 

4. Start All EBS services as

cd $ADMIN_SCRIPTS_HOME

./adstrall.sh <apps_username>/<apps_password>

You should see below output:

All enabled services for this node are started.

adstrtal.sh: Exiting with status 0

adstrtal.sh: check the logfile /u01/oracle/PROD55/fs1/inst/apps/PROD55_iamdemo07/logs/appl/admin/log/adstrtal.log for more information …

This will create complete domain and managed servers.

After that, clicked on Retry button and all Post Install checks passed but one post install check “WLS Domain Validation” have warning message so we can ignore this and proceed further without having any issue as EBS Domain was successfully completed.

WLS_Check_Failed

Now Oracle E-Business Suite R12.2 Installation completed successfully.

Access the EBS URL: http://hostname:port

If you want to learn more about Oracle Apps DBA (Architecture, Installation, WebLogic, Patching, Cloning and other maintenance tasks with the upgrade of Oracle E-Business Suite 12.2.0 to 12.2.4) then have a look at our Oracle Apps DBA (R12.2) Training.

Note: We are so confident on our workshops that we provide 100% Money back guarantee, in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money (or ask us from our 100s of happy trainees in our private Facebook Group)

The post Oracle E-Business Suite – R12.2 Post Install checks (HTTP, Help Page, Login Page, JSP) got failed appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

FREE Live Webinar: Learn Oracle Access Manager (OAM) 11g R2 from team K21

Wed, 2015-11-04 07:54
This entry is part 1 of 2 in the series Oracle Access Manager

k21_oam_webinar

Oracle Access Manager (OAM) is Oracle’s recommended Single Sign-On (SSO) solution and mandatory for Oracle Fusion Applications. Apps DBA’s and Fusion Middleware Administrator with OAM skills have better chances of any opportunities in to Oracle and are always paid higher.

 

Join team K21 Technologies for FREE Webinar on this Saturday (7th November,2015) at 9:00  AM PST/ 12:00 PM EST /10:30 PM IST / 5:00 PM GMT where OAM expert Ganesh Kamble will cover Overview, Architecture and the important components that are part of Oracle Access Manager (OAM).

This Webinar will cover the key points that are important for beginners and those who want to pursue your career in Oracle Identity & Access Management (OAM/OID/OIM).

Oracle Access Manager provides the centralized authentication, authorization and Single sign-on to secure access across enterprise applications.

Below you can see the architecture of Oracle Access Manager 11g R2

OAM

 

 

 

Oracle Access Manager 11g includes:

  • Database that contains OAM metadata and schemas
  • LDAP Server where identities of users and groups are stored
  • OHS /Apache as Web Server
  • Application resource which is protected by OAM
  • OAM Admin Server
  • OAM Managed server
  • WebGate which connects and transfer request from web server to OAM server

To know more about the components of Oracle Access Manager and detailed architecture. Click on the button below to register for our Webinar

 

Click Here to register for the free Webinar

 

If you have any Question related to OAM that you want us to cover in our FREE Webinar on OAM then post it below as comment or ask in our Private Facebook Group

The post FREE Live Webinar: Learn Oracle Access Manager (OAM) 11g R2 from team K21 appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

FREE live webinar : Learn Oracle Apps 12.2 for DBAs and Apps DBAs

Tue, 2015-10-27 08:41

Learn Oracle Apps DBA R12.2 (4)

Do you know enough about the features of Oracle E-Business Suite from 11i to 12 ? Are you interested in becoming an Oracle Apps DBA ?

Join us on our live webinar on Thursday (29th October,2015) at 6:30 – 7:30 PM PST/ 9:30-10:30 PM EST or Friday (30th October,2015) at 7:00-8:00 AM IST to know about the architecture of E-Business Suite highlighting the updates from 11i to 12 and the key points that everyone must know to become an Apps DBA.

To become an Oracle Apps DBA the important thing is that you should be very well familiar with Oracle Applications/E-Business Suite Architecture.

Below you can see the changes in the architecture of EBS R12.2

ebs-122-con9021pdf90210001-8-638

  • Introduction of Fusion Middleware 11g
  • Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g
  • Uses Oracle Application Server 10g R3 (10.1.2.3) for Forms & Reports
  • Default Database 11gR2 (11.2.0.3). Latest is 11.2.0.4 (11g Family)
  • Oracle JSP Compiler is replaced by WebLogic JSP Compiler 11.1.1.4 in R12 version 12.2.
  • Dual File System from R12.2
  • Online Patching – Almost zero Downtime

To know more about the Oracle Apps DBA profession. Click on the button below to register for our webinar

 

Click here to register for the FREE Webinar

The post FREE live webinar : Learn Oracle Apps 12.2 for DBAs and Apps DBAs appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

Oracle Apps R12.2 Log Files Location every Apps DBA must know

Sun, 2015-10-25 09:17

This post covers Log File Location in Oracle E-Business Suite  R12.2 that every Oracle Apps DBA must know. Log File helps in troubleshooting and is first thing you must look when looking at any issue .
This post is from our Oracle Apps DBA (R12.2) Training for E-Business Suite  (next batch starts on 31st October, 2015 and We cover Architecture, Installation, File System, WebLogic Concepts, Patching, Cloning , Common Tasks and difference in 12.2 from previous version. Register here for Oracle Apps DBA 12.2 Training )

One of the trainee from our previous batch asked for the Log File Locations in Oracle E-Business Suite 12.2 so here is the list of Log file locations for Oracle E-Business Suite 12.2 depending on task you are performing:

1. R12.2 Start/Stop Log Files:

a) Startup/Shutdown error message text files like adstrtal.txt, adstpall, adapcctl.txt, adcmctl.txt…for services like oacore, forms, apache, opmn, weblogic admin server/node manager etc

  • $INST_TOP/logs/appl/admin/log

Log files for start/stop of services from $ADMIN_SCRIPTS_HOME

Here is an image representing EBS R12.2 Service control (start/stop) logs:

Green colour boxes indicates location of log files 

4

 

 2. Patching Log files:

a) The Online Patching (ADOP) log files are located on the non-editioned file system (fs_ne), under :

  • $NE_BASE/ EBSapps/ log/adop/ <adop_session_id>/ <phase>_<date>_<time>/ <context_name>/ log

Notefs1 and fs2 are dual file system for software where as fs_ne contains non editioned objects 

This log directory will contain patch logs, patch worker logs and other patch related log files created for specific purposes.
Also, some patch tasks may create separate log files in the same directory from where patch executable is started

3. Log files for concurrent programs/managers

  • $NE_BASE/ inst/ <CONTEXT_NAME>/ logs/ appl/ conc/ log

 Output files for concurrent programs/managers

  • $NE_BASE/inst/<CONTEXT_NAME>/logs/appl/conc/out

Here is an image representing EBS R12.2 Non-Editioned file system Logs:

1

Patching Log file Location:

2

4. Cloning related Log Files:

a) Pre-clone log files in source instance

     I. Database Tier

  • $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)

    II. Application Tier

  • $INST_TOP/admin/log/ (StageAppsTier_MMDDHHMM.log)

b) Clone log files in target instance

    I. Database Tier

  • $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_<time>.log

    II. Apps Tier

  •  $INST_TOP/admin/log/ApplyAppsTier_<time>.log

If your clone on DB Tier fails while running txkConfigDBOcm.pl (Check metalink note – 415020.1)
During clone step on DB Tier it prompts for “Target System base directory for source homes” and during this you have to give like /base_install_dir like ../../r12 and not oracle home like ../../r12/db/tech_st_10.2.0

5. AutoConfig log file:

Autoconfig can be run on Application Tier or Database Tier

a) Autoconfig Log Location on Application tier :

  • $INST_TOP/admin/log/$MMDDHHMM/adconfig.log

b) Autoconfig Log Location on Database tier:

  • $ORACLE_HOME/ appsutil/ log/ $CONTEXT_NAME/ <MMDDHHMM>/  *.log

 

 

6.  Installation Related Logs:

There are four main phases (in context of logs) during R12.2 installation, here is log location of all four phases .

a) The Rapidwiz Configuration File is saved in below locations:

  • $TMP/<MMDDHHMM>/conf_<SID>.txt
  • $INST_TOP/conf_<SID>.txt
  • <RDBMS ORACLE_HOME>/ appsutil/ conf_<SID>.txt

b) Pre-install system check logs:

  • $TMP/<MMDDHHMM>/<MMDDHHMM>.log
  • $TMP/dbPreInstCheck.xxxxx.log
  • $TMP/wtprechk.xxxx/wtprechk.xxxx.log
  • <Global Inventory>/logs/installActions<timestamp>.log

c) Database tier

I. Main Installation log:

  • RDBMS $ORACLE_HOME/ appsutil/ log/ $CONTEXT_NAME/ <MMDDHHMM>.log

II. ORACLE HOME installation logs:

  • RDBMS $ORACLE_HOME/ temp/ $CONTEXT_NAME/ logs/ *.log
  • <Global Inventory>/logs/*.log

d) Application tier

Both primary(Run) and Secondary Edition (Patch) file systems will each contain these logs:

    I. Main Installation Log:

  • $INST_TOP/logs/<MMDDHHMM>.log

    II. FMW and OHS TechStack Installation/Patching logs:

  • $APPL_TOP/admin/$CONTEXT_NAME/log/*
  • <Global Inventory>/logs/*.log

    III. Forms Oracle Home installation logs:

  • $APPL_TOP/admin/$CONTEXT_NAME/log/*.log

 

Here is an image representing the R12.2 Installation logs

ebs_log1

 

6. Fusion Middleware (FMW_HOME) Log Files:

Oracle 12.2 includes Fusion Middleware (WebLogic & OHS) as new components and we cover these components in detail in our Apps DBA Training

 a) Log files for OPMN and OHS processes: Below directory contains log files related OPMN process(opmn.log), OPMN Debug logs(debug.log), HTTP Transaction logs (access.log), security settings related logs.

  • $IAS_ORACLE_HOME/ instances/ <ohs_instance>/ diagnostics/ logs

b) Log files for weblogic node manager: Log file is generated by Node Manager and contains data for all domains that are controlled by Node Manager on a given physical machine.

  • $FMW_HOME/ wlserver_10.3/ common/ nodemanager/ nmHome1/ nodemanager.log

c) Log files for weblogic Oracle Management Service log file: Initial settings AdminServer and Domain level information is written in this log file.

  • $EBS_DOMAIN_HOME/sysman/log

d) Log files for server processes initiated through weblogic: Stdout and stderr messages generated by the server instance (server instances like forms, oafm, oacore etc) at NOTICE severity level or higher are written by Weblogic Node Manager to below directory.

  • $EBS_DOMAIN_HOME/ servers/ <server_name>/ logs/ <server_name>.out

Here is an image representing EBS R12.2 Fusion Middleware Log files:

3

 

If you want to learn more about Oracle Apps DBA (Architecture, Installation, WebLogic, Patching, Cloning and other maintenance tasks with the upgrade of Oracle E-Business Suite 12.2.0 to 12.2.4 then have a look at our  Oracle Apps DBA Training (next batch starts on 31st October, 2015 – Register now for early bird discount, limited time only).

Note: We are so confident on our workshops that we provide 100% Money back guarantee, in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money (or ask us from our 100s of happy trainees in our private Facebook Group)

The post Oracle Apps R12.2 Log Files Location every Apps DBA must know appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

So you know enough in Oracle AppsDBA (EBS) R12.2 – Answer these ? Queries from our Day1 Apps DBA Training

Fri, 2015-10-23 14:14
This entry is part 6 of 6 in the series Oracle Apps 12.2

queries_qanda

This post is from our Oracle Apps DBA (R12.2) Training sharing some of the questions from our Apps DBA Trainees from Day1 (next batch starts on 31st October, 2015 and We cover Architecture, Installation, File System, WebLogic Concepts, Patching, Cloning , Common Tasks and difference in 12.2 from previous version). 

On Day1 of Apps DBA Training We cover Architecture of Oracle E-Business Suite, File System in R12.2 (and change in File System from 12.1 version) and Technology Stack . Here are some of the questions asked in our previous batches of Oracle Apps DBA. Reason for sharing here is so you can check how much you know or help others by answering under comments section (We’ll be answering these over next few days)

1. What is Jinitiator in Oracle Apps? 2. Where is Jinitiator being used in Oracle Apps ? 3. Why OC4J replaced with WebLogic server 11g? 4. Why we are still using Oracle Apps server 10g R3(10.1.2.3) for Forms & Reports 5. Why we used Dual File system in R12.2 ? Application Tier File System has changed in 12.2 to Dual File System to support ………. (answer this in comment) ?  Register here for Oracle Apps DBA 12.2 Training to learn more on Dual File System or Online Patching (ADOP). 6. How do we know Apps tier is using FS1 or FS2 (where FS1 and FS2 are two file system from Apps Dual File System in 12.2)? 7. FS1 or FS2 (dual file system) is independent to each other – TRUE / FALSE ? 8. What is role of Concurrent Manager ? 9. Why do Concurrent Manager Fail (some of the scenarios in which manager could fail) ?

10. What is Database Version that comes with EBS and Can we use any database version with EBS or are there any restrictions ? 11. What is the purpose of patching in Oracle Apps (E-Business Suite) and is it Compulsory to Patch (More Question on Patching on Day3 of Apps DBA Training) ? Well these are just handful of hundreds of questions we answer either in online class or in support ticket (all our trainings comes with 1 Year support for any queries) or in our Private Facebook Group To ask questions like these or learn more about Oracle Apps DBA in 30 Days, register for our Oracle Apps DBA (R12.2) Training (We are so confident on quality and post training support that We provide 100% Money back guarantee so in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money) Do you know answer to some of these question ? If yes, post answer under comments section or If you have question related to Oracle Apps DBA, Oracle Fusion Middleware or Oracle Identity & Access Management then ask them in our Private Facebook Group

The post So you know enough in Oracle AppsDBA (EBS) R12.2 – Answer these ? Queries from our Day1 Apps DBA Training appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

Solution for OAM Error code OAM-02073 status fail is Excluded false

Thu, 2015-10-22 09:21
When you have performed all the configuration required to protect your web application with Oracle Access Manager, the next thing you do is test if the set up works. In this post, we will see a common problem most of us encounter on trying to test the setup for the first time. On accessing a protection resource of your web application, OAM WebGate intercepts the request and forwards it to the OAM server to determine if the resource needs an authenticated access. If yes, the OAM server redirects the user to login page. Here you enter the login credentials, click on Login and you get a blue Oracle System Error Page. At this stage, you go to OAM Server logs folder and check diagnostic logs which provide you information about why you would have got the error. Here I will mention the error that I got on submitting the credentials in one of the environments: oracle.security.am.proxy.oam.requesthandler.OAMProxyException: Event Response status is STATUS_FAIL for GET_AUTHN_SCHEME event. Error code OAM-02073 status fail isExcluded false         at oracle.security.am.proxy.oam.requesthandler.NGProvider.checkProtected (NGProvider.java:4542)         at oracle.security.am.proxy.oam.requesthandler.NGProvider.getIsRescProtectedResponse (NGProvider.java:1401)         at oracle.security.am.proxy.oam.requesthandler.NGProvider.getResponse (NGProvider.java:369)         at oracle.security.am.proxy.oam.requesthandler.RequestHandler.handleRequest (RequestHandler.java:366)         at oracle.security.am.proxy.oam.requesthandler.RequestHandler.handleMessage (RequestHandler.java:170)         at oracle.security.am.proxy.oam.requesthandler.ControllerMessageBean.getResponseMessage (ControllerMessageBean.java:122)         at oracle.security.am.proxy.oam.requesthandler.ControllerMessageBean_eo7ylc_MDOImpl. __WL_invoke (Unknown Source)         at weblogic.ejb.container.internal.MDOMethodInvoker.invoke(MDOMethodInvoker.java:35)         at oracle.security.am.proxy.oam.requesthandler.ControllerMessageBean_eo7ylc_MDOImpl. getResponse Message (Unknown Source)         at oracle.security.am.proxy.oam.mina.ObClientToProxyHandler.messageReceived (ObClientToProxyHandler.java:223)         at org.apache.mina.common.DefaultIoFilterChain$TailFilter.messageReceived (DefaultIoFilterChain.java:743)         at org.apache.mina.common.DefaultIoFilterChain.callNextMessageReceived (DefaultIoFilterChain.java:405)         at org.apache.mina.common.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:40)         at org.apache.mina.common.DefaultIoFilterChain$EntryImpl$1.messageReceived (DefaultIoFilterChain.java:823)         at org.apache.mina.common.IoFilterEvent.fire(IoFilterEvent.java:54)         at org.apache.mina.common.IoEvent.run(IoEvent.java:62)         at oracle.security.am.proxy.oam.mina.CommonJWorkImpl.run(CommonJWorkImpl.java:41)         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

OAM stores the web server host and port information in Host Identifiers configuration. You will get the above error message when the information provided in host identifiers is not correct. The host identifier entry need not be the same as the one you enter in the browser to access protected resource especially when you have multiple network interfaces on the web server machine. To get the exact host name that the OAM server expects, you can enable the OAM logs in Trace mode. It will give you the host name as well as the port number for which the error is logged. In order to fix this problem, you need to provide the correct host name and port number combination entry in Host Identifier for  the configured OAM Agent.

If you get this error from a non-browser based application such as a Java client application, you will need to make sure that you have correct entries in host identifier and resource string that you pass to oracle.security.am.asdk.ResourceRequest() object.

If you want to learn more issues like above or wish to discuss challenges you are hitting in Oracle Access Manager Implementation, register here for our Oracle Access Manager Training (next batch starts on 22nd Nov, 2015).

We are so confident on quality and value of our training that We provide 100% Money back guarantee so in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money.

Did you subscribe to our YouTube Channel (379 already subscribed) ?

The post Solution for OAM Error code OAM-02073 status fail is Excluded false appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

New Features in Oracle R 12.2.5 for Apps DBAs

Wed, 2015-10-21 10:20
This entry is part 5 of 6 in the series Oracle Apps 12.2

Apps12.2

This post on New Features in Oracle Apps 12.2.5 for Apps DBAs is coming from our Oracle Apps DBA Training (next batch starts on 31st October, 2015) where we cover Installation, Patching, Cloning, AutoConfig and other maintenance tasks. We also cover overview of Oracle E-Business Suite upgrade from 12.2.0 to 12.2.4 (and now 12.2.5) to show how to apply patches and new patch tool ADOP  in Oracle Apps.

Register early here for Oracle Apps DBA 12.2 Training to get discounted price (Limited Time Offer)

As you all know Oracle announced release of 12.2.5 last week and this seems to be the most awaited release in 12.2 series as there were many features which were includes. We are managing R12.2 since beginning for our customers and and witness the changes in Oracle Application.

From 11i to R12.1 to R12.2 major technology changes were there, We can say that R12.2.5 is one more steps closer towards Mobile/Cloud

First most visible feature for Business is Look & Feel. Oracle R12.2.5 has come up with Cloud/Icon based UI. Now you will see icons in the login screen which is more comfortable to view from Tablets and Mobiles.

For Apps DBA’s & DBAs side there are few excellent features which I want to highlight (more to follow in upcoming weeks):

1- dualfs option: Standard cloning was easy in R12.1 and when R12.2 was releases cloning was two steps (second step was almost repetitive)

In 12.2 (prior to 12.2.5)
Step1 -> Clone the Source run file system to target run file system
Step2 ->Clone the target run file system to target patch file system.

Now with dualfs option You can do both the above steps in one shot. Yes, Oracle reduced cloning efforts to almost 50% now. In one go both the file system will be configured.

2- Central Inventory: Believe me I am having the feeling that Oracle has started his own listener to Lister my pains. When you are hosting multiple Oracle R12.2 instances on the same server inventory is always need to considered and specially when you are running fs_clone. Now with the introduction of this feature we will be in a comfortable position.

<BASE_PATH>/oraInventory/oraInst.loc
3- ADOP – Maintainance and Validation:  I was wandering till now that why there is no dedicated utility to monitor the Online Pathing and now oracle has introduced one – adopmon. This can be used for
-Overall monitoring
-Individual Phase

Last time when I applied patch I missed to run fs_clone which was post patch application. Now when I ran prepare phase for the next cycle it went into error. We need to abort and cleanup and then redo the stuff again.

Now adop -validate will save us from all this and will let us know our instance is ready for the patching or not.
4- Weblogic oacore Performance enhancement: Overall if you have observed basic memory requirement or usage of R12.2 it is bit on the higher end compared to other versions. Specially managed server if you see it starts Java Messaging services, deployed EJB’s.
Also reported issue related to oacore that it takes long time and alos when you do startall script last one which get start and takes more time is oacore only.
So now oracle has addressed the performance side and did 2 enhancement

a)  Paramter -DserverType=wlx -> This is startup parameter for all the managed server and prevent startup of EJB, JMS,JCA services
b)  Context Variable s_deploy_portlet -> This prevent Portlet Producer libraries to get deployed in EBS domain.

Also default value of s_forms-c4wsstatus is set to Disable as earlier it was enabled.

5- ADOP UI : Someone well said “more information mean more confusion“. Keeping that in mind now ADOP UI has become more selective, to the point information, also more refined information from 12.2.5 onwards.

If you need to learn more on Oracle Apps DBA R12 (Architecture, Installation, WebLogic, Patching, Cloning and other maintenance tasks with the upgrade of Oracle E-Business Suite 12.2.0 to 12.2.4 (now 12.2.5) then have a look at our  Oracle Apps DBA Training (next batch starts on 31st October, 2015).

Note: We are so confident on our workshops that we provide 100% Money back guarantee, in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money (or ask us from our 100s of happy trainees in our private Facebook Group)

 

Looking to get more information or FREE tips on Oracle Administration then join our newsletter or for just specific to Oracle Apps DBA topics then click enter leave you name & email here

The post New Features in Oracle R 12.2.5 for Apps DBAs appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs

Oracle Apps (EBS) 12.2.5 is now available

Sun, 2015-10-18 00:19
This entry is part 1 of 6 in the series Oracle Apps 12.2

Screen Shot 2015-10-18 at 06.56.18

Oracle last week via press release announced general availability of Oracle Apps 12.2.5

Our Oracle pps DBA Training Team is busy evaluating 12.2.5 version (results so far suggests that 12.2.5 is going to make Apps DBA life easy, those of you working on 12.2.x can understand what I mean here) but till then you can check Steven Chan’s post (as usual one of the best Blog for Apps DBAs) or from Brian Kerr on EBS Support Blog

For some of our previous Oracle Apps 12.2 posts check changes in Oracle 12.2 or ADOP(new patching tool) or Installation of Oracle 12.2 on Linux

If you are on 12.2.x and wish to upgrade to 12.2.5 then check My Oracle Support Note 1983050.1 Oracle E-Business Suite Release 12.2.5 Readme

Looking for help or wish to share your experiences with other Apps DBA’s then Contact Us ?
You can join other Apps DBA’s at our private FaceBook Group or subscribe to our YouTube Channel (our Free Apps DBA school on YouTube Channel coming in Jan 2016)

 

Stay tuned for new features that matter to Oracle Apps DBA’s direct from our Apps DBA Training Experts (We not only teach Oracle Apps 12.2 but implement for our partners/customers)

 

The post Oracle Apps (EBS) 12.2.5 is now available appeared first on Oracle Trainings for Apps & Fusion DBA.

Categories: APPS Blogs