unixodbc-使用Log4cxx日志输出至MySQL, 无法找到驱动错误
unixodbcmysqllog4cxx
Hi, guys!
用log4cxx日志框架对log内容输出至数据库(MySQL)一直未成功,不知道是什么步骤出现了问题。希望大伙们能帮帮忙,或者有什么更好的日志系统可以推荐,谢谢各位了。 ^_^
运行环境: Ubuntu 12.04 32bit + Eclipse CDT
log4cxx : apache-log4cxx-0.10.0
log4cxx支持两种ODBC选项(iODBC/unixODBC),这里选择了unixODBC形式进行管理
通过添加选项 ./configure --with-ODBC=unixODBC,编译通过.
之后对unixODBC的驱动和数据源进行配置,可以通过终端 isql log4cxx 成功建立连接
但是代码中使用Log4cxx进行输出的时候一直报下面的错误
<code>log4cxx: Failed to connect to database. - [unixODBC][Driver Manager]Data source name not found, and no default driver specified</code>
怀疑一:
Ecplise中是否没有加环境变量;
查阅ODBC资料,在Eclipse中加入ODBCSYSINI,ODBCINSTINI,ODBCINI变量后,还是没有效果.
怀疑二:
log4cxx配置写的不对;这个有没有什么官方的写法,晕呐!
配置内容:
/etc/odbcinst.ini
<code>[MySQL]Description = MySQLDriver = /usr/lib/i386-linux-gnu/odbc/libmyodbc.soSetup = /usr/lib/i386-linux-gnu/odbc/libodbcmyS.soFileUsage = 1 </code>
/etc/odbc.ini
<code>[log4cxx]Description = The Database for Logging SystemTrace = onTraceFile = stderrDriver = MySQLSERVER = localhostPORT = 3306DATABASE = logUSER = root PASSWORD = 56789</code>
log4cxx.xml
<code><appender name="OdbcMysqlAppender" class="org.apache.log4j.odbc.ODBCAppender"> <param name="URL" value="Driver={MySQL};Server=localhost;Database=log;User=root;Password=56789;"> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="INSERT INTO logs (message) VALUES ('%d - %c - %p - %m')"> </layout></appender><root> <priority value="all"></priority> <appender-ref ref="OdbcMysqlAppender"></appender-ref></root></code>
进展: _Time: 20150702_
查看Log4cxx源码,采用数据库方式记录Log,使用的是ODBCAppender src/main/cpp/odbcappender.cpp
作者原先的代码采用的是 SQLxxxW() 进行DriverConnect和SQLExecDirect操作,根据ODBC的描述,有 W 修饰是采用Unicode编码方式。总之我一直陷在这,一直报找不到数据源。于是乎我将 SQLxxxW()
修改成 SQLxxx()
方式的调用,同时将原先SQLWCHAR
修改成对应 SQLCHAR
,即采用非宽字节的操作方式,成功的找到数据源,并且可以进行调用。
不过这就导致了中文的问题了.
疑惑
在odbcinst.ini中配置的Driver确实是libmyodbc5w.so,即驱动使用Unicode方式的呀! (*与之相对应的是libmyodbc5a.so*). 至今还不知道自己是哪里出错,作者不可能毫无依据的就采用 SQLxxxW() 形式进行ODBC连接的吧.
我在ODBCAppender.cpp中添加了
#define SQL_WCHART_CONVERT,否则make的时候过不去, 即
<code>#if !defined(LOG4CXX)#define LOG4CXX 1#endif#include <log4cxx>#if LOG4CXX_HAVE_ODBC#if defined(WIN32) || defined(_WIN32)#include <windows.h>#endif#define SQL_WCHART_CONVERT#include <sqlext.h>#endif</sqlext.h></windows.h></log4cxx></code>

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

Data Integration Simplification: AmazonRDSMySQL and Redshift's zero ETL integration Efficient data integration is at the heart of a data-driven organization. Traditional ETL (extract, convert, load) processes are complex and time-consuming, especially when integrating databases (such as AmazonRDSMySQL) with data warehouses (such as Redshift). However, AWS provides zero ETL integration solutions that have completely changed this situation, providing a simplified, near-real-time solution for data migration from RDSMySQL to Redshift. This article will dive into RDSMySQL zero ETL integration with Redshift, explaining how it works and the advantages it brings to data engineers and developers.
