While installing apps 12 under OEL 5, I came across a problem and one of the suggestion made was to relink/compile an apps setup to see if that resolves the problem…

1. Locate your environment file.

For me, apps 12 with VISION database the env file “APPSVIS_ebs.env” is located at “/oracle/u01/apps/apps_st/appl” where “/oracle/u01” is Oracle_base

2. Setup your environment by running the env file

[applmgr@ebs appl]$ . APPSVIS_ebs.env

[applmgr@ebs appl]$ set | grep ORACLE
IAS_ORACLE_HOME=/oracle/u01/apps/tech_st/10.1.3
INCLUDE_FLAGS=’-I. -I$(FND_TOP)/include -I$(ORACLE_HOME)/precomp/public -I$(ORACLE_HOME)/rdbms/demo’
ORACLE_CONFIG_HOME=/oracle/u01/inst/apps/VIS_ebs/ora/10.1.2
ORACLE_HOME=/oracle/u01/apps/tech_st/10.1.2
ORACLE_TERM=vt220
PCC=’$(ORACLE_HOME)/bin/proc’
PCCINC=’. include=$(FND_TOP)/include include=$(ORACLE_HOME)/precomp/public’

3. Run adadmin now

Accept all default parameters and enter system password MANAGER & apps user password apps for default install.

To relink apps select option 2 and then 1.

Release 12  Disk Space Required

Rapid Install installs the file system and database files for all products, regardless of their licensed status. The approximate file system requirements in a standard installation are:

Applications node file system (includes OracleAS 10.1.2 ORACLE_HOME, OracleAS 10.1.3 ORACLE_HOME, COMMON_TOP, APPL_TOP, and INST_TOP)	28 GB (40 GB on HP-UX Itanium)
Database node file system (Fresh install)	45 GB
Database node file system (Vision Demo database)	133 GB (145 GB on HP-UX Itanium)

I just finished installing a Release 12 Vision instance on my dell Poweredge 2650 servers and here is a space usage

[oracle@ebs ~]$ df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1              9920592   3335540   6072984  36% /
/dev/sda3            263226696 240114568   9525156  97% /oracle
tmpfs                  1749784         0   1749784   0% /dev/shm

MY /oracle volume consists of Staging area for software , about 70GB

[oracle@ebs ~]$ cd /oracle/stage/
[oracle@ebs stage]$ du -s
72527264 

Total Space used by Apps 12 install = 240114568   – 72527264    = 167587304 i.e 167 GB

Release 11i  Disk Space Required

Rapid Install installs the file system and database files for all products regardless of their licensed status. The approximate file sizes in a single-node installation are:

Applications node file system (includes iAS/8.0.6 ORACLE_HOME, COMMON_TOP, and APPL_TOP)	26 GB
Database tier file system (fresh install with a production database)  OR Database tier file system (fresh install with a Vision Demo database)	31 GB 65 GB
Total space for a single node system, not including stage area	57 GB for a fresh Install with a production database 91 GB for a fresh install with a Vision Demo

With Oracle Applications 11.5.10 the ability to clone from a multi node to a single node system using rapid clone has now been certified.

This is accomplished by the Shared APPL_TOP and Merging APPL_TOP features.
In this post i am listing out the steps to perform a multi note to a single node cloning from scratch. The information mentioned here is the steps which i have used and found them to be successful for a more elaborate explanation you might want to refer to the metalink note Sharing the Application Tier File System in Oracle E-Business Suite 11i (233428.1).

Source System here refers to the multi node system to be cloned
Target System refers to the newly to be created single node system
Applications Version 11.5.10
Operating System Linux ES 4

The following Steps are required to be performed on the source system
1. Apply application tier patches using adpatch
Apply patch 4038964
Apply patch 4175764
Both the above patches are include in the consolidated update 2 or CU2 so in case you are on 11.5.10.2 or later you can ignore this step.

2. Maintain snapshot information
This explanation was from http://forums.oracle.com/forums/thread.jspa?threadID=535869
There are two types of snapshots:
1) APPL_TOP snapshots –> lists patches and versions of files in the APPL_TOP
2) Global snapshots –> lists patches and latest versions of files in the entire Applications system (that is, across all APPL_TOPs)
Both APPL_TOP snapshots and global snapshots may be either current view snapshots or named view snapshots. A current view snapshot is created once and updated when appropriate to maintain a consistent view. A named view snapshot is a copy of the current view snapshot at a particular time (not necessarily the latest current view snapshot) and is not updated.
Patch Wizard uses the information contained in the global current view snapshot to determine which patches have already been applied. AutoPatch uses the APPL_TOP current view snapshot to determine if all prerequisite patches have been applied to that APPL_TOP. Snapshot information is stored in the AD_SNAPSHOTS, AD_SNAPSHOT_FILES, and AD_SNAPSHOT_BUGFIXES tables.
A complete current view snapshot is required for automatic prerequisite patch checking to operate. During the installation, Rapid Install created a current snapshot as a baseline. And, each time you run AutoPatch, it automatically creates a new (updated) snapshot so that the information is current as of the application of the patch. However, after an upgrade to Release 11i, you must update the current snapshot by running this AD Administration task.
Log in as the applications user on each application tier node and run ‘Maintain Snapshot Information’ by using adadmin
Go to APPL_TOP
$ . APPSORA.env
$ adadmin
Choose Maintain Applications Files menu
Choose Maintain Snapshot Information

3. Merge existing APPL_TOPs
Log in to the primary node of your application tier as the application user user and run:
$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appsTier merge
This will prompt you with option to merge secondary nodes
Now log in as the applications user to each of the secondary application tier nodes being merged and run:
$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appltop merge

4. Prepare the source system database tier.
Log on to the database tier of the source system as the oracle user and run the following commands:
$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl dbTier
With this all the pre clone tasks on the source system have been completed.
The next sets of tasks are required to be carried out on the target system that is the system on which you wish to place the merged single node instance.

1. Create OS user accounts
Create a OS user account for your applications
$ useradd -g dba -d [home_directory] -p password username
Similarly create a OS user account for your database

2. Modify the orainventory to reflect the new location
$ vi /etc/oraInst.loc

