[asterisk-bugs] [Asterisk 0017872]: update_odbc always reports that : Key field 'ipaddr' does not exist in table ... Update will fail
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Dec 6 09:00:26 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17872
======================================================================
Reported By: spanov
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17872
Category: Resources/res_config_odbc
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.6.2.11
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-08-16 15:04 CDT
Last Modified: 2010-12-06 09:00 CST
======================================================================
Summary: update_odbc always reports that : Key field 'ipaddr'
does not exist in table ... Update will fail
Description:
I've set up reatime configuration for sippeers and sipregs via ODBC
connected to Oracle 11g. There are a lot of warning (update_odbc always
reports that : Key field 'ipaddr' does not exist in table ... Update will
fail) in the CLI while new SIP registration.
I assume that it's case sensitive issue since actually, the column ipaddr
is updated correctly. By default Oracle return all columns in uppercase.
======================================================================
----------------------------------------------------------------------
(0129327) birgita (reporter) - 2010-12-06 09:00
https://issues.asterisk.org/view.php?id=17872#c129327
----------------------------------------------------------------------
(Sorry for keeping updating this issue, that isn't actually an asterisk
issue.)
I managed to fix it. I compiled & installed a new version of unixODBC.
Make sure the tablename is in CAPITALS in extconfig.conf.
Make sure when you build unixODBC the oracle drivers are build as well (I
edited the DRVConfig/Makefile).
I got still some warnings at startup time, but I think that is a timing
issue.
Versions:
OS: openSUSE 11.3 "Teal", 2.6.34-12
unixODBC: 2.3.0
Oracle install client: 11.2.0
Asterisk: SVN-branch-1.8-r296230M
Issue History
Date Modified Username Field Change
======================================================================
2010-12-06 09:00 birgita Note Added: 0129327
======================================================================
More information about the asterisk-bugs
mailing list