#30630: MemoryError appears when using cx-Oracle 7.2 on Oracle 12c (12.1.0.2.0)
with Python 3.7 (3.7.4).
-------------------------------------+-------------------------------------
Reporter: Alexandru Rudi | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: oracle cx-oracle | Triage Stage:
python-3.7 | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Alexandru Rudi):
* status: new => closed
* resolution: => invalid
Comment:
Replying to [comment:8 Jani Tiainen]:
> Could you please check NLS settings from your db:
> {{{#!sql
> SELECT * FROM NLS_DATABASE_PARAMETERS;
> SELECT * FROM NLS_INSTANCE_PARAMETERS;
> }}}
From NLS_DATABASE_PARAMETERS:
||= PARAMETER =||= VALUE=||
||NLS_RDBMS_VERSION|| 12.1.0.2.0||
||NLS_NCHAR_CONV_EXCP|| FALSE||
||NLS_LENGTH_SEMANTICS|| BYTE||
||NLS_COMP|| BINARY||
||NLS_DUAL_CURRENCY|| $||
||NLS_TIMESTAMP_TZ_FORMAT|| DD-MON-RR HH.MI.SSXFF AM TZR||
||NLS_TIME_TZ_FORMAT|| HH.MI.SSXFF AM TZR||
||NLS_TIMESTAMP_FORMAT|| DD-MON-RR HH.MI.SSXFF AM||
||NLS_TIME_FORMAT|| HH.MI.SSXFF AM||
||NLS_SORT|| BINARY||
||NLS_DATE_LANGUAGE|| AMERICAN||
||NLS_DATE_FORMAT|| DD-MON-RR||
||NLS_CALENDAR|| GREGORIAN||
||NLS_NUMERIC_CHARACTERS|| .,||
||NLS_NCHAR_CHARACTERSET|| AL16UTF16||
||NLS_CHARACTERSET|| WE8ISO8859P1||
||NLS_ISO_CURRENCY|| AMERICA||
||NLS_CURRENCY|| $||
||NLS_TERRITORY|| AMERICA||
||NLS_LANGUAGE|| AMERICAN||
From NLS_INSTANCE_PARAMETERS:
||= PARAMETER =||= VALUE=||
||NLS_LANGUAGE|| AMERICAN||
||NLS_TERRITORY|| AMERICA||
||NLS_COMP|| BINARY||
||NLS_LENGTH_SEMANTICS|| BYTE||
||NLS_NCHAR_CONV_EXCP|| FALSE||
The rest of the values are (null).
> Also note that following settings takes place in environment before
connection is opened:
> {{{
> NLS_LANG=.AL32UTF8
> ORA_NCHAR_LITERAL_REPLACE=TRUE
> }}}
Can these be configured from settings.py?
> {{{ _output_type_handler }}} is used to properly read numerical values
from db. It shouldn't affect model creation but it has effect when reading
values from db.
>
> Also if you could please try older versions of cx_Oracle just to rule
out that it's some bug in cx_Oracle itself.
Tested with 7.1 and 7.0, both worked without issue, so it seems to be a
regression in cx_Oracle, even though I scanned their changelogs twice and
no mention of a change that would impact this. Thank you for being
understanding and guiding me in the right direction. I will raise a ticket
on their end.
--
Ticket URL: <https://code.djangoproject.com/ticket/30630#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/077.960bcf23383be9a62a970aecc863b7f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