3. Copy the following application tier directories
Copy the following application tier directories from the primary node of your source system to the target application tier node, retaining the original directory structure:
– [APPL_TOP]
– [OA_HTML]
– [OA_JAVA]
– [COMMON_TOP/util]
– [COMMON_TOP/clone>
– [806 ORACLE_HOME]
– [iAS ORACLE_HOME]

4. Copy the required files for merging
Log in as the applications user to each of the secondary source nodes and recursively copy:
directory [COMMON_TOP]/clone/appl
– to –
directory [COMMMON_TOP]/clone/appl on the target system node
Before proceeding with the next steps you must shutdown your oracle applications services and the database on the source system

5. Copy the database tier file system
Log on to the source system as the database user
Copy the database (DBF) files from the source to the target system
Copy the source database ORACLE_HOME to the target system
After this you can now startup the database and applications services on your source system and release it for use.

6. Configure the target system database server
Log on to the target system as the database user and type the following commands to configure and start the database:
$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbTier
This will prompt for new ORACLE_SID,ORACLE_HOME,Port Pool,JAVA_TOP and DATA_TOP give the appropriate values matching your target system
Once successful this should start your database and listener

7. Configure the application tier server nodes
The database and its listener should remain up before executing the next set of commands.
Log in to the merged APPL_TOP node as the applications user and execute the following commands:
$ cd [COMMON_TOP]/clone/bin
$ perl adcfgclone.pl appsTier
This will prompt you new port pool for applictaion tier services as well as new APPLTOP,COMMON_TOP,ORACLE_HOME and IAS_TOP
Successful completion of this task will bring up your application tier services on the target or the cloned node.

8. Post Clone Tasks
Log in to the target system application tier node as the APPLMGR user.
Run the following tasks in adadmin for all products:
o generate JAR files
o generate message files
o relink executables
o copy files to destination

9. Clean up of the target system
Remove the temporary directory [COMMON_TOP]/clone/appl to reduce disk space usage.
Note: The version of Oracle Applications used is 11.5.10 and the operating system is Linux ES 4

http://metalink.oracle.com
Using Patches -> simple search with following details

Product and Family : E-Business Suite
Release : Applications R12
Patch Type : Any
Classification : Recommended
Plateform or Language : Select Relevant
Click on Go button. This search will show recommended patches.

OR

Click on Top right hand Side “Patches” , select “Quick Links to: Latest Patchsets, Mini Packs and Maintenance Packs” & you will see “Latest Oracle Applications R12 Packs”

Example : Let’s locate 10.2.0.4 patch for 10.2.0.1 baseline environment

Generally, in Oracle Applications

– All *.fmb located at $AU_TOP/forms/US

– All *.fmx will be located at their respective Product top’s/forms/US.

If you want to create any new form, copy .fmb in to $AU_TOP/forms/US.
11i – Using f60gen syntax, you can generate .fmx in respective product top/forms/US

12 – use frmcmp

http://applicationsdba.wordpress.com/?s=frmcmp

Some people will place both .fmb & .fmx at their Product top’s/forms/US itself.  At runtime it will use .fmx file.

Log4plsql is an open source tool that uses PL/SQL framework to log into PL/SQL code package, function, web application, procedure, trigger and various oracle tools such as reports, forms etc. Before we proceed with Log4plsql for PL/SQL Logging, it is important to understand the concept behind the importance of logging and logs in the development environment.
Logging is very important part of development lifecycle for any process or application. These logs are important for tracing functional events, data and operations. Logs are also used for code debugging and in testing or maintenance phase to understand unforeseen events such as system crash, quit or launch. It is considered as a very time-consuming tedious job as all the logs during the development strategy have to be considered which utilizes vital computer memory or resources.

What Is LOG4PLSQL ?

LOG4PLSQL is a PL/SQL framework for logging in all PL/SQL code
·        Package,
·        Procedure,
·        Function,
·        Trigger,
·        PL/SQL Web application.
·        Oracle Tools (form, report, …)
Purpose:
·        Easy implementation and use
·        Possibility to log apart from transaction
·        Possibility to adapt the level of logging depending on user requirements
·        Ability to use all LOG4J feature.
·        Provide a complete set of  PL/SQL development tools (debug variable, SQLERRM, assert, call stack, … ).

Log destination:
·        table TLOG
·        alert.log file
·        trace file
·        standard output
·        session information (view V$SESSION)
·        advanced queue read by Log4JBackgroundProcess. :
o       Async,
o       JDBC,
o       JMS,
o       NTEventLog,
o       SMTP,
o       Socket,
o       SocketHub,
o       Syslog,
o       Telnet,
o       Writer

Log4plsql was born from the log4J spirit (and use it).

Architecture

 

Package PLOG  It is the main package of the log functionality. Your PL/SQL applications call its public functions to create a log event (info, debug …)

Package PLOGPARAM Package containing default values for the logging context

Package PLOG_INTERFACE  Dispatcher package built dynamically during the installation of the schema (for compilation raison). Its role is to call the dedicated packages for output according to the configuration and installation choices.

Package SL_PLOG_OUT_ALERT Optional package writing log information into the Oracle alert file alert.log. The function DBMS_SYSTEM. Ksdwrt() function is used.

Package SL_PLOG_OUT_TRACE Optional package writing log information into the Oracle trace file ora.trc. The function DBMS_SYSTEM. Ksdwrt() function is used.

Package SL_PLOG_OUT_AQ Optional package writing log information in a multi-consumer advanced queue consumed by the Java background process. The messages are enqueued using the package DBMS_AQ.

Package SL_PLOG_OUT_DBMS_OUTPUT Optional package writing log information into the standard output. The package DBMS_OUTPUT is used.

Package SL_PLOG_OUT_TLOG Package writing the log information in the table SL_TLOG. The package is part of the basis installation.

 

Installation of Log4plsql for PL/SQL Logging is very easy. Just follow these simple steps:

• Download Log4Sql from sourceforge.
• Unzip the zip file at the location where you want Log4plsql for PL/SQL Logging to be installed.
• Run the executable install file in cmd directory.
• Basic installation of Log4plsql for PL/SQL Logging is complete and now you need to proceed only if you want to functions or features.

An advanced user has more requirements or desires from Log4plsql for PL/SQL Logging as compared to normal end users. Some of these advanced requirements are:

• He or she needs to test logging level for which they code it before logging with any of the IsEnabled functions such as isInfoEnabled, isErrorEnabled, isDebugEnabled, isWarnEnabled and isFatalEnabled.
• An advanced user may want to change the default log parameters for a certain application.
• Need to create log section in hierarchical log node. You can also specify your own hierarchical log node by defining begin, end and get section.

Payables Workbenches
Oracle Payables includes two fully integrated workbenches, the Invoice Workbench and the Payment Workbench. You can perform most of your transactions in Payables using the Invoice Workbench or the Payment Workbench. You enter, adjust, and review invoices and invoice batches in the Invoice Workbench. You create, adjust, and review payments and payment batches in the Payments Workbench.
Payables workbenches let you find critical information in a flexible way. For example, in the Invoice Workbench, you can find an invoice based on supplier, purchase order number, status, or other criteria. Then, for that invoice, you can review distributions, scheduled payments, payments, holds, and other detailed invoice information. You can also perform matching, submit invoice validation, apply and release holds, or initiate payment. You can query an invoice then perform several transactions without having to find the invoice again. You can also keep multiple windows open at one time.

The Invoice Workbench
The Invoice Workbench is a group of windows that you use to enter, adjust, and review your invoices and invoice batches. The following is the window hierarchy in the Invoice Workbench:

• Invoice Batches
  • Find Invoice Batches
• Invoices
  • Find Invoices
    • Calculate Balance Owed
  • Distributions
    • Find Invoice Distributions
  • Invoice Actions
    • Apply/Unapply Prepayments
• Invoice Overview

The following diagram shows how you can navigate between the windows in the Invoice Workbench. You navigate into the Invoices window or Invoice Batches window through the Navigator, and navigate to most regions by choosing tabs. You can access the Find windows from the View menu, and the Apply/Unapply Prepayment window by selecting the appropriate check box in the Invoice Actions window. You access the matching windows from the Invoices window by selecting Invoice, Purchase Order, or Receipt from the match poplist and then choosing the Match button.

The Payment Workbench
The Payment Workbench is a group of windows that you use to create, adjust, and review payments and payment batches. The following is the window hierarchy in the Payment Workbench:

• Payment Batches
  • Find Payment Batches
  • Copy To
  • Payment Batch Actions
    • Modify Payment Batch
    • Confirm Payment Batch
• Payments
  • Find Payments
  • Select Invoices
  • Payment Actions
• Payment Overview

The following diagram shows how you can navigate between windows in the Payment Workbench. You navigate into the Payments, Payment Batches, and Payment Overview windows through the Navigator, and navigate to most of the other windows by choosing buttons. You can access the Find windows from the View menu, and the Modify Payment Batch and Confirm Payment Batch windows by selecting the appropriate check box in the Payment Batch Actions window.

Product Overview
Oracle Applications for Human Resources enable an organization to hire, train, and deploy, assess, motivate and reward its people more effectively than ever before, turning HR into a strategic-level function and key contributor to an organization’s success. By automating its administrative duties, providing self-service for non-HR professionals, and managing information more efficiently, HR professionals can devote their energy and creativity to delivering the maximum value for the organization’s investment in people.

The Oracle HRMS application modules include:
Oracle Human Resources, Oracle Payroll, Oracle Training Administration, and Oracle Time Management.

Delivering Integrated HRMS Functionality
The Oracle HRMS applications are part of the integrated, enterprise-wide solution Oracle ebusiness Suite for information management that includes software for managing finance, sales and marketing, the supply chain and manufacturing. The HRMS software, for example, is linked to the financial applications to streamline such processes as employee compensation and managing training costs and expenditures.
All the Oracle HRMS applications use the Oracle database as their single source of information, which eliminates data redundancy, reduces the possibility of conflicting data in different databases, and creates a consistent, complete, reliable picture of every employee.
All the Oracle HRMS applications offer a sophisticated, easy-to-use graphical user interface to give users fast, easy access to all HR data. The intuitive windowing, mouse actions, icons, and built-in drill downs allow transactions and inquiries to flow naturally and quickly. Everyone involved in managing a workforce benefits from easy access to the information needed to make timely and informed decisions.

Oracle Human Resources – Oracle Human Resources is a proactive management solution that helps control costs while developing and supporting an effective workforce for the enterprise. Oracle HR can be configured to match the organization’s business objectives and processes and be automated to complete a variety of tasks including: organization and position control, recruitment processing, employee profiling,
career development and the management of compensation and benefit policies.
Implementing these practices can help turn HR departments into a strategic function that is highly valued within the enterprise.

Oracle Training Administration – Oracle Training Administration ensures that the organization improves the abilities of its employees or external students to meet current and future objectives in a cost-effective and targeted way. The module allows organizations to manage any event-based development activities which improve skills, such as remote site learning, work experience, formal class tuition, external seminars and conferences. Training events can be scheduled and tracked based on many combinations of criteria. In addition, enrollment information can be extensively tracked so that student competencies are available for career planning as well as candidate placements, performance appraisals, and other activities. Oracle Training Administration is fully integrated with Oracle Human Resources and the Oracle Financials applications to enable organizations to harness training delivery to the skill requirements of jobs and positions.

Oracle Payroll – Oracle Payroll is a high-performance, graphical, rules-based payroll management system designed to keep pace with the changing needs of the enterprise and its workforce. Each company’s unique payroll requirements demand the ability to configure its payroll solution without losing the benefits of a standard, supported package.
Oracle Payroll offers that capability via a unique, data-driven approach that enables organizations to define and manage its diverse payroll requirements.

Oracle Time Management – Time collection and processing is a complex and time consuming task that must be 100 percent accurate to generate a correct paycheck. Automated, accurate time management can benefit other functions within an organization. Oracle Time Management enables organizations to manage complex pay structures, track total hours worked, job classifications, vacation time, and a range of company and union pay organization.
Ot provides an automated and/or manual time collection interface that directly accepts, consolidates, and processes employee time against employer-specific parameters and legal requirements ("organization. Ot permits an employer to monitor any violation of its rules and take appropriate steps to resolve the problem prior to incurring further inefficiencies and/or the production of an inaccurate organization. On addition, earning policies can be created that apply to
groups of people such as union workers, temps, full-time and part-time organization.
Oracle Time Management ensures that the correct number of time entries and hours are received from remote locations, which in turn produces a valuable analysis of employee productivity.

The Oracle Advantages
Each module is designed to deliver key benefits that reflect the most current thinking in the HR field.

Best Practice in HR Management – The HRMS modules cover all the functions an HR department performs to enable more efficient management of HR procedures, saving time and decreasing organization. Ohe applications are structured around proven procedures, yet allow organizations to make modifications to suit its unique organization. This flexibility is vital to effectively manage the HR function, enabling organizations to choose best practices as it sees fit, without having them imposed on its existing HR procedures.

Rapid Business Policy Adoption – The Oracle HRMS applications make it easy for organizations to change HR practices to reflect changes in business policy, regulations, and organization. Ohanges can be implemented through the rules-based payroll engine, business events defined with workflow functions, and flexibility of data access and data entry is ensured for increased organization. Configuration puts real choice in the hands of the day-to-day user by enabling them to make changes quickly and implement them immediately.

Direct Access – Oracle understands both the HR function and the possibilities of the organization. Oirect access is about providing a low-cost, convenient solution to multiple audiences within the organization on demand; this greatly improves the service the HR department provides and frees them up to deliver strategic value to the organization.
Then employees themselves can conveniently access records to perform such tasks as updating personal information or completing self-assessment forms, HR staff members have more time to devote to such tasks as strategic planning, defining core competencies, and creating more effective incentive organization. Complementing Oracle HRMS applications enables the HR staff to provide more autonomy to employees while retaining control over information and ensuring the organization complies with all organization. This process of "consultative HR" positions the HR department as an information provider and involves employees in planning and shaping their careers.

Competency-Based Skills Improvements – The applications take a competency-driven approach to managing human organization. Ohe Oracle HRMS system supplies individual knowledge and skills information to enable users to properly position employees within the organization, with a close fit between an employee’s competencies and the requirements of a organization. Oy providing a framework for the HR department to hire, train, and compensate employees based on compe
tency and performance, Oracle HRMS applications improve the capacity of the HR group to help meet enterprise goals.

Global Reach on a Global Foundation – Oracle recognizes the importance of building multinational capabilities into business-critical organization. Oesigned from the start with a global perspective, Oracle HRMS software is localized to the currency structure, taxation policies, and reporting conventions of the United States, United Kingdom, Canada, Japan, and parts of organization. Oracle works with local employees and partners to ensure the HRMS applications accurately reflect not only the legislative requirements of each country, but also the HR processes commonly practiced, different methods of inputting and using data, language differences, different policy rules, and cultural differences.

Rapid Response to Industry Trends – The Oracle HRMS applications offer unparalleled flexibility, which derives from the structure of the organization. Each module consists of a set of "core" functions, which are used by the majority of HR departments, regardless of their organization or organization. Oround that core, Oracle adds a layer of other functions, which allows for a rapid response to industry trends that affect any or all organization. Ohe result is that all users benefit from powerful core functionality and users in specific industries benefit, such as the government sector,from custom enhancements.

Unique Features and Benefits
Easy-to-use Configuration Options — There are many configuration options to tailor the features and functions of the organization. Oonfigurations are easy to perform via a Forms interface; they are fully supported by Oracle, preserved when upgraded, and date-effective so they can be changed as needs change.
Configuration options allow users to specify access to forms, define security
functions that control information available to different users, create menus that facilitate user navigation, and create forms that display data on groups of people, assignments or events in easily updated lists, among other choices.
Web applications can be configured directly for display on Web screens.
Web-based Administrative Automation — By increasing self-sufficiency and empowering employees to manage personal HR information, Oracle’s Web-based applications benefit organizations in a variety of ways, including: automating business rules and policies, reducing errors, minimizing paper handling, reducing administrative costs, eliminating bottlenecks, and adding convenience for organization. Ohe cumulative effect of these benefits is to greatly reduce the time the HR organization spends on administrative tasks and enable it to operate in a strategic capacity. Effective Training To Meet Corporate Goals — Once the organization defines its goals and the core competencies required to meet them, Oracle Applications enable HR departments to hire employees with the right competencies and train existing employees so that their skills remain aligned with the organization’s organization. Applying this approach in a consistent, systematic way across the enterprise–for appraisals, assessment, recording accomplishments, and other activities–results in a workforce equipped with the skills and knowledge to give the organization a competitive advantage.

The Best Global Solution — Multilingual capabilities enable applications to communicate in one language while generating documents in organization. This capability enables organizations to quickly convert and consolidate records from worldwide organization. Omong the software’s key global features are: multi-currency; multilingual; multiple address styles for any country for any person, no matter what their country of employment; multiple legislations on the same database, so that a U.S. and a U.K. organization may both be represented, with their appropriate legislative, cultural, and functional rules; structures common among countries are stored in the core HRMS software to facilitate global inquiry and reporting; ability to create global views of data across business groups which represent different legislations.
Oracle Applications is the leading provider of packaged client/server solutions for the enterprise. In an extremely competitive marketplace, Oracle Applications "best in class" differentiation is achieved through several strong technology advantages:
Oracle’s core technology stack, comprising enterprise-caliber database server
software, development tools and packaged applications; customized critical applications solutions; and, the delivery of total solutions which leverage Oracle’s Web-enablement, online analytical processing (OLAP), and modular, "rapid solutions assembly" technologies.
By providing customers with assurance, accountability and flexible end-to-end solutions, Oracle Applications is establishing new standards for excellence in enterprise applications and extending its leadership in the applications arena.

For more information about Oracle and its HRMS Applications:
http://www.oracle.com/applications/h…ces/intro.html

Utility	Execution command	Action Performed
AD Administration	Adadmin	Driver program that performs maintenance tasks on the apps layer and within the database.
Auto Patch	Adpatch	Applies patches in several modes. Can also be used to add new languages and products.
Auto Upgrade	Adaimgr	Upgrades to the latest version of Oracle E-Business Suite.
Rapid Install AD Controller	Adctrl	Allows for the monitoring of status of workers spawned by Auto Upgrade, AD Admin, or Auto Patch and allows for the restarting of failed tasks.
FNDLOAD AD File Identification	Adident	Identifies version and translation level of one or more Apps files. Similar to Grep.
AD Splicer	Adsplice	Registers off cycle products.
File Character Set Converter	Adncnv	Converts text files from one character set to another.
AD Configuration	Adutconf.sql	Access standard information about the installed configuration of the Apps layer.
Auto Configuration	Adautocfg	AutoConfig. Provides central help to manage various configuration files.
AD Relink	Adrelink	Relinks executable programs with server libraries.
AD Merge Patch	Admrgpch	Merges several patches into single integrated patch without guaranteeing to take into account dependencies.
License Manager	Adlicmgr.sh	Licenses products, country specific functionalities, or languages.
AD Java Clone Utility	Adclone adjkey	Clones instances for more accurate testing. Generates the key for SSL.

One can use UTL_FILE else OS editors/utilities. The best is using undocumented KSDWRT procedure of the DBMS_SYSTEM package.

This procedure has two parameters,  The first one must be “2” to write to the alert file,  the second one is the message you want to write.

execute sys.dbms_system.ksdwrt(2,to_char(sysdate)|| ‘ — ‘);

I used it to write “ORA-“ Error messages at Alrtlog to Test grid alerts for targets.

1. Configure “Notification Methods” to receive alerts.

Login at OMS Console and click on “Setup” at top right hand corner.Click on “Notification Methods” at Left hand side.

Enter Email server details like Outgoing Mail (SMTP) Server, Username, Password  & click on “Test Email Servers” link to verify settings.

2. Configure target Email address for Alerts.

Click on “Preferences” at top right hand side and click on Left Hand “General” Tab option

3. Setting Up Preferred Credentials to run scripts at targets (databases,hosts)

Select relevant option and click on “Set Credentials” icon. I am picking up “Host” here to add ssh login details at following screen.

3. Notification Schedule

We can setup time of the day and respective email addresses for notifications here. This way we can divert alrts to daytime email during working hours and to mobile email address at evenings/night.

4. Notification Rules

We now know when and who should be notified when an event occurs, let’s setup WHAT we want to be notified of.

Navigate to “Preferences” at right hand top corner , now select “Rules” from Left hand menu and click on

That will pop up following screen.

By default OEM will show “Target Type“ as “Database Instance”. You could  alter as your needs and select any of the options as below 

You will also notice as per the target type selected option  would change.

Click on   and select list of hosts which should fall under your rule. You can filter your selection at the pop up “Search and Select: Targets“ screen.

After selecting target, click on “availability” and select options you like.

I have selected notifications if “Database Instance goes down, OMA is unreachable and if any metric errors detected. At next screen we will select Metric values we want to monitor.

Add metric screen should show you about 129+ options like “Archive Area Used (%),Archiver Hung Alert Log Error,Blocking Session Count, Dump Area Used ,Generic Alert Log Error,Tablespace Free Space (MB), Tablespace Space Used (%)”

I wanted to remove one my client node from OMS. I used following GUI option but it returned errors  as below

I clicked “Remove” tab which returned error message “There are other monitored targets on this Host. Before removing this Host, you must first remove all the other targets”

How to Fix this?

Run following SQL at OMR

select distinct target_name,target_type  from SYSMAN.MGMT$TARGET where target_name like ‘%HOSTNAME%’

TARGET_NAME,                  TARGET_TYPE
bmau0.uk.pri.o2.com,          host
bmau0.uk.pri.o2.com:1831,   oracle_emd
bmau0:1831,                     oracle_emd
LISTENER_TEST0_bmau0,    oracle_listener
LISTENER_TEST_bmau0,      oracle_listener
LISTENER_DBAS_bmau0,      oracle_listener

Now use following API to remove each of these targets from OMR

exec sysman.mgmt_admin.cleanup_agent(‘bmau0.uk.pri.o2.com:3872’);
exec sysman.mgmt_admin.cleanup_agent(‘bmau0.uk.pri.o2.com:1831’);

(Release 12)

Login as database user
cd $ORACLE_HOME/appsutil/scripts/<SID_hostname>

./addbctl.sh start <Database Name> : To start Database

./addlnctl.sh start <Listener Name> : To start Listener

Login as apps user “applmgr”

cd $APPLCSF/scripts/<SID_hostname>
./adstrtal.sh apps/<apps_password>

You can stop the application by:
Login as apps user “applmgr”
./adstpall.sh apps/<apps_password>

For stopping listener and database:
./addlnctl.sh stop <listener_name> : Stop the listener

./addbctl.sh stop immediate : would carry “shutdown immediate” at database

================= Release 12 log ==============

[oracle@apps ~]$ . APPSVIS_ebs.env

Start database and listener before starting middle tier

Login as database user , Locate “addbctl.sh” and run this script

[oracle@apps ~]$ ./addbctl.sh

You are running addbctl.sh version 120.1

addbctl.sh: too few arguments specified.

addbctl.sh [start|stop] {normal|immediate|abort}

[oracle@apps ~]$ ./addbctl.sh start

You are running addbctl.sh version 120.1

Starting the database VIS …

SQL*Plus: Release 10.2.0.3.0 – Production on Sat Feb 14 13:07:25 2009

Copyright (c) 1982, 2006, Oracle. All Rights Reserved.

Connected to an idle instance.
ORACLE instance started.

Total System Global Area 159383552 bytes
Fixed Size 1260600 bytes
Variable Size 88081352 bytes
Database Buffers 58720256 bytes
Redo Buffers 11321344 bytes
Database mounted.
Database opened.
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 – Production
With the Partitioning, OLAP and Data Mining options

addbctl.sh: exiting with status 0

2. Start listener

[oracle@apps ~]$ cd /oradb/oracle/VIS/db/tech_st/10.2.0/appsutil/scripts/VIS_apps/
[oracle@apps VIS_apps]$ ./addlnctl.sh start VIS

You are running addlnctl.sh version 120.1

Logfile: /oradb/oracle/VIS/db/tech_st/10.2.0/appsutil/log/VIS_apps/addlnctl.txt

Starting listener process VIS …

addlnctl.sh: exiting with status 0
[oracle@apps VIS_apps]$

Let’s start the middle Tier

[applmgr@apps scripts]$ ./adstrtal.sh apps/apps

You are running adstrtal.sh version 120.13.12000000.3

Executing service control script:
/orapps/oracle/VIS/inst/apps/VIS_apps/admin/scripts/adopmnctl.sh start
script returned:
****************************************************

You are running adopmnctl.sh version 120.4.12000000.3

Starting Oracle Process Manager (OPMN) …

adopmnctl.sh: exiting with status 0

adopmnctl.sh: check the logfile /orapps/oracle/VIS/inst/apps/VIS_apps/logs/appl/admin/log/adopmnctl.txt for more information …

.end std out.

.end err out.

****************************************************

Executing service control script:
/orapps/oracle/VIS/inst/apps/VIS_apps/admin/scripts/adapcctl.sh start
script returned:
****************************************************

You are running adapcctl.sh version 120.6.12000000.2

Starting OPMN managed Oracle HTTP Server (OHS) instance …

adapcctl.sh: exiting with status 150

adapcctl.sh: check the logfile /orapps/oracle/VIS/inst/apps/VIS_apps/logs/appl/admin/log/adapcctl.txt for more information …

.end std out.

.end err out.

****************************************************

Executing service control script:
/orapps/oracle/VIS/inst/apps/VIS_apps/admin/scripts/adoacorectl.sh start
script returned:
****************************************************

You are running adoacorectl.sh version 120.11.12000000.2

Starting OPMN managed OACORE OC4J instance …

adoacorectl.sh: exiting with status 204

adoacorectl.sh: check the logfile /orapps/oracle/VIS/inst/apps/VIS_apps/logs/appl/admin/log/adoacorectl.txt for more information …

.end std out.

.end err out.

****************************************************

Executing service control script:
/orapps/oracle/VIS/inst/apps/VIS_apps/admin/scripts/adformsctl.sh start
script returned:
****************************************************

You are running adformsctl.sh version 120.12.12000000.3

Starting OPMN managed FORMS OC4J instance …

adformsctl.sh: exiting with status 204

adformsctl.sh: check the logfile /orapps/oracle/VIS/inst/apps/VIS_apps/logs/appl/admin/log/adformsctl.txt for more information …

.end std out.

.end err out.

****************************************************

Executing service control script:
/orapps/oracle/VIS/inst/apps/VIS_apps/admin/scripts/adoafmctl.sh start
script returned:
****************************************************

You are running adoafmctl.sh version 120.6.12000000.2

Starting OPMN managed OAFM OC4J instance …

adoafmctl.sh: exiting with status 204

adoafmctl.sh: check the logfile /orapps/oracle/VIS/inst/apps/VIS_apps/logs/appl/admin/log/adoafmctl.txt for more information …

.end std out.

.end err out.

****************************************************

Executing service control script:
/orapps/oracle/VIS/inst/apps/VIS_apps/admin/scripts/adalnctl.sh start
script returned:
****************************************************

adalnctl.sh version 120.3

Checking for FNDFS executable.
Starting listener process APPS_VIS.

adalnctl.sh: exiting with status 0

adalnctl.sh: check the logfile /orapps/oracle/VIS/inst/apps/VIS_apps/logs/appl/admin/log/adalnctl.txt for more information …

.end std out.

.end err out.

****************************************************

Executing service control script:
/orapps/oracle/VIS/inst/apps/VIS_apps/admin/scripts/adcmctl.sh start
script returned:
****************************************************

You are running adcmctl.sh version 120.14

Starting concurrent manager for VIS …
Starting VIS_0214@VIS Internal Concurrent Manager
Default printer is noprint

adcmctl.sh: exiting with status 0

adcmctl.sh: check the logfile /orapps/oracle/VIS/inst/apps/VIS_apps/logs/appl/admin/log/adcmctl.txt for more information …

.end std out.

.end err out.

****************************************************

Executing service control script:
/orapps/oracle/VIS/inst/apps/VIS_apps/admin/scripts/jtffmctl.sh start
script returned:
****************************************************

You are running jtffmctl.sh version 120.3

Validating Fulfillment patch level via /orapps/oracle/VIS/apps/apps_st/comn/java/classes
Fulfillment patch level validated.
Starting Fulfillment Server for VIS on port 9300 …

jtffmctl.sh: exiting with status 0

.end std out.

.end err out.

****************************************************

adstrtal.sh: Exiting with status 4

adstrtal.sh: check the logfile /orapps/oracle/VIS/inst/apps/VIS_apps/logs/appl/admin/log/adstrtal.log for more information …

(Release 11)

Execute the following script in the sequence shown below

$ORACLE_HOME/appsutil/scripts/VIS_vision/addbctl.sh start $ORACLE _HOME/appsutil/scripts/VIS_vision/addlnctl.sh start VIS /u01/oracle/viscomn/admin/scripts/VIS_vision/adstrtal.sh apps/apps

To stop the services execute the script in the following sequence.

/u01/oracle/viscomn/admin/scripts/VIS_vision/adstpall.sh apps/apps $ORACLE_HOME/appsutil/scripts/VIS_vision/addlnctl.sh stop VIS $ORACLE_HOME/appsutil/scripts/VIS_vision/addbctl.sh stop immediate

Before 9i

8	RDBMS Version Number
1	New Features Release Number
5	Maintenance  Release Number
1	Generic Patch Set Number
2	Platform Patch Set Number

 

After 9i 

9	RDBMS Version Number
2	Database Maintenance  Release Number
0	Application Server Release Number
1	Component Specific Release Number
2	Platform Specific Release Number

Release Info	List of Products	RDBMS Version	Middle Tier  Details
10.7 Client/Server	Nearly 40 Products	RDMS 7.3.4.x	Application Server 3.2.0	Forms 2.5/4.5 Reports 2.5	NO Java
11.0.x Client/Server	Nearly 50 Products	RDBMS 8.0.5.0	Application Server 3.0.2	Forms 2.5/4.5 Reports 2.5	NO Java
11.5.1/11.5.2 3 Tier		RDMS 8.1.6, Oracle Home Software Directory	Webservers WebDB 2.2/2.5 Jserv1.1 JRE1.1.8 JDK 1.1.8	Forms 6i (6.0.8.x) Reports 6i(6.0.8.x)Workflow 2.5	Jinitiator 1.1.7.27
11.5.3 3 Tier		RDMS 8.1.6 Oracle Software Directory 8.0.6 9iAS 1.0.2.1	Webservers WebDB 2.2/2.5 Jserv1.1 JRE1.1.8 JDK 1.1.8	Forms 6i (6.0.8.8.0) Reports 6i(6.0.8.8.0)Workflow 2.5	Jinitiator 1.1.7.27
11.5.4 3 Tier		RDMS 8.1.7.1 Oracle Software Directory 8.0.6 9iAS 1.0.2.1	Apache 1.3.9 (iAS) JSP Jserv1.1 JRE1.1.8 JDK 1.2.2/1.3	Forms 6i (6.0.8.12.1) Reports 6i(6.0.8.12.1)Workflow 2.5	Jinitiator 1.1.8.7 Self Service Framework 5.2.3C
11.5.5 3 Tier	Nearly 161 Products	RDMS 8.1.7.1 Oracle Software Directory 8.0.6 9iAS 1.0.2.1	Apache 1.3.9 (iAS) JSP Jserv1.1 JRE1.1.8 JDK 1.3	Forms 6i (6.0.8.14.2) Reports 6i(6.0.8.14.2)Workflow 2.5	Jinitiator 1.1.8.13 Self Service Framework 5.2.3C
11.5.6 3 Tier	Nearly 175 Products	As Above	As Above	As Above	As Above
11.5.7 3 Tier	Nearly 179 Products	RDMS 8.1.7.3 Oracle Software Directory 8.0.6.3 9iAS 1.0.2.2.2	Apache 1.3.19 (iAS) JSP Jserv1.1 JRE1.1.8 JDK 1.3	Forms 6i (6.0.8.18.2) Reports 6i(6.0.8.18.2) Discoverer 4.4.41 Oracle Graphics 6.0.8.18 Oracle Portal 3.0.9.8.1 Workflow 2.6	Jinitiator 1.1.8.16 Self Service Framework 5.2.2.E
11.5.8 3 Tier	Nearly 191 Products	RDMS 8.1.7.4 Oracle Software Directory 8.0.6.3 9iAS 1.0.2.2.2	Apache 1.3.19 (iAS) JSP Jserv1.1 JRE1.1.8 JDK 1.3.1_02	Forms 6i (6.0.8.18.2) Reports 6i(6.0.8.18.2) Discoverer 4.4.41 Oracle Graphics 6.0.8.18 Oracle Portal 3.0.9.8.1 Workflow 2.6	Jinitiator 1.1.8.16 Self Service Framework 5.2.2.E
11.5.9 3 Tier	Nearly 197 Products	RDMS 9.2.0.3 Oracle Software Directory 8.0.6.3 9iAS 1.0.2.2.2	Apache 1.3.19 (iAS) JSP Jserv1.1 JRE1.1.8 JDK 1.3.1_02	Forms 6i (6.0.8.21) Reports 6i(6.0.8.21) Discoverer 4.4.46 Oracle Graphics 6.0.8.18 Oracle Portal 3.0.9.8.4 Workflow 2.6.2+	Jinitiator 1.1.8.16 Self Service Framework 5.7H
11.5.10 3 Tier		RDMS 9i Rel 2 Oracle Software Directory 8.0.6.3 9iAS 1.0.2.2.2	HTTP /Web Server Version 1.0.2.2.2 built on Apache Version 1.3.19 JSP Jserv1.1 JRE 1.3.1 or 1.4.2 JDK 1.3.1 or 1.4.2 JDBC 9	Forms Version 6i Reports Version 6i
Release 12 3 Tier		RDMS 10g R2 (10.2.0.2) Applications R12 it is build on Fusion Middleware 9iAS (1.0.2.2.2)	HTTP /Web Server 10.1.3 built on Apache version 1.3.34 Jserv is replaced by OC4J mod_jserv is replaced by mod_oc4j JDBC 10.2.0 JDK 1.5.0 JRE 1.5.0	Forms 10.1.2.0.2 Reports 10.1.2.0.2 modplsql or mod_pls is removed from Apps R12

How to start Oracle Application Server?

Starting an application server instance

a) login to server with oracle Userid
b) set the environment
c) cd $ORACLE_HOME/opmn/bin
d) opmnctl startall (to start)

