Cloning of a database to another server.

Similar Questions

• The creation of Oracle 11 g DSN for database on another server

  Hello

  How to create a database of Oracle 11 g DSN for a database that is lying on another server? I tried to use the Microsoft ODBC Administrator tool, but it gives me options only for databases on my own machine.

  Hello

  Check this thread can help you https://forums.oracle.com/thread/2479208

• Is this possible in double database on another server without losing any data on the auxiliary database?

  Hi guys.

  I have following scenario

  -i have a backup game compressed a database in NOARCHIVELOG mode.

  -i want a database that has been duplicated on a server different but

  without losing the data on the auxiliary database.

  -the two server contains the same version of oracle 11g.

  -two servers UNIX/Linux then

  s ' please reply to more info.

  DB version: 11.2.0.1

  Name of the comic book source: has

  Name of the comic in double: diferent Pentecost B file structure.

  
  

  
  

  Can someone help me please?

  The target and duplicate database cannot have the same ID duplicate so is not what you need. If you have FOO database on a server and want to copy to FOO on server B, with a different file structure, then simply copy the RMAN backupsets to Server B, and restore the database by renaming the data files. There are many examples on the web.

• The fastest way to move a database to another server even.

  Hello gurus,
  Normally, I have worked with exp/imp, but now our database is too large to move this way takes about 24 hours for export and import. We bought new hardware and I need to go the new material on the production database. Operating system is the same Red Hat Enterprise rel 5.6 Linux 64 bit, oracle is the same 10.2.0.40 same block and character size, 64-bit, only difference, is that the new hardware has space more physical and better memory. Is there an easy way to move the data by copying on the control files and data files to a new server? I have not tried, data pump or transportable tablespaces, and I have limited time - so this request. I need to find the solution the faster your advice, so I can learn quickly how to implement your recemendation.
  My export .dmp database size is 34GB.
  Any advice would be great!

  No need to run a database create new host - already built sound at the source. Make a software 'only' install and get the ORACLE_HOME corrected and updated, you'll clone basically just the database to the new instance.

  As long as the source database is in archivelog mode, you can put the database in backup mode, copy the files of data, complete backup to the source mode and make a log switch.

  Here's a detail how at: http://www.dba-oracle.com/oracle_tips_db_copy.htm

  Instead of step to RECOVER the DATABASE, we use ' database to RECOVER up to TIME AAAA-MM-JJ HH24:MI:SS to the AID of BACKUP CONTROLFILE; "and the value until the time a second or two beyond the"... save end;' timestamp to the source instance. "

  You will need this archivelog, maybe encourage the file generated after the ends of the mode of backup and recovery for ARC files more a couple, depending on the activity of update to the source. If using a spfile, originally executed 'create a spfile pfile=/.../initSID.ora;' scp this file to the new host, adjust as required.

  Maybe you'll want to change DB_NAME, then the '... The DATABASE VALUE... "part of the controlfile create is necessary. Updated the SERVICE_NAME and if using LOCAL_LISTENER adjust the host = properly.

  If the directory paths are all the same, it is even easier. And if the are not, path names can be corrected in the script of create controlfile.

• Need to change the database to another server

  Hello
  
  We purchased a new server and want to move our database to the new. I intend to do following things:
  
  (1) stop the database and backup to take.
  
  (2) create a new database on the new server with the same structure of directory and same name.
  
  (3) copy all the files to the new server (file initorcl.ora, password, data files, control files).
  
  (4) give old IP of the server to the new server.
  
  (5) make the necessary changes to Tnsnames.ora, listener.ora.
  
  (6) start the database.
  
  
  Please advice if I am out of the important steps.
  
  Thank you

  Step 2 is not necessary and can be confusing because it creates data files that you don't want! (you want the data files to from the "old" Server).
  However, if the platform is Windows, you will need to create the Windows Service to start the database instance.

  Hemant K Collette

