Assign the Responsibility to the User but it is not reflecting

Login as sysadmin
workflow->sitemap->configuration->service components
Screen appearing ..Just activate the Workflow Java Deferred Listener .

Next Run the two requests login as sysadmin
Workflow Directory Services User/Role Validation
Synchronize WF LOCAL tables

These two programs must run Compulsory

Auditing

Server Setup
Auditing is a default feature of the Oracle server. The initialization parameters that influence its behaviour can be displayed using the SHOW PARAMETER SQL*Plus command.
SQL> SHOW PARAMETER AUDIT
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
audit_file_dest string C:\ORACLE\PRODUCT\10.2.0\ADMIN
\DB10G\ADUMP
audit_sys_operations boolean FALSE
audit_trail string NONE
SQL>
Auditing is disabled by default, but can enabled by setting the AUDIT_TRAIL static parameter, which has the following allowed values.
AUDIT_TRAIL = { none os db db,extended xml xml,extended }
The following list provides a description of each setting:
· none or false - Auditing is disabled.
· db or true - Auditing is enabled, with all audit records stored in the database audit trial (SYS.AUD$).
· db,extended - As db, but the SQL_BIND and SQL_TEXT columns are also populated.
· xml- Auditing is enabled, with all audit records stored as XML format OS files.
· xml,extended - As xml, but the SQL_BIND and SQL_TEXT columns are also populated.
· os- Auditing is enabled, with all audit records directed to the operating system's audit trail.
Note. In Oracle 10g Release 1, db_extended was used in place of db,extended. The XML options are new to Oracle 10g Release 2.The AUDIT_SYS_OPERATIONS static parameter enables or disables the auditing of operations issued by users connecting with SYSDBA or SYSOPER privileges, including the SYS user. All audit records are written to the OS audit trail.The AUDIT_FILE_DEST parameter specifies the OS directory used for the audit trail when the os, xml and xml,extended options are used. It is also the location for all mandatory auditing specified by the AUDIT_SYS_OPERATIONS parameter.To enable auditing and direct audit records to the database audit trail, we would do the following.
SQL> ALTER SYSTEM SET audit_trail=db SCOPE=SPFILE;
System altered.
SQL> SHUTDOWN
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP
ORACLE instance started.
Total System Global Area 289406976 bytes
Fixed Size 1248600 bytes
Variable Size 71303848 bytes
Database Buffers 213909504 bytes
Redo Buffers 2945024 bytes
Database mounted.
Database opened.
SQL>
Audit Options
One look at the AUDIT command syntax should give you an idea of how flexible Oracle auditing is. There is no point repeating all this information, so instead we will look at a simple example.First we create a new user called AUDIT_TEST.
CONNECT sys/password AS SYSDBA
CREATE USER audit_test IDENTIFIED BY password
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp
QUOTA UNLIMITED ON users;
GRANT connect TO audit_test;
GRANT create table, create procedure TO audit_test;
Next we audit all operations by the AUDIT_TEST user.
CONNECT sys/password AS SYSDBA
AUDIT ALL BY audit_test BY ACCESS;
AUDIT SELECT TABLE, UPDATE TABLE, INSERT TABLE, DELETE TABLE BY audit_test BY ACCESS;
AUDIT EXECUTE PROCEDURE BY audit_test BY ACCESS;
These options audit all DDL and DML, along with some system events.
· DDL (CREATE, ALTER & DROP of objects)
· DML (INSERT UPDATE, DELETE, SELECT, EXECUTE).
· SYSTEM EVENTS (LOGON, LOGOFF etc.)
Next, we perform some operations that will be audited.
CONN audit_test/password
CREATE TABLE test_tab (
id NUMBER
);
INSERT INTO test_tab (id) VALUES (1);
UPDATE test_tab SET id = id;
SELECT * FROM test_tab;
DELETE FROM test_tab;
DROP TABLE test_tab;
In the next section we will look at how we view the contents of the audit trail.
View Audit Trail
The audit trail is stored in the SYS.AUD$ table. Its contents can be viewed directly or via the following views:
SELECT view_name
FROM dba_views
WHERE view_name LIKE 'DBA%AUDIT%'
ORDER BY view_name;
VIEW_NAME
------------------------------
DBA_AUDIT_EXISTS
DBA_AUDIT_OBJECT
DBA_AUDIT_POLICIES
DBA_AUDIT_POLICY_COLUMNS
DBA_AUDIT_SESSION
DBA_AUDIT_STATEMENT
DBA_AUDIT_TRAIL
DBA_COMMON_AUDIT_TRAIL
DBA_FGA_AUDIT_TRAIL
DBA_OBJ_AUDIT_OPTS
DBA_PRIV_AUDIT_OPTS
DBA_REPAUDIT_ATTRIBUTE
DBA_REPAUDIT_COLUMN
DBA_STMT_AUDIT_OPTS
14 rows selected.
SQL>
The three main views are:
· DBA_AUDIT_TRAIL - Standard auditing only (from AUD$).
· DBA_FGA_AUDIT_TRAIL - Fine-grained auditing only (from FGA_LOG$).
· DBA_COMMON_AUDIT_TRAIL - Both standard and fine-grained auditing.
The most basic view of the database audit trail is provided by the DBA_AUDIT_TRAIL view, which contains a wide variety of information. The following query displays the some of the information from the database audit trail.
COLUMN username FORMAT A10
COLUMN owner FORMAT A10
COLUMN obj_name FORMAT A10
COLUMN extended_timestamp FORMAT A35
SELECT username,
extended_timestamp,
owner,
obj_name,
action_name
FROM dba_audit_trail
WHERE owner = 'AUDIT_TEST'
ORDER BY timestamp;
USERNAME EXTENDED_TIMESTAMP OWNER OBJ_NAME ACTION_NAME
---------- ----------------------------------- ---------- ---------- ----------------------------
AUDIT_TEST 16-FEB-2006 14:16:55.435000 +00:00 AUDIT_TEST TEST_TAB CREATE TABLE
AUDIT_TEST 16-FEB-2006 14:16:55.514000 +00:00 AUDIT_TEST TEST_TAB INSERT
AUDIT_TEST 16-FEB-2006 14:16:55.545000 +00:00 AUDIT_TEST TEST_TAB UPDATE
AUDIT_TEST 16-FEB-2006 14:16:55.592000 +00:00 AUDIT_TEST TEST_TAB SELECT
AUDIT_TEST 16-FEB-2006 14:16:55.670000 +00:00 AUDIT_TEST TEST_TAB DELETE
AUDIT_TEST 16-FEB-2006 14:17:00.045000 +00:00 AUDIT_TEST TEST_TAB DROP TABLE
6 rows selected.
SQL>
When the audit trail is directed to an XML format OS file, it can be read using a text editor or via the V$XML_AUDIT_TRAIL view, which contains similar information to the DBA_AUDIT_TRAIL view.
COLUMN db_user FORMAT A10
COLUMN object_schema FORMAT A10
COLUMN object_name FORMAT A10
COLUMN extended_timestamp FORMAT A35
SELECT db_user,
extended_timestamp,
object_schema,
object_name,
action
FROM v$xml_audit_trail
WHERE object_schema = 'AUDIT_TEST'
ORDER BY extended_timestamp;
DB_USER EXTENDED_TIMESTAMP OBJECT_SCH OBJECT_NAM ACTION
---------- ----------------------------------- ---------- ---------- ----------
AUDIT_TEST 16-FEB-2006 14:14:33.417000 +00:00 AUDIT_TEST TEST_TAB 1
AUDIT_TEST 16-FEB-2006 14:14:33.464000 +00:00 AUDIT_TEST TEST_TAB 2
AUDIT_TEST 16-FEB-2006 14:14:33.511000 +00:00 AUDIT_TEST TEST_TAB 6
AUDIT_TEST 16-FEB-2006 14:14:33.542000 +00:00 AUDIT_TEST TEST_TAB 3
AUDIT_TEST 16-FEB-2006 14:14:33.605000 +00:00 AUDIT_TEST TEST_TAB 7
AUDIT_TEST 16-FEB-2006 14:14:34.917000 +00:00 AUDIT_TEST TEST_TAB 12
6 rows selected.
SQL>
Several fields were added to both the standard and fine-grained audit trails in Oracle 10g, including:
· EXTENDED_TIMESTAMP - A more precise value than the exising TIMESTAMP column.
· PROXY_SESSIONID - Proxy session serial number when an enterprise user is logging in via the proxy method.
· GLOBAL_UID - Global Universal Identifier for an enterprise user.
· INSTANCE_NUMBER - The INSTANCE_NUMBER value from the actioning instance.
· OS_PROCESS - Operating system process id for the oracle process.
· TRANSACTIONID - Transaction identifier for the audited transaction. This column can be used to join to the XID column on theFLASHBACK_TRANSACTION_QUERY view.
· SCN - System change number of the query. This column can be used in flashback queries.
· SQL_BIND - The values of any bind variables if any.
· SQL_TEXT - The SQL statement that initiated the audit action.
The SQL_BIND and SQL_TEXT columns are only populated when the AUDIT_TRAIL parameter is set to db,extended or xml,extended.
Maintenance and Security
Auditing should be planned carefully to control the quantity of audit information. Only audit specific operations or objects of interest. Over time you can refine the level of auditing to match your requirements.The database audit trail must be deleted, or archived, on a regular basis to prevent the SYS.AUD$ table growing to an unnacceptable size.Only DBAs should have maintenance access to the audit trail. Auditing modifications of the data in the audit trail itself can be achieved using the following statement:
AUDIT INSERT, UPDATE, DELETE ON sys.aud$ BY ACCESS;
The OS and XML audit trails are managed through the OS. These files should be secured at the OS level by assigning the correct file permissions.
Fine Grained Auditing (FGA)
Fine grained auditing extends Oracle standard auditing capabilities by allowing the user to audit actions based on user-defined predicates. It is independant of theAUDIT_TRAIL parameter setting and all audit records are stored in the FGA_LOG$ table, rather than the AUD$ table. The following example illustrates how fine grained auditing is used.First, create a test table.
CONN audit_test/password
CREATE TABLE emp (
empno NUMBER(4) NOT NULL,
ename VARCHAR2(10),
job VARCHAR2(9),
mgr NUMBER(4),
hiredate DATE,
sal NUMBER(7,2),
comm NUMBER(7,2),
deptno NUMBER(2)
);
INSERT INTO emp (empno, ename, sal) VALUES (9999, 'Tim', 1);
INSERT INTO emp (empno, ename, sal) VALUES (9999, 'Larry', 50001);
COMMIT;
The following policy audits any queries of salaries greater than £50,000.
CONN sys/password AS sysdba
BEGIN
DBMS_FGA.add_policy(
object_schema => 'AUDIT_TEST',
object_name => 'EMP',
policy_name => 'SALARY_CHK_AUDIT',
audit_condition => 'SAL > 50000',
audit_column => 'SAL');
END;
/
Querying both employees proves the auditing policy works as expected.
CONN audit_test/password
SELECT sal FROM emp WHERE ename = 'Tim';
SELECT sal FROM emp WHERE ename = 'Larry';
CONN sys/password AS SYSDBA
SELECT sql_text
FROM dba_fga_audit_trail;
SQL_TEXT
------------------------------------------
SELECT sal FROM emp WHERE ename = 'Larry'
1 row selected.
SQL>
Extra processing can be associated with an FGA event by defining a database procedure and associating this to the audit event. The following example assumes theFIRE_CLERK procedure has been defined:
BEGIN
DBMS_FGA.add_policy(
object_schema => 'AUDIT_TEST',
object_name => 'EMP',
policy_name => 'SALARY_CHK_AUDIT',
audit_condition => 'SAL > 50000',
audit_column => 'SAL',
handler_schema => 'AUDIT_TEST',
handler_module => 'FIRE_CLERK',
enable => TRUE);
END;
/
The DBMS_FGA package contains the following procedures:
· ADD_POLICY
· DROP_POLICY
· ENABLE_POLICY
· DISABLE_POLICY
In Oracle9i fine grained auditing was limited queries, but in Oracle 10g it has been extended to include DML statements, as shown by the following example.
-- Clear down the audit trail.
CONN sys/password AS SYSDBA
TRUNCATE TABLE fga_log$;
SELECT sql_text FROM dba_fga_audit_trail;
no rows selected.
-- Apply the policy to the SAL column of the EMP table.
BEGIN
DBMS_FGA.add_policy(
object_schema => 'AUDIT_TEST',
object_name => 'EMP',
policy_name => 'SAL_AUDIT',
audit_condition => NULL, -- Equivalent to TRUE
audit_column => 'SAL',
statement_types => 'SELECT,INSERT,UPDATE,DELETE');
END;
/
-- Test the auditing.
CONN audit_test/password
SELECT * FROM emp WHERE empno = 9998;
INSERT INTO emp (empno, ename, sal) VALUES (9998, 'Bill', 1);
UPDATE emp SET sal = 10 WHERE empno = 9998;
DELETE emp WHERE empno = 9998;
ROLLBACK;
-- Check the audit trail.
CONN sys/password AS SYSDBA
SELECT sql_text FROM dba_fga_audit_trail;
SQL_TEXT
--------------------------------------
SELECT * FROM emp WHERE empno = 9998
INSERT INTO emp (empno, ename, sal) VALUES (9998, 'Bill', 1)
UPDATE emp SET sal = 10 WHERE empno = 9998
DELETE emp WHERE empno = 9998
4 rows selected.
-- Drop the policy.
CONN sys/password AS SYSDBA
BEGIN
DBMS_FGA.drop_policy(
object_schema => 'AUDIT_TEST',
object_name => 'EMP',
policy_name => 'SAL_AUDIT');
END;

