DBUTIL
 >DETACH IMAGE-BASE

Keven

Emerson, Tom wrote:
> One of our databases needed a structural change -- no problem, run adager to build a jobstream and schedule it after the backup, should be simple, right?
> 
> turns out adager aborted with a message along the lines of:
> 
>    according to the turboconnect file, your database is attached to
> 
>          dbe.sql.testacct
>          dbe.sql.prodacct
> 
>    I can only do capacity management and reporting [paraphrased] if the database is attached to more than one DBE
> 
> Again the immediate thought was "no problem -- the TEST dbe isn't needed for production (especially since it resides on a different box)", however when firing up imagesql to detach the offending dbe, I've run into a snag -- the "testacct" doesn't physically exist on the system, so I cannot "specify the DBE" to issue a "detach" command.
> 
> I seem to recall that this database was built and populated with initial data on the test system, and when all was verified as "OK", moved (via dcsopy or mpex copy) to the production system -- completely ignoring (or forgetting/not realizing) that the ...TC file went along for the ride.
> 
> So, how do I go about removing the offending "attachment"?
>