Friday, March 29, 2013

Performance: Concurrent Requests Hang in Pending Status For Long Time


Performance: Concurrent Requests Hang in Pending Status For Long Time

Applies to:

Oracle Concurrent Processing - Version 12.0.0 to 12.1.3 [Release 12 to 12.1]
Information in this document applies to any platform.
Symptoms

Concurrent managers slow performance leaves many concurrent requests in the Pending/Normal status, extending the completion time due to the prolonged duration of the Pending/Normal state.

Changes

Fresh installation /upgrade to R12

Cause

The cause of this problem has been identified in Bug 9301929 , the relevant SQL code had not been tuned and the FND_CONCURRENT_REQUESTS_N2 index required more columns to improve its performance.
Solution

To implement the solution, please execute the following steps:

For 12.1.x

Apply Patch 12877707 . Update file afcmgr.odf to version 120.19.12010000.2 or higher.

Patch 12877707 modifies index FND_CONCURRENT_REQUESTS_N2 to include program_application_id  and  concurrent_program_id  following  existing  status_code. This improves the performance of the concurrent manager sub-system.

For 12.0.x

Apply Patch 10388925 . Update file afcmgr.odf to version 120.16.12000000.8 or higher.

@ FND_CONCURRENT_REQUESTS  FND_CONCURRENT_REQUESTS_U2 INDEX
@ create INDEX on column STATUS_CODE , PROGRAM_APPLICATION_ID ,
@ CONCURRENT_PROGRAM_ID hang in pending status long time

Wednesday, March 20, 2013

Is There a Script to Identify the Session Identifier (SID) for an Actual Individual Apps User?



Is There a Script to Identify the Session Identifier (SID) for an Actual Individual Apps User?

goal: Is there a script to identify the session identifier (SID) for an
actual individual user in Oracle Applications?
fact: Oracle Application Object Library


fix:

All users in Oracle Applications show up as user APPS. Oracle Applications uses
the database user APPS for every one of its users.

Use the following SQL query to identify the sid and serial# associated with the
session identified in the Monitor Users form:
       SELECT SUBSTR(d.user_name,1,30) "User Name"
       , a.pid
       , b.sid
       , b.serial#
       FROM v$process a, v$session b, fnd_logins c, fnd_user d
       WHERE a.pid = c.pid
       AND c.pid = &PID
       AND d.user_name = UPPER('&USER_NAME')
       AND TO_DATE(c.start_time) = TO_DATE('&START_DATE')
       AND d.user_id = c.user_id
       AND a.addr = b.paddr
       AND c.end_time IS NULL
       /
2.When prompted for "PID" enter the value that appears under the
Oracle Process column on the form.
       .
3.When prompted for "USER_NAME" enter the value that appears under
the User Name column on the form.
       .
4.When prompted for "START_DATE" enter the Date that the user started
the session.
       .
Note: This value has to be determined based on how long the user has been
signed on the system. For instance if the user has been signed on for 10 hours
and the current time is 12:00 noon the current date would be the value that
should be entered.
       .
5.To kill the session make note of the SID and SERIAL# returned from the query
       .
6.Kill the session with the following comands:
SQL] ATLER SYSTEM KILL SESSION '[SID], [SERIAL#]';
ALTER SYSTEM KILL SESSION '[SID], [SERIAL#]';
       .
EXAMPLE:
For the example the following information was entered:
       .
PID = 35
USER_NAME = ZZJONES
START_DATE = 28-mar-00:
       .
       Enter value for pid: 35
       old 7: AND c.pid = &PID
       new 7: AND c.pid = 35
       Enter value for user_name: zzjones
       old 8: AND d.user_name = UPPER('&USER_NAME')
       new 8: AND d.user_name = UPPER('zzjones')
       Enter value for start_date: 28-mar-00
       old 9: AND TO_DATE(c.start_time) = TO_DATE('&START_DATE')
       new 9: AND TO_DATE(c.start_time) = TO_DATE('28-mar-00')
       .
       User Name PID SID SERIAL#
       ------------------------------ --------- --------- ---------
       ZZJONES 35 14 1764
       ZZJONES 35 15 2663
       .
