Sql statement on onstat -g ses command

The output below is from a onstat -g ses <id> command. Note that in the last line the there aren't the Current SQL statement and the Last parsed SQL statement. The output just shows "Changing data structure forced command termination." Does someone knows what this means? The select statement hadn't finished and it's running for hours. Thanks in advance, Dyrson Informix Dynamic Server w/ AD Version 8.21.UD1 -- On-Line -- Up 22:34:54 -- 831488 Kbytes local #RSAM total used sessid sessid user tty pid hostname threads memory memory 1.790 790 c_celsat - -1 cgrdes05 1 434176 340680 tid name rstcb flags curstk status 47880 sqlexec_ 24567110 ---P--- 2320 sleeping(secs: 1) Memory pools count 1 name class addr totalsize freesize #allocfrag #freefrag 790 V 255a0010 434176 93496 608 19 name free used name free used overhead 0 104 scb 80 128 opentable 0 8488 filetable 0 880 log 0 4192 temprec 0 1608 blob 0 192 ralloc 84128 268512 gentcb 0 8432 ostcb 0 2056 net 0 9080 sqscb 0 12368 sql 0 16432 rdahead 0 1592 sqlparser 4640 0 hashfiletab 0 280 osenv 0 1400 sqtcb 0 832 fragman 4648 1168 Sess SQL Current Iso Lock SQL ISAM F.E. Id Stmt type Database Lvl Mode ERR ERR Vers 1.790 SELECT cellsat_biw CR Not Wait 0 0 9.20 Current statement name : _ifxc000000000001o Changing data structure forced command termination. Sent via Deja.com http://www.deja.com/ Before you buy.

dyrson.alves@telemigcelular.com.br wrote: > The output below is from a onstat -g ses <id> command. > Note that in the last line the there aren't the > Current SQL statement and the Last parsed SQL statement. > The output just shows > "Changing data structure forced command termination." This can occur if Informix's Shared Memory is in the midst of a "change". It could also be related to incorrect shmmax settings. Check the release notes in $INFORMIXDIR/release... and get your Sys Admin. to adjust systems settings accordingly. Rudy

The situation only occurs with specific queries so I still in doubt. What if I set shmmax to x and informix needs more than x for a specific task? Thanks in advance. Dyrson In article <3948E1B7.4CCB7505@americasm01.nt.com>, Rudy Fernandes <rferdy@americasm01.nt.com> wrote: > > dyrson.alves@telemigcelular.com.br wrote: > > > The output below is from a onstat -g ses <id> command. > > Note that in the last line the there aren't the > > Current SQL statement and the Last parsed SQL statement. > > The output just shows > > "Changing data structure forced command termination." > > This can occur if Informix's Shared Memory is in the midst of a > "change". It could also be related to incorrect shmmax settings. Check > the release notes in $INFORMIXDIR/release... and get your Sys Admin. to > adjust systems settings accordingly. > > Rudy > > Sent via Deja.com http://www.deja.com/ Before you buy.

The situation only occurs with specific queries so I still in doubt. What if I set shmmax to x and informix needs more than x for a specific task? Thanks in advance. Dyrson In article <3948E1B7.4CCB7505@americasm01.nt.com>, Rudy Fernandes <rferdy@americasm01.nt.com> wrote: > > dyrson.alves@telemigcelular.com.br wrote: > > > The output below is from a onstat -g ses <id> command. > > Note that in the last line the there aren't the > > Current SQL statement and the Last parsed SQL statement. > > The output just shows > > "Changing data structure forced command termination." > > This can occur if Informix's Shared Memory is in the midst of a > "change". It could also be related to incorrect shmmax settings. Check > the release notes in $INFORMIXDIR/release... and get your Sys Admin. to > adjust systems settings accordingly. > > Rudy > > Sent via Deja.com http://www.deja.com/ Before you buy.

dyrson.alves@telemigcelular.com.br wrote: > The situation only occurs with specific queries so I still in doubt. > What if I set shmmax to x and informix needs more than x for a specific > task? Thanks in advance. The problem I'm referring to is related only to Resident Memory (main component is usually BUFFERS) fitting into a single segment. This is nothing to do with the Virtual Memory required by a query. You could reduce Resident size (use onmonitor to check the size) or increase shmmax (preferred option) and check if the problem goes away. Rudy > > Dyrson > > In article <3948E1B7.4CCB7505@americasm01.nt.com>, > Rudy Fernandes <rferdy@americasm01.nt.com> wrote: > > > > dyrson.alves@telemigcelular.com.br wrote: > > > > > The output below is from a onstat -g ses <id> command. > > > Note that in the last line the there aren't the > > > Current SQL statement and the Last parsed SQL statement. > > > The output just shows > > > "Changing data structure forced command termination." > >