Compile INVALIDS

How to find the Invalid Objects?
select count(*) from DBA_OBJECTS where status='INVALID';
select owner,object_type,count(*) from dba_objects where status='INVALID' group by owner,object_type;

Compile Invalid Objects:
cd $ORACLE_HOME/rdbms/admin/utlrp.sql
Connect sqlplus "as sysdba"
sql>@utlrp.sql

This sql compile the All invalid Objects

Compilation scripts in Release 12

Compilation scripts in Release 12

 

 

1. How to compile the JA(India Localization) Forms in R12

Ans: Please follow the below steps to compile the forms in Release 12

In BATCH MODE :

a) Set the APPL_TOP environment.
b) Change directory to $AU_TOP/forms/US. 
c) Execute the following command from the operating system prompt:
frmcmp_batch module=.fmb output_file=$JA_TOP/forms/US/.fmx
userid=apps/
d) Check the output for errors.

In SINGLE MODE :

a) Set the APPL_TOP environment.
b) Change directory to $AU_TOP/forms/US. 
c) Execute the following  command from the operating system prompt:
frmcmp module=.fmb output_file=$JA_TOP/forms/US/.fmx userid=
apps/
d) Check the output for errors.

2. How to compile the library files in R12

Ans: Please follow the below steps to compile the library files in Release 12

In BATCH MODE :-

a) Set the APPL_TOP environment.
b) Change directory to $AU_TOP/resource
c) Execute the following command from the operating system prompt:
frmcmp_batch module=.pll userid=apps/ module_type=library compile_all=special
d) Check the output for errors.

In SINGLE MODE :-

a) Set the APPL_TOP environment.
b) Change directory to $AU_TOP/resource. 
c) Execute the  following command from the operating system prompt:
frmcmp module=.pll userid=apps/ module_type=library compile_all=special

3. Why The AD-ADMIN Utility  is not picking JA Forms in R12?

Ans: Ensure that JA Product is showing as licensed in License Manager.
 Refer Note 548961.1 For More details

4. How to find the versions of the files?

Ans : Please use any of the below commands to find out the file versions

strings -a | grep '$Header' 

(Or)

adident  Header  

 

Oracle AppsDBA Patching

1. How do you Apply a application patch? -> Using adpatch 2. Complete Usage of adpatch? 1. download the patch in three ways.
a) Using OAM-Open Internet Exploreer->Select Oracle Application Manager-> Navigate to Patch Wizard -> Select Download Patches -> Give the patch number(more than one patch give patch numbers separated by comma-> Select option download only->Select langauge and Platform-> Give date and time-> submit ok Note: Before doing this Your oracle apps should be configured with metalink credentials and proxy settings

b) If your unix system is configured with metalink then goto your applmgr account and issue following command

