" /> Troubleshooting DAP Access to DBServer - Genesys CTI User Forum

Author Topic: Troubleshooting DAP Access to DBServer  (Read 6272 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Troubleshooting DAP Access to DBServer
« on: July 08, 2011, 12:05:40 PM »
Advertisement
Hello,

I am trying to find out why a data dip within a IRD routing strategy is not working.

Within the URS log files I see the lines:

[i]11:36:49.762_I_I_007101e8b573025a [07:48] function will be continued(0,648019980)
11:36:49.762_I_I_007101e8b573025a [09:04] <<<<<<<<<<<<suspend interpretator(JUMPING), func:Return timers:00001
11:36:49.762_I_I_007101e8b573025a [07:49] function is continued(0,648019980)
    _I_I_007101e8b573025a [07:44] return to strategy *0x65*CCI (level=1, crc=2658201469)
11:36:49.762_I_I_007101e8b573025a [09:05] >>>>>>>>>>>>resume interpretator(0), func:CallStrategy
11:36:49.762_I_I_007101e8b573025a [07:48] function will be continued(0,564133897)
11:36:49.762_I_I_007101e8b573025a [09:04] <<<<<<<<<<<<suspend interpretator(JUMPING), func:CallStrategy timers:00001
11:36:49.762_I_I_007101e8b573025a [07:49] function is continued(0,564133897)
    _I_I_007101e8b573025a [07:43] call strategy *0x65*sub_Read_Call_Info (level=2, cnt=2 from 1310121409.762 crc=1738033553)
11:36:49.762_I_I_007101e8b573025a [09:06] >>>>>>>>>>>>start interpretator()
    _I_I_007101e8b573025a [07:46] no error mode for this call
    _I_I_007101e8b573025a [09:04] ASSIGN: __Return(SCRIPT) <- STRING:
    _I_I_007101e8b573025a [09:04] ASSIGN: __DBReturn(SCRIPT) <- STRING:
    _I_I_007101e8b573025a [09:04] ASSIGN: __DBStrReturn(SCRIPT) <- STRING:
    _I_I_007101e8b573025a [09:04] ASSIGN: __TargetVar(SCRIPT) <- STRING:
    _I_I_007101e8b573025a [09:04] ASSIGN: intDNIS(LOCAL) <- INTEGER: 882387
11:36:49.762_I_I_007101e8b573025a [07:38] HERE IS XDATA
    _I_E_007101e8b573025a [09:04] error in strategy: 0014 Unknown server
    _I_I_007101e8b573025a [09:04] ASSIGN: __DBReturn(SCRIPT) <- STRING:

11:36:49.762 Int 22000 !! Error: Failed to read from database during sub_read_call_info
11:36:49.762_I_I_007101e8b573025a [07:48] function will be continued(0,25165843)
11:36:49.762_I_I_007101e8b573025a [09:04] <<<<<<<<<<<<suspend interpretator(JUMPING), func:Return timers:00001
11:36:49.762_I_I_007101e8b573025a [07:49] function is continued(0,25165843)
    _I_I_007101e8b573025a [07:44] return to strategy *0x65*CCI (level=1, crc=2658201469)
11:36:49.762_I_I_007101e8b573025a [09:05] >>>>>>>>>>>>resume interpretator(0), func:CallStrategy
    _I_I_007101e8b573025a [09:04] ASSIGN: strNonGeo(LOCAL) <- STRING:
    _I_I_007101e8b573025a [09:04] ASSIGN: strSkill(LOCAL) <- STRING:
    _I_I_007101e8b573025a [09:04] ASSIGN: strType(LOCAL) <- STRING:
    _I_I_007101e8b573025a [09:04] ASSIGN: strBrand(LOCAL) <- STRING:[/i]

The DAP and DBserver appear to be correct.  I have also compared this configuration to a matching set up and there is no difference.  I have checked and confirmed with our database team regarding the password which is correct.  Im not sure which log file best points out where the issue is occurring.

The DBserver logs say the following:

[i]Genesys Database Server, Version:'8.0.200.03'
Copyright (c) 1997-2009 Genesys Telecommunications Labs, Inc.
Component versions:
Commonlib:        8.0.000.11 C2
Loglib:          8.0.200.02
Gmessagelib:      8.0.000.00
GServicelib:      8.0.200.00
Mngmlib:          8.0.000.00
Confservlib:      8.0.200.03
Lcalib:          8.0.200.00
Build platform:  i686-winnt
Application name: rtg_dbserver
Application type: RealDBServer (46)
Command line:    multiserver.exe -service DBServer_3 -app rtg_dbserver -host rstwakguinee -port 2020 -sstart
Host name:        RSTWAKGUINEE
DST:              TZ = 1, timeb = 1
Time zone:        0, GMT Standard Time, GMT Daylight Time
UTC time:        2011-07-08T11:03:40.335
Local time:      2011-07-08T12:03:40.335
Start time (UTC): 2011-07-08T11:03:40
Running time:    0:00:00:00
Host info:        Windows 5.2.3790, 2, Service Pack 2, 2.0, 0110, 3
File:            (1) D:\Program Files (x86)\Logs\RtgDBs\rtg_dbserver.20110708_120340_336.log

12:03:40.335 Trc 04112 The Log Output of type 'D:\Program Files (x86)\Logs\RtgDBs\rtg_dbserver' has been created and opened
12:03:40.335 Trc 04110 Option 'verbose' has been set to the value 'all'
12:03:40.335 Trc 04110 Option 'buffering' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'expire' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'segment' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'spool' has been set to the value ''
12:03:40.335 Trc 04110 Option 'keep-startup-file' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'MessageFile' has been set to the value 'RealDBServer.lms'
12:03:40.335 Trc 04110 Option 'time-format' has been set to the value 'time'
12:03:40.335 Trc 04110 Option 'time-convert' has been set to the value 'local'
12:03:40.335 Trc 04110 Option 'message-format' has been set to the value 'short'
12:03:40.335 Trc 04110 Option 'memory-storage-size' has been set to the value '2 Mb'
12:03:40.335 Trc 04110 Option 'compatible-output-priority' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'print-attributes' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'check-point' has been set to the value '1'
12:03:40.335 Trc 04110 Option 'memory' has been set to the value ''
12:03:40.335 Std 04106 Log Messages file 'RealDBServer.lms' successfully loaded
12:03:40.335 Trc 04112 The Log Output of type 'stderr' has been created and opened
12:03:40.335 Std 04503 Connected to ConfigServer '' at host 'rstwakguinee', port 2020
12:03:40.335 Trc 04110 Option 'verbose' has been set to the value 'all'
12:03:40.335 Trc 04110 Option 'buffering' has been set to the value 'yes'
12:03:40.335 Trc 04110 Option 'expire' has been set to the value '20 file'
12:03:40.335 Trc 04110 Option 'segment' has been set to the value '10000'
12:03:40.335 Trc 04110 Option 'spool' has been set to the value ''
12:03:40.335 Trc 04110 Option 'keep-startup-file' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'MessageFile' has been set to the value 'RealDBServer.lms'
12:03:40.335 Trc 04110 Option 'time-format' has been set to the value 'time'
12:03:40.335 Trc 04110 Option 'time-convert' has been set to the value 'local'
12:03:40.335 Trc 04110 Option 'message-format' has been set to the value 'short'
12:03:40.335 Trc 04110 Option 'memory-storage-size' has been set to the value '2 Mb'
12:03:40.335 Trc 04110 Option 'compatible-output-priority' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'print-attributes' has been set to the value 'no'
12:03:40.335 Trc 04110 Option 'check-point' has been set to the value '1'
12:03:40.335 Trc 04110 Option 'memory' has been set to the value ''
12:03:40.335 Trc 04113 The Log Output of type 'stderr' has been closed and deleted
12:03:40.335 Trc 04112 The Log Output of type 'D:\Program Files (x86)\Logs\RtgDBs\rtg_dbserver' has been created and opened
12:03:40.335 Trc 04110 Option 'level-reassign-disable' has been set to the value 'no'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'connect_break_time' = '1200'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'db2_name' = './dbclient_db2'
12:03:40.335 Trc 06084 Configuration option set: 'dbserver':'dbprocess_name' = './dbclient_sybase'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'dbprocesses_per_client' = '1'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'informix_name' = './dbclient_informix'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'management-port' = '4051'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'msql_name' = './dbclient_msql'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'oracle_name' = './dbclient_oracle'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'sybase_name' = './dbclient_sybase'
12:03:40.335 Trc 06085 Configuration option set to default value: 'dbserver':'tran_batch_mode' = '0'
Open LCALayer on port=4999
LCA Library version 8.0.200.00
12:03:40.335 Std 05060 Application started
Opening listeneres...

Port id 'default':
Open server port: = (
  "protocol" = "addp"
  "addp-timeout" = "0"
  "addp-remote-timeout" = "0"
  "addp-trace" = "off"
  "name" = "rtg_dbserver"
  "server-type" = "46"
  "backlog" = "5"
  "port" = "4065"
)
12:03:41.288 Std 04525 Port 4065 opened for listening
Updating primary/backup config server info 99 0
Primary config server (dbid)(host)(port): (99)(rstwakguinee)(2020)
Error while retrieving backup config server info.
************************************
LCALayer: REventRegistered on LCA...
************************************[/i]

There is no backup config server on this platform so expected the error above.
Thanks,
WA

Offline borkokrz

  • Full Member
  • ***
  • Posts: 154
  • Karma: 6
Re: Troubleshooting DAP Access to DBServer
« Reply #1 on: July 08, 2011, 12:10:35 PM »
Do you have a connection between URS app and DAP ?

Offline bandorka

  • Full Member
  • ***
  • Posts: 120
  • Karma: 1
Re: Troubleshooting DAP Access to DBServer
« Reply #2 on: July 11, 2011, 06:55:13 AM »
Hi,

Did you create table access etc. to your database, mentioned in URS Depl. Guide 7.6 on page 138?

Bandorka

Offline ADB

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: Troubleshooting DAP Access to DBServer
« Reply #3 on: July 11, 2011, 01:03:00 PM »
Sorry if I missed it but, are you using Sybase database?
if not I see the issue here:

'dbserver':'dbprocess_name' = './dbclient_sybase'

DBServer docs, which may be related…says “Only enable the dbprocess_name option for compatibility with previous releases of client applications (5.1, 6.0, or 6.1).”

So, set 'dbprocess_name' = ''  (blank)  -- as an option value.

Then try, and let me know what error you are getting in the DB Server log when you invoke a procedure.

Please let me know the stored procedure parameters as well.

-Ajay

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: Troubleshooting DAP Access to DBServer
« Reply #4 on: July 29, 2011, 06:11:51 PM »
This turned out to a combination of not having a DAP connection in URS as suggested and the password not being correct - now working as normal