" /> SQL2K SP3 with Genesys - Genesys CTI User Forum

Author Topic: SQL2K SP3 with Genesys  (Read 3681 times)

hmcjsr

  • Guest
SQL2K SP3 with Genesys
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Due to the Slammer worm, applying SP3 on SQL2K Server is a must. The latest SP3 for SQL2K comes with a patch installer, and the latest SP3 includes the security fix (from 16Oct02) and a hot fix for memory leak (from 30Oct02).
I understand from Genesys that there are issues related to JDBC connectivity with SP3 on SQL2K. Has anyone come across this ? Since my installation has CCA, JDBC connectivity is important.
Any comments / suggestions / experiences ??
Regards

Superglide

  • Guest
SQL2K SP3 with Genesys
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • We applied the SP3 fix on our development system and now have broken historical reporting. Have raised a call with gensys support.

    Fariborz

    • Guest
    SQL2K SP3 with Genesys
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Below is a prodcut advisory for this issue:


    Product Advisory for CC Analyzer 5.1, 6.1, 6.5
    Issued:
    February 06, 2003
    Defect Number:
    53502
    Summary:
    CC Analyzer components that use a JDBC database connection may stop working after installing MS SQL
    Server 2000 Service Pack 3 (SP3). Formal criteria is not available to assess if the problem will affect a
    particular environment.
    Affected Products & Versions:
    CCAnalyzer ETL Runtime, ETL Assistant, IS DataSourcer, all versions in conjunction with
    MS SQL Server 2000 SP3
    Problem Description:
    CC Analyzer components that use a JDBC database connection may stop working after installing MS SQL
    Server 2000 Service Pack 3 (SP3). The problem is related to the BEA WebLogic JDBC driver operation.
    If the problem occurs, the following error message is printed in the corresponding log file:
    java.sql.SQLException: I/O exception while talking to the server, java.io.EOFException
    Unable to connect, please check your server's version and availability.
    The problem has the following impact:
    ETL Runtime is unable to transfer data collected in the ODS database into the DataMart database. As a
    result, the data is temporarily unavailable in the reports and the corresponding ODS database that is fed by
    Stat Server continues to grow.
    IS Data Sourcer is unable to extract fresh data from the ICS Contact Server database and store it in the
    ODS database. As a result, the data is temporarily unavailable in the reports.
    ETL Assistant is unable to connect to the DataMart database and display the report layouts structure.
    Overall the problem does not lead to data loss provided that a fix is installed shortly. As soon as the fix is
    installed and the affected components begin working properly, the missing data will be gradually transferred
    into the DataMart database and will become available in the reports.
    Note: The ODS database growth can potentially lead to data loss due to a lack of available disk space.
    Workaround:
    A workaround is not available.
    Fix Available In:
    The problem is related to the BEA WebLogic JDBC driver operation. Genesys has received a new JDBC
    driver that resolves the problem from BEA and is planning to include it in Generally Available CC Analyzer
    installation packages. Meanwhile you can download the new driver using the following link:
    ftp://ftp.genesyslab.com/pub/production/weblogic_mssql_SP3_jdbc_driver.zip
    The package consists of the driver itself and the Deployment Procedure document.
    If you have trouble deploying this package, contact Genesys Technical Support.