> -----Original Message-----
> From: Miller,Keven [mailto:[log in to unmask]]
> 
> DBUTIL
>  >DETACH IMAGE-BASE

Bingo!!!

(though it seems like a shotgun approach rather than a sniper approach -- I gather this will delete ALL the DBE's associated with the database rather than one specific DBE)

should be easy enough to add to the job ahead of running adager to make the changes -- fortunately, we already have a specific re-attach script 

Technically, the DBA should have streamed our detach job, THEN this job, and then the re-attach job.  This *probably* would have worked since this would have removed the PRODUCTION DBE leaving only one DBE attached to the database.  though I'm unsure if adager would have choked on the fact the DBE and/or account doesn't exist, but then, that might have been a good thing if it failed on the attempt to reconnect -- we would effectively have what we needed: the removal of the bogus DBE


> Keven
> 
> Emerson, Tom wrote:
> > One of our databases needed a structural change [but]
> >    according to the turboconnect file, your database is attached to
> > 
> >          dbe.sql.testacct
> >          dbe.sql.prodacct

> >  [therefore adager] can only do capacity management and reporting 
> [paraphrased] if the database is attached to more than one DBE
[...]