User Password case sensitivity issue.

Hi,
I have been migrated users from EBS to OID, but having some issues like some existing users password in EBS are in Capital letters but when they connect with SSO the same password not accepted, but users can connect same password in small letters.
How I can solve this issue????????
Senario:
1: Existing EBS User:(Before integration of OID+SSO), users are directly connecting with EBS.
User Name: HINA.SARWAR-----------(Not case sensitive)
Password: ABCDEF -----------( Case sensitive)
2: Existing EBS User:(After integration of OID+SSO), user are connecting via SSO.
Eexpected behavior is that users should logon with above pass "ABCDEF", but they cannot.
eg:-
Cannot connect as:
User Name: HINA.SARWAR -----------(Not case sensitive)
Password: ABCDEF -----------( Case sensitive)
Can connect as:
User Name: HINA.SARWAR -----------(Not case sensitive)
Password: abcdef -----------( Case sensitive)
thx

Hi,
The solution to your problem is here at metalink:
Password Case Sensitivity Lost During Extract And Import From EBS to OID [ID 951170.1]
regards

Similar Messages

Oracle 11G password case sensitive option is not working.

Hello,
I am facing problem in Oracle 11G. I installed and created a database. I disabled password case sensitive option by setting it to false (Pls see the below output). but case sensitive option is not disabled and i am not able to logon using the lower case password.
SQL> connect sys/<pwd in lower case>@<connect string> as sysdba;
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> connect sys/<pwd in uppper case>@<connect string> as sysdba;
Connected.
SQL> show parameter SEC_CASE_SENSITIVE_LOGON
NAME TYPE VALUE
sec_case_sensitive_logon boolean FALSE
Any idea.... should i open the case in the metalink ?
With Regards
Hemant Joshi.

Can you execute:
SQL> select USERNAME, PASSWORD_VERSIONS from dba_users where username = 'SYS';Have you tried reseting the sys password? When you create the password file by default the passwords stored on it are case sensitive, maybe you also need to rebuild it...
Enrique
PS. See Note:429465.1 +11g R1 New Feature : Case Sensitive Passwords and Strong User Authentication+
Edited by: Enrique Orbegozo on Oct 15, 2008 1:20 AM

Case Sensitivity Issue with Latin Characters

Hi,
The Latin Character that i am talking abt is "i",
I am trying to provide in my application the support for Azeri-Latin(Turkish family) Characters,
That is the display and the orientation of characters is perfectly fine throughout the flow of application.
But now there is a problem when selecting a data from DB using like constraint in where clause... The issue has been elaborated below...
From the set of characters there are two character in which i am facing Case Sensitivity issue...
They are as,
i ---> the capital of same is ---> İ
ı ---> the capital of same is ---> I
now in english character mapping,
for i ---> the capital is ---> I
So, this is creating an issue...
Now the test i have done is as follows,
I created a table as,
Create Table CS
CS1 VARCHAR2(20)
Following is the data that is inserted in the table,
Insert into CS values('İ');
Insert into CS values('i');
Insert into CS values('I');
Insert into CS values('ı');
now i am running the following query,
Select * from CS where lower(CS1) like lower('%&a%');
for characters "i","İ","I" it returns 3 rows, that are,
i
İ
I
and for character ı it only returns,
ı
ideally for characters "i" & "İ" should be mapped with each other and "ı" & "I" should be mapped with each other respectively.
But that is not the case.
I am using Oracle 10g
my NLS_database_parameters are as follows,
PARAMETER     VALUE
NLS_LANGUAGE     AMERICAN
NLS_TERRITORY     AMERICA
NLS_CURRENCY     $
NLS_ISO_CURRENCY     AMERICA
NLS_NUMERIC_CHARACTERS     .,
NLS_CHARACTERSET     AL32UTF8
NLS_CALENDAR     GREGORIAN
NLS_DATE_FORMAT     DD-MON-RR
NLS_DATE_LANGUAGE     AMERICAN
NLS_SORT     BINARY
NLS_TIME_FORMAT     HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY     $
NLS_COMP     BINARY
NLS_LENGTH_SEMANTICS     BYTE
NLS_NCHAR_CONV_EXCP     FALSE
NLS_NCHAR_CHARACTERSET     AL16UTF16
NLS_RDBMS_VERSION     10.2.0.1.0
and at client i m using,
NLS_LANG = .AL32UTF8
any help on this issue will be appreciated,
Thanks & Regards,
Pratik

