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..........

Similar Messages

In JDBC Sender Adapter , the server is Microsoft SQL .I need to pass current date as the input column while Executing stored procedure, which will get me 10 Output Columns. Kindly suggest me the SQL Query String

In JDBC Sender Adapter , the server is Microsoft SQL .I need to pass current date as the input column while Executing stored procedure, which will get me 10 Output Columns. Kindly suggest me the SQL Query String , for executing the Stored Procedure with Current date as the input .

Hi Srinath,
The below blog might be useful
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/03/06/executing-stored-procedure-from-sender-adapter-in-sap-pi-71
PI/XI: Sender JDBC adapter for Oracle stored procedures in 5 days
regards,
Harish

SQL Server 2005 Problem: Incorrect syntax near '{'

hi, 
 
I am using SQL Server 2005 JDBC driver from Microsoft (sqljdbc_1.0.809.102_enu.exe), there are some problem when calling stored procedure from Database Control: 
 
The following exception flow when parameters of the stored procedure were wrapped to newline : 
 
weblogic.jws.control.ControlException: ControlException on control test2005DBCtrl[Incorrect syntax near '{'.] 
 
Here is the method that generate the above exception: 
 
/** 
* @jc:sql statement:: 
* {call P_dummyProcedure 
 * ( 
 * {intValue}, {value} 
* ) 
* }:: 
*/ 
void callStoreProcedure(int intValue, String value); 
 
But if the parameters were not wrap, the method work fine: 
 
/** 
* @jc:sql statement:: 
* {call P_dummyProcedure 
 * ( {intValue}, {value} ) 
* }:: 
*/ 
void callStoreProcedure(int intValue, String value); 
 
The above problem exist when I change from SQL Sever 2000 to 2005. Both methods is ok for SQL Server 2000 (both the driver from BEA and Microsoft) 
Do any one got the above problem or know why? 
 
cheer ~
 

Wiz Cheng wrote:
hi Joe, 
 
following is a snippet of the config.xml, please see if that cover what you want ~ 
 
config.xml 
---- 
 <JDBCConnectionPool CapacityIncrement="5" 
?? ?? ?? DriverName="com.microsoft.sqlserver.jdbc.SQLServerXADataSource" 
?? ?? ?? InitialCapacity="10" MaxCapacity="100" Name="sql2005Pool" 
?? ?? ?? PasswordEncrypted="{3DES}lF9SivpaSCc=" Properties="user=sa" 
?? ?? ?? SupportsLocalTransaction="true" Targets="cgServer" 
?? ?? ?? TestConnectionsOnReserve="true" TestTableName="SQL Select 1" 
?? ?? ?? URL="jdbc:sqlserver://svr08006\\SQL2005:1533;databaseName=SBI" 
?? ?? ?? XASetTransactionTimeout="true" XATransactionTimeout="300"/> 
 
<JDBCTxDataSource JNDIName="JNDI_SQL_2005" Name="JNDI_SQL_2005" 
?? ?? ?? PoolName="sql2005Pool" Targets="cgServer"/> 
 
 
Thanks ~ 
WizOk, please recreate the pool, telling the console to use the BEA driver for MS.
when it shows you the pool properties, it should show you a URL, something like:
"jdbc:bea:sqlserver://......". Please then edit the URL to add this to the end:
;spyAttributes=(log=(file)spy.log, so the URL looks like
jdbc:bea:sqlserver://......;spyAttributes=(log=(file)spy.log)
Or just make the pool, and then edit the config file.
You should then see the config entry look something like this:
<JDBCConnectionPool CapacityIncrement="5"
DriverName="weblogic.jdbcx.sqlserver.SQLServerDataSource"
InitialCapacity="10" MaxCapacity="100" Name="sql2005Pool"
PasswordEncrypted="{3DES}lF9SivpaSCc=" Properties="user=sa"
SupportsLocalTransaction="true" Targets="cgServer"
TestConnectionsOnReserve="true" TestTableName="SQL Select 1"
URL="jdbc:bea:sqlserver://......"
XASetTransactionTimeout="true" XATransactionTimeout="300"/>
Then please alter the URL line so it's like:
URL="jdbc:bea:sqlserver://......;spyAttributes=(log=(file)spy.log)"
This will generate a file in the server directory called spy.log.
Then when the server boots, please then run the code that would
have caused the problem, as simply as possible, and then send
me the spy.log file.
thanks,
Joe

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

Problem in executing Stored Procedure from Trigger

Hi,
Case1.
I am executing a stored procedure form a trigger. The stored procedure is not executing fully.
Case 2.
But when when I execute Stored Procedure alone it is executing.
CREATE OR REPLACE TRIGGER mhubadmin.call_proc_ratesheet_new
after INSERT OR delete ON mhubadmin.pvt_br_ratesheet
FOR EACH ROW
declare
var_orgid number;
begin
if inserting then
select org_child_id into var_orgid from business_relationship where br_id=:new.br_id;
mhubadmin.proc_ratesheet_new(var_orgid);
else
select org_child_id into var_orgid from business_relationship where br_id=:old.br_id;
mhubadmin.proc_ratesheet_new(var_orgid);
end if;
end;
CREATE OR REPLACE PROCEDURE proc_ratesheet_new(var_orgid in number)
IS
cursor c3 is select distinct(purs.user_id) from hubuser hu
inner join PVT_USER_RATESHEET purs on hu.USER_ID=purs.USER_ID
               where hu.ORG_ID=var_orgid;
cursor c1(varUser_id number) is select purs.user_id,purs.ratesheet_id from hubuser hu
inner join PVT_USER_RATESHEET purs on hu.USER_ID=purs.USER_ID
               where hu.ORG_ID=var_orgid and purs.USER_ID=varUser_id;
cursor c2(varUser_id number) is select hu.user_id,pbr.ratesheet_id from HUBUSER hu
                         inner join BUSINESS_RELATIONSHIP br on hu.ORG_ID=br.ORG_CHILD_ID
                         inner join PVT_BR_RATESHEET pbr on br.BR_ID=pbr.BR_ID
                              where hu.user_id in(select distinct(purs.USER_ID) from hubuser hu
                                   inner join PVT_USER_RATESHEET purs
                                                                 on hu.USER_ID=purs.USER_ID
                                             where hu.ORG_ID=var_orgid) and hu.user_id=varUser_id;
foundFlag boolean;
incrFound integer;
insertFound integer;
deleteFound integer;
str varchar2(4000);
BEGIN
     incrFound:=0;
     insertFound:=0;
     for c3var in c3 loop
for c2var in c2(c3var.user_id) loop
          insert into test values ('Step3:'||c2var.user_id);
          foundFlag:=false;
          for c1var in c1(c3var.user_id) loop
               if c2var.ratesheet_id=c1var.ratesheet_id then
                    foundFlag:=true;
                         incrFound:=incrFound+1;
                         exit;
                    end if;
               end loop;
               if foundFlag=False then
               --insert into pvt_user_ratesheet (username_ratesheet_id,user_id,ratesheet_id) values (SEQ_USER_RATESHEET.nextval,c3var.user_id,c2var.ratesheet_id);
               dbms_output.put_line('Inserted for user :'||c3var.user_id||' is - ratesheet :'||c2var.ratesheet_id);
               insertFound:=insertFound+1;
               end if;
          end loop;
end loop;
     commit;
     incrFound:=0;
     deleteFound:=0;
     for c3var in c3 loop
          for c1var in c1(c3var.user_id) loop
          foundFlag:=false;
          for c2var in c2(c3var.user_id) loop
                    if c1var.ratesheet_id=c2var.ratesheet_id then
                    foundFlag:=true;
                    incrFound:=incrFound+1;
                    exit;
                    end if;
               end loop;
               if foundFlag=False then
               --delete from pvt_user_ratesheet where user_id=c3var.user_id and ratesheet_id=c1var.ratesheet_id;
                    --dbms_output.put_line('Deleted for userid:'||c3var.user_id||' for ratesheet :'||c1var.ratesheet_id);
                    deleteFound:=deleteFound+1;
               end if;
          end loop;
end loop;
     commit;
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.put_line (SQLCODE||' '|| SQLERRM);
END;
Regards,
Mathew

In general, I would suggest that you only catch errors that you can handle reasonably. If you know that a SELECT INTO might return 0 rows for example, handle the NO_DATA_FOUND exception. Having a WHEN OTHERS, particularly without re-raising the exception, only serves to hide the source of the problem. I would much rather that my code fail quickly and explicitly than hope that I see an error message in the output and that other code doesn't start failing because the system wasn't left in an appropriate state.
As Mark suggests, you may choose to implement a comprehensive logging framework using autonomous transactions, in which case a WHEN OTHERS would be reasonable, but you would still want to propagate exceptions you cannot handle.
If you see a WHEN OTHERS clause and there is no RAISE, you probably have an error waiting to happen.
Justin

SQL server 2005 problem with service starting

I am having a problem starting my sqlserver service. It will not start and therefore i have no access to my sql 2005 server database. This is what in the event log. This database was working fine until i had two drives kill over in a RAID configuration.
The striping went out with a hitch and no i want to see if anyone have any ideas before i perform a restore. Do i need to run SQL server repair with the installation disk?

Well from viewing the log it looks like i am in a pickle. Since the SQL service won't start, is there a command or script to run for a database check using powershell? Since it looks like i will be doing a restore, just curious now.
2014-01-16 15:27:58.30 spid5s      Starting up database 'master'.
2014-01-16 15:27:59.81 spid5s      Error: 824, Severity: 24, State: 2.
2014-01-16 15:27:59.81 spid5s      SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:363; actual 0:0). It occurred during a read of page (1:363) in database ID 1 at offset 0x000000002d6000 in file
'W:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately.
Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2014-01-16 15:27:59.81 spid6s      Error: 922, Severity: 14, State: 1.
2014-01-16 15:27:59.81 spid6s      Database 'master' is being recovered. Waiting until recovery is finished.
2014-01-16 15:27:59.81 spid6s      System Task System Task produced an error that was not handled. Major: 9, Minor: 22, Severity:14, State:1
2014-01-16 15:27:59.81 spid5s      Error: 3313, Severity: 21, State: 2.
2014-01-16 15:27:59.81 spid5s      During redoing of a logged operation in database 'master', an error occurred at log record ID (2369:160:2). Typically, the specific failure is previously logged as an error in the Windows Event Log
service. Restore the database from a full backup, or repair the database.
2014-01-16 15:27:59.81 spid5s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL
Server Books Online.

