Genesys 6.5 with SQL Server 2005

[padmey]

Hi guys..

I need some guidance..My client is currently using Genesys 6.5 that uses SQL Server 7.0 as the database storage. Now they had requested the SQL Server to be upgraded to SQL Server 2005 using the existing Genesys components.

My worry is that would Genesys 6.5 be compatible with SQL Server 2005?
Has anyone has any exprience in it? What are the pre-caution steps that i've to look at?

Thanking in advance.

[Fra]

Try to check "Genesys Supported Operating Environment Reference Manual (formerly titled Genesys Supported Operating Systems & Databases)".

Fra

[bcyk]

Genesys 6.5 works for MS SQL Server 2000 as well.

I encoutered similar issue in non-production environment; early versions in Genesys 7.x did not support 2005 server. It seemed that configuration database worked ok but problems occurred in Genesys CCA applications.

You may try to change database compatibility level as follows; it is afraid that Genesys may not officially "approve" this method!

It is assumed that all required Genesys databases are created.
- run MS SQL Server 2005 Management Studio
- open "New Query" section (use TSQL commands)
- type and execute "[b]sp_helpdb[/b]"
  output table columns -> name,db_size,owner,dbid,created,status,compatibility_level
  The "compatibility_level" value by default should be 90 for MS SQL 2005 server

  60 = SQL Server 6.0
  65 = SQL Server 6.5
  70 = SQL Server 7.0
  80 = SQL Server 2000
  90 = SQL Server 2005

  ==> you may try to change compatibility_level to 70 or 80

- for each Genesys database, change database compatibility_level value manually
  - e.g., databases gcticonf, gctiods and gctidm
  - to view the value: execute "[b]sp_dbcmptlevel gcticonf[/b]"
    expected output: The current compatibility level is 90.
  - to change new value: execute "[b]sp_dbcmptlevel gcticonf, 70[/b]"
    expected output:    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

- enter and execute "[b]sp_helpdb[/b]" to verify compatibility_level values for all databases


Hope these info help
Good luck

[padmey]

Thanks Fra and bcyk...

I really appreciate it...

By the way bcyk, the compability level changes that need to be done that you'd given is really helpful..
Thank you so much...
I'd worked with a dba to do some upgrade using a small portion of database but he had left the compability level to default.. Guess now i've to do the changes..

Last but not least (sorry, am still new..so just want a confirmation) since we need to do data migration from the old server to new server, we need to restore the database during the downtime..How should i go around on this?

Thanking in advance..

[Fra]

There's a Genesys utility called Configuration Import Wizard, you should be able to export your configuration data into a plain text file and subsequently import in your new db. Try to look for in the Framework cd.

Hope it helps

[bcyk]

hi padmey,

How to mininize down-time?

Major factors depend on your call center operation hours and active running Geneys components.
If it is a 24-hour operation and Genesys CCA are being used, it can be a little messy.

Genesys configuration database
 - freeze Genesys configuration a day or so before data migration
 - backup/copy the frozen database to new server and restore it before data migration

Genesys log database
 - depends on its size and how "critical" this information is in your site
 - if it is not classified as critical, freeze and treat it similar to configuration database
 - if last-minute messages must be retented, follow steps for "Genesys ODS/DM databases" below

Genesys ODS/DM databases (and other similar databases if applicable)
 - it is a dynamic database with respect to call traffic
 - agree a cut-off time with end-users and operations
    - for non 24-hour operation, let it be the normal non-office start time
    - for 24-hour operation, make up a cut-off time
 - at the "cut-off" time, do not start database migration yet
 - allow around 15 to 30 minutes (assuming default 15 minute reporting interval in CCA) for Data Sourcer to transfer in-memory statistics to database tables
 - shutdown Genesys components and start databases migration

Well, if incomplete or missing reports during migration is not a issue (not likely in most sites!), the downtime can be further mininized.


Other advices when performing Genesys databases instances
  1. perform some tests before actual data migration
  2. list all databases instances, owner IDs, usernames and passwords in current environment
     - make sure that identical security settings above is properly configured in new database server
     - the TSQL command sp_change_users_login AUTO_FIX, 'my_username' may be needed
       (had trouble once related to MS SQL username when transfer database instance from SQL 2000 to SQL 2000;
        this command helped to resolve the problem)
  3. Estimated backup/restore and verification transaction times
     - need to align with normal operation maintenance window
     - if not, special arrangement for longer maintenance duration is required


regards

[padmey]

Hi,

Once again thank u so much for your precious advices guys (Fra and bcyk)...As from your advices and orders from the manager, I tried to test a small part of the database migration...I copied out a small part from the genesys database (genesys_cfg) and migrated it into a new server wit the compability level set to SQL Server 2000 (we've upgraded it to SQL Server 2005)...After the migration, i installed freshly the config db and config server on a new server...After installing CME, i tried logging into it but i got an error asking me to check my host name and port number...And when i checked the confserv log files..i came across lines stating that i got disconnected from the database server...I wonder where did i go wrong?Had checked and compared both the production and development .cfg files but couldn't find anything...

Am lost...
Hope i'd state my prob clearly so that i can get a solution for it...

Thanking in advance..

[René]

Hi padmey,

I think there were significant changes made to communication protocol between client and server in 2005 release to fix some security flaws. It means that DBServer 6.5 won't be able to connect SQL Server 2005 as it uses old non-supported protocol.

You can try to install SQL Server 2005 Client tools on server where DBServer is running. Maybe it will help.

You should find more details about issue in DBServer log (debug level).

R.

PS. Is there any reason why you can't upgrade to newer Genesys release?

[padmey]

Hi Rene,

So does that mean that my DB Server 6.5 would not work with SQL Server 2005 even though i set the compability level to SQL Server 2000? Guess i need to change it back to SQL Server 7.0..

Well the client are planning to do the upgrade for the Genesys components too but in later phase...Initially I was to upgrade the servers together with the Genesys components but somehow they changed the plan and asked me to do the hardware upgrade first...

[bcyk]

hi padmey,


Did you encounter an error anywhere? such as
  The dynamic link library ntwdblib.dll could not be found in the specified path
  <.... values in PATH...>

The error may be reported when starting Configuration server

ntwdblib.dll
    File version: 2000.2.8.0
    Description: SQL Server Client Library
    Copyrignt: Copyright @Microsoft Corp. 1988-1998

The dll file is part of SQL client utilities / libraries.
You may try to find the file in the production environment using MS SQL 7 and copy it to the in Genesys DB server folder(s).
Thus, if there are multiple instalce of DB server, copy this file to each sub-folders so that it does not affect MS SQL 2005 client utilities.


Official supported MS SQL version for Genesys 6.5 is SQL 7 and SQL 2000.
If compatibility level in SQL 2005 works for SQL 2000, it has high chance that it also works for SQL 7.

You should get the configuration database working (i.e., Genesys Configuration manager client program); the real "challenge" is Genesys CCA (i.e., data sourcer and ETL services).

Since you are planning to upgrade Genesys from 6.5 to 7.5/7.6, database migration for Genesys must be performed anyway. If there is spare resource, upgrading database server ahead is optional and "nice" to have but not mandatory.

BTW, posting detail Genesys log files at debug level when error is encountered helps a lot for others to give comments.

in dbserver.cfg
[log]
verbose = debug
debug = cfgdbserver.deb

in confserv.cfg
[log]
verbose = debug
debug = confserv.deb

[Gulden_NL]

[quote author=bcyk link=topic=3809.msg16506#msg16506 date=1234001546]
Official supported MS SQL version for Genesys 6.5 is SQL 7 and SQL 2000.
If compatibility level in SQL 2005 works for SQL 2000, it has high chance that it also works for SQL 7.
[/quote]
We are in the process of an upgrade from 7.2.2 to 7.6 [b][u]for GVP[/u][/b] We're doing a few other things at the same time, so in the lab we tested 7.6 with SQL Server 2000 and it didn't work.  We played with it for a week and kept getting the same response from Genesys Tech Support "not supported, we won't even bother to look at it."  Our DBA suggested that there was an incompatibility in GVP, so we quit working on it, and changed our sequence to upgrading to 7.6, and upgrading to SQL 2005 in parallel.  We didn't try it on CIM because GVP has a much larger footprint for us.

Not to say that you won't be able to get it to work, but it's another data point of where it didn't work, along with Genesys' response.

[René]

Hi padmey,

My opinion is that it won't work due protocol changes in SQL Server 2005. Compatibility level has nothing to do with the protocol. It tells SQL Server how to interpret executed SQL code as there were some changes made as well. You can find more details about compatibility level in SQL Books On-Line.

Personally, I would recommend you to do Genesys migration in first step and migrate SQL database thereafter.

R.

[Fra]

[quote author=padmey link=topic=3809.msg16505#msg16505 date=1233987316]
Hi Rene,

So does that mean that my DB Server 6.5 would not work with SQL Server 2005 even though i set the compability level to SQL Server 2000? Guess i need to change it back to SQL Server 7.0..

[/quote]

SQL Server 2005 requires DB Server 7.5, check the Supported Operating Environment manual. If you want to keep using DB Server 6.5, you have to switch back to SQL Server 7.0 or 2000.

Fra

[padmey]

Hi..

Thank you so much for all the guidance..

Am now going to try to install back SQL Server 7.0 in the new server and do the integration...
The Genesys upgrade cannot be done for now as it's also intergrating with some other databases which would only be upgraded at later phase..

Anyway attaching is the log files for your comments..

Thanking in advance..Thank you

[cavagnaro]

The wonder of Genesys is that if you upgrade to last version you will keep compatibility with older versions of DB, PBX, etc. So if you upgrade to Genesys 7.6 you still will be able to use old versions of your DBs.