neo is alive

Internet Explorer Crashes When Forms Is Launched

2009-01-17T20:08:00.000-08:00

Internet Explorer Crashes When Forms Is Launched

Applies to:

Oracle Applications Technology Stack - Version: 11.5.2 to 11.5.10
This problem can occur on any platform.

Symptoms

You are attempting to launch any form function from the framework home page in applications E-business Suite 11i. When doing so, Internet Explorer crashes resulting in the following error:

Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience.

Figure 1

Changes

One may of recently installed or upgraded an application on their client PC, however this is not always the case

Cause

The problem can have various causes but generally is caused by incompatibilities between shared dll's

Solution

To attempt to resolve the problem please do the following.

When the error appears select the link "To see what data this error report contains, click here" as seen in Figure 1

You will then see something similar to the following screen

Figure 2

Select the link "To view technical information about the error report, click here". The following screen will then appear

Figure3

Obtain the error report file. Note, instead of the white box you will see the user name of the user signed in to the client PC at the time of the error.

Open the error report file.

Here is an extract of an error report file. I have highlighted the important fields in bold.

<MATCHING_FILE NAME="custsat.dll" SIZE="33792" CHECKSUM="0xA30E1EC0" BIN_FILE_VERSION="9.0.3790.2428" BIN_PRODUCT_VERSION="9.0.3790.2428" PRODUCT_VERSION="9.0.3790.2428" FILE_DESCRIPTION="custsat" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="9.0.3790.2428 (srv03_sp1_qfe.050422-1043)" ORIGINAL_FILENAME="custsat.dll" INTERNAL_NAME="custsat" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0xD494" LINKER_VERSION="0x50002" UPTO_BIN_FILE_VERSION="9.0.3790.2428" UPTO_BIN_PRODUCT_VERSION="9.0.3790.2428" LINK_DATE="11/08/2006 05:03:34" UPTO_LINK_DATE="11/08/2006 05:03:34" VER_LANGUAGE="English (United States) [0x409]" />

You are looking for the first occurrence of the value for "MATCHING_FILE_NAME" and "SIZE". These values indicate which file has the issue and what the file size is.

Search the client operating system for the file name listed. There may be multiple occurrences so look for a file size that matches what is listed in the report file.
Observe which directory this file resides in.

e.g. C:\Program Files\Windows Media Player

Using a search engine such as Google http://google.com search for the problem dll. Determine what this dll is used for. In the above example the search engine
reveals that custsat.dll is used for Windows Media Player. This is reinforced by the directory in which the file exists in.

Here is where the solution can get somewhat tricky. In most cases you can simply un-install the program that owns the dll and the problem should be resolved.

If you actually need the application try un-installing it and re-installing it. You may also try un-installing the application, un-installing Jinitiator, re-installing Jinitiator and then re-installing the application.

If you are running Internet Explorer 7 please make sure you meet the minimum requirements as follows:

- E-Business Suite Release 11i version 11.5.9.CU2
- Oracle Developer 6i patchset 18 (6.0.8.27.x) or later
- Oracle Applications Technology 11i.ATG_PF.H Rollup 4 (RUP 4) (Patch 4676589)
- JInitiator 1.3.1.x
- Desktop clients running Microsoft Windows XP

For complete details about this configuration, see:
Recommended Browsers for Oracle Applications 11i (Metalink Note 285218.1)

If you find that the problem dll actually exists in the Internet Explorer directory e.g. hmmapi.dll then please follow the steps below:

Obviously, un-installing Internet Explorer is not an option. Note: you will find that the Mozilla Firefox browser will work and this has the potential to be a workaround here.

The likely cause of the issue is an incompatibility between Jinitiator and a 3rd-party browser extension. You can test this by disabling 3rd-party browser extensions as follows: Navigate IE - Tools - Internet Options - Advanced - untick 'enable third-party browser extensions'

Re-start IE and re-test. Again, this is only a workaround and will help define the root cause of the issue. If the issue no longer happens please read on

As proven in the previous step the problem is related to a 3rd party browser extension. At present there are some extensions that may cause conflicts with Jinitiator. These are:

Windows Live Toolbar, Windows Live Toolbar Helper, Windows Live Messenger, McAfee Site Advisor

If you have any of the above extensions installed try manually disabling them by selecting the extension and Selecting the disable button. Re-start IE and re-test the issue.

Navigate: Tools - Internet Options - Programs - Manage Addons Button

This plugin loads the (native) JRE used in Internet Explorer. However the native JRE is not compatible with the JRE on which Jinitiator 1.3.1 is based. So when Jinitiator is started is will try to 'reuse' the incompatible jvm.dll already loaded and this causes the error as seen.

To resolve the problem please use one of the following work-arounds at your convenience:

1. Disable the plugin (see above)

2. Remove the software via add/remove programs in the control panel

3. Use a different browser than Internet Explorer for running Applications

see Recommended Browsers for Oracle Applications 11i (Metalink Note 285218.1)

4. A definite solution will come from using the (same) native JRE to run Forms (instead of using Jinitiator). Follow the steps from Note 290807.1 "Upgrading Sun JRE with Oracle Applications 11i" to implement this solution

About Log files in $APPLCSF/$APPLOG directory

2008-12-12T00:25:00.000-08:00

(a) l.req

This is the Concurrent Request log file. When any concurrent request is submitted, request log file is created in this directory with file name as l.req

(b) Events####.log

adstrtal.sh script writes the log information in to this file, when ever there is any problem with starting of any Application Service.

(c) Error####.log

This file contains the Java Exception Errors.

(d) #####.log

This file keeps the information of starting of Apache Listener.

(e) f60webmx_dump_

This file is created when ever any Client Forms Session ends abruptly. When user forms session got crash or terminated abruptly that diagnostics information is written into this dump file. If you want to get rid out of this dump files. Please execute the following stepsSet the FORMS60_CATCHTERM = 0 in Registry (NT) or Environment Variable (Unix/Linux) and bounce the Forms Services

(f) em_.rti

This file contains Client run time process information. These files are used by Oracle Application Manager and Enterprise Manager for Forms Monitoring Services and are generated by Forms runtime processes. For each f60webmx session, there is one .rti file is created. These files are written to the directory set by parameter $FORMS60_RTI_DIR. By default these are written into $APPLCSF/$APPLLOG directory. RTI files should be automatically cleaned up when user logs out of the forms session, in case user logs out of the forms sessions abruptly. Then these files are not cleaned up properly. So then you may need to clear these files manually. We can delete the files, but we should not delete these files when users are active

em –> enterprise manager

–> Process ID of Client

rti –<>

we need to delete the FNDCPPUR program log files and output files manually to free up the disk space. Here I am giving UNIX commands to find out and deleting the old files. If your FNDCPPUR program is scheduled to run daily and given AGE Mode value as 7, purge Program has to delete the files which are older than 7 days. But if program did not delete the files, use this command to find out those files.

Find the Concurrent Request Log and Output files which are not deleted

find $APPLCSF/$APPLLOG -mtime +7 -name “*.req”

find $APPLCSF/$APPLOUT -mtime +7 -name “*.out

Delete the Concurrent Request log and output files which are older than 7 Days

find $APPLCSF/$APPLLOG -mtime +7 -name “*.req” -exec rm “{}” “;”

find $APPLCSF/$APPLOUT -mtime +7 -name “*.out” -exec rm “{}” “;”

Delete other files in $APPLCSF/$APPLLOG directory

find $APPLCSF/$APPLLOG -mtime +7 -name “*.log” -exec rm “{}” “;”

find $APPLCSF/$APPLLOG -mtime +7 -name “*.mgr” -exec rm “{}” “;”

find $APPLCSF/$APPLLOG -mtime +7 -name “f60webmx*” -exec rm “{}” “;”

find $APPLCSF/$APPLLOG -mtime +7 -name “*.rti” -exec rm “{}” “;”

Reference:

(1) What Are .RTI and .FLI Files? Doc ID: Note: 470850.1

(2) Oracle Forms in Applications FAQ Doc ID: Note: 177610.1

Concurrent request pending normal for long time

2008-10-30T02:59:00.000-07:00

Issue:

All Request are in pending normal state. No request was processed since long time.

Cause

Problem with the stadard manager which is not processing the requests

Action Taken #1

1) Shutdown all concurrent Managers
2)Killed any FND process which is running.
3) Ran the cmclean

Result: Not solved ..No Use

Action Taken #2

Found a note from metalink and forums. Followed the steps

1. Shutdown the Concurrent Manager.
2. Export the tables fnd_concurrent_queues and fnd_concurrent_queues_tl.
3. Run the script afdcm019.sql to update the fnd tables with correct manager
informations.
4. Restart the concurrent manager.
5. Resubmit the concurrent reqests.

Result: Not solved

Action taken #3

Finally one of my friend(Bharath) gave the solution, It worked after all.

I deactivated the Standard concurrent manager and re created the standard concurrent manager

1) Shutdown your concurrent managers normally and let all the processes go.
2) If all FNDLIBR processes are unable to go you can kill the processes.
3) login to database as apps user.
4) select running_processes, target_processes from fnd_concurrent_queues
(they shouldnt be indicating 0 processes running - you can skip the next step if they are already zero)

5)update fnd_concurrent_queues set running_processes = 0, target_processes = 0;

6) Now try and start your concurrent managers.
7) In a very remote situation your standard manager may be corrupt. If you see any message in your
concurrent manager log file indicating the same, you may have to re-create your
standard manager. So you can start your application services and login to
application (without your concurrent manager and report server services) . Go to
define manager form and re-create your standard manager. Disable the old
one.

Result: +ve working fine
all concurrent requests are running,
problem with the standard concurrent manager which is corrupted

Tablespace-size(free,Used,Pct)

2008-07-17T03:23:00.000-07:00

select df.tablespace_name "Tablespace",
totalusedspace "Used MB", (df.totalspace - tu.totalusedspace) "Free MB",
df.totalspace "Total MB", round(100 * ( (df.totalspace - tu.totalusedspace)/ df.totalspace)) "Pct. Free" from
(select tablespace_name, round(sum(bytes) / 1048576) TotalSpace
from dba_data_files group by tablespace_name) df,
(select round(sum(bytes)/(1024*1024)) totalusedspace, tablespace_name
from dba_segments group by tablespace_name) tu
where df.tablespace_name = tu.tablespace_name ;

Kill Oracle process at UNIX

2008-06-26T01:41:00.000-07:00

Kill Oracle Session
The SQL*Plus Approach

Sessions can be killed from within oracle using the ALTER SYSTEM KILL SESSION syntax.First identify the offending session as follows:

SELECT s.sid, s.serial#, s.osuser, s.program FROM v$session s;

SID SERIAL# OSUSER PROGRAM---------- ---------- ------------------------------ ---------------
1 1SYSTEM ORACLE.EXE
2 1 SYSTEM ORACLE.EXE
3 1 SYSTEM ORACLE.EXE
4 1 SYSTEM ORACLE.EXE
5 1 SYSTEM ORACLE.EXE
6 1 SYSTEM ORACLE.EXE
20 60 SYSTEM DBSNMP.EXE
43 11215 USER1 SQLPLUSW.EXE
33 5337 USER2 SQLPLUSW.EXE

The SID and SERIAL# values of the relevant session can then be substituted into the following statement:

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#';

In some situations the Oracle.exe is not able to kill the session immediately. In these cases the session will be "marked for kill".

It will then be killed as soon as possible.Issuing the ALTER SYSTEM KILL SESSION command is the only safe way to kill an Oracle session. If the marked session persists for some time you may consider killing the process at the operating system level, as explained below.

Killing OS processes is dangerous and can lead to instance failures, so do this at your own risk.It is possible to force the kill by adding the IMMEDIATE keyword:

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#' IMMEDIATE;

This should prevent you ever needing to use the orakill.exe in Windows, or the kill command in UNIX/Linux.

The NT Approach

To kill the session via the NT operating system, first identify the session as follows:

SELECT s.sid, p.spid, s.osuser, s.program FROM v$process p, v$session s WHERE p.addr = s.paddr;

SID SPID OSUSER PROGRAM---------- --------- ------------------------------ ---------------1 310 SYSTEM ORACLE.EXE
2 300 SYSTEM ORACLE.EXE
3 309 SYSTEM ORACLE.EXE
4 299 SYSTEM ORACLE.EXE
5 302 SYSTEM ORACLE.EXE
6 350 SYSTEM ORACLE.EXE
20 412 SYSTEM DBSNMP.EXE
43 410 USER1 SQLPLUSW.EXE
33 364 USER2 SQLPLUSW.EXE

The SID and SPID values of the relevant session can then be substituted into the following command issued from the command line:

C:> orakill ORACLE_SID spid

The session thread should be killed immediately and all resources released.

The UNIX Approach

To kill the session via the UNIX operating system, first identify the session in the same way as the NT approach, then substitute the relevant SPID into the following command:

% kill -9 spid

If in doubt check that the SPID matches the UNIX PROCESSID shown using:

% ps -ef grep ora

The session thread should be killed immediately and all resources released.

Imp Links

2008-05-28T03:40:00.000-07:00

System Tables in Oracle:
http://www.techonthenet.com/oracle/sys_tables/

Unix --- Sudo

http://www.unixcities.com/sudo/index.html

Kill the Locked session

2008-05-09T02:14:00.000-07:00

Whenevr you patching session or any process get hold just check for the lock and kill those locks by following steps

select * from v$lock where LMODE=6 and block=1 order by SID;

ADDR Kaddr SID ID1 ID2 LMODE REQUEST CTIME
616970C8 61697194 363 TX 524313 6 0 2812
Pick the SID=363 and put in the following command

select * from v$session where SID=&SID;
Enter the value for sid: 363

Then out put should be like
SID SERIAL# AUDSID PADDR USER# USERNAME COMMAND so on....
342AC098 376 47366 T33S 36 PE

Pick the SID and SERIAL# values from the out put and run the script

Alter system kill session '376,1473';

AOLJ Test

2008-05-01T00:47:00.000-07:00

AOLJ test
http:///OA_HTML/jsp/fnd/aoljtest.jsp

To do this run the AOL test UI. This option consists of a collection of tests that you can run to determine if your web server is configured properly. You can access these tests via :
http:///OA_HTML/jsp/fnd/aoljtest.jsp
After you sign in, some preliminary information about your environment will be displayed. Click on the Enter Aol/J Setup Test link to get to the menu of tests. You must run the tests under the "Connection Test" and "Apps Framework Agent" categories.
Test Name Comments
Locate DBC File Mandatory. Run this test first.
Verify DBC Settings Mandatory. Run this test second.
AOL/J Connection test Mandatory. Run this test third.
Apps Framework Agent Mandatory
Virtual Directory Settings Mandatory
Jsp Ping Mandatory
Cabo Setup Tests Mandatory
X Server Accessibility Test Mandatory
OA Framework System Info Mandatory
Servlet Ping Optional
Versions for Loaded Classes Optional

