ODBC crash in OCIStmtExecute
Here's windbg call stack. I'm using Oracle ODBC 8.1.7.8.10 (it's maybe the lastest version.) on Windows 2000 server with 4 CPUs.
oran8!nsdo+0x20
oran8!xaolog+0x26546
OraClient8!xaolog+0x26546
OraClient8!xaolog+0x2086f
OraClient8!upirtr+0xbd
OraClient8!kpurcs+0x8d
OraClient8!kpuertb_reallocTempBuf+0x1060
OraClient8!kpuertb_reallocTempBuf+0x30bb
OraClient8!OCIStmtExecute+0x28
OCI!OCIStmtExecute+0x37
SQORA32!fLoginDlg+0xe9e5
I don't know why process sometimes crashed in OCIStmeExecute. Please help me if you know the reason or ODBC debug solution.
Thanks.
The following are contents of /etc/release in Sol10 ( running machine )
Solaris 10 1/06 s10s_u1wos_19a SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 December 2005The following are contents of /etc/release in Sol8 ( Compiler machine )
Solaris 8 2/04 s28s_hw4wos_05a SPARC
Copyright 2004 Sun Microsystems, Inc. All Rights Reserved.
Assembled 08 January 2004For 2, 3 i will try and told you later
Thanks
Similar Messages
-
Administrator ODBC crash and restart
Hi all, I get the follow error:
> odbc administrator a problem caused the program to stop working correctly. The windows will close the program and notifies you if there is a possible solution.
I get the above error when I try add a DSN System Connection. The Administrator ODBC crash and restart.
Issue as with Windows 7 Professional 64Bits - to connect to a SQL Studio 2012 (Pro).
The issue only appens at this particulary machine, on others are fine.
How can I fix this?
Thank youthank you for your reply @Elvis Long
here is the Thread open at IT Pro hxxp://social.technet.microsoft.com/Forums/en-US/a7980c6e-f674-41ce-acda-9e8e68d27a12/administrator-odbc-crash-and-restart?forum=w7itprogeneral
In case here the msg
Problem signature:
Problem EventName:BEX
Application Name:odbcad32.exe
Application Version:6.1.7600.16385
StampDate / TimeofApplication:4a5bcd4c
FaultModuleName:sqlsrv32.dll_unloaded
FaultyModule Version:0.0.0.0
StampDate / TimeModulewithFailures:4ce7ba09
DeviationException:73358bf5
Exception code:C0000005
ExceptionData:00000008
OS Version:6.1.7601.2.1.0.256.48
RegionID:2070
Additional Information 1:0a9e
Additional Information 2:0a9e372d3b4ad19135b953a78882e789
Additional Information 3:0a9e
Additional Information 4:0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
go.microsoft.com/fwlink/?linkid=104288&clcid=0x0816
If theonline privacy statementis not available,please readour privacy statement
offline:
C:\Windows\system32\pt-PT\erofflps.txtt
(I have translate msg, the machines are in pt-PT)</quote>
I have reinstall OS at Windows 7 Pro 64bits. But problem presist.
btw: SQL Server run in a dedicated machine (Windows Server 2012 Standart Edition - SSD 500GB - 16GB of Ram - Intel Xeon [email protected] - 64bits) -
I have a repeatable crash on Solaris Sparc 32 bit.
I use a table created by
CREATE TABLE "IAN"."PICDAR_MANIFEST"
( "OBJECT_NAME" VARCHAR2(64 BYTE),
"OBJECT_TYPE" VARCHAR2(10 BYTE),
"COUNT" NUMBER,
"FILE_NAME" VARCHAR2(32 BYTE),
"FIELD_NAME" VARCHAR2(32 BYTE),
PRIMARY KEY ("OBJECT_NAME")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "IAN" ENABLE
) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "IAN" ;
and populated using
Insert into PICDAR_MANIFEST (OBJECT_NAME,OBJECT_TYPE,COUNT,FILE_NAME,FIELD_NAME) values ('publicationtext_AUDIT','COUNTER',98,null,null);
I have configured the ODBC using instant client 10.2.0.3 using
odbcinst.ini
[Oracle 10g ODBC Driver]
Description = Oracle ODBC driver for Oracle 10g
Driver = /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
Setup =
FileUsage =
CPTimeout =
CPReuse =
and
odbc.ini
[Ian]
Application Attributes = T
Attributes = W
BatchAutocommitMode = IfAllSuccessful
CloseCursor = F
DisableDPM = F
DisableMTS = T
Driver = Oracle 10g ODBC Driver
DSN = Noddles
EXECSchemaOpt =
EXECSyntax = T
Failover = T
FailoverDelay = 10
FailoverRetryCount = 10
FetchBufferSize = 64000
ForceWCHAR = F
Lobs = T
Longs = T
MetadataIdDefault = F
QueryTimeout = T
ResultSets = T
ServerName = aserver:1522/IAN.ASERVER.ACOMPANY.CO.UK
SQLGetData extensions = F
Translation DLL =
Translation Option = 0
UserID =
When I connect using UnixODBC's isql and execute select * from picdar_manifest it crashes at
#0 0xfe6d979c in bcoConvertFromFloat () from /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
#1 0xfe6d8acc in bcoConvertOciToOdbc () from /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
#2 0xfe6d829c in bcoConvert () from /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
#3 0xfe734314 in bcoTypeCopyLibToSqlc () from /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
#4 0xfe6f50c4 in bcoReturnColData () from /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
#5 0xfe6f94c0 in bcoDBgetdata () from /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
#6 0xfe6f8fec in bcoSQLGetData () from /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
#7 0xfe69f7bc in SQLGetData () from /m/jbod1/oracle/instantclient_10_2/libsqora.so.10.1
#8 0x000248a8 in SQLGetData (statement_handle=0x171ca8, column_number=3, target_type=1,
target_value=0xffbef2b8, buffer_length=301, strlen_or_ind=0xffbef2b0) at SQLGetData.c:439
#9 0x00015c90 in WriteBodyNormal (hStmt=0x171ca8) at isql.c:886
#10 0x00016d84 in main (argc=501760, argv=0x7a800) at isql.c:433
This is clearly in the Oracle driver.
I don't believe I am doing anything wrong because doing exactly the same thing on Linux works just fine (also using instant client release 10.2.0.3).
Has anyone else seen a similar problem?
Is there a solution?
Cheers,
IanI'm not from Oracle, but I'll try and help you nevertheless :)
First, Solaris and other real UNIX systems are much more picky about memory than Linux. I've seen countless applications fail when going from Linux to Solaris, HP-UX, or AIX; almost all of which are just using memory incorrectly. Linux is just more forgiving, which means you need to do more memory bound/leak checking. Nevertheless, that's just a bit of info on UNIX vs. Linux in application porting; it shouldn't have anything to do with Oracle's ODBC driver though.
The thing is, I'm seeing odd memory issues with 10.2.0.3 on Linux (x86_64) as well. What version are you using on Linux? -
JDBC:ODBC Crashes in driver when doing update
I am getting a crash in the native code when trying to update a record through an updateable record set using the JDBC:ODBC bridge. I have appended the crash information at the bottom of this message gotten from the Forte output window. This is going to SQL Server 2000. Through the Beta JDBC driver everything works fine, but through ODBC it always crashes no matter what columns I pick so it doesn't seem to be data type related. I would just use the JDBC driver, but that is not a option for some of our clients. I have used Insert statements without a problem, but one of the fields in one table is a BLOB field and I don't know of any way to access it except through an updatable record set.
Does anyone have any ideas about how I might get around this?
Thanks
Scott Herter
Napersoft, Inc.
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x411611BD
Function=Ordinal78+0x11BD
Library=C:\WINNT\System32\SQLSRV32.dll
Current Java thread:
at sun.jdbc.odbc.JdbcOdbc.setPos(Native Method)
at sun.jdbc.odbc.JdbcOdbc.SQLSetPos(JdbcOdbc.java:4709)
at sun.jdbc.odbc.JdbcOdbcResultSet.setPos(JdbcOdbcResultSet.java:5019)
at sun.jdbc.odbc.JdbcOdbcResultSet.updateRow(JdbcOdbcResultSet.java:4053)
at DBTest.UpdateBlob(DBTest.java:445)
at DBTest.main(DBTest.java:64)
Dynamic libraries:
0x00400000 - 0x00406000 G:\Forte\JDK14~1.0\bin\java.exe
0x77F80000 - 0x77FFB000 C:\WINNT\System32\ntdll.dll
0x77DB0000 - 0x77E0C000 C:\WINNT\system32\ADVAPI32.dll
0x77E80000 - 0x77F35000 C:\WINNT\system32\KERNEL32.DLL
0x77D40000 - 0x77DAD000 C:\WINNT\system32\RPCRT4.DLL
0x78000000 - 0x78046000 C:\WINNT\system32\MSVCRT.dll
0x6D330000 - 0x6D442000 G:\Forte\JDK14~1.0\jre\bin\client\jvm.dll
0x77E10000 - 0x77E74000 C:\WINNT\system32\USER32.dll
0x77F40000 - 0x77F7C000 C:\WINNT\system32\GDI32.DLL
0x77570000 - 0x775A0000 C:\WINNT\System32\WINMM.dll
0x6D1D0000 - 0x6D1D7000 G:\Forte\JDK14~1.0\jre\bin\hpi.dll
0x6D300000 - 0x6D30D000 G:\Forte\JDK14~1.0\jre\bin\verify.dll
0x6D210000 - 0x6D228000 G:\Forte\JDK14~1.0\jre\bin\java.dll
0x6D320000 - 0x6D32D000 G:\Forte\JDK14~1.0\jre\bin\zip.dll
0x6D260000 - 0x6D27C000 G:\Forte\JDK14~1.0\jre\bin\jdwp.dll
0x6D160000 - 0x6D166000 G:\Forte\jdk1.4.0\jre\bin\dt_shmem.dll
0x6D2D0000 - 0x6D2DD000 G:\Forte\jdk1.4.0\jre\bin\net.dll
0x75050000 - 0x75058000 C:\WINNT\System32\WSOCK32.dll
0x75030000 - 0x75043000 C:\WINNT\System32\WS2_32.DLL
0x75020000 - 0x75028000 C:\WINNT\System32\WS2HELP.DLL
0x785C0000 - 0x785CC000 C:\WINNT\System32\rnr20.dll
0x77980000 - 0x779A4000 C:\WINNT\System32\DNSAPI.DLL
0x77340000 - 0x77353000 C:\WINNT\System32\iphlpapi.dll
0x77520000 - 0x77525000 C:\WINNT\System32\ICMP.DLL
0x77320000 - 0x77337000 C:\WINNT\System32\MPRAPI.DLL
0x75150000 - 0x75160000 C:\WINNT\System32\SAMLIB.DLL
0x75170000 - 0x751BF000 C:\WINNT\System32\NETAPI32.DLL
0x77BE0000 - 0x77BEF000 C:\WINNT\System32\SECUR32.DLL
0x751C0000 - 0x751C6000 C:\WINNT\System32\NETRAP.DLL
0x77950000 - 0x7797A000 C:\WINNT\system32\WLDAP32.DLL
0x77A50000 - 0x77B3A000 C:\WINNT\system32\OLE32.DLL
0x779B0000 - 0x77A4B000 C:\WINNT\system32\OLEAUT32.DLL
0x773B0000 - 0x773DE000 C:\WINNT\System32\ACTIVEDS.DLL
0x77380000 - 0x773A2000 C:\WINNT\System32\ADSLDPC.DLL
0x77830000 - 0x7783E000 C:\WINNT\System32\RTUTILS.DLL
0x77880000 - 0x7790D000 C:\WINNT\System32\SETUPAPI.DLL
0x77C10000 - 0x77C6E000 C:\WINNT\System32\USERENV.DLL
0x774E0000 - 0x77512000 C:\WINNT\System32\RASAPI32.DLL
0x774C0000 - 0x774D1000 C:\WINNT\System32\RASMAN.DLL
0x77530000 - 0x77552000 C:\WINNT\system32\TAPI32.DLL
0x716F0000 - 0x7177A000 C:\WINNT\system32\COMCTL32.DLL
0x70BD0000 - 0x70C1C000 C:\WINNT\system32\SHLWAPI.DLL
0x77360000 - 0x77379000 C:\WINNT\System32\DHCPCSVC.DLL
0x775A0000 - 0x77625000 C:\WINNT\System32\CLBCATQ.DLL
0x777E0000 - 0x777E8000 C:\WINNT\System32\winrnr.dll
0x777F0000 - 0x777F5000 C:\WINNT\System32\rasadhlp.dll
0x74FD0000 - 0x74FEF000 C:\WINNT\system32\msafd.dll
0x75010000 - 0x75017000 C:\WINNT\System32\wshtcpip.dll
0x6D250000 - 0x6D25A000 G:\Forte\jdk1.4.0\jre\bin\JdbcOdbc.dll
0x1F7F0000 - 0x1F825000 C:\WINNT\System32\ODBC32.dll
0x76B30000 - 0x76B6E000 C:\WINNT\system32\comdlg32.dll
0x782F0000 - 0x7852F000 C:\WINNT\system32\SHELL32.DLL
0x1F8E0000 - 0x1F8F6000 C:\WINNT\System32\odbcint.dll
0x41160000 - 0x411D3000 C:\WINNT\System32\SQLSRV32.dll
0x41090000 - 0x410BD000 C:\WINNT\System32\SQLUNIRL.DLL
0x77800000 - 0x7781D000 C:\WINNT\System32\WINSPOOL.DRV
0x77820000 - 0x77827000 C:\WINNT\system32\VERSION.dll
0x759B0000 - 0x759B6000 C:\WINNT\system32\LZ32.DLL
0x769A0000 - 0x769A7000 C:\WINNT\System32\NDDEAPI.DLL
0x0F470000 - 0x0F486000 C:\WINNT\System32\sqlsrv32.rll
0x0F4A0000 - 0x0F4BA000 C:\WINNT\System32\odbccp32.dll
0x74CB0000 - 0x74CC7000 C:\WINNT\System32\DBNETLIB.DLL
0x75500000 - 0x75504000 C:\WINNT\System32\security.dll
0x77440000 - 0x774B5000 C:\WINNT\System32\crypt32.dll
0x77430000 - 0x77440000 C:\WINNT\System32\MSASN1.DLL
0x782D0000 - 0x782EE000 C:\WINNT\system32\msv1_0.dll
0x77BF0000 - 0x77C01000 C:\WINNT\System32\ntdsapi.dll
0x74CD0000 - 0x74CD7000 C:\WINNT\System32\DBmsLPCn.dll
0x77920000 - 0x77943000 C:\WINNT\system32\imagehlp.dll
0x72A00000 - 0x72A2D000 C:\WINNT\system32\DBGHELP.dll
0x690A0000 - 0x690AB000 C:\WINNT\System32\PSAPI.DLL
Local Time = Thu Aug 22 11:40:22 2002
Elapsed Time = 28
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.4.0-b92 mixed mode)
# An error report file has been saved as hs_err_pid1804.log.
# Please refer to the file for further information.I am no guru,
but I have written BLOBS into DB2 via JDBC and I use a Prepared Statement, this works well for me.
// Below is some code I originally mimicked and It worked well for me.
// hope it it useful. I have never used SQLServer :-(
import java.io.*;
import java.sql.*;
public void insertBlob( int rowid, byte[] bindata ) {
// In this example I'm assuming there's an open, active
// Connection instance called 'con'.
// This examples uses an imaginary SQL table of the following
// form:
// CREATE TABLE blobs (
// ROWID INT NOT NULL,
// ROWDATA BLOB,
// PRIMARY KEY (rowid)
try {
ByteArrayInputStream bais = new ByteArrayInputStream(bindata);
String sql = "INSERT INTO blobs ( rowid, rowdata ) VALUES ( ?, ? )";
PreparedStatement ps = con.prepareStatement(sql);
// Set up the parameter index for convenience (JDBC column
// indices start from 1):
int paramindex = 1;
// Set the first parameter, the Row ID:
ps.setInt(paramindex++, rowid);
// Now set the actual binary column data by passing the
// ByteArrayInputStream instance and its length:
ps.setBinaryStream(paramindex++, bais, bindata.length);
// Finally, execute the command and close the statement:
ps.executeUpdate();
ps.close();
} catch ( SQLException se ) {
System.err.println("Couldn't insert binary data: "+se);
} catch ( IOException ioe ) {
System.err.println("Couldn't insert binary data: "+ioe);
} finally {
con.close();
} -
Hi All,
We have OBIEE installed on RH Linux server. On the same server we have the Netezza ODBC CLI installed.
So I set up the ODBC connection from OBI to Netezza and build a test rpd.
Everything seemed to work fine with very simple queries. Just querying one table for example.
However, once I started doing more complex reports in answers, the OBI server started to crash.
Symptoms would be I would create the answers report and try to look at the results. After a few seconds I'd get an error message like this...
Odbc driver returned an error (SQLExecDirectW). [Error Details|javascript:void(null)]
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred.
[nQSError: 12010] Communication error connecting to remote end point: address = LOCALHOST; port = 9703. (HY000)
And the SQL at the bottom of course.
Then, I'd log out and try to log back in and I'd get this error...
Odbc driver returned an error (SQLDriverConnectW). [Error Details|javascript:void(null)]
Error Codes: OPR4ONWY:U9IM8TAC
State: 08004. Code: 10092. [NQODBC] [SQL_STATE: 08004] [nQSError: 10092] The Oracle BI Server is not currently running.
Cannot connect to server machine (08004)
And I'd have to bounce the OBI services to get things working again. If I built reports off of any other area that connected to Oracle DBs (via OCI) there was no crash and no problem.
So basically, I've got an intermittent problem of crashes somehow related to using ODBC connection.
Anyone else seen this?
EWish I could give myself points. Oh well.
Our setup is Netezza DB server with Netezza 3.5.
OBI RH Linux ES4 server with Netezza ODBC Client 3.51 and Data Direct (provided by Netezza) already installed.
The reason for this problem is that OBI is not certified to use the Netezza ODBC Linux Driver 3.51.
OBI is certified only through the Netezza ODBC Linux 3.1.4 Driver.
So here's the steps I used to solve my problem. Hope this helps someone else out there.
This solution assumes you have the most recent versions of the Netezza Linux ODBC Client and Data Direct ODBC Administrator (32v51) installed already.
<ul><li>Telnet into the OBI/Netezza Client box.</li>
<li>su to the Netezzaa user.</li>
<li>In Netezza users home directory create a file .odbc.ini and .odbcinst.ini.</li>
<li>Include contents in these according to Netezza's guidance. My examples are at the bottom of this post.</li>
<li>Exit from Netezza user and su into OBI user.</li>
<li>Make sure the .profile or .bash_profile of the OBI user contains references to the Netezza Home Directory on the same server and the Netezza HOST where the Netezza DB resides.</li>
<li>Something like this should be in the profile...</li>
</ul>
bq. bq. {color:#000080}+NZ_DIR=/opt/app/netezza+ \\ + export NZ_DIR+{color} \\ {color:#000080}+NZ_HOST=stdwpprnz1+{color} \\ {color:#000080}+export NZ_HOST+{color}
<ul><li>Also make sure that in the OBI user's profile LD_LIBRARY_PATH there is a reference to *${NZ_DIR}/lib*.</li>
<li>And that the PATH contains a reference to *${NZ_DIR}/bin*.</li>
<li>Shut down all OBI processes.</li>
<li>Copy the .odbc.ini and .odbcinst.ini you created earlier from the Netezza user's home dir to the home dir of the OBI user.
<ul><li>{color:#000080}+cp $NZ_HOME/.odbc.ini $HOME/+{color}</li>
<li>{color:#000080}+cp $NZ_HOME/.odbcinst.ini $HOME/+{color}</li>
</ul>
</li>
<li>Navigate to $OracleBI_HOME/setup
<ul><li>{color:#000080}+cd $OracleBI_HOME/setup+{color}</li>
</ul>
</li>
<li>Backup the original odbc.ini and user.sh files.
<ul><li>+{color:#000080}cp odbc.ini odbc.ini.orig{color}+</li>
<li>+{color:#000080}cp user.sh user.sh.orig{color}+</li>
</ul>
</li>
<li>Open odbc.ini in an editor such as vi.
<ul><li>{color:#000080}+vi odbc.ini+{color}</li>
</ul>
</li>
<li>In the [ODBC Data Sources|http://forums.oracle.com/forums/] section add the same reference you placed in the same location in .odbc.ini file in Netezza.</li>
<li>Then below add a section with all the details just like in the .odbc.ini file in Netezza.</li>
<li>Save and close.</li>
<li>Now open user.sh in an editor such as vi.
<ul><li>{color:#000080}+vi user.sh+{color}</li>
</ul>
</li>
<li>Edit the file for content. See my example below.</li>
<li>Save and close.</li>
<li>su to the Netezza user.</li>
<li>Go into $Netezza_HOME/lib</li>
<li>Remove the libnzsqlodbc3.so symbolic link pointing to libnzodbc.so
<ul><li>{color:#000080}+rm libnzsqlodbc3.s+o{color}</li>
</ul>
</li>
<li>Rename original libnzodbc.so to libnzodbc.so.orig
<ul><li>{color:#000080}+mv libnzodbc.so libnzodbc.so.orig+{color}</li>
</ul>
</li>
<li>FTP to [ftp://ntzftp.netezza.com/Releases/3.1.4/]</li>
<li>Get the file cli.package.tar.z</li>
<li>Note: The FTP site requires a username/password provided by Netezza via a ticket through their support site</li>
<li>Unpack cli.package.tar.z to reveal cli.package.tar</li>
<li>Unpack cli.package.tar to reveal a set of files one of which is clientsw.3.1.4.tar</li>
<li>Unpack clientsw.3.1.4.tar and go into the revealed lib directory</li>
<li>Copy the libnzsqlodbc3.so found there to $Netezza_HOME/lib</li>
<li>Create a new symbolic link pointing libnzodbc.ini to the libnzsqlodbc3.so just copied in
<ul><li>{color:#000080}+ln -s libnzsqlodbc3.so libnzodbc.so+{color}</li>
</ul>
</li>
<li>su to OBI user and restart OBI processes</li>
</ul>
Any issues with using fields of any sort should now be gone.
Example of my files (some entries changed for security reasons):
Example of .odbc.ini in both Netezza user's home and Oracle user's home...
******************************** <-- These are not part of the files. These are just dividers in this post. Do not place these in the files.
; odbc.ini
[ODBC Data Sources|http://forums.oracle.com/forums/]
NGMADM = NetezzaSQL
NGMADM
Driver = /opt/app/netezza/lib/libnzodbc.so
Description = NetezzaSQL ODBC
Servername = 123.345.567.789
Port = 5480
Database = nxdadm
Username = nzread
Password = nzreadpassword
ReadOnly = false
ShowSystemTables = false
LegacySQLTables = false
LoginTimeout = 0
QueryTimeout = 0
DateFormat = 1
NumericAsChar = false
SQLBitOneZero = false
StripCRLF = false
ODBC
IANAAppCodePage=4
InstallDir=/opt/app/netezza/odbc32v51
Trace=0
TraceDll=/opt/app/netezza/odbc32v51/lib/odbctrac.so
TraceFile=odbctrace.out
UseCursorLib=0
Example of .odbcinst.ini in both Netezza user's home and Oracle user's home...
[ODBC Drivers|http://forums.oracle.com/forums/]
NetezzaSQL = Installed
NetezzaSQL
Driver = /opt/app/netezza/lib/libnzodbc.so
Setup = /opt/app/netezza/lib/libnzodbc.so
APILevel = 1
ConnectFunctions = YYN
Description = Netezza ODBC driver
DriverODBCVer = 03.51
DebugLogging = false
LogPath = /tmp
UnicodeTranslationOption = utf8
CharacterTranslationOption = all
PreFetch = 256
Socket = 16384
Example of $OracleBI_HOME/setup/odbc.ini
ODBC
Trace=0
TraceFile=odbctrace.out
TraceDll=/opt/app/oracle/OracleBI/odbc/lib/odbctrac.so
InstallDir=/opt/app/oracle/OracleBI/odbc
UseCursorLib=0
IANAAppCodePage=4
[ODBC Data Sources|http://forums.oracle.com/forums/]
AnalyticsWeb=Oracle BI Server
Cluster=Oracle BI Server
SSL_Sample=Oracle BI Server
NGMADM=NetezzaSQL
AnalyticsWeb
Driver=/opt/app/oracle/OracleBI/server/Bin/libnqsodbc.so
Description=Oracle BI Server
ServerMachine=local
Repository=
Catalog=
UID=
PWD=
Port=9703
Cluster
Driver=/opt/app/oracle/OracleBI/server/Bin/libnqsodbc.so
Description=Oracle BI Server
ServerMachine=local
Repository=
FinalTimeOutForContactingCCS=60
InitialTimeOutForContactingPrimaryCCS=5
IsClusteredDSN=Yes
Catalog=SnowFlakeSales
UID=Administrator
PWD=
Port=9703
PrimaryCCS=
PrimaryCCSPort=9706
SecondaryCCS=
SecondaryCCSPort=9706
Regional=No
[SSL_Sample|http://forums.oracle.com/forums/]
Driver=/opt/app/oracle/OracleBI/server/Bin/libnqsodbc.so
Description=Oracle BI Server
ServerMachine=localhost
Repository=
Catalog=SnowflakeSales
UID=
PWD=
Port=9703
SSL=Yes
SSLCertificateFile=/path/to/ssl/certificate.pem
SSLPrivateKeyFile=/path/to/ssl/privatekey.pem
SSLPassphraseFile=/path/to/ssl/passphrase.txt
SSLCipherList=
SSLVerifyPeer=No
SSLCACertificateDir=/path/to/ca/certificate/dir
SSLCACertificateFile=/path/to/ca/certificate/file.pem
SSLTrustedPeerDNs=
SSLCertVerificationDepth=9
NGMADM
Driver = /opt/app/netezza/lib/libnzodbc.so
Description = NetezzaSQL ODBC
Servername = 123.345.567.789
Port = 5480
Database = nxdadm
Username = nzread
Password = nzreadpassword
ReadOnly = false
ShowSystemTables = false
LegacySQLTables = false
LoginTimeout = 0
QueryTimeout = 0
DateFormat = 1
NumericAsChar = false
SQLBitOneZero = false
StripCRLF = false
Example from the important part of $OracleBI_HOME/setup/user.sh NOT THE WHOLE FILE IN THIS CASE.
# Linux: Oracle BI 32 bit mode
#set +u
# Oracle Parameters
# Make sure that Oracle DB 32 bit Client is installed
ORACLE_HOME=/opt/app/oracle/product/10.2.0_client
export ORACLE_HOME
TNS_ADMIN=$ORACLE_HOME/network/admin
export TNS_ADMIN
PATH=$ORACLE_HOME/bin:/opt/bin:$PATH
export PATH
#LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
#export LD_LIBRARY_PATH
# If you have Linux 64 bit Platform, and would like to run Oracle BI 32 bit
# then you must install Oracle DB 64 bit client, and this client comes with
# 32 bit libraries under $ORACLE_HOME/lib32. The LD_LIBRARY_PATH in this case
# shall be like this:
LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
# Linux: Netezza 32 bit mode
PATH=/opt/app/netezza/bin:$PATH
export PATH
LD_LIBRARY_PATH=/opt/app/netezza/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Edited by: eleavings on Jan 13, 2009 9:31 AM -
Hi All,
I have opened one Applet in IE. During DB operation IE(JVM) is crashed.
The following error file is created.
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x2706DAE5
Function=[Unknown.]
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at sun.jdbc.odbc.JdbcOdbc.getDataString(Native Method)
at sun.jdbc.odbc.JdbcOdbc.SQLGetDataString(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcResultSet.getDataString(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcResultSet.getString(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcConnection.buildTypeInfo(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcConnection.initialize(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcDriver.connect(Unknown Source)
- locked <0x10f6ec00> (a sun.jdbc.odbc.JdbcOdbcDriver)
at java.sql.DriverManager.getConnection(Unknown Source)
- locked <0x16a32538> (a java.lang.Class)
at java.sql.DriverManager.getConnection(Unknown Source)
- locked <0x16a32538> (a java.lang.Class)
at jp.co.nec.diosa.gui.sno.db.ConnectionFactory.getConnection(Unknown Source)
at jp.co.nec.diosa.gui.sno.db.CommandHandler.updateStatus(Unknown Source)
at jp.co.nec.diosa.gui.sno.gui.StatusUtility.changeStatusData(Unknown Source)
at jp.co.nec.diosa.gui.sno.event.SNOGUIDateChangeResult.execute(Unknown Source)
at jp.co.nec.diosa.gui.sno.application.GUIThread.run(Unknown Source)
Dynamic libraries:
0x00400000 - 0x00412000 C:\Program Files\Internet Explorer\IEXPLORE.EXE
0x77F80000 - 0x77FFC000 C:\WINNT\system32\ntdll.dll
0x78000000 - 0x78045000 C:\WINNT\system32\MSVCRT.dll
0x7C570000 - 0x7C623000 C:\WINNT\system32\KERNEL32.dll
0x77E10000 - 0x77E6F000 C:\WINNT\system32\USER32.dll
0x77F40000 - 0x77F7C000 C:\WINNT\system32\GDI32.dll
0x70BD0000 - 0x70C20000 C:\WINNT\system32\SHLWAPI.dll
0x7C2D0000 - 0x7C335000 C:\WINNT\system32\ADVAPI32.dll
0x77D30000 - 0x77DA8000 C:\WINNT\system32\RPCRT4.dll
0x70FD0000 - 0x710FC000 C:\WINNT\system32\SHDOCVW.dll
0x7CF30000 - 0x7D176000 C:\WINNT\system32\SHELL32.dll
0x71730000 - 0x717BA000 C:\WINNT\system32\COMCTL32.dll
0x7CE20000 - 0x7CF0F000 C:\WINNT\system32\ole32.dll
0x60000000 - 0x60045000 C:\WINNT\system32\MSCTF.dll
0x71110000 - 0x7120D000 C:\WINNT\system32\BROWSEUI.dll
0x71960000 - 0x7197F000 C:\WINNT\system32\browselc.dll
0x7C950000 - 0x7C9DF000 C:\WINNT\system32\CLBCATQ.DLL
0x779B0000 - 0x77A4B000 C:\WINNT\system32\OLEAUT32.dll
0x41000000 - 0x4101D000 C:\PROGRA~1\Google\GOOGLE~1\GOA66E~1.DLL
0x70200000 - 0x7027F000 C:\WINNT\system32\WININET.DLL
0x7C740000 - 0x7C7CC000 C:\WINNT\system32\CRYPT32.dll
0x77430000 - 0x77440000 C:\WINNT\system32\MSASN1.dll
0x77840000 - 0x7787E000 C:\WINNT\system32\cscui.dll
0x770C0000 - 0x770E3000 C:\WINNT\system32\CSCDLL.DLL
0x10000000 - 0x1000B000 C:\Program Files\Adobe\Acrobat 6.0\Reader\ActiveX\AcroIEHelper.dll
0x01470000 - 0x01485000 C:\PROGRA~1\egenisys\PROTEC~1\HTMLEdit.dll
0x70290000 - 0x70309000 C:\WINNT\system32\URLMON.DLL
0x77820000 - 0x77827000 C:\WINNT\system32\VERSION.dll
0x759B0000 - 0x759B6000 C:\WINNT\system32\LZ32.DLL
0x70C30000 - 0x70ECB000 C:\WINNT\System32\mshtml.dll
0x718E0000 - 0x7194A000 C:\WINNT\system32\shdoclc.dll
0x70410000 - 0x70498000 C:\WINNT\System32\mlang.dll
0x513E0000 - 0x5140D000 C:\Program Files\Common Files\Microsoft Shared\VS7Debug\pdm.dll
0x51300000 - 0x51328000 C:\Program Files\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll
0x745E0000 - 0x748A6000 C:\WINNT\system32\msi.dll
0x60280000 - 0x602AB000 C:\WINNT\system32\msimtf.dll
0x60180000 - 0x601BB000 C:\WINNT\IME\sptip.dll
0x01C00000 - 0x01C5B000 C:\Program Files\Common Files\Microsoft Shared\Ink\SKCHUI.DLL
0x75AC0000 - 0x75AE8000 C:\WINNT\system32\MSLS31.DLL
0x32520000 - 0x32532000 C:\Program Files\Microsoft Office\Office10\msohev.dll
0x77570000 - 0x775A0000 C:\WINNT\system32\WINMM.DLL
0x77560000 - 0x77568000 C:\WINNT\system32\wdmaud.drv
0x75050000 - 0x75058000 C:\WINNT\system32\wsock32.dll
0x75030000 - 0x75044000 C:\WINNT\system32\WS2_32.DLL
0x75020000 - 0x75028000 C:\WINNT\system32\WS2HELP.DLL
0x77400000 - 0x77408000 C:\WINNT\system32\msacm32.drv
0x77410000 - 0x77423000 C:\WINNT\system32\MSACM32.dll
0x75D40000 - 0x75D46000 C:\WINNT\system32\msadp32.acm
0x43000000 - 0x43005000 C:\Program Files\Google\Google Desktop Search\GoogleDesktopNetwork1.dll
0x44000000 - 0x44025000 C:\Program Files\Google\Google Desktop Search\GoogleDesktopNetwork2.dll
0x74FD0000 - 0x74FEE000 C:\WINNT\system32\msafd.dll
0x774E0000 - 0x77514000 C:\WINNT\system32\RASAPI32.DLL
0x774C0000 - 0x774D1000 C:\WINNT\system32\rasman.dll
0x77530000 - 0x77552000 C:\WINNT\system32\TAPI32.dll
0x77830000 - 0x7783E000 C:\WINNT\system32\RTUTILS.DLL
0x75AB0000 - 0x75AB5000 C:\WINNT\system32\sensapi.dll
0x62000000 - 0x62080000 C:\Program Files\Google\Google Desktop Search\GoogleDesktopResources_en.dll
0x75010000 - 0x75017000 C:\WINNT\System32\wshtcpip.dll
0x7C0F0000 - 0x7C154000 C:\WINNT\system32\USERENV.DLL
0x7CDC0000 - 0x7CE13000 C:\WINNT\system32\netapi32.dll
0x77980000 - 0x779A4000 C:\WINNT\system32\DNSAPI.dll
0x751C0000 - 0x751C6000 C:\WINNT\system32\NETRAP.dll
0x77BF0000 - 0x77C01000 C:\WINNT\system32\NTDSAPI.dll
0x77950000 - 0x7797B000 C:\WINNT\system32\WLDAP32.DLL
0x7C340000 - 0x7C34F000 C:\WINNT\system32\SECUR32.DLL
0x75150000 - 0x75160000 C:\WINNT\system32\SAMLIB.dll
0x6B700000 - 0x6B790000 C:\WINNT\System32\jscript.dll
0x6D460000 - 0x6D470000 C:\Program Files\Java\j2re1.4.2_08\bin\npjpi142_08.dll
0x695E0000 - 0x69609000 C:\WINNT\system32\OLEPRO32.DLL
0x6D330000 - 0x6D348000 C:\Program Files\Java\j2re1.4.2_08\bin\jpiexp32.dll
0x782C0000 - 0x782CC000 C:\WINNT\System32\rnr20.dll
0x77340000 - 0x77353000 C:\WINNT\system32\iphlpapi.dll
0x77520000 - 0x77525000 C:\WINNT\system32\ICMP.DLL
0x77320000 - 0x77337000 C:\WINNT\system32\MPRAPI.DLL
0x773B0000 - 0x773DF000 C:\WINNT\system32\ACTIVEDS.DLL
0x77380000 - 0x773A3000 C:\WINNT\system32\ADSLDPC.DLL
0x77880000 - 0x7790E000 C:\WINNT\system32\SETUPAPI.DLL
0x77360000 - 0x77379000 C:\WINNT\system32\DHCPCSVC.DLL
0x777E0000 - 0x777E8000 C:\WINNT\System32\winrnr.dll
0x6D3A0000 - 0x6D3B8000 C:\Program Files\Java\j2re1.4.2_08\bin\jpishare.dll
0x08000000 - 0x08138000 C:\PROGRA~1\Java\J2RE14~1.2_0\bin\client\jvm.dll
0x02D40000 - 0x02D47000 C:\PROGRA~1\Java\J2RE14~1.2_0\bin\hpi.dll
0x02D60000 - 0x02D6E000 C:\PROGRA~1\Java\J2RE14~1.2_0\bin\verify.dll
0x02D70000 - 0x02D89000 C:\PROGRA~1\Java\J2RE14~1.2_0\bin\java.dll
0x02D90000 - 0x02D9E000 C:\PROGRA~1\Java\J2RE14~1.2_0\bin\zip.dll
0x1A490000 - 0x1A5A2000 C:\Program Files\Java\j2re1.4.2_08\bin\awt.dll
0x77800000 - 0x7781E000 C:\WINNT\system32\WINSPOOL.DRV
0x76620000 - 0x76630000 C:\WINNT\system32\MPR.DLL
0x75E60000 - 0x75E7A000 C:\WINNT\system32\IMM32.dll
0x1A5B0000 - 0x1A601000 C:\Program Files\Java\j2re1.4.2_08\bin\fontmanager.dll
0x72800000 - 0x72846000 C:\WINNT\system32\ddraw.dll
0x728A0000 - 0x728A6000 C:\WINNT\system32\DCIMAN32.dll
0x72CF0000 - 0x72D84000 C:\WINNT\system32\D3DIM700.DLL
0x6D310000 - 0x6D324000 C:\Program Files\Java\j2re1.4.2_08\bin\jpicom32.dll
0x6D480000 - 0x6D49D000 C:\Program Files\Java\j2re1.4.2_08\bin\RegUtils.dll
0x22850000 - 0x2285F000 C:\Program Files\Java\j2re1.4.2_08\bin\net.dll
0x777F0000 - 0x777F5000 C:\WINNT\system32\rasadhlp.dll
0x238F0000 - 0x23912000 C:\Program Files\Java\j2re1.4.2_08\bin\dcpr.dll
0x25200000 - 0x2520C000 C:\Program Files\Java\j2re1.4.2_08\bin\JdbcOdbc.dll
0x25210000 - 0x25242000 C:\WINNT\system32\ODBC32.dll
0x76B30000 - 0x76B6E000 C:\WINNT\system32\comdlg32.dll
0x25350000 - 0x25366000 C:\WINNT\system32\odbcint.dll
0x25430000 - 0x25449000 C:\WINNT\system32\odbccp32.dll
0x782D0000 - 0x782F2000 C:\WINNT\system32\msv1_0.dll
0x77920000 - 0x77943000 C:\WINNT\system32\imagehlp.dll
0x72A00000 - 0x72A2D000 C:\WINNT\system32\DBGHELP.dll
0x690A0000 - 0x690AB000 C:\WINNT\system32\PSAPI.DLL
Heap at VM Abort:
Heap
def new generation total 2176K, used 1495K [0x10010000, 0x10260000, 0x10770000)
eden space 1984K, 65% used [0x10010000, 0x10155dd0, 0x10200000)
from space 192K, 100% used [0x10200000, 0x10230000, 0x10230000)
to space 192K, 0% used [0x10230000, 0x10230000, 0x10260000)
tenured generation total 24820K, used 18110K [0x10770000, 0x11fad000, 0x16010000)
the space 24820K, 72% used [0x10770000, 0x1191f998, 0x1191fa00, 0x11fad000)
compacting perm gen total 14848K, used 14671K [0x16010000, 0x16e90000, 0x1a010000)
the space 14848K, 98% used [0x16010000, 0x16e63c20, 0x16e63e00, 0x16e90000)
Local Time = Mon Jun 26 18:33:49 2006
Elapsed Time = 265
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.4.2_08-b03 mixed mode)
Can any one help out this?
Thanks in Advance.
Regds,
raghuThis is your code?
The error tells you that ODBC crashed (not java.)
So your ODBC driver is the reason.
You can find a work around by determining exactly what call (SQL) causes the crash and then find a way around it. -
Oracle 10g ODBC driver with Windows 7 32 bit connecting to Excel
Hi Everyone,
I'm having an issue connecting to our oracle 10g database (64 bit system) from a 32 bit windows 7 installation running excel 2010/2007 using odbc drivers. Our excel spreadsheets worked without issue in windows xp.
In windows 7 I have been able to install the odbc driver via the following method:
1. Download the oracle 'basic' client and oracle 'odbc' client from www.oracle.com and extract the contents:
instantclient-basic-win32-10.2.0.3-20061115
instantclient-odbc-win32-10.2.0.3-20061115
2. Create a folder 'oracle' and place the instantclient_10_2 folder inside.
3. Ensure all the basic and odbc files reside in this folder.
4. Create a 'network' folder within instantclient_10_2
5. Create an 'admin' folder within 'network'
6. Create sqlnet.ora and tnsnames.ora files within the 'admin' folder:
7. Run 'obdc_install' within the instantclient_10_2 folder
8. Download and run the oracle odbc driver exe file from www.oracle.com (ORA10203.exe)
9. Go to Control Panel -> Administrative Tools -> Data Sources and create a new System DN
This allows excel spreadsheets connecting ONLY to oracle to function.
Unfortunately some of our spreadsheets connect to both a MySQL database as well as oracle. Spreadsheets connecting only to MySQL also function correctly, however, as soon as the vb associated with a spreadsheet includes a mysql call followed by an oracle call the spreadsheets fail. In Excel 2007 excel crashes completely everytime. In Excel 2010 the mysql data is generated, then when the script hits to oracle odbc connection there is a long pause, the oracle ODBC driver connect pops up requesting a username/password (this didn't happen in xp), then the data source selection pops up, then the username/password connect screen pops up again, and finally it fails with a runtime error '1004' General ODBC error.
If you look at the VB script it's failing at the Refresh BackgroundQuery statement in the ODBC connection block:
With Worksheets("Oracle1").QueryTables.Add(Connection:= _
"ODBC;DSN=Oracle_ODBC;UID=user;PWD=password;SERVER=ORACLE_LINUX;", _
Destination:=Worksheets("Oracle1").Range("A1"))
.CommandText = strSql
.Name = "Oracle1_data"
.FieldNames = True
.RowNumbers = False
.FillAdjacentFormulas = False
.PreserveFormatting = True
.RefreshOnFileOpen = False
.BackgroundQuery = True
.RefreshStyle = xlOverwriteCells
.SavePassword = True
.SaveData = True
.AdjustColumnWidth = True
.RefreshPeriod = 0
.PreserveColumnInfo = True
.Refresh BackgroundQuery:=False
End With
Does anyone know how to get around this? It's very important!!
Also if you try to edit the oracle ODBC connections in Control Panels -> Administrative Tools -> Data Sources, ODBC crashes 95% of the time.
Advice greatly appreciated!!Well, here's what I'd check anyway..
1) get Process Explorer from http://sysinternals.com
2) make a mysql connection, get a list of dll's loaded (include the location and version columns in the lower pane output)
3) close that, then make an ora odbc connection, get a list of dlls.
4) close that, then make a mysql connection followed by an ora odbc connection, get a list of dlls
5) compare the lists of loaded dlls. In particular, the difference between #3 and #4, is there a dll dependency that gets loaded by oracle's odbc that comes from a different location when you've opened a mysql connection first?
May or may not help, but might turn up a difference to help point you in a direction.
Greg -
ODBC Access Violations with Ora 8.1.6 install
Hi - we have updated to Oracle 8.1.6 (ODBC 6.1.6.2) and now find regular instability using ODBC. Given the following stack traces can anyone see what may causing this..The exceptions we trace seem to originate from SQLExecute...
Exampe 1.
NTDLL! 77f9f9df()
NTDLL! 77fa6ee1()
NTDLL! 77fb3385()
NTDLL! 77fa6b46()
NTDLL! 77fcac04()
MSVCRT! 78001e97()
ORANL8! 60a083d1()
ORANL8! 60a082cd()
ORANL8! 60a16232()
ORAGENERIC8! 600bdbc7()
ORAGENERIC8! 6009499a()
ORACLIENT8! 60419d2b()
ORACLIENT8! 60419971()
ORACLIENT8! 60445a4e()
ORACLIENT8! 6044540d()
ORACLIENT8! 604012ac()
OCI! 1000d4c7()
SQORA32! 04c1467b()
007a1370()
Example 2.
NTDLL! 77f9f9df()
NTDLL! 77fcc779()
NTDLL! 77f87aa3()
NTDLL! 77fb3c33()
NTDLL! 77fa7131()
NTDLL! 77fca4cb()
MSVCRT! 7800113d()
ORACORE8! 6064e5b1()
ORATRACE8! 6271513b()
Example 3.
NTDLL! 77f9f9df()
NTDLL! 77fa6ee1()
NTDLL! 77fb3385()
NTDLL! 77fa6b46()
NTDLL! 77fcac04()
MSVCRT! 78001089()
MSVCRT! 78001026()
ORAGENERIC8! 600dd4d1()
ORACLIENT8! 604455fc()
ORACLIENT8! 6044540d()
ORACLIENT8! 604012ac()
OCI! 1000d4c7()
SQORA32! 04c1467b()
In addition to these problems we find that a DB connection is taking ~15 seconds with ODBC or SQLPlus on a local machine. This seems to indicate something is wrong - but what? Could the same problem be related (cause?) the ODBC crashes?
To install 8.1.6 we had to manually de-install 8.1.5 since the Oracle installer frooze on every attempt to deinstall 8.1.5. We have reinstalled 8.1.6 twice (last attempt following Oracles manual deinstall procedure). When we saw instability with 8.1.6 we installed 8.1.6.1.1 to no avail.
At this point we have spent days trying to recover from the 8.1.6 install. Is it likely to help if we simply reformat the disk and reinstall ORacle again? This will be very time consuming since we will loose everything on the machine but is beginning to seem like the only way to recover any stability.
Basic question is :- Is our Oracle environment install flawed or is the instability just due to bugs in Oracle 8.1.6. Our test suite worked fine with 8.1.5.
Thanks David M
nullWell we have more info on this. It appears that executing stored procs with output params may be a problem..
The previous post was run on Win 2000 with Ora 8.1.6 and ODBC 8.1.6.2.
We Installed 8.1.6 and ODBC 8.1.6.2 on an NT SP6 machine and got the following Dr Watson..
This machine is not exhibiting the slow connection times and it appears to be a reliable Oracle install.
The error hints occuring during the freeing of an OCI Handle..
function: RtlpWaitForCriticalSection
77f6ce28 e920010000 jmp RtlpWaitForCriticalSection+0x196 (77f6cf4d)
77f6ce2d 803d987ffa7701 ds:77fa7f98=01
cmp byte ptr [fltused+0x12a8 (77fa7f98)],0x1
77f6ce34 1bc0 sbb eax,eax
77f6ce36 25e080fa77 and eax,0x77fa80e0
77f6ce3b 837e1000 cmp dword ptr [esi+0x10],0x0 ds:02428076=????????
77f6ce3f 8945fc mov [ebp-0x4],eax ss:02c1850e=????????
77f6ce42 7506 jnz RtlpWaitForCriticalSection+0x93 (77f6ce4a)
77f6ce44 56 push esi
77f6ce45 e8b6fdffff call RtlSetCriticalSectionSpinCount+0x70 (77f6cc00)
77f6ce4a 8b06 mov eax,[esi] ds:007d9670=20202020
FAULT ->77f6ce4c ff4010 inc dword ptr [eax+0x10] ds:21e50a26=????????
77f6ce4f 8b06 mov eax,[esi] ds:007d9670=20202020
77f6ce51 ff75fc push dword ptr [ebp-0x4] ss:02c1850e=????????
77f6ce54 6a00 push 0x0
77f6ce56 ff4014 inc dword ptr [eax+0x14] ds:21e50a26=????????
77f6ce59 ff7610 push dword ptr [esi+0x10] ds:02428076=????????
77f6ce5c e86fb4ffff call NtWaitForSingleObject (77f682d0)
77f6ce61 3d02010000 cmp eax,0x102
77f6ce66 0f85b2000000 jne RtlpWaitForCriticalSection+0x167 (77f6cf1e)
77f6ce6c 57 push edi
77f6ce6d 6822cdf677 push 0x77f6cd22
77f6ce72 e881940000 call DbgPrint (77f762f8)
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
00fc9b08 77f67586 007d9670 6064cf31 007d9670 00b51300 ntdll!RtlpWaitForCriticalSection
00fc9b20 604435e2 007d0010 00b5131c 01082e20 01081020 ntdll!RtlEnterCriticalSection
00fc9d70 6040120a 00000001 00000007 00fc9d90 1000589f oraclient8!kpufhndl
00fc9d80 1000589f 00b51300 00000007 00fc9e24 04c14c88 oraclient8!OCIHandleFree
The Stored Procedure -
CREATE PROCEDURE SP_StoredProcedureAllTypes (in_int integer, in_char char, in_vchar varchar2, in_date date, in_date1 date, in_dec number, in_double number, out_int out integer, out_char out char, out_vchar out varchar2,out_date out date,out_date1 out date,out_dec out number, out_double out number ) is
begin out_int := in_int; out_char := in_char; out_vchar := in_vchar; out_date := in_date; out_date1 := in_date1; out_dec := in_dec; out_double := in_double;
end;
The ODBC API trace :-
JDataServer -s da-42 EXIT SQLPrepare with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UCHAR * 0x007DB1C0 [ 75] "{call SP_StoredProcedureAllTypes(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}"
SDWORD 75
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 4 <SQL_INTEGER>
SQLULEN 0
SWORD 0
PTR 0x007DD650
SQLLEN 2
SQLLEN * 0x00BAC360
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 4 <SQL_INTEGER>
SQLULEN 0
SWORD 0
PTR 0x007DD650
SQLLEN 2
SQLLEN * 0x00BAC360 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 2
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 1 <SQL_CHAR>
SQLULEN 4
SWORD 0
PTR 0x007DD630
SQLLEN 4
SQLLEN * 0x00BAC370
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 2
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 1 <SQL_CHAR>
SQLULEN 4
SWORD 0
PTR 0x007DD630
SQLLEN 4
SQLLEN * 0x00BAC370 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 3
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 1 <SQL_CHAR>
SQLULEN 4
SWORD 0
PTR 0x007DD610
SQLLEN 4
SQLLEN * 0x00BAC380
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 3
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 1 <SQL_CHAR>
SQLULEN 4
SWORD 0
PTR 0x007DD610
SQLLEN 4
SQLLEN * 0x00BAC380 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 4
SWORD 1 <SQL_PARAM_INPUT>
SWORD 11 <SQL_C_TIMESTAMP>
SWORD 11 <SQL_TIMESTAMP>
SQLULEN 0
SWORD 0
PTR 0x007DD5E0
SQLLEN 23
SQLLEN * 0x00BAC390
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 4
SWORD 1 <SQL_PARAM_INPUT>
SWORD 11 <SQL_C_TIMESTAMP>
SWORD 11 <SQL_TIMESTAMP>
SQLULEN 0
SWORD 0
PTR 0x007DD5E0
SQLLEN 23
SQLLEN * 0x00BAC390 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 5
SWORD 1 <SQL_PARAM_INPUT>
SWORD 9 <SQL_C_DATE>
SWORD 11 <SQL_TIMESTAMP>
SQLULEN 0
SWORD 0
PTR 0x007DD5C0
SQLLEN 10
SQLLEN * 0x00BAC3A0
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 5
SWORD 1 <SQL_PARAM_INPUT>
SWORD 9 <SQL_C_DATE>
SWORD 11 <SQL_TIMESTAMP>
SQLULEN 0
SWORD 0
PTR 0x007DD5C0
SQLLEN 10
SQLLEN * 0x00BAC3A0 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 6
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 3 <SQL_DECIMAL>
SQLULEN 6
SWORD 2
PTR 0x007DD5A0
SQLLEN 6
SQLLEN * 0x00BAC3B0
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 6
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 3 <SQL_DECIMAL>
SQLULEN 6
SWORD 2
PTR 0x007DD5A0
SQLLEN 6
SQLLEN * 0x00BAC3B0 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 7
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 8 <SQL_DOUBLE>
SQLULEN 0
SWORD 0
PTR 0x007DD580
SQLLEN 7
SQLLEN * 0x00BAC3C0
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 7
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 8 <SQL_DOUBLE>
SQLULEN 0
SWORD 0
PTR 0x007DD580
SQLLEN 7
SQLLEN * 0x00BAC3C0 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 8
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 4 <SQL_INTEGER>
SQLULEN 255
SWORD 0
PTR 0x007DB100
SQLLEN 257
SQLLEN * 0x00BAC3D0
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 8
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 4 <SQL_INTEGER>
SQLULEN 255
SWORD 0
PTR 0x007DB100
SQLLEN 257
SQLLEN * 0x00BAC3D0 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 9
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 1 <SQL_CHAR>
SQLULEN 255
SWORD 0
PTR 0x007DA940
SQLLEN 257
SQLLEN * 0x00BAC3E0
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 9
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 1 <SQL_CHAR>
SQLULEN 255
SWORD 0
PTR 0x007DA940
SQLLEN 257
SQLLEN * 0x00BAC3E0 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 10
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 12 <SQL_VARCHAR>
SQLULEN 255
SWORD 0
PTR 0x007DA820
SQLLEN 257
SQLLEN * 0x00BAC3F0
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 10
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 12 <SQL_VARCHAR>
SQLULEN 255
SWORD 0
PTR 0x007DA820
SQLLEN 257
SQLLEN * 0x00BAC3F0 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 11
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 11 <SQL_C_TIMESTAMP>
SWORD 11 <SQL_TIMESTAMP>
SQLULEN 255
SWORD 0
PTR 0x007DE810
SQLLEN 257
SQLLEN * 0x00BAC400
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 11
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 11 <SQL_C_TIMESTAMP>
SWORD 11 <SQL_TIMESTAMP>
SQLULEN 255
SWORD 0
PTR 0x007DE810
SQLLEN 257
SQLLEN * 0x00BAC400 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 12
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 9 <SQL_C_DATE>
SWORD 11 <SQL_TIMESTAMP>
SQLULEN 255
SWORD 0
PTR 0x007DE6F0
SQLLEN 257
SQLLEN * 0x00BAC410
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 12
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 9 <SQL_C_DATE>
SWORD 11 <SQL_TIMESTAMP>
SQLULEN 255
SWORD 0
PTR 0x007DE6F0
SQLLEN 257
SQLLEN * 0x00BAC410 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 13
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 3 <SQL_DECIMAL>
SQLULEN 1
SWORD 0
PTR 0x007DE5D0
SQLLEN 257
SQLLEN * 0x00BAC420
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 13
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 3 <SQL_DECIMAL>
SQLULEN 1
SWORD 0
PTR 0x007DE5D0
SQLLEN 257
SQLLEN * 0x00BAC420 (0)
JDataServer -s da-42 ENTER SQLBindParameter
HSTMT 008E2400
UWORD 14
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 8 <SQL_DOUBLE>
SQLULEN 255
SWORD 0
PTR 0x007DE4B0
SQLLEN 257
SQLLEN * 0x00BAC430
JDataServer -s da-42 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 008E2400
UWORD 14
SWORD 4 <SQL_PARAM_OUTPUT>
SWORD 1 <SQL_C_CHAR>
SWORD 8 <SQL_DOUBLE>
SQLULEN 255
SWORD 0
PTR 0x007DE4B0
SQLLEN 257
SQLLEN * 0x00BAC430 (0)
JDataServer -s da-42 ENTER SQLExecute
HSTMT 008E2400
**** Crashes here ********
null -
Odbcad32.exe errors when creating DSN using 9i client and 9.02.00.65
Hi,
I am about at the end of my rope. I have a brand new Windows xp sp2 machine. I have tried installing, uninstalling deleteing all registry keys, deleting directories, installing the full 92010NT_CLT then installing just the run time, then installing different ODBC drivers - from 9.018 - through 9.2.065 - I have been through the message that I needed a newerr version of the OUI etc etc, I finally found a thread that led me to to ODAC92070 which then I installed - geez!
ALL these configurations resulted in ODBC crashing when creating a DSN! weak! In just about every situation that I had the patience to test TOAD it worked fine - however from the command line SQLPLUS would crash too when connecting - even the MS Driver works sort of - in most situations. What in the world do I need to do to get the ODBC Administrator to not crash when creating an Oracle DSN.
Thanks
JerryHi,
I am about at the end of my rope. I have a brand new Windows xp sp2 machine. I have tried installing, uninstalling deleteing all registry keys, deleting directories, installing the full 92010NT_CLT then installing just the run time, then installing different ODBC drivers - from 9.018 - through 9.2.065 - I have been through the message that I needed a newerr version of the OUI etc etc, I finally found a thread that led me to to ODAC92070 which then I installed - geez!
ALL these configurations resulted in ODBC crashing when creating a DSN! weak! In just about every situation that I had the patience to test TOAD it worked fine - however from the command line SQLPLUS would crash too when connecting - even the MS Driver works sort of - in most situations. What in the world do I need to do to get the ODBC Administrator to not crash when creating an Oracle DSN.
Thanks
Jerry -
Data source creation with XEClient driver crashes ODBC Data Source Admin.
OS: Windows XP Professional SP2
How to reproduce:
1. Install Oracle XEClient 10g from: http://www.oracle.com/technology/software/products/database/xe/htdocs/102xewinsoft.html
2. (optional) You may need to install MSVCRT71.DLL and MFC71.DLL (see Re: odbc error in XE and 9i
3. Open Control Panel
4. Double-click on the Administrative Tools icon
5. Open Data Sources (ODBC) applet.
6. Click Add button
7. Select Oracle in XEClient
8. Name the Data Source.
9. Press OK
10. Double-click on the Data Source. The ODBC Data Source Administrator crashes.OS: Windows XP Professional SP2
How to reproduce:
1. Install Oracle XEClient 10g from: http://www.oracle.com/technology/software/products/database/xe/htdocs/102xewinsoft.html
2. (optional) You may need to install MSVCRT71.DLL and MFC71.DLL (see Re: odbc error in XE and 9i
3. Open Control Panel
4. Double-click on the Administrative Tools icon
5. Open Data Sources (ODBC) applet.
6. Click Add button
7. Select Oracle in XEClient
8. Name the Data Source.
9. Press OK
10. Double-click on the Data Source. The ODBC Data Source Administrator crashes. -
ODBC function SQLDriverConnect() crashes with SQL Server 2008 R2
When calling the SQLDriverConnect() function from a 64-bit process and selecting a system DSN with a SQL Server Native Client 10.0 ODBC driver with SQL Server 2008 R2 SP3, then this call crashes here:
sqlncli10.dll!SNIMemRegion::Pop() + 0x77 bytes
sqlncli10.dll!SNIPacketAllocateEx2() + 0xa8 bytes
sqlncli10.dll!Np::ReadSync() + 0x7e bytes
sqlncli10.dll!Ssl::HandshakeReadToken() - 0x1b bytes
user32.dll!InternalDialogBox() + 0x132 bytes
user32.dll!DialogBoxIndirectParamAorW() + 0x56 bytes
user32.dll!DialogBoxParamW() + 0x85 bytes
sqlncli10.dll!SQLDriverConnectW() + 0x34f23 bytes
odbc32.dll!SQLInternalDriverConnectW() + 0x17c bytes
odbc32.dll!SQLDriverConnectW() + 0xa15b bytes
Am I calling SQLDriverConnect() correctly (see below)? Or is this a bug in the 64-bit version of the ODBC driver?
In the 32-bit version, everything works fine.
Here is a test program:
int _tmain(int argc, _TCHAR* argv[])
SQLHENV hEnv = NULL;
SQLHDBC hDbc = NULL;
SQLRETURN ret = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &hEnv);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
ret = SQLSetEnvAttr(hEnv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER) SQL_OV_ODBC3, 0);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO)
fprintf(stderr, "SQLSetEnvAttr failed\r\n");
return EXIT_FAILURE;
ret = SQLAllocHandle(SQL_HANDLE_DBC, hEnv, &hDbc);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
SQLTCHAR szConnection[2048];
SQLSMALLINT cbChars;
ret = SQLDriverConnect(hDbc, ::GetDesktopWindow(), (SQLTCHAR*) _T(""), SQL_NTS,
szConnection, _countof(szConnection)-1, &cbChars, SQL_DRIVER_PROMPT);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO && ret != SQL_NO_DATA)
fprintf(stderr, "SQLDriverConnect failed\r\n");
return EXIT_FAILURE;
else
fprintf(stdout, "Success\r\n");
return 0;
The stdafx.h contains the following includes:
#include "targetver.h"
#include <stdio.h>
#include <tchar.h>
#include <Windows.h>
#include <sql.h>
#include <sqlext.h>
#include <assert.h>
Steps to reproduce the crash: compile program with Visual Studio 2010 as 64-bit console application; run it and select a 64-bit SQL Server DSN.
If the crash does not occur, try using the "AllocationPreference" registry entry set to 0x100000 (see https://msdn.microsoft.com/en-us/library/windows/hardware/Dn613975%28v=vs.85%29.aspx for details); don't forget to reboot Windows. This registry
helps to find 64-bit portability issues.Hi T.holt,
Personally, I don’t believe SQL 2008 R2 with ADMT 3.2 is supported. From the guidelines of install the Active Directory Migration Tool (ADMT), ADMT v3.2 requires a preconfigured instance of SQL Server for its underlying data store. We
should use SQL Server Express and install ADMT v3.2 on a member server. ADMT installation enforces the following service pack requirements:
• SQL Server 2005 Express must be installed with Service Pack 3 (SP3) or later.
• SQL Server 2008 Express must be installed with Service Pack 1 (SP1) or later.
If you use full versions of SQL Server 2005 or SQL Server 2008. In this case, you need to install and run the ADMT console on a remote computer, and you can run multiple ADMT consoles on different remote computers. If
you use a full version of SQL Server, ADMT installation does not enforce any service pack requirements.
For more information about installing ADMT in the target domain, you can review the following article.http://technet.microsoft.com/en-us/library/cc974370(v=ws.10).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
Oracle 10g Express Edition Beta 3 ODBC Driver Always Crashes
I find that if you set up an ODBC Data Source for Oracle 10g Express Edition on Windows XP SP2 using the "Oracle in XE" driver, anything that tries to access it will crash, even the Windows ODBC Data Source Administratior if you click the "Test Connection" button.
Having clicked the button, you get a window coming up entitled "Oracle ODBC Driver" with a yellow exclamation mark in it, with no other text in the window except for an OK button.
If you press OK, then it crashes and goes through the "Please tell Microsoft about this problem" process....Hi,
Thanks for your comment, but I can't get onto the XE forum.
I found http://www.oracle.com/technology/products/database/xe/forum.html which says:
Forum registration is possible only by downloading and installing Oracle Database XE. After installation, click on the "Registration" link from the Database homepage.
However I find that the "Database Homepage" does not exist.
Choosing the Oracle XE "Go To Database Home Page" takes my browser to http://127.0.0.1:8080/apex which is not available even though my oracle server is running and sqlplus can talk to it.
There's definitely nothing serving on tcp port 8080, as follows:
[dcampbel@clevo]~> telnet localhost 8080
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
Regards,
-- Dave -
Adding Oracle driver crashes MS ODBC adminstrator
Howdy,
I'm trying to set up the new Oracle 10g ODBC driver and it seems to be crashing the MS ODBC Data Source Administrator. After downloading and exploding the files on my drive, I used the Oracle Universal Installer to set it up. As the next step, I tried to add it using the ODBC Administrator, but every time I try, the Administrator program crashes. I'm trying to install on the same server that's running Oracle in order to establish a connection to an application running on the same server. Has anyone else experienced this problem? Alternatively, has anyone tried using the MS ODBC for Oracle driver (version 2.575.1022.00, dated 03/25/03). I had been advised against using this one with Oracle 10g.
My environment is as follows:
OS: MS Windows Server 2003, Enterprise Edition
DB: Oracle 10g, version 10.1.0.2.0
ODBC Driver: Oracle in ODBC, version 10.01.00.31
MS ODBC Administrator: version 3.525.1022.0
Any help would be greatly appreciated!
Thanks,
SteveI had this problem with the Oracle 10g driver as well. The problem was that when I tried to upgrade the odbc driver, I had to specify another Oracle home or the installer would crash. When I specified the other home directory, the install would work but caused this error. The solution was to uninstall the original odbc driver before installing the new one. I'm not sure why this changed all of a sudden, but the universal installer used to do this for you.
Jon -
Crystal Reports XI via ODBC to Lotus Domino Database - crashes client
As soon as I attempt to connect a CR XI report via ODBC to a particular Lotus Domino database my Crystal client crashes with the below error message in the event viewer. I regularly connect to other Lotus Notes databases but this one crashes my client everytime. Anyone have any ideas?
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 7/16/2008
Time: 11:45:27 AM
User: N/A
Computer: 2WC3PC1
Description:
Faulting application crw32.exe, version 11.0.0.2495, faulting module crdb_p2snote.dll, version 11.0.0.1282, fault address 0x00020f1a.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 63 72 77 ure crw
0018: 33 32 2e 65 78 65 20 31 32.exe 1
0020: 31 2e 30 2e 30 2e 32 34 1.0.0.24
0028: 39 35 20 69 6e 20 63 72 95 in cr
0030: 64 62 5f 70 32 73 6e 6f db_p2sno
0038: 74 65 2e 64 6c 6c 20 31 te.dll 1
0040: 31 2e 30 2e 30 2e 31 32 1.0.0.12
0048: 38 32 20 61 74 20 6f 66 82 at of
0050: 66 73 65 74 20 30 30 30 fset 000
0058: 32 30 66 31 61 0d 0a 20f1a..Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with you directly:
http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551 -
Crystal Crashes when Creating a Connection to MySQL 5.0 through ODBC
Post Author: [email protected]
CA Forum: Data Connectivity and SQL
I am using a MS Server to run BO Server. I open Crystal Reports, create a new connection to my MySQL Database through ODBC (that is set up as a System DSN). After i put in the log in credentials the dang thing crashes... Anyone?Now the problem has gone from bad to worse.
I previously had a connection to my database but just couldn't see the tables.
Now after I added another user I can't even make a connection. Instead I get an error message that says "An unidentified error has occured"
My server and database are actually running. I can loginto my database through the MySQL workbench. It says it's running. The apache server also says it's running and if I key in localhost in my internet explorer it says "It works!"
I have now deleted the new user in MySQL that I added and now I can't even connect to the database in Dreamweaver.
Any suggestions?
Thank you,
Blain
Maybe you are looking for
-
I have a calendar with SPD workflow to display multiple lines for Title, Attendees, Location. 1. Created a custom columne "Breaklines" and set to "Multiple lines of text" 2. Set Monthly View to display the "Breaklines" 3. in SPD I created a workflow
-
IPod recognized, but hangs during update
So my iPod will show up in Finder and in iTunes, and automatic updating will begin. However, at random times during the update, sometimes 4 songs in, sometimes 65, the whole process will just hang. iTunes status screen gets stuck on flashing between
-
Previously, when I got a message notification on my iPhone home screen, I could see the first part of the text. Now it just says "iMessage". How can I change this?
-
Small Guide for WebCam ..... How to switch on: Fn - ESC Press again Fn-ESC off Where i can find the WebCam ? with this device ... you can shot pics:via Test Camera... which can saved... thats all.. In Messengers you can set some more parameters and u
-
Accessing super class private variables from derived class
posted November 01, 2005 08:20 PM Profile for kenji mapes Email kenji mapes Send New Private Message Edit/Delete Post Reply With Quote Assume I have a default and a param constructor in both a subclass and a super class. The members are private. So a