OraFAQ Forum: Backup & Recovery » OEM Run RMAN Script Failure- RMAN-06167: Already connected

Home » RDBMS Server » Backup & Recovery » OEM Run RMAN Script Failure- RMAN-06167: Already connected

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129218]

Fri, 22 July 2005 09:19

v9001715
Messages: 6
Registered: July 2005
Location: UK

Junior Member

RMAN Release 9.2.0.6.0 on Redhat Linux.
Run RMAN Script fails with RMAN-06167: Already connected, but creates the backup files as if succeeded. I have tried logging into RMAN and pointing at a different target before logging back out again then running the backup again. Same result. Any help would be greatly appreciated.

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129277 is a reply to message #129218]

Sat, 23 July 2005 01:19

girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)

Senior Member

Quote:

RMAN-06167 already connected

Cause: A CONNECT command was issued, but RMAN is already connected to the specified database.

Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.

Regds
Girish

[Updated on: Sat, 23 July 2005 01:19]

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129456 is a reply to message #129277]

Mon, 25 July 2005 06:02

v9001715
Messages: 6
Registered: July 2005
Location: UK

Junior Member

Yes this is the csurse of action suggested, however this doesn't solve it. In my initial posting I mentioned that this has been tried.

regards

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129458 is a reply to message #129456]

Mon, 25 July 2005 06:16

girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)

Senior Member

HI

Can you post the sequence of events that you are carrying out, on this forum?

I think the backup set that is getting created is for database that was initially connected & not for the database that you are intending to connect via this script that you are executing.

Probably the events that you are following are in this order (do correct me If I am interpreting it wrongly):

connect to target A

run script for backup of target B

Getting error 6167 & backupset as a result.

Here, at this point, pls do check the backup set. It should be of database A & not B.

Regds
Girish

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129480 is a reply to message #129458]

Mon, 25 July 2005 07:24

v9001715
Messages: 6
Registered: July 2005
Location: UK

Junior Member

Sure.

Connect to DB A within RMAN using -
rman target sys/****@A

Run backup job from OMS on (Intended on database B.

Files are backed up and error is given at the end of the backup

Job log indicates that database b is backed up, but the 6167 error is given.

regards,

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129486 is a reply to message #129480]

Mon, 25 July 2005 07:57

girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)

Senior Member

HI

In that case, if actual backup ultimately happens for intended database (database B in your case.. when initially connected to database A) thwn, you can ignore this error.. isn't it?

Regds
Girish

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129509 is a reply to message #129486]

Mon, 25 July 2005 08:59

v9001715
Messages: 6
Registered: July 2005
Location: UK

Junior Member

That is true but the whole reason for us doing backups from oms is so that we dont have to continually check the backups (we would be notified by emails instead). When the backup finishes, Im notified by email that the job has failed. This isnt really ideal. You'd think there would be more information available on the issue.

regards,

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129645 is a reply to message #129509]

Tue, 26 July 2005 02:21

girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)

Senior Member

HI

1 probable way, if allowable in scheme of your things, is to execute 2 different backup jobs for both databases A & B instead of 1 job taking backup of both databases A & B.

Regds
Girish

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129880 is a reply to message #129486]

Wed, 27 July 2005 02:51

v9001715
Messages: 6
Registered: July 2005
Location: UK

Junior Member

I guess Il log an iTAR. If nothing can be done then I guess it has to be acceptable.

Thanks for your help.
Regards

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129890 is a reply to message #129880]

Wed, 27 July 2005 03:37

girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)

Senior Member

Yes, In my opnion, you should.

Regds
Girish

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129903 is a reply to message #129218]

Wed, 27 July 2005 04:20

Scott Cowan
Messages: 15
Registered: February 2004

Junior Member

You can also get this message , if you've cloned your database and the copied version still has the same database id as the original. If this is the case then tread very carefully as your recovery catalog might start to develop some problems later on.

Report message to a moderator

Re: OEM Run RMAN Script Failure- RMAN-06167: Already connected [message #129906 is a reply to message #129903]

Wed, 27 July 2005 04:26

v9001715
Messages: 6
Registered: July 2005
Location: UK

Junior Member

No cloning has been done.

regards

Report message to a moderator

Previous Topic:	Exporting data from a Tablespace
Next Topic:	recover without restoring

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu May 07 14:57:56 CDT 2026