Oracle9i connect sybase use ODBC

hi,everyone
i configure a hsodbc to non-oracle(sqlserver7) database, under win2k platform, it works fine. now i configure it under Solaris platform to Sybase, i download a DataDirect ODBC driver for Sybase. when i create a database link in sqlplus, i select some data from sybase, it work error,error message is:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Generic Connectivity Using ODBC][C077] Could not find symbol 'SQLAllocConnect'
in dynamic library
[C079] Failed to load dynamic library '/opt/odbc/lib/libodbc.so'
i use command elfdump look for SQLAllocConnect symbol, it include in libodbc.so.
my oracle is 9.2.0, anyone know why it run error?

yes, i add the env LD_LIBRARY_PATH in the listener.ora file, but it still work error. the SQLAllocConnect function entry is in the libodbc.so file. generally application using ODBC will call the SQLAllocEnv first, if invokation successful, then invoke the SQLAllocConnect function. i specify HS_FDS_SHAREABLE_NAME = /opt/odbc/lib/libodbc.so in the inithsodbc.ora file, sqlplus should be found SQLAllocConnect.
anyone encounter this situation?

Similar Messages

How to use java+access connectivity without using ODBC

Hello Sir/Madam,
I just want to take a small help from u for using ms-access as backend to java without using the usiual jdbc:odbc bridge.
i'll tell u the scenario which i'm facing now.
i'm in need of sending my software(frame appl.) which uses access as backend to different agencies whom i dont even had contact. so i just dont know what is their status regarding computer knowledge, they might be data-entry-operators or of that type. so i just cant ask them to create an odbc or anything.
so in this case is their any possibility to connect java with ms-access with out creating odbc in windows.
please be kind to solve my problem.
Thanking You,
Ranjith.M

You will need some kind of JDBC driver. And there are
JDBC drivers available for Access that do not use
ODBC, so you could use one of them.There are?

Whats wrong in this code using ODBC interface of T10 in C ?

Hi!
I am trying to connect TimesTen using ODBC in a C application, I am trying to use the dynamic binding of parameters the query. The problem is elaborated in the code. In the comments.
#include <windows.h>
#include <sql.h>
#include <sqlext.h>
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
int main()
SQLRETURN rc = SQL_SUCCESS;
/* General return code for the API */
SQLHENV hEnv = SQL_NULL_HENV;
/* Environment handle */
SQLHDBC hDbc = SQL_NULL_HDBC;
/* Connection handle */
SQLHSTMT hStmt = SQL_NULL_HSTMT;
/* Statement handle */
SQLCHAR ConnOut[255];
/* Buffer for completed connection string */
SQLSMALLINT connOutLen;
/* number of bytes returned in ConnOut */
SQLCHAR ConnString = (SQLCHAR ) "DSN=testTT;PWD=spideradm;";
/* Connection attributes */
rc = SQLAllocEnv(&hEnv);
if (rc != SQL_SUCCESS) {
fprintf(stderr,"Unable to allocate an environment handle\n");
exit(1);
SQLINTEGER param1 = 0;
SQLINTEGER paramstatus = 0;
rc = SQLAllocConnect(hEnv, &hDbc);
rc = SQLDriverConnect(hDbc, NULL,ConnString, SQL_NTS,ConnOut, 255,&connOutLen,SQL_DRIVER_NOPROMPT);
hStmt = SQL_NULL_HSTMT;
rc = SQLAllocStmt(hDbc, &hStmt);
rc = SQLPrepare(hStmt,(SQLCHAR*) "select * from test where recno = ? ",SQL_NTS);
rc = SQLBindParameter(hStmt,1,SQL_PARAM_INPUT,SQL_C_SHORT,SQL_INTEGER,0,0,¶m1,0,¶mstatus);
param1= 1;
rc = SQLExecute(hStmt); // here it goes very perfect
param1 = 2;
rc = SQLExecute(hStmt); // here is the problem it returns -1
}

