Start a conversation
  1. Pivotal Support
  2. Pivotal Articles
  3. Articles

Pivotal 6.6.3 Database Compatibility with Pivotal 6.6.5 (Schema Changes and Upgrade Requirements)

Overview

If you are planning to upgrade Pivotal from 6.6.3 to 6.6.5, you may need to confirm whether the existing database can be reused and whether any database schema changes require a migration.

Engineering has confirmed that Pivotal 6.6.5 introduces no database schema changes compared to 6.6.3, so no database upgrade or migration is required for this version jump.

Key Information

  • Database compatibility: The 6.6.3 database is fully compatible with Pivotal 6.6.5.
  • Schema changes: None between 6.6.3 and 6.6.5 (no table/column/index/constraint changes).
  • Database upgrade/migration: Not required. Pivotal 6.6.5 can point to and use the existing 6.6.3 database directly.
  • Application prerequisite: Upgrade the application server to .NET Framework 4.8 (from 4.7).
  • SQL Server prerequisite: Update the SQL Server 2008 R2 Native Client driver to the version shipped with the 6.6.5 installer.
  • Oracle note: A new optional configuration setting exists in 6.6.5 related to parameterized query behavior; review the 6.6.5 release documentation and apply only if needed.

Customer Impact

No database migration or schema upgrade is needed when moving from Pivotal 6.6.3 to 6.6.5.

Plan the upgrade around platform and prerequisite changes (for example, .NET Framework 4.8 and required database client/driver updates) and validate the upgrade in a non-production environment before production cutover.

Frequently Asked Questions

1. How do I know this applies to me if I don’t have an error message?
This applies if you are planning an upgrade from Pivotal 6.6.3 to 6.6.5 and need to confirm whether a database schema upgrade/migration is required.
2. Are there any schema changes in 6.6.5 compared to 6.6.3?
No. Engineering confirmed no table, column, index, or constraint modifications between 6.6.3 and 6.6.5.
3. Can Pivotal 6.6.5 use the same database from 6.6.3 without a database upgrade?
Yes. The existing 6.6.3 database can be used directly by Pivotal 6.6.5 with no database upgrade or migration steps.
4. If no database upgrade is required, what should I still change/verify during the upgrade?
Verify non-database prerequisites, especially:
  • .NET Framework 4.8 on the application server
  • For SQL Server environments, update the SQL Server 2008 R2 Native Client driver to the version included with the 6.6.5 installer
  • For Oracle environments, review the optional parameterized query behavior setting described in the 6.6.5 release documentation
5. What if 6.6.5 fails to connect to the database after the upgrade?
Focus troubleshooting on prerequisites rather than schema changes:
  • Confirm the correct database client/driver versions are installed (notably the SQL Server 2008 R2 Native Client requirement for SQL Server environments).
  • Verify connection strings and credentials.
  • Review application logs for provider/driver errors and address missing dependencies.
Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments