On May 8, 8:17*pm, "da...@smooth1.co.uk" <da...@smooth1.co.uk> wrote:
> On 8 May, 18:03, Pete <pete.dickson....@gmail.com> wrote:
>
>
>
>
>
> > Version: Informix Dynamic Server 2000 Version 9.21.UC5XF
> > OS: AIX 5.2
>
> > Scenario:
> > We are in the process of converting a system running on AIX 4.3.3 9026/
> > M80 to a 9133/55A running AIX 5.2.
>
> > I did a level 0 archive on the old server, then restored on the new
> > server. No errors/etc. Since we are running ER i did a "CDR STOP"
> > while the system was disconnected to the network. This "test" is just
> > to validate the archive/restore process. After doing the restore and
> > CDR STOP, I want to run oncheck -cDI on all databases/tables. So far,
> > I've had to drop a bunch of indexes and recreate them before I can
> > more forward. After I clean up one index, it gets "stuck" on a
> > different one. There are no errors in the informix log, and no errors
> > on the system. It just "hangs". Also notice that there are no
> > checkpoints like usual. I expect checkpoints to be much lower, but not
> > non-existent.
>
> > Has anybody run into this before? It's driving me nuts.
>
> > And yes, we are in the process of preparing to upgrade to version 10,
> > and part of the upgrade process is to run onchecks on all of the
> > tables. This makes me nervous since it during the upgrade the oncheck
> > command "hangs" we'll be hosed.
>
> > Any output that would be benefitial to somebody to look at to see what
> > could be incorrectly set/etc?
>
> > Pete
>
> Well get onstat -g stk all output and open a support case with IBM...- Hide quoted text -
>
> - Show quoted text -

A support case with IBM... yeah, right.... notice the version...that's
why I posted here because IBM won't help. We "are" in the process of
upgrading, just not yet. Not our reason, our 3rd party vendor hasn't
"got around" to upgrading us, they "technically" are our Informix
contact/1st level support. Long story that I can't really get into for
obvious reasons.... I finally got ONE clean run after dropping and
rebuilding indexes for 3 tables that got "hung". So at this point
oncheck is not getting stuck. What a nightmare.