SQL Server 2005 64-bit & SQL CLR Stored Procedures using DI API. COM Error.

Hi,
We've created a set of SQL CLR Stored Procs in C# .NET which use the DI API to import data into SAP (DEV was carried out on 32-bit environment).
The DLLs and Interop.SAPbobsCOM have been successfully deployed as assemblies on SQL Server with their permission set to UNSAFE on the following environment:
Microsoft Windows Server 2003 R2 Standard Edition 64-bit, Service Pack 2
Microsoft SQL Server 2005 - 9.00.3073.00 (X64)
SAP Business One 2007 A (8.00.180) SP:00 PL:45
When executing the SQL CLR Stored Procs from SQL Server Management Studio, the following error is returned:
"Retrieving the COM class factory for component with CLSID {632F4591-AA62-4219-8FB6-22BCF5F62007} failed due to the following error: 80040154."
From our understanding, this occurs because SQL Server loads the assemblies into it's 64-bit process space, whereas the SAPbobsCOM is 32-bit. Are we assuming correctly?
What can be done to solve this problem?

Hi Jeremy,
I'd agree with your assumption that it's to do with your DLL running in a 64 bit process. When you build your project, try setting the build properties to use a X86 instruction set (ie 32 bit).
More details here:
Re: Addon Develeped on 32bit Install on 64bit
I've never tried for a CLR stored procedure but this is how you get around the issue when running a DI API addon on a 64 bit machine so hopefully it will work if the dll is executed by SQL Server. Let us know how you get on.
Kind Regards,
Owen

Similar Messages

SQL Server 2005 64 bit and Oracle 9

Hi,
I have a situation which involves SQL Server 2005 64 bit and Oracle 9 32 bit,
I have a requirement that involves creating Stored Procedures from Oracle 9 which will call tables from SQL Server 2005 64 bit, with operations involving 'Select' 'Insert' 'Update' and 'Delete'.
it works fins, except when attempting to search for an SQL Server 'varchar' value, wher no mapping is done
though the Oracle sees the field as 'varchar2'
can anyone please advice on this
thanks
Basel

I think you're somehow not getting a resuklt because you're query doesn't return any data.
Why the fiealdA=pat=parameterA construct? Wouldn't it just work if you changed it to fieldA=parameterA?
Also, can you not just define parameterA as a varchar to make them match?
What if you do "select * from (<your query without where>) a where a.fieldA = :parameterA"
While not efficient, it would make the filtering occur in Oracle and maybe that will let you see the problem in native Oracle land and then reuse the solution in your orginal query. If that doesn't work, drop the where clause and inspect the data closly and hardcode a simple where without using PL*SQL or bind variables.

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

I can't link to an I series (IBM AS400) server from my sql server 2014 server (64 bit) -- but yes can link on sql server 2005 (32 bit)

I have an I series (IBM AS400) server linked "OK" to a sql 2005 sql server (32 big). I copied the link script (but changed credentials) from the sql server 2005 link and attempted to run it in the sql server 2014 server (on win 7 64
bit). There are no complaints from SSMS when I run the script, but when I try to query a table I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 11
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Here is the script (from the sql server 2005 (32 bit)) I ran on the sql server 2014 SSMS -- is there anything I need to change? How can I get this I series server to link to my sql server 2014 server?
USE [master]
GO
/****** Object: LinkedServer [CWMPDTA] Script Date: 9/25/2014 10:39:12 AM ******/
EXEC master.dbo.sp_addlinkedserver @server = N'CWMPDTA', @srvproduct=N'cwmpdta', @provider=N'MSDASQL', @datasrc=N'iseries2', @provstr=N'Provider=IBMDA400.DataSource.1;Password=myPwrd;Persist Security Info=True;User ID=myID;Data Source=10.0.0.51;Initial Catalog=T9S', @catalog=N'T9S'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'CWMPDTA',@useself=N'False',@locallogin=NULL,@rmtuser=N'myID',@rmtpassword='myPwrd'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'use remote collation', @optvalue=N'true'
GO
Rich P

Thank you for this reply. I went to the link and selected the option for DB2s and ran the install. Then I started up SSMS. I copied the same script as above, and it executed successfully. But when I try to run a query against
a table in a database on this linked sever -- I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 8
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Do I need to change the line containing -- @provider=N'MSDASQL', maybe?
this is the query I'm running:
select TOP 10 * from CWMPDTA.T9S.CWMPDTA.INSKU
The same exact query runs fine on the sql server 2005 linked server. Is there something I need to configure?
Rich P

SQL Server 2005 (64 bit) returns truncated text from Oracle 10g (64 bit)

