Tuesday, July 31, 2012

Workflow Mailer Config/Status


Workflow Mailer Config/Status

 
Do the query below to get the config of the workflow mailer:
set linesize 130;
col value for a30;
select p.parameter_id,p.parameter_name,v.parameter_value value
from fnd_svc_comp_param_vals_v v,
fnd_svc_comp_params_b p,
fnd_svc_components c
where c.component_type = 'WF_MAILER'
and v.component_id = c.component_id
and v.parameter_id = p.parameter_id
and p.parameter_name in
('OUTBOUND_SERVER', 'INBOUND_SERVER','ACCOUNT', 'FROM', 'NODENAME', 'REPLYTO','DISCARD' ,'PROCESS','INBOX')
order by p.parameter_name;
SQL> /
PARAMETER_ID PARAMETER_NAME VALUE
------------ -------------- ------------------------------
10018 ACCOUNT workflow
10026 DISCARD DISCARD
10029 FROM Workflow Mailer
10033 INBOUND_SERVER 10.0.0.249
10034 INBOX INBOX
10037 NODENAME WFMAIL
10043 OUTBOUND_SERVER mailsrv.home.co.za
10044 PROCESS PROCESS
10053 REPLYTO workflow@home.co.za
9 rows selected.
SQL>

Display the status of all the listeners and agents:
SQL>
set pages 44;
set linesize 130;
select COMPONENT_NAME,COMPONENT_STATUS from fnd_svc_components;
COMPONENT_NAME COMPONENT_STATUS
--------------- ------------------------------
ECX Inbound Agent Listener STOPPED
ECX Transaction Agent Listener STOPPED
Workflow Deferred Agent Listener RUNNING
Workflow Deferred Notification Agent Listener RUNNING
Workflow Error Agent Listener RUNNING
Workflow Inbound Notifications Agent Listener RUNNING
Workflow Notification Mailer RUNNING
WF_JMS_IN Listener(M4U) RUNNING
Web Services OUT Agent STOPPED
Web Services IN Agent STOPPED
Workflow Java Deferred Agent Listener RUNNING
Workflow Java Error Agent Listener RUNNING
Workflow Inbound JMS Agent Listener STOPPED
13 rows selected.
SQL>
To check WF mail status
col mail_status for a12;
select count(*), mail_status
from wf_notifications
where begin_date > sysdate - 1
group by mail_status;
COUNT(*) MAIL_STATUS
---------- ------------
91 FAILED
218
3 MAIL
2 ERROR
471 SENT
SQL>

Check the status of Agent Listeners:
set pagesize 400
set linesize 120
set pagesize 50
column COMPONENT_NAME format a45
column STARTUP_MODE format a15
column COMPONENT_STATUS format a15
select fsc.COMPONENT_NAME,fsc.STARTUP_MODE,fsc.COMPONENT_STATUS
from APPS.FND_CONCURRENT_QUEUES_VL fcq, fnd_svc_components fsc
where fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)
order by COMPONENT_STATUS , STARTUP_MODE , COMPONENT_NAME;
COMPONENT_NAME STARTUP_MODE COMPONENT_STATU
--------------------------------------------- --------------- ---------------
WF_JMS_IN Listener(M4U) AUTOMATIC RUNNING
Workflow Deferred Agent Listener AUTOMATIC RUNNING
Workflow Deferred Notification Agent Listener AUTOMATIC RUNNING
Workflow Error Agent Listener AUTOMATIC RUNNING
Workflow Inbound Notifications Agent Listener AUTOMATIC RUNNING
Workflow Java Deferred Agent Listener AUTOMATIC RUNNING
Workflow Java Error Agent Listener AUTOMATIC RUNNING
Workflow Notification Mailer AUTOMATIC RUNNING
ECX Inbound Agent Listener MANUAL STOPPED
ECX Transaction Agent Listener MANUAL STOPPED
Web Services IN Agent MANUAL STOPPED
Web Services OUT Agent MANUAL STOPPED
Workflow Inbound JMS Agent Listener MANUAL STOPPED
13 rows selected.
SQL>
Status of the JAVA Workflow Mailer:
SQL> SELECT COMPONENT_STATUS from APPS.FND_SVC_COMPONENTS where COMPONENT_ID=10006;
COMPONENT_STATUS
------------------------------
DEACTIVATED_SYSTEM
SQL> /
COMPONENT_STATUS
------------------------------
STARTING
SQL> /
COMPONENT_STATUS
------------------------------
RUNNING
SQL>
Show inbound,reply and account information:
set pagesize 100
set linesize 132
set feedback off
set verify off
col value format a35
col component_name format a30
select c.component_id, c.component_name, p.parameter_id, p.parameter_name, v.parameter_value value
from fnd_svc_comp_param_vals_v v, fnd_svc_comp_params_b p, fnd_svc_components c
where c.component_type = 'WF_MAILER'
and v.component_id = c.component_id
and v.parameter_id = p.parameter_id
and p.parameter_name in ( 'INBOUND_SERVER','ACCOUNT', 'REPLYTO')
order by c.component_id, c.component_name,p.parameter_name;
COMPONENT_ID COMPONENT_NAME                 PARAMETER_ID         PARAMETER_NAME VALUE
------------ ------------------------------ ------------         --------------------------
10006        Workflow Notification Mailer   10018 ACCOUNT        workflow
10006        Workflow Notification Mailer   10033 INBOUND_SERVER 10.130.10.76
10006        Workflow Notification Mailer   10053 REPLYTO        workflow@customer.co.za

