12.2.X Startup Sequence

12.2.X Startup Sequence

Below server are started in same sequence using adstrtall.sh in R12.2.x(12.2.4 at present) instances

-Fulfillment
-Oracle Process Manager (OPMN)
-OPMN managed Oracle HTTP Server (OHS) instance
-node manager
-listener process
-concurrent manager
-Admin server
-form server
-oafm server
-oacore server

Adop phase=cutover Errors With "ORA-20099: E-Business Suite Patch Edition Does Not Exist" When Database Is Not Active

Adop phase=cutover Errors With "ORA-20099: E-Business Suite Patch Edition Does Not Exist" When Database Is Not Active

Error:
The adop phase=cutover Errors when the patch edition is not active attempting to connect to the database:

appgnei1@pwerpl5211 erpapp]$ echo $TWO_TASK
gpsgnei1_patch
[appgnei1@pwerpl5211 erpapp]$ tnsping gpsgnei1_patch

TNS Ping Utility for Linux: Version 10.1.0.5.0 - Production on 19-DEC-2013 09:22:53

Copyright (c) 1997, 2003, Oracle. All rights reserved.

Used parameter files:
/gpsgnei1/erpapp/fs2/inst/apps/gpsgnei1_pwerpl5211/ora/10.1.2/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=pwerpl5211.cloud.test.com)(PORT=1523)) (CONNECT_DATA= (SERVICE_NAME=ebs_patch) (INSTANCE_NAME=gpsgnei1)))
OK (0 msec)
[appgnei1@pwerpl5211 erpapp]$ sqlplus /nolog

SQL*Plus: Release 10.1.0.5.0 - Production on Thu Dec 19 09:22:56 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.

SQL> conn apps/clo#1r2ud

ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-20099: E-Business Suite Patch Edition does not exist.
ORA-06512: at line 23

Cause:

The database patch edition was not active, where when attempting to connect to the database from the application-tier patch edition environment, it failed.

Solution:

This is the expected behavior.  If a database patch edition is not active, then attempting to connect to the database from the application-tier, the patch edition environment will fail.

The following also helps to find to which File System was connected when executed the environment from the fs1 file system:

[appltest@test ~]$ . /d01oracle/R122/EBSapps.env run
E-Business Suite Environment Information
----------------------------------------
RUN File System : /d01/oracle/R122/fs1/EBSapps/appl
PATCH File System : /d01/oracle/R122/fs2/EBSapps/appl
Non-Editioned File System : /d01/oracle/R122/fs_ne
DB Host: test.ora.com Service/SID: TEST
Sourcing the RUN File System ...
[appltest@test]$ sqlplus apps/<appspwd>
SQL*Plus: Release 10.1.0.5.0 - Production on Tue Oct 22 11:28:31 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select ad_zd.get_edition_type from dual;
GET_EDITION_TYPE
--------------------------------------------------------------------------------
RUN

Reference metalink Doc ID 1611655.1

How to Get The Patchset Level of Oracle Applications Products in R12

How to Get The Patchset Level of Oracle Applications Products in R12

Solution:

1.Log into OAM.

(Responsibility "Oracle Applications Manager", menu "OAM Support Cart")
and Navigate:

2.Support Cart --> Applications Signature --> Collect --> Check "Product Information" box
--> Click on "View" (eyeglasses)

This will display the following patchset information:

Application Name
Current Patch Level
Product Version
Status (Installed, Shared Product, Inactive)

3.The patchset level information can be retrieved directly from sqlplus with the following diagnostic script:

$AD_TOP/sql/adutconf.sql

Referene metalink Doc ID 550654.1

EGOEXTUPG.sql – Failed Worker On 12.1.1 Upgrade Patch U6678700.drv

EGOEXTUPG.sql – Failed Worker On 12.1.1 Upgrade Patch U6678700.drv

