RMAN Delete Obsolete job fails due to Error Allocating Device

Experts, I need help, please.
This is 10.2.0.1 on Windows
RMAN> DELETE NOPROMPT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=130 devtype=DISK
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/15/2012 14:10:17
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
I ran RMAN> configure device type 'SBT_TAPE' clear;
but I still get the same error.
I backup to Disk, not tape
Notice the reference to SBT_TAPE:
RMAN configuration parameters are:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
What do I need to do to be able to run DELETE OBSOLETE; ?
Thanks, John

as anand mention ,you've to reset this parameter to default value.
and clear cmd with configure will remove it from configuration parameter
see below
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
*CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;*
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
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 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 '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/16/2012 12:04:34
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2
RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' clear;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
RMAN configuration parameters are successfully reset to default value
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 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 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 '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1591 instance=GG1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=1627 instance=GG1 devtype=DISK
no obsolete backups found

Similar Messages

The Job Failed Due to MAX-Time at ODS Activation Step

Hi
I'm getting these errors "The Job Failed Due to MAX-Time at ODS Activation Step" and
"Max-time Failure"
How to resolve this failure?

Hi ,
You can check the ODs activation logs in ODs batch montior >> click on taht job >>> job log
for this first you check in sm37 how many jobs are running if there are many otehr long running jobs then . the ODs activation will happen very slowly as the system is overloaded .. due to the long running jobs ..this causes the poor performance of system ..
for checking the performance of system .. you first check the lock waits in ST04..and check wether they are progressing or nt ..
check sm66 .. for the no of process running on system ..
check st22 >> for short dumps ..
check Os07> to check the cpu idle tiem if its less tehn 20% . then it means the cpu is overlaoded .
check sm21 ...
check the table space avilable in st04..
see if the system is overlaoded then the ODS wont get enough work process to create the backgorund jobs for that like(Bi_BCTL*)..jobs .the updation will happen but very slowly ..
in this case you can kill few long running jobs which are not important .. and kill few ODs activations also ..
Dont run 23 ODs activation all at a time .. run some of them at a time ..
And as for checking the key points for data loading is check st22,cehck job in R/3 , check sm58 for trfc,check sm59 for Rfc connections
Regards,
Shikha

Document control failed due to error in [DOCMGR-CANCEL] with a return code

i am getting this error while calceling the purchase order "Document control failed due to error in [DOCMGR-CANCEL] with a return code of [OTHER]. "
I am doing the calcel like this
Nav: buyer work centre --> order
searche the po and then
select order --> cancel then click GO button
i gave the Reason as Cancel
communication method: email
Cancel Requisition: Yes
Please help on this, its urgent.
Thanks,
Vijay.

Hi Vijay,
Check this MOS note.
Cancelling A Standard Purchase Order In Buyer Work Center Results In Error [Docmgr-Cancel] With A Return Code [ID 1338826.1]
Thanks
-Arif.

Adobe update process fails due to Error 130200. solutions please

adobe update process fails due to Error 130200. solutions please. Shyam

Is there anything else beside the number 130200?
Try downloading the update from http://www.adobe.com/downloads/updates/
If you still need help, please tell us your operating system details.

My ipad3 is at iOs 7, i'm trying to download update 7.0.2 I keep getting failed due to error like 9 times now. My mini, my two iphone 4s, no problems. What can I do about my ipad3?

ipad3 running iOs 7 trying to update to 7.0.2 keep tting failed due to error like 9 times. Updated iPad mini and 2 iPhone 4s, no problem.
Whats up? And what can I do to update?

Try and update with iTune (computer)