I'm not fully understand your question but I guess you may need to set up NLS_LANGUAGE, NLS_TERRITORY db parameters and client NLS_LANG.
eg client NLS_LANG=TURKISH_AZERBAIJAN.AL32UTF8 and db parameters NLS_LANGUAGE=TURKISH, NLS_TERRITORY=AZERBAIJAN
Full list of supported languages, locales see [Oracle® Database Globalization Support Guide local data subpage|http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/applocaledata.htm]
or tip2: check this: ALTER SESSION SET NLS_COMP=LINGUISTIC;
Edited by: Kecskemethy on Mar 24, 2009 3:14 AM
or you need something like this:
Example 5-16 Matching with the Base Letter Operator [==]
Expression: r[[=e=]]sum[[=e=]]
Matches:
resume<<
résumé<<
résume<<
resumé<<Oracle SQL syntax: SQL> SELECT col FROM test WHERE REGEXP_LIKE(col,'r[[=e=]]sum[[=e=]]');Edited by: Kecskemethy on Mar 24, 2009 3:20 AM

Case sensitive issue CF7 & SQL 2005

I had to rebuild a database from a backup recently. Now I am having a case sensitive issue in my queries that I did not have before.
The following use to work with Rockmart in lowercase even though Rockmart was in the table as all uppercase like so ROCKMART.
<cfquery name="updateAreas" datasource="mySource">
   UPDATE Property
   SET AR = 3610
   WHERE City = 'Rockmart'
</cfquery>
The above has stopped working now the query must specify ROCKMART because it is in the table in all upper case.
My database option is set to SQL_Latin1_General_CP1_CI_AS
Any ideas.
Many thanks for you help.
Brian

A collation can be specified at the server, database, and column level in SQL server. The column collation will take precedence over the database collation. Check that the collation for the column is case-insensitive. You can use the query below to get the column's collation.
SELECT COLUMN_NAME, COLLATION_NAME
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'Property'
    AND COLUMN_NAME = 'City'
You can get info on the collations supported by SQL Server at:
http://msdn.microsoft.com/en-us/library/ms144250%28SQL.90%29.aspx
You can change a column's collation if you need to, but you should be sure that this will not affect any other applications which query the same data. Another option is to specify the desired collation in your query as suggested by glynjackson.
http://msdn.microsoft.com/en-us/library/ms190920%28SQL.90%29.aspx

Making user account logins/passwords case sensitive?

Hi, just a quick question. Is it possible to make user account login/passwords be case sensitive? At the moment they are case insensitive.
Thanks :)

You can make only user account login case sensitive but not password.
SQL> create user "Test" identified by "tEST";
User created.
SQL> grant create session to "Test";
Grant succeeded.
SQL> conn test/test
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> conn "Test"/test
Connected.
SQL>

Oracle Passwords CASE Sensitive

My Oracle 9i DB is not CASE sensitive on my passwords. I can not find any info on what parameter I can change to make it case sensitive.
All documents I find on net tell me that Oracle is CASE sensitive by default why are my passwords not?
Thanks in advance for any and all help,
David Miller

The topic they are typically were talking about being case sensitive is data insdie oracle db...
Also saw discussiona on use of " " (double quotes) on the ALTER USER command and password to make it specific to case.. Not sure where that came from at all...
Miller

Local net users - usernames case sensitive

I am facing an annoying issue with our WLC's 5508.We have configured some local accounts - local net users and we found out that usernames are case sensitive.For example when i setup an account with username:TEST and the then try to login with username:test i get authentication failure..
I thought that only the admin accounts were case sensitive.
Has anyone else faced this problem?Is there any solution for this as i have already configured 60 local accounts.
Thank you in advance.

#Management Usernames are case sensitive.
#Local net user seem to be case sensitive per below bug, however it is a old one on 4.0.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsg72444
*for local netuser, Does WLC allows to create same usernames like this - Apple, APPLE, AppLe. If allowed then at this point its considered that wlc allows to create case insensitive users for local netusers. Else if only Apple is allowed then it is case sensitive for user creation.
*Now try to login like - apple, aPPLE and also like Apple, APPLE, AppLe.
*Share the result along with the tested wlc code for conclusion. Let see what works and doesn't.

Column header sort - case sensitivity issue

Hi guys,
I'm having an issue with the built in column sorting when you click the headers on a report. Basically case sensitivity is taken into account and capital letters get sorted before smaller case letters, for example:
Cats
Dogs
Zebra
ants
bears
How would I be able to fix this built in sort?
Thanks,
Luis

Luis,
See if Denes's solution helps: Report sort by column header question .
Scott

Search User Page - Case Sensitivity Problem

Hi,
While searching users according to the criterias like user's firstname or lastname, the search is case sensitive.
Is there a way to make incase sensitive search?
Thanks.

