Thursday, November 17, 2011

Usefull Unix/Linux commnads


1) To find a "word" or pattern in all files in a directory & subdirectories
find . -name "*" -exec grep -l {} \; -print
Example: belowsearching for word
find . -name "*" -exec grep -l dba {} \; -print

2)To find a class inside a set of Jar files
for i in 'find .-name *.jar'
do
if test 'jar -tvf $i|grep QualityObject.class'
then
ls $i
fi
done


3) To unzip all the patches in 1 directory in one go
for i in *.zip
do
unzip $i
done


4)To find the symbolic links that point to the old path in your oracle_home and appl_top.
This command is useful in cloning after restore from source to target that symbolic link are not pointing to source.
ls -al `find . -type l` | grep $OLD_PATH

5)To find all the text files that contains the old path at the UNIX level.
find . -type f -print|grep -v ":"|xargs file|grep "text"|awk '{FS=":"}{print $1}'|xargs grep -il $OLD_PATH

6) To Sort files based on Size of file in a Directory
Useful in finding out spaces issues
ls -l | sort -nrk 5 | more

7)How to check if a Port is listening for any Service
netstat -an | grep $PORTNO

Oracle Application DBA Interview Questions - III

Oracle Application DBA Interview Questions - III


Q)What is your day to day activity as an Apps DBA?
Ans:
As an Apps DBA we monitor the system for different alerts (Entreprise Manager or third party tools used for configuring the Alerts) Tablespace Issues, CPU consuption
Database blocking sessions..etc

Regular maintanance activies like cloning,patching,custom code migrations (provided by developers)
Working with user isses.

Q)How often Do you patch?
Ans: Usually for non-production the patching request comes aroung weekly 4-6 and the same patches will be applied to Production in the outage or maintanance window.
Production has weekly maintance window (Eg Sat 6PM to 9PM) where all the changes (patches) will applied on production.

Q)How often Do you clone?
Ans: Cloning happens biweekly or monthly depending on the organization requierement.

Q)What change control/management or CCB?
Ans: Every organization has change control process, Change control process is no change goes into production witout proir testing on non-production instance.
Eg: If a user encouters an issue in production instance and the fix for the issue is known, Still the fix should not be applied directly on production, as it is not tested.
The same fix need to be first applied on a non-prod instance where the similar issue is happening and test the issue and instance stability.
Once user is happy with the results the change or fix will be implemented to production with the approval from Change control Board, CCB is a managemant team who reviews all the changes being deployed to production,
Depending on the need and criticality and testing results they approve the change movement to production instance.


Q)How much time does it take to upgrade, clone ?
Ans: Clone usually takes around 48hrs to copy and configure and upgrade depends on the database size and module involved.
upgrade from 11.5.9 to 11.5.10.2 will take around 3-4 days and 11i to R12 upgrade will take around 4-5 days.

Q)What is the meaning QA,CRP,SIT,DEV,UAT,PRE-PROD,PROD Instance?
QA - Tesing Instance
CRP - Conference Room Pilot
SIT - System Integration Testing
DEV - Developement
UAT- User Acceptence Testing
STAGE - Pre-production Instance
Prod - Production/actuall instance where the business is running


Q)What do we have in FND_NODES?Ans:
FND_NODES table contains  information about node_names and services enabled on a node.
In multinode instance if you want to know which node is running what services, You can query the fnd_nodes and get that information.

Q)when do we run FND_CONC_CLONE.SETUP_CLEAN ?
Ans:
FND_NODES table contains node information, If you have cloned test instance from production still the node information of production will be present after clone in the test instance.
we use FND_CONC_CLONE.SETUP_CLEAN to cleanup FND_NODES table in the target to clear source node information as part of cloning.
Below syntax to execute:
SQL> sho user
USER is "APPS"
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;

PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.

This will delete all the entries in the fnd_nodes table, to populate it with target system node information, Run autoconfig on DB node and Applications node.

Q)How verify the sysadmin password from command line?
Ans:
This utility can be used to verify the GUEST/ORACLE password

SQL>select fnd_web_sec.validate_login('SYSADMIN','<sysadmin_password>')from dual;
If it returns Y then sysadmin password is correct
If it returns N then sysadmin password that we are using

Eg:
SQL> select fnd_web_sec.validate_login('SYSADMIN','SYSADMIN123') from dual;
FND_WEB_SEC.VALIDATE_LOGIN('SYSADMIN','SYSADMIN123')
--------------------------------------------------------------------------------
N

SQL> select fnd_web_sec.validate_login('SYSADMIN','SYSADMIN') from dual;
FND_WEB_SEC.VALIDATE_LOGIN('SYSADMIN','SYSADMIN')
--------------------------------------------------------------------------------
Y


Q)List out few Apps related tables ?
Ans:
CONCURRENT REQUEST/PROGRAM/MANAGERS
-------------------
FND_CONCURRENT_QUEUES
FND_CONCURRENT_PROGRAMS
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_PROCESSES
FND_CONCURRENT_QUEUE_SIZE


FND/AOL Tables
--------------

FND_APPL_TOPS
FND_LOGINS
FND_USER
FND_DM_NODES
FND_TNS_ALIASES
FND_NODES
FND_RESPONSIBILITY
FND_DATABASES
FND_UNSUCCESSFUL_LOGINS
FND_LANGUAGES
FND_APPLICATION
FND_PROFILE_OPTION_VALUES


AD/Patches
-------------
AD_APPLIED_PATCHES
AD_PATCH_DRIVERS
AD_BUGS
AD_INSTALL_PROCESSES
AD_SESSIONS
AD_APPL_TOPS


Q) How To find the latest application version
select ARU_RELEASE_NAME||'.'||MINOR_VERSION||'.'||TAPE_VERSION version, START_DATE_ACTIVE updated,ROW_SOURCE_COMMENTS "how it is done",BASE_RELEASE_FLAG "Base version" FROM AD_RELEASES where END_DATE_ACTIVE IS NULL

Q) How to find out if any patch except localisation patch is applied or not, if applied, that what all drivers it contain and time of it's application
select A.APPLIED_PATCH_ID, A.PATCH_NAME, A.PATCH_TYPE, B.PATCH_DRVIER_ID, B.DRIVER_FILE_NAME, B.ORIG_PATCH_NAME, B.CREATION_DATE, B.PLATFORM, B.SOURCE_CODE, B.CREATIONG_DATE, B.FILE_SIZE, B.MERGED_DRIVER_FLAG, B.MERGE_DATE from AD_APPLIED_PATCHES A, AD_PATCH_DRIVERS B where A.APPLIED_PATCH_ID = B.APPLIED_PATCH_ID and A.PATCH_NAME = ''

