While databases are terrific when they work, they are very complicated to fix when they don’t. We’ve had numerous calls for help over the last few years as people find that they cannot connect to the Oracle XE database after installing P6 Professional: an issue often bought about by security settings on their machine or Java setup problems. By giving us an alternative option for standalone client configuration, we can use something other than the Oracle XE database for an in-the-box solution.
This move to SQLite by Oracle Primavera obviates the need to be an Oracle database/Java expert. Come to think of it, who would? In short, it’s ideal as a P6 standalone database because its server-less nature keeps everything simple and packaged on just the PC on which it’s installed. SQLite has a tiny installation footprint of less than 1MB, but a theoretical database size limit of 140TB, yep that’s terabytes: theoretical because the SQLite developers don’t have access to a machine with that much disk space on which to actually test it.
Install primavera p6 update#
SQLite is a popular, self-contained, server-less, zero-configuration database that is prevalent in a variety of systems and devices produced by a wide range of manufacturers: indeed while doing research for this article, I noticed that SQLite is even part of my Garmin map update software package. With the release of Primavera P6 revision 8.4, you now have the option to run the Professional client as a standalone configuration using the SQLite database as its data repository.
As promised earlier this year, Oracle Primavera has now added a new option for running P6 Professional as a standalone tool that uses SQLite as an alternative to the Oracle XE database. This article takes a brief look at what you can expect from the new Primavera P6 Professional R8.4 installation process with regard to using the new SQLite database for your standalone configuration.