RMAN parameters in 8.1.7

Hi,
how can I display all parameteres of RMAN in 8.1.7 version ?
Thanks.
I can not find it here :
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76990.pdf
Recovery Manager User’s Guide and Reference
Release 2 (8.1.6)
December 1999

Hi,
Are you asking about the all parameters.
you can use the SHOW ALL.
or my understanding with your question is wrong.
Sorry for Posting SHOW ALL, its Enhancements In Oracle9i
Check this link this might be use full
http://www.oracle-base.com/articles/8i/RecoveryManager8i.php
Thanks & Regards,
Pavan Kumar N
Message was edited by:
Pavan Kumar

Similar Messages

RMAN parameters - to use more CPU for Backup & Restore

Hi Friends,
I am using RMAN backup on 11g database on windows.
RMAN is taking almost 1 hr to restore the database and i could see the CPU usage is very less - less than 10% during restore.
so how can i make the RMAN backup and restore faster by using more CPU on windows.
Regards,
DB

839396 wrote:
Hi Friends,
I am using RMAN backup on 11g database on windows.
RMAN is taking almost 1 hr to restore the database and i could see the CPU usage is very less - less than 10% during restore.
so how can i make the RMAN backup and restore faster by using more CPU on windows.Where is your bottleneck? ... On Storage? If yes, your CPU available are useless during backup/restore operation.
Even better, check the wait events in your database and you'll know why the backup / restore is not as expected.
See this example:
http://levipereira.wordpress.com/2012/08/09/what-is-slow-rman-or-media-management-library/
Regards,
Levi Pereira

RMAN configuration parameters for Oracle8i

HELP - i'm migrating a production database from one server to another and need the current RMAN configuation parameters on the original database in order to migrate these same parameters to the target database. Could anyone ghelp me figuring out the RMAN configuation parameters including the defaults on the source orcale8i database?
Thanks

In ORACLE 8i, there are NO stored RMAN parameters (I believe, 9i was the first version to add this feature).
Instead, in ORACLE 8i you had to specify all channel parameters, formats etc in a run block ... So, the good news is, in ORACLE 8i these parameters should be already "hardcoded" in the RMAN scripts ... in other words, nothing to transfer on a database level ...

Rman backup scripts

Hi, I am inquiring as to how to create a job to run an rman script without using the Enterprise manager to schedule and create the job.
Thanks
James

You are going to want to at least set the following RMAN parameters. You may need to set other depending on your environment.
RETENTION POLICY
CONTROLFILE AUTOBACKUP ON
CONTROLFILE AUTOBACKUP FORMAT
PARALLELISM
CHANEL DEVICE TYP FORMAT
SNAPSHOT CONTROLFILE NAME
Below is an example of how I have these set on a test system. This from a 10g database
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/ecmtst/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 3 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup/ecmtst/%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/ecmtst/snapcf_ecmtst1.f';
RMAN>

How rman backup messages printed in alert file?

surprised how the messages of rman getting printed in alert file?
i am using 10.2.0.4 on AIX and using veritas net backups.....from rman.....
ORA-19624: operation failed, retry possible
ORA-19506: failed to create sequential file, name="c-1650503797-20091118-0c", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:

Raman wrote:
Well. i agree. we have logs to capture media backups....so wanted to cut only these media backups failure out of alert file...else what is happening here is our monitoring reports these as alerts as already we know from media backup logs...So why not modify your monitoring of the alert log to exclude that particular error?
Personally, I'd allow both systems to continue to report the error from their perspective.
>
in nutshell...just exploring any options to turn off the media backup failures like any rman parameters or can anything to do with veritas parameters?
Anyway thanks to all for your valuable opinions.
Thanks,
Raman.

OSB/RMAN to tape it's failed (hang)

We are trying to backup ODA RAC database to SL150 tape library, backup hangs with no errors. Oracle support was trying to solve the problem with no luck. any help please:
n summary:
OSB/RMAN to disk it's OK
OSB/RMAN to fake tape it's OK
OSB/filesystem to tape it's OK
OSB/RMAN to tape it's failed (hang)
we have checked permission devices, RMAN parameters all seems to be ok.

