You can also enable the maintenance mode by calling the scripts in sql prompt sqlplus /@adsetmmd.sql ENABLE DISABLE

When adsetmmd.sql runs, it sets the Profile Option 'Applications Maintenance Mode' (APPS_ MAINTENANCE_MODE) to 'MAINT' to Enable 'Maintenance Mode' and to 'NORMAL' to Disable it.

If you don't want to put apps in maintenance mode you can use adpatch options=hotpatch feature.
Can you apply patch without putting Applications 11i in Maintenance mode ?
Yes, use options=hotpatch as mentioned above with adpatch.

What are various options available with adpatch ?
Various options available with adpatch depending on your AD version are autoconfig, check_exclusive, checkfile, compiledb, compilejsp, copyportion, databaseprtion, generateportion, hotpatch, integrity, maintainmrc, parallel, prereq, validate

posted by Jaswinder Singh @ 6:49 AM 5 comments

Duties of an oracle apps dba!

Sunday, July 22, 2007

Duties of an oracle apps dba!
An APPs DBA knows all that a regular DBA knows plus the following:-
Application fundamentals such as concepts and architecture
-Application Installation and configuration
-Patching and Upgrades
- Patch Management and Version Control
- Customization Updates
- Cloning requirements.
This can be frequent in an Apps environment
- Concurrent Managers
- Forms/Report Servers
- Web Servers
- all the "ad" utilities
- all the database restrictions for the applications.
That is so that the installation is still supportable and conforms to all vendor (Oracle) requirements.
- All special application related regular and maintenance functions. Such as month end and period end functions.
- Understand any backup and recovery constraints. Such as for table imports (NOT) and partial recoveries.
- special requirements and restrictions for tuning. Example optimizer and index requirements.
- Printer Configuration
- User Access Administration

posted by Jaswinder Singh @ 12:33 AM 0 comments

