How to Clean up Your Oracle Primavera P6 Database

Joe Somerville

A Primavera P6 database naturally grows over time. That is normal. However, if it gets too large, users may notice slower performance, confusing duplicates, and global data that is no longer relevant. Use the four steps below to clean up your Oracle Primavera P6 database and keep schedules easier to manage.

Quick Summary:

Rename tasks, activities, and milestones using a clear naming standard
Remove extra copies of schedules
Reduce time blocks that are no longer needed
Remove outdated Global Change rules
Use the Analyze Data usage feature to help you clean out unused Enterprise Data
Use the Manage User Sessions – recent User Activity to eliminate users who no longer require access to P6

1. Rename tasks, activities, and milestones using clear naming

Project teams often abbreviate activity names, rule names, and schedule names. Abbreviations can work inside one project, but they create confusion when you manage multiple projects that share similar naming patterns. To reduce mix-ups, update names with a consistent standard that includes:

Month and year (for example, 01-2026)
A short, logical abbreviation
Enough detail that someone can recognize the item later

This helps prevent using the wrong constraints, resources, or rules in the wrong project.

2. Remove Extra Copies of Schedules

Saving backup copies can protect you when you run Global Change or make major edits. The issue is that schedule copies add up quickly. If backups are created often, the database can fill with thousands of old schedule versions. A better approach is to delete extra copies after the project is successfully delivered. Keep only what you truly need, such as one final copy for a limited retention period.

3. Reduce time blocks as the project nears completion

Many teams add time blocks to account for risks such as weather or other delays. Those placeholders can be useful early on, but they can become clutter later. As the project approaches completion, remove time blocks that are no longer realistic or needed. This keeps the schedule cleaner for closeout and reduces noise for anyone who reviews the plan after delivery.

4. Remove Global Change rules that are outdated or rarely used

Global Change is powerful because it can update large amounts of data at once. That also means old or unnecessary rules can pile up and make it harder to find the right one later.
A practical guideline is to:

Remove Global Change rules that are more than one year old, unless they are used often
Limit rule sets to a small number (for example, fewer than 10) so the list stays usable

5. Use the Analyze Data usage feature to help you clean out unused Enterprise Data

Over time, your database will accumulate elements of enterprise data such as activity codes, project, codes, resources, etc. which are no longer relevant to your business.
Use the Analyze Data feature in P6 EPPM to identify date items which are no longer used and delete those items.
Not only will this reduce the size of your database storage, it will make selecting the correct values easier for the users.

6. Use the Manage User Sessions – recent User Activity to eliminate users who no longer require access to P6

Users Come and go from your organization.
You can identify users who have not logged on to P6 recently using the Recent User Activity view under Manage User Sessions.
Access this feature by clicking on the dropdown arrow to the right of your user name in P6 EPPM, and selecting User Sessions, then select Recent User Activity.
Users may be deleted under Administration/ User Administration/Users.

Key Takeaway

Cleaning up your Oracle Primavera P6 database is much easier when you do it routinely. At minimum, plan to clean up after each project, or once per year.