Case insensitive comparison

Is there a way or setting at instance level by which all character value comparisons can happen in case insensitive manner ( For example "ABC" = "Abc" or = "abc" ) without requiring to use upper or lower functions in every query

No there isn't a way currently. You can create a function based index which improves the performance of case insensitive searches. For example:
SQL> CREATE INDEX case_insensitive_ind ON my_table(NLS_UPPER(empname));
SQL> SELECT * FROM my_table WHERE NLS_UPPER(empname) = 'KARL';

Similar Messages

Case Insensitive Comparison in Oracle 9i

hi all
in Oracle 10g we have the following statement to enable case-INsensitive comparison:
ALTER SESSION SET nls_sort=binary_ai
do we have somthing like this in Oracle 9i to enable case-INsensitive comparison
thnx
Ashu :)

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
JServer Release 9.2.0.7.0 - Production
SQL> create table t as select 'télé' t from dual
union select 'TÉLÉ' from dual
union select 'tele' from dual
union select 'TELE' from dual
union select 'Bebe' from dual;
Table created.
SQL> alter session set nls_comp=ansi;
Session altered.
SQL> ALTER SESSION SET NLS_SORT=GENERIC_BASELETTER;
Session altered.
SQL> select * from t where t='tele';
T
TELE
TÉLÉ
tele
télé

Blank padding in case of nchar columns while case insensitive comparison

hi
i have my database on oracle 9i .
i want case insensitive behaviour so i set nls_comp=ANSi and nls_sort to GENERIC_BASELETTER.
all columns of type character are nchar in my database.
but when i execute a query having a where condition on nchar column blanks are not padded and there is no result ( documentation says lanks are padded while comparisons)..
for e.g select * from area where code='bom' does not return result.
i need to do select * from area where rtrim(code) = 'bom'. (note code is of length nchar(10))
please suggest if here is any solutions for this.

It's always helpful when you have problems if you can provide a concrete example of those problems. For example can you provide something like the following the exhibits the problem?
SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL> CREATE TABLE AREA(CODE NCHAR(10));
Table created.
SQL> INSERT INTO AREA VALUES ('bom       ');
1 row created.
SQL> SELECT * FROM AREA WHERE CODE = 'bom';
CODE
bom
SQL> SHOW PARAMETER NLS_COMP
NAME                                 TYPE        VALUE
nls_comp                             string
SQL> SHOW PARAMETER NLS_SORT
NAME                                 TYPE        VALUE
nls_sort                             string
SQL> ALTER SESSION SET NLS_COMP=ANSI;
Session altered.
SQL> ALTER SESSION SET NLS_SORT=GENERIC_BASELETTER;
Session altered.
SQL> SELECT * FROM AREA WHERE CODE = 'bom';
CODE
bom

How do I make a case-insensitive comparison with PHP?

This is what I have tried so far:
if (strcasecmp($var, "ComparedString") == 0)
$error = 1;
...but it doesn't seem to work.

You are looking to see if they are equal? Your code should
work to set
$error to true/1 if the two are equal. Is it not doing this?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"AngryCloud" <[email protected]> wrote in
message
news:fkbm59$g70$[email protected]..
> This is what I have tried so far:
>
> if (strcasecmp($var, "ComparedString") == 0)
> {
> $error = 1;
> }
>
> ...but it doesn't seem to work.

Intermittent oracle errors with case-insensitive searches

Hi
I have a table with several columns, two of them are indexed with oracle text.
When I ask queries containing "CONTAINS"-clauses against these columns everything works great. However I have a few other columns in table that I want to run case-insensitive comparisons with.
So I enable case-insensitivity:
ALTER SESSION SET NLS_COMP=LINGUISTIC
ALTER SESSION SET NLS_SORT=BINARY_CI
Now I suddenly start getting intermittent errors.
When I call a query:
SELECT
FROM
article_table at
WHERE
CONTAINS(searchfield , '%MEAT%') > 0
Sometimes it works, but sometimes I get:
ERROR
ORA-29902: ett fel inträffade när rutinen ODCIIndexStart() kördes
ORA-20000: Oracle Text error:
DRG-00100: internal error, arguments : [50935],[drpn.c],[1051],[],[]
DRG-00100: internal error, arguments : [50935],[drpnw.c],[601],[],[]
DRG-00100: internal error, arguments : [51002],[drwa.c],[594],[],[]
DRG-00100: internal error, arguments : [51028],[drwaw.c],[297],[0],[%MEAT%]
DRG-00100: internal error, arguments : [50401],[dreb.c],[1033],[],[]
ORA-00600: intern felkod, argument: [qernsRowP], [1], [], [], [], [], [], []
Anyone knows what is going on? Is this bug? Is there a fox for it?
Thanks for any help anyone can provide.
/Kjell