• Cloning of a database

  Hello
  
  I have a backup of a database in a tar ball.
  I need to create a clone of the database on another server.
  
  The old database was in a position to say: / usr/test01 on another server
  And I extracted the contents of the tar ball on the location/usr/test02
  and changed the initvtls.ora to change the path of the controlfile
  
  I also added the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to change the path of the data file.
  
  When I try to start the database, I get the following error:
  
  
  ORACLE instance started.
  
  Total System Global Area 1073741824 bytes
  Bytes of size 1264968 fixed
  700449464 variable size bytes
  369098752 of database buffers bytes
  Redo buffers 2928640 bytes
  Mounted database.
  ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
  ORA-01110: data file 1: ' / usr/test01/system/sys_01.dbf'
  
  Need help on the error.
  
  Thank you
  Aparna

  Hello

  I also have added DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to change paths of the datafile.
  
  When I try to startup the database, I get the following error -
  
  ORACLE instance started.
  
  Total System Global Area 1073741824 bytes
  Fixed Size 1264968 bytes
  Variable Size 700449464 bytes
  Database Buffers 369098752 bytes
  Redo Buffers 2928640 bytes
  Database mounted.
  ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
  ORA-01110: data file 1: '/usr/test01/system/sys_01.dbf'
  

  Hello

  DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT should serve as a standby database.
  If you want to clone the database that you did. You should be
  (1) create a new control file (with noresetlogs) in the editing phase with the new path of all data files and the redologs (favorite).
  (2) or change the names of the files in data/redologs, using alter tablespace rename datafile

  Concerning
  Anurag Tibrewal.

• 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

• vFoglight - moving the database to another SQL Server

  Hello

  We are moving our vFoglight to a SQL Server database to another SQL (production version) server.  I changed the server/instance name in the foglight.config file to point to the new server and instance and restarted the service (and eventually rebooted as well).  However, vFoglight no longer works.  Is there another step necessary to make it work?

  Any help would be appreciated.

  See you soon,.

  Mark

  Hello Mark,

  We have to examine FMS log and SQL server log to see what error is to jump, but as a quick check you can check that the server authentication is set to SQL Server and Windows authentication mode in the security settings of your instance of SQL Server.

  Concerning

• Oracle9i database from one server to another server.

  I am an Oracle Pl/SQL Developer. We will migrate the database to Oracle9i from one server to another server (both are unix solaris). What are all the meterics we must ensure the Migration succeeded.

  rp0428 wrote:

  user12223156 wrote:

  OK, what about triggers, sequences, synonyms and links from DB? This will affect anything?

  If you stop the database cleanly and then copy all THE files to a new installation of the same version of Oracle on another machine using the same folder structure (a COLD backup) it can not miss anything.

  Re-reading the initial recognition, seeing that they do NOT change the versions of Oracle and do NOT change their operating system, it would seem that a cold backup and a restore would be the preferred method.  Very probably fewer service interruptions and a guaranteed relentless, nothing will 'disappear' from the database...

• the database error duplicate from one server to another server

  Hello
  
  I'm practicing duplicate database to a single database server to another server. Path material and pilot on 2 machines is the same. Here are my steps:
  -Clone site:
  1 change the listener.ora with content:
  LISTENER =
  (DESCRIPTION_LIST =
  (DESCRIPTION =
  (ADDRESS = (PROTOCOL = CIP)(KEY = EXTPROC1521))
  (ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain) (PORT = 1521))
  )
  )
  
  ADR_BASE_LISTENER = / u01/app/oracle
  SID_LIST_LISTENER =
  (SID_LIST =
  (SID_DESC =
  (GLOBAL_DBNAME = orcl)
  (ORACLE_HOME = u01/app/oracle/product/11.2.0/db_1)
  (SID_NAME = orcl)
  )
  )
  ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER = WE
  2. stop and start receiving once again, show message as:
  Service "orcl" has 1 instance (s).
  Instance "orcl", status UNKNOWN, has 1 operation for this service...
  
  The command completed successfully
  3. create pfile from spfile file.
  4. stop and startup nomount with pfile is new pfile create in step 3.
  --------------------------------------- Source site
  1 edit tnsnames.ora with content like:
  VVCOREDB =
  (DESCRIPTION =
  (ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain) (PORT = 1521))
  (CONNECT_DATA =
  (SERVER = DEDICATED)
  (SERVICE_NAME = vvcoredb)
  )
  )
  
  ORCL =
  (DESCRIPTION =
  (ADDRESS = (PROTOCOL = TCP) (HOST = 10.254.1.235) (PORT = 1521))
  (CONNECT_DATA =
  (SERVER = DEDICATED)
  (SERVICE_NAME = orcl)
  )
  )
  2 run the command of rman like these:
  RMAN > Connect target sys@vvcoredb
  RMAN > target password database:
  RMAN > Connect auxiliary sys@orcl
  RMAN > database auxiliary password:
  RMAN > DUPLICATE TARGET DATABASE for database orcl active spfile nofilenamecheck.
  
  Then the result show below:
  From Db double to 24-SEP-12
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_AUX_DISK_1
  channel ORA_AUX_DISK_1: SID = 63 type device = DISK
  
  content of Script memory:
  {
  backup that copy reuse
  TargetFile ' / u01/app/oracle/product/11.2.0/db_1/dbs/spfilevvcoredb.ora' auxiliary format
  ' / u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora';
  clone of SQL 'alter system set spfile = "/u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora";
  }
  execution of Script memory
  
  Backup to starting 24-SEP-12
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 74 type device = DISK
  Backup finished 24-SEP-12
  
  SQL statement: alter system set spfile = "/u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora"
  
  content of Script memory:
  {
  clone of SQL 'alter system set = db_name
  "ORCL" comment =
  "reproduce" scope = spfile;
  clone to stop immediately;
  startup nomount clone;
  }
  execution of Script memory
  
  SQL statement: alter system db_name set = comment "ORCL" = "duplicate" scope = spfile
  
  Instance Oracle to close
  
  connected to the auxiliary database (not started)
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Db in dual at 24/09/2012 17:44:12
  RMAN-03015: an error has occurred in the script stored memory Script
  RMAN-04014: failed to start: ORA-01261: parameter db_recovery_file_dest destination string cannot be translated
  ORA-01262: Stat failed on a destination of the file directory
  Linux-x86_64 error: 2: no such file or directory
  
  I don't know what wrong with my pfile file? I said to correct my pfile site clone like this:
  ORCL.__db_cache_size = 1476395008
  ORCL.__java_pool_size = 16777216
  ORCL.__large_pool_size = 16777216
  ORCL.__oracle_base='/U01/app/oracle'#ORACLE_BASE the value of the environment
  ORCL.__pga_aggregate_target = 1342177280
  ORCL.__sga_target = 1979711488
  ORCL.__shared_io_pool_size = 0
  ORCL.__shared_pool_size = 436207616
  ORCL.__streams_pool_size = 0
  *.audit_file_dest='/U01/app/Oracle/admin/ORCL/adump '
  * .audit_trail = "db".
  * full = '11.2.0.0.0'
  *.control_files='/u01/app/oracle/oradata/orcl/control01.ctl','/u01/app/oracle/flash_recovery_area/orcl/control02.ctl'
  * .db_block_size = 8192
  * .db_domain = "
  * .db_name = "orcl".
  *.db_recovery_file_dest='/U01/app/Oracle/flash_recovery_area/vvcoredb '
  * .db_recovery_file_dest_size = 4070572032
  *.diagnostic_dest='/U01/app/Oracle '
  *. Dispatchers ='(Protocol=TCP) (SERVICE = orclXDB)"
  * .memory_target = 3313500160
  * .open_cursors = 300
  * runoff = 150
  * .remote_login_passwordfile = "EXCLUSIVE."
  * .undo_tablespace = "UNDOTBS1.
  
  Please suggest me I miss some steps when trying to duplicate database?
  
  Any suggestions are welcome.
  
  Thanks in advance!
  
  P/s: sorry for my bad English.

  This error is because the location of the controlfile specified in your spfile is not present on your server to clone. Change the location of the parameter cntrolfile in spfil or create the same location on the server.

  Published by: Slim on 24 Sep 2012 17:47

