SR-B77148 · Issue 325930
Handling added for importing PostgreSQL database Application Bundles
Resolved in Pega Version 7.3.1
Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.
SR-B77536 · Issue 326544
Check added to keep "::" in imports between PostgreSQL systems
Resolved in Pega Version 7.3.1
Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.
INC-130304 · Issue 567925
Retry logic added for downloading upgraded rules
Resolved in Pega Version 8.2.8
A Rules upgrade failed while downloading applications from the maintenance server due to an SFTP server connection failure. This has been resolved by adding logic to retry if the first connection attempt fails.
INC-132218 · Issue 573358
Resolved buffer overflow for Migration loadDatabase
Resolved in Pega Version 8.2.8
A Rules upgrade failed in the Migration step at loadDatabase stage, involving the move of all the table records from old schema to new schema. This was traced to the inability of Migration to load blob of sizes more than 100 MB, and has been resolved by updating Migration to use byte[] to read the blob content with the help of metadata that contains blob length.
INC-133202 · Issue 574700
TableRenameUtil hashing improved
Resolved in Pega Version 8.2.8
During index name generation, the algorithm that was responsible for index name uniqueness was sometimes insufficient and cerated a loop condition. This has been resolved by using a stronger hash algorithm and refactoring the code that could result in a loop.