Error while Executing stored procedure using ant

Hi,
I am trying to execute a stored procedure using ant ..
My build.xml is like this...
<project name="myproject" default="db.build">
<target name="db.build">
<sql driver="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:thin:@idm.orademo.com:1521:orcl"
userid="test"
password="oracle11g"
print="yes"
classpath="E:\\ojdbc14.jar"
src="E:\\upg_9102BP07.sql" />

</target>
</project>
I have my stored procedure in upg_9102BP07.sql as shown in above src..
When im executing ant cmd I got the following exception
E:\>ant -f test.xml
Buildfile: test.xml
db.build:
*[sql] Executing resource: E:\upg_9102BP07.sql*
*[sql] Failed to execute: declare cnt int*
BUILD FAILED
E:\test.xml:12: java.sql.SQLException: ORA-06550: line 1, column 15:
PLS-00103: Encountered the symbol "end-of-file" when expecting one of the following:
*:= . ( @ % ; not null range default character*
Total time: 44 seconds
I have no clue.. But this sql ran successfully when did manually..
Please help me in solving the issue...
-- Marias

Here is my script bit lengthy...
Rem
Rem $Header: oim/server/Database/Oracle/Upgrade/Release91x/910x/List/9102_ddl_AddcolumnToRCE_Oracle.sql st_oim_devjain_bug-9003841/1 2009/10/09 02:24:19 devjain Exp $
Rem
Rem 9102_ddl_AddcolumnToRCE_Oracle.sql
Rem
Rem Copyright (c) 2009, Oracle and/or its affiliates. All rights reserved.
Rem
Rem NAME
Rem 9102_ddl_AddcolumnToRCE_Oracle.sql - <one-line expansion of the name>
Rem
Rem DESCRIPTION
Rem Create a new column 'RCE_DELETE' in RCE table
Rem
Rem MODIFIED (MM/DD/YY)
Rem blaksham 09/30/09 - Created
Rem
declare cnt int;
Begin
 Select Count(1) into cnt From User_Tab_Columns Where TABLE_NAME='RCM' And COLUMN_NAME='RCM_DELETE';
 IF cnt=0 Then
 Begin
 Execute Immediate 'ALTER TABLE RCM ADD RCM_DELETE VARCHAR2(1)';
 End;
 Else
 DBMS_OUTPUT.PUT_LINE('Column already exists in the DB');
 End IF;
End;
Rem
Rem $Header: oim/server/Database/Oracle/Upgrade/Release91x/910x/List/9102_dml_odf_source_name.sql st_oim_devjain_bug-9003841/1 2009/10/09 02:44:45 devjain Exp $
Rem
Rem 9103_dml_odf_source_name.sql
Rem
Rem Copyright (c) 2009, Oracle and/or its affiliates. All rights reserved.
Rem
Rem NAME
Rem 9103_dml_odf_source_name.sql - <one-line expansion of the name>
Rem
Rem DESCRIPTION
Rem <short description of component this file declares/defines>
Rem
Rem NOTES
Rem <other useful comments, qualifications, etc.>
Rem
Rem MODIFIED (MM/DD/YY)
Rem vpotukuc 09/17/09 - Bug8796435: Increase the size of odf_source-name
Rem vpotukuc 09/17/09 - Created
Rem
SET ECHO ON
SET FEEDBACK 1
SET NUMWIDTH 10
SET LINESIZE 80
SET TRIMSPOOL ON
SET TAB OFF
SET PAGESIZE 100
declare
collen NUMBER := 0;
begin
select char_length into collen from user_tab_columns where table_name = 'ODF' and column_name = 'ODF_SOURCE_NAME';
IF (collen < 400) then
execute immediate 'alter table ODF modify ODF_SOURCE_NAME varchar2(400)';
END IF;
END;
File name: 91_dml_update_reviewers_With_NoEmail_attestation.sql
Purpose: Modify the email template to replace the 'Delegated By Last Name' with 'Reviewer Last Name' and 'Delegated By User Id' to 'Reviewer User Id'.
Author: Babu Lakshamanaiah
Description: Modify the email template 'Attestation Reviewers With No E-mail Addresses Defined'
declare
cnt int;
begin
Select Count(1) into cnt From emd Where emd_name='Attestation Reviewers With No E-mail Addresses Defined' and emd_language='en' and emd_country='US';
IF cnt=0 Then
Begin
DBMS_OUTPUT.PUT_LINE('There is no record with emd_name Attestation Reviewers With No E-mail Addresses Defined ');
End;
Else
update emd set emd_body='The following attestation reviewers do not have email addresses defined. Attestation requests have been generated for these reviewers and can be accessed by loging in to Oracle Identity Manager. However, notification emails were not sent.' ||chr(10) || chr(10) ||
'Attestation process: <Attestation Definition.Process Name>' || chr(10) ||
'Attestation Request ID: request <Attestation Request.Request Id>' || chr(10) ||
'Request date: <Attestation Request.Request Creation Date>' || chr(10) || chr(10) ||
'Reviewers Without E-mail Address: <reviewers> ' || chr(10) ||
'<Attestation Task.Reviewer First Name> <Attestation Task.Reviewer Last Name> [<Attestation Task.Reviewer User Id>]' Where emd_name='Attestation Reviewers With No E-mail Addresses Defined' and emd_language='en' and emd_country='US';
End IF;
commit;
end;
Please help me out.....
--Marias

SQL server Query to sort the Stored procedure as text

Hi
I have a requirement as below :
Stored procedure in SQL server has some 1000 lines of code where the SP uses select, insert , update ,delete and Joins on direct tables and as well as temp tables , the requirement is to get all text code from sp which is used for either select/insert
except update and delete.
for example :
Create PROCEDURE testproc
AS
Begin
/*Statement 1*/
select id from emptable
/*Statement 2*/
select address into #empAddress from empAddresstbl
/*Statement 3*/
update a
set id = 0 from usertbl a
/*Statement 4*/
Update u
set access=0 from usertbl u
inner join permissionstbl p
on u.userid = p.userid
/*Statement 5*/
select name into #empname
from empnametbl
inner join Nametbl on
empname.id = name.id
END
for the given sample sp the output of query shld be
from emptable
from empaddresstbl
from empnametbl
join nametbl
it shld not consider the table name from update/delete and the tables used for joins in updates/delete.
This has to be achieved using SQL
Thanks,

Hi All,
Problem is solved after adding files to microsoft access 2000 runtime. runtime missing some DLLs related to sql server 2000 to update those files follow the links below
http://support.microsoft.com/?kbid=287484
http://www.microsoft.com/office/orkarchive/2000ddl.htm#accsql
Thanks,
Brahma

Error While Executing Stored Procedure - SAP BPC 5.0

Hi all
I have defined stored procedure 'EP2' in the account transformation rules and which runs fine with all the entities.
But when I filter particular entity which give no data extrace to the selections made instead of giving the comment:
0 rows created and update it gives the error below.
Kindly Help me out if any one has the idea of running stored procedure
Executing SPRUNCALCACCOUNT "[[FINANCE]],[[ACTUAL]],[[LC]],[[SPSCOPE_367693]],[[SPLOG_887033]],[[EP2]]"
SPRunCalcAccount Version 2.06
-ERR- CALC-070 No DATA Extract From FACT Table
Time to run stored procedure:2.8 sec.
Edited by: Harish Bysani Kodanda on Mar 14, 2008 8:46 AM
Edited by: Harish Bysani Kodanda on Mar 14, 2008 8:47 AM
Edited by: Harish Bysani Kodanda on Mar 14, 2008 8:48 AM

Yes, the business rules stored procedures surface an error if there is an empty data set to operate on.

Error while fetching Stored procedure from JDev DB Adapter

Hello
I am facing a problem while configuring stored procedures from Jdeveloper using DB Adapter. I am using Sql Server 2005 as my database,Jdeveloper version is 10.1.3.1.Bpel Version is 10.1.3.3. Connection to the Sqlserver 2005 database is fine, but it shows only views and tables. I get the following error message when I try to add the sql stored procedure call
"An error occured while obtaining the database schemas.Verify that the database connection is valid , and is supported"
Can someone help me please.
Thanks,
Phani
Edited by: Phani on Oct 28, 2008 11:30 AM

I think you have two problems here. First, JDeveloper 10.1.3.1 doesn't support SQL Server stored procedures. There is a command-line utility that you can use to generate the required BPEL artifacts (WSDL and XSD). Second, you're using a 10.1.3.1 design-time with a 10.1.3.3 runtime. These are not compatible so you will likely run into namespace issues when you try to run your BPEL processes. You should upgrade your JDeveloper to 10.1.3.3. JDeveloper will support third-party databases in 11.1.1 including SQL Server 2005 (but not 2000), IBM DB2 v8.x and v9.x, DB2 AS/400, and MySQL. JDeveloper will support MySQL v5.2.6 and above because the INFORMATION_SCHEMA.PARAMETERS table was added at that time. The PARAMETERS table does not exist in MySQL versions prior to v5.2.6 so you will have to use the command-line utility.

Executing Stored Procedure within Excel

I am in the middle of setting up an Excel spreadsheet that will execute a stored procedure I have created and return the results to Excel. Pretty much following the example set here:
http://datapigtechnologies.com/blog/index.php/running-a-sql-stored-procedure-from-excel-with-dynamic-parameters/
But, the problem I am stuck on and unable to yet find an answer to, is can I execute the procedure from within Excel and instead of specifying a parameter enter a WHERE clause. At the moment the last step of my stored procedure is:
SELECT * FROM MY_TABLE
WHERE ([PRODUCT] LIKE 'DESK-%') AND (NOT([DISCOUNT VALUE] IS NULL))
But, I cannot find if it is possible to execute this from within Excel. I am not sure if it I am able to set the WHERE as a parameter which may be the way I should be going about this.
Thanks.

Are you invoking a stored procedure, or are you sending a SELECT statement (ad-hoc query) to the SQL Server? It seems like you are sending an ad-hoc query.
If that is the case, I would not put the entire WHERE clause as a parameter. I would do it something like this:
"SELECT * FROM MY_TABLE WHERE ([PRODUCT] LIKE '" & Range("B2").Value & "%') AND (NOT([DISCOUNT VALUE] IS NULL))"
That assumes that the parameter that you want to use is in cell B2.
Ideally, I would prefer not to use ad-hoc queries. Instead, create a stored procedure which takes the Product type as a parameter. There are lots of examples on the net on how to query SQL Server from Excel via a stored procedure with parameters.

Cannot execute a MS SQL Server 2005 Stored procedure via OSB BS

I created the jca from Jdeveloper using DBAdapter. Then from eclipse I created the wsdl by generating the service. Then I imported all the relevant files in OSB console and created the business service. After executing the business service I get the below error (Pls scroll down).
I tried many combination s. I tested with a stored procedure which returns only 1 row and 1 column and I hardcoded the column value. I also tried a stored procedure without any input parameters.
I am sure there is no problem with the deployment of the datasource because I can execute operations to a table for select, update, delete using a business service following the above procedures.
I created the stored proc following the same steps for select, update, delete. Also one more info is that when I call a stored proc from Oracle XE database it is working fine.
My JDBC version is 4 . I am using the jar file provided by Microsoft that is sqljdbc4.
Web Logic Server - 11gR1
OSB - 11g + coherence + OEPE
JDeveloper - 11.1.1.3.0
can someone please help. This is very urgent. I have tried many combination's to get this to work from last 3 days without any luck.
Help appreciated.
Regards
this happens only while executing the stored procedure.
The invocation resulted in an error: Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/NEHR_OSB/Lab/SvcNumb [ SvcNumb_ptt::SvcNumb(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'SvcNumb' failed due to: Stored procedure invocation error.
Error while trying to prepare and execute the OSBLogs.dbo.sp_Numb API.
An error occurred while preparing and executing the OSBLogs.dbo.sp_Numb API. Cause: java.lang.NullPointerException
; nested exception is:
BINDING.JCA-11811
Stored procedure invocation error.
Error while trying to prepare and execute the OSBLogs.dbo.sp_Numb API.
An error occurred while preparing and executing the OSBLogs.dbo.sp_Numb API. Cause: java.lang.NullPointerException
Check to ensure that the API is defined in the database and that the parameters match the signature of the API.
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/NEHR_OSB/Lab/SvcNumb [ SvcNumb_ptt::SvcNumb(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'SvcNumb' failed due to: Stored procedure invocation error.
Error while trying to prepare and execute the OSBLogs.dbo.sp_Numb API.
An error occurred while preparing and executing the OSBLogs.dbo.sp_Numb API. Cause: java.lang.NullPointerException
; nested exception is:
BINDING.JCA-11811
Stored procedure invocation error.
Error while trying to prepare and execute the OSBLogs.dbo.sp_Numb API.
An error occurred while preparing and executing the OSBLogs.dbo.sp_Numb API. Cause: java.lang.NullPointerException
Check to ensure that the API is defined in the database and that the parameters match the signature of the API.

Hi,
Even I am getting this kind of problem while executing a stored procedure from OSB.
I have a stored procedure and i have created wsdl and xsd using JDEV. Now when i am creating a .biz with this wsdl and executing it , this is giving following error:
<JCA_TRANSPORT_RUNTIME_APPLICATION_FAULT xmlns="http://www.bea.com/transport/2007/05/jca">
oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/DBTest/TryDB [ TryDB_ptt::TryDB(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'TryDB' failed due to: Error while trying to prepare and execute an API.
An error occurred while preparing and executing the EAIUSER.DIM_Procedure API. Cause: java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00201: identifier 'EAIUSER.DIM_PROCEDURE' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
[Caused by: ORA-06550: line 1, column 7:
PLS-00201: identifier 'EAIUSER.DIM_PROCEDURE' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
; nested exception is:
JCA-11811
Error while trying to prepare and execute an API.
An error occurred while preparing and executing the EAIUSER.DIM_Procedure API. Cause: java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00201: identifier 'EAIUSER.DIM_PROCEDURE' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
[Caused by: ORA-06550: line 1, column 7:
PLS-00201: identifier 'EAIUSER.DIM_PROCEDURE' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
Check to ensure that the API is defined in the database and that the parameters match the signature of the API. Contact oracle support if error is not fixable.
Please help me in solving this..

Error While Installing IDES ECC6 with SQL Server 2005

Dear Experts,
I found an error while installing IDES ECC6 with SQL Server 2005. The error is raising at the stage of 17 of 24 processing the procedure of 195 of 197 (sap_z_set_permissions).
I have tried several times by configuring different type of activites but still i am facing the same problem at the same stage. Please help me in thig regard.
I herewith pasted hereunder log files information
Regards,
B.Sudharsan
ERROR 2008-01-17 18:38:47
FCO-00011 The step ExeProcs with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs was executed with status ERROR .
INFO 2008-01-17 18:40:05
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs".
ERROR 2008-01-17 18:38:47
MDB-05053 Errors when executing sql command: If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.

Sudarshan,
Occasionally, mid-way through the upgrade, DB permissions to users might change. Check to see, if the users SAP<SID>, OPS$ users have the DBA privilege. Re-assign the role and try continuing with the upgrade.

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

Problem using production version of SQL Server 2005 JDBC drivers

A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
Regards,
Sabrina
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)
     ... 11 more
Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
     at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
     ... 12 more

SabrinaL wrote:
A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
Regards,
SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
Does the driver present a dll for each of those? You can also get good JDBC help
from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
Joe Weinstein at BEA
>
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)
     ... 11 more
Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
     at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
     ... 12 more

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

Similar Messages

Maybe you are looking for