Q) How to know that if the patch is applied successfully, applied on both node or not, start time of patch application and end time of patch application, patch top location , session id ... patch run id */
select D.PATCH_NAME, B.APPLICATIONS_SYSTEM_NAME, B.INSTANCE_NAME, B.NAME, C.DRIVER_FILE_NAME, A.PATCH_DRIVER_ID, A.PATCH_RUN_ID, A.SESSION_ID, A.PATCH_TOP, A.START_DATE, A.END_DATE, A.SUCCESS_FLAG, A.FAILURE_COMMENTS from AD_PATCH_RUNS A, AD_APPL_TOPS B, AD_PATCH_DRVIERS C, AD_APPLIED_PATCHES D where A.APPL_TOP_ID = B.APPL_TOP_ID AND A.PATCH_DRIVER_ID = C.PATCH_DRIVER_ID and C.APPLIED_PATCH_ID = D.APPLIED_PATCH_ID and A.PATCH_DRIVER_ID in (select PATCH_DRIVER_ID from AD_PATCH_DRIVERS where APPLIED_PATCH_ID in (select APPLIED_PATCH_ID from AD_APPLIED_PATCHES where PATCH_NAME = '')) ORDER BY 3;

Q) Howto find the base application version
select ARU_RELEASE_NAME||'.'||MINOR_VERSION||'.'||TAPE_VERSION version, START_DATE_ACTIVE when updated, ROW_SOURCE_COMMENTS "how it is done" from AD_RELEASES where BASE_RELEASE_FLAG = 'Y'

Q) How To find all available application version
select ARU_RELEASE_NAME||'.'||MINOR_VERSION||'.'||TAPE_VERSION version, START_DATE_ACTIVE when updated, END_DATE_ACTIVE "when lasted", CASE WHEN BASE_RELEASE_FLAG = 'Y' Then 'BASE VERSION' ELSE 'Upgrade' END "BASE/UPGRADE", ROW_SOURCE_COMMENTS "how it is done" from AD_RELEASES

Q) How To get file version of any application file which is changed through patch application
select A.FILE_ID, A.APP_SHORT_NAME, A.SUBDIR, A.FILENAME, max(B.VERSION) from AD_FILES A, AD_FILE_VERSIONS B where A.FILE_ID = B.FILE_ID and B.FILE_ID = 86291 group by A.FILE_ID, A.APP_SHORT_NAME, A.SUBDIR, A.FILENAME

Q) How To get information related to how many time driver file is applied for bugs
select * from AD_PATCH_RUN_BUGS where BUG_ID in (select BUG_ID from AD_BUGS where BUG_NUMBER = ''

Q) How To find latest patchset level for module installed
select APP_SHORT_NAME, max(PATCH_LEVEL) from AD_PATCH_DRIVER_MINIPKS GROUP BY APP_SHORT_NAME

Q) How To find what is being done by the patch

select A.BUG_NUMBER "Patch Number", B. PATCh_RUN_BUG_ID "Run Id",D.APP_SHORT_NAME appl_top, D.SUBDIR, D.FILENAME, max(F.VERSION) latest, E.ACTION_CODE action from AD_BUGS A, AD_PATCH_RUN_BUGS B, AD_PATCH_RUN_BUG_ACTIONS C, AD_FILES D, AD_PATCH_COMMON_ACTIONS E, AD_FILE_VERSIONS F where A.BUG_ID = B.BUG_ID and B.PATCH_RUN_BUG_ID = C.PATCH_RUN_BUG_ID and C.FILE_ID = D.FILE_ID and E.COMMON_ACTION_ID = C.COMMON_ACTION_ID and D.FILE_ID = F.FILE_ID and A.BUG_NUMBER = '' and B.PATCH_RUN_BUG_ID = ' < > ' and C.EXECUTED_FLAG = 'Y' GROUP BY A.BUG_NUMBER, B.PATCH_RUN_BUG_ID, D. APP_SHORT_NAME, D>SUBDIR, D.FILENAME, E.ACTION_CODE

Q) How To find Merged patch Information from database in Oracle Applications
select bug_number from ad_bugs where bug_id in ( select bug_id from ad_comprising_patches where patch_driver_id =(select patch_driver_id from ad_patch_drivers where applied_patch_id =&n) );
Q) How toto know, what all has been done during application of PATCH
Select J.PATCh_NAME, H.APPLICATIONS_SYSTEM_NAME Instance_Name, H.NAME, I.DRIVER_FILE_NAME, D.APP_SHORT_NAME appl_top,D.SUBDIR, D.FILENAME, max(F.VERSION) latest, E.ACTION_CODE action from AD_BUGS A, AD_PATCH_RUN_BUGS B,AD_PATCH_RUN_BUG_ACTIONS C, AD_FILES D, AD_PATCH_COMMON_ACTIONS E, AD_FILE_VERSIONS F, AD_PATCH_RUNS G,
AD_APPL_TOPS H, AD_PATCH_DRIVERS I, AD_APPLIED_PATCHES J where A.BUG_ID = B.BUG_ID and
B.PATCH_RUN_BUG_ID = C.PATCH_RUN_BUG_ID and C.FILE_ID = D.FILE_ID and E.COMMON_ACTION_ID = C.COMMON_ACTION_ID
and D.FILE_ID = F.FILE_ID and G.APPL_TOP_ID = H.APPL_TOP_ID and G.PATCH_DRIVER_ID = I.PATCH_DRIVER_ID and
I.APPLIED_PATCH_ID = J.APPLIED_PATCH_ID and B.PATCH_RUN_ID = G.PATCH_RUN_ID and C.EXECUTED_FLAG = 'Y' and
G.PATCH_DRIVER_ID in (select PATCH_DRIVER_ID from AD_PATCH_DRIVERS where APPLIED_PATCH_ID
in (select APPLIED_PATCH_ID from AD_APPLIED_PATCHES where PATCH_NAME = 'merged'))
GROUP BY J.PATCH_NAME, H.APPLICATIONS_SYSTEM_NAME, H.NAME, I.DRIVER_FILE_NAME, D.APP_SHORT_NAME, D.SUBDIR,
D.FILENAME, E.ACTION_CODE


Q) How to find out Patch level of mini Pack
Select product_version,patch_level from FND_PROUDCT_INSTALLATIONS where patch_level like '%&shortname%';
Replace short name by name of Oracle Apps Minipack for which you want to find out Patch level . ex.
AD - for Applications DBA
GL - for General Ledger
PO - Purchase Order


Q)List out Profile Options Useful for Oracle Apps DBA?
Here is the list of few profile options which Apps DBA use frequently.
**It is not necessary that you as Apps DBA must know all profile options**
Applications Help Web Agent
Applications Servlet Agent
Applications Web Agent
Concurrent: Active Request Limit
Concurrent: Hold Requests
Concurrent: Multiple Time Zones
Concurrent: Report Access Level
Concurrent: Report Copies
Concurrent: Request priority
Database Instance
Enable Security Group
FND: Debug Log Filename
FND: Debug Log Level
Forms Runtime Parameters
Gateway User ID
ICX: Discoverer Launcher
ICX: Forms Launcher
ICX: Report Launcher
ICX: Limit Connect
ICX: Limit time
ICX: Session Timeout
MO Operating Unit
Node Trust Level
RRA: Delete Temporary Files
RRA: Enabled
RRA: Service Prefix
RRA: Maximum Transfer Size
Self Service Personal Home Page Mode
Sign-On: Audit Level
Signon Password Failure Limit
Signon Password Hard to Guess
Signon Password Length
Signon Password No Reuse
Site Name
Socket Listener Port
TCF: Host
TCF: Port
TWO TASK
Viewer: Text

