1 2 Previous Next 15 Replies Latest reply: Feb 25, 2013 9:31 AM by EdStevens RSS

    unable to connect rman from target databse to catalog database

    941949
      dear all,
      can u please help me in solving this problem?i will b very thankful to u.i configured rman with recovery catalog database.i m unable to connect catalog database from target database but **tnsping** is working fine on both systems.the error is shown below
      please help me in solving this problem


      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-00554: initialization of internal recovery manager package failed
      RMAN-04004: error from recovery catalog database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor



      i m unable to connect to catalog database using sql on target database,getting the error shown below

      ERROR:
      ORA-12514: TNS:listener does not currently know of service requested in connect
      descriptor
        • 1. Re: unable to connect rman from target databse to catalog database
          asahide
          Hi,

          Put your tnsping result, tnsnames.ora, listener.ora, lsnrctl status, lsnrctl services.
          Pls, use code tag..

          Regards,
          • 2. Re: unable to connect rman from target databse to catalog database
            Chanchal Wankhade
            Hi,

            This means your TNSNAME.ORA file does not have entry for the database that you are trying to connect OR your listern is not up and running.
            • 3. Re: unable to connect rman from target databse to catalog database
              damorgan
              And to this list the exact values you entered at the command line in your attempt to log into RMAN.

              For example:
              $ rman TARGET / CATALOG rman/cat@catdb
              • 4. Re: unable to connect rman from target databse to catalog database
                Mihael
                can u please help me in solving this problem?i will b very thankful to u.i configured rman with recovery catalog database.i m unable to connect catalog database from target database but **tnsping** is working fine on both systems.
                tnsping only checks that listener is running on specified host and port, and does not check any services that listener supports
                • 5. Re: unable to connect rman from target databse to catalog database
                  941949
                  hiii,
                  the listener status is as shown below
                  [oratest@localhost]$ lsnrctl status TEST

                  LSNRCTL for Linux: Version 10.2.0.3.0 - Production on 24-FEB-2013 08:57:06

                  Copyright (c) 1991, 2006, Oracle. All rights reserved.

                  Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROCTEST))
                  STATUS of the LISTENER
                  ------------------------
                  Alias TEST
                  Version TNSLSNR for Linux: Version 10.2.0.3.0 - Production
                  Start Date 21-FEB-2013 14:58:25
                  Uptime 2 days 17 hr. 58 min. 41 sec
                  Trace Level off
                  Security ON: Local OS Authentication
                  SNMP OFF
                  Listener Parameter File /opt/oracle/test/network/admin/TEST/listener.ora
                  Listener Log File /opt/oracle/test/network/admin/test.log
                  Listening Endpoints Summary...
                  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROCTEST)))
                  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.oracle.in)(PORT=1522)))
                  Services Summary...
                  Service "PLSExtProc" has 1 instance(s).
                  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
                  Service "TEST" has 2 instance(s).
                  Instance "TEST", status UNKNOWN, has 1 handler(s) for this service...
                  Instance "TEST", status READY, has 1 handler(s) for this service...
                  Service "TEST_XPT" has 1 instance(s).
                  Instance "TEST", status READY, has 1 handler(s) for this service...
                  The command completed successfully


                  the tnsping result is shown below:
                  -----------------------------------------------
                  ]$ tnsping orman

                  TNS Ping Utility for Linux: Version 10.2.0.3.0 - Production on 24-FEB-2013 08:54
                  Copyright (c) 1997, 2006, Oracle. All rights reserved.

                  Used parameter files:
                  /opt/oracle/test/network/admin/TEST/sqlnet_ifile.o

                  Used TNSNAMES adapter to resolve the alias
                  Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.2.121)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=ORMAN) (INSTANCE_NAME=ORMAN)))
                  OK (10 msec)


                  when trying to connect to rman get the error shown below:
                  ----------------------------------------------------------------------------------

                  ]$ rman target system/password@TEST catalog user_rman/user_rman@orman

                  Recovery Manager: Release 10.2.0.3.0 - Production on Sun Feb 24 08:55:51 2013

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

                  RMAN-00571: ===========================================================
                  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
                  RMAN-00571: ===========================================================
                  RMAN-00554: initialization of internal recovery manager package failed
                  RMAN-04005: error from target database:
                  ORA-01031: insufficient privileges

                  HOW TO SOLVE THIS ISSUE?YOUR HELP IS APPRECIATED.
                  • 6. Re: unable to connect rman from target databse to catalog database
                    941949
                    ANYBODY HERE TO HELP ME IN SOLVING THIS PROBLEM
                    • 7. Re: unable to connect rman from target databse to catalog database
                      992918
                      Hi,

                      Do one thing, do static listener configuration for your target listener and then put your target DB in correct mode (mount or Open) then try again.

                      below listener configuration might be helpful.

                      SID_LIST_LISTENER =
                      (SID_LIST =
                      (SID_DESC =
                      (GLOBAL_DBNAME = SID_name)
                      (ORACLE_HOME = /oracle_stdby/app/product/11.2.0)
                      (SID_NAME = SID_name)
                      )
                      )

                      LISTENER =
                      (DESCRIPTION_LIST =
                      (DESCRIPTION =
                      (ADDRESS = (PROTOCOL = TCP)(HOST = your_host)(PORT = 1521))
                      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
                      )
                      )

                      ADR_BASE_LISTENER = /oracle_stdby/app

                      Edited by: 989915 on Feb 24, 2013 12:14 AM
                      • 8. Re: unable to connect rman from target databse to catalog database
                        941949
                        listener is up and running,why i create new listener? my tnsping working on both target and catalog database but i m unable to connect rman using catalog db.
                        • 9. Re: unable to connect rman from target databse to catalog database
                          EdStevens
                          938946 wrote:
                          hiii,
                          the listener status is as shown below
                          [oratest@localhost]$ lsnrctl status TEST

                          LSNRCTL for Linux: Version 10.2.0.3.0 - Production on 24-FEB-2013 08:57:06

                          Copyright (c) 1991, 2006, Oracle. All rights reserved.

                          Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROCTEST))
                          STATUS of the LISTENER
                          ------------------------
                          Alias TEST
                          Version TNSLSNR for Linux: Version 10.2.0.3.0 - Production
                          Start Date 21-FEB-2013 14:58:25
                          Uptime 2 days 17 hr. 58 min. 41 sec
                          Trace Level off
                          Security ON: Local OS Authentication
                          SNMP OFF
                          Listener Parameter File /opt/oracle/test/network/admin/TEST/listener.ora
                          Listener Log File /opt/oracle/test/network/admin/test.log
                          Listening Endpoints Summary...
                          (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROCTEST)))
                          (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.oracle.in)(PORT=1522)))
                          Services Summary...
                          Service "PLSExtProc" has 1 instance(s).
                          Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
                          Service "TEST" has 2 instance(s).
                          Instance "TEST", status UNKNOWN, has 1 handler(s) for this service...
                          Instance "TEST", status READY, has 1 handler(s) for this service...
                          Service "TEST_XPT" has 1 instance(s).
                          Instance "TEST", status READY, has 1 handler(s) for this service...
                          The command completed successfully


                          the tnsping result is shown below:
                          -----------------------------------------------
                          ]$ tnsping orman

                          TNS Ping Utility for Linux: Version 10.2.0.3.0 - Production on 24-FEB-2013 08:54
                          Copyright (c) 1997, 2006, Oracle. All rights reserved.

                          Used parameter files:
                          /opt/oracle/test/network/admin/TEST/sqlnet_ifile.o

                          Used TNSNAMES adapter to resolve the alias
                          Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.2.121)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=ORMAN) (INSTANCE_NAME=ORMAN)))
                          OK (10 msec)


                          when trying to connect to rman get the error shown below:
                          ----------------------------------------------------------------------------------

                          ]$ rman target system/password@TEST catalog user_rman/user_rman@orman

                          Recovery Manager: Release 10.2.0.3.0 - Production on Sun Feb 24 08:55:51 2013

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

                          RMAN-00571: ===========================================================
                          RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
                          RMAN-00571: ===========================================================
                          RMAN-00554: initialization of internal recovery manager package failed
                          RMAN-04005: error from target database:
                          ORA-01031: insufficient privileges

                          HOW TO SOLVE THIS ISSUE?YOUR HELP IS APPRECIATED.
                          RMAN-04005: error from target database:

                          What do you get when you tnsping the target database?
                          What do you get when you try to connect to the target database with sqlplus?
                          • 10. Re: unable to connect rman from target databse to catalog database
                            Hemant K Chitale
                            target system/password@TEST
                            ORA-01031: insufficient privileges
                            An RMAN connection to the target must connect with the SYSDBA privilege.
                            When running RMAN from the same ORACLE_HOME (and ORACLE_SID) as the target database, you do not need to specify a connect-string but simply connect as
                            rman target / 
                            or
                            rman target / catalog user_rman/user_rman@orman
                            If you are connecting from a different ORACLE_HOME or choose to use the @TEST connect-string, you must connect as a user with the SYSDBA privilege. Normally, "SYSTEM" does not have the SYSDBA privilege. You need to connect as SYS AS SYSDBA or grant SYSDBA to an account and connect as that account.


                            Hemant K Chitale
                            • 11. Re: unable to connect rman from target databse to catalog database
                              941949
                              I CREATED PASSWORD FILE IN TARGET DATABASE(TEST) AS SHOWN BELOW
                              dbs]$orapwd file=orapwTEST password=system(password)

                              is my password file correct ? i gave password of system,is this correct ? or do i have to give password of sys?

                              and tnsping result and rman result while connecting

                              ]$tnsping orman
                              Used TNSNAMES adapter to resolve the alias
                              Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.2.100)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=ORMAN) (INSTANCE_NAME=ORMAN)))
                              OK (0 msec)
                              ]$ rman target / catalog user_rman/user_rman@orman

                              Recovery Manager: Release 10.2.0.3.0 - Production on Mon Feb 25 08:55:11 2013

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

                              connected to target database: TEST (DBID=2104560695)
                              RMAN-00571: ===========================================================
                              RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
                              RMAN-00571: ===========================================================
                              RMAN-00554: initialization of internal recovery manager package failed
                              RMAN-04004: error from recovery catalog database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
                              • 12. Re: unable to connect rman from target databse to catalog database
                                Hemant K Chitale
                                ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
                                That's a standard error if the server (the RMAN Catalog server in your case) listener hasn't yet registered the service. A TNSPING only proves that a listener is running not that you are able to connect to a database with that service name.
                                Verify your ORMAN database. Does it configure a different LOCAL_LISTENER in the instance pfile ? Login to ORMAN as SYSDBA and issue an ALTER SYSTEM REGISTER and then retry the TNS connection to ORMAN to see if it does register properly with the listener.


                                Hemant K Chitale
                                • 13. Re: unable to connect rman from target databse to catalog database
                                  941949
                                  I CREATED PASSWORD FILE IN TARGET DATABASE(TEST) AS SHOWN BELOW
                                  dbs]$orapwd file=orapwTEST password=system(password)

                                  is my password file correct ? i gave password of system,is this correct ? or do i have to give password of sys?
                                  • 14. Re: unable to connect rman from target databse to catalog database
                                    Hemant K Chitale
                                    You current issue is not the password or passwor file but the 12514 error from the lisetner you are attempting a connection to.


                                    Hemant K Chitale
                                    1 2 Previous Next