• Moving database from 1 server to another via Data Pump - some queries

  Hello
  
  I am planing to move my database from one windows server to another. Part of the obligation is also to update this database 10g to 11.2.0.3. So I'm combining 2 tasks using the export / import method (via Data Pump) upgrade.
  
  Regarding export / import (which will be a pump full data of the database export) my plan is.
  
  create an empty 11.2.0.3 target database on the server (same number of control files, and redo logs etc.) ready for an import of the source database
  Q1. This will create tablespaces SYSTEM and UNDO - I presume the datapump export doesn't include these spaces of storage anyway?
  
  For export, I intend to simulate CONSISTENT = Y using FLASHBACK_TIME = SYSTIMESTAMP
  Q2. What is the return of flame characteristics must be active on the source database to use this knowledge should I Flashback Database enabled on the source (as opposed to other flashback features) database?
  
  My target is a virtual server with a single virtual processor
  Q3. Is there any point PARALLEL usinng in the import settings file (normally I would fix this number of processors - however in the case of this virtual server, it is actually onely a virtual processor)?
  
  For the import, I intend to use the REMAP_DATAFILE option to change the location of the data files on the target server
  
  Q4. If the import fails before the end, what is the best course of action? for example I just let go of data storage spaces and remake a complete import?
  
  Thank you
  Jim

  Jim,

  I'll take a pass on your questions:

  create an empty 11.2.0.3 target database on the server (same number of control files, and redo logs etc.) ready for an import > source database
  Q1. This will create tablespaces SYSTEM and UNDO - I presume the datapump export does not include these storage spaces > anyway?

  The system tablespace is created when you create a database, but the Data Pump will export and try to import. It will fail with tablespace exists. I am sure that the undo tablespace will be also exported and imported. If they are there, then just import will report that they already exist.

  For export, I intend to simulate CONSISTENT = Y using FLASHBACK_TIME = SYSTIMESTAMP
  Q2. What is the return of flame characteristics must be active on the source database to use this knowledge should I Flashback Database active > on the source (as opposed to other flashback features) database?

  I know not true about it. I thought that you need just enough cancel, but I hope that others will run in.

  My target is a virtual server with a single virtual processor
  Q3. Y at - it no PARALLEL point usinng in the import settings file (normally I put this on the number of processors - > however in the case of this virtual server, it is actually onely a virtual processor)?

  We recommend usually 2 times the number of processes, so 2 parallel should be ok.

  For the import, I intend to use the REMAP_DATAFILE option to change the location of the data files on the target server

  Q4. If the import fails before the end, what is the best course of action? that is, do I just give up storage of data and redo a > full import?

  It depends what is failure. Most of the failures will not stop work, but if this is the case, then most of these jobs may simply be restarted. To restart a job, you just need to know the name of the task, which is printed as you start to export/import, or you name the task in your order Data Pump. To restart, follow these steps:

  password/user Impdp attach = job_name

  If you do not name the work, the name of the job will be something like

  User.sys_import_full_01

  Hope that helps - and good luck with your migration.

  Dean

• Export of databases from phpMyAdmin on another server

  Tomorrow, I need to export 3 databases from one server to another using phpMyAdmin. I'm pretty confident, I can understand, but I want to be sure to leave a copy of the files on the original server. We know if there is an option that I choose to ensure that only one copy of the files are exported?

  I did several times without any problems.  Basic steps:

  1. Open PHPMyAdmin on the new server, and create a database exactly as your old server name.
  2. Open PHPMyAdmin on the old server, and then select the database you want to export, click Export.
  3. In the export window, make sure that all the tables you want to export are selected, SQL is the export and INSERT is the export type:

  

  1. Now click OK, a SQL script will now generate, copy and save this in a text file on your computer.
  2. So what you've done, it's creating an export SQL that maintains the original database intact.
  3. Select PHPMyAdmin on the new server and make sure you have the new database selected.
  4. Click SQL, paste the text and click OK, all your tables and the data should be inserted.
  5. If you have a localhost configuration on your computer, and then test this first.
  6. Don't forget to modify database connection files if the server host is different, or if you use a different database name, do not forget to change the name of it in the connection files as well.
  7. I hope this helps.