Workflow Mailer Config
set wrap on
set linesize 130;
col parameter_name format a30 head "Parameter Name"
col parameter_value format a50 head "Value"
SELECT
c.parameter_name,
a.parameter_value
FROM fnd_svc_comp_param_vals a,
fnd_svc_components b,
fnd_svc_comp_params_b c
WHERE b.component_id = a.component_id
AND b.component_type = c.component_type
AND c.parameter_id = a.parameter_id
AND c.encrypted_flag = 'N'
AND b.component_name = 'Workflow Notification Mailer'
ORDER BY c.parameter_name;

PARAMETER_NAMEPARAMETER_VALUE
ACCOUNTworkflow
ALLOW_FORWARDED_RESPONSEY
ALTERNATE_EMAIL_PARSERoracle.apps.fnd.wf.mailer.DirectEmailParser
ATTACHED_URLSWFMAIL:ATTACHED_URLS
ATTACH_IMAGESY
ATTACH_STYLESHEETY
AUTOCLOSE_FYIY
CANCELEDWFMAIL:CANCELED
CLOSEDWFMAIL:CLOSED
COMPONENT_LOG_LEVEL3
DEBUG_MAIL_SESSIONN
DIRECT_RESPONSEN
DISCARDDISCARD
EMAIL_PARSERoracle.apps.fnd.wf.mailer.TemplatedEmailParser
ENABLE_STYLESHEETN
EXPUNGE_ON_CLOSEY
FRAMEWORK_APP1
FRAMEWORK_RESP20420
FRAMEWORK_URL_TIMEOUT30
FRAMEWORK_USER0
FROMWorkflow Mailer
HTMLAGENThttp://ebs.home.co.za:80/
HTML_DELIMITERDEFAULT
HTTP_USER_AGENTMozilla/4.76
INBOUND_CONNECTION_TIMEOUT120
INBOUND_FETCH_SIZE100
INBOUND_MAX_IGNORE_SIZE1000
INBOUND_MAX_LOOKUP_CACHE_SIZE100
INBOUND_MAX_RET_EMAIL_SIZE100
INBOUND_PROTOCOLIMAP
INBOUND_SERVER10.0.10.76
INBOUND_SSL_ENABLEDN
INBOUND_UNSOLICITED_THRESHOLD2
INBOXINBOX
INLINE_ATTACHMENTN
MAILER_SSL_TRUSTSTORENONE
MAX_INVALID_ADDR_LIST_SIZE100
MESSAGE_FORMATTERoracle.apps.fnd.wf.mailer.NotificationFormatter
MORE_INFO_ANSWEREDWFMAIL:MORE_INFO_ANSWERED
NODENAMEWFMAIL
OPEN_INVALIDWFMAIL:OPEN_INVALID
OPEN_INVALID_MORE_INFOWFMAIL:OPEN_INVALID_MORE_INFO
OPEN_MAILWFMAIL:OPEN_MAIL
OPEN_MAIL_DIRECTWFMAIL:OPEN_MAIL_DIRECT
OPEN_MAIL_FYIWFMAIL:OPEN_MAIL_FYI
OPEN_MORE_INFOWFMAIL:OPEN_MORE_INFO
OUTBOUND_CONNECTION_TIMEOUT120
OUTBOUND_PROTOCOLSMTP
OUTBOUND_SERVERoraclerh5pw7.home.co.za
OUTBOUND_SSL_ENABLEDN
OUTBOUND_USERchangeOnJavaMailerInstall
PROCESSPROCESS
PROCESSOR_DEFER_EVTDATA_READY
PROCESSOR_ERROR_LOOP_SLEEP60
PROCESSOR_IN_THREAD_COUNT1
PROCESSOR_LOOP_SLEEP5
PROCESSOR_MAX_ERROR_COUNT10
PROCESSOR_MAX_LOOP_SLEEP60
PROCESSOR_OUT_THREAD_COUNT1
PROCESSOR_READ_TIMEOUT10
PROCESSOR_READ_TIMEOUT_CLOSEY
REPLYTOworkflow@home.co.za
RESET_NLSN
SEND_ACCESS_KEYN
SEND_CANCELED_EMAILY
SEND_UNSOLICITED_WARNINGY
SUMHTMLWFMAIL:SUMHTML
SUMMARYWFMAIL:SUMMARY
TEST_ADDRESSNONE
WARNINGWFMAIL:WARNING


Cash Positioning Issue in 11i Instance


Hi All.

When attempting to Cash Positioning: Existing worksheet go button
the following error occurs an error:
oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122



Step to reproduce:
Go to CM responsibility --> Cash positioning



Press "Go" button

Got the following error: You have encountered an unexpected error. Please contact the System Administrator for assistance

After changing FND: Diagnostics profile to YES, I can see the full error:
 oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation.  Statement: SELECT * FROM (SELECT WorksheetHeadersEO.WORKSHEET_HEADER_ID, 
WorksheetHeadersEO.WORKSHEET_NAME,
WorksheetHeadersEO.COLUMNS_DISPLAYED,
WorksheetHeadersEO.CREATED_BY,
decode(WorksheetHeadersEO.CREATED_BY,
1, 'DeleteDisabled',
'DeleteEnabled') DELETE_SWITCHER,
decode(WorksheetHeadersEO.CREATED_BY,
1, 'UpdateDisabled',
'UpdateEnabled') UPDATE_SWITCHER
FROM CE_CP_WORKSHEET_HEADERS WorksheetHeadersEO) QRSLT  WHERE (EXISTS (SELECT 1 FROM ((SELECT 1 FROM CE_CP_WS_BA_V WBA WHERE WBA.worksheet_header_id = QRSLT.worksheet_header_id AND WBA.xtr_user_flag = 'N')UNION ALL (SELECT 1 FROM CE_CP_WORKSHEET_LINES WL WHERE WL.CASHPOOL_ID IS NOT NULL)))) ORDER BY WORKSHEET_NAME
at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:891)
at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:865)
at oracle.apps.fnd.framework.OAException.wrapperInvocationTargetException(OAException.java:988)
at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:211)
at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:153)
at oracle.apps.fnd.framework.server.OAApplicationModuleImpl.invokeMethod(OAApplicationModuleImpl.java:750)
at oracle.apps.ce.cashpositions.webui.WorksheetSearchCO.processFormRequest(WorksheetSearchCO.java:130)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:810)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:363)
at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processFormRequest(OAPageLayoutHelper.java:1159)
at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processFormRequest(OAPageLayoutBean.java:1579)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1022)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:988)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:843)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:363)
at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processFormRequest(OAFormBean.java:395)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1022)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:988)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:843)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:363)
at oracle.apps.fnd.framework.webui.beans.OABodyBean.processFormRequest(OABodyBean.java:363)
at oracle.apps.fnd.framework.webui.OAPageBean.processFormRequest(OAPageBean.java:2700)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1707)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:511)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:432)
at _oa__html._OA._jspService(_OA.java:84)
at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)
at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417)
at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267)
at oracle.jsp.JspServlet.internalService(JspServlet.java:186)
at oracle.jsp.JspServlet.service(JspServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)
at org.apache.jserv.JServConnection.run(JServConnection.java:294)
at java.lang.Thread.run(Thread.java:662)
## Detail 0 ##
java.sql.SQLException: ORA-00904: "QRSLT"."WORKSHEET_HEADER_ID": invalid identifier

