Re: media ID not unique in database (34)
Issue:- -------------------------------------------------------------------- Jan 26, 2021 3:16:28 PM Robot: TLD(7) on mdrbu1 Operation: Inventory and Update EMM Server: mbganbu1 ---------------...
Forum Discussion
Sridhart97 wrote:
Update failed: could not add new media ID 'CLN170' into slot 27
Insert media failed:
media ID not unique in database (34)=======================================================================
Findings:-
1.We have TLD6 & 7 robots same roboots we have media ID CLN170-179 cleaning taps loaded.
You cannot have same barcodes/labels in 2 libraries.
Media IDs need to be unique across the entire NBU domain.
Thanks for your reply.i my understanding also the same for CLN170-179 tapes in TLD6
But other rapes CLN160-169 are different robot TLD7 why this also showing error
But other rapes CLN160-169 are different robot TLD7 why this also showing error
We see that CLN170 is in TLD(6).
If you have removed the tape from TLD(6) and inserted into TLD(7), it means that you did not eject the tape through NBU or perfomed a logical 'move' afterwards.
According to NBU, CLN170 is still in TLD(6). You cannot add this tape to TLD(7) before you have updated NBU config for TLD(6).
TLD6 is located in Europe and TLD7 is located in Asia,
The issue what i noticed that smae media ID's CLN170-179 is insterted in both the TLD6&7, but CLN160-169 tapes are instered only in TLD7 why we are not able see and update the inventory in TLD7 ?
# /opt/openv/volmgr/bin/vmquery -m CLN170
================================================================================
media ID: CLN170
media type: 1/2" cleaning tape (13)
barcode: CLN170L1
media description: Cleaning Tape
volume pool: None (0)
robot type: TLD - Tape Library DLT (8)
robot number: 6
robot slot: 101
robot control host: mbganbu1
volume group: 000_00006_TLD
vault name: ---
vault sent date: ---
vault return date: ---
vault slot: ---
vault session id: ---
vault container id: -
created: 10 November 2020 13:05:32 UTC
assigned: ---
last mounted: ---
first mount: ---
expiration date: ---
cleanings left: 92
================================================================================
# /opt/openv/volmgr/bin/vmquery -m CLN163
Could not query by media ID CLN163: volume does not exist in database (35)
#Next step:-
CLN170-179 i will eject the tapes from TLD6 and update the inventory in TLD6 and later that will performTLD7 inventory will this work right and resolve the issue right...
You cannot have same media ID's CLN170-179 in both the TLD6&7.
The master server has ONE volume table for ALL media in the EMM database.
Not one volume table per robot or media server.So, although the robots are in different locations, NBU database cannot have duplicate media id's.
You need to have different tape labels for TLD6&7.