Two rows are returned, because one database session is established for the
Navigator form and a second session is established for any form that is
launched from the Navigator form. It is possible that only one row will be
returned from
the query that corresponds to the navigator form.
       .
ALTER SYSTEM KILL SESSION '14, 1764';
ALTER SYSTEM KILL SESSION '15, 2663';

Tuesday, March 19, 2013

R12.1 hot backup - Using Hot Backup on Open Database

Cloning Oracle Application 11i /R12 with Rapid Clone - Database (9i/10g/11g)

 Using Hot Backup on Open Database

Oracle Applications Manager - Version 11.5.10.0 to 12.0.6 [Release 11.5.10 to 12]
Information in this document applies to any platform.
Goal

This purpose of this article is to help to duplicate/clone the Active/Open database to another machine

Fix

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


IMAPSSL Workflow Mailer Setup Using Self Signed Certificate




IMAPSSL Workflow Mailer Setup Using Self Signed Certificate

Goal

The purpose of this document is to enable customers to use a self signed certificate with the Workflow Mailer for IMAPSSL.  These steps must be followed in order to avoid the untrusted certificate error being thrown by the minimum supported J2SE (JDK) 1.4.2 for the concurrent manager node.  The Workflow Mailer uses the certificate keystore of the J2SE.  Patch 4676589, '11i.ATG_PF.H.RUP4' is minimum recommended version of ATG for users of IMAPSSL.

javax.mail.MessagingException: sun.security.validator.ValidatorException: No trusted certificate found;

ASSUMPTION

The 3rd party IMAP email server is already configured, tested and verified that it will work with IMAPSSL.  Oracle does not provide instructions on how to implement IMAPSSL on 3rd party products.

Fix

1. Source APPSORA.env

2. Place the self signed certificate created for your IMAP Email Server on the Concurrent Manager Node assigned to the Workflow Mailer Service.

3. Use J2SE 1.4.2 and the J2SE(JDK) keytool to create a standalone keystore or import and trust the self signed certificate into the JDK keystore.

a. Login as the OS user that owns the appsTier containing the Concurrent Manager Server node running the Workflow Mailer Service.

b. It is better to create a standalone keystore to mimimize maintenance as the J2SE keystore (cacert) will be different everytime the JDK is upgraded to a new version.

c. Keytool will create a hidden file called .keystore in the OS user home directory.

NOTE:  Keytool is a 3rd party utility whose syntax is not supported by Oracle.  Please research on the Internet if unfamiliar with utility.

4. Test that your keystore is valid from the command line:

a. Connectivity of IMAP server
    ------------------------------
Test invocation is:
$AFJVAPRG -classpath $AF_CLASSPATH -Dprotocol=imap \
( -Ddbcfile= | -Ddbuser -Ddbpassword -Ddburl )\ 
-Dserver= [-Dport= default 143] \ 
-Daccount= -Dpassword=
[ -Dfolder= ] \ 
[ -Dconnect_timeout=5 ] \
[ -Dssl= default N ] \ 
[ -Dtruststore= ]\ 
[ -Dconnect_timeout= default 5 ] \ 
[ -Ddebug= default N ]\ 
[ -Dlogfile= default test.log ]\ 
oracle.apps.fnd.wf.mailer.Mailer

b. IMAPSSL Test Example and Valid Result
----------------------------------------------

 $AFJVAPRG -classpath $AF_CLASSPATH -Dprotocol=imap \
-Ddbcfile=$FND_TOP/secure/VIS_orlncatst-02/vis.dbc.dbc \
-Dport=993 -Dssl=Y \
-Dtruststore=/home/applmgr/.keystore \
-Dserver=testuser.us.oracle.com \
-Daccount=orlncatst02 -Dpassword=orlncatst02 \
-Dconnect_timeout=120 -Ddebug=Y \
-Dlogfile=/tmp/garyimaptest.log -DdebugMailSession=Y oracle.apps.fnd.wf.mailer.Mailer

Server testuser.us.oracle.com at port 993 is reachable
Debug property -> {true}