1.ftp updates.oracle.com
2.Give metalink username and password
3.After connecting, cd patch number
4. ls -ltr
5. get patchnumber.zip(select compatiable to OS)
c) Third way is connect to metalink.oracle.com.
1. After logging into metalink with your username and password
2. Goto Quickfind->Select patch numer-> Give patch number->Patch will be displayed->Select os type->Select download
3. ftp this patch to your unix environment
2. Apply the patch?
1. unzip downloaded patch using unzip
eg: unzip p6241811_11i_GENERIC.zip
2. Patch directory will be unzip with patch number.
3. Goto that directory read readme.txt completely.
4. Make sure that Middle tier should be down, Oracle apps is in maintainance mode and database and listener is UP
5. Note down invalid objects count before patching
6. Goto patch Directory and type adpatch
7. It will ask you some inputs from you like, is this your appl_top,common_top, logfile name,sytem pwd, apps pwd, patch directory location, u driver name etc. Provide everything
2. During Patch What needs to be done?

1. Goto $APPL_TOP/admin/SID/log
2. tail -f patchnumber.log(Monitor this file in another session)
3. tail -f patchnumber.lgi(Monitor this file in another session)
4. TOP comand in another session for CPU Usage
3. Adcontroller during patching?

1. During patching if worker fails, restart failed worker using adctrl(You wil find the option when u enter into adctrl)
2. If again worker fails, Goto $APPL_TOP/admin/SID/log/workernumber.log
3. Check for the error, fix it restart the worker using adctrl
4. If you the issue was not fixed, If oracle recommends if it can e ignorable, skip the worker using adctrl with hidden option 8 and give the worker number
4. Log files during patching?

1. patchnumber.log ($APPL_TOP/admin/SID/LOG/patchnumber.log)
2. patchnumber.lgi($APPL_TOP/admin/SID/LOG/patchnumber.lgi)
3. adworker.log($APPL_TOP/admin/SID/LOG/adworker001.log)
4. l.req($APPL_TOP/admin/SID/LOG/l1248097.req)
5. adrelink.log($APPL_TOP/admin/SID/LOG/adrelink.log)
6. adrelink.lsv($APPL_TOP/admin/SID/LOG/adrelink.lsv)
7.autoconfig.log($APPL_TOP/admin/SID/LOG/autoconfig_3307.log)
5. useful tables for patching?

1. ad_applied_patches->T know patches applied
2. ad_bugs->ugs info
3. fnd_installed_processes
4. ad_deferred_jobs
5. fnd_product_installations(patch level)
6. To know patch Info?

1. You can know whether particular patch is applied or not using ad_applied_patches or ad_bugs 
2. Using OAM->Patch wizard-> Give patch numer
3. To know mini pack patchest level, family pack patchest level and patch numbers by executing script called patchsets.sh(It has to be downloaded from metalink
7. Reduce patch time?

1. using defaults file
2. Different adpatch options you can get these options by typing adpatch help=y(noautoconfig,nocompiledb,hotpatch,novalidate,nocompilejsp,nocopyportion,nodatabaseportion,nogenerateportion etc)
3. By merging patches into single file
4. Distributed AD if your appl_top is shared
5. Staged APPL_TOP while in production env
8. Usage of Admerging?

1. You can merge number of patches into single patch
2. create two directories like eg: merge_source and merged_dest
3. Copy all patches directories to merge_source
4. admrgpch -s merge_source -d merged_dest -logfile logfile.log
5. merged patch will be generated into merged_dest directory and driver name wil be u_merged.drv
8. Usage of Adsplice?

1. Download splice patch, and unzip it
2. Read the readme.txt perfect
3. As per read me, copy following three files to $APPL_TOP/admin
izuprod.txt
izuterr.txt
newprods.txt
4. open newprods.txt using vi and modify the file by giving correct tablespace names available in your environment
5. run adsplice in appl_top/admin directory

Profile Options 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, it depends on your implemnetation. I am goingto update more about 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 Applications Help Web Agent

How to find Oracle Application file versions

FORM 

    1. Use \Help Version 

    2. Or Help, About Oracle Applications (when using 10SC) 

    3. adident   (Ex. adident Header ARXTWINS.fmx) 

    4. strings -a  form.frm |  grep  Revision  (Ex. strings -a POXPOMPO.frm | 

grep Revision) 

    REPORT 

cd $AR_TOP/reports

    1.  adident Header report.rdf (Ex. adident Header ARBARL.rdf) 

    2.  strings -a  report.rdf  |  grep  Header  (Ex. strings -a ARBARL.rdf  |  

grep Header) 

    SQL 

    1.  more  sqlscript.sql  (Ex.  more  arvstrd.sql) 

         The version will be in a line that starts with ¿REM  $Header¿, and 

should be one of the 

         first lines in the .sql file. 

    2.  grep ¿$Head¿ sqlscript.sql  (Ex.  grep  ¿$Head¿  arvsrtds.sql ) 

    BIN or EXECUTABLE 

    An executable in the bin directory will contain numerous C code modules, 

each with its own version. All of the following examples use ident or strings, 

but 

    the difference is what you grep for. 

    1.  Get ALL file versions contained in the executable. 

           adident Header executable (Ex. adident Header RACUST) 

             strings -a  executable  |  grep  Header  (Ex. strings -a RACUST | 

grep Header) 

    2.  Get ALL of the product specific file versions. 

         adident  Header executable (Ex.  adident Header RACUST) 

            strings -a  executable  |  grep  Header

          (Ex.  strings -a  RACUST  |  grep  Header) 

    3.  Get only the version of a specified module. 

         strings -a  executable  |  grep  module  (Ex. strings -a RAXTRX | 

grep raaurt) 

    ORACLE REPORTS 

    To find the version of Oracle Reports the customer is using: 

    1. From the operating system type ¿r20run¿, ¿r25run¿, or ¿r30run¿ (etc), 

depending on Reports version: (find this executable in their $ORACLE_HOME/bin 

directory). Then use the 

        menu patch Help, About Oracle Reports. 

    RDBMS 

    1. Use \Help Version 

    2. Or Help, About Oracle Applications (when using 10SC) 

    3. Get into SQL*Plus using any userid/password. You will get a string that 

gives you the database and PL/SQL version being used. 

Environment Files and Control scripts

Environment files are in place to manage the setup and configuration within the Oracle Application R12 system.Rapid install generates/create number of different environment files.

·  .env => $ORACLE_HOME (10.2.0.2) => Oracle Server Ent. Edition

·  .env => $ORACLE_HOME (AS 10.1.2)=> Oracle Tools Tech Stack

·  .env=> $ORACLE_HOME (AS 10.1.3)=> Java Tech Stack

·  .env => $APPL_TOP => Oracle Applications

·  APPS.env => $APPL_TOP =>Consolidated Environment file


Here CONTEXT_NAME is referred to _.CONTEXT_NAME.env is called environment setup file. Whereas APPS.env.env is called a consolidated environment file which reside under APPL_TOP directory.

Now question must be arise in your mind what is in CONTEXT_NAME.env environment file.

As pre R12 DBA must be aware of and fresher might be thinking what it consist of. 

So here comes the answer....

CONTEXT_NAME.env consist of :

·  Product Directories and Subdirectories

·  Product Directories Paths

·  Other environment information

Oracle application have important and core environment file is.env

Also you should know what parameters are part of.env environment file.

Here you go to know the description of these parameters.

·  APPLFENV - This parameter refers to name of the.env environment file.

·  APPL_TOP - This parameter refers to top-level directory for this installation of Oracle applications.

·  INST_TOP - This parameter refers to top-level directory for this instance.

·  FND_TOP - This parameter refers to path to AOL directory. For e.g /d01/oracle/apps/apps_st/appl/fnd/12.0.0

·  AU_TOP - This parameter refers to path to the applications utilities directory. For e.g /d01/oracle/apps/apps_st/appl/au/12.0.0.

·  NLS_LANG - This parameter refers to territory,language and character set installed in the database. For e.g AMERICAN_AMERICA.UTF8

·  NLS_DATE_FORMAT - This parameter refers to National language support date format.For e.g The default is "DD-MON-RR", e.g 16-JUL-08.

·  NLS_NUMERIC_CHARACTERS - This parameter refers to National language support numberic separators. The defulat is period and comman (".,").

·  _TOP - This parameter refers to path to a product's top directory

·  GWYUID - This parameter refers to the user name/password that give access to the initial sign on.

·  APPLDCP - This parameter refers to whether PCP is being used. This should be set to OFF if not using PCP.

·  APPLTMP - This parameter refers to directory for temp file in Oracle Applications.

·  APPLPTMP - This parameter refers to directory for temp PL/SQL output files.

·  APPLCNAM - This parameter refers to 8.3 file name convention for concurrent manager log and output files format.

·  APPLLOG - This parameter refers to concurrent manager log subdirectory.

·  APPLOUT - This parameter refers to concurrent manager output files subdirectory.

·  APPLCSF - This parameter refers to the top-level directory for concurrent manager log and output files if they are consolidated into single direcotry for all products.

·  PATH - This parameter refers to sets directory search path

·  FNDNAM - This parameter refers to the name of the schema to which the system 
administration responsibility connects.

·  ADMIN_SCRIPTS_HOME - This parameter refers to directory under $INST_TOP that identifies the location of control scripts.

·  PLATFORM - This parameter refers to the O/S currently in use. The value of this parameter should match with $APPL_TOP/admin/adpltfrom.txt

 

How to apply the RUP6 Patch

1)Compile INvalid Objects