Document control failed due to error in [DOCMGR-CANCEL], return code = [OTH

Hi,
When i tried using the cancel PO API, it resulted in the following error.
Document control failed due to error in [DOCMGR-CANCEL], return code = [OTHER]
I searched the metalink and found out that it was a bug as p_doc_num variable was a number and in PO_HEADERS_ALL segment1 is VARCHAR2. But now the bug is fixed.
I tried both ways, with and without quotes but it is still giving this error. Please suggest.
I used the API in the following way.
DECLARE
l_return_status VARCHAR2(1);
BEGIN
fnd_global.apps_initialize(4480,20707,201);
--call the Cancel API
PO_Document_Control_PUB.control_document (
p_api_version=>1.0, -- p_api_version
p_init_msg_list=>FND_API.G_TRUE, -- p_init_msg_list
p_commit=>FND_API.G_TRUE, -- p_commit
x_return_status=>l_return_status,-- x_return_status
p_doc_type=>'PO', -- p_doc_type
p_doc_subtype=>'STANDARD', -- p_doc_subtype
p_doc_id=>34, -- p_doc_id
p_doc_num=>null, -- p_doc_num
p_release_id=>null, -- p_release_id
p_release_num=>null, -- p_release_num
p_doc_line_id=>null, -- p_doc_line_id
p_doc_line_num=>null, -- p_doc_line_num
p_doc_line_loc_id=>null, -- p_doc_line_loc_id
p_doc_shipment_num=>null, -- p_doc_shipment_num
p_action=>'CANCEL', -- p_action
p_action_date=>SYSDATE, -- p_action_date
p_cancel_reason=>null, -- p_cancel_reason
p_cancel_reqs_flag=>'N', -- p_cancel_reqs_flag
p_print_flag=>null, -- p_print_flag
p_note_to_vendor=>null ); -- p_note_to_vendor
commit;
-- Get any messages returned by the Cancel API
FOR i IN 1..FND_MSG_PUB.count_msg
LOOP
DBMS_OUTPUT.put_line(FND_MSG_PUB.Get(p_msg_index => i,
p_encoded => 'F'));
END LOOP;
END;
/

first you have to assign org_id to the program,like fnd_client_info.set_org_context('167');
you also have to initialize,like this
fnd_global.initialize(session_id => l_session_id
,user_id => 2613
,resp_id => 50459
,resp_appl_id => 201
,security_group_id => 0
,site_id => -1
,login_id => 1102144
, --can't be -1,or else will be wrong
conc_login_id => 1102144
,prog_appl_id => -1
,conc_program_id => -1
,conc_request_id => -1
,conc_priority_request => NULL);

OWS-05566: DAD TRY submission failed due to error 12514

Undocumended error:
OWS-05566: DAD TRY submission failed due to error 12514
ORA-12514: Message 12514 not found; product=RDBMS; facility=ORA
during DAD creation in OAS 4.0.7 with Oracle 8i on RH6
anybody has idea ?
Thanks in advance
Vartan
null

Undocumended error:
OWS-05566: DAD TRY submission failed due to error 12514
ORA-12514: Message 12514 not found; product=RDBMS; facility=ORA
during DAD creation in OAS 4.0.7 with Oracle 8i on RH6
anybody has idea ?
Thanks in advance
Vartan
null

LOGGING IN FAILED DUE TO ERROR

Computer will not let me log in because it gives a logging in failed due to error message.

Hello Alison,
If 10.7.0 or later...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
If that doesn't help Reinstall the OS.

Security update 2014-001 failed due to errors

I have attempted to load Security update 2014-001 on a 2009 MacPro running 10.8.5 (2x 2.8GHz Quad Xeons with 12GB of RAM and 1.2 GB of space on the OS disk) but it fails "due to errors". I have tried from the App update and directly from the Apple support site. I even reloaded the OS and still get a fail. Of course I suspect a compromise with this result but how do I fix it?

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Select
/var/log ▹ install.log
from the hierarchical list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar. Then select the messages from the last installation or update attempt, starting from the time when you initiated it. If you're not sure when that was, click the Clear Display button in the toolbar of the Console window and then try the installation again.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

"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

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

ORA-19554: error allocating device, device type: TAPE, device name: ORA-270

Hi everyone, hit errors below when doing rman duplicate database, anyone can assist?
database mounted
released channel: ORA_AUX_DISK_1
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=87 device type=DISK
released channel: ORA_AUX_DISK_1
restarting auxiliary database without server parameter file
Errors restarting database
RMAN-00600: internal error, arguments [6007] [] [] [] []
RMAN-03009: failure of allocate command on ORA_AUX_TAPE_1 channel at 03/14/2013 15:51:21
RMAN-10035: exception raised in RPC:
ORA-19624: operation failed, retry possible
ORA-19554: error allocating device, device type: TAPE, device name:
ORA-27001: unsupported device type
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 235
RMAN-10031: RPC Error: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.DEVICEALLOCATE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/14/2013 15:51:21
RMAN-05501: aborting duplication of target database
RMAN-03009: failure of allocate command on ORA_AUX_TAPE_1 channel at 03/14/2013 15:51:21
ORA-19554: error allocating device, device type: TAPE, device name:
ORA-27001: unsupported device type

Hi.
Tried but kenot...
This command will not work if if I execute in duplicate database?
I am now trying duplicate the database from a server to remote server.
using command below
DUPLICATE DATABASE TO NEW_DB_NAME
PFILE = PFILE_LOCATION
BACKUP LOCATION '/DUMP';
NOFILENAMECHECK;

APO jobs cancelled due to error- Time limit Exceed.

Dear All,
Three jobs are scheduled daily to transfer data from R/3 to APO,
These are cancelled due to error -"Time limit exceed".

Hi Pankaj,
There is a specific time allocated for each queue to clear and to get transferred across the system. the probable reasons are.
1. The queue itself is taking more than the allocated time to clear due to system load. Each queue requires specific free memory from server , in case of overload system is unable to allocate desired memory hence the error might appear.
2. If in a queue the very first entry is stuck due to x,y,z reason the queues following automatically go into "timeout" and then "system fail"
Proposed solution.
1. Analyze the first entry functionally. If Ok then ask the basis team to clear that particular entry.
2. after time out the queue will go to "SYSFAIL". Double clicking on this will reveal the reason. Based on the technical reason I can suggest the relevant OSS notes to be applied.
For detailed technical analysis check t-code CFG1.
Regards,
Ankur
Edited by: Ankur Shrivastava on Dec 19, 2007 5:58 AM

Deleting Indexes Job failing with ORA-01418

Hi,
While deleting the indexes to the Infocube the job is failing with an Error: ORA-01418. In SM37 it is throwing the message SQL-Error ORA-01418 specfied Index does not exist.
Checked in RSRV for the InfoCube it is showing red while we execute for the repair.
Please advice... right replies will be appreciated.
Regards,
DMK

For BW from 7.0 you can take a look to note 1003360.
Have you tried the autorepair from rsrv?

Extract sCSM server name Job failing due to sealed MP ?

The extract of the management server job is failing on the last extract of a CI sealed MP we created.
looking at the event viewer log I see this:
ETL Module Execution failed:
ETL process type: Extract
Batch ID: 36408
Module name: Extract_C3LOBCI_C3SCSMR2
Message: The given value of type String from the data source cannot be converted to type uniqueidentifier of the specified target column.
Stack:    at System.Data.SqlClient.SqlBulkCopy.ConvertValue(Object value, _SqlMetaData metadata, Boolean isNull, Boolean& isSqlType, Boolean& coercedToDataFeed)
   at System.Data.SqlClient.SqlBulkCopy.ReadWriteColumnValueAsync(Int32 col)
   at System.Data.SqlClient.SqlBulkCopy.CopyColumnsAsync(Int32 col, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.CopyRowsAsync(Int32 rowsSoFar, Int32 totalRows, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults, String updateBulkCommandText, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults, String updateBulkCommandText, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken)
   at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount, CancellationToken ctoken)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServer(IDataReader reader)
   at Microsoft.SystemCenter.Warehouse.Utility.SqlBulkOperation.Insert(String sourceConnStrg, String sourceQuery, String destinationTable, Dictionary`2 mapping, String sqlConnectionStrg, Boolean& readerHasRows, DomainUser sourceSecureUser,
DomainUser destSecureUser)
   at Microsoft.SystemCenter.Warehouse.Etl.ADOInterface.Insert(DomainUser sourceConnectionUser, DomainUser destinationConnectionUser)
   at Microsoft.SystemCenter.Warehouse.Etl.ADOInterface.Execute(IXPathNavigable config, Watermark wm, DomainUser sourceConnectionUser, DomainUser destinationConnectionUser)
   at Microsoft.SystemCenter.Warehouse.Etl.ExtractModule.Execute(IXPathNavigable config, Watermark wm, DomainUser sourceConnectionUser, DomainUser destinationConnectionUser, Int32 batchSize)
   at Microsoft.SystemCenter.Warehouse.Etl.ExtractModule.Execute(IXPathNavigable config, Watermark wm, DomainUser sourceConnectionUser, DomainUser destinationConnectionUser)
   at Microsoft.SystemCenter.Etl.ETLModule.OnDataItem(DataItemBase dataItem, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback completionCallback, Object completionState)
Management pack import failed.
Management pack ID: 417daf9b-9505-8824-4419-6c45925a1deb
Management pack name: C3LineofBusinessCI
Management pack version: 1.0.0.4
Data source name: DW_C3SCSMR2
Message: Verification failed with 4 errors:
Error 1:
Found error in 2|C3LineofBusinessCI|1.0.0.1|C3LineofBusinessCI|| with message:
Version 1.0.0.4 of the management pack is not upgrade compatible with older version 1.0.0.1. Compatibility check failed with 3 errors:
Error 2:
Found error in 1|C3LineofBusinessCI/a6ae647f076efa3a|1.0.0.0|C3LOBCI|| with message:
The property Type (C3SupportLocation) has a value that is not upgrade compatible. OldValue=enum, NewValue=string.
Error 3:
Found error in 1|C3LineofBusinessCI/a6ae647f076efa3a|1.0.0.0|C3LOBCI|| with message:
The property Key (C3Client) has a value that is not upgrade compatible. OldValue=True, NewValue=False.
Error 4:
Found error in 1|C3LineofBusinessCI/a6ae647f076efa3a|1.0.0.0|C3LOBCI|| with message:
New Key ClassProperty item (ClientID) has been added in the newer version of this management pack.
Stack trace:
    at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
   at Microsoft.EnterpriseManagement.Common.Internal.ManagementPackServiceProxy.ImportManagementPackWithResources(String managementPack, String keyToken, Dictionary`2 resources)
   at Microsoft.EnterpriseManagement.SystemCenter.Warehouse.Synchronization.Library.BaseManagementGroup.ImportManagementPack(ManagementPackObject mpObj)
any help would be appreciated thanks
David Ulrich

Version 1.0.0.4 of the management pack is not upgrade compatible with older version 1.0.0.1. Compatibility check failed with 3 errors:
The property Type (C3SupportLocation) has a value that is not upgrade compatible. OldValue=enum, NewValue=string.
The property Key (C3Client) has a value that is not upgrade compatible. OldValue=True, NewValue=False.
New Key ClassProperty item (ClientID) has been added in the newer version of this management pack.
you have ignored the error in the management server that your MP was not upgrade compatible, deleted the old version of the management pack form the management server, and imported the new version into the management server without waiting for the MPSync
job to run and clean up the datawarehouse. the DW server is seeing the new version in the management server and is trying to upgrade an MP with a non-upgrade compatible upgrade.
the normal resolution to this is to delete the MP from the Management server, run the MPSync job twice, verify the old version has been cleaned up from the DW server, and then re-import the new version. however, this isn't going to work for you, because
you are changing the primary key, and changing the type of a property, neither of which are EVER upgrade compatible.
if this is a lab or new system, then you can rebuild the Data Warehouse and associate it with the management server again from scratch. if this system is older, or is production, you will lose data doing this, so consider carefully.

RMAN Delete Obsolete job fails due to Error Allocating Device

Similar Messages

Maybe you are looking for