Oninit cdi / Archive
Talk to an expert →

strange behaviour updating statsf or procedure

Posted in 2011

Summary

Karl Oliver reported that updating a procedure took 3 minutes on a DR system (11.50.FC6, HP-UX, ER-replicated, loaded by ontape) versus 2 seconds on the master, even after dropping and reloading it or restarting. Fernando Nunes asked about load, sysprocplan contention and dependent procedures; Karl found none and saw the same with another procedure. Fernando suggested a PMR. Unresolved.

Auto-generated by Claude from the posts below — may be imperfect; read the full thread.

Topics: High Availability & Replication, Backup & Restore, Platform-Specific Issues, Versions, Editions & End-of-Life

KARL OLIVER — — source: IIUG Forums & Mailing Lists

IBM Informix Dynamic Server Version 11.50.FC6 HP-UX wuasp132 B.11.23 U I have hit some strange behaviour while updating a procedure. We have two system replicated using enterprise replication. One is used as a dr system. On one system ( we will call it master) the update takes 2 secs on the other (we will call it dr) it takes 3 minutes ! The update ob our dr sysrem takes the 3 minutes. I have dropped the procedure and reloaed still takes the same time. I have restarted the instance still no difference Has anyone any ideas ? The instance is an exact copy of our master instance .Loaded with ontape

↪ replying to KARL OLIVER
Fernando — — source: IIUG Forums & Mailing Lists

Not really.... Is the procedure heavily used on the slow system? Are you having any kind of contention on the sysprocplan table? Is the procedure used by (many) other procedures? Regards. On Mon, Mar 28, 2011 at 10:52 PM, KARL OLIVER <karl.oliver@maf.govt.nz>wrote: > IBM Informix Dynamic Server Version 11.50.FC6 > HP-UX wuasp132 B.11.23 U > > I have hit some strange behaviour while updating a procedure. > We have two system replicated using enterprise replication. > One is used as a dr system. > On one system ( we will call it master) the update takes 2 secs on the > other > (we will call it dr) it takes 3 minutes ! > The update ob our dr sysrem takes the 3 minutes. > I have dropped the procedure and reloaed still takes the same time. > I have restarted the instance still no difference > Has anyone any ideas ? > The instance is an exact copy of our master instance .Loaded with ontape > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --001636d348662b204f049f92e7db

↪ replying to Fernando
KARL OLIVER — — source: IIUG Forums & Mailing Lists

Nothing is using this system i am preparing it for use - thats why it is so strange. Thes procs only about 100 lines. No ciontention,no locks

↪ replying to KARL OLIVER
KARL OLIVER — — source: IIUG Forums & Mailing Lists

tried on another procedure - same problem someting seriously wrong - may be PMR time

↪ replying to KARL OLIVER
Fernando — — source: IIUG Forums & Mailing Lists

I don't recall seeing anything similar. So yes, I think a PMR would be the way to go. Regards. On Tue, Mar 29, 2011 at 3:26 AM, KARL OLIVER <karl.oliver@maf.govt.nz>wrote: > tried on another procedure - same problem someting seriously wrong - may be > PMR time > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --0015174c4362046459049f9b80a1

Glossary