Hi all,
I'm no expert in Oracle so I desperately need your advice.
I'm using SQL Server 2005 (64 bit) and trying to pull data from a Oracle 10g (64 bit) server. I am able to connect to the Oracle server with no problems.
The problem came when I was trying to pull a text column (I think it's BLOB in Oracle) from the Oracle server. The results came back BUT truncated to only 100 characters. (This is a column containing event logs so the text is really really long...)
As you may already know, Microsoft is not providing the driver for this case (which is insanely ridiculous!!!). There is no standard “Microsoft OLE DB Provider for Oracle” which we would normally use to establish a linked server connection to Oracle. Instead, we had to install the provider given by Oracle (Oracle Provider for OLE DB).
I have tried to Google for solutions but didn't find much. Please help! :(
Thanks in advance,
Eleni

If this is a one time activity, you need to find a migration utility which will do the job for you. SQL Developer is available had your case been the other way round (migrate from SQL Server to Oracle).
Check out tools from SwisSQL
http://www.swissql.com/products/oracle-to-sqlserver/oracle-to-sql-server.html
Microsoft's own SSMA (I think this is what you are using already)
http://www.microsoft.com/sqlserver/2005/en/us/migration-oracle.aspx
Apart from this, if there are any issues with the tools themselves, you need to get in touch with the respective vendors.

SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.) Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
specifically listed as a SQL DB user tries to use the front end they get an error of:
Microsoft SQL Server Login
Connection failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
Thanks a billion in advance ----

Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
all other roles, as well as allowing select only, and still have no access for the guest account.
The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
thru MS Access ACCDB, using a (by default) read only OCDB connection.
This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
since the result set would involve hundreds of thousands if not millions of records.
So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
as well as running our network on Microsoft's network software.

Calling an Oracle stored procedure using Toplink API - Please help

Hi,
We are evaluating Toplink as a possible data access layer in large service-oriented application. The ability to call db stored procedures from within business object layer is crucial for our architechture.
I am trying to follow toplink application developer's guide examples on how to call stored procedures using toplink.
I have the folling java code:
call.setProcedureName("PR_ROMAN_TEST");
call.addNamedArgument("IN_PARAM");
call.addNamedOutputArgument("OUT_PARAM");
ValueReadQuery query = new ValueReadQuery();
query.setCall(call);
query.addArgument("IN_PARAM");
Vector params = new Vector();
params.addElement(new Integer(5));
Number result = (Number) session.executeQuery(query, params);
This generates the following SQL statement:
BEGIN PR_ROMAN_TEST(IN_PARAM=>5, OUT_PARAM=>?); END;
An attempt to execute it causes a
java.sql.SQLException: Invalid column index.
As I understand it, this exception is thrown because of the "?" in place of the out-parameter value holder.
The SQL statement that I would want toplink to generate and execute should look like:
DECLARE result number; BEGIN PR_ROMAN_TEST(IN_PARAM=>5, OUT_PARAM=>result); END;
, but how do I achieve it and how do I capture the return value, all using toplink api?
Please help
Thank you in advance,
Roman