Action plan:
1.  Please download and review the readme for Patch 4715697 .
2. Please apply Patch 4715697 in a TEST environment.
3. Please confirm the following file versions:
ce java/cashpositions/server WorksheetSummaryVOImpl.java 115.7
4. Restart apache server and clear the apache cash
5. Please retest the issue.

Good luck ...

Friday, July 20, 2012

How to Enable Automatic Compilation of JSP pages in R12 Environment



How to Enable Automatic Compilation of JSP pages in R12 Environment [ID 458338.1]

 Modified 10-NOV-2011     Type HOWTO     Status PUBLISHED 

In this Document
  Goal
  Solution
  References

Applies to:

Oracle Applications Technology Stack - Version: 12.0.6 to 12.1.3 - Release: 12.0 to 12.1
Oracle Applications Technology Stack - Version: 12.0.6 to 12.1.3   [Release: 12.0 to 12.1]
Information in this document applies to any platform.

Goal

***Checked for relevance on 12-MAY-2010***

In Release 11i, the deployment of a (custom) JSP was done as follows:
  1. Copy the file (for example: custom.jsp) to the web tier in the $OA_HTML directory. 
  2. Request it in the browser like URL> http://:/OA_HTML/custom.jsp.
The result on the web tier is that:
  • The custom.jsp was compiled 
  • Output files of the compilation _custom.class (and _custom.java) are saved under the _pages directory 
  • The custom.jsp page is shown in the browser 
Performing the same steps in Release 12 environment just shows a blank screen and no compilation of the custom.jsp is done. The steps in this Note explain how the same behavior as in Release 11i can be achieved in Release 12.

Solution

In Release 12 the (automatic) compilation of a JSP is disabled and, at runtime, only the pre-compiled JSP's are picked up. Since this requires fewer checks to be done, the performance is improved and therefore this is the recommended and default setting for a Production environment where JSP's will only be replaced occasionally.

In cases where development activities are done and JSP pages are changing often this default setting makes things more complicated. Each time a JSP is deployed a manual compilation using the ojspCompile.pl is needed and the OC4J running the oacore needs a restart to pick up the changes. This will also affect other people working on the same environment. 

Follow the steps below to:
  • Automatically have the JSP recompiled when the JSP is changed (at least the time stamp)
  • See the new JSP without the need to restart the OC4J running oacore
The objective is to change the setting for main_mode from justrun to recompile in 
$INST_TOP /ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml 
This can be achieved by performing the following:
  • Login into E-Business suite and select System Administrator responsibility
  • Select function AutoConfig (under Oracle Applications Manager) (*)
  • For each web tier server perform the following:
    • Click on pencil icon under Edit Parameters
    • Select tab System
    • Expand section jtff_server
    • Change value for the entry s_jsp_main_mode from justrun to recompile
    • Confirm the change by clicking Save button
  • Run AutoConfig to propagate the changes to the configuration files
  • Verify that the $INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml  has the following:
      
         main_mode
         recompile
      
  • Restart the web tier services
  • Request a JSP in the browser which is compiled. See that a new _.class is created in _pages
  • Make a change in the JSP file
  • Request it again in the browser. See that _.class is 'refreshed' in _pages and the change is seen in the browser



(*) If the Autoconfig function is not available it can also be accessed by selecting other function for Oracle Application Manager and then select Site Map > System Confiration - Autoconfig. Also the Autoconfig function can be added to the menu as follows:
  • Log in as System Administrator and select System Administrator
  • Application>Menu
  • Put the system into query\
  • In Menu enter OAM_ADMIN_MENU
  • Run the query: This should return Oracle Applications Manager Administrator menu
  • Add new line
  • Enter Prompt = Autoconfig + Function select OAM_AD_CONFIG_FILES_TABLE and ensure Grant is ticked
  • Save
  • After recompilation (and possibly bounce) the new function will be available to be used in the future

References

Oracle E-Business Suite Support on x86-64



Oracle E-Business Suite Support on x86-64

Questions addressed in this document

What is x86-64?
What operating systems are supported on x86-64?
Is Oracle E-Business Suite supported on x86-64?
What are the benefits of running Oracle E-Business Suite on x86-64?
How do I install Oracle E-Business Suite database on x86-64?
Why are there two installation packages for E-Business Suite Release 12 for Linux?
How do I migrate an existing Oracle E-Business Suite database to x86-64?
Is RAC supported with the database tier on x86-64?
Is cloning supported on an E-Business Suite system with an x86-64 database?
How do I clone the database on platforms that do not support Rapid Clone?
Are there separate patches for Oracle E-Business Suite on x86-64?
Questions and Answers

