You can run the backup from the NMC console without specifying these parameters in the scripts, usually these parameters are used to solve problems of execution.
You can use the following syntax sending backup from the NMC.
connect target usr/passwd@stringdatabase;
connect catalog usr/passwd@stringdbrman;
run
{
allocate channel c1 type 'SBT_TAPE';
backup archivelog all delete input;
release channel c1;
}
######
other scripts
run
{
allocate channel c1 type 'sbt_tape';
allocate channel c2 type 'sbt_tape';
send 'SBT_PARMS = (NSR_SERVER = nw.vlab.local)';
FULL BACKUP filesperset 1 FORMAT 'men_% d_% U' DATABASE INCLUDE CURRENT CONTROLFILE PLUS ARCHIVELOG;
elvinperez
87 Posts
1
May 5th, 2015 09:00
HI,
What is the problem ?
You can run the backup from the NMC console without specifying these parameters in the scripts, usually these parameters are used to solve problems of execution.
You can use the following syntax sending backup from the NMC.
connect target usr/passwd@stringdatabase;
connect catalog usr/passwd@stringdbrman;
run
{
allocate channel c1 type 'SBT_TAPE';
backup archivelog all delete input;
release channel c1;
}
######
other scripts
run
{
allocate channel c1 type 'sbt_tape';
allocate channel c2 type 'sbt_tape';
send 'SBT_PARMS = (NSR_SERVER = nw.vlab.local)';
FULL BACKUP filesperset 1 FORMAT 'men_% d_% U' DATABASE INCLUDE CURRENT CONTROLFILE PLUS ARCHIVELOG;
release channel c1;
release channel c2;
}
AlvaroG
97 Posts
1
May 5th, 2015 12:00
Use the wizard, it will ask all the information needed to construct an script.
Also in the Advanced Backup Options you can pass parameters to the script like NSR_DATA_VOLUME_POOL1