Home » RDBMS Server » Backup & Recovery » RMAN Connect nocatalog in Legato
RMAN Connect nocatalog in Legato [message #277208] Mon, 29 October 2007 04:21 Go to next message
mwansalovewell
Messages: 71
Registered: October 2007
Location: uk
Member
How do you specify connect nocatalog in oracle 8.1.7 and NMO v4.1

Run the following RMAN SCRIPT

---
connect target sys/orac1@db1 nocatalog
run {
allocate channel t1 type 'SBT_TAPE'
parms 'ENV=(NSR_SERVER=dbserver1.com, NSR_DATA_VOLUME_POOL=Default)';
backup current controlfile;
release channel t1;
}
---

also tried

connect nocatalog target sys/orac1@db1
..


But keep getting an error from Legator when running the job


NOCATALOG -- is a bad command

How do i specify in RMAN script for legator to connect with nocatalog? help will be appreciated
Re: RMAN Connect nocatalog in Legato [message #277235 is a reply to message #277208] Mon, 29 October 2007 05:19 Go to previous messageGo to next message
Michel Cadot
Messages: 64107
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Remove nocatalog.
If you don't connect to a catalog, you are in nocatalog mode.

Regards
Michel
Re: RMAN Connect nocatalog in Legato [message #277240 is a reply to message #277235] Mon, 29 October 2007 05:25 Go to previous messageGo to next message
mwansalovewell
Messages: 71
Registered: October 2007
Location: uk
Member
Thats what i tried at first not putting the nocatalog

But Legato came back with an error saying you are not connected to a catalog.

On the command line when testing

C:\> rman

if you start RMAN

RMAN>connect target sys/oradb1@db1

and then run the backup commands you get an error,

but if you run

c:\> rman nocatalog
RMAN>connect target sys/oradb1@db1

Then run the backup commands, you successfully use NMO to backup to tape





I tried removing the nocatalog
Re: RMAN Connect nocatalog in Legato [message #277258 is a reply to message #277240] Mon, 29 October 2007 05:54 Go to previous messageGo to next message
Michel Cadot
Messages: 64107
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
So you have your solution, if I understand you: rman nocatalog then connect target.

Regards
Michel

[Updated on: Mon, 29 October 2007 05:54]

Report message to a moderator

Re: RMAN Connect nocatalog in Legato [message #277269 is a reply to message #277258] Mon, 29 October 2007 06:28 Go to previous messageGo to next message
mwansalovewell
Messages: 71
Registered: October 2007
Location: uk
Member
No i did not have a solution. That was just a test on the command line.

How do i put that in a script so Legato can execute the job.

When i add that line in the script

rman nocatalog
connect target sys/oracldb@db1
run {
..
.
}

I get an error from Legato job,

-- C:\>rman nocatalog

Is not a recognised command or batch command.

So how will i include the connections to rman with NOCATALOG in the script.
Re: RMAN Connect nocatalog in Legato [message #277278 is a reply to message #277269] Mon, 29 October 2007 06:43 Go to previous messageGo to next message
Michel Cadot
Messages: 64107
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
As you don't post exactly what you did and what is the error we can't help and where it comes from.

Regards
Michel
Re: RMAN Connect nocatalog in Legato [message #277324 is a reply to message #277278] Mon, 29 October 2007 10:16 Go to previous messageGo to next message
mwansalovewell
Messages: 71
Registered: October 2007
Location: uk
Member
I do not have the details of the errors, i was working on site of a client trying to schedule orcle rman backups using legato 7.3.2.

we were using Networker Module for Oracle NMO 4.2.

- You run the rman script from savesets on the Legato Server.
when you submit the job on Legato, it executes the rman commands in the script. Oracle 9i was connecting ok without the nocatalog command, you simply put the connection is the script as

connect target sys/oracledb@dbi

it connects with the no catalog default, but the same in 8i is failing to connect ( it needs you to specify the nocatalog in the connection, and this is where my problem is. The error i was getting is the nocatalog part like i explained before)


- You provide environment parameters using nsrmon.bat file
- you write the rman script on the windows database server which legato executes as part of the rman backups.

So the error you want to know is all about the nocatalog connection. All the jobs for 9i were executed ok using the same commands in the script. I hope this points to where my problem is.






Re: RMAN Connect nocatalog in Legato [message #277325 is a reply to message #277324] Mon, 29 October 2007 10:27 Go to previous messageGo to next message
Michel Cadot
Messages: 64107
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
I still don't know where "rman" command is launched and why you can't put "rman nocatalog" instead of just "rman".

Regards
Michel
Re: RMAN Connect nocatalog in Legato [message #277514 is a reply to message #277325] Tue, 30 October 2007 07:18 Go to previous message
mwansalovewell
Messages: 71
Registered: October 2007
Location: uk
Member
The errors:

--- from the msglog file ( configured in nsrnmo.bat )-------

Recovery Manager: Release 8.1.7.4.1 - Production



RMAN> CONNECT ***********************************************
RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-00558: error encountered while parsing input commands

RMAN-01005: syntax error: found "nocatalog": expecting one of: "newline, ;"

RMAN-01007: at line 1 column 46 file: d:\oracle\rman\scripts/nmosb000003


---- From Legator Server log ---------
savegrp: suppressed 1 lines of verbose output
check daemon.log for details.

C:\>nsrnmostart -s bplbackup -g TEST -LL -m bpl_trackwise -l full -q -W 78 -N "d:\oracle\rman\scripts\prod1.rman" "d:\oracle\rman\scripts\twprod2.rman"

RMAN script execution is not successful. RMAN exited with return code '3'.

C:\>REM

C:\>REM Cleanup from the command

C:\>REM

C:\>ENDLOCAL

--------
Previous Topic: Rman cloning - different node
Next Topic: Unable to perform media recovery
Goto Forum:
  


Current Time: Mon Dec 05 04:34:38 CST 2016

Total time taken to generate the page: 0.09271 seconds