前段时间做了essbase的无线协议配置,做个记录,都有些忘记了:-)
1、 essbase的数据库连接设置,采用本地驱动形式libdb2.sl,必须要求数据库名称与配置名称相同
2、 采用essbase的无线协议,不受客户端限制
修改Essbase的olap管理用户下文件:.odbc.ini -> /interdata/olap/bin/.odbc.ini
[mydbname]
#Driver=/interdata/olap/Hyperion/common/ODBC/Merant/4.2/lib/ivdb219.sl
Driver=/interdata/olap/Hyperion/common/ODBC/Merant/4.2/lib/ARdb219.sl
Description=DataDirect 4.20 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Database=mydbname
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=10.228.8.1
IsolationLevel=CURSOR_STABILITY
LogonID=
Password=
#Package=DB2 package name
PackageOwner=
TcpPort=50000
WithHold=1
[ODBC]
IANAAppCodePage=2025
InstallDir=/interdata/olap/Hyperion/common/ODBC/Merant/4.2
Trace=0
TraceDll=/interdata/olap/Hyperion/common/ODBC/Merant/4.2/lib/odbctrac.sl
TraceFile=odbctrace.out
UseCursorLib=0
另外需要编译一个package
/interdata/olap/Hyperion/common/ODBC/Merant/4.2/lib/bind19 mydbname
参考文章:
http://www.ianywhere.com/developer/product_manuals/sqlanywhere/0902/zh/html/dbodzh9/00000048.htm
http://www.ianywhere.com/developer/product_manuals/sqlanywhere/0902/zh/html/dbodzh9/00000046.htm
注:注意无线驱动版本与数据库版本的兼容性,最近升级DB2为9.5,配置无线驱动的时候一直bind19不成功,提示:“Package creation failed!: Command cannot be completed. Bind process is active.”;并且一连接在db2diag.log中提示错误,并生成一堆dump文件,感觉是4.2无线驱动不支持db29.5,后来只好使用第一种方式!