{"id":12826,"date":"2019-10-01T07:47:10","date_gmt":"2019-10-01T05:47:10","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/"},"modified":"2019-10-01T07:47:10","modified_gmt":"2019-10-01T05:47:10","slug":"migrating-oracle-database-from-windows-to-oda","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/","title":{"rendered":"Migrating Oracle database from windows to ODA"},"content":{"rendered":"

Nowadays I have been working on an interesting customer project where I had to migrate windows oracle standard databases to ODA. The ODAs are X7-2M Models, running version 18.5. This version is coming with Red Hat Enterprise Linx 6.10 (Santiago). Both windows databases and target ODA databases are running PSU 11.2.0.4.190115. But this would definitively also be working for oracle 12c and oracle 18c databases. The databases are licensed with Standard Edition, so migrating through data guard was not possible. Through this blog I would like to share the experience I could get on this topic as well as the method and steps I have been using to successfully migrate those databases.
\n<\/p>\n

Limitations<\/h3>\n

Windows and Linux platform been on the same endian, I have been initially thinking that it would not be more complicated than simply duplicating the windows database to an ODA instance using the last backup. ODA databases are OMF databases, so can not be easier, as no convert parameter is needed.
\nAfter having created a single instance database on the ODA, exported the current database pfile and adapted it for the ODA, created the needed TNS connections, I have been running a single RMAN duplicate command :
\n
\nRMAN> run {
\n2> set newname for database to new;
\n3> duplicate target database to 'ODA_DBNAME' backup location '\/u99\/app\/oracle\/backup';
\n4> }
\n<\/code><\/p>\n

Note : If the database is huge, as for example, more than a Tera bytes, and your sga is small, you might want to increase it. Having a bigger sga size will lower the restore time. Minimum 50 GB would be a good compromise. Also if your ODA is from the ODA-X7 family you will benefit from the NVMe technologie. As per my experience, a duplication of 1.5 TB database, with backup stored locally, did not take more than 40 minutes.<\/em><\/p>\n

I have been more than happy to see the first duplication step been successfully achieved :
\n
\nFinished restore at 17-JUL-2019 16:45:10
\n<\/code><\/p>\n

And I was expecting the same for the next recovery part.<\/p>\n

Unfortunately, this didn’t end as expected and I quickly got following restore errors :
\n
\nErrors in memory script
\nRMAN-03015: error occurred in stored script Memory Script
\nRMAN-06136: ORACLE error from auxiliary database: ORA-01507: database not mounted
\nORA-06512: at \"SYS.X$DBMS_RCVMAN\", line 13661
\nORA-06512: at line 1
\nRMAN-03015: error occurred in stored script Memory Script
\nRMAN-20000: abnormal termination of job step
\nRMAN-11003: failure during parse\/execution of SQL statement: alter database recover logfile '\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_07_17\/o1_mf_1_25514_glyf3yd3_.arc'
\nRMAN-11001: Oracle Error:
\nORA-10562: Error occurred while applying redo to data block (file# 91, block# 189)
\nORA-10564: tablespace DBVISIT
\nORA-01110: data file 91: '\/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/o1_mf_dbvisit_glyczqcj_.dbf'
\nORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 501874
\nORA-00600: internal error code, arguments: [4502], [0], [], [], [], [], [], [], [], [], [], []
\nRMAN-00571: ===========================================================
\nRMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
\nRMAN-00571: ===========================================================
\nRMAN-03002: failure of Duplicate Db command at 07\/17\/2019 16:45:32
\nRMAN-05501: aborting duplication of target database
\n<\/code><\/p>\n

Troubleshooting the problem I could understand that migrating database from Windows to Linux might not be so simple. Following oracle Doc ID is describing the problem :
\nRestore From Windows To Linux using RMAN Fails (Doc ID 2003327.1)
\nCross-Platform Database Migration (across same endian) using RMAN Transportable Database (Doc ID 1401921.1)
\nRMAN DUPLICATE\/RESTORE\/RECOVER Mixed Platform Support (Doc ID 1079563.1)
\nRestore From Windows To Linux using RMAN Fails (Doc ID 2003327.1)<\/p>\n

The problem is coming from the fact that recovering redo transactions between windows and linux platform is not supported if the database is not a standby one. For standard database version, the only possibility would be to go through a cold backup which, in my case, was impossible knowing the database size, the time taken to execute a backup and the short maintenance windows.<\/p>\n

Looking for other solution and doing further tests, I could find a solution that I’m going to describe in the next steps.<\/p>\n

Restoring the database from the last backup<\/h3>\n

In order to restore the database, I have been running next steps.<\/p>\n

    \n
  1. Start the ODA instance in no mount :<\/li>\n


    \nSQL> startup nomount
    \n<\/code><\/p>\n

  2. Restore the last available control file from backup with rman :<\/li>\n


    \nRMAN> connect target \/
    \n 
    \nRMAN> restore controlfile from '\/mnt\/backupNFS\/oracle\/ODA_DBNAME\/20190813_233004_CTL_ODA_DBNAME_1179126808_S2864_P1.BCK';
    \n<\/code><\/p>\n

  3. Mount the database :<\/li>\n


    \nSQL> alter database mount;
    \n<\/code><\/p>\n

  4. Catalog the backup path :<\/li>\n


    \nRMAN> connect target \/
    \n 
    \nRMAN> catalog start with '\/mnt\/backupNFS\/oracle\/ODA_DBNAME';
    \n<\/code><\/p>\n

  5. And finally restore the database :<\/li>\n


    \nRMAN> connect target \/
    \n 
    \nRMAN> run {
    \n2> set newname for database to new;
    \n3> restore database;
    \n4> switch datafile all;
    \n5> }
    \n<\/code>\n<\/ol>\n

    Convert the primary database to a physical standby database<\/h3>\n

    In order to be able to recover the database we will convert the primary database to a physical standby one.<\/p>\n

      \n
    1. We can check the actual status and see that our database is a primary one in mounted state :<\/li>\n


      \nSQL> select status,instance_name,database_role,open_mode from v$database,v$Instance;
      \n 
      \nSTATUS INSTANCE_NAME DATABASE_ROLE OPEN_MODE
      \n------------ ---------------- ---------------- --------------------
      \nMOUNTED ODA_DBNAME PRIMARY MOUNTED
      \n<\/code><\/p>\n

    2. We will convert the database to a physical standby<\/li>\n


      \nSQL> alter database convert to physical standby;
      \n 
      \nDatabase altered.
      \n<\/code><\/p>\n

    3. We need to restart the database.<\/li>\n


      \nSQL> shutdown immediate
      \n 
      \nSQL> startup mount
      \n<\/code><\/p>\n

    4. We can check new database status<\/li>\n


      \nSQL> select status,instance_name,database_role,open_mode from v$database,v$Instance;
      \n 
      \nSTATUS INSTANCE_NAME DATABASE_ROLE OPEN_MODE
      \n------------ ---------------- ---------------- --------------------
      \nMOUNTED ODA_DBNAME PHYSICAL STANDBY MOUNTED
      \n<\/code>\n<\/ol>\n

      Get the current windows SCN database<\/h3>\n

      We are now ready to recover the database and the application can be stopped. The next steps will now be executed during the maintenance windows. The windows database listener can be stopped to make sure there is no new connection.<\/p>\n

        \n
      1. We will make sure there is no existing application session on the database :<\/li>\n


        \nSQL> set linesize 300
        \nSQL> set pagesize 500
        \nSQL> col machine format a20
        \nSQL> col service_name format a20
        \n 
        \nSQL> select SID, serial#, username, machine, process, program, status, service_name, logon_time from v$session where username not in ('SYS', 'PUBLIC') and username is not null order by status, username;
        \n<\/code><\/p>\n

      2. We will create a restore point :<\/li>\n


        \nSQL> create restore point for_migration_14082019;
        \n 
        \nRestore point created.
        \n<\/code><\/p>\n

      3. We will get the last online log transactions archived :<\/li>\n


        \nSQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
        \n 
        \nSystem altered.
        \n<\/code><\/p>\n

      4. We will retrieve the SCN corresponding to the restore point :<\/li>\n


        \nSQL> col scn format 999999999999999
        \n 
        \nSQL> select scn from v$restore_point where lower(name)='for_migration_14082019';
        \n 
        \n SCN
        \n----------------
        \n 13069540631
        \n<\/code><\/p>\n

      5. We will backup the last archive log. This will be executed on the windows database using our dbi services internal DMK tool (https:\/\/www.dbi-services.com\/offering\/products\/dmk-management-kit\/<\/a>) :<\/li>\n


        \nservicedbi@win_srv:E:apporaclelocaldmk_custombin [ODA_DBNAME] .\/rman_backup_ODA_DBNAME_arc.bat
        \n 
        \nE:apporaclelocaldmk_custombin>powershell.exe -command \"E:apporaclelocaldmk_habincheck_primary.ps1 ODA_DBNAME 'dmk_rman.ps1 -s ODA_DBNAME -t bck_arc.rcv -c E:apporacleadminODA_DBNAMEetcrman.cfg
        \n 
        \n[OK]::KSBL::RMAN::dmk_dbbackup::ODA_DBNAME::bck_arc.rcv
        \n 
        \nLogfile is : E:apporacleadminODA_DBNAMElogODA_DBNAME_bck_arc_20190814_141754.log
        \n 
        \nRMAN return Code: 0
        \n2019-08-14_02:19:01::check_primary.ps1::MainProgram ::INFO ==> Program completed
        \n<\/code>\n<\/ol>\n

        Recover the database<\/h3>\n

        The database can now be recovered till our 13069540631 SCN number.<\/p>\n

          \n
        1. We will first need to catalog new archive log backups :<\/li>\n


          \nRMAN> connect target \/
          \n 
          \nRMAN> catalog start with '\/mnt\/backupNFS\/oracle\/ODA_DBNAME';
          \n<\/code><\/p>\n

        2. And recover the database till SCN 13069540632 :<\/li>\n


          \nRMAN> connect target \/
          \n 
          \nRMAN> run {
          \n2> set until scn 13069540632;
          \n3> recover database;
          \n4> }
          \n 
          \narchived log file name=\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30098_go80084r_.arc RECID=30124 STAMP=1016289320
          \narchived log file name=\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30099_go80084x_.arc thread=1 sequence=30099
          \nchannel default: deleting archived log(s)
          \narchived log file name=\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30099_go80084x_.arc RECID=30119 STAMP=1016289320
          \narchived log file name=\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30100_go8008bg_.arc thread=1 sequence=30100
          \nchannel default: deleting archived log(s)
          \narchived log file name=\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30100_go8008bg_.arc RECID=30121 STAMP=1016289320
          \nmedia recovery complete, elapsed time: 00:00:02
          \nFinished recover at 14-AUG-2019 14:35:23
          \n<\/code><\/p>\n

        3. We can check the alert log and see that recovering has been performed until SCN 13069540632 :<\/li>\n


          \noracle@ODA02:\/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/ [ODA_DBNAME] taa
          \nORA-279 signalled during: alter database recover logfile '\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30098_go80084r_.arc'...
          \nalter database recover logfile '\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30099_go80084x_.arc'
          \nMedia Recovery Log \/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30099_go80084x_.arc
          \nORA-279 signalled during: alter database recover logfile '\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30099_go80084x_.arc'...
          \nalter database recover logfile '\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30100_go8008bg_.arc'
          \nMedia Recovery Log \/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30100_go8008bg_.arc
          \nWed Aug 14 14:35:23 2019
          \nIncomplete Recovery applied until change 13069540632 time 08\/14\/2019 14:13:46
          \nMedia Recovery Complete (ODA_DBNAME)
          \nCompleted: alter database recover logfile '\/u03\/app\/oracle\/fast_recovery_area\/ODA_DBNAME_RZA\/archivelog\/2019_08_14\/o1_mf_1_30100_go8008bg_.arc'<\/code><\/p>\n

        4. We can check the new ODA database current SCN :<\/li>\n


          \nSQL> col current_scn format 999999999999999
          \n 
          \nSQL> select current_scn from v$database;
          \n 
          \n CURRENT_SCN
          \n----------------
          \n 13069540631
          \n<\/code>\n<\/ol>\n

          Convert database to primary again<\/h3>\n

          Database can now be converted back to primary.
          \n
          \nSQL> alter database activate standby database;
          \n 
          \nDatabase altered.<\/code><\/p>\n


          \nSQL> select status,instance_name,database_role,open_mode from v$database,v$Instance;
          \n 
          \nSTATUS INSTANCE_NAME DATABASE_ROLE OPEN_MODE
          \n------------ ---------------- ---------------- --------------------
          \nMOUNTED ODA_DBNAME PRIMARY MOUNTED
          \n<\/code><\/p>\n

          At this step if the windows source database would be running 11.2.0.3 version, we could successfully upgrade the new ODA database to 11.2.0.4 following common oracle database upgrade process.<\/em><\/p>\n

          And finally we can open our database and have the database been migrated from windows to linux.<\/p>\n


          \nSQL> alter database open;
          \n 
          \nDatabase altered.
          \n<\/code><\/p>\n


          \nSQL> select status,instance_name,database_role,open_mode from v$database,v$Instance;
          \n 
          \nSTATUS INSTANCE_NAME DATABASE_ROLE OPEN_MODE
          \n------------ ---------------- ---------------- --------------------
          \nOPEN ODA_DBNAME PRIMARY READ WRITE
          \n<\/code><\/p>\n


          \noracle@ODA02:\/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/ [ODA_DBNAME] ODA_DBNAME
          \n********* dbi services Ltd. *********
          \nSTATUS : OPEN
          \nDB_UNIQUE_NAME : ODA_DBNAME_RZA
          \nOPEN_MODE : READ WRITE
          \nLOG_MODE : ARCHIVELOG
          \nDATABASE_ROLE : PRIMARY
          \nFLASHBACK_ON : NO
          \nFORCE_LOGGING : YES
          \nVERSION : 11.2.0.4.0
          \n*************************************
          \n<\/code><\/p>\n

          Post migration steps<\/h3>\n

          There will be a few post migration steps to be executed.<\/p>\n

          Created redo logs again<\/h4>\n

          Redo logs are still stamped with windows path and therefore have been created in $ORACLE_HOME\/dbs folder. In this steps we will create new OMF one again.<\/p>\n

            \n
          1. Checking current online log members :<\/li>\n


            \nSQL> set linesize 300
            \nSQL> set pagesize 500
            \nSQL> col member format a100
            \n 
            \nSQL> select a.GROUP#, b.member, a.status, a.bytes\/1024\/1024 MB from v$log a, v$logfile b where a.GROUP#=b.GROUP#;
            \n 
            \n GROUP# MEMBER STATUS MB
            \n---------- ---------------------------------------------------------------------------------------------------- ---------------- ----------
            \n 6 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_6_1.LOG UNUSED 500
            \n 6 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_6_2.LOG UNUSED 500
            \n 5 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_5_2.LOG UNUSED 500
            \n 5 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_5_1.LOG UNUSED 500
            \n 4 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_4_2.LOG UNUSED 500
            \n 4 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_4_1.LOG UNUSED 500
            \n 3 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_3_2.LOG UNUSED 500
            \n 3 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_3_1.LOG UNUSED 500
            \n 2 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_2_2.LOG UNUSED 500
            \n 2 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_2_1.LOG UNUSED 500
            \n 1 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_1_2.LOG CURRENT 500
            \n 1 \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_1_1.LOG CURRENT 500
            \n<\/code><\/p>\n

          2. Drop the first unused redo log group keeping only one :<\/li>\n


            \nSQL> alter database drop logfile group 6;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database drop logfile group 5;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database drop logfile group 4;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database drop logfile group 3;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database add logfile group 3 size 500M;
            \n 
            \nDatabase altered.
            \n<\/code><\/p>\n

          3. Create the recent dropped group again :<\/li>\n


            \nSQL> alter database add logfile group 3 size 500M;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database add logfile group 4 size 500M;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database add logfile group 5 size 500M;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database add logfile group 6 size 500M;
            \n 
            \nDatabase altered.
            \n<\/code><\/p>\n

          4. Drop the last unused redo log group and create it again :<\/li>\n


            \nSQL> alter database drop logfile group 2;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database add logfile group 2 size 500M;
            \n 
            \nDatabase altered.
            \n<\/code><\/p>\n

          5. Execute a switch log file and checkpoint so the current redo group becomes unused :<\/li>\n


            \nSQL> alter system switch logfile;
            \n 
            \nSystem altered.
            \n 
            \nSQL> alter system checkpoint;
            \n 
            \nSystem altered.
            \n<\/code><\/p>\n

          6. Drop it and create it again :<\/li>\n


            \nSQL> alter database drop logfile group 1;
            \n 
            \nDatabase altered.
            \n 
            \nSQL> alter database add logfile group 1 size 500M;
            \n 
            \nDatabase altered.
            \n<\/code><\/p>\n

          7. Check redo group members :<\/li>\n


            \nSQL> select a.GROUP#, b.member, a.status, a.bytes\/1024\/1024 MB from v$log a, v$logfile b where a.GROUP#=b.GROUP#;
            \n 
            \n GROUP# MEMBER STATUS MB
            \n---------- ---------------------------------------------------------------------------------------------------- ---------------- ----------
            \n 3 \/u03\/app\/oracle\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_3_go81rj4t_.log INACTIVE 500
            \n 3 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_3_go81rjqn_.log INACTIVE 500
            \n 4 \/u03\/app\/oracle\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_4_go81ron1_.log UNUSED 500
            \n 4 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_4_go81rp6o_.log UNUSED 500
            \n 5 \/u03\/app\/oracle\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_5_go81rwhs_.log UNUSED 500
            \n 5 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_5_go81rx1g_.log UNUSED 500
            \n 6 \/u03\/app\/oracle\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_6_go81s1rk_.log UNUSED 500
            \n 6 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_6_go81s2bx_.log UNUSED 500
            \n 2 \/u03\/app\/oracle\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_2_go81sgdf_.log CURRENT 500
            \n 2 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_2_go81sgxd_.log CURRENT 500
            \n 1 \/u03\/app\/oracle\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_1_go81vpls_.log UNUSED 500
            \n 1 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/redo\/ODA_DBNAME_RZA\/onlinelog\/o1_mf_1_go81vq4v_.log UNUSED 500
            \n<\/code><\/p>\n

          8. Delete the wrong previous redo log members files :<\/li>\n


            \noracle@ODA02:\/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/ [ODA_DBNAME] cdh
            \n 
            \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/ [ODA_DBNAME] cd dbs
            \n 
            \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] ls -ltrh *REDO*.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_6_2.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_6_1.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_5_2.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_5_1.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_4_2.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_4_1.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_3_2.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_3_1.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_2_2.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 14:59 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_2_1.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 15:05 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_1_2.LOG
            \n-rw-r----- 1 oracle asmadmin 501M Aug 14 15:05 I:FAST_RECOVERY_AREAODA_DBNAME_SITE1ONLINELOGREDO_1_1.LOG
            \n 
            \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] rm *REDO*.LOG
            \n<\/code>\n<\/ol>\n

            Created temp file again<\/h4>\n
              \n
            1. Checking current temp file we can see that the path is still the windows one :<\/li>\n


              \nSQL> set linesize 300
              \nSQL> col name format a100
              \n 
              \nSQL> select b.name, b.status, b.bytes\/1024\/1024 MB, a.name from v$tablespace a, v$tempfile b where a.TS#=b.TS#;
              \n 
              \nNAME STATUS MB NAME
              \n---------------------------------------------------------------------------------------------------- ------- ---------- -------------------------------------------
              \nF:ORADATAODA_DBNAMETEMPORARY_DATA_1.DBF ONLINE 8192 TEMPORARY_DATA
              \n<\/code><\/p>\n

            2. We can check that the default temporary tablespace is TEMPORARY_DATA<\/li>\n


              \nSQL> col property_value format a50
              \n 
              \nSQL> select property_name, property_value from database_properties where property_name like '%DEFAULT%TABLESPACE%';
              \n 
              \nPROPERTY_NAME PROPERTY_VALUE
              \n------------------------------ --------------------------------------------------
              \nDEFAULT_TEMP_TABLESPACE TEMPORARY_DATA
              \nDEFAULT_PERMANENT_TABLESPACE USER_DATA
              \n<\/code><\/p>\n

            3. Let’s create a new temp tablespace and make it the default one<\/li>\n


              \nSQL> create temporary tablespace TEMP tempfile size 8G;
              \n 
              \nTablespace created.
              \n 
              \nSQL> alter database default temporary tablespace TEMP;
              \n 
              \nDatabase altered.
              \n 
              \nSQL> select property_name, property_value from database_properties where property_name like '%DEFAULT%TABLESPACE%';
              \n 
              \nPROPERTY_NAME PROPERTY_VALUE
              \n------------------------------ --------------------------------------------------
              \nDEFAULT_TEMP_TABLESPACE TEMP
              \nDEFAULT_PERMANENT_TABLESPACE USER_DATA
              \n<\/code><\/p>\n

            4. Drop previous TEMPORARY_DATA tablespace<\/li>\n


              \nSQL> drop tablespace TEMPORARY_DATA including contents and datafiles;
              \n 
              \nTablespace dropped.
              \n 
              \nSQL> select b.file#, b.name, b.status, b.bytes\/1024\/1024 MB, a.name from v$tablespace a, v$tempfile b where a.TS#=b.TS#;
              \n 
              \n FILE# NAME STATUS MB NAME
              \n---------- ---------------------------------------------------------------------------------------------------- ------- ----------
              \n 3 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/o1_mf_temp_go83m1tp_.tmp ONLINE 8192 TEMP
              \n<\/code><\/p>\n

            5. Create TEMPORARY_DATA tablespace again and make it the default one :<\/li>\n


              \nSQL> create temporary tablespace TEMPORARY_DATA tempfile size 8G;
              \n 
              \nTablespace created.
              \n 
              \nSQL> select b.file#, b.name, b.status, b.bytes\/1024\/1024 MB, a.name from v$tablespace a, v$tempfile b where a.TS#=b.TS#;
              \n 
              \n FILE# NAME STATUS MB NAME
              \n---------- ---------------------------------------------------------------------------------------------------- ------- ----------
              \n 1 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/o1_mf_temporar_go83wfd7_.tmp ONLINE 8192 TEMPORARY_DATA
              \n 3 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/o1_mf_temp_go83m1tp_.tmp ONLINE 8192 TEMP
              \n 
              \nSQL> alter database default temporary tablespace TEMPORARY_DATA;
              \n 
              \nDatabase altered.
              \n 
              \nSQL> select property_name, property_value from database_properties where property_name like '%DEFAULT%TABLESPACE%';
              \n 
              \nPROPERTY_NAME PROPERTY_VALUE
              \n------------------------------ --------------------------------------------------
              \nDEFAULT_TEMP_TABLESPACE TEMPORARY_DATA
              \nDEFAULT_PERMANENT_TABLESPACE USER_DATA
              \n<\/code><\/p>\n

            6. And finally drop the intermediare temp tablespace :<\/li>\n


              \nSQL> drop tablespace TEMP including contents and datafiles;
              \n 
              \nTablespace dropped.
              \n 
              \nSQL> select b.file#, b.name, b.status, b.bytes\/1024\/1024 MB, a.name from v$tablespace a, v$tempfile b where a.TS#=b.TS#;
              \n 
              \n FILE# NAME STATUS MB NAME
              \n---------- ---------------------------------------------------------------------------------------------------- ------- ----------
              \n 1 \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/o1_mf_temporar_go83wfd7_.tmp ONLINE 8192 TEMPORARY_DATA
              \n<\/code><\/p>\n

            7. Appropriate max size can be given to the new created temp tablespace<\/li>\n


              \nSQL> alter database tempfile '\/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/ODA_DBNAME_RZA\/datafile\/o1_mf_temporar_go83wfd7_.tmp' autoextend on maxsize 31G;
              \n 
              \nDatabase altered.
              \n<\/code><\/p>\n

            8. Remove wrong temp file stored in $ORACLE_HOME\/dbs<\/li>\n


              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] ls -ltr
              \n-rw-r--r-- 1 oracle oinstall 2851 May 15 2009 init.ora
              \n-rw-r--r-- 1 oracle oinstall 64 Jul 25 08:10 initODA_DBNAME.ora.old
              \n-rw-r----- 1 oracle oinstall 2048 Jul 25 08:10 orapwODA_DBNAME
              \n-rw-r--r-- 1 oracle oinstall 67 Jul 25 08:31 initODA_DBNAME.ora
              \n-rw-r----- 1 oracle asmadmin 8589942784 Aug 14 08:14 F:ORADATAODA_DBNAMETEMPORARY_DATA_1.DBF
              \n-rw-rw---- 1 oracle asmadmin 1544 Aug 14 14:59 hc_ODA_DBNAME.dat
              \n-rw-r----- 1 oracle asmadmin 43466752 Aug 14 15:48 snapcf_ODA_DBNAME.f
              \n 
              \noracle@RZA-ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] rm F:ORADATAODA_DBNAMETEMPORARY_DATA_1.DBF
              \n<\/code>\n<\/ol>\n

              Apply specific ODA parameters<\/h4>\n

              Following specific ODA parameters can be updated to the new created instance.<\/p>\n


              \nSQL> alter system set \"_datafile_write_errors_crash_instance\"=false scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set \"_db_writer_coalesce_area_size\"=16777216 scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set \"_disable_interface_checking\"=TRUE scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set \"_ENABLE_NUMA_SUPPORT\"=FALSE scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set \"_FILE_SIZE_INCREASE_INCREMENT\"=2143289344 scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set \"_gc_policy_time\"=0 scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set \"_gc_undo_affinity\"=FALSE scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set db_block_checking='FULL' scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set db_block_checksum='FULL' scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set db_lost_write_protect='TYPICAL' scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set sql92_security=TRUE scope=spfile;
              \n 
              \nSystem altered.
              \n 
              \nSQL> alter system set use_large_pages='only' scope=spfile;
              \n 
              \nSystem altered.
              \n<\/code><\/p>\n

              “_fix_control”parameter is specific to Oracle12c and not compatible Oracle 11g. See Doc ID 2145105.1.<\/p>\n

              Register database in grid<\/h4>\n

              After applying specific ODA instance parameters, we can register the database in the grid and start it with the grid.<\/p>\n


              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] srvctl add database -d ODA_DBNAME_RZA -o \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1 -c SINGLE -i ODA_DBNAME -x RZA-ODA02 -m ksbl.local -p \/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA\/dbs\/spfileODA_DBNAME.ora -r PRIMARY -s OPEN -t IMMEDIATE -n ODA_DBNAME -j \"\/u02\/app\/oracle\/oradata\/ODA_DBNAME_RZA,\/u03\/app\/oracle\"
              \n 
              \nSQL> shutdown immediate
              \nDatabase closed.
              \nDatabase dismounted.
              \nORACLE instance shut down.
              \n 
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] srvctl start database -d ODA_DBNAME_RZA
              \n 
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] srvctl status database -d ODA_DBNAME_RZA
              \nInstance ODA_DBNAME is running on node rza-oda02
              \n 
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] ODA_DBNAME
              \n********* dbi services Ltd. *********
              \nSTATUS : OPEN
              \nDB_UNIQUE_NAME : ODA_DBNAME_RZA
              \nOPEN_MODE : READ WRITE
              \nLOG_MODE : ARCHIVELOG
              \nDATABASE_ROLE : PRIMARY
              \nFLASHBACK_ON : NO
              \nFORCE_LOGGING : YES
              \nVERSION : 11.2.0.4.0
              \n*************************************
              \n<\/code><\/p>\n

              We can check the well functionning :
              \n
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] srvctl stop database -d ODA_DBNAME_RZA
              \n 
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] srvctl status database -d ODA_DBNAME_RZA
              \nInstance ODA_DBNAME is not running on node rza-oda02
              \n 
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] ODA_DBNAME
              \n********* dbi services Ltd. *********
              \nSTATUS : STOPPED
              \n*************************************
              \n 
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] srvctl start database -d ODA_DBNAME_RZA
              \n 
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] srvctl status database -d ODA_DBNAME_RZA
              \nInstance ODA_DBNAME is running on node rza-oda02
              \n 
              \noracle@ODA02:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [ODA_DBNAME] ODA_DBNAME
              \n********* dbi services Ltd. *********
              \nSTATUS : OPEN
              \nDB_UNIQUE_NAME : ODA_DBNAME_RZA
              \nOPEN_MODE : READ WRITE
              \nLOG_MODE : ARCHIVELOG
              \nDATABASE_ROLE : PRIMARY
              \nFLASHBACK_ON : NO
              \nFORCE_LOGGING : YES
              \nVERSION : 11.2.0.4.0
              \n*************************************<\/code><\/p>\n

              Conclusion<\/h3>\n

              Going through a physical standby database, I was able to migrate successfully the windows databases into ODA linux one. I have been able to achieve migration of source 11.2.0.4 databases but also 11.2.0.3 database by adding an upgrade step in the process.<\/p>\n","protected":false},"excerpt":{"rendered":"

              Nowadays I have been working on an interesting customer project where I had to migrate windows oracle standard databases to ODA. The ODAs are X7-2M Models, running version 18.5. This version is coming with Red Hat Enterprise Linx 6.10 (Santiago). Both windows databases and target ODA databases are running PSU 11.2.0.4.190115. But this would definitively […]<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,59],"tags":[280,23,73,15,79,96,17,988,209,1184,270],"type_dbi":[],"class_list":["post-12826","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-oracle","tag-database","tag-dba","tag-linux","tag-migration","tag-oda","tag-oracle","tag-oracle-11g","tag-oracle-12-2","tag-oracle-12c","tag-oracle-18c","tag-rman"],"acf":[],"yoast_head":"\nMigrating Oracle database from windows to ODA - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Migrating Oracle database from windows to ODA\" \/>\n<meta property=\"og:description\" content=\"Nowadays I have been working on an interesting customer project where I had to migrate windows oracle standard databases to ODA. The ODAs are X7-2M Models, running version 18.5. This version is coming with Red Hat Enterprise Linx 6.10 (Santiago). Both windows databases and target ODA databases are running PSU 11.2.0.4.190115. But this would definitively […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-10-01T05:47:10+00:00\" \/>\n<meta name=\"author\" content=\"Marc Wagner\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Marc Wagner\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"20 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"Migrating Oracle database from windows to ODA\",\"datePublished\":\"2019-10-01T05:47:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/\"},\"wordCount\":1115,\"commentCount\":0,\"keywords\":[\"database\",\"DBA\",\"Linux\",\"Migration\",\"ODA\",\"Oracle\",\"Oracle 11g\",\"Oracle 12.2\",\"Oracle 12c\",\"Oracle 18c\",\"RMAN\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/\",\"name\":\"Migrating Oracle database from windows to ODA - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-10-01T05:47:10+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Migrating Oracle database from windows to ODA\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\",\"name\":\"Marc Wagner\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"caption\":\"Marc Wagner\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Migrating Oracle database from windows to ODA - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/","og_locale":"en_US","og_type":"article","og_title":"Migrating Oracle database from windows to ODA","og_description":"Nowadays I have been working on an interesting customer project where I had to migrate windows oracle standard databases to ODA. The ODAs are X7-2M Models, running version 18.5. This version is coming with Red Hat Enterprise Linx 6.10 (Santiago). Both windows databases and target ODA databases are running PSU 11.2.0.4.190115. But this would definitively […]","og_url":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/","og_site_name":"dbi Blog","article_published_time":"2019-10-01T05:47:10+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"20 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"Migrating Oracle database from windows to ODA","datePublished":"2019-10-01T05:47:10+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/"},"wordCount":1115,"commentCount":0,"keywords":["database","DBA","Linux","Migration","ODA","Oracle","Oracle 11g","Oracle 12.2","Oracle 12c","Oracle 18c","RMAN"],"articleSection":["Database Administration & Monitoring","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/","url":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/","name":"Migrating Oracle database from windows to ODA - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-10-01T05:47:10+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/migrating-oracle-database-from-windows-to-oda\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Migrating Oracle database from windows to ODA"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628","name":"Marc Wagner","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","caption":"Marc Wagner"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12826","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=12826"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12826\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12826"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12826"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12826"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12826"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}