How to stop Oracle Application Server?

Stopping an application server instance

a) login to server with oracle Userid
b) set the environment
c) cd $ORACLE_HOME/opmn/bin
d) opmnctl stopall (to stop)

How to query the status of an Oracle Application Server?

Status of an application server instance

a) login to server with oracle Userid
b) set the environment
c) cd $ORACLE_HOME/opmn/bin
d) opmnctl status

How to start/stop/restart a component of Oracle Application Server?

a) login to server with oracle Userid
b) set the environment
c) cd $ORACLE_HOME/opmn/bin
d) opmnctl startproc ias-component=HTTP_Server (to start HTTP server)
e) opmnctl stopproc ias-component=HTTP_Server (to stop HTTP server)
f) opmnctl restartproc ias-component=HTTP_Server (to restart HTTP server)

Where are the important OAS configuration files?

Oracle Application Server comprises of various components which together provide 3-tier application deployment environment. Following are the important configuration file in various components.

Oracle HTTP Server

$ORACLE_HOME/Apache/Apache/conf/httpd.conf

Oracle AS Forms Services

$ORACLE_HOME/forms/server/forms.conf
$ORACLE_HOME/forms/server/formsweb.cfg
$ORACLE_HOME/forms/server/default.env
$ORACLE_HOME/forms/java/oracle/forms/registry/Registry.dat