There are (at least) 3 problems with this code:
1. The error checking after each ODBC call is far too simplistic. Whenever an ODBC call returns something other than SQL_SUCCESS then you need to call the SQLError() function (multiple times in a loop until it returns SQL_NO_DATA) to retrieve the error or warning information which you should then report. If you do that then the error information would give you a clue to the problem.
2. The parameter variable 'param1' is declared as a SQLINTEGER (32-bit integer) but you bind it in the SQLBindParameter() call as a SQL_C_SHORT. This is incorrect and will likely cause problems. It should be bound as a SQL_C_SLONG.
3. When you execute a statement that retrieves data (such as the SELECT statement in your example) a cursor is created. The cursor remains open until (a) you explicitly close it with SQLFreeStmt(hStmt, SQL_CLOSE), or (b) you do a commit or rollback (which closes all open cursors on the connection).
Your problem here is that the first SQLExecute opens a cursor for hStmt but you then do not fetch any data or close the cursor. When you try the second execute you get an error as there is already an open cursor for that statement. If you had used SQLError(0 to retrieve and report the error codes and messages you would see that you had incurred either an 'INVALID CURSOR STATE' or 'FUNCTION SEQUENCE ERROR' error.
The fix is to insert the call:
SQLFreeStmt(hStmt,SQL_CLOSE);
after the each SQLExecute(0 call. Of course, in a real application there would also be a SQLFetch() loop first to retrieve and process the results of the query.
Chris

Connection to Sybase using Connection profile

Hello,
I've been trying to configure a connection profile to
directly connect to a sybase database, but I have issues with the
drivers. At firt I was told that the JDBC drivers jconn3.jar
weren't found, so I downloaded the ones from Sybase :
http://www.sybase.com/products/allproductsa-z/softwaredeveloperkit/jconnect
In the Edit driver definition windows I've deleted the
jconn3.jar and replaced it with the jconnect.zip I just download.
Then I've entered all the details concerning my database, but when
I Test the connection, I get this message :
java.lang.ClassNotFoundException:
com.sybase.jdbc3.jdbc.sybdriver
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native
Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.net.FactoryURLClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at
org.eclipse.datatools.connectivity.db.generic.JDBCConnection.createConnection(JDBCConnect ion.java:86)
at
org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverCo nnectionBase.java:104)
at
org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:53 )
at
org.eclipse.datatools.enablement.sybase.asa.JDBCASAConnectionFactory.createConnection(JDB CASAConnectionFactory.java:32)
at
org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(Co nnectionFactoryProvider.java:77)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(Connection Profile.java:354)
at
org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:57)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Any idea ? Any solutions ?
TIA.

Moreover, I try to create an application module with the view object which has an entity object. This entity object is connect to a table of sybase database. When I try to test this application module and enter the login id and password of the database server. It pop up and error "(oracle.jbo.NotConnectedException) JBO-25200: Application module is not connected to a database". In fact, I use ODBC to connect the sybase server. However, there is no "JDBC-ODBC Bridge" for me to select in the Connection Type of "Oracle Business Component Browser - Connect" wizard. What should I do? Thank you.

Cannot connect to TimesTen using ODBC

Hi,
I have a TT datastore setup on an AIX server. I have a DSN on the AIX server setup in such a fashion that I can connect to the TT datastore and query the TimesTen database.
Now I installed a TT client on my windows XP laptop and I am trying to establish a connection from the ODBC to the AIX TT database.
On the XP client I have setup a dsn as test3 it has the following TTC settings:
TTC_SERVER = aix server name
TTC_SERVER_DSN = CacheData_tt70 (this is the dsn used to connect to tt dadatabase on the AIX server machine)
TTC_TIMEOUT = 60
Now when I try connecting from the Windows XP box I use the following command:
connect "dsn=test3;UID=ttadmin;PWD=ttadmin";
I am getting the following message:
12701: DatabaseCharacterSet attribute required for data store creation. Refer to the TimesTen documentation for information on selecting a character set.
What I don't understand is that I have ALREADY created the datastore on the AIX server. I do not see what the issue is here.
Last thing ......The datastore was created with character set AL32UTF8. The Oracle database that is used in the Cache Connect was created w/ a character set of AL32UTF8.
Any help from anyone would be appreciated.
Regards Chris Tabb