2)Check MOunt point size after unzipping the patch its take Huze size

3)Pre requistes for RUP6

 

   6767273:Pre req Patch for  R12.AD.delta6

   7305220:R12.AD.Delta6(Please read readme carefully before applying this patch follow the same)

   

In Your environment EAM Module using at that time only u need to apply this patch

   

7427727:Pre req Patch for RUP6(EAMPMUPD.SQL FAILED WHHILE RUP6 XB3 PATCH APPLICATION )

4)RUP6 patch apply

   6728000:RUP6 

   7109200:Online help Of RUP6

Must follow the post installation steps..

Scripts

adautocfg.sh run autoconfig

adstpall.sh stop all services

adstrtal.sh start all services

adapcctl.sh start/stop/status Apache only

adformsctl.sh start/stop/status OC4J Forms

adoacorectl.sh start/stop/status OC4J oacore

adopmnctl.sh start/stop/status opmn

adalnctl.sh start/stop RPC listeners (FNDFS/FNDSM)

adcmctl.sh start/stop Concurrent Manager

gsmstart.sh start/stop FNDSM

jtffmctl.sh start/stop Fulfillment Server

adpreclone.pl Cloning preparation script

adoafmctl.sh adoafmctl.sh to start/stop/status OC4J oafm

(web service, map viewer)

