title: Clone oracle 10g (linux5 32bit) to 10g (linux 6.4 64 bit)
body: <p>My Question is this can i create a clone of oracle 10g (linux5 32bit) to 10g (linux 6.4 64 bit)</p>
  
  <p>kindly help </p>
  
  <p>Can i follow this </p>
  
  <p>STEP 1: On the old system, go into SQL*Plus, sign on as SYSDBA and issue: “alter database backup controlfile to trace”. This will put the create database syntax in the trace file directory. The trace keyword tells oracle to generate a script containing a create controlfile command and store it in the trace directory identified in the user_dump_dest parameter of the init.ora file. It will look something like this:</p>
  
  <pre><code>STARTUP NOMOUNT
  CREATE CONTROLFILE REUSE DATABASE "OLDLSQ" NORESETLOGS
  NOARCHIVELOG
  MAXLOGFILES 16
  MAXLOGMEMBERS 2
  MAXDATAFILES 240
  MAXINSTANCES 1
  MAXLOGHISTORY 113
  LOGFILE
  GROUP 1 ('/u03/oradata/oldlsq/log1a.dbf',
  '/u03/oradata/olslsq/log1b.dbf') SIZE 30M,
  GROUP 2 ('/u04/oradata/oldlsq/log2a.dbf',
  '/u04/oradata/oldlsq/log2b.dbf') SIZE 30M
  DATAFILE
  '/u01/oradata/oldlsq/system01.dbf',
  '/u01/oradata/oldlsq/mydatabase.dbf'
  ;
  # Recovery is required if any of the datafiles are restored
  # backups, or if the last shutdown was not normal or immediate.
  RECOVER DATABASE
  # Database can now be opened normally.
  ALTER DATABASE OPEN;
  </code></pre>
  
  <p>STEP 2: Shutdown the old database</p>
  
  <p>STEP 3: Copy all data files into the new directories on the new server. You may change the file names if you want, but you must edit the controlfile to reflect the new data files names on the new server.</p>
  
  <pre><code>rcp /u01/oradata/oldlsq/* newhost:/u01/oradata/newlsq
  rcp /u01/oradata/oldlsq/* newhost:/u01/oradata/newlsq
  rcp /u03/oradata/oldlsq/* newhost:/u03/oradata/newlsq
  rcp /u04/oradata/oldlsq/* newhost:/u04/oradata/newlsq
  </code></pre>
  
  <p>STEP 4: Copy and Edit the Control file – Using the output syntax from STEP 1, modify the controlfile creation script by changing the following:</p>
  
  <p>Old:</p>
  
  <pre><code>CREATE CONTROLFILE REUSE DATABASE "OLDLSQ" NORESETLOGS
  </code></pre>
  
  <p>New:</p>
  
  <pre><code>CREATE CONTROLFILE SET DATABASE "NEWLSQ" RESETLOGS
  </code></pre>
  
  <p>STEP 5: Remove the “recover database” and “alter database open” syntax</p>
  
  <pre><code># Recovery is required if any of the datafiles are restored
  # backups, or if the last shutdown was not normal or immediate.
  RECOVER DATABASE
  # Database can now be opened normally.
  ALTER DATABASE OPEN;
  </code></pre>
  
  <p>STEP 6: Re-names of the data files names that have changed.</p>
  
  <p>Save as db_create_controlfile.sql.</p>
  
  <p>Old:</p>
  
  <pre><code>DATAFILE
  '/u01/oradata/oldlsq/system01.dbf',
  '/u01/oradata/oldlsq/mydatabase.dbf'
  </code></pre>
  
  <p>New:</p>
  
  <pre><code>DATAFILE
  '/u01/oradata/newlsq/system01.dbf',
  '/u01/oradata/newlsq/mydatabase.dbf'
  </code></pre>
  
  <p>STEP 7: Create the bdump, udump and cdump directories</p>
  
  <pre><code>cd $DBA/admin
  mkdir newlsq
  cd newlsq
  mkdir bdump
  mkdir udump
  mkdir cdump
  mkdir pfile
  </code></pre>
  
  <p>STEP 8: Copy-over the old init.ora file</p>
  
  <pre><code>rcp $DBA/admin/olslsq/pfile/*.ora newhost:/u01/oracle/admin/newlsq/pfile
  </code></pre>
  
  <p>STEP 9: Start the new database</p>
  
  <pre><code>@db_create_controlfile.sql
  </code></pre>
  
  <p>STEP 10: Place the new database in archivelog mode</p>