Deployment Procedure

Contents

Introduction

This deployment procedure applies to the 7.6.015.22 hot fix release of Genesys Info Mart, released 03/19/15. It describes how to deploy Genesys Info Mart using the package you received from Genesys.

Deployment Procedure – Hot Fix [03/19/15]

To deploy this package, do one of the following depending on your current release:

• If you are currently using Genesys Info Mart 7.0.2, use the procedure described in "Migrating Genesys Info Mart from 7.0.2 to 7.6.x" in the Genesys Migration Guide to upgrade to Genesys Info Mart 7.6.015.22.

• If you are currently using Genesys Info Mart 7.2, use the procedure described in "Migrating Genesys Info Mart from 7.2.x to 7.6.x" in the Genesys Migration Guide to upgrade to Genesys Info Mart 7.6.015.22.

• If you are currently using a Genesys Info Mart 7.5 release earlier than 7.5.004.07, upgrade to release 7.5.004.07 using the Deployment Procedure supplied with it, and then use the migration procedure described in "Migrating Genesys Info Mart from 7.5.x to 7.6.x" in the Genesys Migration Guide to upgrade to Genesys Info Mart 7.6.015.22.

• If you are currently using Genesys Info Mart 7.5 Maintenance Release 1 or 2 (release number 7.5.004.xx or 7.5.005.xx) or later, use the procedure described in "Migrating Genesys Info Mart from 7.5.x to 7.6.x" in the Genesys Migration Guide to upgrade to Genesys Info Mart 7.6.015.22.

• If this is a new installation of Genesys Info Mart, use the installation procedures in the Genesys Info Mart 7.6 Deployment Guide.

• To install this release of Genesys Info Mart over a prior 7.6 release, use this Deployment Procedure.

Notes:

• If deploying this Genesys Info Mart release requires you to use procedures documented in the Genesys Migration Guide (as indicated above), make sure the version of the Genesys Migration Guide includes migration information for Genesys Info Mart up to release 7.6.014. If the version of the Genesys Migration Guide you are using does not confirm that this is the case, contact Genesys Customer Care for updated migration information.

• Review all steps before performing any of them.

• Plan a time when you can complete the installation in one continuous session. Several steps can take significant time to complete, and this potentially affects the availability of Info Mart data.

Pre-Installation Steps

1. Set the run-scheduler configuration option to FALSE in the schedule section of the Genesys Info Mart Application object to temporarily stop Genesys Info Mart Server from launching ETL jobs.

2. Wait for any currently running jobs to finish. Use the Genesys Info Mart Administration Console to monitor the completion of the jobs.

3. Stop the Genesys Info Mart Server.

4. Create backup copies of both your Staging Area and Info Mart databases.

5. Create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. These scripts perform the following tasks:

   • Create or modify the source Stat Server databases.

   • Create indexes in the source IDBs (Interaction Databases) to be used by Genesys Info Mart.

   • Create the target Staging Area and Info Mart databases.

   • Create the Info Mart database read-only views.

   The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.

   To locate these SQL scripts, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

6. Make a note of the application startup arguments if you customized them. The installation process will overwrite these arguments and you will lose any changes that you made.

   • If you are running Genesys Info Mart Server as a Windows service, you should have modified the startup arguments in the gim_etl_update_service_arguments.bat file. If you modified the gim_etl_update_service_arguments.bat file, make a backup copy of your .bat file that is located in your gim-etl home folder.

   • If you are not running Genesys Info Mart Server as a Windows service, but rather use Genesys Solution Control Interface to start and stop Genesys Info Mart Server, note the command-line arguments on the Start Info tab of the Genesys Info Mart Application object in Configuration Manager.

   • If you are using the gim_etl_server.bat file to start Genesys Info Mart Server, make a backup copy of your gim_etl_server.bat file that is located in your gim-etl home folder.

Installation Steps

1. Install the new Genesys Info Mart installation package:

   • On a Microsoft Windows operating system, uninstall the current Genesys Info Mart installation package using the Windows Control Panel > Add/Remove Programs. Then run setup to install the new Genesys Info Mart installation package.

   • On a UNIX operating system, run the new Genesys Info Mart installation script. When prompted, select the appropriate action to overwrite existing files (for example, Overwrite only the files contained in this package).

2. Update the 7.6 application startup arguments if you previously customized them.

   • If you are running Genesys Info Mart Server as a Windows service, open the General tab of the Genesys Info Mart 7.6 Windows service Properties window. Copy the arguments for the 7.6 application from the Path to executable text box to the gim_etl_update_service_arguments.bat file located in your 7.6 gim-etl home folder. Update the arguments per the backup copy of the .bat file that you created in Pre-Installation Step 6 above, but preserve the path to the 7.6 executable. Once you update the 7.6 .bat file, execute it in order for the changes to take effect. Genesys recommends that you make the same changes to the Genesys Info Mart Application object in Configuration Manager.

   • If you are using Genesys Solution Control Interface to start and stop Genesys Info Mart Server, modify the command-line arguments on the Start Info tab of the Genesys Info Mart Application object in Configuration Manager, as noted in Pre-Installation Step 6 above. Preserve the path to the 7.6 executable.

   • If you are using the gim_etl_server.bat file to start Genesys Info Mart Server, use the content of the backup gim_etl_server.bat file that you created in Pre-Installation Step 6 above to update the command-line arguments in the 7.6 copy of the gim_etl_server.bat file that the installation placed into your gim-etl home folder. Preserve the path to the 7.6 executable.

3. If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against each Interaction Database (IDB) with Database Access Point role equal to ICON_CORE if you have not previously done so (ER# 206504724):

   • Click to show/hide SQL statements for Oracle

     DROP INDEX GIM_IDX_ASRC_SEQ;
     
     CREATE INDEX GIM_IDX_ASRC_SEQ on G_AGENT_STATE_RC (
        GSYS_SEQ ASC,
        CREATED_TS ASC
     );
     

   • Click to show/hide SQL statements for Microsoft SQL Server

     DROP INDEX G_AGENT_STATE_RC.GIM_IDX_ASRC_SEQ
     go
     CREATE INDEX GIM_IDX_ASRC_SEQ on G_AGENT_STATE_RC (
        GSYS_SEQ ASC,
        CREATED_TS ASC
     )
     go
     

   • Click to show/hide SQL statements for DB2

     DROP INDEX GIM_IDX_ASRC_SEQ;
     
     CREATE INDEX GIM_IDX_ASRC_SEQ on G_AGENT_STATE_RC (
        GSYS_SEQ ASC,
        CREATED_TS ASC
     );
     

   
   

4. If you are installing over release 7.6.001.07, issue the following SQL statements against each Interaction Concentrator database (IDB) with Database Access Point role equal to ICON_CORE (ER# 207130586):

   • Click to show/hide SQL statements for Oracle or DB2

     DROP INDEX GIM_IDX_ASH_STATE;
     DROP INDEX GIM_IDX_ASH_PSTATE;
     DROP INDEX GIM_IDX_ASH_TYPE;
     DROP INDEX GIM_IDX_ASH_SEQ;
     
     CREATE INDEX GIM_IDX_ASH_SEQ on G_AGENT_STATE_HISTORY (
        GSYS_SEQ      ASC,
        TYPE          ASC,
        GSYS_EXT_INT1 ASC,
        ADDED_TS      ASC
     );
     

   • Click to show/hide SQL statements for Microsoft SQL Server

     DROP INDEX G_AGENT_STATE_HISTORY.GIM_IDX_ASH_STATE
     go
     DROP INDEX G_AGENT_STATE_HISTORY.GIM_IDX_ASH_PSTATE
     go
     DROP INDEX G_AGENT_STATE_HISTORY.GIM_IDX_ASH_TYPE
     go
     DROP INDEX G_AGENT_STATE_HISTORY.GIM_IDX_ASH_SEQ
     go
     
     CREATE INDEX GIM_IDX_ASH_SEQ on G_AGENT_STATE_HISTORY (
        GSYS_SEQ      ASC,
        TYPE          ASC,
        GSYS_EXT_INT1 ASC,
        ADDED_TS      ASC
     )
     go
     

   
   

5. If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Staging Area database if you have not previously done so (ER# 206504501):

   • Click to show/hide SQL statements for Oracle

     CREATE INDEX IDX_IR1_DB on STG_IR_1 (
      DBSOURCE_KEY,
      IRID
      );
     
     CREATE INDEX IDX_IR2_DB on STG_IR_2 (
      DBSOURCE_KEY,
      IRID
      );
     
     DROP INDEX SE_PEND_LOGINSESS_IDX;
     DROP INDEX SE_IDX_DB;
     
     CREATE INDEX SE_IDX_DB on STG_GX_SESSION_ENDPOINT_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       ENDPOINTID,
       QUEUEID
       );
     
     DROP INDEX AS_EVENTSEQ_PEND_IDX;
     DROP INDEX AS_LOGINSESS_PEND_IDX;
     DROP INDEX AS_EVENTSEQ_PEND_DB;
     
     CREATE INDEX AS_EVENTSEQ_PEND_DB on STG_G_AGENT_STATE_HISTORY_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       EVENTSEQ,
       ENDPOINTID,
       QUEUEID,
       TYPE
       );
     
     DROP INDEX AR_EVENTSEQ_PEND_IDX;
     DROP INDEX AR_LOGINSESS_PEND_IDX;
     DROP INDEX AR_EVENTSEQ_PEND_DB;
     
     CREATE INDEX AR_EVENTSEQ_PEND_DB on STG_G_AGENT_STATE_RC_PEND (
       DBSOURCE_KEY,
       SESSIONID,
       EVENTSEQ,
       ENDPOINTID
       );
     
     DROP INDEX IDX_STG_G_LSESS_LSID_PEND;
     DROP INDEX IDX_STG_G_LSESS_LSDB_PEND;
     
     CREATE INDEX IDX_STG_G_LSESS_LSDB_PEND on STG_G_LOGIN_SESSION_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID
       );
     
     DROP INDEX EVENTSEQ_IDX_PEND;
     DROP INDEX LOGINSESS_IDX_PEND;
     DROP INDEX EVENTSEQ_DB_PEND;
     
     CREATE INDEX EVENTSEQ_DB_PEND on STG_G_DND_HISTORY_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       EVENTSEQ
       );
     

   • Click to show/hide SQL statements for Microsoft SQL Server

     CREATE INDEX IDX_IR1_DB on STG_IR_1 (
      DBSOURCE_KEY,
      IRID
      )
     go
     
     CREATE INDEX IDX_IR2_DB on STG_IR_2 (
      DBSOURCE_KEY,
      IRID
      )
     go
     
     DROP INDEX STG_GX_SESSION_ENDPOINT_PEND.SE_PEND_LOGINSESS_IDX
     go
     DROP INDEX STG_GX_SESSION_ENDPOINT_PEND.SE_PEND_IDX_DB
     go
     
     CREATE INDEX SE_PEND_IDX_DB on STG_GX_SESSION_ENDPOINT_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       ENDPOINTID,
       QUEUEID
       )
     go
     
     DROP INDEX STG_G_AGENT_STATE_HISTORY_PEND.AS_EVENTSEQ_PEND_IDX
     go
     DROP INDEX STG_G_AGENT_STATE_HISTORY_PEND.AS_LOGINSESS_PEND_IDX
     go
     DROP INDEX STG_G_AGENT_STATE_HISTORY_PEND.AS_EVENTSEQ_PEND_DB
     go
     
     CREATE INDEX AS_EVENTSEQ_PEND_DB on STG_G_AGENT_STATE_HISTORY_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       EVENTSEQ,
       ENDPOINTID,
       QUEUEID,
       TYPE
       )
     go
     
     DROP INDEX STG_G_AGENT_STATE_RC_PEND.AR_EVENTSEQ_PEND_IDX
     go
     DROP INDEX STG_G_AGENT_STATE_RC_PEND.AR_LOGINSESS_PEND_IDX
     go
     DROP INDEX STG_G_AGENT_STATE_RC_PEND.AR_EVENTSEQ_PEND_DB
     go
     
     CREATE INDEX AR_EVENTSEQ_PEND_DB on STG_G_AGENT_STATE_RC_PEND (
       DBSOURCE_KEY,
       SESSIONID,
       EVENTSEQ,
       ENDPOINTID
       )
     go
     
     DROP INDEX STG_G_LOGIN_SESSION_PEND.IDX_STG_G_LSESS_LSID_PEND
     go
     DROP INDEX STG_G_LOGIN_SESSION_PEND.IDX_STG_G_LSESS_LSDB_PEND
     go
     
     CREATE INDEX IDX_STG_G_LSESS_LSDB_PEND on STG_G_LOGIN_SESSION_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID
       )
     go
     
     DROP INDEX STG_G_DND_HISTORY_PEND.EVENTSEQ_IDX_PEND
     go
     DROP INDEX STG_G_DND_HISTORY_PEND.LOGINSESS_IDX_PEND
     go
     DROP INDEX STG_G_DND_HISTORY_PEND.EVENTSEQ_DB_PEND
     go
     
     CREATE INDEX EVENTSEQ_DB_PEND on STG_G_DND_HISTORY_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       EVENTSEQ
       )
     go
     

   • Click to show/hide SQL statements for DB2

     CREATE INDEX IDX_IR1_DB on STG_IR_1 (
      DBSOURCE_KEY,
      IRID
      );
     CREATE INDEX IDX_IR2_DB on STG_IR_2 (
      DBSOURCE_KEY,
      IRID
      );
     
     DROP INDEX SE_PNDLOGSES_IDX;
     DROP INDEX SE_PEND_IDX_DB;
     
     CREATE INDEX SE_PEND_IDX_DB on STG_GX_SESSION_ENDPOINT_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       ENDPOINTID,
       QUEUEID
       );
     
     DROP INDEX GASPND_EVSEQ_IDX;
     DROP INDEX GASPND_LOGIID_IDX;
     DROP INDEX GASPND_DBKEY_IDX;
     
     CREATE INDEX GASPND_DBKEY_IDX on STG_G_AGENT_STATE_HISTORY_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       EVENTSEQ,
       ENDPOINTID,
       QUEUEID,
       TYPE
       );
     
     DROP INDEX ARPND_EVSEQ_IDX;
     DROP INDEX ARPND_SESSID_IDX;
     DROP INDEX ARPND_DBKEY_IDX;
     
     CREATE INDEX ARPND_DBKEY_IDX on STG_G_AGENT_STATE_RC_PEND (
       DBSOURCE_KEY,
       SESSIONID,
       EVENTSEQ,
       ENDPOINTID
       );
     
     DROP INDEX IDX_PNDGLSESS_LID;
     DROP INDEX IDX_PNDGLSESS_DB;
     
     CREATE INDEX IDX_PNDGLSESS_DB on STG_G_LOGIN_SESSION_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID
       );
     
     DROP INDEX IDX_PNDGDND_EVS;
     DROP INDEX IDX_PNDGDND_LID;
     DROP INDEX IDX_PNDGDND_DB;
     
     CREATE INDEX IDX_PNDGDND_DB on STG_G_DND_HISTORY_PEND (
       DBSOURCE_KEY,
       LOGINSESSIONID,
       EVENTSEQ
       );
     

   
   

6. If you are installing over release 7.6.001.07, issue the following SQL statements against the Staging Area database (ER# 207130586):

   • Click to show/hide SQL statements for Oracle

     ALTER TABLE STG_EXTRACT_THROTTLE ADD (
        UNFINISHED NUMBER(1)
      );
     
     UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.000.14';
     COMMIT;
     

   • Click to show/hide SQL statements for Microsoft SQL Server

     ALTER TABLE STG_EXTRACT_THROTTLE
      ADD UNFINISHED NUMERIC(1) NULL
      go
     
     BEGIN TRANSACTION
     go
     
     UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.000.14'
     go
     
     COMMIT
     go
     

   • Click to show/hide SQL statements for DB2

     ALTER TABLE STG_EXTRACT_THROTTLE
       ADD UNFINISHED NUMERIC(1);
     
     UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.000.14';
     COMMIT;
     

   
   

7. If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Info Mart database if you have not previously done so (ER# 206620229):

   • Click to show/hide SQL statements for Oracle or DB2

     UPDATE TIME_RANGE
     SET
            BOUND_4 = (CASE
                         WHEN BOUND_4 IS NULL THEN 0
                         ELSE BOUND_4
                       END),
            BOUND_5 = (CASE
                         WHEN BOUND_5 IS NULL THEN 0
                         ELSE BOUND_5
                       END),
            BOUND_6 = (CASE
                         WHEN BOUND_6 IS NULL THEN 0
                         ELSE BOUND_6
                       END),
            BOUND_7 = (CASE
                         WHEN BOUND_7 IS NULL THEN 0
                         ELSE BOUND_7
                       END),
            BOUND_8 = (CASE
                         WHEN BOUND_8 IS NULL THEN 0
                         ELSE BOUND_8
                       END),
            BOUND_9 = (CASE
                         WHEN BOUND_9 IS NULL THEN 0
                         ELSE BOUND_9
                       END),
            BOUND_10 = (CASE
                          WHEN BOUND_10 IS NULL THEN 0
                          ELSE BOUND_10
                        END),
            BOUND_11 = (CASE
                          WHEN BOUND_11 IS NULL THEN 0
                          ELSE BOUND_11
                        END),
            BOUND_12 = (CASE
                          WHEN BOUND_12 IS NULL THEN 0
                          ELSE BOUND_12
                        END),
            BOUND_13 = (CASE
                          WHEN BOUND_13 IS NULL THEN 0
                          ELSE BOUND_13
                        END),
            BOUND_14 = (CASE
                          WHEN BOUND_14 IS NULL THEN 0
                          ELSE BOUND_14
                        END),
            BOUND_15 = (CASE
                          WHEN BOUND_15 IS NULL THEN 0
                          ELSE BOUND_15
                        END),
            BOUND_16 = (CASE
                          WHEN BOUND_16 IS NULL THEN 0
                          ELSE BOUND_16
                        END),
            BOUND_17 = (CASE
                          WHEN BOUND_17 IS NULL THEN 0
                          ELSE BOUND_17
                        END),
            BOUND_18 = (CASE
                          WHEN BOUND_18 IS NULL THEN 0
                          ELSE BOUND_18
                        END),
            BOUND_19 = (CASE
                          WHEN BOUND_19 IS NULL THEN 0
                          ELSE BOUND_19
                        END);
     
     COMMIT;
     

   • Click to show/hide SQL statements for Microsoft SQL Server

     BEGIN TRANSACTION
     go
     
     UPDATE TIME_RANGE
     SET
            BOUND_4 = (CASE
                         WHEN BOUND_4 IS NULL THEN 0
                         ELSE BOUND_4
                       END),
            BOUND_5 = (CASE
                         WHEN BOUND_5 IS NULL THEN 0
                         ELSE BOUND_5
                       END),
            BOUND_6 = (CASE
                         WHEN BOUND_6 IS NULL THEN 0
                         ELSE BOUND_6
                       END),
            BOUND_7 = (CASE
                         WHEN BOUND_7 IS NULL THEN 0
                         ELSE BOUND_7
                       END),
            BOUND_8 = (CASE
                         WHEN BOUND_8 IS NULL THEN 0
                         ELSE BOUND_8
                       END),
            BOUND_9 = (CASE
                         WHEN BOUND_9 IS NULL THEN 0
                         ELSE BOUND_9
                       END),
            BOUND_10 = (CASE
                          WHEN BOUND_10 IS NULL THEN 0
                          ELSE BOUND_10
                        END),
            BOUND_11 = (CASE
                          WHEN BOUND_11 IS NULL THEN 0
                          ELSE BOUND_11
                        END),
            BOUND_12 = (CASE
                          WHEN BOUND_12 IS NULL THEN 0
                          ELSE BOUND_12
                        END),
            BOUND_13 = (CASE
                          WHEN BOUND_13 IS NULL THEN 0
                          ELSE BOUND_13
                        END),
            BOUND_14 = (CASE
                          WHEN BOUND_14 IS NULL THEN 0
                          ELSE BOUND_14
                        END),
            BOUND_15 = (CASE
                          WHEN BOUND_15 IS NULL THEN 0
                          ELSE BOUND_15
                        END),
            BOUND_16 = (CASE
                          WHEN BOUND_16 IS NULL THEN 0
                          ELSE BOUND_16
                        END),
            BOUND_17 = (CASE
                          WHEN BOUND_17 IS NULL THEN 0
                          ELSE BOUND_17
                        END),
            BOUND_18 = (CASE
                          WHEN BOUND_18 IS NULL THEN 0
                          ELSE BOUND_18
                        END),
            BOUND_19 = (CASE
                          WHEN BOUND_19 IS NULL THEN 0
                          ELSE BOUND_19
                        END)
     go
     
     COMMIT
     go
     

   
   

8. If you are installing over release 7.6.001.07, examine the following SQL commands and issue them against the Info Mart database if you have not previously done so (ER# 206112053):

   • Click to show/hide SQL commands for Oracle

     ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
      DROP constraint PK_AG2_INB_V_QUEUE_ABN_DAY;
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
      DROP constraint PK_AG2_INB_V_QUEUE_ABN_HOUR;
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
      DROP constraint PK_AG2_INB_V_QUEUE_ABN_MONTH;
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
      DROP constraint PK_AG2_INB_V_QUEUE_ANS_DAY;
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
      DROP constraint PK_AG2_INB_V_QUEUE_ANS_HOUR;
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
      DROP constraint PK_AG2_INB_V_QUEUE_ANS_MONTH;
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
      ADD constraint PK_AG2_INB_V_QUEUE_ABN_DAY primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
      ADD constraint PK_AG2_INB_V_QUEUE_ABN_HOUR primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
      ADD constraint PK_AG2_INB_V_QUEUE_ABN_MONTH primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
      ADD constraint PK_AG2_INB_V_QUEUE_ANS_DAY primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
      ADD constraint PK_AG2_INB_V_QUEUE_ANS_HOUR primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
      ADD constraint PK_AG2_INB_V_QUEUE_ANS_MONTH primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     

   • Click to show/hide SQL commands for Microsoft SQL Server

     ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
      DROP constraint PK_AG2_INB_V_QUEUE_ABN_DAY
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
      DROP constraint PK_AG2_INB_V_QUEUE_ABN_HOUR
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
      DROP constraint PK_AG2_INB_V_QUEUE_ABN_MONTH
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
      DROP constraint PK_AG2_INB_V_QUEUE_ANS_DAY
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
      DROP constraint PK_AG2_INB_V_QUEUE_ANS_HOUR
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
      DROP constraint PK_AG2_INB_V_QUEUE_ANS_MONTH
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
      ADD constraint PK_AG2_INB_V_QUEUE_ABN_DAY primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
      ADD constraint PK_AG2_INB_V_QUEUE_ABN_HOUR primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
      ADD constraint PK_AG2_INB_V_QUEUE_ABN_MONTH primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
      ADD constraint PK_AG2_INB_V_QUEUE_ANS_DAY primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
      ADD constraint PK_AG2_INB_V_QUEUE_ANS_HOUR primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
     go
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
      ADD constraint PK_AG2_INB_V_QUEUE_ANS_MONTH primary key
     (STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
     go
     

   • Click to show/hide SQL commands for DB2

     ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
      DROP constraint "P_Key_1";
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
      DROP constraint "P_Key_1";
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
      DROP constraint "P_Key_1";
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
      DROP constraint "P_Key_1";
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
      DROP constraint "P_Key_1";
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
      DROP constraint "P_Key_1";
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
      ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
     TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
      ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
     TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
      ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
     TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
      ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
     TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
      ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
     TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     
     ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
      ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
     TENANT_KEY, RESOURCE_KEY,
     GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
     

   
   

9. If you are installing over release 7.6.001.07, examine the following SQL statement and issue it against the Info Mart database if you have not previously done so (ER# 205563115):

   • Click to show/hide SQL statement for Oracle or DB2

     CREATE INDEX IDX_DT_DAY_NUM on DATE_TIME (
        RUNNING_DAY_NUM ASC
     );
     

   • Click to show/hide SQL statement for Microsoft SQL Server

     CREATE INDEX IDX_DT_DAY_NUM on DATE_TIME (
     RUNNING_DAY_NUM ASC
     )
     go
     

   
   

10. If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Info Mart database if you have not previously done so (ER# 204783401):

    • Click to show/hide SQL statements for Oracle or DB2

      CREATE INDEX IDX_IRF_DTM ON INTERACTION_RESOURCE_FACT (
         MEDIATION_START_DATE_TIME_KEY ASC
      );
      
      CREATE INDEX IDX_RIRF_DTM ON R_INTERACTION_RESOURCE_FACT (
         MEDIATION_START_DATE_TIME_KEY ASC
      );
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      CREATE INDEX IDX_IRF_DTM ON INTERACTION_RESOURCE_FACT (
         MEDIATION_START_DATE_TIME_KEY ASC
      )
      go
      
      CREATE INDEX IDX_RIRF_DTM ON R_INTERACTION_RESOURCE_FACT (
         MEDIATION_START_DATE_TIME_KEY ASC
      )
      go
      

    
    

11. If you are installing over release 7.6.002.07 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 212799606):

    • Click to show/hide SQL statement for Oracle

      CREATE INDEX ICI_CALLID_IDX ON STG_ICON_CALL_INFO (
        CALLID ASC
      );
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      CREATE INDEX ICI_CALLID_IDX ON STG_ICON_CALL_INFO (
        CALLID ASC
      )
      go
      

    • Click to show/hide SQL statements for DB2

      CREATE INDEX ICI_CALLID_IDX ON STG_ICON_CALL_INFO (
         CALLID ASC
      )
      ALLOW REVERSE SCANS;
      

    
    

12. If you are installing over release 7.6.002.07 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 216377068):

    • Click to show/hide SQL statement for Oracle

      CREATE INDEX ICI_CAF_KEY_IDX ON STG_ICON_CALL_INFO (
         CONTACT_ATTEMPT_FACT_KEY ASC
      );
      
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      CREATE INDEX ICI_CAF_KEY_IDX ON STG_ICON_CALL_INFO (
         CONTACT_ATTEMPT_FACT_KEY ASC
      )
      go
      
      

    • Click to show/hide SQL statements for DB2

      CREATE INDEX ICI_CAF_KEY_IDX ON STG_ICON_CALL_INFO (
         CONTACT_ATTEMPT_FACT_KEY ASC
      )
      ALLOW REVERSE SCANS;
      
      

    
    

13. If you are installing over release 7.6.003.08 or an earlier 7.6 release and plan to take advantage of the new functionality introduced in the Genesys Info Mart 7.6 Maintenance Release 3 (release number 7.6.004.07) to extract UserEvent-based key-value pair data associated with voice interactions, issue the following SQL statements against each Interaction Concentrator database (IDB) with Database Access Point role equal to ICON_CORE (ER# 205973400):

    • Click to show/hide SQL statements for Oracle or DB2

      CREATE INDEX GIM_IDX_CUST_CALLID on G_CUSTOM_DATA_S (
            CALLID ASC
      );
      
      CREATE INDEX GIM_IDX_CDS_SYS_SEQ on G_CUSTOM_DATA_S (
        GSYS_SYS_ID ASC,
        GSYS_SEQ    ASC,
        ADDED_TS    ASC
      );
      
      CREATE INDEX GIM_IDX_UH_SYS_SEQ on G_USERDATA_HISTORY (
        GSYS_SYS_ID ASC,
        GSYS_SEQ    ASC,
        ADDED_TS    ASC
      );
      
      CREATE INDEX GIM_IDX_SUH_SYS_SEQ on G_SECURE_USERDATA_HISTORY (
        GSYS_SYS_ID ASC,
        GSYS_SEQ    ASC,
        ADDED_TS    ASC
      );
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      CREATE INDEX GIM_IDX_CUST_CALLID on G_CUSTOM_DATA_S (
        CALLID ASC
      )
      go
      
      CREATE INDEX GIM_IDX_CDS_SYS_SEQ on G_CUSTOM_DATA_S (
        GSYS_SYS_ID ASC,
        GSYS_SEQ    ASC,
        ADDED_TS    ASC
      )
      go
      
      CREATE INDEX GIM_IDX_UH_SYS_SEQ on G_USERDATA_HISTORY (
        GSYS_SYS_ID ASC,
        GSYS_SEQ    ASC,
        ADDED_TS    ASC
      )
      go
      
      CREATE INDEX GIM_IDX_SUH_SYS_SEQ on G_SECURE_USERDATA_HISTORY (
        GSYS_SYS_ID ASC,
        GSYS_SEQ    ASC,
        ADDED_TS    ASC
      )
      go
      

    
    

14. If you are installing over release 7.6.003.08 or an earlier 7.6 release, issue the following SQL statements against each Interaction Concentrator database (IDB) with Database Access Point role equal to ICON_CORE or ICON_MM (ER# 183662866):

    • Click to show/hide SQL statements for Oracle or DB2

      DROP INDEX GIM_IDX_ASH_SEQ;
      
      DROP INDEX GIM_IDX_ASH_SYSID;
      
      CREATE INDEX GIM_IDX_ASH_SEQ on G_AGENT_STATE_HISTORY (
        GSYS_SYS_ID   ASC,
        GSYS_SEQ      ASC,
        TYPE          ASC,
        GSYS_EXT_INT1 ASC,
        ADDED_TS      ASC
      );
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      DROP INDEX G_AGENT_STATE_HISTORY.GIM_IDX_ASH_SEQ
      go
      
       DROP INDEX G_AGENT_STATE_HISTORY.GIM_IDX_ASH_SYSID
      go
      
      CREATE INDEX GIM_IDX_ASH_SEQ on G_AGENT_STATE_HISTORY (
        GSYS_SYS_ID   ASC,
        GSYS_SEQ      ASC,
        TYPE          ASC,
        GSYS_EXT_INT1 ASC,
        ADDED_TS      ASC
      )
      go
      

    
    

15. If you are installing over release 7.6.003.08 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 218900695):

    • Click to show/hide SQL statements for Oracle

      ALTER TABLE STG_ICON_CALL_INFO MODIFY (
        TALK_COUNT NUMBER(5),
        HOLD_COUNT NUMBER(5),
        ACW_COUNT  NUMBER(5)
      );
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      ALTER TABLE STG_ICON_CALL_INFO
       ALTER COLUMN
         TALK_COUNT SMALLINT NULL
      go
      
      ALTER TABLE STG_ICON_CALL_INFO
       ALTER COLUMN
         HOLD_COUNT SMALLINT NULL
      go
      
      ALTER TABLE STG_ICON_CALL_INFO
       ALTER COLUMN
         ACW_COUNT SMALLINT NULL
      go
      

    • Click to show/hide SQL statements for DB2 v9

      ALTER TABLE STG_ICON_CALL_INFO
        ALTER COLUMN TALK_COUNT SET DATA TYPE DECIMAL(5);
      
      ALTER TABLE STG_ICON_CALL_INFO
        ALTER COLUMN HOLD_COUNT SET DATA TYPE DECIMAL(5);
      
      ALTER TABLE STG_ICON_CALL_INFO
        ALTER COLUMN ACW_COUNT SET DATA TYPE DECIMAL(5);
      
      REORG TABLE STG_ICON_CALL_INFO;
      

    • Click to show/hide SQL statements for DB2 v8.2

      RENAME TABLE STG_ICON_CALL_INFO TO STG_ICON_CALL_INFO_TMP;
      
      DROP INDEX ICI_CALLID_IDX;
      DROP INDEX ICI_CAF_KEY_IDX;
      
      CREATE TABLE STG_ICON_CALL_INFO
      (
        CALLID                    VARCHAR(50),
        INTERACTION_ID            NUMERIC(19),
        CALL_ATTEMPT_ID           VARCHAR(64),
        RESOURCE_KEY              INTEGER,
        MEDIA_RESOURCE_KEY        INTEGER,
        PLACE_KEY                 INTEGER,
        STARTTIME                 INTEGER,
        TALK_COUNT                SMALLINT,
        TALK_DURATION             INTEGER,
        HOLD_COUNT                SMALLINT,
        HOLD_DURATION             INTEGER,
        ACW_COUNT                 SMALLINT,
        ACW_DURATION              INTEGER,
        MM_IXN                    NUMERIC(1),
        ROW_STATUS                INTEGER,
        VQ_ROW_STATUS             INTEGER,
        GVP_ROW_STATUS            INTEGER,
        CONTACT_ATTEMPT_FACT_KEY  NUMERIC(19),
        LOAD_OCS_ROW_STATUS       INTEGER,
        SOURCE_TS                 INTEGER
      );
      
       CREATE INDEX ICI_CALLID_IDX ON STG_ICON_CALL_INFO (
        CALLID ASC
      )
      ALLOW REVERSE SCANS;
      
      CREATE INDEX ICI_CAF_KEY_IDX on STG_ICON_CALL_INFO (
        CONTACT_ATTEMPT_FACT_KEY ASC
      )
      ALLOW REVERSE SCANS;
      
      INSERT INTO STG_ICON_CALL_INFO (
        CALLID,
        INTERACTION_ID,
        CALL_ATTEMPT_ID,
        RESOURCE_KEY,
        MEDIA_RESOURCE_KEY,
        PLACE_KEY,
        STARTTIME,
        TALK_COUNT,
        TALK_DURATION,
        HOLD_COUNT,
        HOLD_DURATION,
        ACW_COUNT,
        ACW_DURATION,
        MM_IXN,
        ROW_STATUS,
        VQ_ROW_STATUS,
        GVP_ROW_STATUS,
        CONTACT_ATTEMPT_FACT_KEY,
        LOAD_OCS_ROW_STATUS,
        SOURCE_TS
      )
      SELECT
        CALLID,
        INTERACTION_ID,
        CALL_ATTEMPT_ID,
        RESOURCE_KEY,
        MEDIA_RESOURCE_KEY,
        PLACE_KEY,
        STARTTIME,
        TALK_COUNT,
        TALK_DURATION,
        HOLD_COUNT,
        HOLD_DURATION,
        ACW_COUNT,
        ACW_DURATION,
        MM_IXN,
        ROW_STATUS,
        VQ_ROW_STATUS,
        GVP_ROW_STATUS,
        CONTACT_ATTEMPT_FACT_KEY,
        LOAD_OCS_ROW_STATUS,
        SOURCE_TS
      FROM STG_ICON_CALL_INFO_TMP;
      
      COMMIT;
      

    
    

16. If you are installing over release 7.6.003.08 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 205973400):

    • Click to show/hide SQL statements for Oracle

      CREATE TABLE STG_GUD_STATUS  (
        JOB_ID                   VARCHAR2(512)   NOT NULL,
        TABLE_NAME               VARCHAR2(255)   NOT NULL,
        DBCONNECTION             VARCHAR2(255)   NOT NULL,
        OWNER                    VARCHAR2(255)   NOT NULL,
        GSYS_SYS_ID              NUMBER(10)      NOT NULL,
        MAX_AVAILABLE_SEQUENCE   NUMBER(20),
        MAX_AVAILABLE_TS         NUMBER(10)
      );
      
       CREATE TABLE STG_G_CUSTOM_DATA_S  (
        ID              NUMBER(19,0)     NOT NULL,
        CALLID          VARCHAR2(50),
        PARTYID         VARCHAR2(50),
        ROOTIRID        VARCHAR2(50),
        PSEQ            NUMBER(10)       NOT NULL,
        ENDPOINTID      NUMBER(10),
        ENDPOINTDN      VARCHAR2(255),
        AGENTID         NUMBER(10),
        SWITCHID        NUMBER(10),
        TENANTID        NUMBER(10),
        KEYNAME         VARCHAR2(64)     NOT NULL,
        VALUE           VARCHAR2(255),
        ADDED           DATE             NOT NULL,
        ADDED_TS        NUMBER(10),
        ADDED_TCODE     NUMBER(10),
        GSYS_DOMAIN     NUMBER(10),
        GSYS_PARTITION  NUMBER(10),
        GSYS_SYS_ID     NUMBER(10)       NOT NULL,
        GSYS_SEQ        NUMBER(10),
        GSYS_USEQ       NUMBER(10),
        GSYS_MSEQ       NUMBER(10),
        GSYS_TS         DATE,
        GSYS_TC         NUMBER(10),
        GSYS_EXT_VCH1   VARCHAR2(255),
        GSYS_EXT_VCH2   VARCHAR2(255),
        GSYS_EXT_INT1   NUMBER(10),
        GSYS_EXT_INT2   NUMBER(10),
        DBSOURCE_KEY    SMALLINT         NOT NULL,
        ETL_STATUS      VARCHAR2(32),
        CONSTRAINT PK_STG_G_CUSTOM_DATA_S PRIMARY KEY (ID, GSYS_SYS_ID)
      );
      
      CREATE INDEX CDS_IRID_IDX ON STG_G_CUSTOM_DATA_S (
        ROOTIRID ASC
      );
      
      CREATE INDEX CDS_MSEQ_IDX ON STG_G_CUSTOM_DATA_S (
        GSYS_MSEQ ASC
      );
      
      CREATE INDEX CDS_CALLID_IDX ON STG_G_CUSTOM_DATA_S (
        CALLID ASC
      );
      
      CREATE TABLE STG_G_PROV_CTRL_SNAPSHOT  (
        JOB_ID            VARCHAR2(512)  NOT NULL,
        DBCONNECTION      VARCHAR2(255)  NOT NULL,
        OWNER             VARCHAR2(255)  NOT NULL,
        GSYS_SYS_ID       NUMBER(10)     NOT NULL,
        PROVIDER_TAG      NUMBER(10)     NOT NULL,
        SEQ_CURRENT       NUMBER(20)     NOT NULL,
        MAX_PROVIDER_TS   NUMBER(10),
        MAX_IDB_TS        NUMBER(10),
        MAX_SAFE_MSEQ     NUMBER(20)
      );
      
      UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.004.00';
      COMMIT;
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      CREATE TABLE STG_GUD_STATUS (
        JOB_ID                   VARCHAR(512)   NOT NULL,
        TABLE_NAME               VARCHAR(255)   NOT NULL,
        DBCONNECTION             VARCHAR(255)   NOT NULL,
        OWNER                    VARCHAR(255)   NOT NULL,
        GSYS_SYS_ID              INT            NOT NULL,
        MAX_AVAILABLE_SEQUENCE   NUMERIC(20)    NULL,
        MAX_AVAILABLE_TS         INT            NULL
      )
      go
      
       CREATE TABLE STG_G_CUSTOM_DATA_S (
        ID               NUMERIC(19)    NOT NULL,
        CALLID           VARCHAR(50)    NULL,
        PARTYID          VARCHAR(50)    NULL,
        ROOTIRID         VARCHAR(50)    NULL,
        PSEQ             INT            NOT NULL,
        ENDPOINTID       INT            NULL,
        ENDPOINTDN       VARCHAR(255)   NULL,
        AGENTID          INT            NULL,
        SWITCHID         INT            NULL,
        TENANTID         INT            NULL,
        KEYNAME          VARCHAR(64)    NOT NULL,
        VALUE            VARCHAR(255)   NULL,
        ADDED            DATETIME       NOT NULL,
        ADDED_TS         INT            NULL,
        ADDED_TCODE      INT            NULL,
        GSYS_DOMAIN      INT            NULL,
        GSYS_PARTITION   INT            NULL,
        GSYS_SYS_ID      INT            NOT NULL,
        GSYS_SEQ         INT            NULL,
        GSYS_USEQ        INT            NULL,
        GSYS_MSEQ        INT            NULL,
        GSYS_TS          DATETIME       NULL,
        GSYS_TC          INT            NULL,
        GSYS_EXT_VCH1    VARCHAR(255)   NULL,
        GSYS_EXT_VCH2    VARCHAR(255)   NULL,
        GSYS_EXT_INT1    INT            NULL,
        GSYS_EXT_INT2    INT            NULL,
        DBSOURCE_KEY     SMALLINT       NOT NULL,
        ETL_STATUS       VARCHAR(32)    NULL
      )
      go
      
      CREATE CLUSTERED INDEX CDS_IRID_IDX ON STG_G_CUSTOM_DATA_S (
        ROOTIRID ASC
      )
      WITH  FILLFACTOR= 50
      go
      
      CREATE UNIQUE INDEX PK_STG_G_CUSTOM_DATA_S ON STG_G_CUSTOM_DATA_S (
        ID ASC,
        GSYS_SYS_ID ASC
      )
      go
      
      CREATE INDEX CDS_MSEQ_IDX ON STG_G_CUSTOM_DATA_S (
        GSYS_MSEQ ASC
      )
      go
      
      CREATE INDEX CDS_CALLID_IDX ON STG_G_CUSTOM_DATA_S (
        CALLID ASC
      )
      go
      
      CREATE TABLE STG_G_PROV_CTRL_SNAPSHOT (
        JOB_ID            VARCHAR(512)   NOT NULL,
        DBCONNECTION      VARCHAR(255)   NOT NULL,
        OWNER             VARCHAR(255)   NOT NULL,
        GSYS_SYS_ID       INT            NOT NULL,
        PROVIDER_TAG      INT            NOT NULL,
        SEQ_CURRENT       NUMERIC(20)    NOT NULL,
        MAX_PROVIDER_TS   INT            NULL,
        MAX_IDB_TS        INT            NULL,
        MAX_SAFE_MSEQ     NUMERIC(20)    NULL
      )
      go
      
      BEGIN TRANSACTION
      go
      
      UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.004.00'
      go
      
      COMMIT
      go
      

    • Click to show/hide SQL statements for DB2

      CREATE TABLE STG_GUD_STATUS
      (
        JOB_ID                   VARCHAR(512)   NOT NULL,
        TABLE_NAME               VARCHAR(255)   NOT NULL,
        DBCONNECTION             VARCHAR(255)   NOT NULL,
        OWNER                    VARCHAR(255)   NOT NULL,
        GSYS_SYS_ID              INTEGER        NOT NULL,
        MAX_AVAILABLE_SEQUENCE   NUMERIC(20),
        MAX_AVAILABLE_TS         INTEGER
      );
      
      CREATE TABLE STG_G_CUSTOM_DATA_S
      (
        ID               NUMERIC(19,0)   NOT NULL,
        CALLID           VARCHAR(50),
        PARTYID          VARCHAR(50),
        ROOTIRID         VARCHAR(50),
        PSEQ             INTEGER         NOT NULL,
        ENDPOINTID       INTEGER,
        ENDPOINTDN       VARCHAR(255),
        AGENTID          INTEGER,
        SWITCHID         INTEGER,
        TENANTID         INTEGER,
        KEYNAME          VARCHAR(64)     NOT NULL,
        VALUE            VARCHAR(255),
        ADDED            TIMESTAMP       NOT NULL,
        ADDED_TS         INTEGER,
        ADDED_TCODE      INTEGER,
        GSYS_DOMAIN      INTEGER,
        GSYS_PARTITION   INTEGER,
        GSYS_SYS_ID      INTEGER         NOT NULL,
        GSYS_SEQ         INTEGER,
        GSYS_USEQ        INTEGER,
        GSYS_MSEQ        INTEGER,
        GSYS_TS          TIMESTAMP,
        GSYS_TC          INTEGER,
        GSYS_EXT_VCH1    VARCHAR(255),
        GSYS_EXT_VCH2    VARCHAR(255),
        GSYS_EXT_INT1    INTEGER,
        GSYS_EXT_INT2    INTEGER,
        DBSOURCE_KEY     SMALLINT        NOT NULL,
        ETL_STATUS       VARCHAR(32),
        CONSTRAINT P_KEY_1 PRIMARY KEY (ID, GSYS_SYS_ID)
      );
      
      CREATE INDEX CDS_IRID_IDX ON STG_G_CUSTOM_DATA_S (
        ROOTIRID ASC
      );
      
      CREATE INDEX CDS_MSEQ_IDX ON STG_G_CUSTOM_DATA_S (
        GSYS_MSEQ ASC
      );
      
      CREATE INDEX CDS_CALLID_IDX ON STG_G_CUSTOM_DATA_S (
        CALLID ASC
      );
      
      CREATE TABLE STG_G_PROV_CTRL_SNAPSHOT
      (
        JOB_ID            VARCHAR(512)   NOT NULL,
        DBCONNECTION      VARCHAR(255)   NOT NULL,
        OWNER             VARCHAR(255)   NOT NULL,
        GSYS_SYS_ID       INTEGER        NOT NULL,
        PROVIDER_TAG      INTEGER        NOT NULL,
        SEQ_CURRENT       NUMERIC(20)    NOT NULL,
        MAX_PROVIDER_TS   INTEGER,
        MAX_IDB_TS        INTEGER,
        MAX_SAFE_MSEQ     NUMERIC(20)
      );
      
      UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.004.00';
      COMMIT;
      
      

    
    

17. If you are installing over release 7.6.003.08 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 218560659, 218834630):

    • Click to show/hide SQL statements for Oracle or DB2

      DELETE FROM STG_G_PARTY_HISTORY WHERE PHID = 0;
      COMMIT;
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      BEGIN TRANSACTION
      go
      
      DELETE FROM STG_G_PARTY_HISTORY WHERE PHID = 0
      go
      
      COMMIT
      go
      

    
    

18. If you are installing over release 7.6.004.09 or an earlier 7.6 release and the Staging Area database is on DB2, issue the following SQL statements against the Staging Area database (ER# 223311605):

    • Click to show/hide SQL statements for DB2

      DROP TABLE STG_ACTIVE_DT_DND_FACT;
      
      CREATE TABLE STG_ACTIVE_DT_DND_FACT (
         DT_DND_FACT_KEY      NUMERIC(19)        NOT NULL,
         GMT_ENTERPRISE_DATE_KEY INTEGER         NOT NULL,
         GMT_TENANT_DATE_KEY  INTEGER            NOT NULL,
         GMT_TIME_OF_DAY_KEY  INTEGER            NOT NULL,
         STD_ENTERPRISE_DATE_KEY INTEGER         NOT NULL,
         STD_TENANT_DATE_KEY  INTEGER            NOT NULL,
         STD_ENTERPRISE_TIME_OF_DAY_KEY INTEGER  NOT NULL,
         STD_TENANT_TIME_OF_DAY_KEY INTEGER      NOT NULL,
         TENANT_KEY           INTEGER            NOT NULL,
         MEDIA_TYPE_KEY       INTEGER            NOT NULL,
         RESOURCE_KEY         INTEGER            NOT NULL,
         MEDIA_RESOURCE_KEY   INTEGER            NOT NULL,
         PLACE_KEY            INTEGER            NOT NULL,
         CREATE_AUDIT_KEY     INTEGER            NOT NULL,
         UPDATE_AUDIT_KEY     INTEGER            NOT NULL,
         RESOURCE_SESSION_FACT_KEY NUMERIC(19),
         GMT_START_TIME       TIMESTAMP,
         GMT_END_TIME         TIMESTAMP,
         STD_ENTERPRISE_START_TIME TIMESTAMP,
         STD_ENTERPRISE_END_TIME TIMESTAMP,
         STD_TENANT_START_TIME TIMESTAMP,
         STD_TENANT_END_TIME  TIMESTAMP,
         TOTAL_DURATION       INTEGER,
         ACTIVE_FLAG          NUMERIC(1),
         CREATED_TS           INTEGER,
         TERMINATED_TS        INTEGER,
         LOGINSESSIONID       VARCHAR(50),
         AGENTID              INTEGER,
         ENDPOINTID           INTEGER,
         MEDIA_TYPE           INTEGER,
         OM_TYPE              VARCHAR(255),
         CONSTRAINT P_KEY_1 PRIMARY KEY (DT_DND_FACT_KEY)
      );
      
      CREATE INDEX ACT_DT_DND_IDX_1 ON STG_ACTIVE_DT_DND_FACT (
         LOGINSESSIONID       ASC
      );
      

    
    

19. If you are installing over release 7.6.004.13 or an earlier 7.6 release, issue the following SQL statements against the Staging Area database (ER# 226459195):

    • Click to show/hide SQL statements for Oracle or DB2

      CREATE INDEX STG_IDX_DN_PLACE ON STG_DNSINAPLACE (
         DN_CFG_DBID ASC,
         PLACE_CFG_DBID ASC
      );
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      CREATE INDEX STG_IDX_DN_PLACE ON STG_DNSINAPLACE (
        DN_CFG_DBID ASC,
        PLACE_CFG_DBID ASC
      )
      go
      

    
    

20. If you are installing over release 7.6.004.13 or an earlier 7.6 release, issue the following SQL statements against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE (ER# 227546437):

    • Click to show/hide SQL statements for Oracle or DB2

      CREATE INDEX GIM_IDX_CALL_HA_LIST ON G_CALL (
         IRID        ASC,
         MEDIATYPE   ASC,
         TENANTID    ASC,
         CALLID      ASC
      );
      
      CREATE INDEX GIM_IDX_PARTY_HA_LIST ON G_PARTY (
         CALLID    ASC,
         PARTYID   ASC
      );

    • Click to show/hide SQL statements for Microsoft SQL Server

      CREATE INDEX GIM_IDX_CALL_HA_LIST ON G_CALL (
         IRID        ASC,
         MEDIATYPE   ASC,
         TENANTID    ASC,
         CALLID      ASC
      )
      go
      
      CREATE INDEX GIM_IDX_PARTY_HA_LIST ON G_PARTY (
         CALLID    ASC,
         PARTYID   ASC
      )
      go

    
    
21. If you are installing over release 7.6.004.14 or an earlier 7.6 release, issue the following SQL statements against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE, ICON_MM, or ICON_OCS (ER# 225783911):
    

    ICON_CORE

    • Click to show/hide SQL statements for Oracle or DB2

      drop index GIM_IDX_ASH_USEQ  ;
      drop index GIM_IDX_ASRC_USEQ ;
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      drop index G_AGENT_STATE_HISTORY.GIM_IDX_ASH_USEQ
      go
      drop index G_AGENT_STATE_RC.GIM_IDX_ASRC_USEQ
      go
      

    
    

    ICON_MM

    • Click to show/hide SQL statements for Oracle or DB2

      drop index GIM_IDX_GMF_USEQ  ;
      drop index GIM_IDX_GML_USEQ  ;
      drop index GIM_IDX_PHIS_USEQ ;
      drop index GIM_IDX_UH_USEQ   ;
      drop index GIM_IDX_SUH_USEQ  ;
      drop index GIM_IDX_ASH_USEQ  ;
      drop index GIM_IDX_ASRC_USEQ ;
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      drop index GM_F_USERDATA.GIM_IDX_GMF_USEQ
      go
      drop index GM_L_USERDATA.GIM_IDX_GML_USEQ
      go
      drop index G_PARTY_HISTORY.GIM_IDX_PHIS_USEQ
      go
      drop index G_USERDATA_HISTORY.GIM_IDX_UH_USEQ
      go
      drop index G_SECURE_USERDATA_HISTORY.GIM_IDX_SUH_USEQ
      go
      drop index G_AGENT_STATE_HISTORY.GIM_IDX_ASH_USEQ
      go
      drop index G_AGENT_STATE_RC.GIM_IDX_ASRC_USEQ
      go
      

    
    

    ICON_OCS

    • Click to show/hide SQL statements for Oracle or DB2

      drop index GIM_IDX_GOFH_USEQ  ;
      drop index GIM_IDX_GOCRH_USEQ ;
      drop index GIM_IDX_GOMET_USEQ ;
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      drop index GO_FIELDHIST.GIM_IDX_GOFH_USEQ
      go
      drop index GO_CHAINREC_HIST.GIM_IDX_GOCRH_USEQ
      go
      drop index GO_METRICS.GIM_IDX_GOMET_USEQ
      go

    
    

22. If you are installing over release 7.6.004.14 or an earlier 7.6 release, issue the following SQL statements against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE (ER# 227766321):

    • Click to show/hide SQL statements for Oracle or DB2

      drop index GIM_IDX_IR_MSTATE;
      
      create index GIM_IDX_IR_MSTATE on G_IR (
         GSYS_MSEQ    ASC,
         MERGESTATE   ASC,
         CREATED_TS    ASC
      );
      

    • Click to show/hide SQL statements for Microsoft SQL Server

      drop index G_IR.GIM_IDX_IR_MSTATE
      go
      
      create index GIM_IDX_IR_MSTATE on G_IR (
         GSYS_MSEQ    ASC,
         MERGESTATE   ASC,
         CREATED_TS    ASC
      )
      go
      

    
    

23. If you are installing over release 7.6.004.14 or an earlier 7.6 release, execute the upgrade_gim_76002_thru_76004_to_76005.sql script against the Info Mart database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 208829385, 224984829, 207557859, 224160161)

24. If you are installing over release 7.6.005.12 or an earlier 7.6 release, issue the following SQL statements against each Interaction Database (IDB) with Database Access Point role equal to ICON_CORE or ICON_MM if the database is on Microsoft SQL Server:

    • Click to show/hide SQL statements for Microsoft SQL Server

      DROP INDEX G_USERDATA_HISTORY.GIM_IDX_UH_CALLID
      go
      
      DROP INDEX G_SECURE_USERDATA_HISTORY.GIM_IDX_SUH_CALLID
      go
      
      CREATE INDEX GIM_IDX_UH_CALLID ON G_USERDATA_HISTORY (
         CALLID     ASC,
         KEYID      ASC,
         CHANGETYPE ASC
      )
      go
      
      CREATE INDEX GIM_IDX_SUH_CALLID ON G_SECURE_USERDATA_HISTORY (
         CALLID     ASC,
         KEYID      ASC,
         CHANGETYPE ASC
      )
      go
      

    
    

25. If you are installing over release 7.6.005.12 or an earlier 7.6 release, execute the upgrade_merging_to_76006.sql script against the Merge Staging Area schema, if you have one configured. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 227541181, 121883861)

26. If you are installing over release 7.6.005.12 or an earlier 7.6 release, execute the upgrade_stg_76004_thru_76005_to_76006.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 230639921, 229717291, 232148971)

27. If you are installing over release 7.6.005.12 or an earlier 7.6 release, execute the upgrade_gim_76005_to_76006.sql script against the Info Mart database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

28. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the make_icon_cfg_indexes_for_gim.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CFG. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 235721405)

29. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the upgrade_icon_indexes_for_gim_76005_thru_76006_to_76007.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE or ICON_MM. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 235721405)

30. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the upgrade_iconmm_indexes_for_gim_76005_thru_76006_to_76007.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_MM. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 235721405)

31. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the upgrade_icon_ocs_indexes_for_gim_76005_thru_76006_to_76007.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_OCS. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 235721405)

32. If you are installing over release 7.6.006.19 or an earlier 7.6 release, execute the upgrade_stg_76006_to_76007.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 237376182, 238593940)

33. If you are installing over release 7.6.007.13 or an earlier 7.6 release and are using the new functionality introduced in the Genesys Info Mart 7.6 Maintenance Release 3 (release number 7.6.004.07) to extract UserEvent-based key-value pair data associated with voice interactions, execute the upgrade_icon_indexes_for_gim_76007_to_76008.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 246126748)

34. If you are installing over release 7.6.007.14 or an earlier 7.6 release, execute the upgrade_stg_76007_to_76008.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 235721401, 199733383)

35. If you are installing over release 7.6.008.15 or an earlier 7.6 release, execute the upgrade_gim_76006_thru_76008_to_76009.sql script against the Info Mart database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

36. If you are installing over release 7.6.009.09 or an earlier 7.6 release, execute the upgrade_stg_76008_thru_76009_to_76010.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 252456451)

37. If you are installing over release 7.6.010.10 or an earlier 7.6 release, execute the upgrade_icon_indexes_for_gim_76008_thru_76010_to_76011.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

38. If you are installing over release 7.6.010.10 or an earlier 7.6 release, execute the upgrade_stg_76010_to_76011.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 262028811)

39. If you are installing over release 7.6.011.09 or an earlier 7.6 release, execute the upgrade_stg_76011_to_76012.sql script against the Staging Area database. If your deployment does not include any GVP VAR data sources, uncomment the DROP INDEX statement in the script before running the script. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 268076163)

40. If you are installing over release 7.6.011.09 or an earlier 7.6 release, execute the load_gim_staging_area.sql script against the Staging Area database. If Genesys Info Mart has been configured to use 15-minute level aggregates, then also execute the load_gim_staging_area_15.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 242363776, 249217428)

41. If you are installing over release 7.6.011.09 or an earlier 7.6 release, execute the upgrade_gim_76009_thru_76011_to_76012.sql script against the Info Mart database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

42. If you are installing over release 7.6.011.09 or an earlier 7.6 release, execute the make_gim_agg_views_30.sql script against the Info Mart database if Genesys Info Mart has been configured to use 30-minute level aggregates, or execute the make_gim_agg_views_15.sql script if Genesys Info Mart has been configured to use 15-minute level aggregates. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER#s 233795116, 235625870, 246948595, 249217428)

43. If you are installing over release 7.6.011.09 or an earlier 7.6 release, and your deployment uses the read-only views for the Info Mart database data created by make_gim_view.sql and make_gim_view_for_tenant.sql, perform the procedures documented in "Preparing the Info Mart Database Read-Only Views" and "Creating Genesys Info Mart Tenant Views" in the Genesys Info Mart 7.6 Deployment Guide to recreate all of the read-only views.

44. If you are installing over release 7.6.012.15 or an earlier 7.6 release and are using the functionality introduced in the Genesys Info Mart 7.6 Maintenance Release 3 (release number 7.6.004.07) to extract UserEvent-based key-value pair data associated with voice interactions, execute the upgrade_icon_indexes_for_gim_76011_thru_76012_to_76013.sql script against each Interaction Concentrator database (IDB) with the Database Access Point role equal to ICON_CORE. The SQL statements in the script are commented out by default. Make sure to uncomment those statements before you run the SQL script so that the index gets created. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 270486243)