Clearly that's a bug. Unless anyone here recognizes it and can point you to the bug/patch number I would strongly recomend you to take it to oracle support.
Incidently, doing a search for '%MEAT%' is usually a bad idea. Leading wildcards will disable the use of the index on the $I table, so unless you're using the SUBSTRING_INDEX option such searches will usually perform very badly. They shouldn't cause "internal errors", of course.

Case INSENSITIVE Columns on Oracle

Hello Friends,
Good Monday for everyone....
I would like to ask you guys if there is a way to create a case INSENSITIVE Columns on Oracle. I used on Sqlserver before the COLLATE sintax, and I was able to make a columns (just that one) INSENSITIVE.
I'm using oracle 10gr2 on Windows plataform and herte is my nls_parameters. My ideia is to search on this column without the need of performing a function UPPER and LOWER and etc...
NLS_LANGUAGE BRAZILIAN PORTUGUESE
NLS_TERRITORY BRAZIL
NLS_CURRENCY Cr$
NLS_ISO_CURRENCY BRAZIL
NLS_NUMERIC_CHARACTERS ,.
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD/MM/RR
NLS_DATE_LANGUAGE BRAZILIAN PORTUGUESE
NLS_CHARACTERSET WE8MSWIN1252
NLS_SORT WEST_EUROPEAN
NLS_TIME_FORMAT HH24:MI:SSXFF
NLS_TIMESTAMP_FORMAT DD/MM/RR HH24:MI:SSXFF
NLS_TIME_TZ_FORMAT HH24:MI:SSXFF TZR
NLS_TIMESTAMP_TZ_FORMAT DD/MM/RR HH24:MI:SSXFF TZR
NLS_DUAL_CURRENCY Cr$
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
tks a lot
Keen

APC wrote:
No, they mean a setting which makes "APC" or "apc" match "Apc".
There is nothing to be done on 10g, other than building a function based index on the column in question, so that any UPPER() searches are optimized.
Well, as Kamran Agayev already noted CI is available in 10g too. It also worth mentioning FBI creates a hidden column. Also, your statement
In 11g we have the option to set the NLS_SORT parameter so that any searches are case-insensitive (or indeed accent insensitive). Find out more.
is incomplete. NLS_SORT affects nothing but sort:
SQL> connect scott
Enter password: *****
Connected.
SQL> select * from v$version
2 /
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    order by name
12 /
NAM
Joe
Max
Sam
joe
max
sam
6 rows selected.
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    where name = 'max'
12 /
NAM
max
SQL> alter session set nls_sort = binary_ci
2 /
Session altered.
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    order by name
12 /
NAM
Joe
joe
max
Max
Sam
sam
6 rows selected.
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    where name = 'max'
12 /
NAM
max
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    where name like 'm%'
12 /
NAM
max
SQL> select 'Max' name from dual union
2 select 'max' name from dual
3 /
NAM
Max
max
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select distinct name
10    from t
11 /
NAM
sam
Joe
joe
max
Sam
Max
6 rows selected.
SQL> As you can see, NLS_SORT alone works on sort but not on "searches". We also need to set NLS_COMP, which by default is BINARY. Prior to 10g R2 (I am not 100% sure, it could be prior 10g), the only NLS_COMP choice, besides BINARY, was ANSI. However, ANSI does not work with all comparison operators (e.g. does not work for LIKE, UNION, DISTINCT):
SQL> alter session set nls_sort = binary_ci
2 /
Session altered.
SQL> alter session set nls_comp=ansi
2 /
Session altered.
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    order by name
12 /
NAM
Joe
joe
max
Max
Sam
sam
6 rows selected.
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    where name = 'max'
12 /
NAM
Max
max
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    where name like 'm%'
12 /
NAM
max
SQL> select 'Max' name from dual union
2 select 'max' name from dual
3 /
NAM
Max
max
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select distinct name
10    from t
11 /
NAM
sam
Joe
joe
max
Sam
Max
6 rows selected.
SQL> Starting 10g R2 NLS_COMP can be set to LINGUISTIC, which will also work for LIKE and UNION but not for DISTINCT:
SQL> alter session set nls_sort = binary_ci
2 /
Session altered.
SQL> alter session set nls_comp=linguistic
2 /
Session altered.
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    order by name
12 /
NAM
Joe
joe
max
Max
Sam
sam
6 rows selected.
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    where name = 'max'
12 /
NAM
Max
max
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select name
10    from t
11    where name like 'm%'
12 /
NAM
Max
max
SQL> select 'Max' name from dual union
2 select 'max' name from dual
3 /
NAM
Max
SQL> with t as (
2             select 'Max' name from dual union all
3             select 'sam' name from dual union all
4             select 'Joe' name from dual union all
5             select 'max' name from dual union all
6             select 'joe' name from dual union all
7             select 'Sam' name from dual
8            )
9 select distinct name
10    from t
11 /
NAM
sam
Joe
joe
max
Sam
Max
6 rows selected.
SQL> However even LINGUISTIC does not work with:
• CLOB or NCLOB data types
• Object data types
• Table partitions
• Index-organized tables
SY.

Make oracle database case insensitive

Hi All,
I am using oracle 10g EE as my back end database and front end is in C# .NET. I want to make my oracle database to perform any comparison case insensitively. I searched on the net and found several ways to achieve that
1. using upper function in procedures - can't afford
2. function index - can't afford
3. setting the session parameters
ALTER SESSION SET NLS_COMP=ANSI;
ALTER SESSION SET NLS_SORT=BINARY_CI;
The 3rd looks promising and can save lot of time. I have several question
1. Is there any way I can set these parameters from .NET?
2. Is there any way I can set once and will make only my database case insensitive?
any link, reference is highly appreciated.
Thanks,

user10768079 wrote:
Thanks for your mail.
I want to apply these settings to my oracle database only. It should not affect other oracle database that exist with my db.
Thanks,It would make sense to issue "ALTER SESSION" statements during logon process from the .NET code instead of changing the entire database - which might affect other users. Judging by the way you have written this, I feel you are referring to a schema rather than database.
.NET surely has the capability to run "ALTER SESSION" statements.

Case insensitive searching in Interactive Page

Hi all,
I am currently working on the interactive report, and wondering is it possible to perform case insensitive search for the data in the textbox besides the magnifying class.
By the default, the system uses "=" for searching. I tried the searching option using "contains", and it would be able to search the content in uppercase and lower case scenario. Is it possible to make "contains" as the default?
Thanks,
Thomas.

By the default, the system uses "=" for searching.I get "Row text contains..." as the filter when entering text directly into the default search box. Perhaps you are working with a saved report?
There's a way to make all IR comparisons case insensitive. See this <a ref="http://apex.oracle.com/pls/otn/f?p=34839:18">example of case/accent insensitive search</a> on a standard report.
That code can't be put in a Before Regions process as described to work with IRs as page processes are not executed by the AJAX call that refreshes the report. However, IR refreshes do run the Virtual Private Database PL/SQL call defined in the application security attributes, so putting the NLS modification code there will work.
Go to Application > Shared Components > Edit Security Attribute | Virtual Private Database (VPD), and make the call from there. Due to the specific requirements of the code that has to be called from here when used for security purposes, this is probably best done by setting this up to make separate calls to packages defined outside APEX, one to handle any actual VPD and other security-related details, and others to orchestrate any other code that has to be run. (For example, in this case it may not be desired to alter the NLS environment on every page, so the program could take a parameter specifying the current page and apply the ALTER SESSION conditionally on this.)

XMLIndex - case insensitive search ?

When creating an XMLIndex, is there an option to create it as case-insensitive, so any searches based on that will ignore case ?
My business requirement is that a search, e.g. for 'bank', should match bank, Bank, BANK, etc. ignoring case.
I could put a TO_UPPER around all my comparisons, but my concern then is that the XMLindex will get ignored and I end with with full table scans all the time.

If I am not mistaken, you can create an function based index as an extra layer on top of the XMLIndex / Path Table...

Keeping Case Sensitivity on objects in a case insensitive database

I have some tables and triggers in our case insensitive database which are not cased correctly and would like to correct them. Correcting them in the database projects and using SQLPackage.exe didn't apply those corrections. I suspect that
the comparison is using our database collation to do the comparison thus ignoring case. If I want the case sensitive changes to go thru but keep my current collation, is there a way to do that?

Hi
You can use the COLLATE command when doing comparisons
https://msdn.microsoft.com/en-us/library/ms184391.aspx
Regards
Javier Villegas |
@javier_vill | http://sql-javier-villegas.blogspot.com/
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

Possible to do case-insensitive searches?

G'day,
I was wondering if it's possible to do case-insensitive searches in oracle/HTMLDB?
I've tried what I thought would work
"select * from application where name like '%microsoft%'", this unfortunately doesn't return any records with a capital in it(eg "Microsoft").
If there is no way to do case-insensitive searches what is the best way around it?
Thanks
-Colin

Colin,
Yes it is possible to do case insensitive searches using SQL. Try, for example:
select * from application where upper(name) like '%ORACLE%'
The trick is to upper() both sides of the like operator.
Sergio

Error in a report after enabling case insensitive search in conn pool prop

Hi All,
I put the below code in connection pool's connection string to enable case insensitive search.
alter session set NLS_SORT=BINARY_CI
alter session set NLS_COMP=LINGUISTIC
After putting this code one of my report started giving the below error which was working fine otherwise.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. NQODBC SQL_STATE: HY000 nQSError: 10058 A general error has occurred. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16015 SQL statement execution failed. (HY000)
The report gives error for the below divide condition when I select a column from a different dimension (eg: region)
COUNT(DISTINCT RMA.RMA)/COUNT(DISTINCT User."User Name")
Can anyone please throw a light why this is happening.

Below is the SQL which is throwing error in OBIEE. It was working fine when I tried running it in toad:
select T1609.ATTRIB_05 as c1,
count(distinct T1609.ATTRIB_42) as c2,
TRUNC(T1159.FSCL_WEEK_START_DT) as c3
from
WC_DAY_D T1159 /* RMA_RECEIVED_DT(WC_DAY_D) */ ,
WC_RMA_D T571,
WC_FV_FA_D T1609,
WC_FV_FA_F T1679
where ( T571.ROW_WID = T1679.RMA_WID and T1159.ROW_WID = T1679.RMA_RECEIVED_WID and T1609.ROW_WID = T1679.FV_FA_WID and T1609.ATTRIB_39 <> 'FV' and (T571.STATUS_CD in ('2nd FA', '2nd FA Review', 'Closed')) and TRUNC(T1609.TODO_ACTL_END_DT) is not null and TRUNC(T1159.FSCL_WEEK_START_DT) between TIMESTAMP '2009-03-22 00:00:00' and TIMESTAMP '2009-04-12 00:00:00' )
group by T1609.ATTRIB_05, TRUNC(T1159.FSCL_WEEK_START_DT)
order by c3
-------------------- Query Status: Query Failed: [nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16015] SQL statement execution failed.

How to change Database server is case-insensitive setting at runtime

Is there a way to change any of the properties in Report Options > General Settings at runtime. Mainly the [Database server is case-insensitive] and [Perform grouping on server] settings. We are using the Crystal .Net X1 runtimes (11.5.9707.811). I have sesrched the forums with no luck so thought I'd try my luck here. Thankyou for your time.

Hi Simon,
Sorry, search for the function using the Object Browser in .NET. If you have Crsytal Reports XI R2 (11.5.x.xxxx) then you have it. Unless it's not a developer version. In whcih case you need to upgrade.
If you do have the Developer version then simply add the RAS assemblies to your project. Look in our samples above for more info on h ow to use RAS.
If you don't have the Developer version then your only options are to upgrade or manually change the report settings in the Designer.
Thank you
Don

