cloning/copying an old r11 environment to another server (Windows)

Hi all
We are runing 11.0.3 (multi-level) under windows.

DB, simultaneous Manager, the report server on a server
Forms Apache Server, WEB, on another node.

We are facing some curruption of disc and a few hardware problems. So I need to clone my system to the other server.
Can someone help me to clone R11 to another server on the windows machine.

concerning
Musaddaq

Here's 11.0.3 cloning process
=====================

Helios, he seeks 11.0.3 version cloning, correct me if I'm wrong any of the steps, I use the same procedure for one of our 11.0.3 instance EBS.

I am pasting the note here, then you can try to clone:

There is an internal memo to make a clone on the 11.0.x, release but it is not supported. Please make sure that you have a good backup.

==============================================================================================================================================================
===================
Note 91985.1 Step by step on cloning the ORACLE_HOME (including DB) and APPL_TOP:
=================================================================================
Cloning an instance of Oracle Application version 11 on a separate UNIX Machine
==============================================================================

Goal
---------

Provide a method of cloning an Oracle Applications version 11 APPL_TOP,.
an ORACLE_HOME 8.0.X and database files included.

Scope of Application &
-------------------

It takes a high level of experience with Applications for this document.

Related documents
-----------------

Oracle Applications version 11 for UNIX manual of Installation (part No. A57983-02)

Assumptions
-----------

You have already installed Oracle Applications version 11 and a 8.0.X
ORACLE_HOME/database and all works fine.

If you clone the APPL_TOP and ORACLE_HOME of quite another
UNIX box, you must make sure that the target operating system is the
same and is patched up to the same level as the source area, you are
cloning of.

Measures for Clone
--------------

1. on the target area, create a user and the user who owns the APPL_TOP who
has the ORACLE_HOME files and database files (will be applmgr and)
Oracle, respectively for the purposes of this document). Create an environment
file for each of these users by specifying environment variables
referenced in the Oracle version 11 for the Installation of UNIX Applications
Manual.

Example of variables for the oracle user:

LD_LIBRARY_PATH
ORACLE_HOME
ORACLE_SID
TWO_TASK (if applicable)
PATH
TERM
JRE_DIR

Example of variables for user applmgr:

APPL_TOP
LD_LIBRARY_PATH
NLS_DATE_FORMAT
NLS_LANG
NLS_NUMERIC_CHARACTERS
ORACLE_HOME
PATH
ORACLE_SID
TWO_TASK (if applicable)
TERM

Note: Many of the following steps are since the white paper of the bridges D.
'Copy of a database'. A copy of this is located at the end of this document.

2 plug the sources such as the oracle user machine and the newspaper is
svrmgrl or SQL * more as SYSDBA and SYSOPER DBA role he conceded.
Run the following command:

SQL > ALTER DATABASE BACKUP CONTROLFILE TO TRACE;

The trace will be found at the the USER_DUMP_DEST value which is
defined in the init.ora file. (An example of this trace file is located
d. bridges of paper at the end of this article.)

3. make a list of all data files and redo log files:

SQL > SELECT file_name FROM dba_data_files;
SQL > SELECT Member FROM v$ logfile;

4. stop your database cleanly. Run each to do the following:

SQL > shutdown normal;
SQL > shutdown immediate;
SQL > shutdown transactional;

5 A this point, anything that creates a process of operating system must
be lowered neatly on the Source area. Examples are: Forms Server
Process, process of Web server, concurrent managers and the database listener.

6. make zip files of all APPL_TOP, ORACLE_HOME files and database files
files (datafiles and redo logs) on the Source area.

7 FTP files zipped above the target area. Also ftp on the trace file
that was created in step 2 above, you will be using it again in step 8.

8. unzip all the files in the new $APPL_TOP, $ORACLE_HOME locations.

You are now finished with the source area. Every process can safely be made
Save this box. The rest of the book refers to the target area.

9. changing theinit .ora file on the target area (usually located in the)
Directory$ ORACLE_HOME/dbs) to reflect the structure of your new directory.
(D. bridges paper below gives examples of what should generally be)
changed in the environment).

10 change the track of file that you created in step 2 to take account of your new directory
structure.

11 start server manager (svrmgrl) and run the trace of the file against your
database.

Example: svrmgrl (internal connect)
Svrmgrl > @tracefile.trc

