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
#############################################################################

Similar Messages

  • CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT =SHOW DATE

    Hello everyone.
    The version I am using oracle 11g
    2 questions:
    1 .- CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ ora_backup / backupset /% F'; I get error
    I want the backup to show the date format, as it can get.
    2 .- CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ ora_backup / backupset /% F_.bak';
    rename the extension back to. Bak, one can view the SQL SERVER.
    Thanks,Bye.

    %F is only vaild for controlfile autobackups, there are other elements to store the date:
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsubcl010.htm#i82206
    Werner

  • CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT

    Hello everyone.
    The version I am using oracle 11g
    2 questions:
    1 .- CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ ora_backup / backupset /% F'; I get error
    I want the backup to show the date format, as it can get.
    2 .- CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ ora_backup / backupset /% F_.bak';
    rename the extension back to. Bak, one can view the SQL SERVER.
    Thanks,Bye.
    Edited by: rafelbunyol on 04-feb-2009 5:17
    Edited by: rafelbunyol on 04-feb-2009 5:19

    Hi,
    Probably you were not connected.
    Try:
    connect target /;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ora_backup/backupset/%F';
    My output on the last command:
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ora_backup/backupset/%F';
    new RMAN configuration parameters are successfully stored
    Regards,
    Tycho

  • RMAN-06466: error parsing configuration string (CONFIGURE DEVICE TYPE DISK

    Hi All
    Windows 2003 and 10.2.0.4
    I get the following message when executing show all; connected to rman
    (I have used grid control 11g for the first configuration of rman. Not sure if it has an impact.)
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of show command at 09/22/2011 16:04:11
    RMAN-12010: automatic channel allocation initialization failed
    RMAN-06466: error parsing configuration string (CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;)
    RMAN-01005: syntax error: found "backup": expecting one of: "clear, parallelism"
    RMAN-01007: at line 1 column 28 file: Configuration Row
    RMAN>
    Reading the manual Database Backup and Recovery Basics
    I should be able to configure it like this
    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "backup": expecting one of: ";"
    RMAN-01007: at line 1 column 42 file: standard input
    Anyone that can help me with this ?
    Appreciate your feedback.
    Thanks
    Magnus

    What happens if you type "CONFIGURE DEVICE TYPE DISK CLEAR;" ?

  • RMAN CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET;

    I configure this , How i can clear this ?
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET;

    I assume you would have tried
    CONFIGURE DEVICE TYPE DISK CLEAR;(as described in the documentation) before asking the question.
    What about this does not work for you?

  • ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK

    Why does the command
    "ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;"
    work when running RMAN interactively and not from a script??
    The error I get in the script is...
    18>      ALLOCATE CHANNEL FOR
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "for": expecting one of: "channel_id, double-quoted-string, identifier, single-quoted-string"
    RMAN-01007: at line 18 column 18 file: D:\oracle\ora92\hpcs\Rman_DeleteObsolete.rman
    How can I delete these obsolete backups from the script?

    FIXED IT.
    The ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK command had to be outside of the RMAN RUN BLOCK.
    All works 100% now.

  • Unable to allocate channel device type sbt

    Hi,
    This is my first post on this forum so please advice me if I do something stupid.
    This oracle instance is version: 11.2.0.1
    Running on RHEL 5.6
    So, my problem is that I can't allocate sbt channel/device to crosscheck archivelogs.
    We are using Symantec's Backup Exec to manage your backups, and by looking it's log's (attached below) this should work. What I'am missing?
    Command I'm trying to run:
    RMAN> allocate channel for maintenance device type stb;
    ORA-27211: Failed to load Media Management Library
    I have check't the libobk.so is link'd from $ORACLE_HOME/lib/libobk.so -> VRTSralus/bin/libobk.so.
    BE's log:
    RUN {
    ALLOCATE CHANNEL ch0
    TYPE 'SBT_TAPE';
    SEND '**************';
    BACKUP
    INCREMENTAL LEVEL=0
    FORMAT 'BE_U'
    DATABASE FORCE PLUS ARCHIVELOG FORCE NOT BACKED UP DELETE INPUT;
    BACKUP CURRENT CONTROLFILE
    FORMAT 'BE_U';
    RELEASE CHANNEL ch0;
    connected to target database: PROD
    using target database control file instead of recovery catalog
    allocated channel: ch0
    channel ch0: SID=3987 device type=SBT_TAPE
    channel ch0: Symantec/BackupExec/1.1.0
    sent command to channel: ch0
    Thanks for your help
    Kalle
    P.S. Moved from General questions to RMAN

    im not familiar with Symantec's Backup Exec, but i think you are missing the SEND part in your manual allocation (which is present in the backup log)
    You can specify media management parameters in RMAN backup and restore jobs by the following means:
        Environment variables, which are specified with the ENV parameter of the PARMS option on the CONFIGURE or ALLOCATE CHANNEL commands
        The RMAN SEND command

  • NCM - Configuration Audit - Device Types

    Hi All
    We are using NCM to audit configurations of various cisco devices on the network... We have basic config templates built, which would be compared to provide exceptions. Now, we know, each device has its own limitation , based on the device model/IOS etc.. With a base configuration, NCM throws large number of non-compliance reports for commands compared against..
    my question is - isnt NCM intelligent enough to compare the configurations based on the hardware, ios etc by itself ? Are there any patches/modules etc available for us to upload to NCM, to do this funcationality automatically ? Issue is we have thousands of devices and we are creating thousands of exceptions each day to get the non-compliance solved !
    eg - snmp-server enable trap ospf command is not available on some devices like 3550 (with IOS less than 12.2(25) SE). Now, we manually create a ruleset to exempt this from audit, but there are many rules like this which has to be checked against.
    As far as I know, its not possible, but just thought of giving a shout out !

    If I understand your example, you are trying to have the policy compliance skip over certain devices if they aren't at a certain IOS level. Is that correct? If so, the only way to accomplish this that I have ever seen is to create some dynamic groups and then apply your policies appropriately.
    For example, if you create a dynamic group that contains all Catalyst switches with 12.2(25) or higher and then tell your policy only to apply to that group that may work for you.
    At least, that's how I am doing that in the NCM deployment for the company I work for.
    Hope this helps and good luck!

  • "ORA-19554: error allocating device, device type: SBT_TAPE, device name: "

    Hi expert.
    why I can not delete obsolete?
    I have this error:
    "ORA-19554: error allocating device, device type: SBT_TAPE, device name: "
    but I haven't any tape. How I can remove this from my rman config?
    many thanks, as usual.
    cheers,
    Lain
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oraclesvi/TMP/backup_db_archive/cf_%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/oraclesvi/TMP/backup_db_archive/ora_df%t_s%s_s%p';
    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 '/opt/oracle/product/10.2.0/SvilTMP/dbs/snapcf_DBTMP.f'; # default
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Archive Log          1      28-MAY-10          /oraclesvi/TMP/flash_recovery_area/DBTMP/archivelog/2010_05_28/o1_mf_1_22_60086j50_.arc
    Archive Log          2      29-MAY-10          /oraclesvi/TMP/flash_recovery_area/DBTMP/archivelog/2010_05_29/o1_mf_1_23_6014bh9j_.arc
    Archive Log          3      30-MAY-10          /oraclesvi/TMP/flash_recovery_area/DBTMP/archivelog/2010_05_30/o1_mf_1_24_603o6gls_.arc
    RMAN> delete obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 06/14/2010 14:43:17
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 2

    Try
    CONFIGURE DEVICE TYPE 'SBT_TAPE' clear;
    Werner

  • Difference between RMAN Allocate channel and Configure Channel

    Hello Sir,
    It is a very small problem that the more I study about RMAN I get more confused that what is the difference between Allocate Channel and Configure Channel.
    The thing I understand is that first we allocate channel and then after we configure it for uses.
    Pl. anybody make me clear if it is wrong and please tell me the right theory.
    Thanks and regards

    Hi,
    As Already Aman and Hemant K Chitale .. described the difference..
    Let me put up one thing one thing Ahead... !!
    CONFIGURE CHANNEL takes the same options used to specify one-time options with the ALLOCATE CHANNEL command. You can configure generic channel settings for a device type, that is, a template that is used for any channels created based on configured settings for that device.
    Example :-
    Note that if you use CONFIGURE CHANNEL to specify generic channel settings for a device, any previous settings are discarded, even if the settings are not in conflict. For example, after the second CONFIGURE CHANNEL command, which specifies only the FORMAT for configured disk channels, the MAXPIECESIZE for the disk channel is returned to its default value:
    CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 2G;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT /tmp/%U;
    If you manually allocate a channel during a job, then RMAN disregards any configured channel settings. For example, assume that the default device type is SBT, and you execute the following command:
    RUN
    ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
    BACKUP TABLESPACE users;
    Ever thing is in ORACLE Documentation.. . (Pick out the things....)
    http://download-uk.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmconfb.htm
    Study or Go through Slow and Study... you can understnad ever thing...
    - Pavan Kumar N

  • RMAN Configure Channels vs Duplexed Backupsets

    What is the difference between "duplexed backupsets" where I create multiple copies of RMAN backups and "Configuring Specific Channels" where I set channels to backup to two separate disks?  I am using the duplexed backupset feature now to send 2 copies of the RMAN backups to 2 locations.  I was testing the configuration of specific channels but did not see where I waa getting 2 full copies, one on each channel.  For duplexed backupsets I configure:
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'disk1/backup_%d_%T_%U',   '/disk2/backup_%d_%T_%U' MAXPIECESIZE 4 G;;
    For channels I set:
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT   '/disk1/backup_%d_%T_%U' MAXPIECESIZE 4 G;
    CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT   '/disk2/backup_%d_%T_%U' MAXPIECESIZE 4 G;
    but I cannot tell if I am getting 2 backups on the 2 channels or id RMAN is just making one backup and splitting it up on the 2 channels.
    If I set the CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2 on the channels, then I get 2 backups to disk1 and none to disk2.
    What is the proper way to use channels to get 2 full copies of archivlog and database backups one copy on each channel?

    Hello,
    i have searched in metalink for a while and yes it is bug.
    It is described in metalinknote #6316373.8:
    Bug 6316373 - CROSSCHECK identifies some files as EXPIRED
    It is really new (from 20-AUG-2008) .. i applied the patch and now it is working fine :-))
    So everyone who has the same concept.. please apply this patch.
    Regards
    Stefan

  • Getting the error ORA-27001: unsupported device type

    Hi ,
    While I am starting to backup via RMAN I am getting the following error. I kept my backup files on my disk and configured the channel as
    RMAN> SHOW DEFAULT DEVICE TYPE;
    RMAN configuration parameters are:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    RMAN> restore tablespace user_undo;
    Starting restore at 19-DEC-06
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 12/19/2006 17:00:36
    ORA-19554: error allocating device, device type: DISC, device name:
    ORA-27001: unsupported device type
    When I checked in the v$backup_device its giving my the following result
    SQL> SELECT * FROM V$BACKUP_DEVICE;
    DEVICE_TYPE
    DEVICE_NAME
    SBT_TAPE
    Could anyone please help me out.
    Thanks

    RMAN> SHOW DEFAULT DEVICE TYPE;
    RMAN configuration parameters are:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    RMAN-03002: failure of restore command at 12/19/2006
    17:00:36
    ORA-19554: error allocating device, device type:
    DISC, device name:> ORA-27001: unsupported device type
    Is it possible that you have line similar to the following when you enter
    show all;
    CONFIGURE CHANNEL DEVICE TYPE DISC FORMAT <path>

  • RMAN / channels and device types

    Hello,
    I have a question.
    In the RMAN documentation (for instance in "Oracle Database Backup and Recovery Advanced User's Guide 10g Release 2") one can find the description / instructions how
    to allocate RMAN channels and define the device types.
    There are 2x described device types - DISK and SBT (Tape).
    My question is:
    IS IT POSSIBLE TO USE A PIPE AS A RMAN DEVICE TYPE ?
    If it is not possible to define direct, perhaps there is a possibility to define it
    indirect and to use a pipe to write data.
    Regards.
    Neitour

    Thank you for the link. Is it this RMAN 'duplicate database' option, what you
    would like to recommend me to use?
    I think, it is not exactly what I really need. For 'duplicate database' I will need
    to have as a source a backup of the database and not a running productive
    database.
    Is it correct?
    If it is, it is not what I'd like to do.
    I'd like to make a copy of a productive running database, which is placed on ASM
    storage, to another server creating such a way a database also placed on ASM
    storage. I'd like to do it directly. I think the best possible way can be
    RMAN / BACKUP --> PIPE --> RMAN / RESTORE.
    The issue is - how can I configure RMAN to write BACKUP into a PIPE and
    to read data for RESTORE from a PIPE.
    Any ideas?
    Regards
    Neitour

  • ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt

    what are the scenarios that we have to use the below statement.
    RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;

    first you have to understand why we allocate channel for rman..it crates a session to target database,To manually allocate a channel, which is a connection between RMAN and a database instance. Each connection initiates an Oracle server session on the target or auxiliary instance: this server session performs the work of backing up, restoring, or recovering backup sets and copies.
    Restrictions and Usage of this command
    Execute this command only at the RMAN prompt. This command cannot be used within a RUN block.
    The target instance must be started.
    Do not specify a channel ID.
    You cannot allocate a maintenance channel to a shared session.
    You cannot prefix ORA_ to a channel name. RMAN reserves channel names beginning with the ORA_ prefix for its own use.
    Manually allocated channels (maintenance or normal channels) and automatic channels based on configured settings are never mixed. To perform maintenance on both disk and SBT simultaneously using manually allocated maintenance channels, you must allocate both SBT and DISK channels explicitly.
    If you use ALLOCATE CHANNEL FOR MAINTENANCE, then RMAN uses the following convention for channel naming: ORA_MAINT_devicetype_n, where devicetype refers to DISK or sbt and n refers to the channel number. For example, RMAN uses these names for two manually allocated disk channels:
    ORA_MAINT_DISK_1
    ORA_MAINT_DISK_2
    You can allocate multiple maintenance channels for a single job, but you should only use this feature in these situations:
    o
    To allow crosschecking or deletion of all backup pieces or proxy copies, both on disk and tape, with a single command
    o
    To make crosschecking and deleting work correctly in an Oracle Real Application Clusters configuration in which each backup piece or proxy copy exists only on one node
    here is some example of this command you should check this..
    Deleting a Backup Set: Example This example deletes backup sets from tape created more than a week ago:
    ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
    DELETE NOPROMPT BACKUP OF DATABASE COMPLETED BEFORE 'SYSDATE-7';
    Crosschecking Archived Logs: Example This example crosschecks all archived logs on disk and tape. For disk, the preconfigured disk channel is used; for tape, an SBT channel is allocated manually. If the logs are not found, then RMAN marks them as EXPIRED in the repository:
    ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
    CROSSCHECK ARCHIVELOG ALL;
    Crosschecking on Multiple Nodes of an Oracle Real Application Clusters Configuration: Example In this example, you perform a crosscheck of backups on two nodes of an Oracle Real Application Clusters configuration, where each node has access to a subset of backups. It is assumed here that all backups are accessible by at least one of the two nodes used in the crosscheck. Any backups not accessible from at least one of the nodes are marked EXPIRED after the crosscheck.
    ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK CONNECT 'SYS/change_on_install@inst1';
    ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK CONNECT 'SYS/change_on_install@inst2';
    CROSSCHECK BACKUP;

  • Default device type configuration of controlfile autobackup ?

    1. configure controlfile autobackup format for device type disk to 'E:\oracle\oradata\oid\bk\%F';
    2. backup current controlfile;
    rman first use default device type ORA_DISK_1 and backup the file at "E:\ORACLE\ORA92\DATABASE\0AEU5OQL_1_1" (windows 2000)
    then backup file at "E:\ORACLE\ORADATA\OID\BK\C-804947643-20030807-00"
    when i backup database , rman can backup the controlfile at "E:\ORACLE\ORADATA\OID\BK\"
    when i backup controlfile manully , why rman first backup it at the default device ??
    thanks:)

    One more cogent point for auto backup on will always get automized backup whenever you made any physical structural change in yours database ,whenver you make any physical structural changes in yours database it goes to be highlight in control file,auto backup on will take this new highlighted control file backup at the spot,needn't to take control file backup after any structural changes It will be backed up itself in yours FRA (Flash recovery area).
    Khurram

Maybe you are looking for

  • ISE doesnt send Guest accounts via Email

    HI I have come across an issue in ISE1.1.2. once i create a guest account, and click on email, i get the below error i have patched version 1.1.2 to the latest patch 3 i have also configured teh sponsor portal customisation email address. ISE reports

  • Is there a TLOG? What's wrong?

    Hi, How can I find out if my application has a TLOG device configured. In the dmconfig I see that the parameter DMTLOGDEV is set. Often I see this following error in the ULOG - LIBGWT_CAT:1042: ERROR: Can't open domain log What could be going on? Wil

  • Business Area Filter in Document Journal

    Dear All, S_ALR_87012294- Compact Document Journal The above report can be processed for a particular User/ Document type etc , the client requires above report for a particular business area . How to resolve the issue, useful answers will be rewarde

  • Rotate image X degrees on WM5

    Hello, I'm creating a programs for a PPC running WM5. The program needs to be able to rotate an image X degrees. But until now I didn't find much that I can use. On a desktop you've got the Advanced graphics and awt.geom. But I can't seem to find any

  • Solution Manager vs Netweaver vs BASIS

    Hi Everybody. I have 5 year of experience with Java and J2EE Technologies and now my current company want me to join BASIS team. Is this the right move for me to go? My first question is where to start to learn BASIS. reading material  and so. Then w