Clone Apps 11i Instance (It's very easy)

Wednesday, July 18, 2007

Another important & useful utility under AD_TOP which you and me as apps dba perform quite often i.e. Cloning Oracle Application 11i Instance.

Cloning is process of creating replica of your source apps 11i Instance ( lets say you have one apps Instance with name VISIONTST and you want to create similar instance ( including same patches & user data) like VISIONPRD then you will use adclone utility (Also called as Rapid Clone these days). In this case source Instance will be VISIONTST and target Instance will be VISIONPRD. There are lot for scenario in which you wish to clone your E-Business Suite 11i Instance , like you want to Test if everything is OK in Test & then after testing want to create Production instance or you want to move your Instance from one machine to other machine or if you are highly experienced Apps DAB you can use clone as staged environment during Upgrade to reduce downtime ( this concept is called as staged appl_top or staged patching/upgrade , p.s. this is different from shared APPL_TOP)

So here I am putting broad level steps you will use to clone apps instance .

Step1 . Prerequisites Steps you do before start cloning using rapid clone
1.1 Verify source and target nodes software versions
1.2 Apply the latest AutoConfig Template patch
1.3 Apply the latest Rapid Clone patches
Step2 . Clone Source to Target
2.1 Run preclone on DB tier
2.2 Run preclone on Apps or middle tier
2.3 Copy source file system to target file system
2.4 Configure db tier
2.5 Configure apps/middle tier
Step 3 Finishing Task
3.1 Update profile options
3.2 Update printer settings (If printers are not configured or you don't want to use printer you can skip this step)
3.3 Update workflow configuration settings (Important)

posted by Jaswinder Singh @ 1:22 AM 0 comments

Important Tables For APPSDBA.

Wednesday, July 4, 2007

Concurrent Manager :--
FND_CONCURRENT_QUEUES FND_CONCURRENT_PROGRAMS FND_CONCURRENT_REQUESTS FND_CONCURRENT_PROCESSES FND_CONCURRENT_QUEUE_SIZE

FND :--
FND 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 / PatchesAD_APPLIED_PATCHES AD_PATCH_DRIVERS AD_BUGS AD_INSTALL_PROCESSES AD_SESSIONS AD_APPL_TOPS

posted by Jaswinder Singh @ 8:21 PM 2 comments

Required Sizes for APPS Installations?

Monday, July 2, 2007

Required Different sizes for Different Installations?

For Fresh Production Database :--
                                                             Application Tier = 26 GB
                                                             Database     Tier = 32Gb
                                                                                                 Total = 58GB
For Vision Demo Database :-
                                                              Vision Demo Database = 75Gb

For Stage Area :-
                                                               Stage Area = 24GB

For Additional Language :
                                                             Add Language = 10GB
                                                             In Database     = 800MB

posted by Jaswinder Singh @ 10:08 AM 0 comments

Web Server How to Start and Stop

Sunday, July 1, 2007

Oracle Web Server also called as OHS (Oracle Http Server) or Oracle-Apache is built on Apache Webserver. Oracle has added few custom component (like mod_plsql, mod_osso...) in Apache webserver & shipped it as Oracle Http Server.

Discussion in this page is currently w.r.t. Oracle Http Server Version 1.0.2.2.2 which is shipped with 11i (11.5.8-10). In coming weeks I'll add 10G Application Server Integration with Oracle Applications 11i.

Oracle Web Server or OHS is entry point in applications, It processes requests coming from network over Client. There is Web Listener listening for Web Requests. If request is for simple html page core Apace returns HTML page but if URL refernced need further processing it will be forwarded to respective module like mod_pls, mod_jserv ... I will start with basics like how to start stop webserver, important directories & files , troubleshooting , tuning & important things to know in oracle applications E-Business suite Webserver.

How to Start/Stop Web Server All startup shutdown scripts in Oracle Applications 11i(11.5.10) are in $OAD_TOP/admin/script/$CONTEXT_NAME where OAD_TOP is also called as COMMON_TOP and CONTEXT_NAME is your SID_hostname , lets say your SID or Instance Name is VISION and its on machine with name machine1 so your CONTEXT_NAME will be VISION_machine1. Script to start/stop Web Server is adapcctl.sh where ad (application dba), apc(apache), ctl(control) and sh stands for shell script. (You will find this script only on node on which you have webserver, if you have multi mode Installation and node 1 is only for Concurrent Manager, Reports & Database and node2 is webserver & forms then adapcctl.sh should be on node2 & not node1 ) adapcctl.sh calls apachectl (shell script in $IAS_ORACLE_HOME/Apache/Apache/bin) which in turn calls HTTPD (in same directory which is executable called http daemon) it starts using configuration file httpd.conf (from $IAS_ORACLE_HOME/Apache/Apache/conf directory , this file calls other configuration file. To know all important configuration file follow config files link)

posted by Jaswinder Singh @ 11:44 AM 1 comments

Important APPS scripts

Note : To run these queries, Logon to SQLPLUS as apps user:

/* Query 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 = ''

/* 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;

/* 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

/* Check the concurrent request at backend */
SELECT a.request_id, d.sid, d.serial# ,d.osuser,d.process , c.SPID
FROM apps.fnd_concurrent_requests a,
apps.fnd_concurrent_processes b,
v$process c,
v$session d
WHERE a.controlling_manager = b.concurrent_process_id
AND c.pid = b.oracle_process_id
AND b.session_id=d.audsid
AND a.request_id = '&Request_ID'
AND a.phase_code = 'R';

/* To Find the Applications Version */
select release_name from apps.fnd_product_groups;

posted by Jaswinder Singh @ 11:22 AM 0 comments

Appsdba

Oracle apps is multitier.It provides vertically solutions for Oraganizations.

posted by Jaswinder Singh @ 9:38 AM 2 comments

About Me

Name: Jaswinder Singh
Home: Bangalore, Karnataka, India
Certifications: RAC Certified Expert, OCP 9i, 10g & 11i
About Me: I am working as APPSDBA, have hands on experience on DB RAC, HA on OAS 10g and Oracle Applications.
See my complete profile