What is x86-64?
Answer:
x86-64 (also called x64) refers to both AMD Opteron (AMD64) and Intel Extended Memory (EM64T) processors. AMD64 and EM64T are x86-compatible chip sets with 64-bit extensions. x86-64 based servers can run either a 32-bit or a 64-bit operating system.

Refer to the Intel web site for more information on EM64T and to to the AMD web site for more information on AMD64.

[top]



What operating systems are supported on x86-64?
Answer:
Apple Macintosh, Linux, Microsoft Windows, Solaris and other operating systems are supported on x86-64. Each combination of an operating system and chip architecture is refered to as a platform. Not all these platforms are certified with Oracle E-Business Suite.

[top]



Is Oracle E-Business Suite supported on x86-64?
Answer:
The answer has three parts:

1. 32-bit Operating Systems for Oracle E-Business Suite Release 12 and 11i:
When Linux or Windows 32-bit operating systems are installed, x86-64 servers can be used for Oracle E-Business Suite application and database tiers; "Linux x86" and "Windows 32-bit" platform certification criteria apply. The following 32-bit operating systems are supported:

Microsoft Windows Server
Oracle Linux
Red Hat Enterprise Linux
SUSE Linux Enterprise Server
2. Some 64-bit platforms for Oracle E-Business Suite Release 12: the following 64-bit operating systems are supported for both application and database tiers on x86-64 servers:

Oracle Linux
Red Hat Enterprise Linux
SUSE Linux Enterprise Server
Microsoft Windows Server x64 (2008 R2 only)
3. Remaining 64-bit platforms for Release 12 and all 64-bit platforms for Release 11i : when Oracle E-Business Suite Release 11i or 12 application tier is installed on a certified platform, additional platforms may be used for a 64-bit database tier on x86-64 servers. This is an example of a mixed platform architecture. In Release 11i this was known as Split Configuration.

The following 64-bit operating systems are supported on x86-64 servers for E-Business Suite database tier only:

Microsoft Windows Server x64
Oracle Linux
Red Hat Enterprise Linux
SUSE Linux Enterprise Server
Oracle Solaris on x86-64
For up-to-date information on mixed platform architecture, refer to "Database Tier Only " in Certify -> "View Certifications by Platform", choose "Database Tier Only " in the platform list.


See Certifications on My Oracle Support for more information on certified platforms and specific software versions.

[top]



What are the benefits of running Oracle E-Business Suite on x86-64?
Answer:
When a 32-bit OS is installed on x86-64, the maximum 64GB of main memory (using Physical Address Extension or PAE) provides scalability and stability advantages over x86 (32-bit) processor systems, which are limited to 4GB. The use of OS features such as PAE or the hugemem kernel to increase memory available to a 32-bit operating system should have no effect on the Oracle E-Business Suite and is supported.

Each process is still limited to a 32-bit memory space (4GB for Linux, and up to 3GB for Windows) when running a 32-bit OS on x86-64 processor systems.

When a 64-bit OS is installed on x86-64, the limits on physical and process memory significantly exceed today's manufacturing capabilities.

When larger amounts (higher than 16GB) of memory are installed, running a 64-bit Linux OS is more stable than running a 32-bit Linux OS.

[top]



How do I install Oracle E-Business Suite database on x86-64?
Answer:
For new installations of Oracle E-Business Suite Release 12 on supported 64-bit Linux operating systems, you can use Rapid Install as directed in "Oracle Applications Installation Guide: Using Rapid Install" to install the database and application tiers.

For Database Tier Only platforms in a mixed platform architecture, you can use Rapid Install as directed in "Oracle Applications Installation Guide: Using Rapid Install" to install the database and application tiers on supported platforms, and then migrate the database tier to a certified 64-bit operating system (see references).

[top]



Why are there two installation packages for E-Business Suite Release 12 for Linux?
Answer:
The Oracle E-Business Suite Applications Release 12.0 Media Pack for Linux x86 is used to install on x86 or x86-64 servers with a supported 32-bit Linux operating system. The Oracle E-Business Suite Applications Release 12.0 Media Pack for Linux x86-64-bit is used to install on x86-64 servers with a supported 64-bit operating system. For the Installation and Upgrade Notes specific to each installation package, refer to the documentation in the references

