I vaguely recall facing a similar issue in the past and, also vaguely,
remember that the only option was to set a login trigger for the OEM
database user that executes the alter session statements.
This was a few years ago and a better solution may be available nowadays
but this one may help in this case.
[image: Pythian] <http://www.pythian.com/>
*Jose Rodriguez* | Oracle Database Consultant | [image: LinkedIn]
<https://www.linkedin.com/company/pythian>
*t* +1 613 565 8696 <+1+613+565+8696> *ext.* 1393
*m* +34 607 55 49 91 <+34+607+55+49+91>
jrodriguez2@xxxxxxxxxxx
*www.pythian.com* <https://www.pythian.com/>
[image: Pythian] <https://www.pythian.com/email-footer-click>
On Wed, 19 Sep 2018 at 19:37, Jeffrey Beckstrom <jbeckstrom@xxxxxxxxx>
wrote:
We have an application that alters nls settings at connection time.
Indexes on character columns are built with these revised nls settings. If
we do an explain plan without setting the applicable nls settings, indexes
are not used. The indexes are only selected by the explain plan if an alter
session is first done to set the application settings. My question is, we
use EM 13C with the diagnostic and tuning packs. How can we make EM 13C use
the correct nls settings before running the tuning advisor? The nls
settings dynamically set are:
alter session set nls_comp = LINGUISTIC;
alter session set NLS_SORT = PUNCTUATION;
Jeffrey Beckstrom
Lead Database Administrator
Information Technology Department
Greater Cleveland Regional Transit Authority
1240 W. 6th Street
Cleveland, Ohio 44113
