Problem in XI - JDBC (oracle) Scenario, case sensitive column name

I had a XI -> JDBC scenario, connecting to a SQL server, where the query was being generated using Message Mapping (XML SQL Format),
now the database has been migrated from SQL server to Oracle, and we are using the same XI scenario, but now the problem is, the query generated using message mapping doesnt work because it seems the query (UPDATE statement) requires the field name as having All capital letters, i mean the Column name in query to Oracle has become case sensitive,
can u help me out

Hi
Oracle doesnt have restriction that Query has to be in uppercase for any column. But it is good go use Upper case for the Query.
Use oracle editor to do the query if it is working fine and then use XML SQL in XI
Check this thread SAP has given some
http://help.sap.com/saphelp_nw04s/helpdata/en/43/68a541a1166153e10000000a1553f6/frameset.htm
Check FAQ on the JDBC adapter, see SAP Note 831162
always useful Note
Thanks
Gaurav

Similar Messages

Case sensitive column name problem

I have a strange problem in my application.
I install the application on several machines with no problem but in one machine I'm getting an exceptions on:
"Column 'SomeColumnName' does not belong to table"
the code look like this:
DataRow newDataRow = myTableFromDatabase.NewRow();
newDataRow["SomeColumnName"] = dr["SomeColumnName"];
when I change the code to upper case:
DataRow newDataRow = myTableFromDatabase.NewRow();
newDataRow["SOMECOLUMNNAME"] = dr["SOMECOLUMNNAME"];
it works on the problematic machine.
- I got the same problem on reading data from OracleDataReader.
- The property DataTable.CaseSensitive was not changed (default = false).
I'm not sure this is ODP problem or .net but I can't find any .net issues on that.

Ok ,
This is the most bizar bug that I ever saw:
The problem was that the machine was running in turkey.
In .NET culture settings the function ToUpper is not work on the letter 'i' when the region is turkey.
That means that oracle ODP OracleDataReader is case sensitive on the column name - if the column name have the letter 'i'.

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

Case sensitive Tag names

Hi friends
I have a question, is it possible to transfer case sensitive tag names into xml structure ? for exemple, I want to transfer Tag name "DateCreated" . I did a test but start tag names is "DataCreated" and it is Translated in "DATACREATED" and this is a problem.
Thanks
Sergio

Sergio,
Usually what ever you have given in your xsd or message type you will have the same. So please check it. I just tested this and it seems to be the same as defined in your xsd or message type.
Regards,
---Satish

The error: "Oracle Error 904 / Invalid Column name"

When I try to take the Oracle Backup with the Exp command. I got the following error.
The error: "Oracle Error 904 / Invalid Column name" .
Any solution or suggestion?????????

Asif, to add another question to the list of things to check. Is the version of the exp utility you are using to perform the export operation the same version as the database? If not, that would explain the error.
If you are trying to export using a newer version of the export utility that generally will not work. You should switch to using the db version.
If you are exporting using an older version because the target is an older version then usually you need to run the catexp# where # is the version number script for the target version that Oracle provides in the $ORACLE_HOME/rdbms/admin directory.
HTH -- Mark D Powell --

Oracle is Case Sensitive, can we change this.?

Hi all,
As Oracle Data is a Case sensitive.
but i want to know that,
is there any way to change this ?
that is , the data should not be a case sensitive.
select * from emp where ename = 'smith';
Even the SMITH is in caps. it should return that records for the above query.
Thanks.
GowriShankar.N

As a one off for queries you can use the UPPER and LOWER functions, ie;
select * from emp where LOWER(ename) = 'smith';

Problems retrieving backup from Time Machine, Case-sensitive HD

