EBS 12.2--New Home Page as Apps on IPAD

EBS 12.2 -- The new  Home Page

EBS 12.2 has a UI feature that looks so cool.
The Home page introduced in EBS 12.2 make you feel like you are in an Ipad application..

Here is how the home page looks after enabling the simplified home page in EBS 12.2:




Enable this feature as below:

Login to R12.2 Applications and set the below profile options:

 The "Self Service Personal Home Page Mode" profile must be set to
"Framework Simplified"
After setting this profile option , you can relogin and start the use this simplified Homepage.

EBS 12.2.5 released

EBS 12.2.5 released

Oracle announced EBS 12.2.5 on Oct 16 2015.

The new EBS 12.2.5 is delivered via a RUP patch 19676458 (Patch 12.2.5: ORACLE E-BUSINESS SUITE 12.2.5 RELEASE UPDATE PACK).
The root of the EBS 12.2.5 documentation is "Oracle E-Business Suite Product Specific Release Notes, Release 12.2.5 (Doc ID 2049015.1)"

The prerequisites of the patch 19676458 are R12.AD.C.delta.7 and R12.TXK.C.delta.7.
The upgrade process, in other words, applying the RUP patch 19676458 is explained in "Oracle E-Business Suite Release 12.2.5 Readme (Doc ID 1983050.1)" with all the details. So the document to follow for applying the 12.2.5 patch is 1983050.1.

Just like 12.2.4, applying 12.2.5 RUP patch with the downtime option is supported for the newly installed EBS 12.2 systems.
Lastly, it is important to mention that if you are on 12.2 you can directly upgrade to 12.2.5, but if you are on earlier releases like 11i or 12.0, you need to upgrade to release 12.2 first.

Hope EBS 12.2.5 most stable release as like 11.5.10.2 :)

ERROR: OPatch failed because of Path problem.Some commands below are not in your path: Command= fuser

Oracle Interim Patch Installer version 1.0.0.0.64
Copyright (c) 2011 Oracle Corporation. All Rights Reserved..