[top]



How do I migrate an existing Oracle E-Business Suite database to x86-64?
Answer:
To migrate the database to a certified operating system on x86-64, refer to the documentation in the references.

[top]



Is RAC supported with the database tier on x86-64?
Answer:

Yes, it is. RAC certifications are generic and apply to all platforms unless otherwise specified.

Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12 (My Oracle Support Note 388577.1) contains Oracle E-Business Suite Release 12 with RAC implementation details.

A list of the supported Release 11i versions with RAC is available in Oracle E-Business Suite 11i and Database FAQ (My Oracle Support Note 285267.1). In addition, the following documents contain Oracle E-Business Suite 11i with RAC implementation details:

Oracle E-Business Suite Release 11i with 9i RAC; Installation & Configuration Using AutoConfig (My Oracle Support Note 279956.1)
Configuring Oracle Applications Release 11i with 10g Real Application Clusters and Automatic Storage Management (My Oracle Support Note 312731.1)
If you use parallel concurrent processing (PCP) with Oracle E-Business Suite 11i, we recommend applying ATG Family Pack 11i.ATG_PF.H RUP3 or higher (patch 4334965).

The use of RAC on Solaris 10 Containers (a feature that allows partitioning of an OS into separate virtual hosts) is restricted to global (non-local) containers - please see My Oracle Support Note 317257.1 for the best practices document for deploying Oracle databases in Solaris 10 Containers.

[top]



Is cloning supported on an E-Business Suite system with an x86-64 database?
Answer:

Yes, it is. For Oracle E-Business Suite systems with database tiers on 64-bit operating systems, use Rapid Clone.

More information about Rapid Clone is available in the references.



How do I clone the database on platforms that do not support Rapid Clone?
Answer:

Cloning the E-Business Suite database tier using the Oracle database utilities is a process of cloning the database Oracle home and creating a duplicate database.

To clone the database Oracle home, use the Oracle Universal Installer (OUI). This process allows you to configure inventory information for the new target Oracle home. See the Oracle Universal Installer and OPatch User's Guide, 10g Release 2 for additional information.

To create a duplicate database, use Recovery Manager (RMAN). See the Oracle Database Backup and Recovery Advanced User's Guide, 10g Release 2 for additional information.



Are there separate patches for Oracle E-Business Suite on x86-64 with a 64-bit OS?
Answer:

There are really two answers to this quesiton - for the Database Tier, the answer is yes. Since we bundle the 64-bit Database for use on 64-bit OS'es, the database tier's patches may indeed differ for the 64-bit distribution vs the 32-bit.

On the application tier, the answer is no. Users should apply 32-bit patches for components on the application tier (E-Business Suite applications, Fusion Middleware components, 3rd party patches) since there is not a separate 64-bit distribution generally for E-Business Suite.


Cloning Oracle Application 11i /R12 with Rapid Clone - Database (9i/10g/11g) Using Hot Backup on Open Database


You need to follow the "pre-requisite" and "preparation" steps from section 1 and 2 of the cloning note applicable to your EBS Version:

Release 11i  : Note 230672.1 - 'Cloning Oracle Applications Release 11i with Rapid Clone'
Release 12  : Note 406982.1 - 'Cloning Oracle Applications Release 12 with Rapid Clone'


This Note helps you to implement the steps mentioned in "Appendix B: Recreating database control files manually in Rapid Clone" as per above Clone Note.

Step 1: Ensure adpreclone.pl has been run

Step 2: Obtain a trace file script to recreate the controlfile. On the source database issue the following
            command:

SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;


The trace file script will be put into the user_dump_dest directory. The name of the trace file script will be something like PROD_ora_12345.trc.
Compare the date and time of the new trace file script to the time in which you entered the ALTER DATABASE BACKUP CONTROLFILE TO TRACE command.
This will ensure you will be using the most recent trace file script, the one you created in this step


Step 3: In the create controlfile script just created in step 2 change:
CREATE CONTROLFILE REUSE DATABASE "PROD" NORESETLOGS

to:

CREATE CONTROLFILE DATABASE "PROD" RESETLOGS ARCHIVELOG
If you want to change the Database Name , You need to use the clause SET DATABASE in the create control file script as follows:
CREATE CONTROLFILE SET DATABASE "newdbname" RESETLOGS NOARCHIVELOG
You must specify RESETLOGS.

