- 3,715,654 Users
- 2,242,820 Discussions
- 7,845,479 Comments
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 467 General Database Discussions
- 22 Multilingual Engine
- 487 MySQL Community Space
- 3 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 416 SQLcl
- 42 SQL Developer Data Modeler
- 184.8K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 8 DevOps
- 3K QA/Testing
- 247 Java
- 5 Java Learning Subscription
- 10 Database Connectivity
- 66 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 18 Programs
- 125 LiveLabs
- 30 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 10 Español
- 1.9K Japanese
- 2 Portuguese
What factors influence language used by ODP.NET ?
I am struggling to find possible reasons the client language is changing in a report and trying to determine if it can be ODP.NET related.
I will try to explain the situation as best I can and hopefully some of you wonderful members will have some suggestions of where to look for answers.
Here is the test case we are running (to the best of my ability to describe).
Developers create a report using Microsoft Visual Studio that will be executed against and Oracle 12.1 database.
The report is scheduled on Microsoft SSRS server to run every 30 minutes.
The client connect appears to be "ODP.NET, Managed Driver"
The client language in the report occasionally changes.
The following statement is the source of the report.
SYS_CONTEXT ('USERENV', 'IP_ADDRESS') "IP Address",
SYS_CONTEXT ('USERENV', 'LANG') CLIENT_LANG,
regexp_substr(SYS_CONTEXT ('USERENV', 'LANGUAGE'),'[^.]+',1,1) CLIENT_NLS,
SYS_CONTEXT ('USERENV', 'HOST') HOST,
SYS_CONTEXT ('USERENV', 'TERMINAL') TERMINAL,
SYS_CONTEXT ('USERENV', 'SESSION_USER') USER_NAME,
TO_CHAR(SYSDATE, 'MONTH DD, YYYY, HH24:MI:SS') DATE_TIME,
FROM v$session_connect_info where sid=sys_context('USERENV','SID');
The CLIENT_LANG in this report does change once in a while.
This is a scheduled report so I can not figure out what would cause the change.
I am not a developer (just a DBA) but I have searched through the documentation and the only thing I find is that ODP.NET is NOT NLS_LANG sensitive (whatever that means)
I would appreciate any thoughts on....
What kind of factors might be related to ODP.NET and the client language being used to query the database?
Is it possible to "force" ODP.NET to use AMERICAN to query the database?