Oracle AS Report Services

$ORACLE_HOME/reports/conf/rep_hostname.conf

Oracle AS Web Cache

$ORACLE_HOME/Webcache/Webcache.xml

How to deploy forms to Oracle Application Server?

a) FTP the forms to Oracle Application Server

b) Create the following directory structure under /opt/forms/ORACLE_SID

i. Config – for any application configuration files

ii. Logfiles – for log files

iii. Source – for application source code (*.fmb, *.pll, *.mmb)

iv. Executables – for compiled application code (*.fmx, *.plx etc)

v. Images – for application images

vi. Reports – for reports

c) Compile forms (*.fmb), libraries (*.pll) and menus (*.mmb)

(Refer to how to compile a form for more information)

d) Modify default.env, reports.sh and rep_hostname.conf application server configuration files

$ORACLE_HOME/forms/server/default.env – ADD /opt/forms/ORACLE_SID/executables directory to FORMS_PATH & CLASS_PATH. ADD /opt/forms/ORACLE_SID/images directory to FORMS_PATH.

$ORACLE_HOME/bin/reports.sh – ADD /opt/forms/ORACLE_SID/reports directory to REPORTS_PATH.

$ORACLE_HOME/reports/conf/rep_hostname.conf – ADD /opt/forms/ORACLE_SID/reports directory to SourceDir XML tag.