adexecsql.pl Execute sql scripts that update the profiles in an AutoConfig run

java.sh Call java executable with additional args, (used by opmn, Conc. Mgr)

listener servlet config files

10.1.2 'C' Oracle home config, Contains tnsnames and forms listener servlet config files
10.1.3 Apache & OC4J config home, Apache, OC4J and opmn
This is the 'Java' oracle home configuration for OPMN, Apache and OC4J
pids Apache/Forms server PID files here
portal Apache's DocumentRoot folder

INST TOP directory

Instance top contains all the config files, log files, ssl certificates, document root etc. Addition of this directory makes the middle-tier more organized, since data is kept separate from config/log files. Another advantage is that, multiple instances can easily share the same middle tier. To create a new instance that shares an existing middle-tier, just create a new instance_top with proper config files and NFS mount the middle tier in the server.

INSTANCE TOP - STRUCTURE 

$INST_TOP: /oracle/inst/apps/SID_hostname

/admin /scripts  ADMIN_SCRIPTS_HOME: Find all AD scripts here

/appl  APPL_CONFIG_HOME. For standalone envs, this is set to $APPL_TOP

/fnd/12.0.0/secure FND_SECURE: dbc files here

 /admin All Env Config files here

/certs SSL Certificates go here

/logs LOG_HOME: Central log file location. All log files are placed here (except adconfig)

