Bgrenon

Migrating Databases to Advisors Release 8.5.2

Content on this page is specific to migrating your database installations to Advisors release 8.5.2.

General Considerations

• Starting with Advisors release 8.5.202, both the Platform and the Metric Graphing database scripts are supplied in the Platform IP in the ip\platform-database-sql and \ip\metric-graphing-database-sql folders, respectively.
• Upgrade all AGA metrics schemas before you start the Platform schema upgrade.
• If you have the Bulk Configuration tool installed, you need to upgrade it separately by executing the blkObjectsCre.sql script taken from the corresponding folder in \ip\platform-database-sql\<rdbms>\bulkconfig</rdbms>. The blkObjectsCre.sql script must be applied after the general migration script is applied.

Migrating MS SQL Server Databases to Advisors Release 8.5.2

To migrate MS SQL Server databases to release 8.5.2:

1. Stop all Advisors components.
2. Apply the gc_metrics_db_<version>.sql</version> script, supplied in the \ip\configuration-schema\mssql folder of the AGA installation package, to the AGA metrics database of any version.
3. Apply the advisors-platform-migrateSchema_8.5.101(102)-<version>.sql</version> script, supplied in the corresponding folder within the \ip\platform-database-sql\mssql\ folder, to the Platform database of any version between, and including, 8.5.101 and the current release.
4. Apply the mg-new-database-<version>.sql</version> script, supplied in the corresponding folder within the \ip\metric-graphing-database-sql\ folder, to the metric graphing database of any version between, and including, 8.5.101 and the current release.

Migrating Oracle Schemas to Advisors Release 8.5.2

If you use Oracle databases in your environment, use the procedure on this page to migrate to Advisors release 8.5.2.

Prerequisites

• If you moved Advisors schemas to another Oracle database, run the DBMS_SCHEDULER.sql script as a privileged user to create a job class for Advisors, or ask your DBA to run the script. This is a one-time, database-wide operation that does not need to be repeated as long as the same Oracle database is used.
• Advisors release 8.5.2 supports the Oracle 12C In-Memory option. If you choose to use the In-Memory option, have your DBA enable the option. Enabling the option can result in extra charges from Oracle, so make sure you have confirmed the choice with your management team.
• Advisors release 8.5.2 needs the Oracle JServer Java Virtual Machine component installed in the Oracle database. If the component is not installed, and cannot be added to the existing Oracle installation, ask your DBA to grant the following privilege:

  GRANT EXECUTE ON SYS.DBMS_LOCK TO <platform schema="" owner="">;</platform>

1. Migrate the AGA metrics schema objects.

Note that there is no need to run the gc_metrics_<version>_ObjectsDrop.sql</version> script before the object creation script while upgrading the AGA metrics schema. The object creation script will replace the existing objects, where necessary. Do one of the following:

• If you use SQL*Plus, apply the gc_metrics_<version>_ObjectsPlus.sql</version> script while connected as the AGA Metrics schema owner.
• If you want all of the AGA metrics objects recreated in the AGA Metrics user default tablespace, connect as the AGA Metrics schema owner and run the gc_metrics_<version>_ObjectsDefault.sql</version> script from Oracle SQL Developer or SQL*Plus.
• If you want to separate the AGA metrics objects by placing them into different tablespaces, and want to use SLQ Developer, then run the gc_metrics_<version>_ObjectsCustom.sql</version> script while connected as AGA Metrics schema owner.

After you have performed one of the preceding actions, then do the following, if applicable:

• If you are using the In-Memory option, then execute gc_metrics_<version>_INMEMORY.sql</version> in AGA metrics schema. This change can be easily reverted at any time by running the gc_metrics_<version>_NO_INMEMORY.sql</version> script.

Finally, perform the following mandatory action:

• Grant select permissions to the Platform user on all views contained in the migrated AGA metrics schema. If such permissions were granted earlier, you still have to re-issue them before you proceed to the next Step.

Repeat all of the above for each schema if you use more than one AGA metrics schema.

2. Migrate the Platform schema objects.

To migrate the Platform schema objects, do the following:

• Ask your DBA to grant the following privileges to the Platform schema owner:

GRANT EXECUTE ON SYS.GENADVISORSJOBCLASS TO &&platformschemaowner;
GRANT CREATE JOB TO &&platformschemaowner;

• Make sure that the Platform schema owner has select privileges to all views that belong to all GENESYS sources listed in the Platform ICM_DATABASE table.

  To verify the privileges, connect as the Platform schema owner and run the following set of queries for each <aga metrics="" schema="" name=""> listed in the Platform ICM_DATABASE table. </aga>

SELECT * FROM  <aga metrics="" schema="" name="">.AGENT_SKILL_GROUP_REAL_TIME WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.CALL_TYPE WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.CALL_TYPE_REAL_TIME WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.CONTROLLER_TIME WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.INTERACTION_QUEUE WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.INTERACTION_QUEUE_REAL_TIME WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.LOGICAL_INTERFACE_CONTROLLER WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.PERIPHERAL WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.PERIPHERAL_REAL_TIME WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.SERVICE WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.SERVICE_MEMBER WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.SERVICE_REAL_TIME WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.SKILL_GROUP WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.SKILL_GROUP_REAL_TIME WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.QUEUE_SET1_REAL_TIME WHERE ROWNUM<2;
SELECT * FROM  <aga metrics="" schema="" name="">.QUEUE_SET2_REAL_TIME WHERE ROWNUM<2;