To deploy this release of Genesys Info Mart, do one of the following, depending on your current release:
Note: Review all the 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
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.
Wait for any currently running jobs to finish. Use the Genesys Info Mart Administration Console to monitor the completion of the jobs.
Stop the Genesys Info Mart Server.
Create backup copies of both your Staging Area and Info Mart databases.
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 .
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
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 ).
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.
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
);
If you are installing over release 7.6.001.07, issue the following SQL statements against each Interaction Concentrator (IDB) with Database Access Point role equal to ICON_CORE (ER# 207130586):
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
);
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;
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):
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);
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):
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):
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;
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;
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 (IDB)
with Database Access Point role equal to ICON_CORE (ER# 205973400):
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 (IDB) with Database Access Point role equal to ICON_CORE or ICON_MM (ER# 183662866):
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;
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;
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):
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):
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 (IDB) with the Database Access Point role equal to ICON_CORE. (ER # 227546437):
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)
If you are installing over release 7.6.004.14 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 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 .
- 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 (IDB) with the Database Access Point role equal to
ICON_CORE , ICON_MM , or ICON_OCS . (ER #225783911)
ICON_CORE
ICON_OCS
ICON_MM
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):
If you are installing over release 7.6.004.14 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 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 .
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 (IDB) with the Database Access Point role equal to ICON_CORE. (ER # 227766321):
If you are installing over release 7.6.004.14 or an earlier 7.6 release, issue the following SQL statements against the Merge Staging Area schema, if you have one configured. (ER 227541181):
Restart the Genesys Info Mart Server.
If you are installing over release 7.6.004.14 or an earlier 7.6 release, manually run Job_InitializeGIM using the Genesys Info Mart Administration Console.
-
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
|