This discussion is archived
1 2 Previous Next 20 Replies Latest reply: Sep 19, 2013 12:05 PM by 993806 RSS

Database migration from NON ASM to ASM

993806 Newbie
Currently Being Moderated

Hello All,

 

I have Oracle database 11g running on NON Oracle ASM with platform Windows 64bit, I wanted to migrate it to Linux 64bit and the storage type will be Oracle ASM as well.

I

used Oracle RMAN to convert the database on source platform. the convert has completed successfully and I used the db_name_file_convert as (Non ASM source path to Non ASM destination path.

 

I moved all the converted files to the destination platform, and I reflected all the values which needed to be changed on my new pfile.ora file. I created control file on the destination platform but I can't open database with resetlogs!

 

It says file system needs recovery, I'm wondering why I need to recover the database since the source db was in read only mode.

 

Again, I haven't used "Format" in the RMAN convert command during the conversion, may be this causing this issue?

 

Have any one experienced this issue?

Mohammed

  • 1. Re: Database migration from NON ASM to ASM
    DK2010 Guru
    Currently Being Moderated

    Hi,

     

    Can you share the first line of your control file, which you used to create controlfile for the database.

     

    and what is the result of the below Query

    select file#,STATUS, FUZZY from v$datafile_header where FUZZY='YES';

  • 2. Re: Database migration from NON ASM to ASM
    993806 Newbie
    Currently Being Moderated

    I used RMAN transport script to create the control file on the destination platform, please take a look as below:

     

    CREATE CONTROLFILE SET DATABASE "xfwbudb" RESETLOGS ARCHIVELOG

        MAXLOGFILES 16

        MAXLOGMEMBERS 3

        MAXDATAFILES 100

        MAXINSTANCES 8

        MAXLOGHISTORY 9344

    LOGFILE

      GROUP 1 '+BUDB_DATAG/xfwbudb/redo01.log' SIZE 50M BLOCKSIZE 512,

      GROUP 2 '+BUDB_DATAG/xfwbudb/redo02.log' SIZE 50M BLOCKSIZE 512,

      GROUP 3 '+BUDB_DATAG/xfwbudb/redo03.log' SIZE 50M BLOCKSIZE 512

    DATAFILE

      '+BUDB_DATAG/xfwbudb/SYSTEM01.DBF',

      '+BUDB_DATAG/xfwbudb/SYSAUX01.DBF',

      '+BUDB_DATAG/xfwbudb/UNDOTBS01.DBF',

      '+BUDB_DATAG/xfwbudb/USERS01.DBF',

      '+BUDB_DATAG/xfwbudb/TD_BIPLATFORM.DBF',

      '+BUDB_DATAG/xfwbudb/TD_MDS.DBF',

      '+BUDB_DATAG/xfwbudb/USERS02'

    CHARACTER SET WE8MSWIN1252

    ;

  • 3. Re: Database migration from NON ASM to ASM
    DK2010 Guru
    Currently Being Moderated

    Hi,

    What is the o/p of this Query

    select file#,STATUS, FUZZY from v$datafile_header where FUZZY='YES';


    if no row selected then

     

     

     

     

    alter database open resetlogs;

     

     

     

     

    or

     

     

    recover database using backup controlfile until cancel;

     

     

    cancel

    alter database open resetlogs;

     

    Hope this help

  • 4. Re: Database migration from NON ASM to ASM
    993806 Newbie
    Currently Being Moderated

    Still encountering the same issue, please take a look as in the output below:

     

    On the source platform database:

     

    SQL> select file#,STATUS, FUZZY from v$datafile_header where FUZZY='YES';

     

         FILE# STATUS  FUZ

    ---------- ------- ---

             1 ONLINE  YES

             2 ONLINE  YES

             3 ONLINE  YES

             4 ONLINE  YES

             5 ONLINE  YES

             6 ONLINE  YES

             7 ONLINE  YES

     

    7 rows selected.

     

    On the destination platform database:

     

    SQL> select file#,STATUS, FUZZY from v$datafile_header where FUZZY='YES';

     

    no rows selected

     

    SQL> alter database open resetlogs;

    alter database open resetlogs

    *

    ERROR at line 1:

    ORA-01092: ORACLE instance terminated. Disconnection forced

    ORA-00704: bootstrap process failure

    ORA-39700: database must be opened with UPGRADE option

    Process ID: 3955

    Session ID: 254 Serial number: 1

     

    SQL> recover database using backup controlfile until cancel;

    ERROR:

    ORA-03114: not connected to ORACLE

  • 5. Re: Database migration from NON ASM to ASM
    TSharma-Oracle Guru
    Currently Being Moderated

    TRY THIS:

    alter database open resetlogs upgrade;


    Also, check your source and destination database are same at version and patch level.

  • 6. Re: Database migration from NON ASM to ASM
    993806 Newbie
    Currently Being Moderated

    I just did before your last update sent, error as below:

     

    SQL> alter database open resetlogs upgrade;

    ERROR:

    ORA-03114: not connected to ORACLE

  • 7. Re: Database migration from NON ASM to ASM
    TSharma-Oracle Guru
    Currently Being Moderated

    Because you are disconnected. mount the database again and run the exact above command. make sure you use 'upgrade' clause in the end.

     

    Also, check your patchset level for both source and destination. if  you are trying to restore using higher patchset level, you can use the following doc.

     

    Restoring a database to a higher patchset (Doc ID 558408.1)

  • 8. Re: Database migration from NON ASM to ASM
    993806 Newbie
    Currently Being Moderated

    Why it says incomplete recovery since the source database was in open read only!

     

    SQL> startup mount pfile='/home/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_xfwbkp.ora';

    ORACLE instance started.

     

    Total System Global Area 2.6924E+10 bytes

    Fixed Size            2241104 bytes

    Variable Size         1.3086E+10 bytes

    Database Buffers     1.3824E+10 bytes

    Redo Buffers           11227136 bytes

    Database mounted.

    SQL> alter database open resetlogs upgrade;

    alter database open resetlogs upgrade

    *

    ERROR at line 1:

    ORA-01139: RESETLOGS option only valid after an incomplete database recovery

  • 9. Re: Database migration from NON ASM to ASM
    TSharma-Oracle Guru
    Currently Being Moderated

    Run this on your source database and paste the output

     

    SELECT tablespace_name, status

    FROM dba_tablespaces;

    SYSTEM tablespace can never be made read only because it contains active rollback segments.

  • 10. Re: Database migration from NON ASM to ASM
    993806 Newbie
    Currently Being Moderated

    Please note that the database is running in open read write since I done with the convert.

     

    SQL> SELECT tablespace_name, status FROM dba_tablespaces;

     

    TABLESPACE_NAME                STATUS

    ------------------------------ ---------

    SYSTEM                         ONLINE

    SYSAUX                         ONLINE

    UNDOTBS1                       ONLINE

    TEMP                           ONLINE

    USERS                          ONLINE

    TD_BIPLATFORM                  ONLINE

    TD_IAS_TEMP                    ONLINE

    TD_MDS                         ONLINE

     

    8 rows selected.

  • 11. Re: Database migration from NON ASM to ASM
    TSharma-Oracle Guru
    Currently Being Moderated

    Like I said, system tablespace cannot be in read only mode. So you need to recover. Did you try recovering?

     

    Also, when did you convert your database to read only? before or after RMAN backup?

  • 12. Re: Database migration from NON ASM to ASM
    993806 Newbie
    Currently Being Moderated

    The output of what I recently sent you was from the source database not the cross platform destination database which I want to open now.

     

    I thought you asked me on the source db! well, here is what I got from the destination db:

     

    SQL> SELECT tablespace_name, status FROM dba_tablespaces;

    SELECT tablespace_name, status FROM dba_tablespaces

                                        *

    ERROR at line 1:

    ORA-01219: database not open: queries allowed on fixed tables/views only

     

    Destination database in mount mode, and when I run recover database until cancel I got the error below:

    ORA-00283: recovery session canceled due to errors

    ORA-16433: The database must be opened in read/write mode.

  • 13. Re: Database migration from NON ASM to ASM
    TSharma-Oracle Guru
    Currently Being Moderated

    Right, I asked you to send the output from source database which you did right. I am saying did you try to recover the database using 'recover database' command.

     

    Also, you did not answer my below question

    Also, when did you convert your database to read only? before or after RMAN backup?

  • 14. Re: Database migration from NON ASM to ASM
    993806 Newbie
    Currently Being Moderated

    I sent you my update regarding the recovery in my previous update, here is the output again:

     

    when I run recover database until cancel I got the error below:

    ORA-00283: recovery session canceled due to errors

    ORA-16433: The database must be opened in read/write mode.

     

     

    The conversion was made after started database in read only mode. RMAN will not let you convert unless the db in read only mode.

     

    Thanks.

1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points