Error:
sqlplus -s APPS/***** @/u00/app/oracle/xxxx/apps/apps_st/appl/ego/12.0.0/patch/115/sql/EGOEXTUPG.sql &un_ego &pw_ego
Session altered.
DECLARE
*
ERROR at line 1:
ORA-00904: "REQUEST_ID": invalid identifier
ORA-06512: at line 326

Cause:

This error typically occurs for customers who do not use Product Information Management (PIM) module -- also known as
Product Lifecycle Management, Advanced Product Catalog, Engineering Online (EGO), or Product Data Hub.

Solution:

1) If you have not installed EGO product or if you are not using "Advanced Product Catalog" functionality, you can skip the failed job.

Notes:
- Use the following note in order to check if EGO product is not installed
Note 414470.1 (How To Determine the Product Lifecycle Management
(PLM) Patchset and Rollup Patch Version).

2) If you are using the PIM/EGO product and see this error, please raise a SR with support to investigate

Reference metalink Doc ID 1342266.1

Workflow Service Containers Will Not Start: oracle.jms.AQjmsException: JMS-120: Dequeue failed

Workflow Service Containers Will Not Start: oracle.jms.AQjmsException: JMS-120: Dequeue failed

Error:
The Workflow Service Container logs shows error:
oracle.jms.AQjmsException: JMS-120: Dequeue failed
at oracle.jms.AQjmsError.throwEx(AQjmsError.java:233)
at oracle.jms.AQjmsConsumer.dequeue(AQjmsConsumer.java:1424)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:692)
at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:629)
at oracle.apps.fnd.wf.bes.ControlListener.run(ControlListener.java:74)

Monitoring failed this iteration -> oracle.apps.fnd.cp.gsc.ProcessorException: Could not start automatic component -> oracle.apps.fnd.cp.gsc.server.GenericSvcComponentEOException: ORA-20002: 3825: Error '-24033 - ORA-24033: no recipients for message' encountered during execution of Rule function 'WF_RULE.ERROR_RULE' for event 'oracle.apps.fnd.cp.gsc.SvcComponent.start' with key 'SVC:15/JAN/2010'. FUNCTION_NAME=WF_EVENT_OJMSTEXT_QH.enqueue()

Cause:
The APPS user do not have the privilege to execute the SYS.DBMS_AQIN package.
The following error is thrown when run describe from the apps schema sys.dbms_aqin.
sqlplus apps/apps_pw
desc sys.dbms_aqin
ERROR:
ORA-04043: object sys.dbms_aqin does not exist

Solution:
1. Grant AQ_ADMINISTRATOR_ROLE to APPS which includes execute privilege on DBMS_AQIN.
sqlplus <apps_user>/<apps_pw> @$AD_TOP/patch/115/sql/adgrnaq.sql <system_pw> <apps_user> <apps_pw>
Example
sqlplus apps/apps @$AD_TOP/patch/115/sql/adgrnaq.sql manager apps apps
2. Confirm AQ_ADMINISTRATOR_ROLE is granted to APPS as BOTH ADMIN and DEFAULT.
This is the result for R12.1.  Some roles are not in 11.5.x. The APPS user need to always have the DEFAULT profile.  Do not revoke DEFAULT from the APPS User.

select * from DBA_ROLE_PRIVS where grantee='APPS';
GRANTEE GRANTED_ROLE ADM DEF
APPS RESOURCE NO YES
APPS CONNECT NO YES
APPS HR_REPORTING_USE YES YES
APPS CTXAPP NO YES
APPS OWS_STANDARD_ROLE NO YES
APPS WEBDB_DEVELOPER NO YES
APPS APPS_CONNECT NO YES
APPS JAVASYSPRIV NO YES
APPS HR_SECURE_USER YES YES
APPS AQ_ADMINISTRATOR_ROLE YES YES

3. Give the Default profile to the APPS user if it has been revoked.
alter user APPS default role ALL;
4. Shutdown and restart the Concurrent Manager.

11.5.x
cd $COMMON_TOP/admin/scripts/$CONTEXT_NAME

12.x
cd $ADMIN_SCRIPTS_HOME
sh adcmctl.sh stop apps/apps_pw
sh adcmctl.sh start apps/apps_pw

Reference metalink Doc ID 1050892.1

ORA-48913: Writing into trace file failed, file size limit [10485760] reached Shows In ALERT.LOG

ORA-48913: Writing into trace file failed, file size limit [10485760] reached Shows In ALERT.LOG 

Error:

Non critical error ORA-48913 caught while writing to trace file "/oraotcprd1/app/oracle/diag/rdbms/otcprd1/OTCPRD11/trace/OTCPRD11_ora_14925.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached

Cause:
Parameter MAX_DUMP_FILE_SIZE  is set too low

Solution:
Increase the setting for the parameter MAX_DUMP_FILE_SIZE or set it to unlimited

Note:

MAX_DUMP_FILE_SIZE specifies the maximum size of trace files (excluding the alert file). Change this limit if you are concerned that trace files may use too much space.

A numerical value for MAX_DUMP_FILE_SIZE specifies the maximum size in operating system blocks.

A number followed by a K or M suffix specifies the file size in kilobytes or megabytes.

The special value string UNLIMITED means that there is no upper limit on trace file size. Thus, dump files can be as large as the operating system permits.

Reference metalink Doc ID 1153040.1