The issue is under investigation but users if hit it, they can use the workaround described in KB 2000474.We confirm that SSIS is not impacted by the abovementioned issue in SQL Server 2016 SP1.

updating statistics in oracle-60updating statistics in oracle-57

Updating statistics in oracle dating pages international

Also, if you encountered a message listing obsolete initialization parameters when you started the database for upgrade, then remove the obsolete initialization parameters from the parameter file before restarting.

If necessary, convert the SPFILE to a PFILE so you can edit the file to delete the Post-Upgrade Status Tool $ORACLE_HOME/rdbms/admin/utlu112which provides a summary of the upgrade at the end of the spool log.

The issue and error below is applicable only to SQL Server 2016 branches patched with Security Update, CU3 or SP1 and doesn’t apply to lower versions of SQL Server.

“This business rule contains corrupted rule item(s), as corresponding SQL Script has been changed” “The sequence must be greater than zero” The fix for this issue is included in the following updates: ODBC Driver 13.1 With the default installation of SQL Server 2016, ODBC Driver 13.0 is installed on the server which is used by SQL Agent and SSMS (installed on server) to connect to the SQL Server instance.

Start SQL*Plus and connect to the database instance as a user with SYSDBA privileges. Please note that the database should be started using the Source Oracle Home.

$ sqlplus '/ as sysdba' SQLIf the script reports any invalid objects, run $ORACLE_HOME/rdbms/admin/(multiple times) to validate the invalid objects in the database, until there is no change in the number of invalid objects.

SQL Server Integration Services (SSIS) After installing SQL Server 2016 SP1, the DCOM permissions for launching and accessing Integration Services service may get reset to default permissions.

This issue is unconfirmed yet but if you have customized DCOM permissions, you might have to reapply the customization.

Database Upgrade are common but risky task for a DBA if not done properly.