We must run the correct stored procedure sp__generate_sysgen_objects_V17 when upgrading a qdbmgr environment to version 17 to properly generate sysgen objects. If the wrong procedure is run, it may seem like sysgen completed when it did not actually run. To verify sysgen was generated, check the MAX_SYSGEN_DATE column in the QTRAN_ENV_OBJ_RESULT_ALL table for the most recent date.
We must run the correct stored procedure sp__generate_sysgen_objects_V17 when upgrading a qdbmgr environment to version 17 to properly generate sysgen objects. If the wrong procedure is run, it may seem like sysgen completed when it did not actually run. To verify sysgen was generated, check the MAX_SYSGEN_DATE column in the QTRAN_ENV_OBJ_RESULT_ALL table for the most recent date.
We must run the correct stored procedure sp__generate_sysgen_objects_V17 when upgrading a qdbmgr environment to version 17 to properly generate sysgen objects. If the wrong procedure is run, it may seem like sysgen completed when it did not actually run. To verify sysgen was generated, check the MAX_SYSGEN_DATE column in the QTRAN_ENV_OBJ_RESULT_ALL table for the most recent date.
Hi all,We have to be careful about running the correct stored procedure to generate
sysgen. If the qdbmgr environment is upgraded to be compatible with qdbmgr v17,
we must call the stored procedure sp__generate_sysgen_objects_V17. The command that stored procedure calls is powershell.exe -ExecutionPolicy Unrestricted -File "C:\QuorumApps\QDBMGR_TEST\QDBMGRRemote_V17.ps1" -env "wke". May be possible to have false sense that sysgen ran when it really did not. The following query in context of a qdbmgr database shows the last date a generate sysgen occurred. Could use this to verify sysgen actually ran. SELECT MAX(UPDT_DT) AS MAX_SYSGEN_DATE FROM QTRAN_ENV_OBJ_RESULT_ALL;