The ARCHIVELOG mode may be changed to NOARCHIVELOG if you wish to run the copied database in noarchive log mode. Change all directories in the create controlfile clause to point to the correct directories for the new target database, if necessary.

Leave "only" the CREATE CONTROLFILE clause. The other statements, like the recover command, will be done manually. Be sure you also remove the STARTUP NOMOUNT command.
Note:  Please ensure that there is no new datafile/tablespace added to Database after you generate controlfile script as above

Step 4: On the source database make an online copy of all datafiles using:
SQL> ALTER TABLESPACE BEGIN BACKUP;

Copy all datafiles within tablespace to the new directory. 
On Unix systems, this can be done with the cp command.

Then do:

SQL> ALTER TABLESPACE END BACKUP;

Do NOT copy the controlfiles and redo log files as they will be recreated. You must copy the datafiles only after the ALTER .. BEGIN BACKUP command has been executed, otherwise the datafiles may be corrupted.

The names of the datafiles and tablespaces to which the datafiles belong can be obtained using the following command:

SQL> SELECT FILE_NAME, TABLESPACE_NAME FROM DBA_DATA_FILES;

Note: Instead of performing step 4 and step 5 to create a new online backup, you may instead use a previously taken online backup of your database.If you choose to use a previous online backup be sure to copy the required archived redo logs taken with the the previous online backup.

Step 5: After all datafiles have been copied and the tablespaces taken out of backup mode issue the following command:

SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;

You will need all of the archivelog files from the start of datafile copy commands including the one just created with the command ALTER SYSTEM ARCHIVE LOG CURRENT.

Step 6: Copy the database (DBF) files,controlfile script and archive log files from the source to the target
           system

Step 7: So, As mentioned in 230672.1 (Appendix B), Replace section 2.2a (Configure the target system database server) with the following steps:

Execute the following commands to configure the target system. You will be prompted for the target system specific values (SID, Paths, Ports, etc)

· Log on to the target system as the ORACLE user
· Configure the
cd /appsutil/clone/bin
perl adcfgclone.pl dbTechStack

Step 7: On the target system issue STARTUP NOMOUNT command. For example:
     
SQL> startup nomount pfile=initTEST.ora


Step 8: Run the prepared script created in step 3 to create the new controlfile. For example:

SQL> @PROD_ora_12345.trc

Step 9: Issue the command:
         
SQL> RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE


You will be prompted to apply all of the archived redo logs from the source database including
the last archive redo log file created with the ALTER DATABASE ARCHIVE LOG CURRENT
command from step 5.

After applying all of these archive log files issue the CANCEL command.

Step 10: Open the database with resetlogs:
         
SQL>ALTER DATABASE OPEN RESETLOGS

 At this point the target database will have been successfully cloned and opened.

Step 11:  Create Temporary Tablespace if not created in Source, else you shall add Temporary tablespace

You can check if tablespace TEMP has tempfiles or datafiles using the following SQL:

SQL> SELECT FILE_NAME,TABLESPACE_NAME,STATUS,AUTOEXTENSIBLE from DBA_TEMP_FILES where TABLESPACE_NAME like 'TEMP';

SQL> SELECT FILE_NAME,TABLESPACE_NAME, STATUS,AUTOEXTENSIBLE FROM DBA_DATA_FILES WHERE TABLESPACE_NAME LIKE 'TEMP';

If Temporary Tablespace is not created from above query,
SQL> create temporary tablespace temp add tempfile 'xxxx.dbf' size xx

Or

SQL> alter tablespace TEMP add tempfile  'xxxx.dbf' size xx


Step 12:  Run the library update script against the database

· cd /appsutil/install/
· sqlplus "/ as sysdba" @adupdlib.sql
      where is "sl" for HP-UX, "so" for any other UNIX platform and 
      not required for Windows.

Step 13: Configure the target database (the database must be open)

· cd /appsutil/clone/bin
· perl adcfgclone.pl dbconfig
     where target context file is:
     /appsutil/.xml 


Finally, refer back to cloning notes and the following sections:

· Copy the Application Tier File System
· Configure the Target System Application Tier Server Nodes
· Finishing Tasks
Release 11i : Note 230672.1 - 'Cloning Oracle Applications Release 11i with Rapid Clone'
Release 12 : Note 406982.1 - 'Cloning Oracle Applications Release 12 with Rapid Clone'