Form Compile

2008-05-01T00:46:00.001-07:00

f60gen JAINPO.fmb output_file=$JA_TOP/forms/US/JAINPO.fmx userid=apps/apps

FND&AD Tables

2008-05-01T00:43:00.000-07:00

Apps tables
FND_USER--à No of users in the system
FND_PRODUCT_GROUPS
FND_PRODUCT_INSTALLATIONS-à Patch set level
FND_INSTALL_PROCESS
FND_NODES
FND_LANGUAGES
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_QUEUES
FND_LOGINS-à No of users logged in.
FND_ORACLE_USERID-à when validating apps schema
FND_APPLICATIONS
FND_RESPONSIBILITY
AD_DEFFERED_JOBS
AD_BUGS
AD_PATCH_HIST_TEMP-à Temp tables to store patch history
AD_PATCH_DRIVERS
AD_APPLIED_PATCHES
AD_SNAPSHOT
AD_SNAPSHOT_FILES
AD_SNAPSHOT_BUFFERS
Select * from v$FIXED_TABLE; -à To know all the views

Cron and Crontab

2008-04-28T04:23:00.000-07:00

What are cron and crontab, and how do I use them?
Don't know....No issue folks i will give some needful introduction which will give an idea on that........
If you have any queries and have more information than this let share with me.....
Coming to the point what are CRON and CRONTAB
cron is a unix, solaris utility that allows tasks to be automatically run in the background at regular intervals by the cron daemon. These tasks are often termed as cron jobs in unix , solaris. Crontab (CRON TABle) is a file which contains the schedule of cron entries to be run and at specified times

1. Crontab Restrictions
You can execute crontab if your name appears in the file /usr/lib/cron/cron.allow. If that file does not exist, you can usecrontab if your name does not appear in the file /usr/lib/cron/cron.deny. If only cron.deny exists and is empty, all users can use crontab. If neither file exists, only the root user can use crontab. The allow/deny files consist of one user name per line.

Note: On most systems, you must get permission from the system administrator before you can submit job requests to cron. On some shared systems, because there is only one crontab file, only the administrator has access to the crontab command. The cron daemon is a long-running process that executes commands at specific dates and times. You can use this to schedule activities, either as one-time events or as recurring tasks.

Crontab Environment
cron invokes the command from the user's HOME directory with the shell, (/usr/bin/sh).
cron supplies a default environment for every shell, defining:
HOME=user's-home-directory
LOGNAME=user's-login-id
PATH=/usr/bin:/usr/sbin:.
SHELL=/usr/bin/shUsers who desire to have their .profile executed must explicitly do so in the crontab entry or in a script called by the entry
For commands that need to be executed repeatedly (e.g., hourly, daily, or weekly), you can use the crontab command. The crontab command creates a crontab file containing commands and instructions for the cron daemon to execute. You can use the crontab command with the following options:
crontab -a filename
Install filename as your crontab file. On many systems, this command is executed simply as crontab filename (i.e., without the -a option).
crontab -e
Edit your crontab file, or create one if it doesn't already exist.(if you want to edit the timing which the script has 2 be run, we have to use this command to c the file and hash for not 2 run the script or changr the timings)

crontab -l
Display your crontab file. (we give this command in database to find out any scheduled task is going on at this moment)
crontab -r Remove your crontab file.
crontab -v Display the last time you edited your crontab file. (This option is available on only a few systems.)
crontab -u user
Used in conjunction with other options, this option allows you to modify or view the crontab file of user. When available, only administrators can use this option.
Each entry in a crontab file consists of six fields, specifying in the following order:minute(s) hour(s) day(s) month(s) weekday(s) command(s)
The fields are separated by spaces or tabs. The first five are integer patterns and the sixth is the command to execute. The following table briefly describes each of the fields:
Field Value Description

minute 0-59 The exact minute that the command sequence executes
hour 0-23 The hour of the day that the command sequence executes
day 1-31 The day of the month that the command sequence executes
month 1-12 The month of the year that the command sequence executes
weekday 0-6 The day of the week that the command sequence executes (Sunday = 0, Monday = 1, Tuesday = 2, and so forth)

Disable Email

By default cron jobs sends a email to the user account executing the cronjob. If this is not needed put the following command At the end of the cron job line .
>/dev/null 2>&1

Generate log file