There's not enough information here to begin. Please supply full "obtool lsdev -lvg" output and also the full log files from the jobs.
Thanks
Rich

RMAN backup to a CATALOG on another Server

Hi All,
Our environment has a mixture of Oracle versions from 7.x, 8.1.x,9i and 10g. My question is I have setup RMAN on a new server running 10g R2. I need to be able to backup my older version databases to the RMAN server. My situation thus needs running the RMAN executable from the old servers to connect to the RMAN catalog server. Also keep in mind that there is no Active Directory which means that all servers are in different workgroups. Currently the Oracle Services are running under the Local System Account on each server.
I configured the necessary RMAN parameters on a test server running 10g and was successful in taking backups onto the new RMAN server.
I want to know the feasibility and long time concerns of using a local account with Admin rights and 'Log on as a Service' rights which will be having the same credentials on all the servers including the RMAN server and configure the OracleService on every server to run under its context.
Thanks in advance,

Hi All,
I have confirmed that this is possible. I had to take the initiative as no concerns came across my way. I have to check the restore too but then logically if RMAN can backup it should be able to RESTORE too. Thank you all.

RMAN RETENTION POLICY FOR ORACLE8I

Dear all,
How to config RETENTION POLICY for oracle8i(CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;), same 9i ?
Thanks for advance !
Chara

In ORACLE 8i, there are NO stored RMAN parameters (I believe, 9i was the first version to add this feature).
Instead, in ORACLE 8i you had to specify all channel parameters, formats etc in a run block ... So, the good news is, in ORACLE 8i these parameters should be already "hardcoded" in the RMAN scripts ... in other words, nothing to transfer on a database level ...

Comments on this style of scripting.