Oracle recommends you to use the latest OPatch version
and read the OPatch documentation available in the OPatch/docs
directory for usage. For information about the latest OPatch and
other support-related issues, refer to document ID 293369.1
available on My Oracle Support (https://myoraclesupport.oracle.com)

Oracle Home           : /apps/upgmgr/tech_st/10.1.2
Oracle Home Inventory : /apps/upgmgr/tech_st/10.1.2/inventory
Central Inventory     : /apps/upgmgr/inst/apps/NJVCUPG_oralnxaptst/admin/oraInventory
   from               : /apps/upgmgr/tech_st/10.1.2/oraInst.loc
OUI location          : /apps/upgmgr/tech_st/10.1.2/oui
OUI shared library    : /apps/upgmgr/tech_st/10.1.2/oui/lib/linux/liboraInstaller.so
Java location         : /apps/upgmgr/tech_st/10.1.2/jdk/jre/bin/java
Log file location     : /apps/upgmgr/tech_st/10.1.2/.patch_storage//*.log

Some commands below are not in your path:
  Command= fuser
  Extra Search Path= /sbin/fuser, /usr/sbin/fuser
  Path= /apps/upgmgr/inst/apps/NJVCUPG_oralnxaptst/admin/scripts:/apps/upgmgr/tech_st/10.1.3/perl/bin:/apps/upgmgr/tech_st/10.1.2/bin:/apps/upgmgr/apps_st/appl/fnd/12.0.0/bin:/apps/upgmgr/apps_st/appl/ad/12.0.0/bin:/apps/upgmgr/tech_st/10.1.3/appsutil/jdk/jre/bin::/apps/upgmgr/tech_st/10.1.2/bin:/usr/bin:/usr/sbin:/apps/upgmgr/tech_st/10.1.3/appsutil/jdk/jre/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/apps/upgmgr/bin:/apps/upgmgr/tech_st/10.1.2/OPatch:/apps/upgmgr/tech_st/10.1.3/appsutil/jdk/bin:/apps/upgmgr/tech_st/10.1.3/ant/bin:/apps/upgmgr/bin

ERROR: OPatch failed because of Path problem.

Solution:

I installed the psmisc package that includes the fuser program

Upgrading JDK To 7_45 - Step 3.7 Rebuild Forms Reports: Error: Collect2: Ld Returned 1 Exit Status

While Rebuild Forms and Reports Executables  Error libjvm.so: undefined reference to `pthread_cond_timedwait@GLIBC_2.3.2'

1) All required patches per Note 1467892.1 have been applied

Critical patch to be applied is 16271876 PROVIDE LIBJVM-STUB.SO FOR RELINKING OF FORMS WITH JDK 1.7

2)  Confirm the following reflects correct information:

$ $ADJVAPRG -version
$ echo $CLASSPATH
$ $AFJVAPRG -version
$ echo $AF_CLASSPATH

applmgr@xxxx:/u01/xxxx/applmgr/apps/tech_st/10.1.2/forms/lib>$ADJVAPRG -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)


applmgr@xxxx:/u01/xxx/applmgr/apps/tech_st/10.1.2/reports/lib>$AFJVAPRG -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)

3) Please create the below softlink:

cd $ORACLE_HOME/lib/stubs
ln -s libjvm-1.7-stub.so libjvm.so

Retry the make command.

(Doc ID 1569998.1)

OID start and Stop Locations

To start DB, follow the steps in the order given below:

1. Set the environment variables (if they are not already set) by executing the below commands:
    a. export ORACLE_HOME = /app/oracle/product/11.2.0/dbhome_1. Path of the base directory of database
    b. export PATH = /app/oracle/product/11.2.0/dbhome_1/bin: $PATH.  The bin  directory of ORACLE_HOME
    c. export LD_LIBRARY_PATH=/app/oracle/product/11.2.0/dbhome_1/lib. The lib folder of ORACLE_HOME
    d. export ORACLE_SID=orcl. Database SID
PS: All these variables can be permanently set in the session by writing these commands to ".profile" file of the unix user.
2. Start the database listener by executing the below command:
    a. lsnrctl start
    b.startup

OID Services Start Location:

Steps to Start OID using OPMN

1. Set the environment variables required to start OID by executing the below commands:

    a. export ORACLE_HOME=/home/oracle/Oracle/Middleware/Oracle_IDM1. Path of the base directory of Oracle Internet Directory

    b. export ORACLE_INSTANCE=/home/oracle/Oracle/Middleware/asinst_1. Path of the instance directory created while installation
    c. export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_INSTANCE/bin:$PATH. 
    d. export TNS_ADMIN=$ORACLE_INSTANCE/config
PS: Make sure the first directory of PATH variable is always bin directory of ORACLE_HOME as defined above. You might get errors while executing ldap commands if this is not maintained.
2. Start OID by executing
    a. opmnctl startall
You can check the status of OID by executing opmnctl status to verify if the status is Alive i.e., if OID is started.
3.Stop OID by executing
opmnctl stopall

Example:

[oemora@lnxdbtst > /apps/oemora]$ export ORACLE_HOME=/apps/oemora/Oracle/Middleware/Oracle_IDM1
[oemora@lnxdbtst > /apps/oemora]$ export ORACLE_INSTANCE=/apps/oemora/Oracle/Middleware/asinst_1
[oemora@lnxdbtst > /apps/oemora]$ export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_INSTANCE/bin:$PATH
[oemora@lnxdbtst > /apps/oemora]$ export TNS_ADMIN=$ORACLE_INSTANCE/config
[oemora@lnxdbtst > /apps/oemora]$ cd $ORACLE_INSTANCE
[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1]$ ls
auditlogs  bin  config  diagnostics  EMAGENT  OHS  OID  OVD  tmp
[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1]$ cd bin
[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1/bin]$ ls
opmnctl
[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1/bin]$ opmnctl status

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
ohs1                             | OHS                |   31898 | Alive
ovd1                             | OVD                |   31897 | Alive
oid1                             | oidldapd           |   32217 | Alive
oid1                             | oidldapd           |   32245 | Alive
oid1                             | oidmon             |   31896 | Alive
EMAGENT                          | EMAGENT            |   31895 | Alive


[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1/bin]$

Steps to start Web logic Admin and Managed Server

1. To start Weblogic Admin Server, Navigate to /bin directory and execute:

    a. ./startWeblogic

2. To start Managed Server, Navigate to /bin directory and execute:

   a. ./startManagedWeblogic

[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/user_projects/domains/base_domain/bin]$ ls -ltr

total 68

drwxr-x--- 2 oemora oemora  4096 Jul 21 16:25 service_migration

drwxr-x--- 2 oemora oemora  4096 Jul 21 16:25 server_migration

drwxr-x--- 2 oemora oemora  4096 Jul 21 16:25 nodemanager

-rwxr-x--- 1 oemora oemora  1979 Jul 21 16:25 stopWebLogic.sh

-rwxr-x--- 1 oemora oemora  5697 Jul 21 16:25 startWebLogic.sh

-rwxr-x--- 1 oemora oemora  2415 Jul 21 16:25 stopManagedWebLogic.sh

-rwxr-x--- 1 oemora oemora  3203 Jul 21 16:25 startManagedWebLogic.sh

-rwxr-x--- 1 oemora oemora 16132 Jul 21 16:25 setDomainEnv.sh

-rw------- 1 oemora oemora 20100 Oct 20 06:18 nohup.out

Troubleshooting the Discovery of Targets in OEM12c

Troubleshooting the Discovery of Targets in OEM12c

 Please enable perl trace to debug mode and then after discovery please send perl log file to OracleSupport for further observation.

1. Go to /agent_inst/sysman/config
2. Open emd.properties file and
3. Change this line EMAGENT_PERL_TRACE_LEVEL=INFO to EMAGENT_PERL_TRACE_LEVEL=DEBUG
4. Restart agent
5. Run discovery again and send us /agent_inst/sysman/log/emagent_perl.trc file.

APEX Listener configuration on standalone Mode.

Download the Apex listner (2.0) and unzip.

unzip apex_listener.2.0.0.354.17.05.zip

Create Images:

[apexxxx@xxxx /apps/apexxxx/apex_listener]$ /apps/apexxx/java/jdk1.7.0_10/bin/java -jar apex.war static /apps/apexxx/APEX/apex_sw/apex/images
WAR Generation complete
 WAR location     : /apps/apexxx/apex_listener/i.war
 Context path     : /i
 Static resources : /apps/apexxx/APEX/apex_sw/apex/images

Once images created.

Run Stand alone Script:

/apps/apexxxx/java/jdk1.7.0_10/bin/java -jar apex.war standalone --port 8090 --apex-images /apex/apexxx/APEX/apex_sw/apex/images

Aug 07, 2015 11:27:34 AM oracle.dbtools.common.config.file.ConfigurationFolder logConfigFolder

INFO: Using configuration folder: /apps/apexxxx/apex_lsnr/apex

Aug 07, 2015 11:27:35 AM oracle.dbtools.standalone.Standalone execute

INFO: NOTE:

Standalone mode is designed for use in development and test environments. It is not supported for use in production environments.

Aug 07, 2015 11:27:35 AM oracle.dbtools.standalone.Standalone execute

INFO: Starting standalone Web Container in:  /apps/apexmgr/apex_lsnr/apex

Aug 07, 2015 11:27:35 AM oracle.dbtools.standalone.Deployer deploy

INFO: Will deploy application path = /apps/apexxx/apex_lsnr/apex/apex/WEB-INF/web.xml

Aug 07, 2015 11:27:35 AM oracle.dbtools.standalone.Deployer deploy

INFO: Deployed application path = /apps/apexxxr/apex_lsnr/apex/apex/WEB-INF/web.xml

Aug 07, 2015 11:27:35 AM oracle.dbtools.common.config.file.ConfigurationFolder logConfigFolder

INFO: Using configuration folder: /apps/apexxxx/apex_lsnr/apex

Configuration properties for: apex

cache.caching=false

cache.directory=/tmp/apex/cache

cache.duration=days

cache.expiration=7

cache.maxEntries=500

cache.monitorInterval=60

cache.procedureNameList=

cache.type=lru

db.hostname=xxxxerp.xxxx.com

db.password=******

db.port=1525

db.sid=XXXX

debug.debugger=false

debug.printDebugToScreen=false

error.keepErrorMessages=true

error.maxEntries=50

jdbc.DriverType=thin

jdbc.InactivityTimeout=1800

jdbc.InitialLimit=3

jdbc.MaxConnectionReuseCount=1000

jdbc.MaxLimit=10

jdbc.MaxStatementsLimit=10

jdbc.MinLimit=1

jdbc.statementTimeout=900

log.logging=false

log.maxEntries=50

misc.compress=

misc.defaultPage=apex

security.disableDefaultExclusionList=false

security.maxEntries=2000

db.username=APEX_PUBLIC_USER

Using JDBC driver: Oracle JDBC driver version: 11.2.0.3.0

Aug 07, 2015 11:27:37 AM oracle.dbtools.rt.web.SCListener contextInitialized

INFO: Oracle Application Express Listener initialized

Application Express Listener version : 2.0.0.354.17.06

Application Express Listener server info: Grizzly/1.9.49

Aug 07, 2015 11:27:37 AM com.sun.grizzly.Controller logVersion

INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 8/7/15 11:27 AM

Aug 07, 2015 11:27:37 AM oracle.dbtools.standalone.Standalone execute

INFO: http://localhost:8090/apex started.