Tuesday, July 10, 2012

Interoperability Notes Oracle EBS 12 with Oracle Database 10gR2 (10.2.0) 812362.1



This note is the master document describing the use of Oracle E-Business Suite Release 12 (12.0 and 12.1) with Oracle Database 10g Release 2 (10.2.0.x),
where x denotes the patch set level (currently 5). It may refer to related interoperability notes, which you should review if they apply to your specific release of the Oracle Database.

The most current version of this document is document 812362.1 on OracleMetaLink. There is a change log at the end of this document.

Attention: Interoperability notes of previous patch sets are available through the following links:
10.2.0.3 Interoperability Notes
10.2.0.4 Interoperability Notes

Attention: Check My Oracle Support to make sure that your platform and environment configuration are certified to work with Oracle Database 10g before performing any instruction in this document.

Attention: If you are going to use 10g Real Application Clusters (RAC) or Automatic Storage Management (ASM), see Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage
Management with Oracle E-Business Suite Release 12 on My Oracle Support.

Attention: These notes apply to UNIX, Linux, and Windows platforms. However, you may need to modify some instructions slightly depending on your platform. For example, these notes typically
use UNIX/Linux syntax when specifying a directory, so Windows users will need to substitute the appropriate syntax when accessing that directory.

Attention: You can obtain the 10.2.0.5 patch set from patch 8202632 on My Oracle Support.

Upgrading an Existing Oracle Database 10g Release 2 (10.2.0) patch set

Follow the instructions in this section if you have an Oracle E-Business Suite Release 12.x system using Oracle 10g Release 2 (10.2.0) and you wish to apply the latest certified Oracle 10g Release 2 (10.2.0) patch set to it.

    Apply 10.2.0.5 interoperability patch 13725068 (conditional)

    If you are on E-Business Suite Release 12.0.4 or a later version, apply 10.2.0.5 interoperability patch for Release 12.0 (13725068)

    Perform 10.2.0.5 Patch Set preinstallation tasks (conditional)

    On the database server node, as the owner of the Oracle 10g file system and database instance, unzip and extract the patch set file appropriate for your platform.

Read the patch set notes (usually README.html) and make sure that you thoroughly understand the patch set installation process before you begin.

Check My Oracle Support or contact Oracle Support Services to determine any known issues with the patch set and its interoperability with Oracle Applications.

    Perform the tasks in the "Preinstallation Tasks" section of the patch set notes (if they apply to your system).

    Shut down Applications server processes

    Shut down all Applications and database server processes. The Applications will be unavailable to users until all tasks in this section are completed.

    Perform 10.2.0.5 Patch Set installation tasks

    On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks in the "Installing the Oracle Database 10g Patch Set Interactively"

 section of the patch set notes. Make sure that you use the runInstaller (UNIX/Linux) or the setup.exe executable (Windows) provided in the patch set to run OUI.

    Do not perform the "Postinstallation Tasks" section yet.

    Perform 10.2.0.5 Patch Set postinstallation tasks

    Review the "Postinstallation Tasks" section of the patch set notes. Perform the steps that are relevant for your database.

    Note: Skip the sections "Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.5)" and "Enabling Oracle Database Vault" of the patch set notes.

    Apply additional 10.2.0.5 RDBMS patches

    Apply the following patches:

    For all UNIX/Linux platforms, apply RDBMS patches:
        4247037
        9726739
        9870614

    For all Windows platforms:
        Apply patch 1 or the latest Windows patch: 10058290 (32-bit), 10099855 (64-bit)
        4247037

    Attention: While not mandatory for the interoperability of Oracle E-Business Suite with the Oracle Database, customers may choose to apply Database Patch Set Updates (PSU) on their
Oracle E-Business Suite Database. If so, please see Document 1147107.1 ('Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite') on
My Oracle Support for more information.

    Gather statistics for SYS schema

    Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server node. Note that adstats.sql has to be run in restricted mode.
 Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode, run adstats.sql, and restart the database in normal mode:

        $ sqlplus "/ as sysdba"
        SQL> shutdown normal;
        SQL> startup restrict;
        SQL> @adstats.sql
        SQL> shutdown normal;
        SQL> startup;
        SQL> exit;

    Note: Make sure that you have at least 1.5 GB of free default temporary tablespace.

    Restart Applications server processes

    Restart all the Applications server processes that you shut down before installing the patch set. Users may return to the system.