2 Replies Latest reply: Dec 5, 2012 7:28 AM by Stephen Phillips RSS

    RMAN/ORA Error

    Stephen Phillips
      We are trying to copy another database to make our new production database, and we keep getting this memory error:
      $ rman TARGET sys@HR91CFG NOCATALOG AUXILIARY sys@HR91PRD
      
      Recovery Manager: Release 11.2.0.3.0 - Production on Wed Dec 5 04:43:19 2012
      
      Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
      
      target database Password: 
      connected to target database: HR91CFG (DBID=3420135695)
      using target database control file instead of recovery catalog
      auxiliary database Password: 
      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-00554: initialization of internal recovery manager package failed
      RMAN-04006: error from auxiliary database: ORA-04031: unable to allocate 32 bytes of shared memory ("shared pool","GV$INSTANCE","KGLS^c967c516","kglHeapInitialize:temp")
      ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 4205
      ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 8041
      ORA-06512: at line 1
      RMAN-04015: error setting target database character set to US7ASCII
      I think that we have plenty of memory free:
      $ free -m
                   total       used       free     shared    buffers     cached
      Mem:         64411      63838        573          0        328      51821
      -/+ buffers/cache:      11687      52723
      Swap:        66491        178      66313
      I thought that maybe it was because we had some orphan processes out there, but I can't anything:
      $ ps -ef | grep -i HR91PRD
      oracle    5176     1  0 Dec04 ?        00:00:04 ora_pmon_HR91PRD
      oracle    5178     1  0 Dec04 ?        00:00:03 ora_psp0_HR91PRD
      oracle    5181     1  1 Dec04 ?        00:08:00 ora_vktm_HR91PRD
      oracle    5185     1  0 Dec04 ?        00:00:00 ora_gen0_HR91PRD
      oracle    5188     1  0 Dec04 ?        00:00:01 ora_diag_HR91PRD
      oracle    5190     1  0 Dec04 ?        00:00:00 ora_dbrm_HR91PRD
      oracle    5192     1  0 Dec04 ?        00:01:01 ora_dia0_HR91PRD
      oracle    5194     1  0 Dec04 ?        00:00:00 ora_mman_HR91PRD
      oracle    5196     1  0 Dec04 ?        00:00:00 ora_dbw0_HR91PRD
      oracle    5198     1  0 Dec04 ?        00:00:00 ora_dbw1_HR91PRD
      oracle    5200     1  0 Dec04 ?        00:00:00 ora_dbw2_HR91PRD
      oracle    5202     1  0 Dec04 ?        00:00:00 ora_lgwr_HR91PRD
      oracle    5204     1  0 Dec04 ?        00:00:02 ora_ckpt_HR91PRD
      oracle    5206     1  0 Dec04 ?        00:00:00 ora_smon_HR91PRD
      oracle    5208     1  0 Dec04 ?        00:00:00 ora_reco_HR91PRD
      oracle    5210     1  0 Dec04 ?        00:00:02 ora_mmon_HR91PRD
      oracle    5212     1  0 Dec04 ?        00:00:16 ora_mmnl_HR91PRD
      19781     8971 11512  0 04:44 pts/0    00:00:00 grep -i HR91PRD
      $ sqlplus / as sysdba
      
      SQL*Plus: Release 11.2.0.3.0 Production on Wed Dec 5 04:44:53 2012
      
      Copyright (c) 1982, 2011, Oracle.  All rights reserved.
      
      
      Connected to:
      Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
      With the Partitioning, OLAP, Data Mining and Real Application Testing options
      
      SQL> shutdown;
      ORA-01507: database not mounted
      
      
      ORACLE instance shut down.
      SQL> exit
      Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
      With the Partitioning, OLAP, Data Mining and Real Application Testing options
      $ ps -ef | grep -i HR91PRD
      19781    10184 11512  0 04:45 pts/0    00:00:00 grep -i HR91PRD
      It's probably something simple, but I can't find it. Can anyone point anything out that I am missing?
        • 1. Re: RMAN/ORA Error
          Balazs Papp
          I think that we have plenty of memory free:
          $ free -m
          total       used       free     shared    buffers     cached
          Mem:         64411      63838        573          0        328      51821
          -/+ buffers/cache:      11687      52723
          Swap:        66491        178      66313
          doesnt mean anything if Oracle is not allowed to use it
          you didnt tell anything about your auxiliary instance
          with what memory parameters was it started?
          • 2. Re: RMAN/ORA Error
            Stephen Phillips
            I think that I figured it out. rman had created an spfile with errors in it. I needed to delete that:
            $ cd $ORACLE_HOME/dbs
            $ ls *HR91PRD*
            hc_HR91PRD.dat
            initHR91PRD.ora
            lkHR91PRD
            spfileHR91PRD.ora
            While the database was shutdown, I deleted the spfile:
            rm spfileHR91PRD.ora
            After that, I started the database back up in nomount mode, and rman logged in.
            $ rman TARGET sys@HR91CFG NOCATALOG AUXILIARY sys@HR91PRD
            
            Recovery Manager: Release 11.2.0.3.0 - Production on Wed Dec 5 04:59:04 2012
            
            Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
            
            target database Password: 
            connected to target database: HR91CFG (DBID=3420135695)
            using target database control file instead of recovery catalog
            auxiliary database Password: 
            connected to auxiliary database: HR91PRD (not mounted)
            
            RMAN> exit
            
            
            Recovery Manager complete.