On 12/01/2011 1:38 PM, Jiang Wu wrote:
> We are running a SQLAnywhere 126.96.36.1996 engine on Windows as a service.
> Then from a separate machine, we do a "dbstop ..." trying to stop this
> database engine.
> 1 out of 4 times the dbstop cannot complete. The engine goes into 100%
> CPU state and dbstop does not return. The service status shows: "Stop
> pending" for the database engine. The system event log shows:
There are a number of operations the database server must perform once a
shut-down has been triggered - it is possible that these events are
taking a 'long time'.
To start, any open transactions for open connections will need to be
rolled back and the rollback log applied:
A checkpoint also needs to occur:
Do you have a console log (-z -o) from the time that the server is
taking a 'long time' (how long do you normally wait?) and what it's
actually doing once it has received a stop request?
> What we want to achieve is to swap the database file that is running on
> this engine. I.e. we prepared another database file with updated data.
> We want to stop the existing database and put the new database in. Is
> there another way to do this?
There are many ways to 'merge' new data; we would have to know more
about your business case to better understand your requirements and the
'best' way to achieve them.
Jeff Albion, Sybase iAnywhere, an SAP Company
iAnywhere Developer Community :
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
SQL Anywhere Patches and EBFs :
Report a Bug/Open a Case : http://case-express.sybase.com/cx/