To collect the cron execution execution log in a file :30 18 * * * rm /home/someuser/tmp/* > /home/someuser/cronlogs/clean_tmp_dir.log

command Special
The complete sequence of commands to execute. The command string must conform to Bourne shell syntax. Commands, executables (such as scripts), or combinations are acceptable.
Each of the patterns from the first five fields may be either * (an asterisk), meaning all legal values, or a list of elements separated by commas. An element is either a number or an inclusive range, indicated by two numbers separated by a minus sign ( e.g., 10-12). You can specify days with two fields: day of the month and day of the week. If you specify both of them as a list of elements, cron will observe both of them, for example:0 0 1,15 * 1 /mydir/myprogram
The cron daemon would run the program myprogram in the mydir directory on the first and fifteenth of each month, as well as on every Monday. To specify days by only one field, the other field should be set to * ,

for example:0 0 * * 1 /mydir/myprogram

In the above example, the program would run only on Mondays.
If a cron job specified in your crontab entry produces any error messages when it runs, you will get a mail message reporting the errors.
For more information, consult the following relevant man pages:
man crontab man cron man at man batch

Printer Configuration

2008-04-04T02:56:00.000-07:00

1. Introduction and scope

Printer configuration for OnDemand customers is normally done by customer. Some cases where customer has issues with infrastucture like OS, network,firewall will be handled by respective groups. Issues related with application will be worked by Product Support, who will then provide an Action Plan for Operations to fix the issue.
This documents covers the following topics

Navigation used to configure printers in applications
Configuration files used
Troubleshooting information for printing issues

2. Standard configuration steps description

2.1 Prerequisites

Printers should be first defined at Unix OS level by customers @Oracle model using PrintPro.

Printpro URL which will be used by customer for defining printers is http://hostname.domain:631/

Eg: http://auohssato01.oracleoutsourcing.com:631/

Please check the status of printer at unix level by using the following command

lpstat –a

Logins for printpro will be provided by Onlinesupport/OnDemandhub/SDM to the customer

2.2 Standard Configuration

Here are the steps to be followed in configuring a printer in Oracle Applications

Define Driver
Define Style
Define Printer Type
Register the Printer
Test printing to the printer
Login to application using System Administrator or Application Administrator resp

Define the printer driver, Install > Printer > Driver

Enter the Driver Name : LANDWIDEHPLJ4SI
Enter the User Driver Name: LANDWIDE for Printer HPLJ4SI
Description: Give some desc appropiate
SRW Driver: HPW
SRW drivers are read by Oracle reports when a report is run and insert control characters which tell the destination printer on where to insert the page breaks and font to be used etc.. SRW driver is used when output file is sent to the printer

SRW driver files on unix are located in $FND_TOP/reports. In the above example, file name would be HPW.prt
Platform: Not required
Arguments: Printer Driver pass the following arguments to progrram
Name of the destination printer
Number of Copies to print
Banner of the title page
Filename
Initialization and Reset strings: Instructs printer on printing characteristics are needed for the document to be printed. Printer vendor provides these details
Define the printer style , Install > Printer > Style

Style Name : HPW
Seq: Enter unique sequence number
User Style: LANDWIDE - HPLJ4
SRW Driver: HPW , this should match with driver define page
Layout:Columns,Rows and Orinetation: Columns and Rows inserted here override the height and width defined in SRW driver file

Define the printer type, Install > Printer > Type

Type: HPLJ4SI
Style: Style name
Driver Name: Driver name

Register a new printer , Navigation Path is Install > Printer > Register

Printer : Printer Name
Type: Type defined earlier
Description : Useful description

Configuration files

Some of the important configuration files in printer configuration are
<8.0.6>/guicommon6/tk60/admin/uiprint.txt
<8.0.6>/guicommon6/tk60/admin/Tk2Motif.rgb

For more details about above config files, please refer to Doc id: 16888.1 and 8422.1

Some important tables related with printing in APPLSYS schema are

FND_PRINTER
FND_PRINTER_INFORMATION
FND_PRINTER_STYLES
FND_PRINTER_DRIVERS

Bouncing Concurrent Manager

Concurrent Manager cache printing related information, so any changes to Printer Type, Style and Driver needs bouncing of concurrent manager for the changes to take effect.
2.2.1 @Oracle Customers

Printers are configured at unix by customers using PrintPro url mentioned in Prereq
2.2.2 @Customer

Printers at unix level are configured by customer or third party who is hosting customer hardware
2.2.3 Architecture specifics (RAC, PCP, Multi MT...etc)

Printers at unix level have to be added on all PCP nodes
2.2.4 Version/Patchset dependency

NA

2.3 Post steps

Customeers should print from applications and test it. If any issues, printing should be first tested at unix level with the following command

lp –d /tmp/test.txt

/tmp/test.txt can be a ASCII text file.

3. Known issues

Most of the times when we get TARs related with ‚‘not printing to particular printer‘,

please check if the jobs are queued at unix level by using the following command
lpstat –o
Please check if printer is configured on unix by using the following command
lpstat -a

If you see jobs are stuck, please transfer the TAR to unix Sas to fix the issue.
If printer is not configured, please request the customer to define the printer from PrintPro

4. Refresh/Patch persistency

NA

5. Automation/Verification

NA
5.1 Reference to any automation scripts
NA
5.2 Reference to any diagnostic scripts

NA

6. Exceptions from standard

NA

7. Time information

2 hrs for defining Printer Driver,Style,Type and boucing concurrent manager

8. Other Documentation

NA

health check

2007-12-22T08:35:00.000-08:00

Front_End Health checks

1. To check web server is up and runningor not
http://localhost.domainname:port no------->>displays Home Page

2. To check database is up and running
Check 11i online help

Check E_Business Suit

3. To check that servelet is up and running.
url/servelet/hello displays ¨congrates¨

4. To check that fullfillment server is up and running.
Which is used to gather instance diagnostic information.
url/OA_HTML/jtflogin.jsp asks for login id/pwd

5. To check for discoverer server is up and running or not
url/discoverer4i/viewer asks for login id/pwd/Dbname

6. To check that concurrent manager is up and running.
E-Business suit--->system administrator--->administer--->internal conc.mgr-->Atual=target(other than 0)
7. To check Jserv working or not
url/OA_HTML/AppsLocalLogin.jsp

8. It displays workflow manager status.
Oracle Application Manager--->navigate to--->workflow manager check status

Backend Health Checks

1)check for invalid counts
Select count(*) from dba_objects where object_Name= 'INVALID' ;
Run utlrp.sql, location ORACLE_HOME/rdbms/admin

2)check workflow
select fsc.COMPONENT_ NAME,fsc. STARTUP_MODE, fsc.COMPONENT_ STATUS
from APPS.FND_CONCURRENT _QUEUES_VL fcq, fnd_svc_components fsc
where fsc.concurrent_ queue_id = fcq.concurrent_ queue_id( +)
and fcq.USER_CONCURRENT _QUEUE_NAME like '%Mail%';

MULTIPLEXING OF ONLINE REDOLOG FILES

2007-11-09T22:26:00.000-08:00

MULTIPLEXING OF ONLINE REDOLOG FILES USING ORACLE MANAGED FILES

1.connect to the spqplus as sysdba
SQL> sqlplus '/as sysdba'
2.startup the database

3.Check to see that the database is using Oracle-Managed Files.
SQL> show parameter db_create_online_log_dest

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_create_online_log_dest_1 string /home/oracle9i/oradata/db
db_create_online_log_dest_2 string
db_create_online_log_dest_3 string
db_create_online_log_dest_4 string
db_create_online_log_dest_5 string

If the value of all of the DB_CREATE_ONLINE_LOG_DEST column were null, it means that you cannot take advantage of Oracle-Managed Files.

4.Create a directory called multi in the location
$cd /home/oracle9i/oradata/db
$mkdir multi
5.Alter the system so that the database will manage the Online Redo Log files in the Online Redo Log destination 2.
SQL> alter system set db_create_online_log_dest_2=' /home/oracle9i/oradata/db/multi';
System altered.
6.Display the DB_CREATE_ONLINE_LOG_DEST parameter again.
SQL> show parameter db_create_online_log_dest

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_create_online_log_dest_1 string /home/oracle9i/oradata/db
db_create_online_log_dest_2 string /home/oracle9i/oradata/db/mul
ti
db_create_online_log_dest_3 string
db_create_online_log_dest_4 string
db_create_online_log_dest_5 string
Notice that there is a value for the log destination 2.

7.Alter the database to add one more group to the online redo log files.
SQL> alter database add logfile group 5;
Database altered.
8.Query the V$LOGFILE view.
SQL> select * from v$logfile;

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
3 ONLINE
/home/oracle9i/oradata/db/redo03.log

2 ONLINE
/home/oracle9i/oradata/db/redo02.log

1 STALE ONLINE
/home/oracle9i/oradata/db/redo01.log

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
5 ONLINE
/home/oracle9i/oradata/db/o1_mf_5_36c3fxly_.log

4 ONLINE
/home/oracle9i/oradata/db/o1_mf_4_36c08djq_.log

5 ONLINE
/home/oracle9i/oradata/db/multi/o1_mf_5_36c3g17c_.log

6 rows selected.

Notice the Oracle naming convention. The 5 indicates the group number.

9.Add a member to the Online Redo Log files group number 5, using Oracle-Managed Files (OMF).
SQL> alter database add logfile member 'redo5.log' to group 5;

Database altered.
101.connect to the spqplus as sysdba
SQL> sqlplus '/as sysdba'
2.startup the database.Query the V$LOGFILE view.
SQL> select * from v$logfile;

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
3 ONLINE
/home/oracle9i/oradata/db/redo03.log

2 ONLINE
/home/oracle9i/oradata/db/redo02.log

1 STALE ONLINE
/home/oracle9i/oradata/db/redo01.log

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
5 ONLINE
/home/oracle9i/oradata/db/o1_mf_5_36c3fxly_.log

4 ONLINE
/home/oracle9i/oradata/db/o1_mf_4_36c08djq_.log

5 ONLINE
/home/oracle9i/oradata/db/multi/o1_mf_5_36c3g17c_.log

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
5 INVALID ONLINE
/home/oracle9i/9.2.0.4/dbs/redo5.log

7 rows selected.

MULTIPLEXING OF ONLINE REDO LOG FILES USING USER MANAGED FILES

1.connect to the database as sysdba
SQL> sqlplus '/as sysdba'
2.startup the database
3.Create a directory called multi in the location
$cd /home/oracle9i/oradata/db
$mkdir multi
4.Alter the database to add one more group to the online redo log files.
SQL> alter database add logfile group 5
'/home/oracle9i/oradata/db/multi/redo03.log' size 4m;

Database altered.
5.query the v$logfile view
SQL> select * from v$logfile;

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
3 ONLINE
/home/oracle9i/oradata/db/redo03.log

2 ONLINE
/home/oracle9i/oradata/db/redo02.log

1 STALE ONLINE
/home/oracle9i/oradata/db/redo01.log

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
5 ONLINE
/home/oracle9i/oradata/db/multi/redo03.log

4 ONLINE
/home/oracle9i/oradata/db/o1_mf_4_36c08djq_.log

6.Add a member to the Online Redo Log files group number 5.
SQL> alter database add logfile member
'/home/oracle9i/oradata/db/multi/redo02.log' to group 5;

Database altered.
7. query the v$logfile view
SQL> select * from v$logfile;

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
3 ONLINE
/home/oracle9i/oradata/db/redo03.log

2 ONLINE
/home/oracle9i/oradata/db/redo02.log

1 STALE ONLINE
/home/oracle9i/oradata/db/redo01.log

GROUP# STATUS TYPE
---------- ------- -------
MEMBER
--------------------------------------------------------------------------------
5 ONLINE
/home/oracle9i/oradata/db/multi/redo03.log

4 ONLINE
/home/oracle9i/oradata/db/o1_mf_4_36c08djq_.log

5 INVALID ONLINE
/home/oracle9i/oradata/db/multi/redo02.log

6 rows selected.

Data Guard

2007-11-09T21:57:00.000-08:00

Oracle Data Guard

Oracle Data Guard is the most effective and comprehensive data availability, data protection and disaster recovery solution for enterprise databases.

Oracle Data Guard is the management, monitoring, and automation software infrastructure that creates, maintains, and monitors one or more standby databases to protect enterprise data from failures, disasters, errors, and corruptions.

Data Guard maintains these standby databases as synchronized copies of the production database. These standby databases can be located at remote disaster recovery sites thousands of miles away from the production data center, or they may be located in the same city, same campus, or even in the same building. If the production database becomes unavailable because of a planned or an unplanned outage, Data Guard can switch any standby database to the production role, thus minimizing the downtime associated with the outage, and preventing any data loss.

Data Guard 11g builds upon an already unique set of capabilities, and redefines what users can expect from a disaster recovery solution. It can address both High Availability and Disaster Recovery requirements, and is the ideal complement to Oracle Real Application Clusters (Oracle RAC). Data Guard has the requisite knowledge of the Oracle database to reliably protect a standby database from corruptions that attempt to propagate from a primary database. It is straightforward to implement and manage. It enables all standby databases, both physical and logical, to be used for productive purposes while in standby role. Data Guard delivers:

Reliability– optimum data protection and availability. You always know the state of your standby database and it can very quickly (in seconds), assume the primary role.
Lower cost and complexity – Data Guard's mature capabilities and rich management interface are included features of Oracle Enterprise Edition.
Maximum return on investment – All standby databases can be utilized for production purposes while in standby role. Idle resources are eliminated WITHOUT increased complexity.

Data Guard can be used in combination with other Oracle High Availability (HA) solutions such as Real Application Clusters (RAC), Oracle Flashback , Oracle Recovery Manager (RMAN), and new database options for Oracle Database 11g that include Oracle Active Data Guard and Oracle Advanced Compression, to provide a high level of data protection, data availability, and resource utilization that is unprecedented in the industry.

The following diagram presents a hi-level overview of Oracle Data Guard.

Overview of Oracle Data Guard Functional Components

Data Guard Configuration

A Data Guard configuration consists of one production (or primary) database and up to nine standby databases. The databases in a Data Guard configuration are connected by Oracle Net and may be dispersed geographically. There are no restrictions on where the databases are located, provided that they can communicate with each other.

Redo Apply and SQL Apply

A standby database is initially created from a backup copy of the primary database. Once created, Data Guard automatically maintains the standby database as a synchronized copy of the primary database by transmitting primary database redo data to the standby system and then applying the redo data to the standby database.

Data Guard provides two methods to apply this redo data to the standby database and keep it synchronized with the primary, and these methods correspond to the two types of standby databases supported by Data Guard.

Redo Apply, used for physical standby databases
SQL Apply, used for logical standby databases

A physical standby database provides a physically identical copy of the primary database, with on-disk database structures that are identical to the primary database on a block-for-block basis. The database schema, including indexes, are the same. The Redo Apply technology applies redo data on the physical standby database using standard Oracle media recovery techniques. In addition to traditional Data Guard functionality, the Active Data Guard Option for Oracle Database 11g enables a physical standby database to be open read-only while it applies updates received from the primary database. This makes physical standby databases useful for offloading the primary database from the overhead of processing read-only queries and reports. It also becomes effortless to validate that the standby database is synchronized with the primary database at all times.

A logical standby database contains the same logical information as the production database, although the physical organization and structure of the data can be different. The SQL apply technology keeps the logical standby database synchronized with the primary database by transforming redo data received from the primary database into SQL statements and then executing the SQL statements on the standby database. This makes it possible for the logical standby database to be open read-write and accessed for queries and reporting purposes at the same time the SQL is being applied to it.

Role Management

Using Data Guard, the role of a database can be switched from a primary role to a standby role and vice versa, ensuring no data loss in the process, and minimizing downtime. There are two kinds of role transitions - a switchover and a failover. A switchover is a role reversal between the primary database and one of its standby databases. This is typically done for planned maintenance of the primary system. During a switchover, the primary database transitions to a standby role and the standby database transitions to the primary role. The transition occurs without having to re-create either database. A failover is an irreversible transition of a standby database to the primary role. This is only done in the event of a catastrophic failure of the primary database, which is assumed to be lost and to be used again in the Data Guard configuration, it must be re-instantiated as a standby from the new primary. Administrators have the option of executing failovers manually, or Data Guard can be configured to automatically detect primary database failures and execute a failover to the standby database without manual intervention.

Data Guard Protection Modes

In some situations, a business cannot afford to lose data at any cost. In other situations, some applications require maximum database performance and can tolerate a potential loss of data. Data Guard provides three distinct modes of data protection to satisfy these varied requirements:

Maximum Protection—This mode offers the highest level of data protection. Data is synchronously transmitted to the standby database from the primary database and transactions are not committed on the primary database unless the redo data is available on at least one standby database configured in this mode. If the last standby database configured in this mode becomes unavailable, processing stops on the primary database. This mode ensures no-data-loss, even in the event of multiple failures.
Maximum Availability—This mode is similar to the maximum protection mode, including zero data loss. However, if a standby database becomes unavailable (for example, because of network connectivity problems), processing continues on the primary database. When the fault is corrected, the standby database is automatically resynchronized with the primary database. This mode achieves no-data-loss in the event of a single failure (e.g. network failure, primary site failure . . .)
Maximum Performance—This mode offers slightly less data protection on the primary database, but higher performance than maximum availability mode. In this mode, as the primary database processes transactions, redo data is asynchronously shipped to the standby database. The commit operation of the primary database does not wait for the standby database to acknowledge receipt of redo data before completing write operations on the primary database. If any standby destination becomes unavailable, processing continues on the primary database and there is little effect on primary database performance.

Data Guard Broker

The Oracle Data Guard Broker is a distributed management framework that automates and centralizes the creation, maintenance, and monitoring of Data Guard configurations. All management operations can be performed either through Oracle Enterprise Manager, which uses the Broker, or through the Broker's specialized command-line interface (DGMGRL). Data Guard Broker 11g also enables automatic database failover for Data Guard configurations using either Maximum Availability or Maximum Performance modes.

Data Guard Architecture Diagram

The following diagram shows an overview of the Oracle Data Guard architecture.

1.What's New in Oracle Data Guard 11g?

Data Guard 11g has been made even more straightforward to implement and manage using either the Data Guard broker command line interface or Enterprise Manager Grid Control. Data Guard 11g adds new ways to detect corruptions that avoid data loss and extended down time. Data Guard 11g includes flexible configuration options for fast, automatic failover in both Maximum Availability and Maximum Performance protection modes. Data Guard 11g physical standby databases can offload the primary database of queries and reporting by being open read-only while apply is active, effectively creating a new level of performance protection and return on investment for every Data Guard environment. The sections below highlight some of the key new features of Oracle Data Guard 11g. For details, please refer to the following:

Technical white paper on Oracle Data Guard 11g

2.Snapshot Standby

This is a new type of standby database that is created from a physical standby database. Once created, a snapshot standby can be opened read-write to process transactions that are independent of the primary database for test or other purposes. A snapshot standby will continue to receive and archive updates from the primary database, however, redo data received from the primary will not be applied until the snapshot standby is converted back into a physical standby database and all updates that were made to it while it was a snapshot standby are discarded. The ability for the snapshot standby to archive data received from the primary while the snapshot is open read-write means production data stays protected at all times.

3.Support for the Oracle Active Data Guard Option

The Active Data Guard Option is a separately licensed database option for Oracle Database 11g Enterprise Edition that includes the new feature, Real-time Query. Using Real-time Query, a physical standby database can be open read-only while Redo Apply is active. This allows users attached to a physical standby database to query and report against data that is up-to-date with the primary database. Real-time query makes all physical standby databases able to do useful work while in standby role.

Real-time Query also enables deployment of “Reader Farms” using physical standby. A Data Guard reader farm complements RAC and offers an alternative architecture for scaling out read performance to web scale by using multiple read-only standby databases to isolate workload, isolate faults, and benefit from modular, linear growth in capacity by simply provisioning additional read-only copies of the primary database. For example, a popular online music retailer has implemented a reader farm configuration using Data Guard 10g and SQL Apply (logical standby). Now both physical and logical standby databases can be used for such a purpose. In the ideal reader farm configuration an Oracle RAC primary database is used for scale-out and HA for updates, inserts and deletes. One standby database serves as the failover target and has an identical configuration to the Oracle RAC primary so that service levels for updates, inserts, and deletes are maintained at failover time. Each additional standby databases in the reader farm (also known as bystander standbys) is a vanilla, single node standby database dedicated to read-only queries. HA is easily maintained at failover time since all bystanders transparently recognize the new primary database after a failover occurs.

4.Failover enhancements

Data Guard 10g Release 2 introduced automatic failover using the new feature Fast-Start Failover with Maximum Availability protection mode (SYNC). Data Guard 11g extends Fast-Start Failover support Maximum Performance mode (ASYNC) by adding a user configurable data loss threshold that guarantees an automatic failover will never result in data loss that exceeds the desired recovery point objective (RPO).

Users can also configure an automatic failover to occur immediately without waiting for the Fast-Start Failover threshold time period to expire based on designated health check conditions or any desired ORA-nnnnn error.

A new DBMS_DG PL/SQL package can be used to enable applications to notify the Fast-Start Failover Observer process to initiate an automatic failover.

Other enhancements enable faster failovers across a range of Data Guard configurations – both manual and automatic failovers, and both logical and physical standby databases.

Enhanced data protection

A Physical Standby can detect lost datafile writes caused by faulty storage hardware and firmware that lead to data corruption on either the primary or the standby database. Data Guard will compare versions of blocks on the standby with that of the incoming redo stream. If there is a version discrepancy it implies a lost write. The user can then failover to the standby database and restore data consistency..

Redo Transport enhancements

Data Guard 11g implements a new streaming design that significantly increases the throughput of redo transport in Maximum Performance protection mode (during asynchronous redo transport and when using ARCn processes to resolve gaps). The benefit of these enhancements will be particularly noticeable in high latency – WAN environments.

Enhancements to synchronous redo transport in Maximum Availability mode will further reduce the impact of network latency on primary database throughput, expanding the number of applications that will be able to tolerate synchronous zero data loss protection, and extending the distance between primary and standby databases that is practical for such implementations.

Faster resynchronization of standby databases following network or standby database outages when using the Oracle Advanced Compression Option. One of the capabilities of the Advanced Compression Option enables automatic network compression of archive logs shipped by Data Guard to resolve gaps on the standby database. This feature is particularly beneficial for bandwidth constrained, high latency network environments.

Apply performance enhancements

Parallel media recovery significantly enhances Redo Apply performance (physical standby) for all workload profiles.

SQL Apply enhancements for logical standby increase apply performance for inserts and updates to tables that are not partitioned and that do not contain LOB, LONG or XML type column. Also, SQL Apply now applies parallel DDL in parallel, rather than serially as was the practice in previous releases.

Transient Logical Standby

Users can convert a physical standby to a transient logical standby database to effect a rolling database upgrade, and then revert the standby to its original state as a physical standby database once the upgrade is complete - using the KEEP IDENTITY clause. This benefits physical standby users who wish to execute a rolling database upgrade without investing in redundant storage otherwise needed to create a logical standby database.

Fine-grained monitoring of Data Guard configurations

Oracle Enterprise Manager has been enhanced to provide granular, up-to-date monitoring of Data Guard configurations, so that administrators may make an informed and expedient decision regarding managing this configuration.

RMAN enhancements for Data Guard

RMAN DUPLICATE can create standby databases directly from the primary database to the standby system without requiring interim storage at either location.

In addition to Real-time Query discussed above, the Active Data Guard Option adds support for RMAN block-change tracking on a physical standby database enabling fast incremental backup of a standby database. Tests have shown that incremental backups on a database with a moderate rate of change can complete up to 20x faster when using RMAN block-change tracking, compared to traditional incremental backups.

Enhanced security

SSL authentication can be used in lieu of password file to authenticate redo transmission. Note: SSL authentication requires use of PKI Certificates, the Oracle Advanced Security Option and Oracle Internet Directory.

Enhanced SQL Apply support

XMLType data type (when stored as CLOB)
Ability to execute DDL in parallel on a logical standby database
Transparent Data Encryption (TDE)
DBMS_FGA (Fine Grained Auditing)
DBMS_RLS (Virtual Private Database)

SQL Apply Manageability

Scheduler jobs can be created on a standby database using the DBMS_SCHEDULER package and can be associated with an appropriate database role such that they run when intended (e.g. when the database is the primary, standby, or both).

Switchover using SQL Apply with Oracle RAC databases no longer requires the prior shutdown of all but the first instance in each Oracle RAC cluster.

Data Guard SQL Apply parameters may also be set dynamically without requiring SQL Apply to be restarted. Using the DBMS_LOGSTDBY.APPLY_SET package, you can dynamically set initialization parameters, thus improving the manageability, uptime, and automation of a logical standby configuration.

Data Guard Broker

Enables automatic database failover for configurations using either Maximum Availability or Maximum Performance mode.
Enables configurable events to trigger immediate automatic failover to a target standby database.
Improved support for redo transport options, enabling an administrator to specify a connect description for Redo Transport Services.
Elimination of database downtime when changing the protection mode to and from Maximum Availability and Maximum Performance.
Support for single instance databases configured for HA using Oracle Clusterware and cold failover clusters.

Enterprise Manager Grid Control 11g

Creation of standby databases from existing RMAN backups
Creation of an Oracle RAC standby database from an Oracle RAC primary
Automated standby clones for reporting, development, and test
Automatic propagation of Enterprise Manager jobs and metric thresholds to the new primary database upon switchover or failover
Fault-tolerant observer for Fast-Start Failover
Enterprise Manager Data Recovery Advisor will utilize available standby databases when making recommendations for Intelligent Data Repair (IDR)

Data Guard Benefits

Disaster recovery and high availability

Data Guard provides an efficient and comprehensive disaster recovery and high availability solution. Automatic failover and easy-to-manage switchover capabilities allow quick role reversals between primary and standby databases, minimizing the downtime of the primary database for planned and unplanned outages.
Complete data protection

A standby database also provides an effective safeguard against data corruptions and user errors. Storage level physical corruptions on the primary database do not propagate to the standby database. Similarly, logical corruptions or user errors that cause the primary database to be permanently damaged can be resolved. Finally, the redo data is validated at the time it is received at the standby database and further when applied to the standby database.
Efficient utilization of system resources

A physical standby database can be used for backups and read-only reporting, thereby reducing the primary database workload and saving valuable CPU and I/O cycles. A physical standby database can also be easily converted back and forth between being a physical standby database and an open read/write database, without compromising data protection. A logical standby database enables read-write access to a synchronized standby database, and/or adding local tables to the standby database that can also be updated, and/or creating additional indexes to optimize read performance.
Flexibility in data protection to balance availability against performance requirements

Oracle Data Guard offers the maximum protection, maximum availability, and maximum performance modes to help enterprises balance data availability against system performance requirements.
Protection from communication failures

If network connectivity is lost between the primary and one or more standby databases, redo data cannot be sent from the primary to those standby databases. Once connectivity is re-established, the missing redo data is automatically detected by Data Guard and the necessary archive logs are automatically transmitted to the standby databases. The standby databases are resynchronized with the primary database, with no manual intervention by the administrator.
Centralized and simple management

Data Guard Broker automates the management and monitoring tasks across the multiple databases in a Data Guard configuration. Administrators may use either Oracle Enterprise Manager or the Broker’s own specialized command-line interface (DGMGRL) to take advantage of this integrated management framework.
Integrated with Oracle database

Data Guard is available as an integrated feature of the Oracle Database (Enterprise Edition) at no extra cost

cloning faqa

2007-08-21T04:06:00.000-07:00

What is cloning?

Answer:
Cloning is the process of creating an identical copy of an already existing Oracle Applications system.

How can I clone an Oracle Applications system?

Answer:
There are two cloning methods documented in the following white papers available off of Oracle MetaLink Note 135792.1

Cloning Oracle Applications Release 11i
Cloning Oracle Applications Release 11i with Rapid Clone

Note: The third Cloning method (Cloning Oracle Applications Release 11i with AutoConfig) has been fully replaced by Cloning with Rapid Clone, and is no longer supported.

What are the differences between the two cloning methods?

Answer:

Cloning Oracle Applications Release 11i was originally published in conjunction with Release 11.5.5 and is applicable for all 11i releases up to 11.5.5 that are not AutoConfig enabled.
Cloning Oracle Applications Release 11i with Rapid Clone is applicable for all 11i systems that have migrated to AutoConfig and enabled Rapid Clone. This method contains steps to install AutoConfig and Rapid Clone.

What is the AD Cloning utility?

Answer:
AD Cloning utility (adclone.pl) is the name of the cloning command line utility. This utility is used to preserve and apply configuration information to the cloned target system.

What is Rapid Clone?

Answer:
Rapid Clone is the new cloning utility introduced in Release 11.5.8. Rapid Clone leverages the new installation and configuration technology utilized by Rapid Install. See OracleMetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone) for instructions on installing and enabling Rapid Clone.

How do I determine if my system is Rapid Clone enabled?

Answer:
First, verify that your system is AutoConfig enabled. Then, verify that you have applied the latest Rapid Clone patch documented in OracleMetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone). See Searching the Patch History Database in the AD Procedures Guide for instructions on searching for patches applied to your system.

What is AutoConfig?

Answer:
AutoConfig is a configuration tool that supports automated configuration of an Oracle Applications Instance. All of the information required for configuring an Applications instance is collected into a central repository, called the Applications Context. When the AutoConfig tool runs, it uses information from the Applications Context file to generate configuration files and update database profiles. See OracleMetaLink Note 165195.1 for details on installing and migrating to AutoConfig.

How do I determine if my system is AutoConfig enabled?

Answer:
There are several identifiers for when the system is AutoConfig enabled. The following are two common indicators:

Open the environment file APPSORA.env in your APPL_TOP. If the top of the file says that it is maintained by AutoConfig, then your system is probably using AutoConfig.
Check if there is an Applications Context file in the APPL_TOP/admin directory. This file will typically be named .xml or _.xml.
Check if there is an Applications Context file in the RDBMS ORACLE_HOME under the appsutil directory. This file will typically be named .xml or _.xml.

See OracleMetaLink Note 165195.1 for more details on identifying if your system already uses AutoConfig.

We are running Release 11.5.7 (or any prior release), which cloning method can we use?

Answer:
Due to the advancements in the cloning solution with Rapid Clone, all customers are now recommended to move to using Rapid Clone. if you are on release 11.5.7 or any release before 11.5.7, you will need to first enable AutoConfig on your system, if not already done, before you can use Rapid Clone as documented in the Cloning Oracle Applications Release 11i with Rapid Clone white paper.

We are running Release 11.5.8 (or any later release), which cloning method can we use?

Answer:
In 11.5.8 AutoConfig is enabled on the middle tier out of the box. In 11.5.9 and any later release, AutoConfig is enabled by default on both the database tier and the middle tier. Update AutoConfig and Rapid Clone code to the latest code line and use Rapid Clone to clone your system. Full instructions are in Cloning Oracle Applications Release 11i with Rapid Clone document 230672.1 on OracleMetalink.

	Single node to Single node	Recloning	Multi-node to Multi-node	Single node to Multi-node	Multi-node to Single node	With Oracle9i Database	Windows Platform
Cloning Oracle Applications	Available	Available	Available	Not Available	Not Available	Not Available	Available
Cloning Oracle Applications with Rapid Clone	Available	Available	Available	Available	Available	Available	Available

Prompt	Comment
database SID	Target database SID
domain name	Target system domain name
Prompts specific to the DB Tier
Target System database name	Target System database name
Target instance is a Real Application Cluster (RAC) instance (y/n)	Answer yes if the target system is going to be part of a RAC instance.
Current node is the first node in an N Node RAC Cluster (y/n)	This prompt only appears when you answered "yes" to the previous question. Answer Â¨yes" to this question if the current host is the first node being configured in the target system RAC cluster. The tool will then ask for the number of nodes that will exist in the final RAC instance and gather, the following information for every node: - Hostname - Database Sid - Instance number - Listener port - Private interconnect name Answer "no" to this qion if at least one node of the target RAC cluster has already been configured by Rapid Clone (i.e if you already replied "yes" to this question for any other node in the cluster). The tool will then prompt for the following information to connect to a life node (the answers must describe a node that has already been configured): - Hostname - Database Sid - Listener port
RDBMS ORACLE_HOME directory	Path to the Target system RDBMS ORACLE_HOME
Number of DATA_TOP's: DATA_TOP 1: DATA_TOP 2: DATA_TOP 3:	Database mount points. Enter the number of distinct directories containing the target database dbfs, then their paths.
Prompts specific to the Apps Tier
database server node	hostname of the machine hosting the database server
Does the target system have more than one applications tier server node (y/n)?	Answer yes if the target system is part of a multi-nodes configuration. The tool with then prompt for the hostnames of: - concurrent processing node - administration node - forms server node - web server node
Is the target system APPL_TOP divided into multiple mount points (y/n)?	Answer yes if the target system APPL_TOP is divided across multiple mount points. The tool will then prompt for each auxiliary mount (4 mounts): - APPL_TOP mount point - APPL_TOP aux.1 - APPL_TOP aux.2 - APPL_TOP aux.3 Note: if your APPL_TOP is divided into 2 or 3 mounts only, you can specify identical mounts to the above prompts.
APPL_TOP mount point	APPL_TOP directory
COMMON_TOP directory	COMMON_TOP directory
8.0.6 ORACLE_HOME directory	8.0.6 ORACLE_HOME directory
iAS ORACLE_HOME directory	iAS ORACLE_HOME directory
Location of JDK 1.3.1	Location of JDK 1.3.1
Prompt common to DB and Apps Tiers
Port pool number:[0-99]	Enter the port pool that you want to use on the target system. Make sure to specify the same port pool on the DBTier and the AppsTier. If the source and target machines are different, you have the option to preserve the source port values on the target system.

Port Name	Autoconfig Variable	(Default) Port Numbers allocated for Port Pool: 0	(Custom) Port Numbers allocated for Port Pool:
Web Listener Port	s_webport	8000	8001
Database Port	s_dbport	1521	1522
RPC Port	s_rpcport	1626	1627
Reports Port	s_repsport	7000	7001
OPROC Manager Port	s_oprocmgr_port	8100	8101
Web PLSQL Port	s_webport_pls	8200	8201
Servlet Port	s_servletport	8800	8801
Forms Listener Port	s_formsport	9000	9001
Metrics Server Data Port	s_metdataport	9100	9101
Metrics Server Req. Port	s_metreqport	9200	9201
JTF Fulfillment Server Port	s_jtfuf_port	9300	9301
iMeeting Collaboration Server Port	s_imtsrvport	9500	9501
iMeeting Recording Server Port	s_imtrecport	9600	9601
iMeeting Monitor (iMon) Port	s_imtimonport	9700	9701
Map Viewer Servlet Port	s_mapviewer_port	9800	9801
OEM Web Utility Port	s_oemweb_port	10000	10001
VisiBroker OrbServer Agent Port	s_osagent_port	10100	10101
MSCA Server Port	s_mwaPortNo	10200	10201
MSCA Dispatcher Port	s_mwaDispatcherPort	10300	10301
TCF Port	s_tcfport	15000	15001
OACORE Servle Port Range	s_oacore_servlet_portrange	16000-16009	16010-16019
Discoverer Servlet Port Range	s_disco_servlet_portrange	17000-17009	17010-17019
Forms Servlet Port Range	s_forms_servlet_portrange	18000-18009	18010-18019
XMLSVCS Servlet Port Range	s_xmlsvcs_servlet_portrange	19000-19009	19010-19019
Forms Start Port	s_frmStartPort	20000	20001
Java Object Cache Port	s_java_object_cache_port	12345	12346

Table Name	Column Name	Column Value Details
WF_NOTIFICATION_ATTRIBUTES	TEXT_VALUE	Value starts with http:// : Update to new web host
WF_ITEM_ATTRIBUTE_VALUES	TEXT_VALUE	Value starts with "http:// : Update to new web host
WF_SYSTEMS	GUID	Create a new system defined as the new global database name using the Workflow Administrator Web Applications responsibility.
WF_SYSTEMS	NAME	Value needs to be replaced with the database global name
WF_AGENTS	ADDRESS	Update database link with the new database global name.
FND_FORM_FUNCTIONS	WEB_HOST_NAME	Update with the new web host name
FND_FORM_FUNCTIONS	WEB_AGENT_NAME	Update to point at the new PLSQL listener name
FND_CONCURRENT_REQUESTS	LOGFILE_NAME	Update with the correct path to the logfile directory
FND_CONCURRENT_REQUESTS	OUTFILE_NAME	Update with the new directory path on the target system

neo is alive

Internet Explorer Crashes When Forms Is Launched

Internet Explorer Crashes When Forms Is Launched

Applies to:

Symptoms

Changes

Cause

Solution

About Log files in $APPLCSF/$APPLOG directory

Concurrent request pending normal for long time

Tablespace-size(free,Used,Pct)

Kill Oracle process at UNIX

Imp Links

Kill the Locked session

AOLJ Test

Form Compile

FND&AD Tables

Cron and Crontab

Printer Configuration

health check

MULTIPLEXING OF ONLINE REDOLOG FILES

Data Guard

cloning faqa

What is cloning?

How can I clone an Oracle Applications system?

What are the differences between the two cloning methods?

What is the AD Cloning utility?

What is Rapid Clone?

How do I determine if my system is Rapid Clone enabled?

What is AutoConfig?

How do I determine if my system is AutoConfig enabled?

We are running Release 11.5.7 (or any prior release), which cloning method can we use?

We are running Release 11.5.8 (or any later release), which cloning method can we use?

Our Oracle Applications system is on Windows, which cloning method can we use?

We have a Platinum installation of Oracle Applications. Can we clone our system?

Can I clone from one operating system version to another?

Can I clone from one platform to a different platform?

Can I reclone just the database?

Can I clone a single-node system to a multi-node system?

Can I clone a multi-node system to a single-node system?

What cloning options are available for each cloning method?

Does Rapid Clone modify the source system?

How does adcfgclone.pl know the target system values?

What is the port pool? What if I want to give a specific value to a Server Port?

Does Rapid Clone preserve the patch history?

Can I clone a clone?

Can I change the database dbf files layout while cloning?

What is the oraInventory?

What is a binary oraInventory? Is my Inventory binary?

What is a XML oraInventory? Is my Inventory XML?

What is the Global (or Central) Inventory?

What is the Local (or Home) Inventory?

How does Rapid Clone deal with the oraInventory?

Why don't I need to manually copy the oraInventory when cloning?

What does OUISetup.pl do?

System-Level Response-Time Analysis

11i Post Cloning Steps

Section 3: Finishing Tasks

Oracle RMAN

Overview of RMAN Functional Components

New Features in Oracle Database 11g

New Features in Oracle Database 10g Release 2

List the users in command line

SQL FAQ`s

Linux

9i to 10g

Metalink DocID

ORA-0600