Home » RDBMS Server » Backup & Recovery » Backing up Oracle 10g using RMAN & TDP (OS- 2008 x64)
Backing up Oracle 10g using RMAN & TDP [message #448636] Wed, 24 March 2010 07:37 Go to next message
N.joshi
Messages: 1
Registered: March 2010
Junior Member
hey all...
Im trying to take the backup of my ORACLE 10g server to the tape library through TDP 5.4.1 and when invoking RMAN with the command file using the following command

rman target XXXX/YYYY@orcl[/email] rcvcat xxx/yyy@rman[/email] cmdfile="filename" msglog="msg log"

and getting the following error in my msg log

RMAN-00554:initialization of intarnal recovery manager package
failed.
RMAN-04005:error from target database.
ORA-12154:TNS:couldnot resolve the connect identifier specified.

i have successfully taken the backup once but next time when i tried the command its getting me errors....

Please help me in this as im new to oracle....

Thanx

[Updated on: Wed, 24 March 2010 07:44]

Report message to a moderator

Re: Backing up Oracle 10g using RMAN & TDP [message #448651 is a reply to message #448636] Wed, 24 March 2010 08:37 Go to previous message
babuknb
Messages: 1734
Registered: December 2005
Location: NJ
Senior Member

Quote:
i have successfully taken the backup once but next time when i tried the command its getting me errors...


rman target XXXX/YYYY@orcl[/email] rcvcat xxx/yyy@rman[/email]


Then try to check your able to connect target database using the above command or not.

If not. Then


oerr ora 12154
12154, 00000, "TNS:could not resolve the connect identifier specified"
// *Cause:  A connection to a database or other service was requested using
// a connect identifier, and the connect identifier specified could not
// be resolved into a connect descriptor using one of the naming methods
// configured. For example, if the type of connect identifier used was a
// net service name then the net service name could not be found in a
// naming method repository, or the repository could not be
// located or reached.
// *Action:
//   - If you are using local naming (TNSNAMES.ORA file):
//      - Make sure that "TNSNAMES" is listed as one of the values of the
//        NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
//        (SQLNET.ORA)
//      - Verify that a TNSNAMES.ORA file exists and is in the proper
//        directory and is accessible.
//      - Check that the net service name used as the connect identifier
//        exists in the TNSNAMES.ORA file.
//      - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
//        file.  Look for unmatched parentheses or stray characters. Errors
//        in a TNSNAMES.ORA file may make it unusable.
//   - If you are using directory naming:
//      - Verify that "LDAP" is listed as one of the values of the
//        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
//        (SQLNET.ORA).
//      - Verify that the LDAP directory server is up and that it is
//        accessible.
//      - Verify that the net service name or database name used as the
//        connect identifier is configured in the directory.
//      - Verify that the default context being used is correct by
//        specifying a fully qualified net service name or a full LDAP DN
//        as the connect identifier
//   - If you are using easy connect naming:
//      - Verify that "EZCONNECT" is listed as one of the values of the
//        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
//        (SQLNET.ORA).
//      - Make sure the host, port and service name specified
//        are correct.
//      - Try enclosing the connect identifier in quote marks.
//
//   See the Oracle Net Services Administrators Guide or the Oracle
//   operating system specific guide for more information on naming.

-Babu
Previous Topic: How can we open the database when we do not have pfile, spfile, control file and backup.
Next Topic: hot backup mode question
Goto Forum:
  


Current Time: Sat Dec 03 18:04:43 CST 2016

Total time taken to generate the page: 0.22328 seconds