Hi Susan,
The .ODBC.INI file on AIX is quite long (sorry for that). I am using the "CacheData_tt70", here it is:
# Copyright (C) 1999, 2007, Oracle. All rights reserved.
# The following are the default values for connection attributes.
# In the Data Sources defined below, if the attribute is not explicitly
# set in its entry, TimesTen 7.0 uses the defaults as
# specified below. For more information on these connection attributes,
# see the accompanying documentation.
# Lines in this file beginning with # or ; are treated as comments.
# In attribute=_value_ lines, the value consists of everything
# after the = to the end of the line, with leading and trailing white
# space removed.
# Authenticate=1 (client/server only)
# AutoCreate=1
# CkptFrequency (if Logging == 1 then 600 else 0)
# CkptLogVolume=0
# CkptRate=0 (0 = rate not limited)
# ConnectionCharacterSet (if DatabaseCharacterSet == TIMESTEN8
# then TIMESTEN8 else US7ASCII)
# ConnectionName (process argv[0])
# Connections=64
# DatabaseCharacterSet (no default)
# Diagnostics=1
# DurableCommits=0
# ForceConnect=0
# GroupRestrict (none by default)
# Isolation=1 (1 = read-committed)
# LockLevel=0 (0 = row-level locking)
# LockWait=10 (seconds)
# Logging=1 (1 = write log to disk)
# LogAutoTruncate=1
# LogBuffSize=65536 (measured in KB)
# LogDir (same as checkpoint directory by default)
# LogFileSize=64 (measured in MB)
# LogFlushMethod=0
# LogPurge=1
# MatchLogOpts=0
# MemoryLock=0 (HP-UX, Linux, and Solaris platforms only)
# NLS_LENGTH_SEMANTICS=BYTE
# NLS_NCHAR_CONV_EXCP=0
# NLS_SORT=BINARY
# OverWrite=0
# PermSize=2 (measured in MB; default is 2 on 32-bit, 4 on 64-bit)
# PermWarnThreshold=90
# Preallocate=0
# PrivateCommands=0
# PWD (no default)
# PWDCrypt (no default)
# RecoveryThreads=1
# SQLQueryTimeout=0 (seconds)
# Temporary=0 (data store is permanent by default)
# TempSize (measured in MB; default is derived from PermSize,
# but is always at least 6MB)
# TempWarnThreshold=90
# TypeMode=0 (0 = Oracle types)
# UID (operating system user ID)
# WaitForConnect=1
# Oracle Loading Attributes
# OracleID (no default)
# OraclePWD (no default)
# PassThrough=0 (0 = SQL not passed through to Oracle)
# RACCallback=1
# TransparentLoad=0 (0 = do not load data)
# Client Connection Attributes
# ConnectionCharacterSet (if DatabaseCharacterSet == TIMESTEN8
# then TIMESTEN8 else US7ASCII)
# ConnectionName (process argv[0])
# PWD (no default)
# PWDCrypt (no default)
# TTC_Server (no default)
# TTC_Server_DSN (no default)
# TTC_Timeout=60
# UID (operating system user ID)
[ODBC Data Sources]
TT_tt70=TimesTen 7.0 Driver
TpcbData_tt70=TimesTen 7.0 Driver
TptbmDataRepSrc_tt70=TimesTen 7.0 Driver
TptbmDataRepDst_tt70=TimesTen 7.0 Driver
TptbmData_tt70=TimesTen 7.0 Driver
BulkInsData_tt70=TimesTen 7.0 Driver
WiscData_tt70=TimesTen 7.0 Driver
RunData_tt70=TimesTen 7.0 Driver
CacheData_tt70=TimesTen 7.0 Driver
ttdbgdev=TimesTen 7.0 Driver
TpcbDataCS_tt70=TimesTen 7.0 Client Driver
TptbmDataCS_tt70=TimesTen 7.0 Client Driver
BulkInsDataCS_tt70=TimesTen 7.0 Client Driver
WiscDataCS_tt70=TimesTen 7.0 Client Driver
RunDataCS_tt70=TimesTen 7.0 Client Driver
ttdbgdevCS=TimesTen 7.0 Driver
# Instance-Specific System Data Store
# A predefined instance-specific data store reserved for system use.
# It provides a well-known data store for use when a connection
# is required to execute commands.
[TT_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/TT_tt70
DatabaseCharacterSet=US7ASCII
# Data source for TPCB
# This data store is created on connect; if it doesn't already exist.
# (AutoCreate=1 and Overwrite=0). For performance reasons, database-
# level locking is used. However, logging is turned on. The initial
# size is set to 16MB.
[TpcbData_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/TpcbData
DatabaseCharacterSet=US7ASCII
PermSize=16
WaitForConnect=0
Authenticate=0
# Data source for TPTBM demo
# This data store is created everytime the benchmark is run.
# Overwrite should always be 0 for this benchmark. All other
# attributes may be varied and performance under those conditions
# evaluated. The initial size is set to 20MB and durable commits are
# turned off.
[TptbmData_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/TptbmData
DatabaseCharacterSet=US7ASCII
PermSize=20
Overwrite=0
Authenticate=0
# Source data source for TPTBM demo in replication mode
# This data store is created everytime the replication benchmark demo
# is run. This datastore is set up for the source data store.
[TptbmDataRepSrc_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/TptbmDataRepSrc_tt70
DatabaseCharacterSet=US7ASCII
PermSize=20
Overwrite=0
Authenticate=0
# Destination data source for TPTBM demo in replication mode
# This data store is created everytime the replication benchmark demo
# is run. This datastore is set up for the destination data store.
[TptbmDataRepDst_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/TptbmDataRepDst_tt70
DatabaseCharacterSet=US7ASCII
PermSize=20
Overwrite=0
Authenticate=0
# Data source for BULKINSERT demo
# This data store is created on connect; if it doesn't already exist
# (AutoCreate=1 and Overwrite=0).
[BulkInsData_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/BulkInsData
DatabaseCharacterSet=US7ASCII
LockLevel=1
PermSize=32
WaitForConnect=0
Authenticate=0
# Data source for WISCBM demo
# This data store is created on connect if it doesn't already exist
# (AutoCreate=1 and Overwrite=0). For performance reasons,
# database-level locking is used. However, logging is turned on.
[WiscData_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/WiscData
DatabaseCharacterSet=US7ASCII
LockLevel=1
PermSize=16
WaitForConnect=0
Authenticate=0
# Default Data source for TTISQL demo and utility
# Use default options.
[RunData_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/RunData
DatabaseCharacterSet=US7ASCII
Authenticate=0
# Sample Data source for the xlaSimple demo
# See manual for discussion of this demo.
[Sample_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/Sample
DatabaseCharacterSet=US7ASCII
TempSize=16
PermSize=16
Authenticate=0
# Sample data source using OracleId.
# Before using the CacheData DSN, uncomment both the OracleId and
# DatabaseCharacterSet attributes and insert the appropriate values for
# the name of your Oracle database and its database character set.
# See the jdbc demo README for information on how to obtain these values.
[CacheData_tt70]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.a
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/Test1
DatabaseCharacterSet=AL32UTF8
OracleId=dbgdev
PermSize=16
UID=oracle
# Authenticate=1
# New data source definitions can be added below.
[ttdbgdev]
Driver=/u01/app/oracle/TimesTen/tt70/lib/libtten.so
DataStore=/u01/app/oracle/TimesTen/tt70/info/DemoDataStore/Test1
PermSize=20
TempSize=20
DatabaseCharacterSet=AL32UTF8
#UID=chris
OracleID=dbgdev
# This following sample definitions should be in the .odbc.ini file
# that is used for the TimesTen 7.0 Client.
# The Server Name is set in the TTC_SERVER attribute.
# The Server DSN is set in the TTC_SERVER_DSN attribute.
# Data source for TPCB
[TpcbDataCS_tt70]
TTC_SERVER=LocalHost_tt70
TTC_SERVER_DSN=TpcbData_tt70
# Data source for TPTBM demo
[TptbmDataCS_tt70]
TTC_SERVER=LocalHost_tt70
TTC_SERVER_DSN=TptbmData_tt70
# Data source for BULKINSERT demo
[BulkInsDataCS_tt70]
TTC_SERVER=LocalHost_tt70
TTC_SERVER_DSN=BulkInsData_tt70
# Data source for WISCBM demo
[WiscDataCS_tt70]
TTC_SERVER=LocalHost_tt70
TTC_SERVER_DSN=WiscData_tt70
# Default Data source for TTISQL demo and utility
[RunDataCS_tt70]
TTC_SERVER=LocalHost_tt70
TTC_SERVER_DSN=RunData_tt70
# Default Data Source for ttdbgdev
[ttdbgdevCS]
TTC_SERVER=LocalHost_tt70
TTC_SERVER_DSN=ttdbgdev
Now for the Windows ODBC.ini file, I am trying to use the "Test3" connection. Specifics of this connection are in the windows registry. Please note I have tried setting the connectionCharacterSet to AL32UTF8 as well as a few others:
[ODBC 32 bit Data Sources]
dwhdev=Oracle in OraHome92 (32 bit)
dwhqas=Oracle in OraHome92 (32 bit)
RunDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
TpcbDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
TptbmDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
BulkInsDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
WiscDataCS_tt70_32=TimesTen Client 7.0 (32 bit)
test1=TimesTen Client 7.0 (32 bit)
MS Access Database=Microsoft Access Driver (*.mdb) (32 bit)
Excel Files=Microsoft Excel Driver (*.xls) (32 bit)
dBASE Files=Microsoft dBase Driver (*.dbf) (32 bit)
test2=TimesTen Client 7.0 (32 bit)
test3=TimesTen Client 7.0 (32 bit)
dbgdev=Oracle in OraHome92 (32 bit)
[dwhdev]
Driver32=c:\oracle\BIN\SQORA32.DLL
[dwhqas]
Driver32=c:\oracle\BIN\SQORA32.DLL
[RunDataCS_tt70_32]
Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
[TpcbDataCS_tt70_32]
Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
[TptbmDataCS_tt70_32]
Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
[BulkInsDataCS_tt70_32]
Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
[WiscDataCS_tt70_32]
Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
[test1]
Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
[MS Access Database]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[Excel Files]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[dBASE Files]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[test2]
Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
[test3]
Driver32=C:\TimesTen\tt70_32\bin\ttcl70.dll
[dbgdev]
Driver32=c:\oracle\BIN\SQORA32.DLL
Regards,
Chris

How can I connect to the database using ODBC within excel.

Hi,
How can I connect to the database using ODBC within excel and just refresh the data when needed.
Thanks,
Priyanka
Edited by: user554934 on Jun 9, 2009 2:53 AM

This is NOT an APEX relevant question, try posting it in the SQL/PL/SQL Forum..
Thank you,
Tony Miller
Webster, TX

How to connect sybase database in JDeveloper 11g using JConnect

Hi
How to connect sybase database in JDeveloper 11g using JConnect? Please help.

User,
It would help if you explained Sybase Jconnect instead of leaving us to google.
At any rate, it appears you need to create a library definition in JDeveloper, add the appropriate JConnect JAR files to the library's classpath, and then add the library to your project.
John

Problem using JDBC to connect to WBEM ODBC driver

Hello,
I've got a problem to connect to WBEM ODBC driver using JDBC. The error is:
exception due a la requetejava.sql.SQLException: [Microsoft][WBEM ODBC Driver]Unable to connect
When I try to connect to a MS access database, replacing only the ODBC source name, it's working. I can access to the MS access db. But when I put the WMI ODBC source name, WMI, I've got this error.
Does anybody know what could happened? Is it possible to access to WMI through JDBC? With MS access, accessing WMI ODBC is working !
Thanks very much for your help.
Here is the part of the source code :
import java.sql.*;
import java.io.*;
public class Main_1 {
/** Creates a new instance of Main_1 */
public Main_1() {
* @param args the command line arguments
public static void main(String[] args) {
try {
String url = "jdbc:odbc:WMI";
Class.forName ("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con = DriverManager.getConnection(url);
String query = "Select * from Win32_Processor";
//String query = "Select * from test;";
ResultSet results;
Statement stmt = con.createStatement();
results = stmt.executeQuery(query);
//System.out.println (results);
catch(Exception e){
System.out.println("exception due a la requete" + e);
e.printStackTrace();
}

you have to first start the network listener before you can run the program
start TNSLSNR before running the jdbc program

Connect to SQL Server by using ODBC

We use ODBC to connect to a Microsoft SQL Server database. We are able to describe and select in Oracle for those tables (in MS SQL) granted to us. However, we cannot select on the views created in MS SQL. Do we miss something? Here is the SQL statement in MS SQL:
ELECT MRN, SSN, MaritalStatus, LastName, FirstName, MiddleName, MMaidenName, Address, City, State, Phone, DOB, CitizenshipStat, AlienNumber,
ELADocType, ELASecNo, ELAExpDate, ELAISUDate, PCC, PCCCode, PCP, FileDate, LastUpdate, SystemDate, [TimeStamp], SystemSource,
ENR_HASH_NO, ActiveMRN, RIGHT(PCCCode, 4) AS PCCshortname, AutoAssignPCC, AutoAssignPCCTimeStamp, AutoAssignInactivate,
ActivePanelAssignment, ActivePanelIND
FROM dbo.tblPatient
WHERE (DeceasedIND <> 'Y') AND (IsTestPatient <> 'NY')

Here is the sql statment:
SELECT MRN, SSN, MaritalStatus, LastName, FirstName, MiddleName, MMaidenName, Address, City, State, Phone, DOB, CitizenshipStat, AlienNumber,
ELADocType, ELASecNo, ELAExpDate, ELAISUDate, PCC, PCCCode, PCP, FileDate, LastUpdate, SystemDate, [TimeStamp], SystemSource,
ENR_HASH_NO, ActiveMRN, RIGHT(PCCCode, 4) AS PCCshortname, AutoAssignPCC, AutoAssignPCCTimeStamp, AutoAssignInactivate,
ActivePanelAssignment, ActivePanelIND
FROM dbo.tblPatient
WHERE (DeceasedIND <> 'Y') AND (IsTestPatient <> N'Y')

MS Access .mdb connection using ODBC could not resolve the connect identifier ORA-12154

Dear All,
I'm trying to use MS Access .mdb file as source to my OWB application. I need to connect to the ms access .mdb file first using odbc. Here are the step I do:
1. Define ODBC connectifity
     control panel -> admin tools -> data sources -> System DSN -> Add
     Choose Microsoft Access Driver (*.mdb) -> Finish
     Data source name: msaccess -> Database: Select -> .mdb file location (C:\MSAccess\att2000..mdb)
2. Configure Listener
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = CLRExtProc)
      (ORACLE_HOME = C:\app\Administrator\product\11.2.0\dbhome_1)
      (PROGRAM = extproc)
      (ENVS = "EXTPROC_DLLS=ONLY:C:\app\Administrator\product\11.2.0\dbhome_1\bin\oraclr11.dll")
    (SID_DESC =
      (SID_NAME = msaccess
      (ORACLE_HOME = C:\app\Administrator\product\11.2.0\dbhome_1)
      (PROGRAM = hsodbc)
LISTENER =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (SID_DESC =
      (SID_NAME = msaccess
      (ORACLE_HOME = C:\app\Administrator\product\11.2.0\dbhome_1)
      (PROGRAM = hsodbc)
ADR_BASE_LISTENER = C:\app\Administrator
3. Configure Oracle HS
     File name initmsaccess.ora
# HS init parameters
HS_FDS_CONNECT_INFO = msaccess
HS_FDS_TRACE_LEVEL = 1
# Environment variables required for the non-Oracle system
#set <envvar>=<value>
4. Edit tnsnames.ora
msaccess=
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (CONNECT_DATA =
      (SID=msaccess)
      (SERVICE_NAME=msaccess)
(HS=OK)
5. create database link
create database link msaccess using 'msaccess';
6. Run a query to test connection
SQL> select * from departments@msaccess;
ERROR at line 1:
ORA-12154: TNS:could not resolve the connect identifier specified
I check the tns using tnsping msaccess, it return
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhos
t)(PORT = 1521)) (CONNECT_DATA = (SID=msaccess) (SERVICE_NAME=msaccess)) (HS=OK))
OK (120 msec)
Any body know how to solve this?
Best Regards
Akhmad H Gumas

Klaus,
just fix the point you mention.
here are the execution result:
C:\>C:\app\Administrator\product\11.2.0\dbhome_1\bin\lsnrctl status
LSNRCTL for 32-bit Windows: Version 11.2.0.1.0 - Production on 05-AUG-2014 17:10
:23
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 32-bit Windows: Version 11.2.0.1.0 - Produ
ction
Start Date                05-AUG-2014 17:09:18
Uptime                    0 days 0 hr. 1 min. 5 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   C:\app\Administrator\product\11.2.0\dbhome_1\network\a
dmin\listener.ora
Listener Log File         c:\app\administrator\diag\tnslsnr\eric-fd165f15bb\list
ener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "msaccess" has 1 instance(s).
Instance "msaccess", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
C:\>C:\app\Administrator\product\11.2.0\dbhome_1\bin\dg4odbc
Oracle Corporation --- TUESDAY   AUG 05 2014 17:12:18.509
Heterogeneous Agent Release 11.2.0.1.0 - Production Built with
   Oracle Database Gateway for ODBC
C:\>C:\app\Administrator\product\11.2.0\dbhome_1\bin\tnsping msaccess
TNS Ping Utility for 32-bit Windows: Version 11.2.0.1.0 - Production on 05-AUG-2
014 17:12:48
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
C:\app\Administrator\product\11.2.0\dbhome_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhos
t)(PORT = 1521)) (CONNECT_DATA = (SID=msaccess)) (HS=OK))
OK (20 msec)
Looks like the problem is the missing closing bracket. Finally the query work after i fix it. Thanks a lot Klaus
Best Regards
Akhmad H Gumas

Problem connecting Dev server using odbc

We are running siebel 8.0.0.5 on solaris 10 on Oracle DB (10.2.0.4). We are planning to upgrade it to siebel 8.1.1.10. I just want you to help me with few parameters and executables as me new in SADMIN . When tried using odbc connection on dev its througing below mentioned errors
To check the ODBC connection:-
Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:-
odbcsql /u database_account_name /p password /s OBDC_DSN
bash-3.00$ pwd
/appl/siebel/siebsrvr/bin
bash-3.00$
bash-3.00$ ./odbcsql /u sadmin /p sadmin123
ld.so.1: odbcsql: fatal: libsslcosa.so: open failed: No such file or directory
Killed
bash-3.00$
bash-3.00$
bash-3.00$ ./odbcsql
ld.so.1: odbcsql: fatal: libsslcosa.so: open failed: No such file or directory
Killed
bash-3.00$
bash-3.00$ odbcsql
bash: odbcsql: command not found

Also verify the access provided to the library files and entries mentioned in the .odbc.ini file in /siebsrvr/sys folder. ODCBSQL depends on the entries in this file.

Memory leak when using database connectivity toolset and ODBC driver for MySQL

The "DB Tools Close Connection VI" does not free all the memory used when "DB Tools Open Connection VI" connects to "MySQL ODBC Driver 3.51".
I have made a small program that only opens and close the connection that I run continously and it's slowly eating all my memory. No error is given from any of the VI's. (I'm using the "Simple Error Handler VI" to check for errors.)
I've also tried different options in the DSN configuration without any results.
Attachments:
TestProgram.vi ‏16 KB
DSNconfig1.jpg ‏36 KB
DSNconfig2.jpg ‏49 KB

Also,
I've duplicated the OPs example: a simple VI that opens and closes a connection. I can say this definately causes a memory leak.
Watching the memory:
10:17AM - 19308K
10:19AM - 19432K
10:22AM - 19764K
10:58AM - 22124K
Regards,
Ken
Attachments:
OpenCloseConnection.vi ‏13 KB

Long Connection Times Using ADO/ODBC and VB

I have written a Visual Basic program that connects to Oracle on the Unix server. When I first issue the connect command it takes 3 minutes to actually open the database. Once I am connected the program functions very efficiently. When I run the same program against Oracle running under windows NT, it takes 30 seconds to connect to the database.
Any suggestions on why it would take 3+ minutes to just connect to the database on the Unix server?
Here is the code I use to connect to the database...
Conn = "UID=xxxx;PWD=xxxx;DRIVER={Microsoft ODBC for Oracle};" _
& "SERVER=" & P_DataBase & ";"
' Connect to the database
Set Cn = New ADODB.Connection
' Open the database
With Cn
.ConnectionString = Conn
.CursorLocation = adUseClient
.Open Cn
End With
Thanks for any help you can provide
Tim

A ping goes rather quickly, and the TNSNAMES.ORA file already contains the IP address. I have other software that connects to the Oracle server just fine without a long delay. I am not sure if this other software uses ODBC, it is a package software. I was begining to think I might have miscoded the connection in the VB program?
Tim

Which data flow source type to use when specifying a connection manager using an ODBC provider

I'm trying to create a SSIS package to connect to an IBM iSeries DB2 database. After running into all sorts of issues seemingly related to data type (issues with packed decimal fields actually having places to the right of the decimal) I decided to
try creating an ODBC data source on my windows server 2008 r2 Administrative Tools - Data Sources ODBC to connect to the iSeries and then create an SSIS connection manager to use the windows ODBC connection. Successfully created the ODBC connection in
windows then successfully added a SSIS connection manger to my project using the windows ODBC connection and tested the connection manager successfully. To create the connection manager I RMB in the connection manager section - select new connection
- select ODBC - select the newly created ODBC connection from the list and operate the ok button. Edited the connection manager specified the userid and pw and connected succcessfully.
Problem is I don't seem to be able to find a Data Flow Source in the SSIS tool box that will let me specify the connection manager using the ODBC connection. The Data Flow Sources in my tool box are "Pointer", "ADO NET Source",
"Excel Source", "Flat File Source", "OLE DB Source", "Raw File Source" and "XML Source".
Can someone kindly show me what Data Flow Source I should be using and how to specify my SSIS connection manager that uses the windows ODBC connection?
Thanks Much in advance for any help, Roscoe

This would help you
http://social.msdn.microsoft.com/Forums/en-US/c688b646-28bb-44b9-b53b-fddf23e15189/how-to-connect-to-odbc-using-ssis?forum=sqlintegrationservices
Abhinav http://bishtabhinav.wordpress.com/

How connect the oracle/Linux using ODBC

I want to connect the Oracle which install on Linux using Odbc, so my win98 machine can connect with the oracle.
But I don't know how to do ? May I install some Odbc driver in the Linux machine? and install odbc driver in my win98 machine?
my email: [email protected]

You may use this way:
1. Start on the server (Linux) Net*8 listener (lsnrctl start)
2. Install on the client (win98) Net*8 and configure it (Net8 Easy Configuration)
3. Install on the client (win98) ODBC drivers for ORACLE (by ORACLE or others) and configure it

Oracle9i connect sybase use ODBC

Similar Messages

Maybe you are looking for