Trace files Generated with "psdgbt: bind csid () does not match session csid ()" (Doc ID 456351.1)

Last updated on SEPTEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.2 and later
Information in this document applies to any platform.

Symptoms

Database is creating trace files with the following contents

*** SERVICE NAME:(SYS$USERS) 2007-07-16 15:13:39.317
*** SESSION ID:(607.1431) 2007-07-16 15:13:39.317
psdgbt: bind csid (1) does not match session csid (871)
psdgbt: session charset is UTF8
*** 2007-07-16 15:13:39.319
ksedmp: internal or fatal error
Current SQL statement for this session:
begin sys.dbms_application_info.set_module('PL/SQL Developer', :action); end;
----- Call Stack Trace -----
psdgbtds_debug_support
psdgbt
ph2gbi
ph2dr2
ph2drv

Argument/Register addr=0x00000001063CD77C.
Dump of memory from 0x00000001063CD73C to 0x00000001063CD87C
1063CD730                            00000000              [....]
1063CD740 00000000 00000000 00000000 00000000  [................]
    Repeat 2 times
1063CD770 00000000 00000000 00000000 01000000  [................]
1063CD780 01300100 00000130 02000000 2C504C2F  [.0.....0....,PL/]
1063CD790 53514C3A 20436F6D 70696C61 74696F6E  [SQL: Compilation]
1063CD7A0 20756E69 7420616E 616C7973 69732074  [ unit analysis t]
1063CD7B0 65726D69 6E617465 64010000 00013101  [erminated.....1.]
1063CD7C0 00000001 37020000 002F504C 532D3030  [....7..../PLS-00]
1063CD7D0 3535333A 20636861 72616374 65722073  [553: character s]
1063CD7E0 6574206E 616D6520 6973206E 6F742072  [et name is not r]
1063CD7F0 65636F67 6E697A65 64000132 01000000  [ecognized..2....]
1063CD800 02333602 0000002F 504C532D 30303535  [.36..../PLS-0055]
1063CD810 333A2063 68617261 63746572 20736574  [3: character set]
1063CD820 206E616D 65206973 206E6F74 20726563  [ name is not rec]
1063CD830 6F676E69 7A656401 31010000 00013702  [ognized.1.....7.]
1063CD840 0000002F 504C532D 30303535 333A2063  [.../PLS-00553: c]
1063CD850 68617261 63746572 20736574 206E616D  [haracter set nam]
1063CD860 65206973 206E6F74 20726563 6F676E69  [e is not recogni]
1063CD870 7A656400 01310100 00000137           [zed..1.....7]

Changes

Nothing has changed at database side but new users / workstations started to access the database.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms