Release Number | Date | Release Type |
---|---|---|
8.1.402.11 | 06/22/17 | Hot Fix |
8.1.402.10 | 08/31/15 | Hot Fix |
8.1.402.09 | 06/19/15 | Hot Fix |
8.1.402.08 | 03/13/15 | Hot Fix |
8.1.402.07 | 11/24/14 | General |
8.1.401.05 | 10/24/14 | Hot Fix |
8.1.401.02 | 09/22/14 | General |
8.1.400.12 | 07/30/14 | General |
8.1.301.07 | 07/02/14 | Hot Fix |
8.1.301.06 | 04/23/14 | Hot Fix |
8.1.301.05 | 03/20/14 | Hot Fix |
8.1.301.04 | 03/06/14 | General |
8.1.300.14 | 12/23/13 | General |
8.1.202.04 | 11/08/13 | Hot Fix |
8.1.202.03 | 09/30/13 | Hot Fix |
8.1.202.01 | 08/23/13 | General |
8.1.201.06 | 07/12/13 | Hot Fix |
8.1.201.05 | 06/21/13 | Hot Fix |
8.1.201.02 | 04/25/13 | General |
8.1.200.21 | 03/18/13 | General |
8.1.103.07 | 02/04/13 | Hot Fix |
8.1.103.05 | 12/14/12 | Hot Fix |
8.1.103.03 | 10/30/12 | General |
8.1.102.02 | 09/05/12 | General |
8.1.101.07 | 08/20/12 | Hot Fix |
8.1.101.05 | 07/23/12 | Hot Fix |
8.1.101.04 | 07/11/12 | General |
8.1.002.08 | 04/12/13 | Hot Fix |
8.1.002.07 | 07/06/12 | Hot Fix |
8.1.002.05 | 04/30/12 | Hot Fix |
8.1.002.03 | 04/02/12 | Hot Fix |
8.1.002.02 | 02/10/12 | General |
8.1.001.07 | 01/17/12 | Hot Fix |
8.1.001.05 | 12/20/11 | General |
8.1.000.28 | 11/18/11 | Hot Fix |
8.1.000.25 | 10/07/11 | General |
This deployment procedure applies to the releases of Genesys Info Mart listed in the Release table, above. Click the link in the Release table for the version you are deploying to jump to a description of how to deploy Genesys Info Mart using the package you received from Genesys. Most releases use the same standard deployment procedure.
If your release requires a specialized procedure, the link in the Release table takes you to a header specifying the version number and date of the release. Click the header, and the procedure will open.
To deploy this installation package within a new environment, follow the instructions in the Genesys Info Mart 8.1 Deployment Guide.
To deploy this package in your existing Genesys Info Mart 8.x environment, follow all of the Pre-Installation and Installation steps in the Standard Deployment Procedure that follows.
Notes:
Review all steps before you perform 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.
The Interaction Database (IDB) schema might need to be updated as part of the migration. To minimize the possibility of deadlocks or concurrency problems, plan to execute your migration at a time when there is little activity on the IDBs, such as during off-peak hours or after hours (but not during IDB maintenance, when purge stored procedures will be running).
If you are migrating Genesys Info Mart in a deployment in which you use or plan to use Genesys-provided aggregation, review the Reporting and Analytics Aggregates (RAA) and Genesys Interactive Insights (GI2) Release Notes and Release Advisories, for information about the impact of Genesys Info Mart migration on aggregation, as well as workarounds or additional steps to take during Genesys Info Mart migration.
For reference purposes, identify and make notes of any custom changes that you made to the Info Mart database—for example, table spaces, partitions, additional indexes, views, or permissions.
The Genesys Info Mart SQL scripts that you will run to update these databases sometimes create new tables, instead of updating the old tables. They may also replace some tables with views, for backward compatibility. You will need to re-create any custom database objects or permissions that become lost or invalidated during the update process.
For reference purposes, create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.
The default location for these scripts is the sql_scripts
directory within the Genesys Info Mart installation directory.
For reference purposes, identify and make notes of any custom changes that you made to the Genesys Info Mart Application
object.
You might need to transfer customizations in your Genesys Info Mart deployment for the new Genesys Info Mart release.
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.
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.
If your system includes a second instance of
Genesys Info Mart Server in the active-active configuration, ensure that the ETL cycle has been suspended on both servers,
to prevent possible concurrency problems if the IDB(s) need to be updated as part of the migration and the second Genesys Info Mart Server
attempts to extract from an IDB while the update_IDB
script is running.
Note: Stopping the Genesys Info Mart server does not result in data loss. As long as all ongoing interaction data is stored in IDBs, Genesys Info Mart will process that data after you complete the migration.
If you are using Genesys-provided aggregation, stop the aggregation job. If the aggregation job is running in automated mode:
run-aggregates
option to FALSE
in the [schedule]
section of the Genesys Info Mart Application
object.Wait for any currently running jobs to finish. Use the Genesys Info Mart Manager to monitor completion of the jobs. To do so, open
Genesys Info Mart Manager and periodically click Refresh
to check the updated status of the jobs.
Note: The aggregation job might take a long time to complete. If this is the case, proceed with the next step as soon as all other jobs finish.
Stop the Genesys Info Mart Server.
Create a backup copy of your Info Mart database.
If necessary, migrate Interaction Concentrator. For information about the minimum Interaction Concentrator release that is required for the Genesys Info Mart release to which you are migrating, see the Genesys Info Mart 8.x Release Notes.
Install the new Genesys Info Mart installation package:
Control Panel > Add/Remove Programs
.
Then run setup
to install the new Genesys Info Mart installation package.
Overwrite only the files contained in this package
).
In the Release Note, review the "New in This Release" section for the release to which you are upgrading.
Identify if any configuration option changes affect customizations that you may have made in your Genesys Info Mart deployment.
If necessary, modify configuration settings in the Genesys Info Mart Application
or other configuration objects, as required, to transfer custom settings for your deployment.
Because release 8.1.x no longer uses relative values to determine when calendar dimensions start
(for example, date-time-start-year = -1
is no longer valid), verify the validity of the date-time-start-year
setting for existing calendars.
If you used a relative value for the date-time-start-year
option in the [date-time]
and any custom [date-time-*]
sections, change the setting to the appropriate absolute value.
Otherwise, an error will be generated when Genesys Info Mart performs the configuration check.
(For Oracle users only) If you are migrating from a release earlier than 8.1.103.05, grant permissions to the Info Mart database user by issuing the following commands against the Info Mart database:
GRANT
CREATE SESSION,
CREATE PROCEDURE,
CREATE SEQUENCE,
CREATE TABLE,
CREATE VIEW to <Info Mart user>;
GRANT EXECUTE ON DBMS_LOCK to <Info Mart user>;
Restore any customizations in startup arguments, start the Genesys Info Mart Server, and check for error messages:
InfoMart database schema version is out-of-date
," or if
you find log message 55-20152 ("GIM Server - current state is MIGRATION
")
or 55-20034 ("...database schema version...is not up to date...
"),
you must run Job_MigrateGIM
to
upgrade the Info Mart database schema and, if necessary, automatically execute the scripts to update IDBs.
Continue with Step 5.
InfoMart database schema version is out-of-date
" or
log message 55-20152 or 55-20034, continue with Step 9.
Note: Genesys recommends that you set an alarm condition for log event 55-20152.
If you need to run Job_MigrateGIM,
Genesys Info Mart Server will automatically be in the correct state to perform the migration.
Warning! From this point onward, the Info Mart database should not be accessed by report queries or other scheduled activities, such as custom aggregation, until the migration job is complete. Doing otherwise would interfere with the migration process, which will be modifying database tables, views, and indexes. If your system includes a second instance of Genesys Info Mart Server in the active-active configuration, ensure that the ETL cycle has been suspended on both servers.
Launch Job_MigrateGIM
from the Genesys Info Mart Manager.
To do so, perform the following steps:
Run Job
to open the Run Job
dialog box. Job_MigrateGIM
.OK
.Allow this job to complete before continuing.
Notes:
If Job_MigrateGIM
does not complete successfully, do the following:
Job_MigrateGIM
failed because of deadlocks or
concurrency problems on IDB, there are additional steps you might be
able to take to prevent such issues.
For more information, see “Preventing Deadlocks on IDB During
Genesys Info Mart Migration” in the “Genesys Info Mart 8.x Migration
Procedures” chapter in the Genesys Migration Guide.If you decide to terminate the migration process, restore:
Job_MigrateGIM
when you do not need to do so, Genesys Info Mart will silently ignore the command to launch the job.If you stopped ICON as part of the migration preliminaries related to preventing deadlocks or concurrency problems on IDB, start ICON.
If your deployment uses read-only views, you must re-create the read-only views after the migration job completes. For more information, see the section about creating Genesys Info Mart read-only views in the Genesys Info Mart 8.1 Deployment Guide.
If your deployment uses Genesys-provided aggregation, in addition to re-creating the Info Mart tenant views (see Step 7), you must also update the tenant aliases.
For more information, see the description of the updateAliases
runtime parameter in the Reporting and Analytics Aggregates Deployment Guide
and the section about updating tenant aliases in the Reporting and Analytics Aggregates User’s Guide.
Review the "New in This Release" sections in the Release Notes and in the Genesys Info Mart 8.x Reference Manuals for your RDBMS, and make any changes to the database schema values or to downstream reporting applications that may require action as part of the migration process.
For example, if you are migrating to release 8.1.x directly from release 8.0.0, you might need to check the values of the IS_ONLINE
column in the MEDIA_TYPE
table to see whether all media types are correctly identified as online
(real-time communication, such as chat) or offline (responses may be
deferred, such as e-mail).
Be aware that Genesys Info Mart migration does not go back to manipulate existing data (in other words, data that was processed before migration). In particular:
If you are migrating from release 8.1.0 or 8.1.1, be aware that Genesys Info Mart creates new CTL_AUDIT_LOG
and
CTL_*_HISTORY
tables during the migration.
Genesys Info Mart renames the existing tables to CTL_*_BK
and retains them for reference.
CTL_AUDIT_LOG
table for
postprocessing (for example, to move data from the Info Mart database to
a data warehouse or to support custom aggregation),
verify that CTL_AUDIT_LOG_BK
does not contain any unprocessed audit keys.
If you find any unprocessed audit keys, copy them from CTL_AUDIT_LOG_BK
to the new CTL_AUDIT_LOG
table.
CTL_*_BK
tables when you are satisfied that you no longer need them for reference purposes or backup.
Be aware that, during migration from release 8.1.3 or earlier to release 8.1.4:
STG_TRANSFORM_DISCARDS
table, renaming the existing table to
STG_TRANSFORM_DISCARDS_BK
.
GIDB_G_IR_MM
, GIDB_G_CALL_MM
, GIDB_G_ROUTE_RESULT_MM
,
GIDB_G_VIRTUAL_QUEUE_MM
, GIDB_G_PARTY_MM
, and GIDB_G_PARTY_HISTORY_MM
tables,
renaming the existing tables to GIDB_G_*_MM_BK
.
Genesys Info Mart populates the new GIDB_G_*_MM
tables by copying over, from the existing tables, only active interaction
data that has not yet been transformed. Genesys Info Mart retains the *_BK
tables for reference.
Delete them when you are satisfied that you no longer need them for reference purposes or backup.
During migration from 8.1.3 or earlier to 8.1.400, the content of these tables was not preserved.GIDB_G_*_MM_BK
tables as soon as possible. The GIDB_G_*_MM_BK
tables that are created during such a migration might significantly slow down purge, causing the maintenance job to not complete
within the configured maintenance window, resulting in job errors when the ETL cycle resumes.
If the Genesys Info Mart database is partitioned, launch Job_MaintainGIM
from the Genesys Info Mart Manager. To do so, perform the following steps:
Run Job
to open the Run Job
dialog box. Job_MaintainGIM
.OK
.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.
If you are using Genesys-provided aggregation, set the run-aggregates
configuration option to TRUE
in
the [schedule]
section of the Genesys Info Mart Application
object, to resume running the aggregation job in automated mode.
To deploy this installation package within a new environment, follow the instructions in the Genesys Info Mart 8.1 Deployment Guide.
To deploy this package in your existing Genesys Info Mart 8.x environment, follow all of the Pre-Installation and Installation steps in the Standard Deployment Procedure that follows.
Notes:
Review all steps before you perform 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.
The Interaction Database (IDB) schema might need to be updated as part of the migration. To minimize the possibility of deadlocks or concurrency problems, plan to execute your migration at a time when there is little activity on the IDBs, such as during off-peak hours or after hours (but not during IDB maintenance, when purge stored procedures will be running).
If you are migrating Genesys Info Mart in a deployment in which you use or plan to use Genesys-provided aggregation, review the Reporting and Analytics Aggregates (RAA) and Genesys Interactive Insights (GI2) Release Notes and Release Advisories, for information about the impact of Genesys Info Mart migration on aggregation, as well as workarounds or additional steps to take during Genesys Info Mart migration.
For reference purposes, identify and make notes of any custom changes that you made to the Info Mart database—for example, table spaces, partitions, additional indexes, views, or permissions.
The Genesys Info Mart SQL scripts that you will run to update these databases sometimes create new tables, instead of updating the old tables. They may also replace some tables with views, for backward compatibility. You will need to re-create any custom database objects or permissions that become lost or invalidated during the update process.
For reference purposes, create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.
The default location for these scripts is the sql_scripts
directory within the Genesys Info Mart installation directory.
For reference purposes, identify and make notes of any custom changes that you made to the Genesys Info Mart Application
object.
You might need to transfer customizations in your Genesys Info Mart deployment for the new Genesys Info Mart release.
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.
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.
Note: Stopping the Genesys Info Mart server does not result in data loss. As long as all ongoing interaction data is stored in IDBs, Genesys Info Mart will process that data after you complete the migration.
If you are using Genesys-provided aggregation, stop the aggregation job. If the aggregation job is running in automated mode:
run-aggregates
option to FALSE
in the [schedule]
section of the Genesys Info Mart Application
object.Wait for any currently running jobs to finish. Use the Genesys Info Mart Administration Console to monitor completion of the jobs.
Note: The aggregation job might take a long time to complete. If this is the case, proceed with the next step as soon as all other jobs finish.
Stop the Genesys Info Mart Server.
Create a backup copy of your Info Mart database.
If necessary, migrate Interaction Concentrator. For information about the minimum Interaction Concentrator release that is required for the Genesys Info Mart release to which you are migrating, see the Genesys Info Mart 8.x Release Notes.
Install the new Genesys Info Mart installation package:
Control Panel > Add/Remove Programs
.
Then run setup
to install the new Genesys Info Mart installation package.
Overwrite only the files contained in this package
).
In the Release Note, review the "New in This Release" section for the release to which you are upgrading.
Identify if any configuration option changes affect customizations that you may have made in your Genesys Info Mart deployment.
If necessary, modify configuration settings in the Genesys Info Mart Application
or other configuration objects, as required, to transfer custom settings for your deployment.
Because release 8.1.x no longer uses relative values to determine when calendar dimensions start
(for example, date-time-start-year = -1
is no longer valid), verify the validity of the date-time-start-year
setting for existing calendars.
If you used a relative value for the date-time-start-year
option in the [date-time]
and any custom [date-time-*]
sections, change the setting to the appropriate absolute value.
Otherwise, an error will be generated when Genesys Info Mart performs the configuration check.
(For Oracle users only) If you are migrating from a release earlier than 8.1.103.05, grant permissions to the Info Mart database user by issuing the following commands against the Info Mart database:
GRANT
CREATE SESSION,
CREATE PROCEDURE,
CREATE SEQUENCE,
CREATE TABLE,
CREATE VIEW to <Info Mart user>;
GRANT EXECUTE ON DBMS_LOCK to <Info Mart user>;
Restore any customizations in startup arguments, start the Genesys Info Mart Server, and review the Genesys Info Mart log.
"GIM Server - current state is MIGRATION"
) or 55-20034 ("...database schema version...is not up to date..."
), you must run Job_MigrateGIM
to upgrade the Info Mart database schema and, if necessary, automatically execute the scripts to update IDBs.
Continue with Step 5.
Note: Genesys recommends that you set an alarm condition for log event 55-20152.
If you need to run Job_MigrateGIM,
Genesys Info Mart Server will automatically be in the correct state to perform the migration.
Warning! From this point onward, the Info Mart database should not be accessed by report queries or other scheduled activities, such as custom aggregation, until the migration job is complete. Doing otherwise would interfere with the migration process, which will be modifying database tables, views, and indexes.
Launch Job_MigrateGIM
from the Genesys Info Mart Administration Console v8.0.100.04 or higher.
To do so, perform the following steps:
Schedule
tab.Run Job…
. Job_MigrateGIM
.Allow this job to complete before continuing.
Notes:
If Job_MigrateGIM
does not complete successfully, do the following:
Job_MigrateGIM
failed because of deadlocks or
concurrency problems on IDB, there are additional steps you might be
able to take to prevent such issues.
For more information, see “Preventing Deadlocks on IDB During
Genesys Info Mart Migration” in the “Genesys Info Mart 8.x Migration
Procedures” chapter in the Genesys Migration Guide.If you decide to terminate the migration process, restore:
Job_MigrateGIM
when you do not need to do so, Genesys Info Mart will silently ignore the command to launch the job.If you stopped ICON as part of the migration preliminaries related to preventing deadlocks or concurrency problems on IDB, start ICON.
If your deployment uses read-only views, you must re-create the read-only views after the migration job completes. For more information, see the section about creating Genesys Info Mart read-only views in the Genesys Info Mart 8.1 Deployment Guide.
If your deployment uses Genesys-provided aggregation, in addition to re-creating the Info Mart tenant views (see Step 7), you must also update the tenant aliases.
For more information, see the description of the updateAliases
runtime parameter in the Reporting and Analytics Aggregates Deployment Guide
and the section about updating tenant aliases in the Reporting and Analytics Aggregates User’s Guide.
Review the "New in This Release" sections in the Release Notes and in the Genesys Info Mart 8.x Reference Manuals for your RDBMS, and make any changes to the database schema values or to downstream reporting applications that may require action as part of the migration process.
For example, if you are migrating to release 8.1.x directly from release 8.0.0, you might need to check the values of the IS_ONLINE
column in the MEDIA_TYPE
table to see whether all media types are correctly identified as online
(real-time communication, such as chat) or offline (responses may be
deferred, such as e-mail).
Be aware that Genesys Info Mart migration does not go back to manipulate existing data (in other words, data that was processed before migration). In particular:
If you are migrating from release 8.1.0 or 8.1.1 to release 8.1.2 or 8.1.3, be aware that Genesys Info Mart creates new CTL_AUDIT_LOG
and CTL_*_HISTORY
tables during the migration.
Genesys Info Mart renames the existing tables to CTL_*_BK
and retains them for reference.
CTL_AUDIT_LOG
table for
postprocessing (for example, to move data from the Info Mart database to
a data warehouse or to support custom aggregation),
verify that CTL_AUDIT_LOG_BK
does not contain any unprocessed audit keys.
If you find any unprocessed audit keys, copy them from CTL_AUDIT_LOG_BK
to the new CTL_AUDIT_LOG
table.
CTL_*_BK
tables when you are satisfied that you no longer need them for reference purposes or backup.
If you are migrating to release 8.1.200.21 in an Oracle deployment with a partitioned Info Mart database, execute the following SQL statements to prevent a possible post-migration problem because of unavailable partitions:
begin execute immediate 'alter table CTL_AUDIT_LOG add
PARTITION GIM__MAXVALUE VALUES LESS THAN(MAXVALUE)'; exception when
others then if sqlcode in (-14074) then null; else raise; end if; end;
begin execute immediate 'alter table CTL_ETL_HISTORY add PARTITION
GIM__MAXVALUE VALUES LESS THAN(MAXVALUE)'; exception when others then if
sqlcode in (-14074) then null; else raise; end if; end;
Job_MaintainGIM
from the Genesys 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.
If you are using Genesys-provided aggregation, set the run-aggregates
configuration option to TRUE
in the [schedule]
section of the Genesys Info Mart Application
object, to resume running the aggregation job in automated mode.
To deploy this installation package within a new environment, follow the instructions in the Genesys Info Mart 8.1 Deployment Guide.
To deploy this package in your existing Genesys Info Mart 8.x environment, follow all of the Pre-Installation and Installation steps in the Standard Deployment Procedure that follows.
Notes:
Review all steps before you perform 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.
If you are migrating Genesys Info Mart in a deployment in which you use or plan to use Genesys-provided aggregation, review the Reporting and Analytics Aggregates (RAA) and Genesys Interactive Insights (GI2) Release Notes and Release Advisories, for information about the impact of Genesys Info Mart migration on aggregation, as well as workarounds or additional steps to take during Genesys Info Mart migration.
For reference purposes, identify and make notes of any custom changes that you made to the Info Mart database—for example, table spaces, partitions, additional indexes, views, or permissions.
The Genesys Info Mart SQL scripts that you will run to update these databases sometimes create new tables, instead of updating the old tables. They may also replace some tables with views, for backward compatibility. You will need to re-create any custom database objects or permissions that become lost or invalidated during the update process.
For reference purposes, create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.
The default location for these scripts is the sql_scripts
directory within the Genesys Info Mart installation directory.
For reference purposes, identify and make notes of any custom changes that you made to the Genesys Info Mart Application
object. You might need to transfer customizations in your Genesys Info Mart deployment for the new Genesys Info Mart release.
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.
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.
Note: Stopping the Genesys Info Mart server does not result in data loss. As long as all ongoing interaction data is stored in Interaction Databases (IDBs), Genesys Info Mart will process that data after you complete the migration.
Verify that Genesys Info Mart has transformed all extracted data. If necessary, rerun the transformation job manually. For information about running a job on an unscheduled basis, see the chapter about working with jobs in the Genesys Info Mart Operations Guide.
If you are using Genesys-provided aggregation, stop the aggregation job. If the aggregation job is running in automated mode:
run-aggregates
option to FALSE
in the [schedule]
section of the Genesys Info Mart Application
object.Wait for any currently running jobs to finish. Use the Genesys Info Mart Administration Console to monitor completion of the jobs.
Note: The aggregation job might take a long time to complete. If this is the case, proceed with the next step as soon as all other jobs finish.
Stop the Genesys Info Mart Server.
Create a backup copy of your Info Mart database.
If necessary, migrate Interaction Concentrator. For information about the minimum Interaction Concentrator release that is required for the Genesys Info Mart release to which you are migrating, see the Genesys Info Mart 8.x Release Notes.
Install the new Genesys Info Mart installation package:
Control Panel > Add/Remove Programs
. Then run setup
to install the new Genesys Info Mart installation package.Overwrite only the files contained in this package
).Review the "New in This Release" information in the Genesys Info Mart 8.1 Deployment Guide.
Identify if any configuration option changes affect customizations that
you may have made in your Genesys Info Mart deployment. If necessary,
modify configuration settings in the Genesys Info Mart Application
or other configuration objects, as required, to transfer custom settings for your deployment.
Because release 8.1.x no longer uses relative values to determine when calendar dimensions start
(for example, date-time-start-year = -1
is no longer valid), verify the validity of the date-time-start-year
setting for existing calendars.
If you used a relative value for the date-time-start-year
option in the [date-time]
and any custom [date-time-*]
sections, change the setting to the appropriate absolute value.
Otherwise, an error will be generated when Genesys Info Mart performs the configuration check.
For each IDB from which Genesys Info Mart will extract ICON
details, run the appropriate Genesys Info Mart–provided SQL
scripts—located in the <GIM root>/sql_scripts/<dbms>
folder—to add to each IDB the views and indexes that Genesys Info Mart requires.
update_idb_for_gim.sql
.update_idb_for_gim_mm.sql
.update_idb_for_gim.sql
or update_idb_for_gim_mm.sql
.Note: If the scripts do not complete correctly, analyze the problem by referring to the log file, resolve any issues, and then run the update script again. If problems persist, or if for any reason you decide to terminate the migration process, run the update script from your pre-migration release of Genesys Info Mart.
(For Oracle users only) If you are migrating from a release earlier than 8.1.103.05, grant permissions to the Info Mart database user using the following commands:
GRANT
CREATE SESSION,
CREATE PROCEDURE,
CREATE SEQUENCE,
CREATE TABLE,
CREATE VIEW to <Info Mart user>;
GRANT EXECUTE ON DBMS_LOCK to <Info Mart user>;
(For Oracle users only) If you are migrating to release 8.1.101.07 or earlier 8.1.1 release, manually configure the jdbc-url
option in the [gim-etl]
section
on the Options
tab of all DAPs that Genesys Info Mart uses, to ensure that Genesys Info Mart will use the correct JDBC connection parameters.
For more information about configuring the jdbc-url
option, see the chapter about configuring DAPs in the Genesys Info Mart 8.1 Deployment Guide.
Note: The Genesys Info Mart 8.1 Deployment Guide describes the jdbc-url
option as applicable to non-JDBC DAPs only,
but the option is supported on JDBC DAPs as well. (ER# 307205061)
Restore any customizations in startup arguments, start the Genesys Info Mart Server, and review the Genesys Info Mart log.
"GIM Server - current state is MIGRATION"
) or 55-20034 ("...database schema version...is not up to date..."
), you must upgrade the Info Mart database schema.
Continue with Step 7.Note: Genesys recommends that you set an alarm condition for log event 55-20152.
If you need to update the Info Mart database schema, Genesys Info Mart Server will automatically be in the correct state to perform the migration.
Warning! From this point onward, the Info Mart database should not be accessed by report queries or other scheduled activities, such as custom aggregation, until the migration job is complete. Doing otherwise would interfere with the migration process, which will be modifying database tables, views, and indexes.
Update the Info Mart database by launching Job_MigrateGIM
from the Genesys Info Mart Administration Console v8.0.100.04 or higher.
To do so, perform the following steps:
Schedule
tab.Run Job…
. Job_MigrateGIM
.Allow this job to complete before continuing.
Notes:
If Job_MigrateGIM
does not complete successfully, do the following:
Job_MigrateGIM
when you do not need to do so, Genesys Info Mart will silently ignore the command to launch the job.If your deployment uses read-only views, you must re-create the read-only views after the migration job completes. For more information, see the section about creating Genesys Info Mart read-only views in the Genesys Info Mart 8.1 Deployment Guide.
If your deployment uses Genesys-provided aggregation, in addition to re-creating the Info Mart tenant views (see Step 8), you must also
update the tenant aliases. For more information, see the description of the updateAliases
runtime parameter in the Reporting and Analytics Aggregates Deployment Guide
and the section about updating tenant aliases in the Reporting and Analytics Aggregates User’s Guide.
Review the "New in This Release" sections in the Release Notes and in the Genesys Info Mart 8.x Reference Manuals for your RDBMS, and make any changes to the database schema values or to downstream reporting applications that may require action as part of the migration process.
For example, if you are migrating to release 8.1.x directly from release 8.0.0, you might need to check the values of the IS_ONLINE
column in the MEDIA_TYPE
table to see whether all media types are correctly identified as online
(real-time communication, such as chat) or offline (responses may be
deferred, such as e-mail).
Be aware that Genesys Info Mart migration does not go back to manipulate existing data (in other words, data that was processed before migration). In particular:
Job_MaintainGIM
from the Genesys 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.
run-aggregates
configuration option to TRUE
in the [schedule]
section of the Genesys Info Mart Application
object, to resume running the aggregation job in automated mode.
To deploy this installation package within a new environment, follow the instructions in the Genesys Info Mart 8.1 Deployment Guide.
To deploy this package in your existing Genesys Info Mart 8.x environment, follow all of the Pre-Installation and Installation steps in the Standard Deployment Procedure that follows.
Notes:
Review all steps before you perform 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.
If you are migrating Genesys Info Mart in a deployment in which you use or plan to use Genesys-provided aggregation, review the Reporting and Analytics Aggregates (RAA) and Genesys Interactive Insights (GI2) Release Notes and Release Advisories, for information about the impact of Genesys Info Mart migration on aggregation, as well as workarounds or additional steps to take during Genesys Info Mart migration.
For reference purposes, identify and make notes of any custom changes that you made to the Info Mart database—for example, table spaces, partitions, additional indexes, views, or permissions.
The Genesys Info Mart SQL scripts that you will run to update these databases sometimes create new tables, instead of updating the old tables. They may also replace some tables with views, for backward compatibility. You will need to re-create any custom database objects or permissions that become lost or invalidated during the update process.
For reference purposes, create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.
The default location for these scripts is the sql_scripts
directory within the Genesys Info Mart installation directory.
For reference purposes, identify and make notes of any custom changes that you made to the Genesys Info Mart Application
object. You might need to transfer customizations in your Genesys Info Mart deployment for the new Genesys Info Mart release.
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.
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.
Note: Stopping the Genesys Info Mart server does not result in data loss. As long as all ongoing interaction data is stored in Interaction Databases (IDBs), Genesys Info Mart will process that data after you complete the migration.
Verify that Genesys Info Mart has transformed all extracted data. If necessary, rerun the transformation job manually. For information about running a job on an unscheduled basis, see the chapter about working with jobs in the Genesys Info Mart Operations Guide.
If you are using Genesys-provided aggregation, stop the aggregation job. If the aggregation job is running in automated mode:
run-aggregates
option to FALSE
in the [schedule]
section of the Genesys Info Mart Application
object.Wait for any currently running jobs to finish. Use the Genesys Info Mart Administration Console to monitor completion of the jobs.
Note: The aggregation job might take a long time to complete. If this is the case, proceed with the next step as soon as all other jobs finish.
Stop the Genesys Info Mart Server.
If you also plan to upgrade Reporting and Analytics Aggregates
(RAA), temporarily disable aggregation so that Genesys Info Mart and RAA
do not attempt to migrate their database schemas at the same time.
To disable aggregation, set the aggregation-engine-class-name
option to none
in the gim-etl
section of the Genesys Info Mart Application
object.
Create a backup copy of your Info Mart database.
If necessary, migrate Interaction Concentrator. For information about the minimum Interaction Concentrator release that is required for the Genesys Info Mart release to which you are migrating, see the Genesys Info Mart 8.x Release Notes.
Install the new Genesys Info Mart installation package:
Control Panel > Add/Remove Programs
. Then run setup
to install the new Genesys Info Mart installation package.Overwrite only the files contained in this package
).Review the "New in This Release" information in the Genesys Info Mart 8.1 Deployment Guide.
Identify if any configuration option changes affect customizations that
you may have made in your Genesys Info Mart deployment. If necessary,
modify configuration settings in the Genesys Info Mart Application
or other configuration objects, as required, to transfer custom settings for your deployment.
Because release 8.1.x no longer uses relative values to determine when calendar dimensions start
(for example, date-time-start-year = -1
is no longer valid), verify the validity of the date-time-start-year
setting for existing calendars.
If you used a relative value for the date-time-start-year
option in the [date-time]
and any custom [date-time-*]
sections, change the setting to the appropriate absolute value.
Otherwise, an error will be generated when Genesys Info Mart performs the configuration check.
For each IDB from which Genesys Info Mart will extract ICON
details, run the appropriate Genesys Info Mart–provided SQL
scripts—located in the <GIM root>/sql_scripts/<dbms>
folder—to add to each IDB the views and indexes that Genesys Info Mart requires.
update_idb_for_gim.sql
.update_idb_for_gim_mm.sql
.update_idb_for_gim.sql
or update_idb_for_gim_mm.sql
.Note: If the scripts do not complete correctly, analyze the problem by referring to the log file, resolve any issues, and then run the update script again. If problems persist, or if for any reason you decide to terminate the migration process, run the update script from your pre-migration release of Genesys Info Mart.
(For Oracle users only) Grant permissions to the Info Mart database user using the following commands:
GRANT
CREATE SESSION,
CREATE PROCEDURE,
CREATE SEQUENCE,
CREATE TABLE,
CREATE VIEW to <Info Mart user>;
GRANT EXECUTE ON DBMS_LOCK to <Info Mart user>;
Restore any customizations in startup arguments, start the Genesys Info Mart Server, and review the Genesys Info Mart log.
"GIM Server - current state is MIGRATION"
) or 55-20034 ("...database schema version...is not up to date..."
), you must upgrade the Info Mart database schema.
Continue with Step 6.Note: Genesys recommends that you set an alarm condition for log event 55-20152.
If you need to update the Info Mart database schema, Genesys Info Mart Server will automatically be in the correct state to perform the migration.
Warning! From this point onward, the Info Mart database should not be accessed by report queries or other scheduled activities, such as custom aggregation, until the migration job is complete. Doing otherwise would interfere with the migration process, which will be modifying database tables, views, and indexes.
Update the Info Mart database by launching Job_MigrateGIM
from the Genesys Info Mart Administration Console v8.0.100.04 or higher.
To do so, perform the following steps:
Schedule
tab.Run Job…
. Job_MigrateGIM
.Allow this job to complete before continuing.
Notes:
If Job_MigrateGIM
does not complete successfully, do the following:
Job_MigrateGIM
when you do not need to do so, Genesys Info Mart will silently ignore the command to launch the job.If your deployment uses read-only views, you must re-create the read-only views after the migration job completes. For more information, see the section about creating Genesys Info Mart read-only views in the Genesys Info Mart 8.1 Deployment Guide.
If you disabled Genesys-provided aggregation because you also want to upgrade RAA (see Pre-Installation Step 10), re-enable aggregation. To do so:
aggregation-engine-class-name
option to "GIMAgg.GimInterfaceImpl.AggregationImpl"
in the gim-etl
section of the Genesys Info Mart Application
object.If your deployment uses Genesys-provided aggregation and there were Info Mart schema changes, in addition to re-creating the Info Mart tenant views (see Step 7), you must also:
Re-create the RAA and Genesys Interactive Insights (GI2) main schema views. To do so:
merge into CTL_SCHEMA_INFO d using (select 'Interactive Insights' SCHEMA_NAME from dual) s on ( d.SCHEMA_NAME = 'Interactive Insights' ) WHEN MATCHED THEN UPDATE SET d.SCHEMA_VERSION = '0clean' WHEN NOT MATCHED THEN INSERT (d.SCHEMA_NAME, d.SCHEMA_VERSION) values ('Interactive Insights', '0clean'); commit;
begin transaction; delete from CTL_SCHEMA_INFO where SCHEMA_NAME = 'Interactive Insights'; insert into CTL_SCHEMA_INFO (SCHEMA_NAME, SCHEMA_VERSION) values ('Interactive Insights', '0clean'); commit transaction;
Update the tenant aliases. For more information, see the description of the updateAliases
runtime parameter in the Reporting and Analytics Aggregates Deployment Guide
and the section about updating tenant aliases in the Reporting and Analytics Aggregates User’s Guide.
Review the "New in This Release" sections in the Release Notes and in the Genesys Info Mart 8.x Reference Manuals for your RDBMS, and make any changes to the database schema values or to downstream reporting applications that may require action as part of the migration process.
For example, if you are migrating to release 8.1.x directly from release 8.0.0, you might need to check the values of the IS_ONLINE
column in the MEDIA_TYPE
table to see whether all media types are correctly identified as online
(real-time communication, such as chat) or offline (responses may be
deferred, such as e-mail).
Be aware that Genesys Info Mart migration does not go back to manipulate existing data (in other words, data that was processed before migration). In particular:
Job_MaintainGIM
from the Genesys 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.
run-aggregates
configuration option to TRUE
in the [schedule]
section of the Genesys Info Mart Application
object, to resume running the aggregation job in automated mode.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Genesys Info Mart 8.1 Release Advisory provides important information that applies to the entire Genesys Info Mart release.
Genesys Info Mart 8.1 Deployment Guide includes installation procedures for Genesys Info Mart Manager, the Genesys Info Mart Administration Console, and Genesys Info Mart and acquaints you with their functions, while Genesys Administrator Extension 8.1 Deployment Guide provides information about the installing Genesys Administrator Extension (GAX), which supports the Genesys Info Mart Manager plug-in.
Genesys Info Mart 8.1 Operations Guide provides information about the Genesys Info Mart jobs. The jobs extract, transform, and load (ETL) data, maintain the Info Mart database, and migrate the database schema as required. The guide also explains how to use Genesys Info Mart Manager and the Genesys Info Mart Administration Console to monitor and administer the jobs.
Genesys Info Mart 8.1 Reference Manual for your particular RDBMS acquaints you with the subject areas, tables, and fields that make up the Genesys Info Mart star schemas.
Genesys Info Mart 8.1 User's Guide provides examples of common voice and multimedia interactions.
The Genesys Info Mart section of the Framework 8.1 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.