• Access to the database/schema to another server...

  Hello - I have a need that will require me to access additional information about a schema on a server that is different from what my APEX installation runs on (IE 3rd part of the data that is not part of the inherent schema that accesses the APEX)...
  
  My APEX server running version 3.2.1.00.11 on top of oracle 11 g Enterprise Edition Release 11.1.0.7.0 - 64 bit Production. We will call this server "A".
  
  The target server is currently an Oracle server, but will eventually migrate to a Teradata installation (no - I have no word to say in the matter!). We will call this server 'B '. No idea what versions in both cases.
  
  I understand that if I needed to access different patterns on the same server (IE Server A) it would be easy enough to do using grant statements.
  
  Also, I understand that to access a schema on server B, I could use a DBLink to do.
  
  My questions are:
  
  (1) oracle allow a DBLink to teradata? I found the following thread that seems to indicate that it is possible (or at least used to be - don't know if it's still a valid configuration) Re: Teradata to Oracle connection
  
  (2) is there another way to make this available external data source? A tech in our team 'Architecture COMPUTING"said DBLinks are not recommended or a best practice. He proposed adding the data source 'directly '?
  
  This thread (add multiple schemas in a workspace seems to speak of adding multiple schemas to a workspace, but I do not have access to this part of our oracle server (I'm only a workspace administration).)
  
  (3) if I create a view that accesses the tables through the DBLink to Server B when it comes to Oracle, and then update the DBLink to point to the new teradata server during the migration happens - it will break anything within the APEX?
  
  My hypothesis is that the table names are the same concerns only APEX that the view is valid and not what fuels the view.
  
  
  The rationale against using DBLinks gave me was that "it is not sensible for APEX down to the oracle database (its native underlying server/schema) to cross to another server and return to the oracle database that then went up to the APEX." It makes more sense for APEX to go straight to the other source of data. Normally, I would say that they (Apex/infrastructure) are the same server so it does not really matter that he might have to go through additional 1 'service' or 'interface', but this area is not my specialty.
  
  Also - I think that technically speaking our APEX service is already separated from its native schema/data on different servers (for load balancing), so in this case really maybe a middle Server Getting (IE Server APEX A-> native schema/data of the server where the DBLink might be-> server B) do an unnecessary extra jump (APEX Server A)-> server B. Note : I am sure that our architect does not know that this is the case, then it is not part of its raison d'etre.
  
  Thoughts?
  
  Thank you!
  Jim

  (1) there is a wide variety of databases that you can access from Oracle using the links to the db. The main purpose of a db link must provide connectivity between databases that are not consistent with the use of a certain type of driver or translator. Some databases provide native connectivity with other thing than their own products.

  (2) I would ask another dba from this source that he or she recommends, and if he or she has all the documentation. The long and short of it is (as I explained above) few providers of database provides native support for other database engines, which is needed for the kind of "direct connection" implies that person. My suspicion is that this person is an ODBC user and is equivalent to the use of ODBC drivers with "direct connection", which is far from accurate. ODBC only provides a generic interface to a database, at the expense of speed, functionality and efficiency thanks to the translation of the command and overhead.

  (3) oracle generally doesn't care about the back end of a connection to a different database and neither does APEX. As long as you can build a database to the database in question, shouldn't you have any problems ask these data, although only in a reduced performance due to air travel, networking, drivers, etc.

  Really, APEX is intended to be run against and integrates better with Oracle databases. If your main data is on another platform, APEX may not be the best solution for your needs.

• 11.1.0.7 database move (solaris 9) to another server (solaris 10)?

  Hi gurus,
  
  I have the production database which is having performance issues due to the high utilization of the processor in the area (due to other databases). We decided to move the database to another area, the source is 11.1.0.7 version (solaris 9), is it a good idea to move from db to solaris box 10 (clone)? no compatibility issues? or additional patch needed? can you please help?
  
  Thank you.

  Salvation;

  Pelase see the paragraphs below:
  Note to master for the upgrades of Oracle database and migration [ID 1152016.1]
  Oracle database on Unix AIX, HP - UX, Linux, Mac OS X, Solaris, Tru64 Unix operating system Installation and Configuration requirements checklist (8.0.5 to 11.2) [ID 169706.1]

  Respect of
  HELIOS

• ESX 3.5 migrate vcenter to another server

  
  How to migrate from ESX 3.5 vcenter migrate to another server? I need to drop the current server vcenter.

  What is the best way to migrate?

  Also, how can I move the license server?

  Thank you

  Be physical vmotion wouldn't work - then you options:

  (1) vCenter maintaining physical - to maintain the existing environment, you will need to copy the existing database on the new server vCenter - once it is install a new copy of vCenter on the new machine set up the oDBC connector to point to the version copied from the database. If you are not concerned to maintain the existing environment, you can simply install a fresh instance of vcenter and remove the old environment ESX hosts and add them to the new vcenter.

  Yu could also invest in a product like PlateSpin migrate and migration of P2P.

  (2) travel vCenter for a VM - use Standaloone of VMware P2V VM vCenter Converter.