DEBUG: getProvider() returning javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc]
* OK dovecot ready.
A0 CAPABILITY
* CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE AUTH=PLAIN
A0 OK Capability completed.
A1 LOGIN orlncatst02 orlncatst02
A1 OK Logged in.
A2 NOOP
A2 OK NOOP completed.
Successfully connected to the IMAP account
Note: Special folders like Inbox/Trash may not get listed on some IMAP servers
Folders defined are:
A3 LSUB "" "*"
* LSUB () "/" "Trash"
* LSUB () "/" "Processed"
A3 OK Lsub completed.
Trash
Processed
A4 LOGOUT
* BYE Logging out
A4 OK Logout completed.
A5 LOGOUT

5. Verify that you have the Workflow Mailer already configured and working on the default non-SSL port 143. If 143 is not available, login to E-Business Suite (EBS) and navigate to Workflow Mailer inside OAM and set Inbound Thread Count = 0 so that one can input the IMAP User Name and Password without validation.

Login to E-Business as a user assigned the System Administrator responsibility and navigate:

System Administrator > Oracle Applications Manager > Workflow > Notification Mailers > Edit > Advanced

6. Run $FND_TOP/sql/afsvcpup.sql from sqlplus to set the following parameters for the Workflow Mailer:

Working Example on ATG RUP3
----------------------------------

NOTE: You can get the component id and parameter id by running these queries:


SELECT component_id, component_name
FROM fnd_svc_components c
WHERE component_name like 'Workflow Notification Mailer'
order by component_id;

COMPONENT_ID COMPONENT_NAME
------------ --------------------------------------------------------------------------------
10006 Workflow Notification Mailer



set pagesize 100
set linesize 132
set feedback off
set verify off
set wrap off

col comp_param_id 999999999
col parameter_value format a35
col component_name format a30

select v.component_parameter_id comp_param_id, v.parameter_value, c.component_name
from fnd_svc_comp_param_vals_v v, fnd_svc_comp_params_b p, fnd_svc_components c, fnd_svc_comp_params_vl vl
where c.component_type = 'WF_MAILER'
and v.component_id = c.component_id
and v.parameter_id = p.parameter_id
and vl.parameter_id = p.parameter_id
and p.parameter_name in ('MAILER_SSL_TRUSTSTORE');

COMP_PARAM_ID PARAMETER_VALUE                     COMPONENT_NAME
------------- ----------------------------------- ----------------------------
        10475 /home/applmgr/.keystore             Workflow Notification Mailer
        11011 NONE                                Cs_MsgsMailer
        10741 NONE                                AG_Mailer
        10521 NONE                                Oracle Alert Email
a. Example:

Updating Debug Mail Session:

sqlplus apps/ @$FND_TOP/sql/afsvcpup.sql


Enter Component Id:


Enter the Parameter Id to update :

You have selected parameter : Debug Mail Session
Current value of parameter : N

Enter a value for the parameter : Y

b. Update the following Parameters:

10082 Inbound Thread Count 1
10025 Debug Mail Session Y (Optional setting to obtain diagnostics data and should be set to N after a successful test)
10140 Inbound SSL Enabled Y
10475 SSL Trust store /home/applmgr/.keystore (My standalone keystore)

7. Shutdown and restart the Workflow Mailer Service from inside OAM.

8. Confirm that the Workflow Mailer starts and will process inbound responses from the Workflow Mailer inbox.


How to setup an IMAP server on LINUX for E-Business Suite usage


How to setup an IMAP server on LINUX for E-Business Suite usage

Applies to:

Oracle Workflow Cartridge
Linux x86
Oracle Application Object Library - Version: 11.5.5 to 11.5.10
Goal

This note will guide you through the steps to allow you to set up an IMAP server so that you can respond to Notifications via e-mail and fully implement the "Forgot Password" functionality.
Solution

1. Install Dovecot IMAP/POP3 Mailer
- check if dovecot is installed
$ rpm -q dovecot