45. If you are installing over release 7.6.012.15 or an earlier 7.6 release, execute the upgrade_gim_76012_to_76013.sql script against the Info Mart database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle. (ER# 270651652)

46. If you are installing over release 7.6.013.08 or an earlier 7.6 release, execute the upgrade_stg_76012_thru_76013_to_76014.sql script against the Staging Area database. To locate the SQL script, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle.

47. Restart the Genesys Info Mart Server.

48. If you are installing over release 7.6.013.08 or an earlier 7.6 release, manually run Job_InitializeGIM using the Genesys Info Mart Administration Console. (ER# 272325553)

49. Set the run-scheduler configuration option to TRUE in the schedule section of the Genesys Info Mart Application object to resume the Genesys Info Mart Server schedule.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software.

• Genesys Info Mart 7.6 Release Advisory provides important information that applies to the entire Genesys Info Mart release.

• Genesys Info Mart 7.6 Deployment Guide includes installation procedures for the Genesys Info Mart Administration Console and Genesys Info Mart and acquaints you with their functions.

• Genesys Info Mart 7.6 Operations Guide describes the procedures for using the Genesys Info Mart Administration Console to monitor ETL job status and, when necessary, to start or stop an ETL job outside of the normal schedule.

• Genesys Info Mart 7.6 Reference Manual for your RDBMS acquaints you with the subject areas, tables, and fields that make up the Genesys Info Mart star schemas.

• Genesys Info Mart 7.6 User's Guide provides examples of common voice and multimedia interactions.

• Genesys Info Mart 7.6 SQL Queries provides sample SQL queries, descriptions, and lists of Fact and Dimension tables that each sample accesses.

• The Genesys Info Mart section of the Framework 7.6 Combined Log Events Help provides detailed information on the log events associated with Genesys Info Mart.

• Genesys Migration Guide includes installation procedures for the Genesys Info Mart Administration Console and upgrade procedures for Genesys Info Mart.

If you encounter any issues with the deployment of this package, please contact Genesys Customer Care.

Top of Page