when dataset is migrated it is still accessible, but DB3 has no location. Or even worse a bad one like the SE where the file was initially created and then deleted.
Somehow in this case DBS2 was apparently falling back silently to PhEDEx.
Maybe even as simple as tell user to make sure they really want to use local DBS,
or enforce that only USER tier can be accessed in phys03 ?
when dataset is migrated it is still accessible, but DB3 has no location. Or even worse a bad one like the SE where the file was initially created and then deleted. Somehow in this case DBS2 was apparently falling back silently to PhEDEx.
Maybe even as simple as tell user to make sure they really want to use local DBS, or enforce that only USER tier can be accessed in phys03 ?