![]() ![]() A Primavera P6 user can utilize resource and role information from a global data perspective, for example. Primavera P6 global data resides at the enterprise level and it is available and usable to all projects throughout the enterprise. Primavera P6 contains two types of data, global data and project data. Primavera P6 database corruption can include any of the following: erroneous POBS data and unwanted risk types (more on these scenarios shortly), data-bloated XER files resulting in extremely slow imports to Primavera P6, and Primavera P6 crashes. Several warning signs may occur when exporting and importing Primavera P6 XER files. If the Primavera P6 database has encountered corruption, it will often show in this instance. Data corruption is part of the territory when it comes to large storage capabilities, and unfortunately, Primavera P6 is not an exception to this issue.Ī Primavera P6 user may notice an issue when attempting to use Primavera P6’s XER import and export feature. The database contains dozens of tables and along with massive amounts of data storage can come data corruption. Primavera P6 uses a database to store its data and this database can contain millions of values, dates, and other data. Primavera P6 Database Corruption During File Imports and Why It Occurs ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |