Issue using ODBC CALL

I'm calling a oracle stored procedure using ODBC Call method
{call testSP(?)}"&params
The parameter read from the SP is VARCHAR2. On this call, the 2001th character gets replaced by chr(0). The same SP called with Begin, End block does not reproduce the error. Can someone please point me to a document which explains this? please feel free to ask any questions to clarify the issue

maybe you can try another theme. You can download hundreds of themes. There is surely one that displays the time during the "incoming call" screen.
The search box on top-right of this page is your true friend, and the public Knowledge Base too:

Similar Messages

Issues on ODBC CALL SQLStatistics

We have an application that call ODBC
function SQLStatistics to get the information of database objects, oracle
ODBC Driver can return the right answer,
the problem is that the process is very
slow, we analyzed the database, why oracle ODBC driver doesn't use the instant statistics information from
system view?
thanks for your advice
Mark

The first issue you raised doesn't seem to be a cucm prompt. This looks like the Telco is playing this prompt. Was this an outside number you forwarded the call to? Does this happen when you do a call forward to an internal number
The second issue can be solved by changing the calling device properties on the gateway. Go to the gateway, then scroll to:
Call Routing Information - Outbound Calls and choose either of the ff: ( it appears that the gateway is set to use the last/first redirecting number (which is the users desk phone not the calling phone)
Originator—Send the directory number of the calling device.
Once the change is made reset the gateway. If its mgcp you need to stop and start the mgcp process on the gateway itself

How can I debug leaks caused by ODBC calls in app linked with libtt.so?

Hi,
we are using TimesTen Release 7.0.5.0.0 on Solaris 10.
and we are using libtt.so to link our application and connect using ODBC calls.
The problem is that we have made some serious changes to our large code base and now we see a leak.
Here is what I know:
1) Although it is easy to reproduce it doesn't seem to follow a clear pattern. ie. the amount leaked isn't a direct function of the number of request or time spent.
2) When our application is linked with libttclient.so there is no leak at all.
3) prstat shows increments of 4 MBytes each time it leaks.
So I suspect it is because the memory isn't freed but how can I tell which ODBC calls are causing it?
Is there a debug option I could turn on to help with this?
Perhaps something in ttTraceMon?
Thanks

Hello Serge,
Just a note that we often times get this type of alarm about memory leaks in TimesTen when using the libtt.so library when using tools such as top or prstat to gage memory consumption. The reality is that these commands are not a good way to look for memory leaks / memory utilization when using TimesTen in direct connect mode. The TimesTen database resides in shared memory and so the fact that prstat shows big or increasing numbers should not be alarming.
The only reliable way to check for memory leaks is to use a tool designed exactly for that such as Purify, which the TimesTen development team uses extensively and so it's unlikely that you'll find memory leaks in TimesTen.
Have you found that memory is being exhausted after a period of application runtime and transaction iterations?
You could use ttTraceMon and work with TimesTen support/engineering to extrapolate and answer from the trace it gaves, but unfortunately, there's rarely an easy way to answer queries on what is going on in either the Permament or Temporary partition.
I'd first make sure that there is indeed a problem but running your application workload for some time. My suspicion is that the prstat command results are being misleading once more.
Regards,
Henri

Anybody experiencing static when using Advanced Calling?

Since activating Advanced Calling, I hear static behind the callers voice, the caller says they can hear my clearly. So I went ahead an disabled Advanced Calling because of this.
Anyone else experiencing similar issues using Advanced Calling?

Yes, on one call today I could hear just the faintest static that I have never heard before. The other calls I made since upgrading seem fine or it wasn't quiet enough to hear it.

How to call PL/SQL stored procedure using ODBC?

Could anyone tell me how can I call PL/SQL stored procedure using
ODBC? Are there any sample codes?
Thanx!
null

You are correct on all counts, they all should work.
Oracle Product Development Team wrote:
: Hi,
: I don't know the exact syntax in ODBC, but reasoning by analogy
: with other API's, I'd bet one of the following works
: (for a call to: procedure my_proc(n1 number, n2 number);):
: "{ my_proc(1,2); }"
: "{ call my_proc(1,2); }"
: "{ begin my_proc(1,2); end }"
: "begin my_proc(1,2); end;"
: "begin my_proc(1,2); end"
: Hope this helps. - Pierre
: jiangbuf (guest) wrote:
: : Could anyone tell me how can I call PL/SQL stored procedure
: using
: : ODBC? Are there any sample codes?
: : Thanx!
: Oracle Technology Network
: http://technet.oracle.com
null

"use ODBC outer join syntax on limits" issues

I'm converting a series of BQY's from Brio 6.6 to Hyperion 9.3. I have some questions about the "use ODBC outer join syntax on limits" option in the OCE. I sort of understand this option's purpose, but I don't completely understand the SQL I'm seeing. For example Brio 6.6 is generating the following SQL statement:
SELECT * FROM tblA AL1 LEFT OUTER JOIN tblB AL38 ON (AL38.ParentID=AL1.ChildID AND
AL38.Data='SomeData') WHERE ((NOT AL38.Action IS NULL))
Now, Hyperion 9.3 generated the SQL statement as follows:
SELECT * FROM tblA AL1 LEFT OUTER JOIN tblB AL38 ON (AL38.ParentID=AL1.ChildID AND
AL38.Data='SomeData') AND (NOT AL38.Response IS NULL))
My questions are:
1) Why isn't the "NOT AL38.Action IS NULL" statement included in the outer join in Brio? I'm OK with the fact that it is not, but my limited understanding of the "use ODBC outer join syntax on limits" seems to indicate that it should end up there.
2) The Hyperion SQL is returning incorrect results. How can I get Hyperion to generate the same SQL as Brio? And still use the OCE with "use ODBC outer join syntax on limits" selected? This setting is working fine for other BQY's.

In the first post, I modified the actual table name I'm using, the following is my actual output:
SQL> SELECT A0.name partName,A2.name usedPartName FROM WTPartUsageLink A1
2 RIGHT OUTER JOIN (
3 (SELECT A0.idA2A2,A0B.name FROM WTPart A0 INNER JOIN WTPartMaster A0B
4 ON ((A0.idA3masterReference = A0B.idA2A2)))
5 UNION ALL
6 (SELECT A0.idA2A2,A0B.name
7 FROM WTProduct A0 INNER JOIN WTProductMaster A0B ON ((A0.idA3masterRefer
ence = A0B.idA2A2)))) A0
8 ON (A0.idA2A2 = A1.idA3A5) LEFT OUTER JOIN
9 (SELECT A2.idA2A2,A2.name FROM WTPartMaster A2
10 UNION ALL
11 SELECT A2.idA2A2,A2.name FROM WTProductMaster A2) A2
12 ON (A1.idA3B5 = A2.idA2A2) ORDER BY partName DESC,usedPartName DESC;
FROM WTProduct A0 INNER JOIN WTProductMaster A0B ON ((A0.idA3masterRefer
ence = A0B.idA2A2)))) A0
ERROR at line 7:
ORA-00923: FROM keyword not found where expected
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit Production
PL/SQL Release 9.2.0.1.0 - Production
CORE 9.2.0.1.0 Production
TNS for Solaris: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production
Thanks,

How to use ODBC SQLDriverConnect() without using tnsnames.ora file

I have an ODBC application that connects to an Oracle 10g database. Currently, my SQLDriverConnect() function call uses the following connection string:
DRIVER={Oracle in OraClient10g_home1}; DBQ=MyDB.world; DBA=W; UID=foo; PWD=bar
This requires an entry in the tnsnames.ora file that looks like this:
MyDB.world =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)(Host = server1.intel.com)(Port = 1521)
(ADDRESS =
(PROTOCOL = TCP)(Host = server2.intel.com)(Port = 1521)
(ADDRESS =
(PROTOCOL = TCP)(Host = server3.intel.com)(Port = 1521)
(ADDRESS =
(PROTOCOL = TCP)(Host = server4.intel.com)(Port = 1521)
(LOAD_BALANCE = yes)
(CONNECT_DATA = (SERVER = DEDICATED)
(SERVICE_NAME = MY_SRVC))
However, I would really like to be able to connect using ODBC without having to create that entry in the tnsnames.ora file. I have tried to substitute the DBQ=MyDB.world with the entire (DESCRIPTION=..... string from the original tnsnames.ora file, but it returns the error:
ORA-12154: TNS: Could not resolve the connect identifier specified.
I have heard others are able to use sqlplus with no tnsnames.ora file and the do specify the entire (DESCRIPTION=.... string on the sqlplus connection string, but is this possible to do using the ODBC SQLDriverConnect() function? If so, do I need to use a different keyword/value pair other than DBQ=?
Any help on this would be greatly appreciated.
Thank you.

How would that work in a load balanced configuration? Take a closer look at the tnsnames.ora example I included in my original post. I have 4 ADDRESS= sections to denote 4 servers that are part of the load balanced environment.
Also, I'm not familiar with that syntax, I need to use the syntax supported by the SQLDriverConnect() API function, which looks like this:
DRIVER={Oracle in OraClient10g_home1}; DBQ=MyDB.world; DBA=W; UID=foo; PWD=bar
I don't know as SQLDriverConnect() would accept an alternative syntax. But the more important issue here is the ability to specify those 4 servers in the load balanced configuration as indicated by that tnsnames.ora entry.

Unable to connect to SQL database through ODBC calls

I have been looking around for an answer to this, but haven't found the exact issue I'm seeing.
I have several Excel spreadsheets which have been working until recently, which use an ODBC call to a remote SQL database. The database is running, remote connections are allowed. The SQL server is in a domain which has no external trusts. Users with accounts
in this domain can remotely access the SQl databases through ODBC just fine. Users who do not have domain accounts in this domain are being denied access by their domain account, and the SQL authentication is not passed through, even though remote access is
set to allow "everyone", and the database is set to Windows authentication and SQL authentication. This worked until early this week (the spreadsheet was created in 2010), and I have been looking fruitlessly for a fix ever since. As far as I know,
no changes were made to group policy on this domain, and no changes were made to the server or database recently, except Microsoft patches. None of the patches this month looked like they would affect this.

It works locally on the server and remotely for users in the same domain. I am trying to use the SQL account and password to connect to the database, but users from outside this domain fail to reach the SQL database for authentication. It looks like Windows
authentication is not passing the SQL credentials on if the windows authentication fails. I don't know how to resolve this. The only options in SQL are "Windows authentication and SQL authentication" or "Windows authentication only". The database is already
set to the first option. Somehow, I need to set the server to allow the SQL authentication even if the Windows authentication fails.
Hi pkuti01,
SQL Server mixed mode is "Windows Authentication and SQL Server Authentication", we have to restart SQL Server service after change the authentication to mixed mode.
In your case, have you got any error message/information if you faild connect to SQL Server via ODBC? If so, please post them to us for further investigation. Furthermore, here is an article regarding steps to troubleshooting SQL connectivity issues for
your reference. Please see:
http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
Anyone have an idea on other things to try to debug/resolve this?
Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
Thanks!

After a week's worth of debugging, I found the issue.
The Java type returned from the call was defined as ArrayList. Changing it to List resolved the problem.
I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid. And, why it works in Debug mode and not in Release build is even stranger. Maybe someone can shed some light on the logic here to me.

Post Goods issue using bapi_goodsmvt_create

hi,
Iam trying to do post goods issue using bapi_goodsmvt_create. please let me know what are the mandatory fields to be passed?

hi,
*& Report ZRPT_SUB_KO01GOODSMOVEMENT
REPORT ZRPT_SUB_KO01GOODSMOVEMENT.
PARAMETERS : P_BAG(17) TYPE C,
             P_ZZORG LIKE zaUFK-ZZORG,
             P_MATNR LIKE MARA-MATNR,
             P_WERKS LIKE AUFK-WERKS,
             P_WERK LIKE AFPO-PWERK,
             P_DATE LIKE MKPF-BUDAT,
             P_LGORT LIKE GOITEM-LGOBE.
DATA : BDC_DATA TYPE STANDARD TABLE OF BDCDATA. "internla table for bdc data
DATA : WA_BDC_DATA TYPE BDCDATA .                "work area for bdc data
DATA : T_XMSEG TYPE   MSEG.
DATA : T_XMKPF TYPE MKPF.
DATA : V_BAGS1(17) TYPE C.
DATA : BEGIN OF WA_MB1B,
       ZZGCODE TYPE ZMIGO-ZZGCODE,
       ZZGBAGS TYPE ZMIGO-ZZGBAGS,
       WERKS TYPE AUFK-WERKS,
       LGORT TYPE VBRP-LGORT,
       ZZORG TYPE zAUFK-ZZORG,
       END OF WA_MB1B.
DATA : V_MATERIAL TYPE BAPI2017_GM_HEAD_RET-MAT_DOC.
data : v_date(10) type c.
DATA : T_GOODSMVT_HEADER TYPE BAPI2017_GM_HEAD_01,
       T_GOODSMVT_CODE TYPE BAPI2017_GM_CODE,
       T_GOODSMVT_ITEM TYPE STANDARD TABLE OF BAPI2017_GM_ITEM_CREATE,
       T_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA : WA_GOODSMVT_ITEM TYPE BAPI2017_GM_ITEM_CREATE.
DATA : BEGIN OF S_MARA,
       MEINS LIKE MARA-MEINS,
       END OF S_MARA.
DATA : MATERIALDOCUMENT TYPE BAPI2017_GM_HEAD_RET-MAT_DOC.
*FORM GOODSMOVEMENT TABLES T_RETURN
                         USING WA_MB1B LIKE WA_MB1B.
SELECT SINGLE MEINS
               FROM MARA
               INTO S_MARA
               WHERE MATNR = P_MATNR.
   CONCATENATE p_date6(2) p_date4(2) p_date+0(4) INTO V_DATE SEPARATED BY '.'.
    T_GOODSMVT_HEADER-PSTNG_DATE = P_DATE.
    T_GOODSMVT_HEADER-DOC_DATE = P_DATE.
    T_GOODSMVT_CODE-GM_CODE = '04'.
    WA_GOODSMVT_ITEM-MATERIAL =      P_MATNR.                    "'000000000000001556'.
    WA_GOODSMVT_ITEM-PLANT =        P_WERK.                     " '1000'.
    WA_GOODSMVT_ITEM-STGE_LOC =      P_LGORT.                    " '0001'.
    WA_GOODSMVT_ITEM-MOVE_TYPE =     'Z42'.
    WA_GOODSMVT_ITEM-VENDOR =         P_ZZORG.                   "'0000100224'.
    WA_GOODSMVT_ITEM-ENTRY_QNT =      P_BAG.                   " '1'.
    WA_GOODSMVT_ITEM-ENTRY_UOM =     S_MARA-MEINS.
    WA_GOODSMVT_ITEM-ENTRY_UOM_ISO = S_MARA-MEINS.
    WA_GOODSMVT_ITEM-MOVE_PLANT = P_WERKS.
    APPEND WA_GOODSMVT_ITEM TO T_GOODSMVT_ITEM.
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
EXPORTING
      GOODSMVT_HEADER          = T_GOODSMVT_HEADER
      GOODSMVT_CODE            = T_GOODSMVT_CODE
IMPORTING
    MATERIALDOCUMENT           = V_MATERIAL
TABLES
      GOODSMVT_ITEM            = T_GOODSMVT_ITEM
RETURN                        = T_RETURN.
BREAK shailajaa.
           EXPORT t_return to MEMORY ID '123'.
           EXPORT V_MATERIAL TO MEMORY ID 'MAT'.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
     EXPORTING
       WAIT          = ' '.
*ENDFORM.

Crystal 2011 getting Logon failed IM004 error when using ODBC (RDO)

I just installed Crystal Reports 2011 on Windows 7 Ultimate SP1. Sporadically, but way too often (I would estimate about 60% of the time), when I go to set up an ODBC (RDO) connection or refresh an existing report and enter the password, I get the following error:
Logon failed.
Details: IM004:[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_Handle_ENV failed
Other times, it just works, with no changed made. It seems to work slightly more often when using the SQL Server driver (the one for SQL 2000) as opposed to the SQL Native Client or SQL Server Native Client 10.0 drivers. But not often enough for that to be the solution.
I have tested this with a locally installed SQL Server (on the same machine as Crystal Reports) and remote SQL Servers, with SQL 2000, 2005 and 2008. Same results.
I have Crystal Reports 2008 installed on the same machine and have not once had this problem. I have tried using the same ODBC connections I already had from Crystal 2008 with Crystal 2011 and also to create new ones, same results either way.
Is this a known issue, or is there a switch/setting I need to change to make this work consistently? I am especially puzzled by the fact that it seems random, I have not been able to find any pattern at all.

Hi Victoria,
MS SQL Server 2008 has a client install now, the MDAC/WDAC doesn't install it as MS used to do with all of their OS's. CR also had to update the use of SQL Server 2008 to include the SQLNCLI10 client engine.
I suggest, if you have not already, install the Native 10 client from either the SQL Server CD or you can download the MSI from MS's site and only use the Native 10 driver.
MS kind of dropped ODBC and moved to OLE DB. The native client actually uses the OLE DB driver so using ODBC just puts another layer on top of OLE DB anyways. It's more convenient to use ODBC for deploying applications but it can affect performance.
Anyways, as noted, CR 2011 is still in Ramp up mode so this issue may have been tracked. If not though you can purchase a support case, if it's a bug then you'll get a refund, if it's a limitation in MS then no refund.
There is [SP 1 for CR 2011|https://smpdl.sap-ag.de/~sapidp/012002523100007683092011E/cr2011sp1.exe] - http://service.sap.com/sap/bc/bsp/spn/bobj_download/main.htm
Seems to be a problem with that page right now so try again later... and apply SP 1 or wait until it goes GA and test again. If it's still an issue then you can log a case.
Firefox just got updated and it's failing, IE works though...
Thanks again
Don
Edited by: Don Williams on Jun 22, 2011 8:51 AM

An issue using the COM components supplied with SAP GUI 6.2 or 6.4

We are having an issue using the COM components supplied with SAP GUI 6.2 or 6.4. We used to have SAP 4.6c and now we have 5.0. When we were on 4.6c, we used these COM components to logon and execute RFC calls and we had much success. Now that we are on 5.0, we cant seem to instance any SAP functions that have something to do with SAP Workflow. We have experienced this problem when using VB6 or .NET, but our existing code that always worked is in VB 6.0.
SAP Components used:
o     SAP Logon Control
o     SAP Function Control
o     Librfc32.dll
o     Other supporting C DLLs and/or COM object supplied with the SAP GUI installation.
For example, if we want to call the RFC ARCHIV_CONNECTION_INSERT, this code fails in VB6 when the Set objworkflow = objFuncCtrl.Add(strFunction) line of code executes. Instead of returning an instance of the object ARCHIV_CONNECTION_INSERT function, no object is created. In 6.2, SAP raises no errors, but the object we are trying to create is still Nothing. If we use 6.4, SAP raises an error SAP data type not supported via a message box and then the object is still = Nothing. Interestingly enough, the 6.2 GUI COM controls dont display the error dialog. The message box that is shown comes from the SAP Function COM Object "SAP.Functions" (wdtfuncs.ocx).
Now, what is interesting is if we use the same code to call a standard function or custom function that doesnt have anything to do with SAP Workflow, then the code works fine. Again, all of our code used to work just fine on an SAP 4.6 system.
Here is the code that fails:
    'SAP Logon control - object for creating connections to an SAP system
    Dim objSAPLogonCtrl As Object
    'SAP connection object
    Dim objConnection As Object
    'Object that will represent the SAP function called
    Dim objSAP As Object
    'SAP function control object - object factory for creating other SAP function objects
    Dim objFuncCtrl As Object
    'Create instance of an SAP logon conrol
    Set objSAPLogonCtrl = CreateObject("SAP.Logoncontrol.1")
    'Create a connection object
    Set objConnection = objSAPLogonCtrl.NewConnection
    'Define connecion parameters
    objConnection.ApplicationServer = "sapvm"
    objConnection.SystemNumber = "00"
    objConnection.Client = "800"
    objConnection.User = "iissap"
    objConnection.Password = "tstadm"
    objConnection.Language = "E"
    objConnection.TraceLevel = 10
    'call the logon method of the connection object
    If objConnection.Logon(0, True) = False Then
        MsgBox Error
        Exit Sub
    End If
    'Create an instance of the SAP Function control object
    Set objFuncCtrl = CreateObject("SAP.Functions")
    'Set the function control connection object
    Set objFuncCtrl.Connection = objConnection
    'Function name to be generated and called
    Dim strFunction As String
    strFunction = <b>"ARCHIV_PROCESS_RFCINPUT"</b>
    'Create an instance of the function defined in strFunction
    Set objworkflow = objFuncCtrl.Add(strFunction)
    If objworkflow Is Nothing Then
        MsgBox "Could not create object " & strFunction
    Else
        MsgBox strFunction & " object created."
    End If
If anyone has seen anything like this or has any ideas, please help!
Mike and Hameed
<b></b>

Hi,
documentation on the Scripting API is available at ftp://ftp.sap.com/pub/sapgui/win/640/scripting/docs/
This API is a replacement of the existing, obsolete COM interfaces.
Best regards,
Christian

Errors when using the Call statement for MS SQL Server

I've tried executing a Stored Procedure using the Call method of Portal 2 Go. But it gets an internal error b/c of it. Any Ideas why and how to resolve?

Hello,
Which version of SAP BOBJ XI3.1 you are using?
What I am aware is BEGIN_SQL was very well working for SQLServer2005 in case of ODBC connection.
Can you try one thing for SQLServer2008 have a Native driver installed on your client machine and use ODBC connection rather than OLEDB connection.
If that works fine, its good
Otherwise you can raise a message for resolving this problem with the support team.
Thanks,
Vivek

ODBC call SQLDriverConnect for data source Server name failed: [ . Notify Customer Support.

Need help !
While running DS job through designer we are getting below error:
ODBC call <SQLDriverConnect> for data source <SErver name> failed: <[>. Notify Customer Support.
Additional notes:
1. Source and Target datastore are getting connected properly as i have imported table's definition using it.
2. Source and target data store pointing to SQL server 2008 R2 express edition DB (64 bit).
3. It seems like server machine has both 32bit and 64bit drivers installed on it. Please refer attached driverdetails.jpg file for more details.
Thanks

Hi did you referred this :
ODBC call <SQLDriverConnect> for data source <MyComputer\SQLServer2008R2> failed: <[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.>. Notify Customer Support.

Can't select char type columns using ODBC link to SQL Server 2K

I have set up a db link using hsodbc from 8.1.7 to SQL Server 2000. I can select numeric and date columns from the
SQL Server table with no problem. But any character datatype (nchar or nvchar) column name included in the query
returns an ORA-00904 ("invalid column name"). I know the column names are valid for SQL Server and can access
these columns via EXCEL using the same user id and data source that is used for the link. I don't have a clue as to why ORACLE can't "see" the character type columns. Following is the hs trace file (HS_FDS_TRACE_LEVEL = debug) generated for "select assay_name from bio_assay@sqlsrvl":
FRIDAY SEP 05 2003 10:39:47.674
(0) hoagprd(2); Entered.
(0) [Generic Connectivity Using ODBC] version: 2.0.4.0.0010
(0) connect string is:
(0) YEAR2000_POLICY=-1;CTL_DEBUG=T;CONSUMER_API=1;SESSION_BEHAVIOR_FLAGS=4;PARSER_-
(0) DEPTH=2000;EXEC_FLAGS =
(0) 131080;defTdpName=SQLSRVL;binding=(SQLSRVL,ODBC,"LIBERTY");
(0) ORACLE GENERIC GATEWAY Log File Started at 05-Sep-03 10:39:47
(0) Class version: 65
(0) hoagprd(2); Exited with retcode = 0.
(0) hoainit(3); Entered.
(0) hoainit(3); Exited with retcode = 0.
(0) hoalgon(7); Entered. name = XXXXXXXXXXX.
(0) Created new ODBC connection (28382608)
(0) Silent DB Function!!
(0) (Last message occurred 4 times)
(0) hoalgon(7); Exited with retcode = 0.
(0) hoaulcp(4); Entered.
(0) hoaulcp(4); Exited with retcode = 0.
(0) hoauldt(5); Entered.
(0) hoauldt(5); Exited with retcode = 0.
(0) hoabegn(9); Entered. formatID = 306206, hoagttid
(0) =XXXXXXXXXXXXXXXXXXXXXXXX, hoagtbid = , tflag = 0, initial = 1
(0) hoabegn(9); Exited with retcode = 0.
(0) hoapars(15); Entered. stmtType = 0, id = 1.
(0) nvOUT (P:\Src\QP\QP_SQTXT.C 55): SELECT * FROM "BIO_ASSAY"
(0) odbc_rec: select * from "BIO_ASSAY"
(0) Silent DB Function!!
(0) nvOUT (P:\Src\QP\QPT2SEXE.C 929):
(0) SELECT "T0000"."WH_ADDED_DATE" AS c00010, "T0000"."ASSAY_MODIFIED_TIME" AS c0009, "T0000"."ASSAY_CREATED_TIME" AS c0008, "T0000"."ASSAY_DATE_COMPLETED" AS c0007, "T0000"."ASSAY_DATE_PLANNED" AS c0006, "T0000"."ASSAY_DATE_STARTED" AS c0005, "T0000"."ASSAY_STATUS_NO" AS c0004, "T0000"."TIMEFRAME_KEY" AS c0003, "T0000"."TARGET_KEY" AS c0002, "T0000"."ENVIRONMENT_KEY" AS c0001, "T0000"."ASSAY_KEY" AS c0000 FROM "BIO_ASSAY" T0000
(0) nvOUT (P:\Src\QP\QPT2SEXE.C 932):
(0) <<<<<<<<<<<<<<<<<<< Execution Strategy Begin <<<<<<<<<<<<<<<<<<<<<<<<<<<<
(0) Original SQL:
(0) SELECT * FROM "BIO_ASSAY"
(0)
(0)
(0) Accessing Database "SQLSRVL" with SQL:
(0) SELECT "T0000"."WH_ADDED_DATE" AS c00010, "T0000"."ASSAY_MODIFIED_TIME" AS c0009, "T0000"."ASSAY_CREATED_TIME" AS c0008, "T0000"."ASSAY_DATE_COMPLETED" AS c0007, "T0000"."ASSAY_DATE_PLANNED" AS c0006, "T0000"."ASSAY_DATE_STARTED" AS c0005, "T0000"."ASSAY_STATUS_NO" AS c0004, "T0000"."TIMEFRAME_KEY" AS c0003, "T0000"."TARGET_KEY" AS c0002, "T0000"."ENVIRONMENT_KEY" AS c0001, "T0000"."ASSAY_KEY" AS c0000 FROM "BIO_ASSAY" T0000
(0)
(0)
Execution Strategy End >>>>>>>>>>>>>>>>>>>>>>>>>>>>(0) hoapars(15); Exited with retcode = 0.
(0) hoaopen(19); Entered. id = 1.
(0) hoaopen(19); Exited with retcode = 0.
(0) hoadscr(16); Entered. id = 1.
(0) hoastmt(195); Array fetch size is: 1.
(0) ------ hoadscr() -------:
(0) hoadamsz: 11, hoadasiz: 11, hoadambr: 1, hoadabrc: 1
(0) row 0 - hoadambl: 20, hoadadty: 134, hoadaprc: 19, hoadacst: 0
(0) row 0 - hoadascl: 0, hoadanul: 0, hoadanml: 9, hoadanam: ASSAY_KEY, hoadabfl:
(0) 20, hoadamod: 0
(0) row 1 - hoadambl: 20, hoadadty: 134, hoadaprc: 19, hoadacst: 0
(0) row 1 - hoadascl: 0, hoadanul: 0, hoadanml: 15, hoadanam: ENVIRONMENT_KEY,
(0) hoadabfl: 20, hoadamod: 0
(0) row 2 - hoadambl: 20, hoadadty: 134, hoadaprc: 19, hoadacst: 0
(0) row 2 - hoadascl: 0, hoadanul: 1, hoadanml: 10, hoadanam: TARGET_KEY,
(0) hoadabfl: 20, hoadamod: 0
(0) row 3 - hoadambl: 20, hoadadty: 134, hoadaprc: 19, hoadacst: 0
(0) row 3 - hoadascl: 0, hoadanul: 0, hoadanml: 13, hoadanam: TIMEFRAME_KEY,
(0) hoadabfl: 20, hoadamod: 0
(0) row 4 - hoadambl: 2, hoadadty: 7, hoadaprc: 5, hoadacst: 0
(0) row 4 - hoadascl: 0, hoadanul: 1, hoadanml: 15, hoadanam: ASSAY_STATUS_NO,
(0) hoadabfl: 2, hoadamod: 0
(0) row 5 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 5 - hoadascl: 0, hoadanul: 1, hoadanml: 18, hoadanam: ASSAY_DATE_STARTED,
(0) hoadabfl: 7, hoadamod: 0
(0) row 6 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 6 - hoadascl: 0, hoadanul: 1, hoadanml: 18, hoadanam: ASSAY_DATE_PLANNED,
(0) hoadabfl: 7, hoadamod: 0
(0) row 7 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 7 - hoadascl: 0, hoadanul: 1, hoadanml: 20, hoadanam:
(0) ASSAY_DATE_COMPLETED, hoadabfl: 7, hoadamod: 0
(0) row 8 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 8 - hoadascl: 0, hoadanul: 0, hoadanml: 18, hoadanam: ASSAY_CREATED_TIME,
(0) hoadabfl: 7, hoadamod: 0
(0) row 9 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 9 - hoadascl: 0, hoadanul: 1, hoadanml: 19, hoadanam: ASSAY_MODIFIED_TIME,
(0) hoadabfl: 7, hoadamod: 0
(0) row 10 - hoadambl: 0, hoadadty: 0, hoadaprc: 0, hoadacst: 0
(0) row 10 - hoadascl: 0, hoadanul: 0, hoadanml: 13, hoadanam: WH_ADDED_DATE,
(0) hoadabfl: 0, hoadamod: 0
(0) hoadscr(16); Exited with retcode = 0.
Note, the query I entered doesn't appear and I never entered the query "select * from bio_assay" - it appears that this is
automatically generated by the hsodbc process and raises other questions (like wouldn't this return a lot of unneeded
data ?). It also appears that the "select * from bio_assay" gets translated somehow into a select statement listing each column - however, non of the columns listed are character type columns like assay_name.
Does this make sense to anyone? Any ideas ? HELP !

Remote view gives the same error. I think the problem has to do with nchar and nvchar fields. It seems that the hsodbc agent issues a "select * from bio_assay" at the beginning of the session (see above trace).
0) odbc_rec: select * from "BIO_ASSAY"
(0) Silent DB Function!!
(0) nvOUT (P:\Src\QP\QPT2SEXE.C 929):
(0) SELECT "T0000"."WH_ADDED_DATE" AS c00010, "T0000"."ASSAY_MODIFIED_TIME" AS c0009, "T0000"."ASSAY_CREATED_TIME" AS c0008, "T0000"."ASSAY_DATE_COMPLETED" AS c0007, "T0000"."ASSAY_DATE_PLANNED" AS c0006, "T0000"."ASSAY_DATE_STARTED" AS c0005, "T0000"."ASSAY_STATUS_NO" AS c0004, "T0000"."TIMEFRAME_KEY" AS c0003, "T0000"."TARGET_KEY" AS c0002, "T0000"."ENVIRONMENT_KEY" AS c0001, "T0000"."ASSAY_KEY" AS c0000 FROM "BIO_ASSAY" T0000
Apparently, the list of fields that is returned from the "select *" does not include any of the nchar or nvchar type columns. After this initial "select *" the oracle server only looks at the initial list of columns and gives an "invalid column" error for any fields that are not in this initial list. So the question is: how do I make the hsodbc agent see the nchar/nvchar type fields and include them in the initial list ? I've tried setting the HS_NLS_LANGUAGE and HS_NLS_NCHAR parameters but these seem to have no effect.
Any clue as to what's going on ?

Issue using ODBC CALL

Similar Messages

Maybe you are looking for