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!

Similar Messages

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

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;" ?

"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

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

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

Solaris 10connectivity to EMC: failed to configure ANY device on FCA port

I'm connecting a E2900 server with a EMC symmetrix storage with fiber channel.
But I'm getting the following errors, and I'm not able to see the external disks. Any help is really appreciated.
bash-3.00# cfgadm -al
c3 fc-fabric connected unconfigured unknown
c3::5006048c52a5b746 unavailable connected unconfigured failed
c4 fc-fabric connected unconfigured unknown
c4::5006048c52a5b749 unavailable connected unconfigured failed
bash-3.00# cfgadm -c configure c3
cfgadm: Library error: report LUNs failed: 5006048c52a5b746
failed to configure ANY device on FCA port
bash-3.00# tail -f /var/adm/messages
Nov 27 16:42:12 cosemm1 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Nov 27 16:42:12 cosemm1 Unsupported LUN Addressing method 40 in response to REPORT_LUN
bash-3.00#
SO is Solaris 10 and I have installed recommended pathes:
118833-36 SunOS 5.10: Kernel patch
125100-10 SunOS 5.10: Kernel patch
120011-14 SunOS 5.10: Kernel patch
127111-01 SunOS 5.10: Kernel patch
119130-33 SunOS 5.10: Sun Fibre Channel Device Drivers (only necessary for Leadville Stack driver)
125184-04 SunOS 5.10: Sun Fibre Channel Device Drivers.
120222-21 SunOS 5.10: Emulex-Sun LightPulse fibre channel adapter driver v2.20k (only required for Emulex HBAs running Leadville)
125166-06 SunOS 5.10: Qlogic ISP fibre channel device driver v2.22 (only required for Qlogic HBAs running Leadville)
122640-05 SunOS 5.10: zfs genesis patch (require for zfs)
120473-12 SunOS 5.10: lib nss ldap PAM zfs patch (require for zfs)
119090-24 SunOS 5.10: iSCSI device driver and utilities
Also I have modified /etc/system adding those lines:
set ssd:ssd_max_throttle=20
forceload: drv/ssd
bash-3.00# modinfo |grep qlc
66 7ba7e000 ce1f8 282 1 qlc (SunFC Qlogic FCA v20070717-2.22)
bash-3.00# luxadm -e port
/devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
bash-3.00# luxadm qlgc
Found Path to 2 FC100/P, ISP2200, ISP23xx Devices
Opening Device: /devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl
Detected FCode Version: QLA2460 Host Adapter FCode(SPARC): 1.26 05/17/07
Opening Device: /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl
Detected FCode Version: QLA2460 Host Adapter FCode(SPARC): 1.26 05/17/07
Complete
bash-3.00# luxadm -e port
/devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
bash-3.00# luxadm -e dump_map /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:
devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 610f13 0 5006048c52a5b746 5006048c52a5b746 0x0 (Disk device)
1 617613 0 2100001b320122b7 2000001b320122b7 0x1f (Unknown Type,Host Bus Adapter)
bash-3.00# luxadm -e dump_map /devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:
devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 620f13 0 5006048c52a5b749 5006048c52a5b749 0x0 (Disk device)
1 627613 0 2100001b32014eb8 2000001b32014eb8 0x1f (Unknown Type,Host Bus Adapter)

Check the configuration on the EMC side. This error message is the heart of the problem:
"Unsupported LUN Addressing method 40 in response to REPORT_LUN"
A quick Googling leads me to believe this means you're trying to assign a LUN ID higher than 255 to the host.
Best of luck!

CiscoWorks user options "device type groups|switch and Hubs"

Hi,
We are using CiscoWorks software to deploy new configuration to our network devices. Because our environnement is mixed about version of network devices we have to create a new netconfig job for each device model, because in some plate-forme configuration option, syntax maybe different of each other.
When I create a new netconfig job with my username under "device type groups|switch and Hubs" I have a list there of all plate-forme we have in our production environnement managed by CiscoWorks software. I know thoses group was'nt define by on of us and thoses are define by default in CiscoWorks software, but they are hiden by default per user basic.
We have a new one in our team, I had created his user name and password, but I can find the option where I can asked to make visible to him plate-form device type group as I have in my user configuration.
Also, is it possible to copy private define group to an other user without to make thoses as public ?
Thanks a lot !

Here,
is a view of what I have with my user
but in his profile he is only see
Device type Groups
     + Routers
     + Switches and Hubs
     + Wireless
if he clic on the plus sing to develop group "Switches and Hubs" he see all switches and hub managed by CiscoWorks software. I know He did not create Cisco Catalyst 2912 XL Switch and Cisco Catalyst 2924 XL Switch group in my profile. I know we have to modify an option in CiscoWorks per user basic to view those group, the person who where that option should be modifiy is currently in vacation, but he will need that option enable before our specialist will be back !
Thanks a lot !

Device type to be used for Zebra 220XiIII Printer

Hello All,
We are printing labels from SAP to the printer Zebra 220XiIII Printer using Adobe Print forms technology. When configuring the printer, we used the device type as PDF1. The print was fine in terms of data display and positioning of the text and barcodes but the issue is that it takes 30secs. to print each label. This was not acceptable as it is creating delays in Shipment.
To address the issue we changed the device type to LZEB3. The print was fast i.e., in 20 seconds the printer was able to print 5 labels but the font on the label is increased automatically because of which the data on the label is truncated.
Does any one have any ideas on what is the device type to be used and is there any specific font to be used?
Please note that we desinged the forms using ADOBE FORMS TECHNOLOGY. There are many notes in Service market place which are specific to Smart forms. Please come up with your ideas.
Regards,
Praveen T

Hi Florian,
Thank you for your response. We were able to fix the issue by changing the Device type to LZEB2.
For some reason YZB200, YZB300 and other device types which we found in the device type wizard did not work in our case. We did not investigate the reason as LZEB2 worked and we have time crunch
Regards,
Praveen T

SPAD: Device type to be selected for 'HP Laser Jet P2055dn'

Hi,
Recently we were asked to configure 'HP Laser Jet P2055dn' as the cheque printer in our landscpe.
While configuring the printer, I have a doubt of the Device Type to be selected in SPAD settings.
Could you please suggest me which Device Type to be selected for this printer
Below are the details of the Printer provided o me by the infrastructure team:
HP Universal Printing PCL 5: 'HP Laser Jet P2055dn' with a Troy badge on it
Regards,
Manish Sharma

Hello,
Try using HP Laserjet 4 series PCL-5 driver for the printer you have mentioned.
Otherwise you can customize your own drivers with needed controls, formats, etc macthing the cheque printing.
Regards,
Yoganand.V

ORA-19554: error allocating device, device type: SBT_TAPE

Running HP DataProtector 6.0. Attempting to configure an Oracle 9i database for backup. Receive the following errors.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on DP_TEST channel at 07/08/2008 13:37:51
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Recovery Manager complete.
After extensive troubleshooting HP Support reports the following.
"Please contact Oracle and have them explain why RMAN refuses to load our library regardless of if the library is copied into the specific path or called from the softlink."
We tried to run the following without success.
RMAN> run {
allocate channel 'sch1' type 'sbt_tape' parms'ENV=(SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so)';
Thanks in advance for any help you can give,
Mark

Verify if the SHLIB_PATH environment variable includes the $ORACLE_HOME/lib path and verify the symbolic link between the libobk.so to the HP DP shared library file.
~ Madrid
http://hrivera99.blogspot.com

[Forum FAQ]How to troubleshoot common issue when configuring user device affinity from usage data

Symptom:
Some clients might fail to automatically configure user device affinity from usage data if you have manually configured user device affinity before.
When you check the UserAffinity.log, you can find the similar error messages as below:
User 'XXXXX\XXXXX' has xxxxx usage minutes UserAffinity
Setting auto affinity for user 'XXXXX\XXXXX'. UserAffinity
Found same state message existing. (was sent before) Skip sending same state message for user 'XXXXX\XXXXX'.. UserAffinity
Figure 1. Error Message in UserAffinity.log
Cause:
As the log said, there is a user affinity state message existing in WMI which prevents client from sending new user affinity state message.
Resolution:
We can delete the user affinity state message in WMI to force the client to resend the user affinity state message.
We can follow the steps below:
1. Run Windows Management Instrumentation Tester (“Wbemtest”).
2. In Windows Management Instrumentation Tester dialog box, click “Connect”.(Figure 2)
Figure 2.
3. Type “root\ccm\statemsg” under the Namespace table and then click “Connect”.(Figure 3)
Figure 3.
4. Click “Enum Classes”. (Figure 4)
Figure 4.
5. Choose “Recursive”
in Superclass Info dialog box.(Figure 5)
Figure 5.
6. Double-click “CCM_StateMsg” in Query Result dialog box.(Figure 6)
Figure 6.
7. Click “Instances”
in Object editor for CCM_StateMsg dialog box. (Figure 7)
Figure 7.
8. Choose the messages that contain "domain/user_Auto" and click “Delete” in the Query Result dialog box.(Figure 8)
Figure 8.
After you delete user affinity state message in WMI, the user affinity state message for the user will be resent. After a period time, we can check the UserAffinity.log to
see if the user affinity state message has been successfully sent. The related information would be similar as below:
Successfully sent user affinity state message for user 'xxxxx\xxxxx'.
Successfully created pending user affinity for user 'xxxxx\xxxxx' into WMI.
Figure 9.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I'm not sure whether this is the appropriate place to add this but - a (possible) cause that I have seen which is not mentioned above is a request for an AAAA record (IPv6 address)
being responded to with an A record (IPv4 address).
DNS debug logging (Windows 2008 R2 SP1) captured requests to
192.225.156.200 and the corresponding responses. In each case the response was followed in the debug log by the event “The DNS server encountered an invalid domain name
in a packet from 192.225.156.200. The packet will be rejected. The event data contains the DNS packet.”
The domain name in the response was the same as that in the query, and looks OK.
The logged query shows an AAAA record (IPv6 address) request and the logged response returned an A record (IPv4 address).
http://www.rfc-editor.org/rfc/rfc4074.txt “Common
Misbehavior Against DNS Queries for IPv6 Addresses” says, under “Expected Behavior”:
   Suppose that an authoritative server has an A RR but has no AAAA RR
   for a host name. Then, the server should return a response to a
   query for an AAAA RR of the name with the response code (RCODE) being
   0 (indicating no error) and with an empty answer section (see
   Sections 4.3.2 and 6.2.4 of [1]). Such a response indicates that
   there is at least one RR of a different type than AAAA for the
   queried name, and the stub resolver can then look for A RRs.

NCM - Configuration Audit - Device Types

Similar Messages

Maybe you are looking for