12 edit listener.ora and tnsnames.ora files to reflect your new
environment. These files must be in the $ORACLE_HOME/network/admin
Directory.

13 put in place the process of listening and trying to connect to SQL * more to test
connectivity to the database. Make sure the applmgr and oracle
environment of the users can connect to SQL * more.

14 create a link to the technology stack in the ORACLE_HOME. Example of elements to
be related:

CD $ORACLE_HOME/procbuilder/lib; f ins_procbuilderv8.mk install
CD $ORACLE_HOME/browser20/lib; f ins_browser20v8.mk install
CD $ORACLE_HOME/forms45/lib; f ins_forms45wv88.mk install
CD $ORACLE_HOME/rdbms/lib; f ins_rdbms.mk install

15. There are several configuration files that need to be changed so that
the Web server in order to work on the new box. The recommended method for
change the host name in the configuration files is to uninstall, then
Reinstall the Web server using the oracle Installer.

16. Enter the area of the target as the applmgr and run adadmin. Choose from the
Option "reissue Applications programs. If you have changed the directory
structure for your APPL_TOP on the target from the Source area, you
will also have to choose recreate your environment file.

This is a good place to open a SQL * Plus the term and log in as the APPS
user. Once you connect to SQL * more run the following query as a system of
Search for invalid objects in the database:

SQL > select owner, object_type, object_name in dba_objects
When status = 'INVALID';

If all objects are returned that belong to the user apps need to recompile the
APPS schema in adadmin.

17 follow chapter 4 of the manual version 11 install and configure the
webserver.

18 start concurrent managers. The name of the node in the-> simultaneous
Manager-> administer form should take the new machine dynamically
target name of the area.

If the competitor-> Manager-> form to administer the node name is
No poster, at the prompt, type UNIX:

uname - a (this will return the machine think his name)

The UNIX administrator at this stage you will need to reconfigure
the target area to register the correct node for this box.

19. you must now change the profile options that could have been
affected by cloning. Examples: RRA:URL, WEB_AGENT, and
HELP_SYSTEM_BASE_URL.

20 start your forms and Server Web server process after sourcing (running)
your new file of environment under the directory $APPL_TOP.

21 change the static html page or set up your dynamic cartridge and
to connect to your applications on the target area.

Copy of a database
==================
By Dave Bridges

Move a database from one location to another is conceptually very simple.
However, you must be extremely careful or the migration fails. There are
two basic ways - a logical and a physical examination - to move a database.

