Comments on: GSIS vs. IBM, Round 2 http://www.duckyparedes.com/blogs/2009/06/29/gsis-vs-ibm-round-2/ Columns from Malaya and Abante Fri, 10 Sep 2010 01:21:17 +0000 http://wordpress.org/?v=2.2 By: Concerned Citizen http://www.duckyparedes.com/blogs/2009/06/29/gsis-vs-ibm-round-2/#comment-2550 Concerned Citizen Tue, 18 Aug 2009 03:48:03 +0000 http://www.duckyparedes.com/blogs/2009/06/29/gsis-vs-ibm-round-2/#comment-2550 Is it ok if you can also check what's happening to PPA and BOC computerize projects, this is one classic examples Philippine money go to waste. Consultants are not qualified to handle projects such as BOC and PPA. All projects are long due already. Is it ok if you can also check what’s happening to PPA and BOC computerize projects, this is one classic examples Philippine money go to waste. Consultants are not qualified to handle projects such as BOC and PPA. All projects are long due already.

]]> By: Bert Peronilla http://www.duckyparedes.com/blogs/2009/06/29/gsis-vs-ibm-round-2/#comment-2427 Bert Peronilla Wed, 15 Jul 2009 20:34:31 +0000 http://www.duckyparedes.com/blogs/2009/06/29/gsis-vs-ibm-round-2/#comment-2427 As the saying goes, there are always two sides to a story. Here is the other side: I quote from the GSIS Web Site Press Release dated May 25, 2009: "GSIS said in early 2008, the IBM software had started showing problems, particularly in handling voluminous chunks of data. IBM upgraded its database system purportedly to enable it to handle unlimited volumes of data." The problem according to GSIS started in early 2008 under DB2 8.x. This is because they were starting to exceed the 256GB table space limit of 8.x. They could have solved the issue then under 8.x if they were willing to buy the Database Partition Feature (DPF) which would give them the capability to have up to 254 partitions of 256GB each. However, they decided to go to DB2 9.x which was a FREE upgrade to them and giving them a 2TB table space limit for a single partition. In about a year, GSIS encountered the "overflow" error which has been fixed by IBM on May 26, 2009. You can check this out either with GSIS or Questronix whether the "overflow" is still happening. (As an aside, I am just wondering out loud, how could a database grow from 256GB to 2TB in a span of one year? That is growing 8 times in size in one year???? Hmmmmmm.) I will give GSIS the benefit of the doubt on this "unusual" rate of growth in size of their database, so I will keep my mouth shut on this. I appreciate your sharing with me your understanding of this issue, I hope I have shared with you the rest of the story as best I can. Regards, Bert Peronilla As the saying goes, there are always two sides to a story. Here is the other side: I quote from the GSIS Web Site Press Release dated May 25, 2009:

“GSIS said in early 2008, the IBM software had started showing problems, particularly in handling voluminous chunks of data. IBM upgraded its database system purportedly to enable it to handle unlimited volumes of data.”

The problem according to GSIS started in early 2008 under DB2 8.x. This is because they were starting to exceed the 256GB table space limit of 8.x. They could have solved the issue then under 8.x if they were willing to buy the Database Partition Feature (DPF) which would give them the capability to have up to 254 partitions of 256GB each. However, they decided to go to DB2 9.x which was a FREE upgrade to them and giving them a 2TB table space limit for a single partition. In about a year, GSIS encountered the “overflow” error which has been fixed by IBM on May 26, 2009. You can check this out either with GSIS or Questronix whether the “overflow” is still happening. (As an aside, I am just wondering out loud, how could a database grow from 256GB to 2TB in a span of one year? That is growing 8 times in size in one year???? Hmmmmmm.) I will give GSIS the benefit of the doubt on this “unusual” rate of growth in size of their database, so I will keep my mouth shut on this.

I appreciate your sharing with me your understanding of this issue, I hope I have shared with you the rest of the story as best I can.

Regards,

Bert Peronilla

]]>