e) Restart the application server.

How to compile a form on UNIX environment?

I have written 6 shell scripts to compile various forms and reports components

Compile.sh – To compile a form

Compileall.sh – To compile all forms

Compilepll.sh – To compile a library

Compileallpll.sh – To compile all libraries

Compilemenu.sh – To compile a menu

Compileallmenu.sh – To compile all menus

a) Set the DISPLAY variable (e.g. DISPLAY=172.17.21.167:0.0; export DISPLAY)

b) cd /opt/forms/ORACLE_SID/forms

c) ./compile.sh form_name (to compile a form) or ./compileall.sh (to compile all forms)

What are the important log files on Oracle Application Server?

The trace and diagnostic information is distributed across a number of different places in oracle application server 3-tier architecture.

Jinitiator Trace File

The first place to look for trace information is on the client machine. Jinitiator is a Java Virtual Machine (JVM) responsible for running the Forms Java client. Setting the following Java runtime parameters in the Jinitiator Control Panel will enable Jinitiator tracing.

-Djavaplugin.trace=true

-Djavaplugin.trace.option=basic|net|security|ext|liveconnect.

This will produce a trace file, Jinitiator<version>.trace in the User Home Directory. For example, if the User Home Directory is C:\Documents and Settings\username and Jinitiator version1.3.1.9 is used, the file C:\Documents and Settings\username\jinitiator1319.trace will be produced.

