Solved TD-18469: ORACLE LOGGING - Param. names 1st char only

Post found bugs and possible workarounds.
GabrielCifci

TD-18469: ORACLE LOGGING - Param. names 1st char only

Post by GabrielCifci » 03 Oct 2012, 09:38

When doing an SQL-log, the String parameters aren't fully logged anymore. Only the first char is showen. See below the log and the example file attached .
The log file is also NOT unicode but ANSI format.

THIS PART BECOMES FROM TD1.5
******************************
10/2/12 10:25:11 1>
10/2/12 10:25:11 1> [execute]
10/2/12 10:25:11 1> [1] BLACKBOX
10/2/12 10:25:11 1> [2] CHECKBETREKK

10/2/12 10:25:11 1> [3] 8177
10/2/12 10:25:11 1> [fetch]
10/2/12 10:25:11 1> [end of fetch]
10/2/12 10:25:11 1> [commit]
10/2/12 10:25:11 1> [disconnect]

THIS PART BECOMES FROM TD6.1
******************************
10/2/12 10:26:04 1> [execute]
10/2/12 10:26:04 1> [1] B
10/2/12 10:26:04 1> [2] C

10/2/12 10:26:04 1> [3] 8177
10/2/12 10:26:04 1> [bind] position = 1, buffer size = 16, datatype = 96
10/2/12 10:26:04 1> [bind] position = 2, buffer size = 24, datatype = 96
10/2/12 10:26:04 1> [bind] position = 3, buffer size = 4, datatype = 1
10/2/12 10:26:04 1> [fetch]
10/2/12 10:26:04 1> [end of fetch]
10/2/12 10:26:04 1> [commit]
10/2/12 10:26:04 1> [disconnect]
You do not have the required permissions to view the files attached to this post.

Jeff Luther

Re: TD-18469: ORACLE LOGGING - Param. names 1st char only

Post by Jeff Luther » 03 Oct 2012, 20:18

I'll need more details as to how you are testing. I'm using SB 11.6.2 local ISLAND that comes with TD v6.1 SP2, and see that while the LOG file -- I'll attach mine -- is indeed in ANSI format, my bind values display the full values:
10/03/12 12:13:08 3> 0[CHAR] (pdt=32, len=4)
10/03/12 12:13:08 3> 1[VARCHAR] (pdt=32, len=7)

(I couldn't run your test as I don't have that par table or view...) My settings:
SB 11.6.2
SB SQL.INI file settings:
[dbntsrv]
...
log=c:\dbsrv.log

What I did: Start the DB, set Level = 4 and Process Activity data will be saved to the LOG file.

I suggest you try a query that uses the SYS tables somehow, as I did. Then your test can be run against any SB server without regard to any user-defined table. (BTW, I notice your LOG file format is different. What SB version are you running??)

BTW #2, this would seem to actually be a SQLBase issue, not a TD issue. TD doesn't manage the LOG file. I'll leave this thread here for the moment but we have a SQLBase section for issues such as this.
You do not have the required permissions to view the files attached to this post.

GabrielCifci

Re: TD-18469: ORACLE LOGGING - Param. names 1st char only

Post by GabrielCifci » 04 Oct 2012, 09:25

Hi Jeff,

Thanks for your respons.

I'm using oracle 11.g as database. Probably. that's way the log is diffrent then yours. The table I use in the select is an user defined table (not a system table)
I add this topic here because, it has nothing to do with SQLBase, I quest it is a router/dll problem of TD client.
FYI: The same attached test application is working fine on TD1.5.

See the ini file I use:

[win32client.dll]
comdll=sqlora32

[ORAGTWY]
longbuffer=32767
substitute=SYSSQL.,
substitute=",
substitute=SYSSQL.,
substitute=",
substitute=SYSSQL.,SYS.
fetchrow=20
nodefparse=yes
...
[odbcrtr]
odbctrace=off
odbctracefile=sql.log

[win32client.ora32]
log=c:\SQLlog.txt

Jeff Luther

Re: TD-18469: ORACLE LOGGING - Param. names 1st char only

Post by Jeff Luther » 04 Oct 2012, 18:28

The table I use in the select is an user defined table (not a system table)
Yes, I know :) And I couldn't run your test because you didn't include a CREATE TABLE + a couple INSERTs in the TD code... So to see if this was a generic issue, I used a SQLBase system table -- that way anyone could run it with SB and wouldn't need a SQL script or other code to add a user-defined table for testing.

With my own Oracle test, now I can repro. this:
...
10/4/12 10:15:41 1> [1] T
10/4/12 10:15:41 1> [2] S
...

I will report this. New defect added: TD-18469

Update: and I just see that management has set fix versions for this defect to be next SPs: 6.0 SP8, 6.1 SP3

Return to “Bug Reports”

Who is online

Users browsing this forum: [Ccbot] and 0 guests