The logical method is to create a new empty database in the new location
(target database), perform a complete export of the original database (source
(database), and then import the source database in the target database.
This article assumes that you have decided not to use this approach. For more information
on export and import, please see the Oracle Server Utilities
Guide for your particular server.

The physical approach involves the cloning of the source database. This method is
very similar to a backup of the database offline. The steps are:

1 back up the source database control file in a trace file.
2. a list of all your data and redo log files.
3. perform a "clean" source database shutdown.
4. copy all the files of database redo log files, file init.ora and trace file
(from step 1) the location of the source to the target location.
5. change the file init.ora target and the trace file.
6. start the target instance.
7. re-create the control file, retrieve and open the database.

Each of these steps is explained in the following instructions.

Note: The following instructions assume (1) you already have the server
installed in the location of the target, (2) all parameters are already set
environmental target and (3) If you use NT, you must
already created and started the services necessary for the target
database.

1 back up the source database control file in a trace file. To connect to
the source via open or SQL database * more using an account that has the
SYSDBA and SYSOPER DBA role he conceded. Run the following command:

SQL > ALTER DATABASE BACKUP CONTROLFILE TO TRACE;

This will create a text file that we will use later. This file will be
written in the subdirectory named by the value of the USER_DUMP_DEST
parameter.

2. a list of all data files and redo log files. It is absolutely
essential to know about the names and locations of all the files of data and redo
the log files. To do this, run the following queries:

SQL > SELECT file_name FROM dba_data_files;

SQL > SELECT Member FROM v$ logfile;

The first query will give the path and name for each of your
data files. The second query will give the same information to redo all the
the log files. Be sure to save this information for future reference.

3. perform a "clean" source database shutdown. A clean shutdown is
are necessary to ensure that all data files and control files
synchronized with the latest transactions. What follows
commands give you a clean shutdown:

normal stop;
stop immediately;
Shutdown transactional;

Note: The shutdown transactional is not available in Oracle7.

4. copy all the files of database redo logs trace and the init.ora file
target file to the location of the source to the location. With the help of the
information collected in step 2, copy all the data source and redo log files
files to the target location. Also copy the file init.ora and the
trace file generated in step 1 to the location target.

5. change the target init.ora file, and the trace file. Using a text editor
revise the init.ora file to reflect the new values for the target
database. It will be change the paths indicated in the settings
as CONTROL_FILES USER_DUMP_DEST, BACKGROUND_DUMP_DEST and all
another parameter that specifies a path/file location (see annex 1
below). Similarly, we must change the trace file. This file contains
the CREATE CONTROLFILE command we will use in step 7. You
will have to change the paths for all data files and redo log files
to reflect their new location (see attachment 2 below).

6. start the target instance. Once the init.ora file is changed, you can
Start the instance. However, since we do not have control files.
You must use the following command:

startup nomount;

7. re-create the control file. Once the instance is started, you can create
your control files. If you saved your file of track under mytrace.trc, you can
now create the command files by running this file as follows:

@mytrace.trc

This script will create the control files, perform a database recovery
to resynchronize the control file with the rest of the database, and
Open the database.

Now, your target database must be open and consistent. There may always be
some remaining tasks you need to perform, such as the creation of a password for the new file
database or create/update a listener on the node target. These tasks are
beyond the scope of this discussion.

Attachment 1. Example of init.ora file
-----------------------------------

Here is an example of the init.ora file.

Are entries that need to be changed to reflect the location of the target file
identified by a '<-- edit="" this'="">

init.ora

AQ_TM_PROCESSES = 1
background_dump_dest = G:\orant\rdbms80\trace<-- edit="">
compatible = 8.0.5.0.0
control_files = ("G:\orant\database\ctl1home.ora",<-- edit="">
"G:\orant\database\ctl2home.ora")<-- edit="">
db_block_buffers = 200
DB_BLOCK_SIZE = 2048
db_file_multiblock_read_count = 8
DB_FILES = 1020
db_name = home
dml_locks = 100
log_buffer = 8192
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
max_dump_file_size = 10240
process = 50
Remote_login_passwordfile = exclusive lock
SEQUENCE_CACHE_ENTRIES = 10
sequence_cache_hash_buckets = 10
shared_pool_size = 6500000
sort_area_size = 65536
user_dump_dest = G:\orant\rdbms80\trace<-- edit="">

Attachment 2. Example of trace file
--------------------------------

Here is a sample of the output of the command alter database backup
controlfile to trace.

Are entries that need to be changed to reflect the location of the target file
identified by a '<-- edit="" this'="" entry.="" edit="" this'="">

Clone.TRC

1999.10.08.10.49.07.171
# The following commands will create a new control file and use
# to open the database.
# Data used by the Recovery Manager will be lost. Additional logs may
# be required for the media recovery of offline data files. Use this
# only if the current version of all newspapers online is available.
STARTUP NOMOUNT
CREATE NORESETLOGS NOARCHIVELOG CONTROLFILE REUSE DATABASE "HOME".
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 1
MAXLOGHISTORY 112
LOGFILE
GROUP 1 ' G:\ORANT\DATABASE\LOGHOME1. ORA' SIZE 1 M.<-- edit="">
GROUP 2 ' G:\ORANT\DATABASE\LOGHOME2. ORA' SIZE 1 M<-- edit="">
DATA FILE
' G:\ORANT\DATABASE\HOMESYS. DBF',.<-- edit="">
' G:\ORANT\DATABASE\HOMERBS. DBF',.<-- edit="">
' G:\ORANT\DATABASE\HOMEUSER. DBF',.<-- edit="">
' G:\ORANT\DATABASE\HOMETEMP. DBF',.<-- edit="">
' G:\ORANT\DATABASE\HOMEINDX. DBF'<-- edit="">
;
# Recovery is required if any of the data files are restored backups.
# or if the last stop was not normal or immediate.
RECOVER THE DATABASE
# Database can now be opened normally.
ALTER DATABASE OPEN;
================================= ================================================================================
================================================================

If you need assistance with the cloning of your instance, you will need to contact Oracle Con
relativeme.

Edited by: 3Amigos December 13, 2010 01:39

Tags: Oracle Applications

cloning/copying an old r11 environment to another server (Windows)

Similar Questions

Set up Mail

This has happened

Maybe you are looking for