Re: Hunting down (possible) memory leak in DBD::Oracle

On 2017-12-19 20:55:30 +0000, Fennell, Brian wrote:
> And, also with the log level set to 15 here are the LAST 200 lines
[...]
>     -> fetchrow_array for DBD::Oracle::st (AAA::DBI::Connection::st=HASH(0x3abd310)~0x39f75f0) thr#24d4010
>         dbd_st_fetch 6 fields...
>         dbd_st_fetched 6 fields with status of 0(SUCCESS)
>         field #1 with rc=0(OK)
> 
>                 3abd340 (field=0): '1105427'
>         field #2 with rc=0(OK)
> 
>                 3abd340 (field=1): '1268254'
>         field #3 with rc=0(OK)
> 
>                 3abd340 (field=2): 'sampl...'
>         field #4 with rc=25196(UNKNOWN RC=25196))
>         OCIErrorGet(3b535c8,1,"<NULL>",7ffd7b72b7cc,"ORA-01403: no data found
> ",1024,2)=SUCCESS
>         OCIErrorGet after ORA-25196 error on field 4 of 6, ora_type 2 (er1:ok): -1, 1403: ORA-01403: no data found
> 
>         OCIErrorGet(3b535c8,2,"<NULL>",7ffd7b72b7cc,"ORA-01403: no data found
> ",1024,2)=NO_DATA
>     -- HandleSetErr err=1403, errstr='ORA-01403: no data found (DBD ERROR: ORA-25196 error on field 4 of 6, ora_type 2)', state=undef, undef
> 
>                 3abd340 (field=3): undef

Can you check the actual contents of any rows in tableA with
field1=1268254 and field2='sampl...'? The error occurs in field3 which
is numeric, but it's adjacent to field4 which is VARCHAR2(4000). I
wonder if an overflow is possible if field4 is actually close to 4000
characters and it is expanded further by character encoding. Which
raises the next question: What are the database and client encodings set
to?

        hp

-- 
   _  | Peter J. Holzer           | I think we need two definitions:
|_|_) | WSR - Softwaredevelopment | 1) The problem the *users* want us to solve
| |   | und Projektunterstützung  | 2) The problem our solution addresses.
__/   | [email protected]             |    -- Phillip Hallam-Baker on spam

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRBxFQuhqmAWMsX6L0x0V9Brrg8LAUCWjo5mQAKCRAx0V9Brrg8
LLjnAJ9Y4FE/UtuopTMMdydgQEhOdV5KXgCgmnYIRE4m73daYI/C8oMgwPmoepg=
=WPzk
-----END PGP SIGNATURE-----