Hi,
This is my first rman shell script, still learning the ropes. Just looking for any commentary on the pro's cons of how I'm doing this. You'll notice instead of saving a job in RMAN with "create script" I've elected to leave the script in the backup file my self.. comments? ps: I'm not concerned about sharing these passwords, they are my dummy ones that are specifically never to be used in production...
Tasks remaining:
- removing passwords from the file [Or maybe not, if this script is chmod 700 it should be fine right?]
- adding more options regarding archive logs, cross checking, expirys and those good things
- I plan on 2 versions of this script. One for Sundays to do full backups, one for every other day to incremntals + archive logs.
#!/bin/ksh
export ORACLE_SID=orcl
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u00/app/oracle/product/11.2.0/dbhome_1/
export PATH=$PATH:${ORACLE_HOME}/bin
# Notes
# - page 282 of beginners book
# - create a recovery catalog VS. using control file.
# - show all is; handy. use it.
rman <<EOF
connect catalog rcat/rcat@orcl;
connect target sys/xoc65kej;
configure controlfile autobackup on;
configure retention policy to recovery window of 60 days;
run {
allocate channel c1 type disk;
backup
incremental level 0
format "/u00/app/oracle/flash_recovery_area/ORCL/backupset/b_t%t_s%s_p%p"
database plus archivelog;
exit;
EOF

I put the rman parameters in there more of a way of documenting them, but i guess Show all does the same. Perhaps I'll leave them there, but comment them out.
For backups, I just backup tomy flash recovery area, this is okay right?
I guess I could send my backups to a different spot, so that they don't fill up my flash recovery and cause my db to stop accepting connections just because of a large backup :)
Jeff.

CONFIGURE CHANNEL DEVICE TYPE DISK doesn't function

Dear all,
I have a problem with a backup.
Facts:
OS: SunOS hod 5.10 Generic_142901-03 i86pc i386 i86pc
Oracle 11.2.0.1 with RAC
So, Although i put in rman parameters section the CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rman/backups/%U'; the backup was done but in FRA that is located in
BS Key Type LV   Size       Device Type Elapsed Time Completion Time
36 Incr 0 210.82G DISK 10:32:57 24-JAN-13
BP Key: 36 Status: AVAILABLE Compressed: YES Tag: TAG20130123T210005
*Piece Name: +DATA/db_name/backupset/2013_01_23/nnndn0_tag20130123t210005_0.442.805496407*
List of Datafiles in backup set 36...
ANd my question is:
How, although i configure that the backups would be in /rman/backups/%U this was located in +DATA (fRA) ??
what im doing wrong ??
Thanks for your help.

thanks for your answer: here is my rman script. We invoked the script like this: rman_db_script.sh SID 0
#!/bin/ksh
function email_dba
if [ -s $email_file ]
then
subj="$prog: FAILED on $sid@$box at `date`"
while read dba_id
do
mailx -s "$subj" $dba_id < $email_file
echo "mailx -s "$subj" $dba_id "
done < /oracle/app/oracle/dba/util/motifylist.txt
fi
# set and check
function set_and_check
ps -ef | grep ora_pmon_$sid | grep -v grep > /dev/null
rc=$?
if [ $rc != 0 ]
then
echo "$prog: database $ORACLE_SID is not online" >> $log_file
echo "$prog: database $ORACLE_SID is not online" >> $email_file
# email_dba
exit 1
fi
rtime=`date '+%Y%m%d_%H%M'`
ORACLE_BASE=/opt/app/oracle
ORACLE_HOME=/opt/app/oracle/product/11.2.0/dbhome_1
export ORACLE_HOME
PATH=$ORACLE_HOME/bin:$PATH
export PATH
logdir=/opt/oracle/logs
log_file=$logdir/$prog.$sid.level${bk_level}.log.$rtime
email_file="$logdir/$prog.email.$sid"
cat /dev/null > $email_file
box=`hostname`
orauser=oracle
bk_dir=/rman/backups/$sid
echo "===== `date '+%Y%m%d %H:%M:%S'` $prog: Started =====" > $log_file
backup_type="INCREMENTAL LEVEL $bk_level"
# find $logdir -name $prog.*.log.* -type f -mtime +10 -exec /bin/rm -f {} \;
# find $bk_dir -name ctl.* -type f -mtime +10 -exec /bin/rm -f {} \;
echo "ORACLE_SID=$ORACLE_SID" >> $log_file
echo "ORACLE_USER=$orauser" >> $log_file
echo "ORACLE_HOME=$ORACLE_HOME" >> $log_file
echo "BACKUP TYPE=$backup_type" >> $log_file
return
# backup database and archive logs to disk
function backup_dbs_to_disk
echo "===== Backup $sid to FRA Started At `date` =====" >> $log_file
$ORACLE_HOME/bin/rman nocatalog << rman_cmd >> $log_file 2>&1
connect target
     # se haran en el directorio sgte no en el FRA
     CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rman/backups/%U';
#CONFIGURE CONTROLFILE AUTOBACKUP ON;
run
ALLOCATE CHANNEL ch1 TYPE disk ;
BACKUP $backup_type
filesperset 10
DATABASE;
sql 'alter system archive log current';
BACKUP filesperset 10 ARCHIVELOG ALL DELETE ALL INPUT;
sql "alter database backup controlfile to trace as ''$bk_dir/ctl.trc.$rtime''";
sql "alter database backup controlfile to ''$bk_dir/ctl.$rtime'' reuse";
RELEASE CHANNEL ch1;
#CONFIGURE CONTROLFILE AUTOBACKUP OFF;
rman_cmd
rc=$?
if [ $rc != 0 ]
then
echo "Backup $sid to Disk Failed At `date`" >> $log_file
echo "Backup $sid to Disk Failed At `date`" >> $email_file
email_dba
exit 1
else
echo "===== Backup $sid to Disk Completed At `date` =====" >> $log_file
fi
return
# delete obsolete backups
function del_obsolete_bk
echo "===== Delete Obsolete Backups Started At `date` =====" >> $log_file
$ORACLE_HOME/bin/rman nocatalog << rman_cmd >> $log_file 2>&1
connect target
ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;
Report obsolete;
delete force noprompt obsolete;
rman_cmd
rc=$?
if [ $rc != 0 ]
then
echo "Delete Obsolete Backups Failed At `date`" >> $log_file
echo "Delete Obsolete Backups Failed At `date`" >> $email_file
email_dba
exit 1
else
echo "===== Delete Obsolete Backups Completed At `date` =====" >> $log_file
fi
return
# main program
if [ $# -ne 2 ]
then
clear
echo "\nIncorrect argument, ORACLE_SID Backup_Level needed\n"
echo "\nUsage: $0 ORACLE_SID BACKUP_LEVEL(0/1)\n"
return 1
fi
sid=$1
bk_level=$2
diff_cum=$3
# prog=`basename $0`
prog=rman_backup_dbs.sh
export debug='N'
if [[ $debug = 'Y' ]];then set -x;fi
unset ORACLE_SID
unset ORACLE_HOME
unset SQLPATH
ORACLE_SID=$sid
export ORACLE_SID
set_and_check
backup_dbs_to_disk
del_obsolete_bk
echo "===== `date '+%Y%m%d %H:%M:%S'` $prog: Completed =====" >> $log_file
subj="$sid@$box backup completed successfully at `date`"
# while read dba_id
# do
# mailx -s "$subj" $dba_id < $log_file
# done < /oracle/app/oracle/dba/util/backup/scripts/email_dba.list
return 0
# end program
#############################################################################

ARCHIVELOG MODE --- Please assist

dear experts,
I have this doubt in my mind and would like you guys to advise on.
Is it true that when a database is in ARCHIVELOG MODE, database recovery using archived logs & hotbackup is possible to the last commit?
probably using the command: recover database using backup controlfile until cancel; (to apply all the arhive logs to last hotbackup)
From my point of view, i feel that the database recovery using the ARCHIVED LOGS and hotbackup is possible only up to the last redo log switch. In order to recover the database to the last commit, I have to recover the database using both the ARCHIVED LOGS as well as the last ACTIVE REDO LOG.
It is because the most recent commited transactions on the current redo log might not be written to archive log (as the active log is not full and no alter system switch logfile performed) at the point of time when the db crashed.
Please advise.
thanks all!

Also, by using RMAN you can approach more to the last commit with RMAN parameters like SCN, etc.
It's quite easy!

Scheduled backups with Enterprise Manager

Hi all,
I have shceduled a full backup with Entreprise Manager 10g. Previusly I went to Backup settings and I have specified the path. The test executed sucssesfully.
Then, once the backup was executed, it fails, but I can see any log from the Enterprise Manager on Backup Reports. Does somene know where I can find the backup logs?
Thanks in advance!
Víctor.

When u r using oracle EM to schedule the backup it is actually using RMAN at the backend so you should provide the location of the backup log file aswell, only then it will generate the log file.
The following are the command line RMAN parameters in which log is one of them,
target
catalog
nocatalog
cmdfile
LOG
trace
append
debug
msgno
send
pipe
timeout
checksyntax

Possible to parallel disk channels when using BrBackup?

Hi,
we are testing disk backup for our SAP landscape.
In RMAN it is possible to configure channels, when performing a disk backup.
Is it possible to define channels also within BrBackup?
Thanks for your help.
Best regards
Carlos

Hello
You could just configure Br*Tools to use Rman, you could even configure Rman parameters (such as channels) in the BR*Tools configuration file.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a8910c3a-0d01-0010-a6a9-f4a8aae140fe?overridelayout=t…
https://help.sap.com/saphelp_nw04/helpdata/en/3f/9d800e1aec11d2b42c00609419997a/content.htm
PS: you should post Oracle related question in the area dedicated to Oracle SAP on Oracle
Regards

RMAN scripts & variables/parameters

Hi
We are using RMAN with TSM. There are a number of 9i and 8i databases. I tried to set the environment up to with as few scripts as possible to cover the variety of databases. I provide various variables/parameters to handle the differences between the various databases.
In the 9i environment I "CONFIGURE" as much as possible to avoid setting changes in the actual backup script. That gives me a fairly clean generic backup script which also avoids manual channel allocations ie :
run
backup incremental level=0
not backed up since time='SYSDATE-(8/24)'
check logical
filesperset=4
format='/LVL0_%d_%T_%U'
(database include current controlfile)
plus archivelog format '/ARC_%d_%T_%U' delete all input;
However due to the lack of "CONFIGURE" in 8i I cannot configure automatic channels. Therefor my script has to change to :
run
allocate channel ch01 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
allocate channel ch02 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
allocate channel ch03 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
allocate channel ch04 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
backup incremental level=0
check logical
filesperset=4
format='/LVL0_%d_%T_%U'
(database include current controlfile)
(archivelog all format '/ARC_%d_%T_%U' delete input);
release channel ch01;
release channel ch02;
release channel ch03;
release channel ch04;
I have multiple database instances on the same server & would like to have a single generic script with a variable/parameter to change the "tdpo.opt" file for each instance. The alternate is to have a complete set of scripts for each DB instance with everything hard coded.
The question is : Can I pass variables/parameters to a RMAN script? If yes, how do I go about it?
Maybe there are other ideas out there to do this. The key to me in this whole execise is to reduce maintenance & increase flexibility.
Your responses will be appreciated
CM

I was hoping to get away from building part of the backup script ie the channel allocation in the RMAN statement.Don't know how you expect to do this when it's required for 8i databases ?
Well since you are looking to accommodate 8i & 9i database and you need to manually allocate channels for the 8i databases, then you could configure your script to include an IF..THEN block that will run one set of RUN commands if the database name that is passed in is in a certain list and run the other RUN block if it isn't. You could maintain two "here document" blocks, one for 8i and one for 9i. Therefore, all of the commands can reside in one generic script.
For example, you could configure your single, generic script as:
# add your logic checking here to see if a 9i database sid
# was passed in as a parameter. If so run the following code
rman target / log=${sid}bkp_log append << !1
run
backup incremental level=0
not backed up since time='SYSDATE-(8/24)'
check logical
filesperset=4
format='/LVL0_%d_%T_%U'
(database include current controlfile)
plus archivelog format '/ARC_%d_%T_%U' delete all input;
!1
# if not run the following (ie. 8i databases)
rman target / log=${sid}bkp_log append << !2
run
allocate channel ch01 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
allocate channel ch02 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
allocate channel ch03 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
allocate channel ch04 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo_${ORACLE_SID}.opt)';
backup incremental level=0
check logical
filesperset=4
format='/LVL0_%d_%T_%U'
(database include current controlfile)
(archivelog all format '/ARC_%d_%T_%U' delete input);
release channel ch01;
release channel ch02;
release channel ch03;
release channel ch04;
!2then you could call this generic script with the appropriate command line parameters.
Hope I'm following your explanation/requirement.

RMAN duplicate - instance parameters

Hello all.
I want to refresh the test environment with new production backup in oracle database 10g.
we have standby configured and its in sync with prod. So we took standby database latest backup and going to use to refresh the test environment.
prod is a 2 node rac and test is also a two node rac.
prod use different asm disk group and test uses different asm disk group.
so after taking backup, moved the backups to test environment.
Took backup of test spfile.
shut down the test both rac nodes after editing the parameter "cluster_database=false" parameter in spfile.
i am little confused about the the parameters to be removed and not to be removed in pfile to start the auxiliary instance.
we can remove parameters related to rac and these parameters also
cluster_database_instances=2
*.cluster_database=TRUE
kindly let me know
what value i can give for the parameters since the location is different in prod and test and how the duplicate command handle these parameter to duplicate the database
control_files
db_create_file_dest=
db_create_online_log_dest_1
db_create_online_log_dest_2
and i am going to use duplicate target database to <aux_db_name>
Regards

Pradeep,
Refresh rac database is not like refresh standalone database. You need to follow below steps
Step 1) Take the full backup of production database
            * Backup of database , controlfile and pfile to backup location
            * Comment the all rac related parameters and add change the control_files,db_file_name_convert,log_file_name_convert parameters as per test environment
            * scp all backupfiles to any of the server in test environment
Step 2)
            * connect to database which you want to refresh in test env
            * change the cluster_database=false (so that we can start the database exclusively for this instance only)
            * shutdown immediate and startup restrict nomount
            * drop dtabase
Step 3)
           * Remove the database information from ocr file
              srvctl remove database -d <db_name>
Step 4)
          * startup nomount pfile=<location>
          * connect to rman
               rman auxiliary /
          * use duplicate command to create a database
Step 5)
         * shutdown the database and make changes in pfile as remove all comments for all rac related parameters then create spfile from pfile
         * and startup database
         * use srvctl add database -d <db_name>
         * create second instance in second node also

RMAN parameters in 8.1.7

Similar Messages

Maybe you are looking for