It's in DBUTIL : ENABLE AUTODEFER for <this_database>, IIRC.
But ....
I certainly would NOT, repeat NOT recommend that, for 1) it can lead to
serious performance issues, and 2) it's a HUGE, repeat HUGE risk of physical
integrity problems.
For instance, what do you think would happen if you have to abort a session
with a partially updated database, say, the pointers OK in the master but
the details not yet updated ?
Bottom line : unless you have really compelling reasons for doing so, and a
nice plan B in case of just about anything happening against the DB, you may
not want to disable XM against an Image DB.
HTH,
Christian
> -----Message d'origine-----
> De : HP-3000 Systems Discussion [mailto:[log in to unmask]] De la part
> de Kent Wallace
> Envoyé : jeudi 2 février 2006 15:47
> À : [log in to unmask]
> Objet : [HP3000-L] Transaction manager
>
> How do I turn the transaction manager off for a specific IMAGE database?
>
>
>
> Thanks
>
> Kent Wallace
>
>
>
>
>
>
>
>
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