/ora ORA_CONFIG_HOME

    /10.1.2 'C' Oracle home config, Contains tnsnames and forms listener servlet config files

    /10.1.3 Apache & OC4J config home, Apache, OC4J and opmn

This is the 'Java' oracle home configuration for OPMN, Apache and OC4J

/pids Apache/Forms server PID files here

/portal Apache's DocumentRoot folder

Web Services

Web Services

The Web services component of Oracle Application Server processes requests received over the network from the desktop clients, and includes the following components:

• Web Listener (Oracle HTTP Server powered by Apache)

• Java Servlet Engine (OC4J)

• Oracle Process Manager (OPMN)

The Web listener component of the Oracle HTTP server accepts incoming HTTP requests (for particular URLs) from client browsers, and routes the requests to the appropriate OC4J container

 

Application server we find 3 Tops:

 

COMMON_TOP, APPL_TOP, INST_TOP

 

Under COMMON_TOP find admin clone java _pages temp util webapps

 

Use of Two Oracle Application Server ORACLE_HOMEs in Release 12

 

Oracle Application Server 10g release Two Different Oracle Homes...

• The latest version of Oracle Containers for Java (OC4J), the successor to JServ, is included in Oracle Application Server 10.1.3.

 

• All major services are started out of the Oracle iAS 10.1.3 ORACLE_HOME.

 

• The Applications modules (packaged in the file formsapp.ear) are deployed into the OC4J-Forms instance running out of the Oracle IAS 10.1.3 ORACLE_HOME, while the frmweb executable is invoked out of the OracleAS 10.1.2 ORACLE_HOME.

 ·          The 10g Release 2 (10.2) Database ORACLE_HOME replaces the Oracle9i     ORACLE_HOME used in Release 11i.

·          The Oracle Application Server 10.1.2 ORACLE_HOME (sometimes referred to as the Tools, C, or Developer     ORACLE_HOME) replaces the 8.0.6 ORACLE_HOME provided by Oracle9i Application Server 1.0.2.2.2 in Release 11i.

·          The Oracle Application Server 10.1.3 ORACLE_HOME (sometimes referred to as the Web or Java ORACLE_HOME)      replaces the 8.1.7-based ORACLE_HOME provided by Oracle9i Application Server 1.0.2.2.2 in Release 11i.

DESKTOP TIER

The client interface is provided through HTML for HTML-based applications, and via a

Java applet in a Web browser for the traditional Forms-based applications

APPLICATION TIER:

The application tier managing communication between desktop tier and the database tier. This tier is sometimes referred to as the middle tier. Hosting the various servers and service groups that process the business logic.

Three servers or service groups comprise the basic application tier for Oracle Applications:

• Web services

• Forms services

• Concurrent Processing server

In R12 Web, forms services are provided by Oracle Application Server 10g.

Architecture of Application DBA

The Oracle Applications Architecture is a framework for multi-tiered like Desktop Tier, Application Tier & Database Tier.