{"id":34877,"date":"2016-05-06t13:43:24","date_gmt":"2016-05-06t17:43:24","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=34877"},"modified":"2016-05-06t13:43:24","modified_gmt":"2016-05-06t17:43:24","slug":"pobs-data-bug-fixed-oracle-primavera-p6-16-1","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/pobs-data-bug-fixed-oracle-primavera-p6-16-1\/","title":{"rendered":"pobs data bug fixed in oracle primavera p6 16.1"},"content":{"rendered":"

by now, if you’re an oracle primavera p6 user you’ve probably heard about the problems with large xer files<\/a>, slow xer import processes<\/a> and the problems with pobs data in the primavera p6 database. we showed you how to circumvent those pobs issues either by cleaning up your xer file<\/a> before import or by cleaning primavera p6’s pobs tables<\/a>\u00a0from the database itself.<\/p>\n

oracle support has confirmed this presence of this bug in the software as far back as primavera p6 v8.3<\/a>. and they report that patches were released to the following p6 versions:<\/p>\n