Summary: | ASTERISK-16588: ast_odbc_direct_execute: SQL Exec Direct failed while storing CDR rto Oracle 11g | ||
Reporter: | Sergey Panov (spanov) | Labels: | |
Date Opened: | 2010-08-18 12:42:18 | Date Closed: | 2011-06-07 14:05:00 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Resources/res_odbc |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | It always show the following error when trying to store CDR ro Oracle [Aug 18 21:37:44] WARNING[4604]: res_odbc.c:584 ast_odbc_direct_execute: SQL Exec Direct failed. At tempting a reconnect... [Aug 18 21:37:44] NOTICE[4604]: res_odbc.c:1428 odbc_obj_connect: Connecting asterisk [Aug 18 21:37:44] NOTICE[4604]: res_odbc.c:1456 odbc_obj_connect: res_odbc: Connected to asterisk [a sterisk-orca] > cdr_odbc: Error in ExecDirect: -1 [Aug 18 21:37:44] WARNING[4604]: res_odbc.c:584 ast_odbc_direct_execute: SQL Exec Direct failed. At tempting a reconnect... [Aug 18 21:37:44] NOTICE[4604]: res_odbc.c:1428 odbc_obj_connect: Connecting asterisk [Aug 18 21:37:44] NOTICE[4604]: res_odbc.c:1456 odbc_obj_connect: res_odbc: Connected to asterisk [a sterisk-orca] [Aug 18 21:37:44] ERROR[4604]: cdr_odbc.c:147 odbc_log: CDR direct execute failed ****** ADDITIONAL INFORMATION ****** DDL create table AST_CDR ( ID INTEGER not null, CALLDATE TIMESTAMP(0) WITH LOCAL TIME ZONE not null, CLID VARCHAR2(80 CHAR), SRC VARCHAR2(80 CHAR), DST VARCHAR2(80 CHAR), DCONTEXT VARCHAR2(80 CHAR), CHANNEL VARCHAR2(80 CHAR), DSTCHANNEL VARCHAR2(80 CHAR), LASTAPP VARCHAR2(80 CHAR), LASTDATA VARCHAR2(80 CHAR), DURATION NUMBER(11) default 0 not null, BILLSEC NUMBER(11) default 0 not null, DISPOSITION VARCHAR2(45 CHAR), AMAFLAGS NUMBER(11) default 0 not null, ACCOUNTCODE VARCHAR2(20 CHAR), UNIQUEID VARCHAR2(32 CHAR), USERFIELD VARCHAR2(255 CHAR), constraint PK_AST_CDR primary key (ID) ) | ||
Comments: | By: Tilghman Lesher (tilghman) 2010-08-18 15:34:27 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. You may find it helpful to read the Asterisk Issue Guidelines http://www.asterisk.org/developers/bug-guidelines. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). This likely includes output from the console with debug level logging and configuration information such as the contents of all odbc-related files (e.g. /etc/odbcinst.ini, /etc/odbc.ini, and /etc/asterisk/res_odbc.conf). Thanks! By: Leif Madsen (lmadsen) 2011-01-05 15:41:21.000-0600 Suspended due to lack of feedback. |