The concurrent manager is the job-scheduling component of Oracle Apps:
The following SQL scripts located under $FND_TOP/sql are useful when diagnosing concurrent manager problems:
1. afimchk.sql Tells the status of the ICM and PMON method
2. afcmstat.sql Lists active manager processes
3. afrqrun.sql Lists all the running, waiting and terminating requests
4. afrqwait.sql Lists requests that are constrained and waiting for the ICM to release them
5. afrqscm.sql Prints log file name of managers that can run a given request. It can be used to check for possible errors when a request stays in pending status. It requires a request id value.
6. afcmcreq.sql Prints the log file name of the manager that processed the request
7. afrqstat.sql Summary of completed concurrent requests grouped by completion status and execution type. It requires number of days prior to today on which to report parameter.
8. afimlock.sql Lists locks that the ICM is waiting to get
9. afcmrrq.sql Lists managers that currently are running a request
Techniques for checking the status of the concurrent manager:
1. Log in to applications as System Administrator responsibility and navigate to the concurrent manager administration page (Concurrent, Manager, Administrator) and under the processes column if the target and actual column equal the same number (above 0) this means the managers are up and running.
2. You can also go into SQL*PLUS as APPS and run the following script:
SQL> @$FND_TOP/sql/afimchk.sql
This script will return output similar to the below:
Status Since Method
-------------------------------------- --------- ----------- ------
Internal Conc Manager is running on - colapp03 05-MAR-99 06:41:32 PM LOCK
Also, this on bouncing (stopping and re-starting) the concurrent manager.
As an practice, u should stop ur concurrent manager service through adcmctl lying under $APPLCSF/scripts/host_sid
whenever there's a need to shutdown n then startup ur database.
As there could be a scenario that ur ICM wont work.
Wednesday, June 11, 2008
How To Use FNDCPASS to Change The Oracle Users, APPS, APPLSYS and Application Module Passwords (INV, AR, AP, etc.) For Applications 11.5 in Unix
goal: How to use FNDCPASS to change the oracle users, APPS, APPLSYS and
application module passwords (INV, AR, AP, etc.) for Applications 11.5 in Unix
fact: Oracle Application Object Library 11.5
fix:
1. Download and install the Password changing utility available from
patch 1685689 or later if not already included in your
version of Applications.
NOTE 1: FNDCPASS should be run from the database tier to prevent encryption issues.
2. Issue the commands at the Unix command line similar to the following:
To change the APPS and APPLSYS passwords:
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS
Ex: $FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS NEWPASSWORD
NOTE 2: Changing the APPLSYS password automatically changes the APPS password
to match as these two must always agree.
To change an Oracle user password:
FNDCPASS apps/apps 0 Y system/manager ORACLE oracle user new
password
Ex: FNDCPASS apps/apps 0 Y system/manager ORACLE GL GLPASSWORD
NOTE 3: Altering the ORACLE User name (schemas) passwords with FNDCPASS without first updating the APPS/APPLSYS password with FNDCPASS will cause the ORACLE User password to be undecodable by Applications.
Use FNDCPASS to "refresh" the APPS/APPLSYS password, even if it is to the same value.
To change an application user password:
FNDCPASS apps/apps 0 Y system/manager USER username password
Ex: FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME
NOTE 4: VERY IMPORTANT!!
When changing the password for APPS it is important to manually change the APPS
password in the following files as well as necessary:
1. $ORACLE_HOME/listener/cfg/wdbsvr.app file as well. (Otherwise users will not
be able to login to the Personal Home Page or Self-service web apps.) This may also be necessary in the $IAS_ORACLE_HOME\Apache\modplsql\cfg\wdbsvr.app file
2. Workflow Notification Mailer - $FND_TOP/resource/wfmail.cfg
3. The concurrrent manager start script.
4. $OA_HTML/bin/appsweb.cfg
5. $AD_TOP/admin/template/CGIcmd.dat may contain the password if it is being
used.
(Please refer to Note 159033.1 How to Setup Oracle Reports in Portal to Use
CGICMD.DAT File)
6. If you instance is Multi-node and Autoconfig enabled, it may be necessary to invoke Autoconfig to implement the above changes.
For additional information, please see the README file included with the patch.
application module passwords (INV, AR, AP, etc.) for Applications 11.5 in Unix
fact: Oracle Application Object Library 11.5
fix:
1. Download and install the Password changing utility available from
patch 1685689 or later if not already included in your
version of Applications.
NOTE 1: FNDCPASS should be run from the database tier to prevent encryption issues.
2. Issue the commands at the Unix command line similar to the following:
To change the APPS and APPLSYS passwords:
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS
Ex: $FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS NEWPASSWORD
NOTE 2: Changing the APPLSYS password automatically changes the APPS password
to match as these two must always agree.
To change an Oracle user password:
FNDCPASS apps/apps 0 Y system/manager ORACLE oracle user new
password
Ex: FNDCPASS apps/apps 0 Y system/manager ORACLE GL GLPASSWORD
NOTE 3: Altering the ORACLE User name (schemas) passwords with FNDCPASS without first updating the APPS/APPLSYS password with FNDCPASS will cause the ORACLE User password to be undecodable by Applications.
Use FNDCPASS to "refresh" the APPS/APPLSYS password, even if it is to the same value.
To change an application user password:
FNDCPASS apps/apps 0 Y system/manager USER username password
Ex: FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME
NOTE 4: VERY IMPORTANT!!
When changing the password for APPS it is important to manually change the APPS
password in the following files as well as necessary:
1. $ORACLE_HOME/listener/cfg/wdbsvr.app file as well. (Otherwise users will not
be able to login to the Personal Home Page or Self-service web apps.) This may also be necessary in the $IAS_ORACLE_HOME\Apache\modplsql\cfg\wdbsvr.app file
2. Workflow Notification Mailer - $FND_TOP/resource/wfmail.cfg
3. The concurrrent manager start script.
4. $OA_HTML/bin/appsweb.cfg
5. $AD_TOP/admin/template/CGIcmd.dat may contain the password if it is being
used.
(Please refer to Note 159033.1 How to Setup Oracle Reports in Portal to Use
CGICMD.DAT File)
6. If you instance is Multi-node and Autoconfig enabled, it may be necessary to invoke Autoconfig to implement the above changes.
For additional information, please see the README file included with the patch.
How to Find Patching History (10.7, 11.0, 11i)
Starting with Oracle Applications 11.5.5 (or 11i.AD.E (Patch 1945611) and
higher) a new autopatch feature that causes all patch history information to be
stored in the database instead of the applptch.txt and applpsum.txt files was
introduced.
Two scripts, adphrept.sql (patch history) and adfhrept.sql (file history),
provide the patch and file history reports (see Note 162498.1). Both are
located in the $AD_TOP/patch/115/sql directory. When the scripts are ran under
the APPS schema from Sql*Plus, they create report files called adphrept.r and
adfhrept.r, respectively.
There are 16 parameters to pass through the adphrept.sql script. It takes some
time to understand how to use these parameters effectively. As an alternative,
the following SQL statements may be used to obtain basic patch history from the
database:
a. To find a list of all the patches that have been applied:
select DRIVER_FILE_NAME
from AD_PATCH_DRIVERS;
b. To find if a particular patch has been applied:
select DRIVER_FILE_NAME
from AD_PATCH_DRIVERS
where DRIVER_FILE_NAME like '%2408149%';
Note: the SQL statements will return a listing of the respective C, D, and G
drivers of each patch. Thus, for the SQL statement in (b) above if the patch
had been applied to this instance, the results would be:
DRIVER_FILE_NAME
------------------------------
g2408149.drv
c2408149.drv
d2408149.drv
(Also note that any patches, which were applied using admrgpch, will not be
listed in the results of the above SQL statements.)
3. Here is a useful option to find details of patchsets applied to any Oracle
Applications instance, whether 10.7, 11.0, or 11i. It is called the Patchset
Comparison Utility tool (see Note 139684.1).
A UNIX shell script is used to compare the Oracle Applications' applptch.txt
file (or AD_PATCH_DRIVERS table) with the currently available patchsets. In
order to keep this script up to date, it is put out on the Oracle ftp site on a
nightly basis. Therefore, the patchset analysis is only as up to date as of the
last time this script was downloaded.
There are four sections within a typical output of this report:
a. The top of the script tells the date when the patchsets were last,
the date when the report was ran, the current Release Version from
the applptch.txt file, and the URL of a new version of the
patchsets.sh script with the latest patchset data.
b. The second section is a complete list of the applied patchsets that
match ARU.
c. The third section states the most recent patchsets for each of the
products that have not yet been applied.
d. The final section provides the base patchset listing that came
bundled in that particular Oracle Applications version.
4. A GUI for querying Patch History and File History information is available
as part of the HTML-based version of Oracle Applications Manager (OAM 11i).
RELATED DOCUMENTS
-----------------
139684.1 (Oracle Applications Current Patchset Comparison Utility)
162498.1 (Storing Applied Patch Information In The Database For Applications 11i)
162524.1 (How To Identify What Patches and Patchsets Installed in Applications 11i)
140848.1 (Where to Find the Applications Patch History File (applptch.txt))
181665.1 (Release 11i Adpatch Basics)
higher) a new autopatch feature that causes all patch history information to be
stored in the database instead of the applptch.txt and applpsum.txt files was
introduced.
Two scripts, adphrept.sql (patch history) and adfhrept.sql (file history),
provide the patch and file history reports (see Note 162498.1). Both are
located in the $AD_TOP/patch/115/sql directory. When the scripts are ran under
the APPS schema from Sql*Plus, they create report files called adphrept.r and
adfhrept.r, respectively.
There are 16 parameters to pass through the adphrept.sql script. It takes some
time to understand how to use these parameters effectively. As an alternative,
the following SQL statements may be used to obtain basic patch history from the
database:
a. To find a list of all the patches that have been applied:
select DRIVER_FILE_NAME
from AD_PATCH_DRIVERS;
b. To find if a particular patch has been applied:
select DRIVER_FILE_NAME
from AD_PATCH_DRIVERS
where DRIVER_FILE_NAME like '%2408149%';
Note: the SQL statements will return a listing of the respective C, D, and G
drivers of each patch. Thus, for the SQL statement in (b) above if the patch
had been applied to this instance, the results would be:
DRIVER_FILE_NAME
------------------------------
g2408149.drv
c2408149.drv
d2408149.drv
(Also note that any patches, which were applied using admrgpch, will not be
listed in the results of the above SQL statements.)
3. Here is a useful option to find details of patchsets applied to any Oracle
Applications instance, whether 10.7, 11.0, or 11i. It is called the Patchset
Comparison Utility tool (see Note 139684.1).
A UNIX shell script is used to compare the Oracle Applications' applptch.txt
file (or AD_PATCH_DRIVERS table) with the currently available patchsets. In
order to keep this script up to date, it is put out on the Oracle ftp site on a
nightly basis. Therefore, the patchset analysis is only as up to date as of the
last time this script was downloaded.
There are four sections within a typical output of this report:
a. The top of the script tells the date when the patchsets were last,
the date when the report was ran, the current Release Version from
the applptch.txt file, and the URL of a new version of the
patchsets.sh script with the latest patchset data.
b. The second section is a complete list of the applied patchsets that
match ARU.
c. The third section states the most recent patchsets for each of the
products that have not yet been applied.
d. The final section provides the base patchset listing that came
bundled in that particular Oracle Applications version.
4. A GUI for querying Patch History and File History information is available
as part of the HTML-based version of Oracle Applications Manager (OAM 11i).
RELATED DOCUMENTS
-----------------
139684.1 (Oracle Applications Current Patchset Comparison Utility)
162498.1 (Storing Applied Patch Information In The Database For Applications 11i)
162524.1 (How To Identify What Patches and Patchsets Installed in Applications 11i)
140848.1 (Where to Find the Applications Patch History File (applptch.txt))
181665.1 (Release 11i Adpatch Basics)
Thursday, June 5, 2008
What happens when you login to Apps?
Firstly and surely there is a URL for oracle applications that is structured possibly in below format, although it can vary from version of apps.
http://machinename:portnumber/OA_HTML/US/ICXINDEX.htm
http://machinename:portnumber /oa_servlets/AppsLogin
When you join an Oracle Apps development team for an employer, you will first be given URL of the development environment.
In any Oracle Apps implementation project (assuming it has gone live), there are minimum of three environments, each with different URL's and different database instances.
These are:-
---------------
Development environment
Testing environment
Production environment
You will most probably, as a techie, be given url,username ad password of the development environment.
What happens when you login(no advanced info here):-
--------------------------------------
A. Your login gets authenticated against a table named fnd_user for your username and password. The screen below is where username and password defined. This screen is called user definition screen. Only system administrators have access to this screen.
B. As you can see above, this username xxpassi is attached to two responsibilities (this will be discussed in details in latter training lesson). It is this assignment to the responsibility that controls what a logged in person can do and can't do. In layman’s words, a responsibility is a group of menu.
It will prompt you to change your password, to a value different than that assigned by System Administrator.
You might be prompted to install jinitiator…..just keep clicking OK…OK for all Jinitiator messages). Effectively, what I mean to say is that you do not need to download jinitiator from anywhere; Oracle will do this automatically (provided your DBA’s got this cofig’ed) for you during your first logon attempt from the PC. Once your jInitiator gets installed .
Oracle internally uses a login named GUEST, prior to invoking validation of actual username. Some people regard this as a security threat, but it isn’t. Your DBA’s can change the “guest” password from its default value after installation.
Oracle uses a DB User account named applsyspub to which it first connects during validation of LOGIN. This user account has very restricted privileges and has access to below objects (primarily for authentication purposes):-
FND_APPLICATION
FND_UNSUCCESSFUL_LOGINS
FND_SESSIONS
FND_PRODUCT_INSTALLATIONS
FND_PRODUCT_GROUPS
FND_MESSAGES
FND_LANGUAGES_TL
FND_APPLICATION_TL
FND_APPLICATION_VL
FND_LANGUAGES_VL
FND_SIGNON
FND_PUB_MESSAGE
FND_WEBFILEPUB
FND_DISCONNECTED
FND_MESSAGE
FND_SECURITY_PKG
FND_LOOKUPS
http://machinename:portnumber/OA_HTML/US/ICXINDEX.htm
http://machinename:portnumber /oa_servlets/AppsLogin
When you join an Oracle Apps development team for an employer, you will first be given URL of the development environment.
In any Oracle Apps implementation project (assuming it has gone live), there are minimum of three environments, each with different URL's and different database instances.
These are:-
---------------
Development environment
Testing environment
Production environment
You will most probably, as a techie, be given url,username ad password of the development environment.
What happens when you login(no advanced info here):-
--------------------------------------
A. Your login gets authenticated against a table named fnd_user for your username and password. The screen below is where username and password defined. This screen is called user definition screen. Only system administrators have access to this screen.
B. As you can see above, this username xxpassi is attached to two responsibilities (this will be discussed in details in latter training lesson). It is this assignment to the responsibility that controls what a logged in person can do and can't do. In layman’s words, a responsibility is a group of menu.
It will prompt you to change your password, to a value different than that assigned by System Administrator.
You might be prompted to install jinitiator…..just keep clicking OK…OK for all Jinitiator messages). Effectively, what I mean to say is that you do not need to download jinitiator from anywhere; Oracle will do this automatically (provided your DBA’s got this cofig’ed) for you during your first logon attempt from the PC. Once your jInitiator gets installed .
Oracle internally uses a login named GUEST, prior to invoking validation of actual username. Some people regard this as a security threat, but it isn’t. Your DBA’s can change the “guest” password from its default value after installation.
Oracle uses a DB User account named applsyspub to which it first connects during validation of LOGIN. This user account has very restricted privileges and has access to below objects (primarily for authentication purposes):-
FND_APPLICATION
FND_UNSUCCESSFUL_LOGINS
FND_SESSIONS
FND_PRODUCT_INSTALLATIONS
FND_PRODUCT_GROUPS
FND_MESSAGES
FND_LANGUAGES_TL
FND_APPLICATION_TL
FND_APPLICATION_VL
FND_LANGUAGES_VL
FND_SIGNON
FND_PUB_MESSAGE
FND_WEBFILEPUB
FND_DISCONNECTED
FND_MESSAGE
FND_SECURITY_PKG
FND_LOOKUPS
Autoconfig
What is Autoconfig ?
Autoconfig is tool in Apps to configure oracle Applications 11i , Application Tier as well Database Tier.
Autoconfig is method of configuring Oracle Applications . All the information required to configure Oracle Apps 11i is stored in file called as Context file. So there are two context file, one for Database Tier & Second for Application Tier. Context file is repository for configuration stored in xml format. Its xml file and file name format is_.xml so if your machine name is machine1 & SID is VISION then context file name will be VISION_machine1.xml
How to run Autoconfig ?
If you want to configure database tier then you have to execute autoconfig script adautocfg.sh on database tier else if you want to configure on application tier (Middle Tier ) then you have to execute one on middle tier .
Here is the script location
For Database tier its $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME
For Application Tier its $OAD_TOP/admin/scripts/$CONTEXT_NAME
adautocfg.sh calls adconfig.sh from $AD_TOP/bin which inturn calls adconfig.pl from $AD_TOP/bin
Don't forget to take backup before executing autoconfig.
What source of information for Autoconfig to update configuration files ?
If you are wondering where is configuration information stored about your apps 11i instance based on which it updates your Instance then this file is xml file also called as Context file and its in $APPL_TOP/admin for Application Tier or $ORACLE_HOME/appsutil in Database Tier
So xml file also called as context file or autoconfig configuration file stores configuration in these main tags for Application Tier
oa_context : For Start of Context file & context related information
oa_system : System related information under this there are further sections which I'll discuss in next post
oa_host : Information specific to local hosts like users, groups, Apps User, Groups..
oa_install : Installation related information like type of FS, Installation Location
oa_environments : environment specific information this tag has further subsections
oa_processes : this section is related to processes for forms, apache, reports, cm i.e. for all services
oa_custom : This section contain any custom setting (If any)
I'll explain subsections under this main section in my coming posts & few important parameters
Autoconfig Basics
Unwrapping Autoconfig Config file, XML file or Context File
Autoconfig Questions on My Site
Now lets understand how Autoconfig populate/creates files , In order to understand whole process you as apps dba need to understand template files under each product top or tech stack directory in oracle Applications 11i.
These template directory are under each top. In order to explain here I am taking example on how Apache (Oracle Web Server) related files are created when you run Autoconfig.
If you go to $IAS_ORACLE_HOME/appsutil/template directory, all template files related to iAS ORACLE HOME like http.conf , jserv.conf, zone.properties .. are stored in this their respective directories under template directory.
So template file to create httpd.conf is stored in $IAS_ORACLE_HOME/appsutil/template/Apache/Apache/conf
similarly template file for jserv.conf will be in
$IAS_ORACLE_HOME/appsutil/template/Apache/Jserv/etc
In these directories you will see file like httpd.conf or jserv.conf with parameter like
ApJServGroup OACoreGroup 1 1 %s_weboh_oh%/Apache/Jserv/etc/jserv.properties (in jserv.conf under template directory)
or
ServerAdmin applmgr@%s_domainname% ( in httpd.conf under template directory)
Now when Autoconfig executes , its picks up these files & replaces parameters like
%s_weboh_oh% & %s_domainname% from Autoconfig Configuration File i.e. Context file or XML file of format SID_HOSTNAME.xml (Discussed in previous post)
So in my case for vision instance in xml file has these values
s_weboh_oh is /u01/applmgr/VIS11i/ora9/iAS
s_domainname is co.in
Autoconfig is tool in Apps to configure oracle Applications 11i , Application Tier as well Database Tier.
Autoconfig is method of configuring Oracle Applications . All the information required to configure Oracle Apps 11i is stored in file called as Context file. So there are two context file, one for Database Tier & Second for Application Tier. Context file is repository for configuration stored in xml format. Its xml file and file name format is
How to run Autoconfig ?
If you want to configure database tier then you have to execute autoconfig script adautocfg.sh on database tier else if you want to configure on application tier (Middle Tier ) then you have to execute one on middle tier .
Here is the script location
For Database tier its $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME
For Application Tier its $OAD_TOP/admin/scripts/$CONTEXT_NAME
adautocfg.sh calls adconfig.sh from $AD_TOP/bin which inturn calls adconfig.pl from $AD_TOP/bin
Don't forget to take backup before executing autoconfig.
What source of information for Autoconfig to update configuration files ?
If you are wondering where is configuration information stored about your apps 11i instance based on which it updates your Instance then this file is xml file also called as Context file and its in $APPL_TOP/admin for Application Tier or $ORACLE_HOME/appsutil in Database Tier
So xml file also called as context file or autoconfig configuration file stores configuration in these main tags for Application Tier
oa_context : For Start of Context file & context related information
oa_system : System related information under this there are further sections which I'll discuss in next post
oa_host : Information specific to local hosts like users, groups, Apps User, Groups..
oa_install : Installation related information like type of FS, Installation Location
oa_environments : environment specific information this tag has further subsections
oa_processes : this section is related to processes for forms, apache, reports, cm i.e. for all services
oa_custom : This section contain any custom setting (If any)
I'll explain subsections under this main section in my coming posts & few important parameters
Autoconfig Basics
Unwrapping Autoconfig Config file, XML file or Context File
Autoconfig Questions on My Site
Now lets understand how Autoconfig populate/creates files , In order to understand whole process you as apps dba need to understand template files under each product top or tech stack directory in oracle Applications 11i.
These template directory are under each top. In order to explain here I am taking example on how Apache (Oracle Web Server) related files are created when you run Autoconfig.
If you go to $IAS_ORACLE_HOME/appsutil/template directory, all template files related to iAS ORACLE HOME like http.conf , jserv.conf, zone.properties .. are stored in this their respective directories under template directory.
So template file to create httpd.conf is stored in $IAS_ORACLE_HOME/appsutil/template/Apache/Apache/conf
similarly template file for jserv.conf will be in
$IAS_ORACLE_HOME/appsutil/template/Apache/Jserv/etc
In these directories you will see file like httpd.conf or jserv.conf with parameter like
ApJServGroup OACoreGroup 1 1 %s_weboh_oh%/Apache/Jserv/etc/jserv.properties (in jserv.conf under template directory)
or
ServerAdmin applmgr@%s_domainname% ( in httpd.conf under template directory)
Now when Autoconfig executes , its picks up these files & replaces parameters like
%s_weboh_oh% & %s_domainname% from Autoconfig Configuration File i.e. Context file or XML file of format SID_HOSTNAME.xml (Discussed in previous post)
So in my case for vision instance in xml file has these values
s_weboh_oh is /u01/applmgr/VIS11i/ora9/iAS
s_domainname is co.in
Installing Oracle Apps 11i
1.Check the prerequisites-Windows/Unix/Linux , jdk and perl is installed or not.
2.Check space: 26 Gb for file systems,16-20 GB for forms/reports/Web server, 32 GB for fresh db, 75 for vision,24 GB for stage area, 10GB for each language support, 800Mb in database for each language. – 150GB in total. Average of 60 GB.
2.Create the login accounts for applmgr and oracle logging in as root user who will have to be the owners for APPL_TOP and ORA_TOP respectively.
Adduser applmgr
3.Create mount points.
1.APPL_TOP
2.ORA_TOP
3.COMMON_TOP
4.DATA_TOP
5.DB_TOP
Then chown of appl_top and ora_top.
3.Insert the cd and run adautostg.pl
Go to the location where the rapidwiz is and run
Perl adautostg.pl
It will create different directories for the cds. – startdisk, oraApps, oradb, oraiAs, oraAppDb, oraNls.
We have to specify the directory where stage will be created. Eg /u01.
4. Run the rapidwiz
Go to the stage location
Unix:
Cd /u01/stage11i/startCD/Disk1/rapidwiz
rapidwiz
Windows:
Cd f:\
Cd stage11i\startCd\Disk1\rapidwiz
rapidwiz.cmd.
Single Node installation:
1.Start the rapidwiz wizard
2.TYPE OF OPERATION:select the wizard operation
1)install the e business suite
2)express configuration – just have to specify the top level directories and configuration. Rest the wizard will use default names.
3)upgrade to oracle apps e-business 11i.
3. CONFIGURATION:Specify YES and the location of configuration files or else NO for specifying the configuration by ourselves.
4. TYPE: single node or multimode.
5.DATABASE TYPE:fresh/vision vision (for training purposes)
6.DATABASE DIRECTOTIES:
Os user
Os Group
Base install directory
Oracle Home
DATA_TOP(SYS)
DATA_TOP(LOG)
DATA_TOP(TXN)
DATA top(ARCHIVE)
7.Product licence type
*E-business suite licensing – automatic
*Component application-each individual product is installed after getting the child option from us.
8.country specific functionality
9.Additional languages
10.NLS settings
11.Enter node specific functionality
Appl_top,Common_top,RDBMS home,ias oracle_home
12.review global settings
Dbport
Listener port
Forms listener port
Report port
13.perform pre – install check
14.install
15.perform post installation check.
If it is tick mark then success.
If ! mark then review
If X mark then go back and correct something.
Multinode installation
1.Start the rapidwiz
2.Select the type
1)ebuisiness suite
2)express configuration
3) upgrade
3.Give YES and specify the configuration file location or choose NO.
4.Select the TYPE of installation
1)single node
2)multimode
5.Choose whether to enable load balancing or not.
If YES then requests can be spread across concurrent programs and forms.
And specify the number of concurrent managers and forms server
6.assign servers to nodes indicating the operating system.
7.Setting up shared appl_top option is there
8.Choose the database type FRESH/VISION
9.Setup database installation directory
10.Select product licence type
*Ebusiness suite licensing
*component applications licensing
11. NLS language support
12.select additional languages
13.internationalization settings are selected (character set)
14. APPL_TOP,COMMON_TOP,iAS home, RDMS home is selected.
15.Review global settings
16.Perform pre-installation check
17.Begin installation
18. Perform post-installation.
2.Check space: 26 Gb for file systems,16-20 GB for forms/reports/Web server, 32 GB for fresh db, 75 for vision,24 GB for stage area, 10GB for each language support, 800Mb in database for each language. – 150GB in total. Average of 60 GB.
2.Create the login accounts for applmgr and oracle logging in as root user who will have to be the owners for APPL_TOP and ORA_TOP respectively.
Adduser applmgr
3.Create mount points.
1.APPL_TOP
2.ORA_TOP
3.COMMON_TOP
4.DATA_TOP
5.DB_TOP
Then chown of appl_top and ora_top.
3.Insert the cd and run adautostg.pl
Go to the location where the rapidwiz is and run
Perl adautostg.pl
It will create different directories for the cds. – startdisk, oraApps, oradb, oraiAs, oraAppDb, oraNls.
We have to specify the directory where stage will be created. Eg /u01.
4. Run the rapidwiz
Go to the stage location
Unix:
Cd /u01/stage11i/startCD/Disk1/rapidwiz
rapidwiz
Windows:
Cd f:\
Cd stage11i\startCd\Disk1\rapidwiz
rapidwiz.cmd.
Single Node installation:
1.Start the rapidwiz wizard
2.TYPE OF OPERATION:select the wizard operation
1)install the e business suite
2)express configuration – just have to specify the top level directories and configuration. Rest the wizard will use default names.
3)upgrade to oracle apps e-business 11i.
3. CONFIGURATION:Specify YES and the location of configuration files or else NO for specifying the configuration by ourselves.
4. TYPE: single node or multimode.
5.DATABASE TYPE:fresh/vision vision (for training purposes)
6.DATABASE DIRECTOTIES:
Os user
Os Group
Base install directory
Oracle Home
DATA_TOP(SYS)
DATA_TOP(LOG)
DATA_TOP(TXN)
DATA top(ARCHIVE)
7.Product licence type
*E-business suite licensing – automatic
*Component application-each individual product is installed after getting the child option from us.
8.country specific functionality
9.Additional languages
10.NLS settings
11.Enter node specific functionality
Appl_top,Common_top,RDBMS home,ias oracle_home
12.review global settings
Dbport
Listener port
Forms listener port
Report port
13.perform pre – install check
14.install
15.perform post installation check.
If it is tick mark then success.
If ! mark then review
If X mark then go back and correct something.
Multinode installation
1.Start the rapidwiz
2.Select the type
1)ebuisiness suite
2)express configuration
3) upgrade
3.Give YES and specify the configuration file location or choose NO.
4.Select the TYPE of installation
1)single node
2)multimode
5.Choose whether to enable load balancing or not.
If YES then requests can be spread across concurrent programs and forms.
And specify the number of concurrent managers and forms server
6.assign servers to nodes indicating the operating system.
7.Setting up shared appl_top option is there
8.Choose the database type FRESH/VISION
9.Setup database installation directory
10.Select product licence type
*Ebusiness suite licensing
*component applications licensing
11. NLS language support
12.select additional languages
13.internationalization settings are selected (character set)
14. APPL_TOP,COMMON_TOP,iAS home, RDMS home is selected.
15.Review global settings
16.Perform pre-installation check
17.Begin installation
18. Perform post-installation.
Clonning with Rapid Clone
Cloning Oracle Applications Release 11i with Rapid Clone
Cloning creates an identical copy of an existing Oracle Applications system. There are various reasons for cloning an Oracle Applications system such as:
Creating a copy of the production system for testing updates.
Migrating an existing system to new hardware.
Creating a stage area to reduce patching downtime.
This document describes the process of cloning an Oracle Applications Release 11i system. The most current version of this note is document 230672.1 on OracleMetaLink. A FAQ is also available in document 230672.1 on OracleMetaLink. A FAQ is also available in document 216664.1 on OracleMetaLink.document 216664.1 on OracleMetaLink.
Note: Rapid Clone is currently not supported on Windows Itanium or on Windows x86-64 (AMD64/EM64T).
Attention: Windows users. This document typically uses UNIX syntax when specifying directories; Please substitute the appropriate Windows syntax
Section 1: Prerequisites
Tasks to perform before using Rapid Clone.
Section 2: Clone Oracle Applications 11i
Tasks to prepare, copy, configure, and verify a cloned Applications System.
Section 3: Finishing Tasks
Tasks to complete the cloning process.
Section 4: Advanced Cloning Methods
Tasks for advanced options such as refreshing and multi-node cloning.
Conventions
Convention Meaning
Source system Applications system being cloned.
Target system Applications system being created as a copy of the source.
APPLMGR User which owns the applications file system (APPL_TOP and application tier technology stack)
ORACLE User which owns the database file system (RDBMS ORACLE_HOME and database files).
CONTEXT_NAME The CONTEXT_NAME variable refers to the name of the Applications Context file. For systems installed with Rapid Install 11.5.8 or earlier, this value will typically be set to. For new AutoConfig or Rapid Clone customers, CONTEXT_NAME will be set to _.
Monospace Text Represents command line text. Type this command exactly as shown.
< > Text enclosed in angle brackets represents a variable. Substitute a value for the variable text. Do not type the angle brackets.
________________________________________
Section 1: Prerequisites
Before cloning, prepare the source system by applying patches and running AutoConfig.
1. Verify source and target nodes software versions
In addition to the Oracle Applications software requirements (see Installing Oracle Applications Release 11i Part No. B10638-01), the following software component versions must exist on the source and/or target nodes. The location column indicates the node where the software component must be present.
Software Minimum Version Location Details
Oracle Universal Installer 2.2.0.19 All source system nodes Apply OUI22 patch 5035661 on every iAS and RDBMS ORACLE_HOME to be cloned. Do not apply the patch to your RDBMS ORACLE_HOME, if you have Oracle 10g or higher installed.
Perl 5.005 Source and target database nodes Use the Perl shipped with iAS1022 and RDBMS 9i if available or download it from Perl.com. Perl must be in the PATH before cloning. Windows users: do not use Perl from MKSToolKit.
JRE 1.1.8 Source database node If the RDBMS ORACLE_HOME was not installed using Rapid Install, install JRE 1.1.8 into the/jre/1.1.8 directory.
JRE 1.3.1 Source database node Windows users only: install JRE 1.3.1 into the/jre/1.3.1 directory. See Appendix A for installation instructions.
JDK 1.3.1 Target middle-tier applications nodes Refer to Upgrading to JDK 1.3 with Oracle Applications 11i on OracleMetaLink for instructions.
Zip 2.3 All source nodes Download from InfoZip. Zip must be in your PATH for cloning.
OS utilities N/A All target nodes OS utilities (see 11i Install Manual) must be in the the PATH when running adcfgclone.pl (Unix: make,ld,cc,ar - Windows: gnumake,link,cc,cmd)
2. Windows users only:
Apply patch 2237858 to enable long file names support.
3. Apply the latest AutoConfig Template patch
Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes.
Please refer to document 165195.1 on OracleMetaLink to obtain the latest Autoconfig165195.1 on OracleMetaLink to obtain the latest Autoconfig Template Rollup Patch available in Metalink.
4. Apply the latest Rapid Clone patches
Update the Oracle Applications file system with the latest Rapid Clone files by applying the following patches to all application tier server nodes :
o 3453499 (11i.ADX.F)
o 5225940 (Post ADX.F Fixes)
5. Setup Rapid Clone on the Applications Tier
a. If the source Applications system was created with Rapid Install version 11.5.5 or earlier and has not been migrated to AutoConfig, follow the instructions Migrating to AutoConfig on the Applications Tier Migrating to AutoConfig on the Applications Tier in document 165195.1 on OracleMetaLink).
b. All users must run AutoConfig on the Applications Tier (see section 5: Maintaining System Configuration Maintaining System Configuration in document 165195.1 on OracleMetaLink).
6. Setup Rapid Clone on the Database Tier
Implement AutoConfig in the RDBMS ORACLE_HOME (Follow the instructions in section Migrating to AutoConfig on the Database Tier Migrating to AutoConfig on the Database Tier in document 165195.1 on OracleMetaLink). Follow steps 1 and 4 of Section 7 in the AutoConfig document for all versions of RapidInstall and every time you apply a new version of the Rapid Clone patch.
7. Maintain Snapshot information
Log in to each Application Tier Node as the APPLMGR user and run Maintain Snapshot information in AD Administration.
See Oracle Applications Maintenance Utilities for more information.
________________________________________
Section 2: Clone Oracle Applications 11i
Use Rapid Clone to create template files for cloning on the source system. After the source system is copied to the target, Rapid Clone updates these templates to contain the new target system configuration settings. Rapid Clone will not change the source system configuration.
There are three phases to the cloning process:
1. Prepare the Source System
Execute the following commands to prepare the source system for cloning.
a. Prepare the source system database tier for cloning
Log on to the source system as the ORACLE user and run the following commands:
cd/appsutil/scripts/
perl adpreclone.pl dbTier
b. Prepare the source system application tier for cloning
Log on to the source system as the APPLMGR user and run the following commands on each node that contains an APPL_TOP:
cd/admin/scripts/
perl adpreclone.pl appsTier
2. Copy the Source System to the Target System
Copy the application tier file system from the source Applications system to the target node by executing the following steps in the order listed. Ensure the application tier files copied to the target system are owned by the target APPLMGR user, and that the database tier files are owned by the ORACLE user.
a. Copy the application tier file system
Log on to the source system application tier nodes as the APPLMGR user.
Shut down the application tier server processes
Copy the following application tier directories from the source node to the target application tier node:
/util
/clone
/_pages (when this directory exists)
<806 ORACLE_HOME>
b. Copy the database tier file system
Log on to the source system database node as the ORACLE user.
Perform a normal shutdown of the source system database
Copy the database (DBF) files from the source to the target system
Copy the source database ORACLE_HOME to the target system
Start up the source Applications system database and application tier processes
Note: Unix/Linux users, make sure that the softlinks are preserved when copying.
3. Configure the Target System
Execute the following commands to configure the target system. You will be prompted for the target system specific values (SID, Paths, Ports, etc)
a. Configure the target system database server
Log on to the target system as the ORACLE user and type the following commands to configure and start the database:
cd/appsutil/clone/bin
perl adcfgclone.pl dbTier
b. Configure the target system application tier server nodes
Log on to the target system as the APPLMGR user and type the following commands:
cd/clone/bin
perl adcfgclone.pl appsTier
Attention: Windows user only: add <806 ORACLE_HOME>\bin to the system path before running this step.
________________________________________
Section 3: Finishing Tasks
This section lists tasks that may be necessary depending on your implementation and the intended use of the cloned system.
1. Update profile options
Rapid Clone updates only site level profile options. If any other profile options are set to instance specific values, you must update them manually.
2. Update printer settings
If the new cloned system needs to utilize different printers, update the target system with the new printer settings now.
3. Update workflow configuration settings
Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the target system.
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
4. Verify the APPLCSF variable setting
Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory for concurrent manager log and output files) points to an acceptable directory. To modify it, change the value of s_applcsf in the contextfile and run AutoConfig.
5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
If the target system is in a different domain name than the source system and SESSION_COOKIE_DOMAIN was not null in the source system, update that value to reflect the new domain name.
6. Windows users only reboot the target machine
Once cloning is completed reboot to enable the services.
________________________________________
Section 4: Advanced Cloning Options
This section describes advanced cloning procedures.
1. Refreshing a target system
You may need to refresh the target system periodically to synchronize it with changes from the source.
To refresh the target system, perform the following steps as described in previous sections:
a. Prepare the Source System
b. Copy the Source System to the Target System
o Copy the application tier file system if the APPL_TOP, 806 ORACLE_HOME, or iAS ORACLE_HOME needs to be refreshed. Copy the portion of the application tier file system which has been updated.
o Copy the database tier file system if the RDBMS ORACLE_HOME or the database needs to be refreshed. If refreshing the database, the ORACLE_HOME should be refreshed at the same time.
c. Configure the Target System
Specify the existing target system context file when running adcfgclone.pl commands:
o perl adcfgclone.pl dbTier
where database context file is:
/appsutil/.xml
o perl adcfgclone.pl appsTier
where appltop context file is:
/admin/.xml
d. Finishing Tasks
2. Cloning a single-node system to a multi-node system
This procedure allows the original single-node system to be cloned into a multi-node system. An Applications system comprises five server types:
o Database server (database tier)
o Forms server (application tier)
o Web server (application tier)
o Concurrent Processing server (application tier)
o Administration server (application tier)
During the single-node to multi-node cloning process, each of these servers can be placed on its own node, resulting in a multi-node target system.
f. Perform prerequisites
Perform these steps on all source and target nodes.
g. Clone Oracle Applications 11i
Prepare, copy and configure the cloned Applications System. When creating more than one application tier server node from a single node system, the copy and configure steps must be performed on each target node. You can specify the server type for each target node while answering the prompts during the configuration step.
The database ORACLE_HOME and database only need to be copied to the node on which the database will be run.
h. Finishing Tasks
Note: Another way of changing a single-node system to a multi-node system is to share the APPL_TOP. See document 233428.1 on OracleMetaLink document 233428.1 on OracleMetaLink for details.
3. Cloning a multi-node system to a multi-node system with same number of nodes
A multi-node system can be cloned provided the number of nodes and distribution of servers in the target system matches that of the source system.
To clone a multi-node system to a multi-node system, perform the cloning process on each node. For example, if the source system contains three nodes, perform the cloning process three times.
o Clone source system node 1 to target system node 1.
o Clone source system node 2 to target system node 2.
o Clone source system node 3 to target system node 3.
Attention: The database server node must be cloned first.
4. Adding a new node to an existing system
You can use Rapid Clone to clone a node and add it to the existing Application System. The new node will run the same or a subset of the server types running on the source node. Follow the instructions in the Application Tier part of Clone Oracle Applications 11i:
o Prepare the source system, copy it to the new node and configure it.
o After adcfgclone.pl completes, source the Applications environment and run the following commands on the target system:
o cd/clone/bin
o perl adaddnode.pl
Note: If the SQL*Net Access security is enabled in the existing system (enabled by default from 11i10), you first need to authorize the new node to access the database through SQL*Net. See Managed SQL*Net Access from HostsManaged SQL*Net Access from Hosts in document 281758.1 on OracleMetalink for instructions on how to achieve this from OAM.
5. Reducing the number of nodes of a multi-node system (merge APPL_TOP)
You can use Rapid Clone to clone a multi-node system to a single-node system (or a multi-node system with fewer nodes) by merging the APPL_TOPs filesystem together. Follow the procedure for Merging existing APPL_TOPs in document 233428.1 Merging existing APPL_TOPs in document 233428.1 on OracleMetaLink.
6. Cloning a RAC system
You can use Rapid Clone to clone a RAC system. While cloning, you have the possibility to remove or add nodes to the cluster in the target RAC system. To clone a RAC system, perform the following tasks:
. Verify the prerequisites
o Apply TXK patch 3571388 (AutoConfig support for Oracle RAC instances)
o Migrate the source system cluster ORACLE_HOMES to AutoConfig as documented in document 165195.1 on OracleMetaLinkdocument 165195.1 on OracleMetaLink
a. Prepare the Source System
Choose one of the ORACLE_HOMEs on the source cluster. This ORACLE_HOME will be used as a master to create all the target cluster system ORACLE_HOME. Run "perl adpreclone.pl dbTier" on it.
Note: You also have the option to clone each ORACLE_HOME from the source RAC cluster to the target cluster. In that case, run adpreclone.pl on every ORACLE_HOME.
b. Copy the Source System to the Target System
o Copy the master ORACLE_HOME from the source system to each node that will compose the target cluster. For example, if your source RAC system had 2 nodes, and you want to clone it to a 3 node target RAC system, you should copy the source master ORACLE_HOME to the 3 nodes on the target system.
o Copy the database files from the source to target system.
c. Configure the Target System
o Log on to any ORACLE_HOME in the target cluster and run
adcfgclone.pl dbTier
This step configures the first node of the target system RAC cluster and recreates the database control files. The prompts, however, will gather information about every node in the target RAC cluster and the data will be re-used when configuring each subsequent node in the next step.
o For each remaning RDBMS ORACLE_HOME in the target system, run the following command as the ORACLE file system owner:
adcfgclone.pl dbTier
o If your database is version 10g or higher, run the following commands to register the database and the instance to the cluster manager .
srvctl add database -d -o
srvctl add instance -d \
-i -n
Note: If the cluster manager is not on Linux (ORACM) or the database is version 10g or higher, manually start up the cluster manager on the target system before running adcfgclone.pl
d. Clone the application tier
Follow the steps in section 2 to prepare, copy and configure the application tier. When prompted for the database SID, specify any one of the RAC service names.
Note: To clone from RAC to non-RAC, follow the same above steps but copy the master ORACLE_HOME to one target node only, and answer "No" to the question "Target instance is a Real Application Cluster (RAC) instance (y/n)", when prompted by adcfgclone.pl.
7. Adding a node to an existing RAC Cluster
You can use Rapid Clone to add one or several nodes to an existing RAC Cluster. Perform the following tasks:
. Choose any one of the ORACLE_HOMEs in the existing cluster and run "perl adpreclone.pl dbTier" on it. This ORACLE_HOME will be used as a master to create the additional node(s).
a. Copy the master ORACLE_HOME filesystem to the new node(s).
b. Reconfigure the RAC Cluster to include the new node(s):
o Log on to the new node, or any one of the new nodes if adding more than one, and run the following command:
cd /appsutil/clone/bin
perl adcfgclone.pl dbTier
Note: You will be prompted for information about all the nodes forming the new cluster and asked to perform the next step before completing adcfgclone.pl on this node.
o When instructed so by the previous step, log on to every node from the original cluster and run the following command on each of them:
cd /appsutil/clone/bin
perl adcfgclone.pl addracnode
o Go back to the first node and complete adcfgclone.pl
o If you are adding more than one node to the original cluster, log on to each of the remaining new nodes and run
cd /appsutil/clone/bin
perl adcfgclone.pl dbTier
Note: If the cluster manager is not on Linux (ORACM) or the database is version 10g or higher, manually start up the cluster manager on the target systems before running adcfgclone.pl
8. Cloning a Shared File System
You can use Rapid Clone to clone a shared APPL_TOP system. Since all the nodes share a unique APPL_TOP you only need to fully clone one of the source system nodes to its target machine and add more nodes directly sharing the APPL_TOP on the target system. Choose one of the shared APPL_TOP nodes on source system (the rest of this section will refer to it as Node A) and perform the following tasks:
. Perform prerequisites
Perform these steps on Node A and and every target nodes.
a. Clone Oracle Applications 11i
Perform a full clone (Prepare, copy and configure steps) of the Database Tier and Node A (Application tier).
b. Add the shared file system nodes to the target system
On the target system, follow the instructions for adding a node to a shared APPL_TOP system in document 233428.1adding a node to a shared APPL_TOP system in document 233428.1 on OracleMetalink and add more nodes sharing the target system APPL_TOP to match the source system topology.
________________________________________
Appendix A: Install JRE 1.3.1 into RDBMS ORACLE_HOME
Windows customers will need to perform the following steps:
Download JRE 1.3.1 from Sun Microsystems.
Run the install executable
When prompted for the location to install jre, click browse and enter the location:
\jre\1.3.1
Accept the default installation options.
JRE 1.3.1 will be installed into the\jre\1.3.1 directory.
________________________________________
Appendix B: Recreating database control files manually in Rapid Clone.
This Appendix documents the steps to allow manual creation of the target database control files within the Rapid Clone process. Examples of when to use this method are for databases on raw partitions or hot backup cloning. Replace section 2.3a (Configure the target system database server) with the following steps:
Log on to the target system as the ORACLE user
Configure the
cd/appsutil/clone/bin
perl adcfgclone.pl dbTechStack
Create the target database control files manually
Start the target system database in open mode
Run the library update script against the database
cd/appsutil/install/
sqlplus "/ as sysdba" @adupdlib.sql
where is "sl" for HP-UX, "so" for any other UNIX platform and not required for Windows.
Configure the target database (the database must be open)
cd/appsutil/clone/bin
perl adcfgclone.pl dbconfig
where target context file is:
/appsutil/.xml
Cloning creates an identical copy of an existing Oracle Applications system. There are various reasons for cloning an Oracle Applications system such as:
Creating a copy of the production system for testing updates.
Migrating an existing system to new hardware.
Creating a stage area to reduce patching downtime.
This document describes the process of cloning an Oracle Applications Release 11i system. The most current version of this note is document 230672.1 on OracleMetaLink. A FAQ is also available in document 230672.1 on OracleMetaLink. A FAQ is also available in document 216664.1 on OracleMetaLink.document 216664.1 on OracleMetaLink.
Note: Rapid Clone is currently not supported on Windows Itanium or on Windows x86-64 (AMD64/EM64T).
Attention: Windows users. This document typically uses UNIX syntax when specifying directories; Please substitute the appropriate Windows syntax
Section 1: Prerequisites
Tasks to perform before using Rapid Clone.
Section 2: Clone Oracle Applications 11i
Tasks to prepare, copy, configure, and verify a cloned Applications System.
Section 3: Finishing Tasks
Tasks to complete the cloning process.
Section 4: Advanced Cloning Methods
Tasks for advanced options such as refreshing and multi-node cloning.
Conventions
Convention Meaning
Source system Applications system being cloned.
Target system Applications system being created as a copy of the source.
APPLMGR User which owns the applications file system (APPL_TOP and application tier technology stack)
ORACLE User which owns the database file system (RDBMS ORACLE_HOME and database files).
CONTEXT_NAME The CONTEXT_NAME variable refers to the name of the Applications Context file. For systems installed with Rapid Install 11.5.8 or earlier, this value will typically be set to
Monospace Text Represents command line text. Type this command exactly as shown.
< > Text enclosed in angle brackets represents a variable. Substitute a value for the variable text. Do not type the angle brackets.
________________________________________
Section 1: Prerequisites
Before cloning, prepare the source system by applying patches and running AutoConfig.
1. Verify source and target nodes software versions
In addition to the Oracle Applications software requirements (see Installing Oracle Applications Release 11i Part No. B10638-01), the following software component versions must exist on the source and/or target nodes. The location column indicates the node where the software component must be present.
Software Minimum Version Location Details
Oracle Universal Installer 2.2.0.19 All source system nodes Apply OUI22 patch 5035661 on every iAS and RDBMS ORACLE_HOME to be cloned. Do not apply the patch to your RDBMS ORACLE_HOME, if you have Oracle 10g or higher installed.
Perl 5.005 Source and target database nodes Use the Perl shipped with iAS1022 and RDBMS 9i if available or download it from Perl.com. Perl must be in the PATH before cloning. Windows users: do not use Perl from MKSToolKit.
JRE 1.1.8 Source database node If the RDBMS ORACLE_HOME was not installed using Rapid Install, install JRE 1.1.8 into the
JRE 1.3.1 Source database node Windows users only: install JRE 1.3.1 into the
JDK 1.3.1 Target middle-tier applications nodes Refer to Upgrading to JDK 1.3 with Oracle Applications 11i on OracleMetaLink for instructions.
Zip 2.3 All source nodes Download from InfoZip. Zip must be in your PATH for cloning.
OS utilities N/A All target nodes OS utilities (see 11i Install Manual) must be in the the PATH when running adcfgclone.pl (Unix: make,ld,cc,ar - Windows: gnumake,link,cc,cmd)
2. Windows users only:
Apply patch 2237858 to enable long file names support.
3. Apply the latest AutoConfig Template patch
Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes.
Please refer to document 165195.1 on OracleMetaLink to obtain the latest Autoconfig165195.1 on OracleMetaLink to obtain the latest Autoconfig Template Rollup Patch available in Metalink.
4. Apply the latest Rapid Clone patches
Update the Oracle Applications file system with the latest Rapid Clone files by applying the following patches to all application tier server nodes :
o 3453499 (11i.ADX.F)
o 5225940 (Post ADX.F Fixes)
5. Setup Rapid Clone on the Applications Tier
a. If the source Applications system was created with Rapid Install version 11.5.5 or earlier and has not been migrated to AutoConfig, follow the instructions Migrating to AutoConfig on the Applications Tier Migrating to AutoConfig on the Applications Tier in document 165195.1 on OracleMetaLink).
b. All users must run AutoConfig on the Applications Tier (see section 5: Maintaining System Configuration Maintaining System Configuration in document 165195.1 on OracleMetaLink).
6. Setup Rapid Clone on the Database Tier
Implement AutoConfig in the RDBMS ORACLE_HOME (Follow the instructions in section Migrating to AutoConfig on the Database Tier Migrating to AutoConfig on the Database Tier in document 165195.1 on OracleMetaLink). Follow steps 1 and 4 of Section 7 in the AutoConfig document for all versions of RapidInstall and every time you apply a new version of the Rapid Clone patch.
7. Maintain Snapshot information
Log in to each Application Tier Node as the APPLMGR user and run Maintain Snapshot information in AD Administration.
See Oracle Applications Maintenance Utilities for more information.
________________________________________
Section 2: Clone Oracle Applications 11i
Use Rapid Clone to create template files for cloning on the source system. After the source system is copied to the target, Rapid Clone updates these templates to contain the new target system configuration settings. Rapid Clone will not change the source system configuration.
There are three phases to the cloning process:
1. Prepare the Source System
Execute the following commands to prepare the source system for cloning.
a. Prepare the source system database tier for cloning
Log on to the source system as the ORACLE user and run the following commands:
cd
perl adpreclone.pl dbTier
b. Prepare the source system application tier for cloning
Log on to the source system as the APPLMGR user and run the following commands on each node that contains an APPL_TOP:
cd
perl adpreclone.pl appsTier
2. Copy the Source System to the Target System
Copy the application tier file system from the source Applications system to the target node by executing the following steps in the order listed. Ensure the application tier files copied to the target system are owned by the target APPLMGR user, and that the database tier files are owned by the ORACLE user.
a. Copy the application tier file system
Log on to the source system application tier nodes as the APPLMGR user.
Shut down the application tier server processes
Copy the following application tier directories from the source node to the target application tier node:
<806 ORACLE_HOME>
b. Copy the database tier file system
Log on to the source system database node as the ORACLE user.
Perform a normal shutdown of the source system database
Copy the database (DBF) files from the source to the target system
Copy the source database ORACLE_HOME to the target system
Start up the source Applications system database and application tier processes
Note: Unix/Linux users, make sure that the softlinks are preserved when copying.
3. Configure the Target System
Execute the following commands to configure the target system. You will be prompted for the target system specific values (SID, Paths, Ports, etc)
a. Configure the target system database server
Log on to the target system as the ORACLE user and type the following commands to configure and start the database:
cd
perl adcfgclone.pl dbTier
b. Configure the target system application tier server nodes
Log on to the target system as the APPLMGR user and type the following commands:
cd
perl adcfgclone.pl appsTier
Attention: Windows user only: add <806 ORACLE_HOME>\bin to the system path before running this step.
________________________________________
Section 3: Finishing Tasks
This section lists tasks that may be necessary depending on your implementation and the intended use of the cloned system.
1. Update profile options
Rapid Clone updates only site level profile options. If any other profile options are set to instance specific values, you must update them manually.
2. Update printer settings
If the new cloned system needs to utilize different printers, update the target system with the new printer settings now.
3. Update workflow configuration settings
Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the target system.
Table Name Column Name Column Value Details
WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE Value starts with http://
WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE Value starts with "http://
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
4. Verify the APPLCSF variable setting
Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory for concurrent manager log and output files) points to an acceptable directory. To modify it, change the value of s_applcsf in the contextfile and run AutoConfig.
5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
If the target system is in a different domain name than the source system and SESSION_COOKIE_DOMAIN was not null in the source system, update that value to reflect the new domain name.
6. Windows users only reboot the target machine
Once cloning is completed reboot to enable the services.
________________________________________
Section 4: Advanced Cloning Options
This section describes advanced cloning procedures.
1. Refreshing a target system
You may need to refresh the target system periodically to synchronize it with changes from the source.
To refresh the target system, perform the following steps as described in previous sections:
a. Prepare the Source System
b. Copy the Source System to the Target System
o Copy the application tier file system if the APPL_TOP, 806 ORACLE_HOME, or iAS ORACLE_HOME needs to be refreshed. Copy the portion of the application tier file system which has been updated.
o Copy the database tier file system if the RDBMS ORACLE_HOME or the database needs to be refreshed. If refreshing the database, the ORACLE_HOME should be refreshed at the same time.
c. Configure the Target System
Specify the existing target system context file when running adcfgclone.pl commands:
o perl adcfgclone.pl dbTier
where database context file is:
o perl adcfgclone.pl appsTier
where appltop context file is:
d. Finishing Tasks
2. Cloning a single-node system to a multi-node system
This procedure allows the original single-node system to be cloned into a multi-node system. An Applications system comprises five server types:
o Database server (database tier)
o Forms server (application tier)
o Web server (application tier)
o Concurrent Processing server (application tier)
o Administration server (application tier)
During the single-node to multi-node cloning process, each of these servers can be placed on its own node, resulting in a multi-node target system.
f. Perform prerequisites
Perform these steps on all source and target nodes.
g. Clone Oracle Applications 11i
Prepare, copy and configure the cloned Applications System. When creating more than one application tier server node from a single node system, the copy and configure steps must be performed on each target node. You can specify the server type for each target node while answering the prompts during the configuration step.
The database ORACLE_HOME and database only need to be copied to the node on which the database will be run.
h. Finishing Tasks
Note: Another way of changing a single-node system to a multi-node system is to share the APPL_TOP. See document 233428.1 on OracleMetaLink document 233428.1 on OracleMetaLink for details.
3. Cloning a multi-node system to a multi-node system with same number of nodes
A multi-node system can be cloned provided the number of nodes and distribution of servers in the target system matches that of the source system.
To clone a multi-node system to a multi-node system, perform the cloning process on each node. For example, if the source system contains three nodes, perform the cloning process three times.
o Clone source system node 1 to target system node 1.
o Clone source system node 2 to target system node 2.
o Clone source system node 3 to target system node 3.
Attention: The database server node must be cloned first.
4. Adding a new node to an existing system
You can use Rapid Clone to clone a node and add it to the existing Application System. The new node will run the same or a subset of the server types running on the source node. Follow the instructions in the Application Tier part of Clone Oracle Applications 11i:
o Prepare the source system, copy it to the new node and configure it.
o After adcfgclone.pl completes, source the Applications environment and run the following commands on the target system:
o cd
o perl adaddnode.pl
Note: If the SQL*Net Access security is enabled in the existing system (enabled by default from 11i10), you first need to authorize the new node to access the database through SQL*Net. See Managed SQL*Net Access from HostsManaged SQL*Net Access from Hosts in document 281758.1 on OracleMetalink for instructions on how to achieve this from OAM.
5. Reducing the number of nodes of a multi-node system (merge APPL_TOP)
You can use Rapid Clone to clone a multi-node system to a single-node system (or a multi-node system with fewer nodes) by merging the APPL_TOPs filesystem together. Follow the procedure for Merging existing APPL_TOPs in document 233428.1 Merging existing APPL_TOPs in document 233428.1 on OracleMetaLink.
6. Cloning a RAC system
You can use Rapid Clone to clone a RAC system. While cloning, you have the possibility to remove or add nodes to the cluster in the target RAC system. To clone a RAC system, perform the following tasks:
. Verify the prerequisites
o Apply TXK patch 3571388 (AutoConfig support for Oracle RAC instances)
o Migrate the source system cluster ORACLE_HOMES to AutoConfig as documented in document 165195.1 on OracleMetaLinkdocument 165195.1 on OracleMetaLink
a. Prepare the Source System
Choose one of the ORACLE_HOMEs on the source cluster. This ORACLE_HOME will be used as a master to create all the target cluster system ORACLE_HOME. Run "perl adpreclone.pl dbTier" on it.
Note: You also have the option to clone each ORACLE_HOME from the source RAC cluster to the target cluster. In that case, run adpreclone.pl on every ORACLE_HOME.
b. Copy the Source System to the Target System
o Copy the master ORACLE_HOME from the source system to each node that will compose the target cluster. For example, if your source RAC system had 2 nodes, and you want to clone it to a 3 node target RAC system, you should copy the source master ORACLE_HOME to the 3 nodes on the target system.
o Copy the database files from the source to target system.
c. Configure the Target System
o Log on to any ORACLE_HOME in the target cluster and run
adcfgclone.pl dbTier
This step configures the first node of the target system RAC cluster and recreates the database control files. The prompts, however, will gather information about every node in the target RAC cluster and the data will be re-used when configuring each subsequent node in the next step.
o For each remaning RDBMS ORACLE_HOME in the target system, run the following command as the ORACLE file system owner:
adcfgclone.pl dbTier
o If your database is version 10g or higher, run the following commands to register the database and the instance to the cluster manager .
srvctl add database -d
srvctl add instance -d
-i
Note: If the cluster manager is not on Linux (ORACM) or the database is version 10g or higher, manually start up the cluster manager on the target system before running adcfgclone.pl
d. Clone the application tier
Follow the steps in section 2 to prepare, copy and configure the application tier. When prompted for the database SID, specify any one of the RAC service names.
Note: To clone from RAC to non-RAC, follow the same above steps but copy the master ORACLE_HOME to one target node only, and answer "No" to the question "Target instance is a Real Application Cluster (RAC) instance (y/n)", when prompted by adcfgclone.pl.
7. Adding a node to an existing RAC Cluster
You can use Rapid Clone to add one or several nodes to an existing RAC Cluster. Perform the following tasks:
. Choose any one of the ORACLE_HOMEs in the existing cluster and run "perl adpreclone.pl dbTier" on it. This ORACLE_HOME will be used as a master to create the additional node(s).
a. Copy the master ORACLE_HOME filesystem to the new node(s).
b. Reconfigure the RAC Cluster to include the new node(s):
o Log on to the new node, or any one of the new nodes if adding more than one, and run the following command:
cd /appsutil/clone/bin
perl adcfgclone.pl dbTier
Note: You will be prompted for information about all the nodes forming the new cluster and asked to perform the next step before completing adcfgclone.pl on this node.
o When instructed so by the previous step, log on to every node from the original cluster and run the following command on each of them:
cd /appsutil/clone/bin
perl adcfgclone.pl addracnode
o Go back to the first node and complete adcfgclone.pl
o If you are adding more than one node to the original cluster, log on to each of the remaining new nodes and run
cd /appsutil/clone/bin
perl adcfgclone.pl dbTier
Note: If the cluster manager is not on Linux (ORACM) or the database is version 10g or higher, manually start up the cluster manager on the target systems before running adcfgclone.pl
8. Cloning a Shared File System
You can use Rapid Clone to clone a shared APPL_TOP system. Since all the nodes share a unique APPL_TOP you only need to fully clone one of the source system nodes to its target machine and add more nodes directly sharing the APPL_TOP on the target system. Choose one of the shared APPL_TOP nodes on source system (the rest of this section will refer to it as Node A) and perform the following tasks:
. Perform prerequisites
Perform these steps on Node A and and every target nodes.
a. Clone Oracle Applications 11i
Perform a full clone (Prepare, copy and configure steps) of the Database Tier and Node A (Application tier).
b. Add the shared file system nodes to the target system
On the target system, follow the instructions for adding a node to a shared APPL_TOP system in document 233428.1adding a node to a shared APPL_TOP system in document 233428.1 on OracleMetalink and add more nodes sharing the target system APPL_TOP to match the source system topology.
________________________________________
Appendix A: Install JRE 1.3.1 into RDBMS ORACLE_HOME
Windows customers will need to perform the following steps:
Download JRE 1.3.1 from Sun Microsystems.
Run the install executable
When prompted for the location to install jre, click browse and enter the location:
Accept the default installation options.
JRE 1.3.1 will be installed into the
________________________________________
Appendix B: Recreating database control files manually in Rapid Clone.
This Appendix documents the steps to allow manual creation of the target database control files within the Rapid Clone process. Examples of when to use this method are for databases on raw partitions or hot backup cloning. Replace section 2.3a (Configure the target system database server) with the following steps:
Log on to the target system as the ORACLE user
Configure the
cd
perl adcfgclone.pl dbTechStack
Create the target database control files manually
Start the target system database in open mode
Run the library update script against the database
cd
sqlplus "/ as sysdba" @adupdlib.sql
where
Configure the target database (the database must be open)
cd
perl adcfgclone.pl dbconfig
where target context file is:
Subscribe to:
Posts (Atom)
