D
Dmitri Levin
Guest
First of all I would like to say thank you to PSC for that parameter. It is a major step into making all schema changes online. We added a couple indexes online in Dev. All worked as expected. After about 3-4 months of using that parameter in dev we moved it to production yesterday. Unfortunately as we found out that parameter prevents disconnecting the users from the database. So proshut -C disconnect user does not work. It sets the flag for the user to disconnect, but the user does not disconnect from the database. Same in promon option 8/1. We have a script that disconnect users with active transactions over 30 minutes that works well for us over 10 years. Yesterday we had users running transactions over 5-6 hours. As a result our .bi file start growing ... 5 GB, 10 GB, 12 GB fortunately I allocated 20 GB and have an other 30 GB free. But that is really not a nice position to see .bi grow. So we removed -usernotifytime and will log it to PSTS today. -usernotifytime is a dynamic parameter. I did set it to zero in promon R&D 4/7/8 when we hit that problem. Unfortunately that did not affect the users that were already flagged to disconnect and refused to do so by the time of setting -usernotifytime to zero. Progress 11.7.1 IBM AIX 7.1
Continue reading...
Continue reading...