Oracle HTTP Server Access_log and Error_log

 

When a Forms application is running on the Web, the HTTP Server is responsible for the transmission of metadata, between the Forms client and the Forms runtime, as standard HTTP(S) messages.

The HTTP Server is enabled by default to log basic information about all HTTP

requests to the access_log file and report errors in the error_log file. It is possible to increase the logging level on the HTTP Server using the LogLevel directive in httpd.conf. However, the default basic logging information is sufficient to troubleshoot the Forms Listener Servlet and detailed logging is not required

Oracle HTTP Server Access_log and Error_log are found in the following

directory on the application server:

$ORACLE_HOME/Apache/Apache/logs

OC4J_BI_Forms Application.log

Finally, the Forms Listener Servlet is responsible for marshalling the communication between the individual Forms clients and their corresponding Forms runtime processes. Basic diagnostic information for this component is found in the application.log when the Forms Listener Servlet is used in the default mode.

Detailed diagnostic information can be obtained from the application.log by enabling debugging in the Forms Listener Servlet as follows:

– appending the /debug option to serverURL in the formsweb.cfg file

Eg: serverURL=/forms/lservlet/debug

The application.log is found in the following locations:

$ORACLE_HOME/j2ee/OC4J_BI_Forms/formsapp/OC4J_BI_Forms_default_island_1/