- Download dovecot-0.99.13-1.2.el4.test.i386.rpm if needed
( http://dag.wieers.com/packages/dovecot/ )


2. Install sendmail-mc if it is not installed


3. Create directory structure for dovecot if needed
- /var/run/dovecot/login
- /var/run/dovecot-login


4. Setup sendmail by editing mail configuration files

a. Look for and edit the following lines as needed in /etc/mail/sendmail.mc. Remove the "dnl" at the beginning of the line to make the line active.  Replace the IP address and host with your local values.

- LOCAL_DOMAIN(`AOL-linux.us.oracle.com')dnl
- MASQUERADE_DOMAIN(AOL-linux.us.oracle.com)dnl
- MASQUERADE_DOMAIN(AOL-linux)dnl

Change the following line to allow connection from the Internet. Be aware that this opens up your sendmail to public access.

From:
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
To:
DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl


b. Add a line with your IP Address in /etc/mail/access
###.##.##.### RELAY

c. Add your hostname and full qualified hostname as needed in /etc/mail/local-host-names
AOL-linux.us.oracle.com
AOL-linux

d. Add mail accounts as needed in /etc/mail/virtusertable
applmgr@AOL-linux.us.oracle.com applmgr
wfmailer@AOL-linux.us.oracle.com wfmailer

e. Compile the mail configuration files
- $ make

f. Restart the sendmail service
- $ service sendmail restart


5. Setup dovecot by editing /etc/dovecot.conf. Edit and/or add the following lines as needed. These values are set for small usage and most defaults are being used for processes. Remove the comments (#) from any lines as needed.


Change the following and/or remove comment:

protocols = imap pop3
default_mail_env = mbox:~/mail:INBOX=/var/mail/%u
auth_userdb = passwd
mbox_locks = fcntl

base_dir = /var/run/dovecot
login_dir = /var/run/dovecot/login
imap_listen = *
pop3_listen = *
login_executable = /usr/libexec/dovecot/imap-login
login_user = dovecot
login_executable = /usr/libexec/dovecot/pop3-login
imap_executable = /usr/libexec/dovecot/imap
pop3_executable = /usr/libexec/dovecot/pop3
auth_executable = /usr/libexec/dovecot/dovecot-auth
auth_count = 1

These are already defaulted:

login = imap
login = pop3
auth = default
auth_mechanisms = plain
auth_user = root


6. Start the dovecot service (root user)

$ service dovecot start


7. Test connect to sendmail account testmail

$ telnet testsystem.domain 25
$ helo  
$ quit

Example:

$ telnet testsystem.domain 25
Trying ###.#.##.###...
Connected to testsystem.domain (###.#.##.###).
Escape character is '^]'.
220 testsystem.domain ESMTP Sendmail 8.13.1/8.13.1; Fri, 3 Mar 2006 15:24:02 -0500
helo AOLTest-sun
250 testsystem.domain Hello testsystem.domain [###.#.##.###], pleased to meet you
quit
221 2.0.0 testsystem.domain closing connection
Connection closed by foreign host.


8. Test connection to the Dovecot IMAP vaild user - i.e. "testmail" with password "testmail1"

Type the following three commands:

$ telnet testsystem.domain 110
$ user testmail
$ pass testmail1

Example:

$ telnet testsystem.domain 110
Trying ###.#.##.###...
Connected to testsystem.domain (###.#.##.###).
Escape character is '^]'.
+OK dovecot ready.
user testmail
+OK
pass testmail1
+OK Logged in.
quit
+OK Logging out.
Connection closed by foreign host.


9. Configure an E-mail client to test you IMAP Server

Outlook 2000

a. Open Outlook

b. Click Tools -> Accounts

c. Click the [Add] button then choose “Mail” to create a new account

d. Choose the Account Name and click the [Next] button

e. Verify the email address (i.e. wfmailer@dovecot host.com)

f. Click the (next] button

g. Choose IMAP for the incomping Mail server

h. Enter the Server Name into the “Incoming Mail Server” and “Outgoing Mail Server” fields

i. Click the [Next] button

j. Enter the Username(wfmailer) and Password

k. Click the [Next] button

l. Choose the LAN connection type

m. Click the [Next] button

n. Click the [Finish] button to save the settings

o. Click the [Close] button on the “Internet Accounts” screen

Friday, March 15, 2013

FNDLOAD


FNDLOAD

The Generic Loader (FNDLOAD) is a concurrent program that can transfer Oracle Application entity data between database and text file. The loader reads a configuration file to determine which entity to access. In simple words FNDLOAD is used to transfer entity data from one instance/database to other. for example if you want to move a concurrent program/menu/valuesets developed in DEVELOPMENT instance to PRODUCTION instance you can direct use this command.


Steps to Move a Concurrent program from one instance(Database) to other

· Define your concurrent program and save it in first instance(for how to register a concurrent program click here)
· Connect to your UNIX box on first instance and run the following command to download the .ldt file

FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="Concurrent program application short name" CONCURRENT_PROGRAM_NAME="concurrent program short name"

· Move the downloaded .ldf file to new instance(Use FTP)
· Connect to your UNIX box on second instance and run the following command to upload the .ldt file

              FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct
              file_name.ldt


Note: Make sure you are giving proper .lct file in the commands and don’t confuse with .lct and .ldt files


These following are the other entity data types that we can move with FNDLOAD
1 - Printer Styles
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME="printer style name"

2 - Lookups
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="FND"
LOOKUP_TYPE="lookup name"

3 - Descriptive Flexfield with all of specific Contexts
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt DESC_FLEX P_LEVEL=’COL_ALL:REF_ALL:CTX_ONE:SEG_ALL’ APPLICATION_SHORT_NAME="FND" DESCRIPTIVE_FLEXFIELD_NAME="desc flex name" P_CONTEXT_CODE="context name"

4 - Key Flexfield Structures
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt KEY_FLEX P_LEVEL=’COL_ALL:FQL_ALL:SQL_ALL:STR_ONE:WFP_ALL:SHA_ALL:CVR_ALL:SEG_ALL’ APPLICATION_SHORT_NAME="FND" ID_FLEX_CODE="key flex code" P_STRUCTURE_CODE="structure name"

5 - Concurrent Programs
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="FND" CONCURRENT_PROGRAM_NAME="concurrent name"

6 - Value Sets
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name"

7 - Value Sets with values
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"

8 - Profile Options
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME="profile option" APPLICATION_SHORT_NAME="FND"

8 - Request Groups
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME="request group" APPLICATION_SHORT_NAME="FND"

10 - Request Sets
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET
APPLICATION_SHORT_NAME="FND" REQUEST_SET_NAME="request set"

11 - Responsibilities
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY="responsibility"

12 - Menus
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME="menu_name"

13 - Forms Personalization
FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES function_name=FUNCTION_NAME
Note: UPLOAD command is same for all except replacing the .lct and passing any extra parameters if you want to pass
               FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/corresponding.lct
               upload_file.ldt

Tuesday, March 12, 2013

E Business Suit Import note ids


The various knowledge documents listed here are written and maintained by the Oracle Applications Technology Group (ATG) and other development organizations, and divided into the following categories:

Section 1: Installation and Configuration
Section 2: Database Tier
Section 3: Application Tier
Section 4: Client Tier
Section 5: Security
Section 6: Documentation Resources
Section 1: Installation and Configuration

1.1 General

Document 399362.1, Oracle Applications Release 12 Upgrade Sizing and Best Practices
Document 387859.1, Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12
Document 406369.1, Oracle Configuration Manager and E-Business Suite Release 12 Release Notes
Document 727157.1, Upgrading OCM and Switching to Native Integration with Oracle E-Business Suite Release 12
Document 438086.1, Platform Migration with Oracle Applications Release 12
Document 406558.1, Configuring Applications Node Services in Oracle Applications Release 12
Document 384248.1, Sharing the Application Tier File System in Oracle E-Business Suite Release 12
Document 567015.1, Using IPv6 with Oracle E-Business Suite Releases 11i and 12
Document 380483.1, Oracle E-Business Suite Release 12 Additional Configuration and Deployment Options
Document 380489.1, Using Load-Balancers with Oracle E-Business Suite Release 12
Document 393861.1, Globalization Guide for Oracle Applications Release 12
Document 563019.1, Complying with Daylight Saving Time (DST) and Time Zone Rule Changes in E-Business Suite Release 12
Document 558959.1, Configuring Oracle Connection Manager With Oracle E-Business Suite Release 12
Document 414992.1, Using Cygwin to Maintain Oracle E-Business Suite Release 12 on Windows
Document 974422.1, Embedding Analytics in Oracle E-Business Suite
Document 1112325.1, Deploying Oracle GoldenGate to Achieve Operational Reporting for Oracle E-Business Suite
1.2 Cloning

Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone
Document 559518.1, Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone
Document 783188.1, Certified Oracle RAC Scenarios for Oracle E-Business Suite Cloning
1.3 Oracle VM

Document 1355641.1, Introduction to Oracle VM, Oracle VM Manager and EBS template deployment
Document 975734.1, Using Oracle VM Templates for Oracle E-Business Suite
Document 977681.1, Oracle VM Template Developer's Guide For Oracle E-Business Suite
Document 465915.1, Using Oracle VM with Oracle E-Business Suite Release 11i or Release 12
1.4 Secure Enterprise Search

Document 462377.1, Installing Oracle E-Business Suite Secure Enterprise Search, Release 12
Document 744820.1, Oracle E-Business Suite Secure Enterprise Search Best Practices, Release 12
Document 726239.1, Oracle E-Business Suite Secure Enterprise Search Troubleshooting Guidelines, Release 12
Document 551247.1, Oracle E-Business Suite Secure Enterprise Search Documentation Update, Release 12
Document 740499.1, Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.0.6
Document 566097.1 Document 566097.1, Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.1.1
Document 566097.1 Document 953483.1, Oracle E-Business Suite Secure Enterprise Search, Release Notes for Release 12.1.2
Document 1077540.1, Oracle E-Business Suite Secure Enterprise Search, Release Notes for Release 12.1.3
Document 781366.1, Search Modeler 1.1 for Oracle E-Business Suite Readme
1.5 Oracle Forms

Document 397174.1, Deploying a New Forms .ear File in Oracle Applications Release 12
Document 384241.1, Using Forms Socket Mode with Oracle E-Business Suite Release 12
Document 373548.1, Using Forms Trace in Oracle Applications Release 12
Document 437878.1, Upgrading Forms and Reports 10g in Oracle Applications Release 12
Document 444248.1, Using the OracleAS 10.1.2 Forms and Reports Builders with Oracle Applications Release 12
Document 1292611.1, Upgrading Form Personalizations and OA Framework Personalizations from Oracle E-Business Suite Release 11i to 12.1
Section 2: Database Tier

2.1 General

Document 396009.1, Database Initialization Parameter Settings for Oracle Applications Release 12
Document 467778.1, Oracle 10g Release 2 (10.2.0.2) Database Preparation Guidelines for an E-Business Suite Release 12 Upgrade
Document 552973.1, Oracle 10g Release 2 (10.2.0.3) Database Preparation Guidelines for an E-Business Suite Release 12 Upgrade
Document 403339.1, Oracle 10g Release 2 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
Document 554539.1, Using Database Partitioning with Oracle E-Business Suite
2.2 Interoperability Notes

Document 735276.1, Interoperability Notes for Oracle E-Business Suite Release 12 with Oracle Database 11g Release 1 (11.1.0)
Document 812362.1, Interoperability Notes for Oracle E-Business Suite Release 12 with Oracle Database 10g Release 2 (10.2.0)
Document 802875.1, Interoperability Notes for Oracle E-Business Suite Release 12.1 with Oracle Database 11g Release 1 (11.1.0)
Document 1058763.1, Interoperability Notes for Oracle E-Business Suite Release 12 with Oracle Database 11g Release 2 (11.2.0)
2.3 Oracle Real Application Clusters and High Availability

Document 1072636.1, Oracle E-Business Suite Release 12 High Availability Documentation Roadmap
Document 823587.1, Using Oracle 11g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
Document 466649.1, Using Oracle 11g Release 1 (11.1.0.7) Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
Document 783044.1, Using Oracle 11g Release 1 (11.1.0.6) Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
Document 388577.1, Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
Document 1137763.1, Using Oracle 10g Release 2 (10.2.0.4) Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
Document 1134753.1, Adding and Deleting Oracle RAC Nodes for Oracle E-Business Suite Release 12
Document 265633.1, Automatic Storage Management Technical Best Practices
Document 452056.1, Business Continuity for Oracle Applications Release 12 on Database Release 10gR2 - Single Instance and RAC
Document 1070033.1, Business Continuity for Oracle E-Business Release 12 Using Oracle 11g Physical Standby Database
Document 603325.1, Using Cisco ACE Series Application Control Engine with Oracle E-Business Suite Release 12
Oracle Maximum Availability Architecture
2.4 Patching

Document 734025.1, Using a Staged Applications System to Reduce Patching Downtime in Oracle Applications Release 12
Document 244040.1, Recommended Performance Patches for Oracle E-Business Suite
Document 1147107.1, Database Patch Set Update Overlay Patches Required by E-Business Suite
Document 1061366.1, List of Critical Patches Required For Oracle 11g Table Compression
Document 1267768.1, New Required Patches for Patch Wizard, Patch Manager, and Oracle Application Change Management Pack for Oracle E-Business Suite Releases 11i, 12.0, and 12.1
Section 3: Application Tier

3.1 General

Document 415007.1, Oracle Application Server with Oracle E-Business Suite Release 12: Frequently Asked Questions
Document 454811.1, Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12
Document 380487.1, Oracle Application Server 10g with Oracle E-Business Suite Release 12 Troubleshooting
Document 454178.1, Oracle Application Server Diagnostic Tools and Log Files in Applications Release 12
3.2 External Integrations

Document 1388152.1, Overview of Single Sign-On Integration Options for Oracle E-Business Suite
Document 975182.1, Integrating Oracle E-Business Suite with Oracle Access Manager 10g using Oracle E-Business Suite AccessGate
Document 1304550.1, Migrating Oracle Single Sign-On 10gR3 (10.1.4.3) to Oracle Access Manager 11gR1 (11.1.1.5) with Oracle E-Business Suite
Document 1309013.1, Integrating Oracle E-Business Suite Release 12 with Oracle Access Manager 11gR1 (11.1.1.5) using Oracle E-Business Suite AccessGate
Document 1484024.1, Integrating Oracle E-Business Suite Release 12 with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate
Document 1485033.1, Migrating Oracle Single Sign-On 10gR3 (10.1.4.3) to Oracle Access Manager 11gR2 (11.1.2) with Oracle E-Business Suite
Document 376811.1, Integrating Oracle E-Business Suite Release 12 with Oracle Internet Directory and Oracle Single Sign-On
Document 876539.1, Using the Latest Oracle Internet Directory 11gR1 Patchset with Oracle Single Sign-on and Oracle E-Business Suite
Document 373634.1, Using Discoverer 10.1.2 with Oracle E-Business Suite Release 12
Document 1074326.1, Using Discoverer 11.1.1 with Oracle E-Business Suite Release 12
Document 380484.1, Using Oracle Portal 10g with Oracle E-Business Suite Release 12
Document 1074334.1, Using Oracle Portal 11.1.1 with Oracle E-Business Suite Release 12
Document 380486.1, Installing and Configuring Web Cache 10g and Oracle E-Business Suite 12
Document 755067.1, Using Oracle BPEL 10g with E-Business Suite Release 12.1.1
Document 1070257.1, Integrating Oracle E-Business Suite 12.1.3 with BPEL in SOA Suite 11g
Document 1321776.1, Integrating Oracle E-Business Suite Release 12 with Oracle BPEL available in Oracle SOA Suite 11g
Document 557221.1, Oracle WebCenter 10g Application Creation and Deployment Guide for Oracle E-Business Suite Release 12
Document 1074345.1, Using WebCenter 11.1.1 with Oracle E-Business Suite Release 12
Document 1296491.1, Integration of Oracle E-Business Suite and Oracle Application Development Framework (ADF) Applications
Document 1205963.1, Configuring Oracle E-Business Suite Release 12 on Amazon Cloud Infrastructure
Document 1061947.1, Integrating Oracle E-Business Suite (11i, R12, and R12.1) with Content Management Repositories
Section 4: Client Tier

Document 1155883.1, Oracle E-Business Suite Desktop Client Hardware and Software Requirements
Document 389422.1, Recommended Browsers for Oracle E-Business Suite Release 12
Document 402138.1, Oracle Applications Release Notes for Apple Macintosh OS X 10.4
Document 418664.1, Overview of Using Java with Oracle E-Business Suite Release 12
Document 362851.1, Guidelines to Set Up the JVM in Oracle E-Business Suite Releases 11i and 12
Document 384249.1, Using Latest Update of JDK 5.0 with Oracle E-Business Suite Release 12
Document 455492.1, Using Latest Update of Java 6.0 with Oracle E-Business Suite Release 12
Document 1207184.1, Enhanced Signing of Oracle E-Business Suite JAR Files
Document 393931.1, Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12
Section 5: Security

Document 403537.1, Best Practices for Securing Oracle E-Business Suite Release 12
Document 946372.1, Secure Configuration of Oracle E-Business Suite Profiles
Document 376694.1, Using the Oracle Wallet Manager Command Line Interface with Oracle E-Business Suite Release 12
Document 376700.1, Enabling SSL in Oracle Applications Release 12
Document 380490.1, Oracle E-Business Suite Release 12 Configuration in a DMZ
Document 566841.1, Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 10.2.0.4
Document 859397.1, Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 11.1.0.7
Document 732764.1, Using TDE Column Encryption with Oracle E-Business Suite Release 12
Document 828229.1, Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12
Document 1437485.1, Using Oracle E-Business Suite Release 12.1.3 Template for the Data Masking Pack
Document 1460742.1, Deploying Oracle E-Business Suite on Oracle Exalogic Elastic Cloud and Oracle Exadata Database Machine
Section 6: Documentation Resources

Document 396957.1, Oracle Applications Technology Stack Documentation Resources, Release 12
Document 405565.1, Oracle Applications Release 12 Installation Guidelines
Change Log

"FS-CANT OPEN TEMPFILE" MESSAGE WHEN OPENING ANY VIEW LOGS OR OUTPUT LOGS


"FS-CANT OPEN TEMPFILE" MESSAGE WHEN OPENING ANY VIEW LOGS OR OUTPUT LOGS


Applies to:

Oracle Enterprise Performance Foundation - Version: 11.5.10 to 12.0.0 - Release: 11.5 to 12
Information in this document applies to any platform.
Checked for relevance 26-Sep-2011
FEM
Symptoms

Users get the following error message when trying to open any View Log or Output Log:

"FS-CANT OPEN TEMPFILE"

The navigation path is:  Process Management --> Requests --> View Requests --> Users select a failed or working job and click the icon in the Details column, then click the View Log.  If they click the icon in the Output column, the message also appears.

"FS-CANT OPEN TEMPFILE" is the only message to appear on the screen.
Cause

The message is not specific to FEM.  It could indicate problems with Concurrent Manager, or RRA: Profile Options, or Permissions and Space on the $APPLTMP directory.
Solution

1.  Concurrent manager may need to be checked to see if it is up and running.

2.  Concurrent manager may need bouncing.

3.  You may need to review Note 236311.1 FS-Cant Open Tempfile When Try to Send Output to Excel.  There are some Profile Options that may need to be examined:

RRA: Delete Temporary Files
RRA: Enabled
RRA: Maximum Transfer Size
RRA: Service Prefix
RRA: URL

If the "RRA: URL" Profile Option is missing a valid url, it is possible you will get the error message.

4.  FNDWRR attempts to create a temporary file under $APPLTMP. If unsuccessful, it will return FS-CANT CREATE TEMPFILE.  You may need to check the permissions to see if they are correct for $APPLTMP location and check for sufficient space.

5.  If you are using SAN, check to see if the file system is READ ONLY.  You may need to change that.