I would say a no for it because at the back-end the findUsers() API is getting called for which the value is a String Object. So its always case insensitive according to me.

UTL_FILE & User Input: Case Sensitive File Names

Hi.
I'm trying to reduce problems due to the whether the user uses upper or lower case or combo of them in entering file names.
Scenario is:
Existing file to be read: Orig_File.Txt (file name changes daily)
Output to be saved into file: RESULTS_FILE.TXT
In response to PL/SQL commands (please see below), the user enters:
ORIG_FILE.TXT and Results_FILE.txt
as the Input & Output file names. The problem is that the input file has been saved using Upper and Lower case and I get back a file not found error.
Is there a way to call a file with is a different case than the input?
Thanks.
Current commands are:
In_File          UTL__File.file_type;
Out_File          UTL__File.file_type;
Curr_Line     VarChar2(2000);
BEGIN
In_File := UTL__File.fopen('UTIL_FILE_DIR', '&input_file', 'R', 2048);
Out_File := UTL__File.fopen('UTIL_FILE_DIR', '&output_file', 'W', 2048);
LOOP
BEGIN
UTL__File.get_line(In_File, Curr_Line, 2048);
.......

A shell script would typically issue something along the lines of
newfile=$(ls -C1 | grep -i "\<${filename}\>")although of course it is possible for this to match multiple filenames, so it would have to check for that scenario and report it as an error. possibly you could call a shell script like this from PL/SQL via Java or DBMS_SCHEDULER. Good luck with that though.

Oracle 11g database & OBIEE 10g user id case sensitivity

Hi,
Previously we used to point OBIEE to 10g database and the following query used to return data. But now we have database upgraded to 11g R2. Is there a way to make the 11g R2 database case insensitive and make the following query return results? Here when EMP_LOGIN = upper(bmiller) query is working, but not when EMP_LOGIN = bmiller.
select T32660.X_DISTRICT as c1,
count(distinct case when T32385.OPTY_WID > 0 then T32385.OPTY_WID end ) as c2
from
W_POSITION_H T37785 /* Dim_W_POSITION_H */ ,
W_POSITION_D T36585 /* Dim_W_POSITION_D */ ,
W_EMPLOYEE_D T32660 /* Dim_W_EMPLOYEE_D */ ,
W_OPTY_D T31547 /* Dim_W_OPTY_D */ ,
W_ORG_D T31796,
W_REVN_F T32385 /* Fact_W_REVN_F */
where ( T32385.PR_TEAM_POS_WID = T36585.ROW_WID
and T31547.ROW_WID = T32385.OPTY_WID
and T31796.ROW_WID = T32385.PR_ACCNT_WID
and T32385.PR_TEAM_EMP_WID = T32660.ROW_WID
and T36585.ROW_WID = T37785.SUB_POSITION_WID
and T37785.EMP_LOGIN = upper('bmiller')
and T37785.EMP_LOGIN = 'bmiller' )
group by T32660.X_DISTRICT
order by c1
Thanks
MNRK

If this query was working in the old system, my assumption is that something was changing your session's NLS_COMP to Linguistic. If OBIEE isn't issuing that ALTER SESSION in a login script, the next most likely scenario would be a login trigger that was issuing the ALTER SESSION when the OBIEE user logged in. That trigger would have remained in place had you used the DBUA to upgrade. If you did an export and import, however, it's possible that you didn't export the login trigger.
Justin

Case sensitivity issue with hostname and sessions

I'm running into a strange issue with mixed cases and my webservice.
I have a JAX-WS service running at my host http://sumac.us.oracle.com/interlace/services/AdminService. When I connect my JAX-WS client to this, using the same URL, I have no problems and the session management code seems to work.
However, if I set my JAX-WS client to connect to http://SUMAC.us.oracle.com/interlace/services/AdminService, the session management doesn't work any more. It seems that the client does not send the JSessionID cookie back to the server.
I did notice that my webservice sends the following Set-Cookie header and the host that is sent in the original request is SUMAC.us.oracle.com
Set-Cookie: JSESSIONID=vWjmMJwJXVLf2LBwYN82rxpqbwyKPP4SpD8kd7zLYVkLDJG2Bnnp!-234350174; path=/interlace; HttpOnly
I'm wondering if anyone has run into this. I'm just using the standard JAX-WS client which is generated from a WSDL file. Let me know if this is sufficient information and I'll add more if necessary.
Thanks,
Anil

I tracked this down and the issue has to do with the CookieJar class used to store the cookie information. It seems that this has already been patched in the JAX-WS 2.2.x line, but I believe that JDK 1.6 u21 uses a version of the 2.1.x branch.
The JAX-WS issue number is 834.