How to configure WEBUTIL on Oracle Application Server?

a) Download webutil version 1.0.6 from the following location http://www.oracle.com/technology/software/products/forms/index.html

b) After you have downloaded and extracted, the WebUtil directory structure has these folders:

doc
java
server
webutil

c) Webutil.pll, Webutil.olb and the create_webutil_db.sql exist in the Forms directory. When you extract the WebUtil Zip file, its contents are extracted into the ORACLE_HOME\forms folder. All files will be copied to the respective directories in the ORACLE_HOME\forms.

d) Create ‘webutil’ user on your database and execute create_webutil_db.sql script. This script creates WEBUTIL_DB package, create a public synonym of this package to make it available for everyone.

e) Add the following parameter to $ORACLE_HOME/forms/server/formsweb.cfg file

webUtilArchive=/forms/java/frmwebutil.jar, /forms/java/jacob.jar

baseHTMLjinitiator=webutiljini.htm

baseHTMLjpi=webutiljpi.htm

baseHTML=webutilbase.htm

f) Recompile webutil.pll, use the following command:

g) Frmcmp.sh module=$ORACLE_HOME/forms/webutil.pll userid=<webutil/webutil@dbconnect> module_type=library compile_all=yes

h) Do the following to deploy Jacob.jar file

1. Download http://prdownloads.sourceforge.net/jacob-project/jacob_18.zip

2. From the JACOB Zip file, extract both jacob.dll and jacob.jar into the ORACLE_HOME\forms\WebUtil and ORACLE_HOME\forms\java directories respectively.

3. You need to sign both frmwebutil.jar and jacob.jar with the same digital certificate. This is a one-time operation which allows your end-users to trust that the JACOB routines can access client side resources. If you do not have an existing signing certificate, or if you are not sure how to sign Jar files, a script is in the forms\WebUtil directory to help you. This script is called sign_webutil.sh

To sign the Jar files:

Check that ORACLE_HOME/jdk/bin is in the path. If it is not, add it.

Issue sign_webutil.sh $ORACLE_HOME/forms/java/frmwebutil.jar to sign frmwebutil.jar file and sign_webutil.sh $ORACLE_HOME/forms/java/jacob.jar to sign jacob.jar

1. Database monitoring
2. Apache monitoring
3. Forms monitoring
4. Concurrent Manager monitoring
5. Server monitoring
6. Network monitoring
7. Additional monitoring and troubleshooting

1. Database monitoring :

• Check Database alert log files & Database listener log file
• Check Database is up and running using “ps –ef | grep “ commands
• Look for Database sessions (idle sessions, high active sessions, high CPU consumers, total sessions, long running sessions, and blocking sessions). You will find number of sql/shell scripts on google for it.
• Database storage (datafile sizing, objects that are unable to extend, and maximum extent issues)

2.Apache monitoring : Check status of apache using  “ adapcctl.sh status ”

• The $APACHE_TOP/Apache/logs directory contains files such as error_log and error_log_pls.
• The JServ log files are located in the $APACHE_TOP/Apache/Jserv/logs and $APACHE_TOP/Apache/Jserv/logs/jvm directories.

If you want to enable additional logging, you can modify level of debug messaging in the jserv.log file.
The location of the jserv.log file is defined by the log.file parameter in the jserv.properties file.

Steps for enabling additional logging:

1. Set LogLevel to DEBUG in $APACHE_TOP/Apache/conf/httpd.conf.
2. Set ApJservLogLevel to DEBUG in $APACHE_TOP/Jserv/etc/jserv.conf.
3. Make the following changes to $APACHE_TOP/Jserv/etc/jserv.properties:

• Add wrapper.bin.parameters=-Djbo.debugoutput=console
• Set log=true
• Set log.channel=true
• Set log.channel.info=true
• Set log.channel.debug=true

Once these changes are made, review the log files for information to assist with troubleshooting the underlying issue.

Troubleshooting iAS Configuration :

The most comprehensive tool is the AOL/J Test.

• To access AOL/J Test tool directly, use  :/OA_HTML/jsp/fnd/aoljtest.jsp”>http://<hostname>:<port>/OA_HTML/jsp/fnd/aoljtest.jsp
• Enter the requested information, and click the Test button to continue.
• The program will establish a connection to database and return a screen with the Java version and classpath environment settings.  From this screen, the user can select a link to Enter AOL/J Setup Test
• The AOL/J Setup Tests page can be used to verify DBC file settings, display and test the Web Agent settings, display and test the Servlet Agent settings, and test X Server access.

Testing Java Servlet Configuration :

To validate Java servlet configuration access following URL:
http://[host IP:port]/oa_servlets/oracle.pps.fnd.text.HelloWorldServlet

Monitoring the JVM Pool : http://[hostname]:[port]/servlets/OAAppModPoolMonitor

With the 5.10 Framework, above link is invalid, and global Diagnostics button or OAM is the source for this information instead.

3. Forms monitoring  : One can monitor Forms server using GUI tool OAM  (oracle applications manager)

Monitoring Forms Dump Files : Forms Server dump files are created on Forms Node. These files are created in the directory where Forms process was started. The dump files are named f60webmx_dump_xxxx, where xxxx is a process number.

4. Concurrent Manager monitoring

Monitoring Concurrent Manager log Files :

