4 Replies Latest reply: Apr 22, 2013 10:06 AM by 1004503 RSS

    RMAN report schema returns errors

    1004503
      Hi there,
      some one there to get me a quicker answer to this; i connected to rman as a privileged OS DB user successfully and this time when i issued the report schema command it returned the below errors.i have run tnsping on my service and it has returned ok for all instances. am running RAC of 3 clusters.

      RMAN> report schema;

      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-03002: failure of report command at 04/22/2013 08:27:21
      RMAN-06403: could not obtain a fully authorized session
      ORA-01034: ORACLE not available
      ORA-27101: shared memory realm does not exist
      Linux-x86_64 Error: 2: No such file or directory
        • 1. Re: RMAN report schema returns errors
          1002948
          The database which you are trying to connect using rman is not opened. once check..
          • 2. Re: RMAN report schema returns errors
            1004503
            Thanks Rajesh;
            i have run the same command in RMAN again and it returned the same error, but the database is open and running as you can see below;
            i cant start an sql session successfully.
            RMAN> report schema;

            using target database control file instead of recovery catalog
            RMAN-00571: ===========================================================
            RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
            RMAN-00571: ===========================================================
            RMAN-03002: failure of report command at 04/22/2013 14:40:42
            RMAN-06403: could not obtain a fully authorized session
            ORA-01034: ORACLE not available
            ORA-27101: shared memory realm does not exist
            Linux-x86_64 Error: 2: No such file or directory

            RMAN> exit

            Recovery Manager complete.
            [oracle@billclnode2 ~]$ sqlplus utlxxx15/xxxxx80@utrod2

            SQL*Plus: Release 10.2.0.3.0 - Production on Mon Apr 22 14:41:20 2013

            Copyright (c) 1982, 2006, Oracle. All Rights Reserved.

            Connected to:
            Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
            With the Partitioning, Real Application Clusters, OLAP and Data Mining options

            SQL>
            • 3. Re: RMAN report schema returns errors
              EdStevens
              1001500 wrote:
              Thanks Rajesh;
              i have run the same command in RMAN again and it returned the same error, but the database is open and running as you can see below;
              i cant start an sql session successfully.
              RMAN> report schema;

              using target database control file instead of recovery catalog
              RMAN-00571: ===========================================================
              RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
              RMAN-00571: ===========================================================
              RMAN-03002: failure of report command at 04/22/2013 14:40:42
              RMAN-06403: could not obtain a fully authorized session
              ORA-01034: ORACLE not available
              ORA-27101: shared memory realm does not exist
              Linux-x86_64 Error: 2: No such file or directory

              RMAN> exit

              Recovery Manager complete.
              [oracle@billclnode2 ~]$ sqlplus utlxxx15/xxxxx80@utrod2

              SQL*Plus: Release 10.2.0.3.0 - Production on Mon Apr 22 14:41:20 2013

              Copyright (c) 1982, 2006, Oracle. All Rights Reserved.

              Connected to:
              Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
              With the Partitioning, Real Application Clusters, OLAP and Data Mining options

              SQL>
              Ok, so you proved there is a database you can connect to using sqlplus.
              Unfortunately, you have NOT proved that is the database you are expcting rman to connect to. Why not show us the full command you used to start rman, just like you did for sqlplus?
              • 4. Re: RMAN report schema returns errors
                1004503
                Thanks Guys,
                Edstevens,

                finally i understood it, i realized that i was running Rman on a secondary instance,(node2), and i wasnt realizing the error down that not started.

                [oracle@billclnode2 ~]$ $ORACLE_HOME/bin/rman target/

                Recovery Manager: Release 10.2.0.3.0 - Production on Mon Apr 22 16:59:17 2013

                Copyright (c) 1982, 2005, Oracle. All rights reserved.

                connected to target database (not started)

                RMAN>


                i have connected via the primary instance and every thing has worked out well.
                [oracle@billclnode1 bin]$ $ORACLE_HOME/bin/rman target/

                Recovery Manager: Release 10.2.0.3.0 - Production on Mon Apr 22 17:06:37 2013

                Copyright (c) 1982, 2005, Oracle. All rights reserved.

                connected to target database: UTLxxD (DBID=139999404074)

                RMAN> report schema;

                using target database control file instead of recovery catalog
                Report of database schema

                List of Permanent Datafiles
                ===========================
                File Size(MB) Tablespace RB segs Datafile Name
                ---- -------- -------------------- ------- ------------------------
                1 3848 SYSTEM *** +DG3_DATA/utxxod/datafile/system.265.658435511
                2 32767 UNDOTBS1 *** +DG3_DATA/utxxod/datafile/undotbs1.256.658435523
                3 5800 SYSAUX *** +DG3_DATA/utxxod/datafile/sysaux.267.658435525
                4 32767 UNDOTBS2 *** +DG3_DATA/utlxxrod/datafile/undotbs2.269.658435531
                5 5120 OPLN *** +DG3_DATA/opln2
                6 2048 USERS *** +DG3_DATA/utxxrod/datafile/users.271.658435537
                7 32767 PM_TDAT_001 *** +DG3_DATA/utxxrod/datafile/pm_tdat_001.312.662461623
                8 32767 ABL_TRANS_TBL1 *** +DG3_DATA/abl_trans_tbl_01
                9 1024 ZIPBILL *** +DG3_DATA/utxxrod/datafile/zipbill.274.702124539