Wednesday, November 9, 2011

To Find and Delete bigger size and older files in Linux

--To find out files size more than 5MB
find . -size +5000  -exec ls -ltr {} \; 
-- To **Remove** files size more than 5MB
find . -size +5000k  -exec rm -rf {} \;

--To find out files older than 30days
find . -mtime +30 -exec ls -ltr {} \;
--To find **Remove** files older than 30days
find . -mtime +30  -exec rm -rf {} \; &

CONCURRENT REQUEST MONITORING QUERIES

SQL TO FIND OUT CONCURRENT REQUESTS CURRENTLY RUNNING:
**********************************************
set lines 180
set pages 1000
set verify off
undef spid
column req_id format 99999999999
column OPID format a10
column PPID format a8
column SPID format a8
column ST_CD format a1
column ph_cd format a1
column CNAME format a30
column event format a15
column user_name format a10
column program format a8
column serial# format 999999
column sid format 9999
column username format a8
select a.request_id "REQ_ID",a.oracle_process_id "OPID",a.os_process_id
"PPID",
e.user_concurrent_program_name "CNAME",
f.user_name,a.status_code "ST_CD",a.phase_code "PH_CD", b.username,b.sid,
b.serial#,b.program,g.event,
to_char(a.ACTUAL_START_DATE,'MON-DD-HH-MI-SS') START_DATE,
to_char(a.ACTUAL_COMPLETION_DATE,'MON-DD-HH-MI-SS') COMPL_DATE
from apps.fnd_concurrent_requests a,(select c.username,c.sid,c.serial#,
                        c.program,d.spid from v$session c, v$process d
                        where c.paddr=d.addr) b,
                        apps.fnd_concurrent_programs_tl e,
                        apps.fnd_user f,
                        v$session_wait g
                        where a.oracle_process_id=b.spid
                        and a.concurrent_program_id=e.concurrent_program_id
                        and e.language='US'
                        and a.requested_by=f.user_id
                        and b.sid=g.sid
            and a.status_code='R'
            and a.phase_code='R';

SQL TO FIND CONCURRENT REQUEST SID,OS PROCESS DETAILS BY REQUEST ID
*******************************************************************

select a.argument_text, a.phase_code, a.status_code, a.oracle_process_id "DB_PROCESS", a.OS_PROCESS_ID "MT_PROCESS", f.user_name
from apps.fnd_concurrent_requests a, apps.fnd_user f where request_id='&REQUEST_ID' and a.requested_by=f.user_id;

OR
==

SELECT C.SID, C.SERIAL#, A.PID
FROM   GV$PROCESS A, FND_CONCURRENT_REQUESTS B, GV$SESSION C
WHERE  B.ORACLE_PROCESS_ID = A.SPID
-- AND    B.REQUEST_ID like '%'
AND    B.REQUEST_ID =&x
AND    A.ADDR=C.PADDR;


SQL TO FIND THE CONCURRENT REQUEST TRACE FILE DETAILS (Input Request ID)
*************************************************************************

SELECT 'Request id: '||request_id ,
'Trace id: '||oracle_Process_id,
'Trace Flag: '||req.enable_trace,
'Trace Name: '||dest.value||'/'||lower(dbnm.value)||'_ora_'||oracle_process_id|
|'.trc',
--'Prog. Name: '||prog.user_concurrent_program_name,
'File Name: '||execname.execution_file_name|| execname.subroutine_name ,
'Status : '||decode(phase_code,'R','Running') ||'-'||decode(status_code,'R','Normal'),
'SID Serial: '||ses.sid||','|| ses.serial#, 'Module : '||ses.module
from
fnd_concurrent_requests req,
v$session ses,
v$process proc,
v$parameter dest,
v$parameter dbnm,
fnd_concurrent_programs_vl prog,
fnd_executables execname where req.request_id = &request
and req.oracle_process_id=proc.spid(+)
and proc.addr = ses.paddr(+)
and dest.name='user_dump_dest'
and dbnm.name='db_name'
and req.concurrent_program_id = prog.concurrent_program_id
and req.program_application_id = prog.application_id
and prog.application_id = execname.application_id
and prog.executable_id=execname.executable_id ;

Wednesday, September 7, 2011

Blocks Corrupted in system09.dbf After Fresh Installation of E-Business Suite R12.1.1

We have identified a block corruption in the 12.1.1 Fresh Installed Instance, This block corruption identified while running RMAN.

RMAN LOG:
=========


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 09/06/2011 19:51:02
ORA-19566: exceeded limit of 0 corrupt blocks for file /u01/db/apps_st/data/system09.dbf


SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
---------- ---------- ---------- ------------------ ---------
352 165657 1 0 ALL ZERO
352 165656 1 0 CORRUPT


SQL> select file_name,FILE_ID,TABLESPACE_NAME from dba_data_files where file_id=352;
FILE_NAME FILE_ID TABLESPACE_NAME
------------------------------------------------------------ ---------- ------------------------------
/u01/db/apps_st/data/system09.dbf 352 SYSTEM


DB Verify OUTPUT
================

dbv file=/u01/db/apps_st/data/system09.dbf feedback=1000
DBVERIFY - Verification complete
Total Pages Examined : 192128
Total Pages Processed (Data) : 53193
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 27615
Total Pages Failing (Index): 0
Total Pages Processed (Other): 2081
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 82766
Total Pages Marked Corrupt : 26473
Total Pages Influx : 0
Total Pages Encrypted : 0
Highest block SCN : 3723391595 (1388.3723391595)



The Segments are Free segments - No need to Panic
=====================================