I read the conversation above. I am running into a similar kind of problem. I get the following error.
<an exponent (**)> <> or != or ~= >= <= <> and or like between || The symbol "." was subs Error Code: 6550Local Exception Stack: Exception [TOPLINK-4002] (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)): oracle.toplink.exceptions.DatabaseException Exception Description: java.sql.SQLException: ORA-06550: line 1, column 38: PLS-00103: Encountered the symbol "NAME" when expecting one of the following:. ( ) , * @ % &' | = - + < / > at in is mod not range rem =>.. <an exponent (**)> <> or != or ~= >= <= <> and or like as between from using || The symbol "." was substituted for "NAME" to continue.ORA-06550: line 1, column 55: PLS-00103: Encountered the symbol "ID" when expecting one of the following:. ( ) , * @ % &' | = - + < / > at in is mod not range rem =>.. <an exponent (**)> <> or != or ~= >= <= <> and or like between || The symbol "." was subs Internal Exception: java.sql.SQLException: ORA-06550: line 1, column 38:PLS-00103: Encountered the symbol "NAME" when expecting one of the following . ( ) , * @ % &' | = - + < / > at in is mod not range rem =>.. <an exponent (**)> <> or != or ~= >= <= <> and or like as between from using || The symbol "." was substituted for "NAME" to continue.ORA-06550: line 1, column 55:PLS-00103: Encountered the symbol "ID" when expecting one of the following: . ( ) , * @ % &' | = - + < / > at in is mod not range rem =>.. <an exponent (**)> <> or != or ~= >= <= <> and or like between || The symbol "." was subs Error Code: 6550 at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:227)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:733)
at oracle.toplink.internal.databaseaccess.DatabasePlatform.executeStoredProcedureCall(DatabasePlatform.java:1605)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:649)
at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:506)at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:131)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:115)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeSelectCall(CallQueryMechanism.java:194)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeSelect(CallQueryMechanism.java:175)
at oracle.toplink.queryframework.DirectReadQuery.executeNonCursor(DirectReadQuery.java:65)
at oracle.toplink.queryframework.DataReadQuery.execute(DataReadQuery.java:73)
at oracle.toplink.queryframework.ValueReadQuery.execute(ValueReadQuery.java:59)
at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:493)
at oracle.toplink.queryframework.ReadQuery.execute(ReadQuery.java:125)
at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:1958)
at oracle.toplink.threetier.ServerSession.internalExecuteQuery(ServerSession.java:629)
at oracle.toplink.threetier.ClientSession.internalExecuteQuery(ClientSession.java:392)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1086)
at oracle.toplink.publicinterface.UnitOfWork.internalExecuteQuery(UnitOfWork.java:2246)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1086)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1055)
at com.eplinc.common.persistence.toplink.TopLinkTemplate$2.readFromSession(TopLinkTemplate.java:181)
at com.eplinc.common.persistence.toplink.SessionReadCallback.doInTopLink(SessionReadCallback.java:59)
at com.eplinc.common.persistence.toplink.TopLinkTemplate.execute(TopLinkTemplate.java:110)
at com.eplinc.common.persistence.toplink.TopLinkTemplate.executeQuery(TopLinkTemplate.java:178)
at com.eplinc.common.persistence.toplink.TopLinkTemplate.executeQuery(TopLinkTemplate.java:172)
at com.epl.outletteller.dao.toplink.TopLinkOIDGeneratorDAO.generateId(TopLinkOIDGeneratorDAO.java:45)
The call I am making is as follows :
public long generateId(String name, long outletId) throws DataAccessException {
TopLinkTemplate tlTemplate = new TopLinkTemplate();
StoredProcedureCall call = new StoredProcedureCall();
call.setProcedureName("AUTONUM.GET_NEXT_VALUE");
call.addNamedArgument("autonum name");
call.addNamedArgument("outlet id");
call.addNamedOutputArgument("OUTPUT_1");
ValueReadQuery query = new ValueReadQuery();
query.setCall(call);
query.addArgument("autonum name");
query.addArgument("outlet id");
Object[] parameters = new Object[2];
parameters[0] = name;
parameters[1] = Long.toString(outletId);
Number uniqueNumber = (Number)tlTemplate.executeQuery(query,parameters);
return uniqueNumber.longValue();
This is my Table AUTONUM_SETTING
AUTONUM_NAME AUTONUM_TYPE START_VAL END_VAL INCREMENT_VALUE
TRAN_NUM GLOBAL 1 999999 1
TRACE_NUM OUTLET 1 999999 1
Any help would be appreciated. Thanks

Oracle 10.2.0.3 64-bit to SQL Server 2005 64-bit on Windows 2003 64-bit

I have not been successful in setting up HS ODBC to allow Oracle to connect to SQL Server with the above 64 bit editions. Is it possible in 10.2.0.3 Win 64-bit or must we use another method to connect? Any advice would be much appreciated.

The bad news at the beginning:
There is no HSODBC for Windows 64bit nor a gateway.
It is planned for 11gR2 to provide gateways for Windows 64bit.
As all 10g gateways have been desupported and you start with a new project so I would suggest you start with the supported gateways release 11g. The other advantage of 11g is we here offer a database gateway for ODBC (follow up product of HSODBC but which can now reside on its own machine and there isn't anymore the restriction it must be used with a database from the same Oracle_Home.
Not sure about your environment and operating system preferences, but you can install and 11g gateway for Windows on a 32bit Windows machine. Or if you prefer a Unix OS you can install it on this machine.
So your env lokks like the Oracle db is running on machine A, the gateway on machine B and the SQL Server on machine C.
The products we offer are DG4ODBC and DG4MSQL. The gateway for ODBC is a generic one which uses a 3rd party ODBC driver to connect to the SQL Server. We do not provide you any ODBC driver. You need to get one on your own, install it and configure it. The Gateway for SQL Server is ready to use after the configuration.
Difference between both products is the capability of the gateways. The ODBC gateway is generic and thus offers only limited capabilities. For example only a few functions are supported which results in POST PROCESSING. Post processin means, if a function is not translated to a function the remote database can understand, all records from the remote database are transferred to the Oracle database and the result is then processed locally. Depending now on the amount of data this might cause performance issues.
The gateway for SQL Se4rver is designed for SQl Server connections and thus supports a lot of functions it can map to the SQL Server syntax and no post processing is done. In addition it supports distributed transactions.

SQL Server 2005 (64-bit) - 10.1/10.2 via Transparent Gateway

From what I gather, there is no 64-bit Transparent Gateway for SQL Server. Has anyone used the 32-bit gateway with a 64-bit SQL Server instance? Will this even work?
Also, what are the ramifications for the Oracle instances -- will this setup work with both 32-bit & 64-bit 10.1/10.2 instances?
Thanks!
-charles.

Can you provide some context as to whay you think this will not work? The gateway is just a client to the 64 bit SQL Server. I'm sure that 64 bit server supports access from clients that are running 32 bit operating systems.

Sql server 2005 reports with sql server 2014

Can i upload SSRS 2005 reports as it is on SSRS 2014 and use it without doing anything extra or without changing anything ??
I can use SSRS 2005 reports as it is with SSRS 2012. But for SSRS 2014 not sure.
h2007

You can upgrade the the RDL schema will be upgraded.
Report definition (.rdl) files are automatically upgraded in the following ways:
When you open a report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008 or SQL Server 2008 R2 report server in the project properties, the report
definition is saved in a schema that is compatible with the target server.
When you upgrade a Reporting Services installation to a SQL Server 2014 Reporting Services (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first
time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.
Reports are not upgraded when you upload a report definition file directly to the report server or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying
problems in the report are detected. For more information, see Reporting Services Backward Compatibility.
For more information about new features for SQL Server 2014 Reporting Services (SSRS), see
What's New (Reporting Services).
Check the below Microsoft link for more information
http://msdn.microsoft.com/en-us/library/ms143674.aspx
Mudassar

WL 6.0 using MS SQL Server 2000 - Transaction timeout when invoking stored procedure

Hi,
Facing a problem on WL6.0. We are connecting to MS SQL server 2000 using a stateless
session bean
using container managed transaction. The bean method does a few updates to the
database and also
calls a stored procedure that generates primary keys many times. This stored procedure
(SP) is running
in a transaction of its own since it has to increment a counter, update the database
and then return the
primary key.The primary key generator SP is working fine and does not lock the
database in many bean
methods.
In some methods we find that the primary key generator SP has locked the database.
We
then see a lock on the database created due to this SP in the MS SQL client. The
execution goes
into the SP and gets stuck there till the bean's transaction times out. The error
message given is
...... .. Exception Message - The transaction is no longer active
(status = Rolling Back. [Reason = weblogic.transaction.internal.TimedOutExcepti
on: Transaction timed out after 31seconds
tx = transaction=(IdHash=1746718,Name = [EJB StructMgrBeanImpl.addStructure()],X
id=10908:51e67e9d7185816a,Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=
0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '7'
for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[web
logic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[myserver]=(state
=active),properties=({weblogic.transaction.name=[EJB StructMgrBeanImpl.addStruct
ure()], weblogic.jdbc=t3://10.200.15.136:7001}))]). No further JDBC access is
al
lowed within this transaction.
What could be the potential problems in the method's code/SP that could be causing
the timeout?
Anyone faced similar problems?
Thanks in advance,
Sreeja

Hi,
Facing a problem on WL6.0. We are connecting to MS SQL server 2000 using a stateless
session bean
using container managed transaction. The bean method does a few updates to the
database and also
calls a stored procedure that generates primary keys many times. This stored procedure
(SP) is running
in a transaction of its own since it has to increment a counter, update the database
and then return the
primary key.The primary key generator SP is working fine and does not lock the
database in many bean
methods.
In some methods we find that the primary key generator SP has locked the database.
We
then see a lock on the database created due to this SP in the MS SQL client. The
execution goes
into the SP and gets stuck there till the bean's transaction times out. The error
message given is
...... .. Exception Message - The transaction is no longer active
(status = Rolling Back. [Reason = weblogic.transaction.internal.TimedOutExcepti
on: Transaction timed out after 31seconds
tx = transaction=(IdHash=1746718,Name = [EJB StructMgrBeanImpl.addStructure()],X
id=10908:51e67e9d7185816a,Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=
0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '7'
for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[web
logic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[myserver]=(state
=active),properties=({weblogic.transaction.name=[EJB StructMgrBeanImpl.addStruct
ure()], weblogic.jdbc=t3://10.200.15.136:7001}))]). No further JDBC access is
al
lowed within this transaction.
What could be the potential problems in the method's code/SP that could be causing
the timeout?
Anyone faced similar problems?
Thanks in advance,
Sreeja

Connecting to SQL Server and MYSQL from a Java stored procedure

hope someone can help with this. i'm trying to connect to different databases (My SQL, SQL Server) from a java stored procedure. when invoking from within an oracle 9i database, i get the java exception error -
"Cannot connect to MySQL server on 135.177.196.75:3306. Is there a MySQL server running on the machine/port you are trying to connect to?java.security.AccessControlException)".
this store procedure works fine when invoked from outside of oracle. any replies would be greatly appreciated. thanks!

the correct drivers have been loaded. it works when called from outside of oracle. only when invoking from within oracle do we get the error message "Cannot connect to MySQL server on 135.177.196.75:3306. Is there a MySQL server running on the machine/port you are trying to connect to?(java.security.AccessControlException)". it sounds like a permissions/security/configuration issue - oracle is not allowing access to the machine/port for the MySQL or SQL Server database. appreciate the responses so far.

MS SQL Server 2005... Problem while executing stored procedure

Hi.. all
I have got a problem with sql server 2005
When i execute any stored procedure on a remote database using
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY
options, it throws SQL Exception with following message
"A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor."
Note: Every thing works fine, if I execute the same sp from the PC where sql server is installed, it throws this exception only when i execute sp from a computer different thn one where SQL server is installed.
Here is d code.
CallableStatement call = conn.prepareCall( "{call getAttributeLabelValues(?,?,?)}",
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY
// set parameters.
ResultSet rs = call.executeQuery( ) ;
If I remove options
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY
while executin SP, thn every thing works fine.
here is d exception
com.microsoft.sqlserver.jdbc.SQLServerException: A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.sendExecute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteQuery(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(Unknown Source)
I will appreciate any help.
Sudhir
http://www.jyog.com

use sql server jdbc driver v1.2..........

OraOledb for 64-bit, Linked Servers and SQL Server 2005 issues

Our environment is : SQL Server 2005, Windows Server 2003, 64-bit and 32-bit operating systems.
Problem on 64-bit operating system box: (32-bit works fine).
I am trying to access Oracle 10g database using linked server from our SQL Server 2005. In case of number fileds i got the following error:
Invalid data for type "numeric".
After going through one of the posting in this forumn i was able to resolve the problem by converting those column values to char while querying and then converting them back to numeric type on SQL server side.
But today i ran into another problem. There is a VARCHAR2 column. I was able to retrieve the data yesterday for that column but today i am getting a blank recordset. If i exclude the colum from the query then i am getting all the rows.
I am querying against a view and it has got a number of columns whose data type is VARCHAR2.
Again the problem is on 64-bit operating system only. We have a 32-bit operating system on which i am able to retrieve the data including this column. I looked at the data and everything looks OK. No funny characters etc.
I tried workarounds like using cast, to_char, checking for nulls etc., Nothing works.
Any help is greately appreciated. Thanks.

Did you find a resolution for this? We have similar problem. Set up a linked server in SQL 2006 to Oracle (running on Windows 64-bit) Linked server works and views I had set up were working but they added some new data in the Oracle test database I am using and now I get errors on one of the views.
Error I am getting on the view is "Cannot initialize the data source object of OLE DB Provider "OraOLDEDB.ORacle" for the linked server"
If I fine tune my queries to find the specific table or view that is at issue, then I get the error "inconsistent metadata for a column"

Crystal Report 8.5 with SQL SERVER 2005 problems

Post Author: AREVA
CA Forum: Data Connectivity and SQL
Hi All !We have some problems with Crystal Reports version 8.5 with SQL Server 2005: 1) When we want to generate a report (using data in SQL Server 2005) we have a popup message error : "impossible to loaded pdssql.dll".2) If we want to use SQL Server 2005, which Crystal Reports version we must used ? Is there any restrictions with this connectivity with 8.5 version ?Please, let me known, all informations about SQL Server 2005 and Crystal Report 8.5.Thanks for all !Best regards Anthony

Hello Kamlesh,
There is no expectation that the ActiveX viewer (RDC?) from CR8.5 will work in any version of Visual Studio .NET. There is also no expectation that the ActiveX viewer from CR8.5 will work on a machine with a 64 bit operating system.
You're using VS2008. You should migrate to the bundled edition of CR for VS2008 (v10.5), the ReportDocument object, and the .NET Windows form viewer or Web form viewer.
Sincerely,
Dan Kelleher

SQL Server 2005 64-bit & SQL CLR Stored Procedures using DI API. COM Error.

Similar Messages

Maybe you are looking for