Making user account logins case sensitive?

Hi, just a quick question. Is it possible to make a user account login name case sensitive? Currently I can log on using upper or lower case for the login name however I would rather only the exact login name could be used.
Thanks

I had already answered with example.
Re: Making user account logins/passwords case sensitive?

Installing to a case-sensitive fs

When I did my original 10.4 install, I opted
for a case-sensitive boot disk. I come from a
UNX background, and am using UNIX utilities
from darwin ports and my own UNIX files in
a cvs tree. It seemed natural to use a case-
sensiticve fs, since I would be using a lot
of files ad applications that are case
sensitive.
Enter my girlfriend's graphics applications.
After fighting with Adobe CS2 for hours, I
cloned my data drive and re-partitioned it
to have a 50 GB case-insensitive partition,
just for applications. All was good with the
world again.
Enter the next of her applications, Macromedia
Flash Pro. One of the same two errors as
the Adobe suite was getting [ 1008:17, -4 in
thie case ]. Looks like Flash writes to /Users,
not just /Applications, so I think I am
getting case-sensitive issues again.
I attempted to symlink the dir onto my
case-sensitive drive, but the installer
did not recognized the symlink as a
directory and prompted me to delete it.
I've learned two things from this experience:
1. A case-sensitive boot drive is near-useless
for commercial applications.
2. The people who write Mac installers are
very, very poor progrsmmers. Cavalier
attitude towards case, refusal to handle
symlinks ... someone spent too much time in
the primitive world of OS 9.
OK, on to the question...
I've repaired permissions, googled the error code,
verified the hdd, even sampled the installed to find
out it errored out during a file read.
I am not going to clone my boot drive and reinstall
onto a case-insensitive partition.
Is there any sane way of fixing this? Maybe a
wrapper daemon for crippled programs that are
incapable of handling a case-sensitive fs?

heya,
Yeah, I was afraid of that. Kinda hoping there would be
some crazy kext hack like you'd find in the linux/bsd
world. Hmm, could be an interesting project actually,
a case-insensitizer with an application white-list.
Well, I got most everything installed after some
trickery. Had to symlink /Users/Shared into a
case-insensitive partition, which fooled the
installer long enough for it to crash later
on the example files, then changed it back to
a dir.
Kept the error dialog open and copied what had
managed to install, hit ok on the error, and
let it clean up after itself. I now have
incomplete but functional installations of
flash pro and dreamweaver.
Now trying to find a way to pull the files
out of macromedia's installer. Looks like a
typical archive; has the unusual header SVCT,
which I cannot find documentation for [yet],
and file(1) identifies it only as 'data'. If I
can find some docs describing the file format I'm
golden.
Hard not to knock the developers though. In the
month I've been using OS X apps, I've seen many
things that would be a firing offense where I
work

How to retrieve column names in a query in a case sensitive way

Given a query, I want to extract all the column names/aliases in the query in a case-sensitive way.
When I use dbms_sql.describe_columns() or java.sql.ResultSetMetaData classes getColumnName() or getColumnLabel()
it returns the columns name ONLY in Upper case.
My application needs to extract the column names in the same case as it appears in the query string.
Is there any API to get this without parsing the SQL query string?
Thanks
PS: The dbms_sql.describe_columns() returns the column name in upper case.
declare
IS
l_column_recs DBMS_SQL.DESC_TAB;
l_cur NUMBER;
l_column_count NUMBER;
BEGIN
l_cur := dbms_sql.open_cursor;
dbms_sql.parse(l_cur, 'select target_type from targets', dbms_sql.NATIVE);
dbms_sql.describe_columns(l_cur, l_column_count, l_column_recs);
FOR i IN l_column_recs.FIRST..l_column_recs.LAST
LOOP
dbms_output.put_line(l_column_recs(i).col_name);
end loop;
end;
/

As far as the result set is concerned, though, the column name is in all upper case. If you query the data dictionary, you would see that the TARGET_TYPE column in the TARGETS table is stored in upper case.
The way Oracle works is that column names that are not enclosed in double-quotes are converted to upper case in the data dictionary and elsewhere and then Oracle looks for the column name in the table definition. That is what allows Oracle to have case-insensitive identifiers unless a user specifies case-sensitive identifiers by enclosing the identifier in double quotes.
If you changed the query to be
SELECT target_type as "target_type"
FROM targetsOracle should report the alias in a case sensitive fashion because you've now indicated that the alias should be treated as case sensitive.
Justin

User Password case sensitivity issue.

Similar Messages

Maybe you are looking for