SQL> SELECT e.owner, e.segment_type, e.segment_name, e.partition_name, c.file#
2 , greatest(e.block_id, c.block#) corr_start_block#
, least(e.block_id+e.blocks-1, c.block#+c.blocks-1) corr_end_block#
3 , least(e.block_id+e.blocks-1, c.block#+c.blocks-1)
4 5 - greatest(e.block_id, c.block#) + 1 blocks_corrupted
, null description
6 7 FROM dba_extents e, v$database_block_corruption c
8 WHERE e.file_id = c.file#
9 AND e.block_id <= c.block# + c.blocks - 1
10 AND e.block_id + e.blocks - 1 >= c.block#
11 UNION
12 SELECT s.owner, s.segment_type, s.segment_name, s.partition_name, c.file#
13 , header_block corr_start_block#
14 , header_block corr_end_block#
15 , 1 blocks_corrupted
16 , 'Segment Header' description
17 FROM dba_segments s, v$database_block_corruption c
18 WHERE s.header_file = c.file#
19 AND s.header_block between c.block# and c.block# + c.blocks - 1
20 UNION
21 SELECT null owner, null segment_type, null segment_name, null partition_name, c.file#
22 , greatest(f.block_id, c.block#) corr_start_block#
23 , least(f.block_id+f.blocks-1, c.block#+c.blocks-1) corr_end_block#
24 , least(f.block_id+f.blocks-1, c.block#+c.blocks-1)
25 - greatest(f.block_id, c.block#) + 1 blocks_corrupted
, 'Free Block' description
26 27 FROM dba_free_space f, v$database_block_corruption c
28 WHERE f.file_id = c.file#
29 AND f.block_id <= c.block# + c.blocks - 1
AND f.block_id + f.blocks - 1 >= c.block#
30 31 order by file#, corr_start_block#;



OWNER SEGME SEGME PARTITION_NA FILE# CORR_START_BLOCK# CORR_END_BLOCK# BLOCKS_CORRUPTED DESCRIPTION
---------- ----- ----- ------------ ---------- ----------------- --------------- ---------------- --------------
352 165656 165656 1 Free Block
352 165657 165657 1 Free Block


SOLUTION TO FIX THE ISSUE
==========================


This is known issue in R12.1.1, The installation media of R12 has block corruption in it.

Ref NoteID: ID 840963.1

Have performed below actions to fix it.

SQL> select sum(bytes/1024/1024),sum(maxbytes/1024/1024) from dba_data_files where FILE_NAME like '%system09.dbf';
SUM(BYTES/1024/1024) SUM(MAXBYTES/1024/1024)
-------------------- -----------------------
                1501                       0


SQL>alter database datafile '/u01/db/apps_st/data/system09.dbf' resize 1000M;

Check for Corruption Now: NONE :)


$dbv file=/u01/db/apps_st/data/system09.dbf feedback=1000
DBVERIFY: Release 11.1.0.7.0 - Production on Wed Sep 7 08:41:53 2011
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
DBVERIFY - Verification starting : FILE = /u01/db/apps_st/data/system09.dbf
................................................................................
................................................

DBVERIFY - Verification complete
Total Pages Examined         : 128000
Total Pages Processed (Data) : 53193
Total Pages Failing   (Data) : 0
Total Pages Processed (Index): 27615
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 2081
Total Pages Processed (Seg)  : 0
Total Pages Failing   (Seg)  : 0
Total Pages Empty            : 45111
Total Pages Marked Corrupt   : 0
Total Pages Influx           : 0
Total Pages Encrypted        : 0
Highest block SCN            : 3723488883 (1388.3723488883)

Sunday, September 4, 2011

Unable To View workflow Status Diagram


In a fresh R12 installed instance, When clicked on the Status diagram following message appears "You have encountered an unexpected error. Please contact the System Administrator for assistance."

When pressed on the click Here link the below error message displays:
oracle.apps.fnd.framework.OAException: java.lang.NullPointerException ( and it displays lot of lines with the exception message)

Solution:

Set the profile option Server Timezone at Site level (should be set to the value of database timezone) and Bounce the Apache Server

Function not available to this responsibility. Change Responsibilities or contact your System Administrator

Function not available to this responsibility. Change Responsibilities or contact your System Administrator


In R12 after setting up New CUSTOM TOP, When you try to access Forms we are hitting "Function not available to this responsibility. Change Responsibilities or contact your System Administrator"

Even after defining the CUSTOM_TOP properly and defining the TOP in application env, this error would occur.

Solution:

1)In R12 go to $INST_TOP/ora/10.1.2/forms/server
2)Make sure your CUSTOM_TOP is defined in  default.env
Example:
Add the entrey as below  in the default.env
XXXYZ=/u01/oracle/EBSR12/apps/apps_st/appl/xxxyz/12.0.0


3)Bounce adopmnctl.sh stopall & Startall
4)Re-test the issue.

Tuesday, July 19, 2011

What is REVIVER In Oracle Applications:

What is REVIVER In Oracle Applications:

Reviver is used for momentary disconnects in the system where the concurrent managers and/or forms go down, and forms is later reconnected while the concurrent managers are not. FNDREVIVER revives the Internal Concurrent Manager (ICM) when it fails.
When ICM can no longer get a database connection, it kills itself and spawns the reviver. Reviver loops every 30 seconds, attempting to login to the database as apps user. Once login is successful, it starts up the ICM again.

If the failure is due to a brief network outage, or database issue, the managers are restarted, so the client does not have to restart the managers manually.

Reviver is recovery mechanism delivered with ATG RUP4 (patch 4676589), and runs in the background. In a Real Applications Cluster (RAC) environment, when the primary node goes down and ICM is set to migrate to the secondary node, the reviver parameter will be passed to the secondary node.

The easiest way to determine if reviver.sh exists is by checking the $FND_TOP/bin directory.

The variable resides in the context file under 's_cp_reviver' and can be set to "enabled" or "disabled". Based on the value of s_cp_reviver in the context file, AFCPDNR is started with a value of either "enabled" or "disabled" .

The reviver is started when starting the ICM, by passing a parameter reviver="enabled". You do this on the node you start the manager, and if the ICM is set to migrate to the second node, this parameter will be passes to the second node.
A common misconception is that users must start the reviver.sh manually, however this is not the intended use. It is automatically enabled when the parameter REVIVER_PROCESS="enabled" is passed via the adcmctl.sh concurrent manager startup script.


On a single node concurrent processing system, FNDREVIVER is the only way to recover from a database connection loss.

On a two node system (PCP), there is another factor, the Internal Monitor (FNDIMON).The FNDIMON will race to restart the internal manager in a multi node setup, and by the time the reviver starts it will likely see that the ICM is already running and exit accordingly.
FNDIMON checks whether it can connect to the database in order to determine if the ICM is running, and if the database connection is not available it fails to run and exits accordingly. The reviver is a shell script which loops until a connection is obtained, and then starts the manager accordingly. The reviver's job is the last line of defense after a database connection failure, as FNDIMON only works when the database connection is available.

In the event the ICM goes down due to a network outage, then the reviver would be needed to bring the ICM back up.

How to check and Enable reviver in Oracle Applications (Its by default enabled in R12):

The following parameters can be set in the context file, and then autoconfig should be re-run to enable reviver:

Example:
 $grep -i s_cp_reviver $CONTEXT_FILE
<cp_reviver oa_var="s_cp_reviver">enabled</cp_reviver>


Reviver Process PID Directory Location (s_fndreviverpiddir)

This variable specifies the path where ICM reviver process pid file will be created. Oracle recommends using a local disk as the PID file location because
the reviver process may run when the network is down.


Example:
<fndreviverpiddir oa_var="s_fndreviverpiddir">/u02/oracle/visappl/fnd/11.5.0/log</fndreviverpiddir>


All about DataInstaller & Hrglobal.drv in Oracle Applications

All about DataInstaller & Hrglobal.drv in Oracle Applications

This posts covers what is datainstaller & hrglobal.drv and when do we need to run them.

DataInstaller and hrglobal.drv are used for installing legislative data into Oracle Applications,For example a company operates in multiple counntries and payroll and HR practices are different in each countires, So they need to have all the legislative regulations (Taxation and HR rules and regulations) of the all the countries they run their business.

To achive this Oracle provides a set of patches, which need to applied to the Oracle applications.

These patches are country specific, The patch matrix can be found from Latest Oracle HRMS Legislative Data Patch Available (HR Global / hrglobal) [ID 145837.1]

To Install the legislative data please follow the below 4 steps:

1) PER & PAY modules need to be licenced ( This is madantory requirement)

2) Identify the patches & apply them based on your requirement from the Note:  145837.1
(Check the countires you need legislations and versions of the Applications)

3)After applying the patches run the datainstaller