How do I move my large iTunes collection from a case-sensitive hard drive to a case-insensitive hard drive?

I currently keep my iTunes media on an external hard drive because it takes up too much space on my machine. I recently discovered that it was formatted as case-sensitive when I bought it, and now months later I'm having issues. When attempting to back up my files on a case-insensitive hard drive, the operation failed due to conflicting file/folder names (Artist and artist are now considered the same file name and one would have to overwrite the other). I now have a large iTunes file collection that is stuck on the case-sensitive hard drive, and I want to save a backup on a case-insensitive drive.
Is there a way to identify all cases where multiple files/folders have the same title/album/artist but different spelling so there will be no conflicts? The folder/file names would have to be crossed referenced to highlight any cases where File/fiLe/file would cause a problem.
I imagine there is a way to do this using iTunes script or Automator or a command in terminal or something rather than going through and checking/fixing all the information for thousands of songs by hand. I'm at the limits of my minimal development skills, so any help would be appreciated.

You should be able to use either "Carbon Copy Cloner" or "SuperDuper" (free for this purpose) to copy your case-sensitive volume to an empty case-insensitive one. Make at least two such copies on different drives. One is not enough to be safe.
If there are any name conflicts—that is, files in the same folder with names that differ only in case, such as "File" and "file"—then you will either get an error or one of the files won't be copied. You must ensure either that no such conflicts exist, or that the consequences are not important. How you do that is up to you. Unless you went out of your way to create conflicts, they probably don't exist.
Then erase the source volume in Disk Utility as case-insensitive. This action will remove all data from the volume.
Restore from one of your backups using the same application you used to create it, or use the "Restore" feature of Disk Utility, which will be faster. Search its built-in help for the term "duplicate" if you need instructions.

Time Machine says both of my external hard drives require reformatting to case insensitive. What do I do?

I have been successfuly using Time Machine to back my iMac to an external hard drive (via usb) and everything has been fine for the last year. I have been using TM to back up to a HD called Terra LaCie via usb.
A week ago, my iMac hard drive was full--so I spulrged and bought a 6 TB external hard drive (Western Digital My Book-Thunderbolt). I set up the new Thunderbold HD to use RAID 1 (mirror) and copied most of my iMac hard drive over to the Thunderbolt HD.
I kept my working photographs (most recent) on my iMac and felt good to know my older photographs are on my new Thunderbolt hard drive.
For a few days, Time Machine seemed to work fine (backing up my iMac to Terra LaCie HD. I haven't been concerned with backing up the Thunderbolt drive (as I feel that mirroring is same as backing up).
Yesterday, Time Machine indicated the lastest back-up failed (for the HD called Terra LaCie). Now, when I go into Time Machine, the dialog box indicates the following message:
"Are you sure you want to erase the backup disk “Terra Lacie”? Erasing will destroy all information on the disk and can’t be undone.
The disk must be erased before it can be used for Time Machine backups because a disk you are backing up is case sensitive, but the backup disk is not."
When I open Time Machine to look at my external hard drives (I also have a third usb portable drive); two of the three drives indicate the following:
"reformat required; case insensitive disk".
The small, portable hard drive (that I'm also using) doesn't say it needs to be reformated (but my new Thunderbolt and my old usb HD both indicate the same message (above).
What should I do? I just spent days transferring my photographs from my iMac to my new Thunderbolt. Should I just not use Time Machine any longer and work from my Thunderbolt drive?
Am I to understand that my iMac suddenly become case sensitive? Sorry if this was too much information about my hard-ware set-up.
Any help someone can provide me would be greatly appreciated. I suppose I need to understand Time Machine and perhaps my Thunderbolt better.

Hi BDAqua,
Bravo, you helped me solve my problem.
The Case Sensitive Disk was the small portable hard drive that I was using termporarily.
I just disconnected it and I started TM machine and everything seems to be working just fine.
Thank you very much!!!!

Case insensitive comparison

Similar Messages

Maybe you are looking for