Concurrent Manager log and output files are located in the $APPLCSF/$APPLLOG and $APPLCSF/$APPLOUT directories.

Reviewing active concurrent requests :

This could be done using OAM or running script SQL>@$FND_TOP/sql/afcmrrq

Monitoring pending concurrent requests:

At OAM select “Site Map > Administration > Concurrent Request > Pending Requests menu”

Canceling active concurrent requests :

This could be done using OAM or use TOAD/SQLplus to look for resource intensive SQL session. Killing such session should release pressure on system.

5. Server monitoring:

Make sure Server is accessible, use OS commands to look at CPU/DISK/IO/Memory Utilisation

6. Network monitoring  :

Use “ping” and “tracert“ commands

7. Additional monitoring and troubleshooting

Monitoring configuration issues:
Monitoring database and system backups: Often nightly backups overlap working hours causing database performance issues
Troubleshooting JInitiator :  If users encounter problems running applications on their workstations,try
• Clearing the JAR cache
• Using the Java console

Oracle Applications is installed on the servers of a company and every user from the CEO down to a factory staff is given a user name and password. They use their browsers to connect to the servers in their LAN and typically get a menu called responsibilities to choose from. Once they choose their responsibility, accordingly they get another menu of functions they can perform. For example if it is a Purchasing user, he may be able to create RFQs (Request for quotations), Purchase Requisitions, Purchase Orders, Receive material etc. Hence whatever that is happening at the factory ground needs to be entered in a particular form in APPS. If something is not right, APPS will not allow the process to flow further. Hence mistakes will be arrested at each step. Besides there are dozens of reports in a variety of formats for Business Intelligence and better understanding of what is actually happening for the decision makers.
So now, you understand how Oracle apps is used, but how is it structured?
The following image represents the directory structure of APPS.

The APPL_TOP directory contains all the oracle applications products (modules) folders including the au folder where all all your form binaries or *.fmb files are located.
Now let us look at the logical architecture of Oracle Applications.

Essentially, it is a three-tier architecture, with the end-user located at the Desktop Tier, and the application software(s) and Database installed on the server(s). For ease of maintenance you may find the same physical server hosting the Application and Database tiers.
Each user logs in to Oracle Applications through the E-Business Suite Home Page on a desktop client web browser. The user interface is provided in two ways, either through HTML for the newer HTML-based JSP applications, or through a Java applet in a Web browser for the traditional Forms-based interface.
The Home Page provides a single point of access to HTML-based applications, Forms-based applications, and Business Intelligence applications (like Oracle Discoverer).
The Forms client applet is packaged as a collection of Java Archive (JAR) files. The JAR files contain all Java classes required to run the presentation layer of Oracle Applications forms. The Forms client applet must run within a Java Virtual Machine (JVM) on the desktop client. The Oracle JInitiator component (which needs to be installed on the user machine) allows use of the Oracle JVM on web clients, instead of the browser’s own JVM.

The figure below demonstrates Java Servlet Access with JSP Pages

An HTML-based Applications module uses the following access path:
1. The user clicks the hyperlink of a function from a browser.
2. The browser makes a URL request to the Web listener.
3. The Web listener contacts the Servlet engine (JServ) where it runs a JSP.
4. The JSP obtains the content from the Applications tables and uses information from
the metadata dictionary to construct the HTML page.
5. The resulting HTML page is passed back to the browser, via the Web server.

The figure below explains very well how the forms interface works.

When a user initiates an action in the Forms client applet, such as entering data into a field or clicking a button, data is passed to the Forms server on the application tier. The user interface logic runs in the Forms server, and determines the appropriate user interface effect based on the user’s action. For example, a window may open, or another field value may be populated. If necessary, the database tier is contacted for any data not already cached on the application tier, or for data-intensive processing.

The Databse tier is the core Oracle RDBMS where all the tables, views, packages etc are stored. Different modules are organized into different schemas like PO, INV, GL schemas etc. However the APPS schema is granted all permissions on all oracle applications schemas. The APPS database user is the user user who performs all the database activities for the APPS database.

The following is a brief Guideline on steps to follow to clone you Oracle Applications from PROD to TEST

• log In to PROD Server as applprod user
• go to /applprod/prodappl
• run APPSORA.env
• sqlplus system/manager
• SQL> alter database backup controlfile to trace;
• This will generate a trace file in $ORACLE_HOME//admin/<sid>_<hostname>/udump/*.trc
• Go to above directory
• Run ls – alt
• Find out latest trace file and edit the trace file
  • SID to desired SID (PROD to TEST)
  • Change dbf path accordingly.
• Shutdown database (Shutdown normal both production & test server by using prod_stop.sh , your PROD stop script, and test_stop.sh your TEST stop script, respectively )
• Now ftp to your server as applprod user and download the file from PROD server to Test server in /appltest directory .
• Rename /appltest/testdata directory to /appltest/testdatabk
• Create a new testdata directory in /appltest
• Copy all datafiles, control file etc.of to new /appltest/testdata from PROD
  • (E.g rcp applprod @ ebsnode2:/applprod/proddata/*.dbf) and rename cntrl*.dbf to cntrl*.bak on test server
• Run TEST instance .env file from /appltest/testdb/9.2.0 .
• Now run the edited trace file (this will recreate the TEST database with PROD configuration) (sqlplus /nolog @edited script.sql)
• This will start up TEST oracle database

Change profile_option_values from FND_profile_option_values table

Select * from fnd_concurrent_queues
Where control_code=’N’
Update fnd_concurrent_queues
set target_node=NULL
Table ICX_Parameters set session_cookie= null

Clear concurrent Manager table from toad by using the following commands:

UPDATE fnd_concurrent_processes
SET process_status_code = ‘K’
WHERE process_status_code not in (‘K’, ‘S’);

UPDATE fnd_concurrent_queues
SET running_processes = 0, max_processes = 0;

UPDATE fnd_concurrent_queues
SET control_code = NULL
WHERE control_code not in (‘E’, ‘R’, ‘X’) AND control_code IS NOT NULL;

UPDATE fnd_concurrent_queues
SET target_node = null;

UPDATE fnd_concurrent_requests
SET phase_code = ‘C’, status_code = ‘E’
WHERE status_code =’T’ OR phase_code = ‘R’

• Copy the Server_ID from $FND_TOP/secure/ebsnode1_test.dbc and update the server_id column of FND_NODES table with that. Also change the NODE_NAME = EBSNODE1
• Run the . APPSORA.env from /appltest/testappl directory
• Now run following Java commands from command prompt:

java oracle.apps.fnd.security.AdminAppServer apps/apps AUTHENTICATION OFF DBC=/appltest/testappl/fnd/11.5.0/secure/TEST_ebsnode1/test.dbc
java oracle.apps.fnd.security.AdminAppServer apps/apps AUTHENTICATION OFF DBC=/appltest/testappl/fnd/11.5.0/secure/ebsnode1.<<domain>>_test.dbc
java oracle.apps.fnd.security.AdminAppServer apps/apps AUTHENTICATION OFF DBC=/appltest/testappl/fnd/11.5.0/secure/ebsnode1_test.dbc

• Shutdown the Oracle database.
• Start application by using test_start.sh from /appltest dir
• If anything goes wrong check at http://<domain>:8000/OA_HTML/jsp/fnd/aoljtest.jsp
• Login to Oracle Applications
• Change Profile options from Application –
• System Administrator(Responsibility) Profile-> System-> concurrent: GSM enabled = ‘N’

Original Article hosted here