Datainstaller is java command which will launch a interface to choose the set of legislation you require.

Always Install Global along with the country legislation you install.

Ex: If you wish to install US  legislations , Install Global and US.

You can install either payroll or hr for the the specific country your require or you can choose both.

The command line for the Data Install program is as follows:

Always run the datainstaller command from Middle Tier (Not from DB node) command line (VNC not needed)

Syntax:
java oracle.apps.per.DataInstall apps <apps_pwd> thin <db Hostname>:<db port>:<Db SID>
Example:

java oracle.apps.per.DataInstall apps apps thin testdb.oracle.com:1521:TESTDB

You will see a screen like below:

DataInstall Main Menu

1. Select legislative data to install/upgrade
2. Select college data to install/upgrade
3. Select JIT/Geocode or OTL to install/upgrade
4. Exit to confirmation menu

Enter your choice : 1

For more details on how to run Data Installer and hrglobal.drv Please check NOTE ID 140511.1

4)The last step in this process is to apply the hrglobal.drv

hrglobal.drv is patch driver file located in $PER_TOP/patch/115/driver, Apply it using
adpatch to populate the legislative data into the required HR tables in the database.

hglobal.drv can be applied as hotpatch.

Syntax:
adpatch driver=$PER_TOP/patch/115/driver/hrglobal.drv logfile=hrglobal.drv.log options=hotpatch <optional>

FAQ

Q) Do we need to run the datainstaller and hrglobal.drv every time we apply a HRMS patch?

A) No, Not needed, You need to run datainstaller when ever you apply the HRMS RUP patches or Upgrade Oracle Apps or Upgrade HRMS module.

In the above cases you need re0check the patch matrix and apply the nessesaty paches and run datinstaller & hrglobal.drv.

If any patch explicitely says you to run the datainstaller & hrglobal.drv you need to run them

Basically for regular HRMS patching (one-offs and Mini) you no need to run the datainstaller.

Sometimes you may need to apply hrglobal.drv and you may not needed datainstaller (when there is no change in the legislative selection)

Oracle Apps 12.1.3 upgrade post upgrade steps for Oracle E-Business Suite Integrated SOA Gateway:

Oracle Apps 12.1.3 upgrade post upgrade steps for Oracle E-Business Suite Integrated SOA Gateway:

If you have upgraded the applications to 12.1.3 and you have SOA gateway integrated with EBSO, The below steps are mandatory to perform.

0)Techstack Upgrade

The Minimum patch set for Applications Server required for SOA is 10.1.3.5.0
A)upgrade your system to Oracle10g Application Server Patch Set 5 (10.1.3.5.0).

i)Apply the latest opatch
- cd $IAS_ORACLE_HOME
- mv OPatch OPatch_old

- unzip -d $IAS_ORACLE_HOME /tmp/p6880880_101000_LINUX.zip (Download the patch from support.oracle.com)
- chmod -R 755 OPatch
- $IAS_ORACLE_HOME/OPatch/opatch version
- OPatch Version: 1.0.0.0.63

ii)Install 10.1.3.5 Patchset 8626084
- Source the env file under $INST_TOP/ora/10.1.3

- cd $INST_TOP/ora/10.1.3
- . ./$CONTEXT_NAME.env
- uname -i
- If it is a 64-bit OS (x86_64) then do the following
- linux32 ksh
- uname –i
- It should give i386

iii)Verify the inventory and ensure it has proper values

iv)Invoke the runInstaller from VNC
- cd /patches/8626084/Disk1
- ./runInstaller -invPtrLoc $ORACLE_HOME/oraInst.loc
- Screen 1) Select the 1013 ORACLE_HOME from the drop down list
- Screen 2) Provide the oc4jadmin password

- Complete the upgrade

Command to check version After the Upgrade:
- $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc | egrep 'Oracle Application Server 10g|Patch of Oracle Application Server 10g'

B)Verify the 10.1.2.X  Oracle Home version and the required version is 10.1.2.3:

Example:
$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc | egrep 'Oracle Application Server 10g|Patch of Oracle Application Server 10g'
Oracle Application Server 10g                                    10.1.2.0.2
Patch of Oracle Application Server 10g                           10.1.2.3.0


1)Source the file $INST_TOP/ora/10.1.3/.env and then apply the following patches to the Oracle10g
Application Server 10.1.3.5 Oracle Home using opatch:

- Source the env file under $INST_TOP/ora/10.1.3
- cd $INST_TOP/ora/10.1.3
- . ./$CONTEXT_NAME.env

Apply the below techstack patches using opatch
- 9435187
- 9371120
- 9668283
- 7366746


2)Configuring Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3

A)Apply the following Oracle E-Business Suite patch:

i) 9668283

- unzip p9668283_10135_GENERIC.zip
- cd $INST_TOP/ora/10.1.3
- . ./$CONTEXT_NAME.env
- cd 9668283
- opatch apply

ii) 9905881
Apply the above patch 9905881 using adpatch

B)Follow the configuration steps from Step 2 to Step 11 described in the section 3.3 Configuring
Oracle E-Business Suite Integrated SOA Gateway Release 12.1.2 to enable Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3. 

i)Set applications environment and stop all application tier processes.

- From the applications instance $APPL_TOP, set the environment by running the APPS<CONTEXT_NAME>.env script
- Stop all application tier processes for the instance by running the script $ADMIN_SCRIPTS_HOME/adstpall

ii)Run TXK development script to install Oracle Application Server Adapter for Oracle Applications as shown below:

- $FND_TOP/bin/txkrun.pl -script=CfgOC4JApp -applicationname=pcapps -oracleinternal=Yes  - oc4jpass=welcome12 -runautoconfig=No

Note: If the 'oc4jadmin' password for the OAFM oc4j instance is not known, then reset the password in the file  
 $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml before running the script. Take the backup of system-jazn-data.xml before resetting the password.
 Replace the modified system-jazn-data.xml with backup of system-jazn-data.xml after running the script.


        For example, if you want to reset the password to 'welcome12', below should be the entry:

              <user>
                  <name>oc4jadmin</name>
                  <display-name>OC4J Administrator</display-name>
                  <guid>23C8E4F0BDDE11DCBFB8AF3B7E0DDB2D</guid>
                  <description>OC4J Administrator</description>
                  <credentials>!welcome12</credentials>
              </user>

iii)Run TXK deployment script to install forms-c4ws.ear and configure container Forms-c4ws J2EE group correctly, as shown below:
- $FND_TOP/bin/txkrun.pl -script=DeployForms-c4ws

iv)Enable the new container forms-c4ws. (By default, the new OC4J container forms-c4ws will be disabled.)

- To enable the new container forms-c4ws, modify the following values of context variables in the $CONTEXT_FILE:
- Set 's_forms-c4wsstatus' to "enabled".
- Set 's_forms-c4ws_nprocs' to "1".

v)Run AutoConfig on MT Node

vi)Start all application tier processes for the instance by running the script $ADMIN_SCRIPTS_HOME/adstrtal

vii)Enable ASADMIN user using the following steps:

         1. Log on to Oracle E-Business Suite using sysadmin/sysadmin.
         2. Select the User Management responsibility in the Navigator.
         3. Click the Users link from the navigation menu to open the User Maintenance window.
         4. Locate 'ASADMIN' user by entering information in the search area to retrieve the 'ASADMIN' user.
         5. Click the Update icon next to the ASADMIN user to open the Update User window.
         6. Remove the Active To date field and click Apply.
         7. Click the Reset Password icon next to the ASADMIN user to open the Reset Password window.
         8. Enter new password twice and click Submit.


viii)After activating the ASADMIN user, verify if the ASADMIN user has the 'Apps Schema Connect Role' (UMX|APPS_SCHEMA_CONNECT) role in wf_user_roles.

- If the 'Apps Schema Connect Role' role is not present in the wf_user_roles for the ASADMIN user, then run the 'Workflow Directory Services User/Role Validation' concurrent program to grant the role.
ix)Reset the 'ASADMIN' password in the file system.

 After 'ASADMIN' user is enabled from Oracle E-Business Suite, update the file

 $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml as shown below to reset the password:

 <user>
 <name>ASADMIN</name>

 <display-name>Default Apps SOA User</display-name>
 <description>Used by SOAProvider for DB connection</description>
 <credentials>!<NEW PASSWORD></credentials>
 </user>

3)Bring up all the services and perform complete health check

Oracle Applications Upgrade from 12.1.1 to 12.1.3

Oracle Applications Upgrade from 12.1.1 to 12.1.3 (With Database 11.1.0.7):

The below steps outline the step by step actions to upgrade Oracle apps from 12.1.1 to 12.1.3

1)Bring down all the services and Take cold backup of the instance (Suggested)

2) Apply Database Patches
Please check and apply the below database patches.
For all UNIX/Linux platforms
    * 7111245
    * 7211965
    * 7330434
    * 7486407
    * 7627743
    * 7639602
    * 7684818
    * 8199107
    * 8639653
    * 8940108
    * 9026927
    * 9066130
    * 9554727
    * 9743057


3)For Linux x86-64, patch 7319922 contained within 7684818 was packaged incorrectly.

The new version of patch 7319922 has to be applied. Perform the following instructions:
Go to the 11.1.0.7 $ORACLE_HOME/inventory/oneoffs/7319922 directory.
Run "opatch rollback -id 7319922" to rollback patch 7319922.
Download the new version of patch 7319922 on My Oracle Support.
Go to the patch 7319922 directory.

Run "opatch apply"

4)Modify Initialization Parameters
_disable_fast_validate=TRUE
recyclebin=off

5)Techstack Upgrade:
 A)Verify the 10.1.3.X  Oracle Home version and the required version is 10.1.3.4 or higher <Use Document 454811.1> (for 10.1.3.5 ) or <Document 728531.1> (for 10.1.3.4 ) to upgrade it

 TO check the versions perform the below
 --------------------------------


 cd $INST_TOP/ora/10.1.3
 . ./$CONTEXT_NAME.env


 $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc | egrep 'Oracle Application Server 10g|Patch of Oracle Application Server 10g'
 Note: Oracle Application Server 10g signifies the Base Install and
 Patch of Oracle Application Server 10g signifies the Patchset on top of it

 Example: 
  $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc | egrep 'Oracle Application Server 10g|Patch of Oracle Application Server 10g'
 Oracle Application Server 10g                                    10.1.3.0.0
 Patch of Oracle Application Server 10g                           10.1.3.4.0
 


 B)Verify the 10.1.2.X  Oracle Home version and the required version is 10.1.2.3 <Use Document 437878.1 to upgrade it.>

 TO check the versions perform the below
 ----------------------------------------


 Log-out and Re-Login, before performing the following steps.

 $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc | egrep 'Oracle Application Server 10g|Patch of Oracle Application Server 10g'

 Note: Oracle Application Server 10g signifies the Base Install

 Patch of Oracle Application Server 10g signifies the Patchset on top of it

 Example:

 $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc | egrep 'Oracle Application Server 10g|Patch of Oracle Application Server 10g'
 Oracle Application Server 10g                                    10.1.2.0.2
 Patch of Oracle Application Server 10g                           10.1.2.3.0
 



6)Applications upgrade


a)Apply R12.AD.B.DELTA.3 <Patch 9239089>

Usage:
------
  1. Create $ORACLE_HOME/appsutil/admin on the database server.

  2. Copy adgrants.sql (UNIX) from this patch directory to $ORACLE_HOME/appsutil/admin.
  3. Set the environment to point to ORACLE_HOME on the database server.
  4. Use SQL*Plus to run the script:
     $ sqlplus /nolog
     SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql APPLSYS
  5. Apply u9239089.drv of the patch using adpatch
b)Apply Oracle E-Business Suite Release 12.1.3 <Patch 9239090>
  Apply  u9239090.drv of the patch using adpatch
c)Apply the latest consolidated online help <Patch 9239095>
  Apply u9239095.drv of the patch using adpatch


7)Post-Update Steps:

Apply post-install Oracle E-Business Suite Applications Technology patches. (Required)

 A) Apply mandatory Patch 9817770 (9817770:R12.ATG_PF.B [POST-R12.ATG_PF.B.DELTA.3 CONSOLIDATED PATCH].)
 
     Apply  u9817770.drv of the patch using adpatch
    
 B) Apply mandatory Patch 9966055 (9966055:R12.FND.B [TRANSLATED VERSION OF FNDSCSGN NOT LAUNCHED].)

     Apply  u9966055.drv of the patch using adpatch

8)Run autoconfig

Application tier:
-------------------

$cd $ADMIN_SCRIPTS_HOME
$adautocfg.sh
Run the admkappsutil.pl utility to create the file appsutil.zip in the <INST_TOP>/admin/out directory.
$perl $AD_TOP/bin/admkappsutil.pl

Database tier:
-------------------

Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>.
$cd $ORACLE_HOME
$unzip -o appsutil.zip
Run AutoConfig on the Database Node:
$cd $ORACLE_HOME/appsutil/scripts
$adautocfg.sh
9)Modify Initialization Parameters and bounce database
remove entry _disable_fast_validate=TRUE
set recyclebin=ON


10) Start Applications and Perform a health check of the instance.

Wednesday, July 6, 2011

Oracle Applications Installation and Upgrade Notes

Oracle Applications Installation and Upgrade Notes Release 12.1.1

Note 798258.1 –  Oracle Applications Release Notes, Release 12.1.1
Note 788053.1 –  Oracle Applications NLS Release Notes, Release 12.1.1

Note 761569.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for IBM AIX Based Systems (64-bit)
Note 762891.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for HP-UX Itanium
Note 762894.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for HP-UX PA-RISC (64-bit)
Note 761564.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86′
Note 761566.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64′
Note 761568.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Sun Solaris SPARC (64-bit)
Note 761567.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Microsoft Windows Server (32-bit)