Hello.
I'm trying to manually retrieve the information I got in a Time Machine, but for some reason I kept getting an error saying that there were files that were going to the same location were named in the same way. After checking a couple of things I noticed that, somehow, the external HD was Case-sensitive, so I'm assuming that, instead of +File, File 01 File 02+ it's sorted out like +File, file, filE+, and since the computer's HD is normal it's having a conflict with those file names.
That being said, is there a way to fix this? What I'm trying to move is an iTunes and iPhoto Library, "probably" iTunes could be done manually, but in iPhoto there's over 10 GB of pictures and I'd probably take a looooong while to fix it manually.
Any work around?
Thanks!

Hi Adrian ...
Let me see if I can help ...
I'm trying to manually retrieve the information I got in a Time Machine, ...
How? With the TM App or from the Finder?
but for some reason I kept getting an error saying that there were files that were going to the same location were named in the same way.
It's just letting you know that the original file, on the System HD, still exists and wants your permission to over write the original file with the TM file. Backing up your System HD to TM should not have changed any of the original file names. If TM had changed the Case when backing up from your System then TM Restore would have duplicate these files/folders without even asking you.
That being said, is there a way to fix this?
Yes. After you have restored the files/folders that you want to keep you can reformat the TM HD. Or try one of my tricks which is to just reformat the free space. Use the Mac OS X Extended (Journaled).
Good Luck.
Buzz

Problem in connectString = "jdbc:oracle:oci8@";

i get error in following lines.
=========================================
connectString = "jdbc:oracle:oci8@";
connection = DriverManager.getConnectionconnectString,"ORDMEDIADEMO",
"ORDMEDIADEMO");
===========================================
what should be there in connection string??? after @ , anything is to be specified??
I wrote my computer name(win2000server)...(p4.headquarter.local) .but it diden/t work.......plz help me.
thanks

Look in the JDBC documentation.
What is your service name?
You can use a string like:
@(description=(address=(host=your_machine.your_domain.com)(protocol=tcp)(port=1521))(connect_data=(service_name=your_service.your_service_domain.com)))
Or you can use one of the definitions in your tnsnames.ora file @my_sid
Larry

Case sensitive table names and column names in 8i or 9i databases

Hi everybody,
I've got a couple of business-side colleagues who insist that Oracle table and column names are case sensitive. That is, there is a setting in the set up of a database that lets you pick if table and column names are case sensitive. For example, this would mean that there could be a table named EMP in a given schema schema plus a table named emp in that same schema.
Can this be true? I'd be surprised of course, but I've been surprised before.
Thanks for any direction.
-- Bill Loggins

You can do it, but I would avoid it like the plague.
SQL> create table "a" (b date);
Table created.
SQL> create table "A" (b date);
Table created.
I think I would refuse to work on a database where this has been used !

Problems on selecting views with french characters into column names

Hi All,
I have views with column names such as "Détermination Planimétriq" or "Année de construction:*";
I can get in my c# function this columns names from ALL_VIEWS dictionary table, but if I try to make a selectionby use of an OracleCommand, Oracle returns an "Invalid identifier" error:
SELECT "Détermination Planimétriq" FROM mytable;
System.Data.OracleClient.OracleException (0x80131938): ORA-00904: "Determination Planimetriq": invalid identifier at System.Data.OracleClient.OracleConnection.CheckError(OciErrorHandle errorHandle, Int32 rc) at ...
Any suggestion?...

Be wary of using character codes outside the Western European "simple" alphanumeric [A-Z0-9] for object names, i.e. columns, table names, function and procedure names, and so on.
First reason, there is a 30 character limit for most object names, and characters that have to be spelled out with unicode characters take more space, i.e.:
select dump( 'Détermination Planimétriq' ) from dual;
DUMP('D?TERMINATIONPLANIM?TRIQ')
Typ=96 Len=29: 68,239,[ ... ]Although the varchar string for that column name looks like 25 characters, it needs room for 29 to store the e<acute> character. And could also depend on the client settings. Using case sensitive names is not a best practice, its better to avoid specifying objects with the double quotes.
http://docs.oracle.com/cd/E11882_01/server.112/e26088/sql_elements008.htm#i27570

