Agreed on the upgrade, but ... not my call.

On Wed, Feb 4, 2009 at 12:20 PM, Wally Terhune <[email protected]> wrote:

> published (entitled) tech tip:  (note that the enhanced message display at
> 6.0 is yet one more reason to upgrade from a version of UniData released in
> 2002. )
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>  Problem
>  Some commands in ECL and / or BASIC will prevent dbpause from
> initializing.
> Could we get a list
>  of these please?
>
>
>
>  Solution
>  If any UniData process in performing any of the following commands when
> dbpause is started, the
>  command will need to complete before dbpause can complete and fully pause
> the
> database.
>
>  ECL commands:
>  CREATE.FILE
>  DELETE.FILE
>  CLEAR.FILE
>  REBUILD.FILE
>  RESIZE (but not memresize)
>  ED
>  DELETE
>  MODIFY
>  CREATE.INDEX
>  BUILD.INDEX
>  CREATE.TRIGGER
>
>  UniBasic statements:
>  WRITE
>  DELETE
>  OSBWRITE
>  OSDELETE
>  WRITESEQ
>  WEOFSEQ
>  TRANSACTION COMMIT (for RFS or Journaling)
>
>  Also, starting with UniData 6.0, dbpause will provide additional
> information
> about the status
>  of the UniData process blocking it's completion. Previously, just the
> process
> id of the UniData
>  process was displayed.
>
>
>
>
>
>
>
>
>
>
> Wally Terhune
> U2 Support Architect
> IBM Information Management Software
> Tel: (303) 773-7969             T/L 656-7969
> Mobile: (303) 807-6222
> Email: [email protected]
> http://www.ibm.com/software/data/u2/support
>
>
>
>  From:       Kevin King <[email protected]>
>
>  To:         [email protected]
>
>  Date:       02/04/2009 12:07 PM
>
>  Subject:    [U2] dbpause: ... has one operation unfinished, please check
> it.
>
>  Sent by:    [email protected]
>
>
>
>
>
>
> Anyone seen this message (triggered by dbpause in a backup script on
> Unidata
> 5.2.30)?
>
> dbpause: udtno=61 (pid=60496) has one operation unfinished, please check
> it.
>
> This message repeats a bunch of times and then finally dbpause apparently
> gave up and proceeded on without pausing.  This system does not have
> RFS/TP.  Best we can tell, this was a normal telnet login that lost its tty
> (i.e. someone shut down the telnet client without logging off) but we
> couldn't get back to it via tandem, couldn't kill it via kill (with no
> options, -1, and -15) and eventually had to log it off with UniAdmin.
>
> Any idea what this means?
>
> -Kevin
> http://www.PrecisOnline.com
> -------
> u2-users mailing list
> [email protected]
> To unsubscribe please visit http://listserver.u2ug.org/
>
> [demime 1.01d removed an attachment of type image/gif which had a name of
> ecblank.gif]
>
> [demime 1.01d removed an attachment of type image/gif which had a name of
> graycol.gif]
> -------
> u2-users mailing list
> [email protected]
> To unsubscribe please visit http://listserver.u2ug.org/
>



-- 
-Kevin
http://www.PrecisOnline.com
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to