Oracle Applications Installation and Upgrade Notes Release 12.0.X
Note 402310.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0.4) for Linux (32-bit)
Note 416305.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0.4) for Linux (64-bit)
Note 402312.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0.4) for Solaris Operating System (SPARC)
Note 402311.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0.4) for Microsoft Windows
Note 402306.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0.4) for AIX-Based Systems
Note 402307.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0.4) for HP-UX Itanium
Note 402308.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0.4) for HP-UX PA-RISC

Note 555895.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for HP-UX PA-RISC
Note 555893.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for HP-UX Itanium
Note 555874.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for Linux (32-bit)
Note 555876.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for Linux (64-bit)
Note 555879.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for Microsoft Windows
Note 555873.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for AIX-Based Systems
Note 555877.1 –  Oracle Applications Installation and Upgrade Notes Release 12 (12.0) for Solaris Operating System (SPARC)

Monday, July 4, 2011

error while loading shared libraries: libdb.so.2: cannot open shared object file: No such file or directory

After installing R12 on OEL5/RHEL5,http services not starting.


The below error found in the logfiles:
----------------------------------------
error while loading shared libraries: libdb.so.2: cannot open shared object file: No such file or directory

Fix:
------
ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

Friday, June 24, 2011

Mobile Wireless Applications (MWA) Telnet GUI Client for 11i/R12


To use MWA GUI Client ,The MWA server need to be setup and it must be accessibe from telnet.

The below steps are applicable for both 11i and R12(12.0.X and 12.1.X) Versions, Though the patch is for 11i.

1) Create 2 directories say C:\MWA\lib and C:\MWA\log

2) Extract the patch files from the patch p4205328_11i_GENERIC into C:\MWA\lib

3) Install jdk1.1.8 on your PC

4) Create a batch file say Start_MWA.bat on desktop with the following contents

Open notepad and copy & paste the below content and save it as Start_MWA.bat

set MWA_GUI_TOP=C:\MWA\
set JAVA_TOP=c:\jdk1.1.8
%JAVA_TOP%\bin\java -classpath %JAVA_TOP%\lib\classes.zip;%MWA_GUI_TOP%\lib\j4205328.zip oracle.apps.mwa.awt.client.StartGUI


5) Whenever you run this batch file, you must be able to see the GUI client for MWA

The loging screen will like below.


Tuesday, June 21, 2011

Oracle Applications Database Documentation Resources

Oracle Applications Database Documentation Resources, Release 12
================================================================
 

 Note 396009.1 Database Initialization Parameters for Oracle Applications Release 12
 Note 802875.1 Interoperability Notes E-Business Suite Release 12.1 with Oracle Database 11gR1 (11.1.0)
 Note 1058763.1 Interoperability Notes EBS R12 with Database 11gR2
 Note 735276.1 Interoperability Notes E-Business Suite R12 with Oracle Database 11gR1 (11.1.0)
 Note 782224.1 Interoperability Notes Oracle E-Business Suite Release 12 with 11gR1 (11.1.0.6)
 Note 454750.1 Oracle Apps Release 12 with Oracle Database 10.2.0 interoperability notes
 Note 761570.1 Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade
 Note 728244.1 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
 Note 738556.1 Oracle 11gR1 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
 Note 784374.1 Oracle 11gR1 (11.1.0.6) Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
 Note 403339.1 Oracle 10gR2 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
 Note 552973.1 Oracle 10gR2 (10.2.0.3) Database Preparation Guidelines for an E-Business Suite Release 12.0 Upgrade
 Note 467778.1 Oracle 10gR2 (10.2.0.2) Database Preparation Guidelines for an E-Business Suite Release 12.0 Upgrade
 Note 756050.1 Troubleshooting Autoconfig issues with Oracle Applications RAC Databases
 Note 745759.1 Oracle E-Business Suite and Oracle Real Application Clusters Documentation Roadmap
 Note 823587.1 Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12
 Note 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
 Note 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
 Note 388577.1 Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
 Note 762669.1 Using Oracle EBS R12 with a Database Tier Only Platform on Oracle 11gR1
 Note 456197.1 Using Oracle E-Business Suite Release 12 with a Database Tier Only Platform on Oracle 10g Release 2
 Note 741818.1 Export/Import Process for Oracle E-Business Suite Release 12 Database Instances Using Oracle Database 11g Release 1
 Note 454616.1 Export/Import Process for Oracle E-Business Suite Release 12 Database Instances Using Oracle Database 10g Release 2
 Note 452056.1 Business Continuity for Oracle Applications Release 12 on Database Release 10gR2 - Single Instance and RAC
 Note 859397.1 Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 11.1.0.7
 Note 566841.1 Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 10.2.0.4
 Note 744363.1 Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 10.2.0.3
 Note 732764.1 Using TDE Column Encryption with Oracle E-Business Suite Release 12
 Note  828229.1 Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12
 Note 734763.1 Using Transportable Database to migrate Oracle E-Business Suite R12 using Oracle Database 10g Release 2
 

Oracle Applications Database Documentation Resources, Release 11i
================================================================

 Note 216205.1 Database Initialization Parameters for Oracle Applications Release 11i
 Note 881505.1 Oracle Applications Release 11i with Oracle 11g Release 2
 Note 452783.1 Interoperability Notes Oracle E-Business Suite Release 11i with Oracle Database 11g Release 1 (11.1.0)
 Note 757593.1 Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0.6)
 Note 362203.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)
 Note 726982.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0.3)
 Note 423056.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0.2)
 Note 282038.1 Oracle Applications Release 11i with Oracle Database 10g Release 1 (10.1.0)
 Note 362202.1 Oracle Applications Release 11i with Oracle 10g (10.1.0.4)
 Note 216550.1 Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
 Note 399078.1 Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0.7)
 Note 162091.1 Interoperability Notes Oracle Applications R11i with Oracle9i Release 9.0.1
 Note 148903.1 Interoperability Notes Oracle Applications Release 11i with Release 8.1.7
 Note 359483.1 Upgrading 9.2.0.6 to 10.1.0.4.2 with 11.5.10.2 Applications
 Note 148902.1 Interoperability Notes Oracle Applications Release 11.0 with Release 8.1.7
 Note 148901.1 Interoperability Notes Oracle Applications Release 10.7 with Release 8.1.7
 Note 455398.1 Using Oracle Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 11i and Oracle Database 11g
 Note 757980.1 Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 11i (11.1.0.6)
 Note 362135.1 Configuring Oracle Applications Release 11i with Oracle10g Release 2 Real Application Clusters and Automatic Storage Management
 Note 312731.1 Configuring Oracle Applications Release 11i with 10g RAC and 10g ASM
 Note 279956.1 Oracle E-Business Suite Release 11i with 9i RAC Installation and Configuration using AutoConfig
 Note 261924.1 Oracle Applications 11.5.8 with 9i RAC Installation and Configuration
 Note 760637.1 Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC
 Note 946413.1 Using Oracle EBS with a Split Configuration Database Tier on 11gR2
 Note 562983.1 Using Oracle E-Business Suite with a Split Configuration Database Tier on Oracle 11g Release 1
 Note 369693.1 Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 2
 Note 356839.1 Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 1
 Note 304489.1 Using Oracle Applications with a Split Configuration Database Tier on Oracle 9i Release 2
 Note 332977.1 Using Oracle Applications with an HP OpenVMS Alpha Database Server
 Note 204015.1 Export/Import Process for Oracle Applications Release 11i Database Instances
 Note 557738.1 Export/Import Process for Oracle E-Business Suite Release 11i Database 11g
 Note 362205.1 10g Release 2 Export/Import Process for Oracle Applications Release 11i
 Note 331221.1 10g Export/Import Process for Oracle Applications Release 11i
 Note 230627.1 9i Export/Import Process for Oracle Applications Release 11i
 Note 204015.1Export/Import Process for Release 11i Database Instances Using Oracle8i Enterprise Edition
 Note 341437.1 Business Continuity for Oracle Applications Release 11i Using Oracle Real Application Clusters and Physical Standby Database
 Note 859399.1 Integrating Oracle E-Business Suite Release 11i with Oracle Database Vault 11.1.0.7
 Note 403294.1 Using TDE Column Encryption with Oracle E-Business Suite Release 11i
 Note 828223.1 Using TDE Tablespace Encryption with Oracle E-Business Suite Release 11i
 Note 729309.1 Using Transportable Database to migrate Oracle E-Business Suite Release 11i Using Oracle Database 10g Release 2 Enterprise Edition
 Note 285267.1 Oracle E-Business Suite 11i and Database FAQ