Oracle 10g - Defining the column name in Non English

Hi Experts,
I have an exisitng application which is developed on Windows using ASP Technology and uses Oracle 10g 10.1.0.2.0.
The application is supported with an instance of Data Base within which multiple tablespaces are created for different clients. The application is developed in such a way that some of the tables arecreated dynamically and the columns are named using the data entered through the UI.
This application needs to be globalized now. The problem is, the column name entered through the UI can be in any language based on the client's settings and those values in turn will be used for naming the columns in the tables.
1) Can I have the column names to be named using non english characters in Oracle 10g DB? If so,
1.1) what should I do to configure the exisiting Oracle instance to support it?
1.2) To what level is that configuration possible, is it per DB instance level (or) can it be done at Tablespace level. I would like to configure each tablespace to host tables with columns defined with different languages, say for example, tablespace 1 will have tables with Japaenese column names and tablespace 2 will have tables with German column names?
2) What should I do to make my entire DB to support unicode data i.e., to accept any language strings. Currently all strings are declared as VarChar2, should I change all VarChar2 to NVarChar2 (or) is there a way to retain the VarChar2 as is and make some database wide setting?
Please note that I do not have an option of retaining the column in English as per the Business Requirement.
Envionment:
OS - Windows 2003 32 bit
Oracle 10g 10.1.0.2.0
UI forms in ASP
TIA,
Prem

1. Yes, you can.
SQL> create table ÜÝÞ( ßàá number(10));
Table created.
SQL> insert into ÜÝÞ values (10);
1 row created.1.1 and 1.2 and 2. You can choose UTF as your default character set. It allows the user of non-English characters in VARCHAR columns in your whole database. It is not per tablespace.
SQL> create table ÜÝÞ( ßàá varchar2(100));
Table created.
SQL> insert into ÜÝÞ values ('âãäçìé');
1 row created.

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.

Case Sensitive File Names

Hi...
I've been trying out the trial version of RH8, before
upgrading from RH7. One of the problems I have noticed is the
option to "Use Lowercase File Names (Recommended for UNIX)" in the
Single Source Layouts setting, only works for actual pages in the
project. As i have a number of PDF's as baggage files (that now get
indexed), when they are returned in the search results, I just get
a "Not Found" error. This is because it is not correctly putting
the folder names or file names in lower case.
Does anyone know a solution or workaround for this? (aside
from renaming all files/folders!). Or know where I can submit this
as a bug?
Thanks...

Bug/Feature requests can be filed
here..
As a workaround, you could try renaming your baggage files - for
example File.pdf to file1.pdf and then to file.pdf. You'd need ot
delete and add the baggage file references though. An alternative
is to exclude the baggage file type from the search. You can find
out how to do this from the latest post on my blog.

Case sensitive table names

Hi all, I create a table named "Organism" on my marvel schema. When I do a SELECT * FROM "Organism", I get correct results, but when I try to do
DESC "Organism"
I get an error message saying the table doesn't exist.
Is there something I am missing ?
regards,
Davide

hmmm. it looks like you found a tiny bug in our Ad Hoc module within the SQL Workshop. you can get around it for now by browsing for your table in the Data Browser of the SQL Workshop. it just appears that in the SQL Workshop we haven't accounted for the cases where people are defining their objects with mixed case text. it's a super easy fix on our part, though, so i imagine we'll see things working more smoothly soon.
regards,
raj

Retaining case sensitive path names

We are currently using initial capital letters for our directories in our path names. But every time I update my Fireworks file it automatically changes all directory names back to lower case, thus breaking our links on our web pages. Is there a way I can configure Fireworks to retain my Upper Case first letters of my directory names after I've updated the Fireworks file?

Hi Jim,
Thanks so much for your help--much appreciated!!

Problem in XI - JDBC (oracle) Scenario, case sensitive column name

Similar Messages

Maybe you are looking for