Miscellaneous - Oracle Applications Database Documentation Resources
================================================================

Note 216211.1 Nologging in the E-Business Suite
Note 312421.1 PL/SQL Native Compilation of Applications 11i on Oracle Database 10g Release 1 (10.1.0)
Note 554539.1 Using Database Partitioning with Oracle E-Business Suite
 

Monday, June 20, 2011

What is the difference between startup Upgrade and Migrate

What is the difference between startup Upgrade and Migrate:



startup migrate:
---------------

Used to upgrade a database till 9i.


Startup Upgrade ?
---------------

From 10G  we are using startup upgrade to upgrade database.


What happens internally when you use startup upgrade/migrate?
------------------------------------------------------------

It will adjust few database (init) parameters (irrespective of what you have defined) automatically to certain values in order to run upgrade scripts smoothely.

in other way..it will issue few alter statements to set certain parameters which are required to complete the upgrade scripts without any issues.

Oracle E-Business Suite 12.2 is coming soon:

Oracle E-Business Suite 12.2 is coming soon:

Oracle apps 12.2 is coming soon, This version Replacing OC4J with WebLogic Server 11G,It comes with database version 11G,

Please find the below architecture, More details can be found from http://blogs.oracle.com/stevenChan


Sunday, June 19, 2011

Configure Parallel Concurrent Processing For Oracle Applications

Configure Parallel Concurrent Processing (Note ID:362135.1)
NOTE: This section is for UNIX platforms only. Windows users should follow the instructions in Appendix F for configuration of Parallel Concurrent Processing and transaction managers.

a) PCP Prerequisites:
---------------------
It is assumed that you have more than one Concurrent processing tiers in your environment to setup PCP.

If you do not have this refer to Oracle MetaLink Note: 230672.1 for cloning of Applications tier.

b) Set Up PCP:
-------------
   1. Execute AutoConfig by using $COMMON_TOP/admin/scripts/<context_name>/adautocfg.sh on all concurrent nodes.

   2. Source the application environment by using $APPL_TOP/APPSORA.env
   3. Check the configuration files tnsnames.ora and listener.ora located under 8.0.6 ORACLE_HOME at $ORACLE_HOME /network/admin/<context>. Ensure that you         have information of all the other concurrent nodes for FNDSM and FNDFS entries.
   4. Restart the application listener processes on each application node.
   5. Logon to Oracle E-Business Suite Applications using SYSADMIN in login and System Administrator Responsibility. Navigate to Install > Nodes screen             and ensure that each node in the cluster is registered.
 
   6. Verify whether the Internal Monitor for each node is defined properly with correct primary and secondary node specification and work shift details.           Also make sure the Internal Monitor manager is activated by going into Concurrent -> Manager -> Administrator and activate the manager.
      (e.g. Internal Monitor: Host2 must have primary node as host2 and secondary node as host3)

   7. Set the $APPLCSF environment variable on all the CP nodes pointing to a log directory on a shared file system.
   8. Set the $APPLPTMP environment variable on all the CP nodes to the value of the UTL_FILE_DIR entry in init.ora on the database nodes. This value should        be pointing to a directory on a shared file system.
   9. Set profile option ' Concurrent: PCP Instance Check' to OFF if DB instance sensitive failover is not required. By setting it to 'ON' Concurrent               Managers will failover to a secondary middle-tier node when database instance it is connected goes down.

Friday, June 10, 2011

Purging and performence related Concurrent Requests for 11i and R12

The below seeded purging requests will help you to reduce the unwanted data and increase the performence of the oracle Applications.
These requests are applicable to both 11i and R12.

Note :Please note the purging request will delete the data permanently, So if you have any other business requierements please be cautious.

1)The "WORKFLOW CONTROL QUEUE CLEANUP" concurrent program should be scheduled to run at least every 12 HOURS.
 
2)Request Set with the following parameters:

For instances using Oracle Applications Release 11.5.8 or later, a concurrent request set consisting of the "PURGE OBSOLETE WORKFLOW RUNTIME DATA" and "COMPLETE DEFUNCT HR WORKFLOW PROCESSES" concurrent programs should be scheduled to run daily with the following parameters:
    "Purge Obsolete Workflow Runtime Data":
      Item Type: NULL
      Item Key: NULL
      Age: 7
      Persistence Type: select meaning
                        from fnd_lookups
                        where lookup_type = 'FND_WF_PERSISTENCE_TYPE'
                        and lookup_code = 'TEMP';

    "Complete Defunct HR Workflow Processes":
      Item Type: HR
      Age: 7
      Transaction Status: ALL

In addition, the stages of the request set should be linked such that the "Complete Defunct HR Workflow Processes" concurrent program only runs if the "Purge Obsolete Workflow Runtime Data" concurrent program returns Success or Warning.
 


3)The "GATHER SCHEMA STATISTICS" concurrent program should be scheduled to run at least every 7 DAYS.
 
4) For instances using Oracle Applications Release 11.5.8 or later, if PO is licensed, then the "PURGE OBSOLETE WORKFLOW RUNTIME DATA" concurrent program should be scheduled to run every week with the following parameters:

    Item Type: PO Approval
   
5)The program "PURGE CONCURRENT REQUEST AND/OR MANAGER DATA" should be scheduled to run within the next 24 hours with the following parameter(s): Entity=ALL, Mode=Age, Mode Value=30
  
6)The "PURGE OBSOLETE GENERIC FILE MANAGER DATA" concurrent program should be scheduled to run at least once a month with the following parameters:

     Expired=Yes
     Program Name=NULL
     Program Tag=NULL
    
7)The program "PURGE SIGNON AUDIT DATA" should be scheduled to run within  the next 30 days with the following parameter value:

      Audit date: <30 days prior to the scheduled run date>
In addition, the "Increment date parameters each run" scheduling option should be selected for the scheduled run of the program.