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

Similar Messages

  • 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 !

  • Query in expdp with case-sensitive table and columnname

    Hi,
    I've got a problem with exporting some specific rows of a table.
    The problem is a case-sensitive table and column name. I've tried this in a parfile:
    dumpfile=dpumpdir1:test.dmp
    logfile=dpumpdir1:test.log
    tables="Data"
    query="Data":'"where "DataID" = 11"'
    but it ended like this:
    ORA-31693: Table data object "Data" failed to load/unload and is being skipped due to error:
    ORA-06502: PL/SQL: numeric or value error
    ORA-31605: the following was returned from LpxXSLSetTextVar in routine kuxslSetParam:
    LPX-314: an internal failure occurred
    Edited by: [Logik on 18.04.2013 01:18                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    I've tried to make a function with this. I think you used some Oracle 11 parameters. reusefile for example.
    However I've managed to compile the function without error:
    CREATE OR REPLACE FUNCTION EXPDP RETURN NUMBER IS
      h1 number;
      v_job_state       varchar2(4000);
    BEGIN
      h1 := dbms_datapump.open(operation=>'EXPORT',job_mode=>'TABLE',job_name=>'HARRY10');
      dbms_datapump.add_file(h1,'example1.dmp','DPUMPDIR1');
      dbms_datapump.add_file(h1,'example1.log','DPUMPDIR1',filetype => dbms_datapump.ku$_file_type_log_file);
      dbms_datapump.metadata_filter(handle => h1,name => 'NAME_EXPR',value => 'IN (''Data'')',object_type => 'TABLE');
      dbms_datapump.data_filter(handle => h1,name => 'SUBQUERY',value => 'WHERE "DataID" = 1');
      dbms_datapump.start_job(h1);
      DBMS_DATAPUMP.WAIT_FOR_JOB (h1,v_job_state);
      DBMS_OUTPUT.PUT_LINE(v_job_state);
      RETURN NULL;
    END EXPDP;But when I execute I get:
    ORA-31626: job does not exist
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 938
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 4592
    ORA-06512: at EXPDP", line 5
    ORA-06512: at line 5
    Probably not my day :(
    By the way... how can I Format the text as a script?
    Edited by: [Logik on 19.04.2013 11:01                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • 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

  • 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'.

  • 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

  • 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.

  • 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!!

  • Case-sensitive Table

    I'm working with an application that has double quotes wrapped around its scripting which creates tables. Is there any way to facilitate coding by eliminating the requirement to wrap the tablename with double quotes.
    Renaming the table is not an option, it will end up breaking the application that created the table. Also, I cannot change how the applcation is written either. I was hoping that there might be something that can be done within the database to facilitate this.
    Keith

    Would a simple synonym do the trick?
    SQL> create table "lowercase_tab"
      2  (x   number
      3  ,y   varchar2(10));
    Table created.
    SQL> create synonym lowercase_tab_s for "lowercase_tab";
    Synonym created.
    SQL> insert into lowercase_tab_s values (1, 'blah');
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> select *
      2  from lowercase_tab_s;
                       X Y
                       1 blahMessage was edited by:
    ericch2

  • Jdbc bug in executeUpdate(sql, int[]) when table name is case-sensitive;

    I have found a bug in oracle's jdbc (ojdbc6.jar), can someone tell me how to submit it so that it can be fixed?
    The BUG: using executeUpdate(insert_sql_stmt, int[]) to retrieve the generatedKey generated by before-insert trigger using a sequence results in error when the tablename is case-sensitive (but OK if table name in uppercase).
    Steps to reproduce:
    1a. create table "mixCase" (f1 integer, f2 varchar2(20));
    1b. create table upperCase (f1 integer, f2 varchar2(20));
    2a. create sequence mixCase_seq start with 1;
    2b. create sequence upperCase seq start with 1;
    3a. create or replace trigger mixCase_trigger before insert on "mixCase"
    bq. for each row \\ begin \\ select mixCase_seq.nextval into :new.f1 from dual; \\ end;
    3b. create or replace trigger upperCase_trigger before insert on upperCase
    bq. for each row \\ begin \\ select upperCase_seq.nextval into :new.f1 from dual; \\ end;
    4a. String url = "jdbc:oracle:thin:@//localhost:1521/orcl";
    bq. conn=DriverManager.getConnection(url,user,password); \\ Statement stmt = conn.createStatement (); \\ int rc=stmt.executeUpdate("insert into \"mixCase\"(f2) values('aa')",new int[]{1});
    4b. String url = "jdbc:oracle:thin:@//localhost:1521/orcl";
    bq. conn=DriverManager.getConnection(url,user,password); \\ Statement stmt = conn.createStatement (); \\ int rc=stmt.executeUpdate("insert into upperCase(f2) values('aa')",new int[]{1});
    When you run 4a or 4b in a java jdbc program:
    4b runs OK and rset=stmt.getGeneratedKeys() returns the correct f1 value of 1.
    4a results in error:
    bq. h6. java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist \\ + at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)+ \\ + at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)+ \\ + at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)+ \\ + at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)+ \\ + at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:406)+ \\ + ...+
    +Notes:</</em>
    # If Statement.RETURN_GENERATEDKEYS is used instead of "new int[]{1}" in 4b, there is no error but the rset=stmt.getGeneratedKeys() returned in a ROWID such as 'AAARUyAAEAAAAGQAAL', not what is expected. Other database's jdbc return the correct generated integer value.
    # Same 4b error if new String[]{"f1"} is used as 2nd argument for executeUpdate.
    # The only difference in 4a and 4b is that 4a has case-sensitive table name. All sequence names, trigger names, column names are implicitly deemed to be uppercase by oracle in both cases.
    bq.
    Edited by: user10343198 on Oct 2, 2008 5:50 PM
    Edited by: user10343198 on Oct 2, 2008 6:34 PM

    Please patch one fo your machines to 10.2.0.3 and then try and duplicate. You do not have to go through the complete registration of the XSD process thoguh you can check and see if the c based parser will validate on the command line using the
    schema executible under your oracle_home bin directory.
    schema 1.xml 1.xsd
    for example
    if it dupes in 10.2.0.3 open a TAR with support so that we may bug it.
    regards
    Coby

  • Unable to create cache groups from CASE-SENSITIVE oracle table's name

    Hello All
    I have some case-sensitive tables in a oracle database and their columns are the same too. I've tried to cache these tables into TimesTen under a read-only cache group. I think timesten cannot find
    case-sensitive tables because as soon as I changed name of the tables, the creation could succeeded. What can I do to overcome this issue? I don't want lose case-sensitive feature. Is it because of
    I'm using an old version of TimesTen(11.2.1.4.0)

    Hi Chris
    Thanks for your answer. I'm using SQL Developer(both graphical and by command) to manage Timesten db. When I'm about to select root table for cache group i can see the table and when I
    select on it, the caching procedures can not be done and it says your table does not have Primary Key; you can see below that this is not true and the table has two primary key. When I'm
    trying to create the cache group via command in work sheet the error is "TT5140: could not find HLR.SUBSCRIBER. may not have privileges"
    in Oracle:
    CREATE TABLE "HLR"."Subscriber"
    "SSI" NUMBER(10,0) NOT NULL ENABLE,
    "CCNC" VARCHAR2(50 BYTE) NOT NULL ENABLE,
    "Code" VARCHAR2(128 BYTE) DEFAULT NULL NOT NULL ENABLE,
    "Account" NVARCHAR2(32),
    "Mnemonic" NVARCHAR2(15),
    "Region" NVARCHAR2(32),
    "UserAddress" NVARCHAR2(32),
    "Name" NVARCHAR2(32) NOT NULL ENABLE,
    "VPNCode" NUMBER(10,0),
    "VPNCCNC" VARCHAR2(50 BYTE),
    "SubOrgId" NUMBER(10,0),
    "SubscriberTypeId" NUMBER(2,0) DEFAULT 5 NOT NULL ENABLE,
    "StatusId" NUMBER(2,0) DEFAULT 1 NOT NULL ENABLE,
    "SubscriberClass" NUMBER(2,0),
    "DefinedIpAddressId" NUMBER(10,0),
    CONSTRAINT "Subscriber_PK" PRIMARY KEY ("SSI", "CCNC") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "USERS" ENABLE,
    CONSTRAINT "FK_DefinedIpAdd_Subscriber" FOREIGN KEY ("DefinedIpAddressId") REFERENCES "HLR"."DefinedIPAddress" ("Id") ENABLE,
    CONSTRAINT "Fk_Status_Subscriber" FOREIGN KEY ("StatusId") REFERENCES "HLR"."Status" ("Id") ENABLE,
    CONSTRAINT "Fk_SubOrg_Subscriber" FOREIGN KEY ("SubOrgId") REFERENCES "HLR"."SubOrganization" ("Id") ENABLE,
    CONSTRAINT "Fk_SubscriberType_Subscriber" FOREIGN KEY ("SubscriberTypeId") REFERENCES "HLR"."SubscriberType" ("Id") ENABLE,
    CONSTRAINT "Fk_VPN_Subscriber" FOREIGN KEY ("VPNCode", "VPNCCNC") REFERENCES "HLR"."VPN" ("SSI", "CCNC") ENABLE
    in TimesTen:
    CREATE READONLY CACHE GROUP "PRO1"
    AUTOREFRESH MODE INCREMENTAL INTERVAL 5 MINUTES
    STATE PAUSED
    FROM "HLR"."Subscriber"
    "SSI" NUMBER(10,0) NOT NULL ,
    "CCNC" VARCHAR2(50 BYTE) NOT NULL ,
    "Code" VARCHAR2(128 BYTE) NOT NULL ,
    "Account" NVARCHAR2(32),
    "Mnemonic" NVARCHAR2(15),
    "Region" NVARCHAR2(32),
    "UserAddress" NVARCHAR2(32),
    "Name" NVARCHAR2(32) NOT NULL ,
    "VPNCode" NUMBER(10,0),
    "VPNCCNC" VARCHAR2(50 BYTE),
    "SubOrgId" NUMBER(10,0),
    "SubscriberTypeId" NUMBER(2,0) DEFAULT 5 NOT NULL ,
    "StatusId" NUMBER(2,0) DEFAULT 1 NOT NULL ,
    "SubscriberClass" NUMBER(2,0),
    "DefinedIpAddressId" NUMBER(10,0),
    PRIMARY KEY("CCNC","SSI")
    )

  • Oracle 9 table names are not case sensitive

    Sorry about the trivial question, but I noticed that when I am creating table in Oracle their names is always upper case.
    Example:
    CREATE TABLE MyTable (i NUMBER(5))
    CREATE TABLE MYTable (i NUMBER(5))
    CREATE TABLE MyTABLE (i NUMBER(5))
    CREATE TABLE MyTablE (i NUMBER(5))
    it is the same table. Is it true that Oracle cannot create tables with names case sensitive, or I am doing something wrong.
    Any help

    You can create case sensitive table with table names enclosed in quotes.
    SQL> create table sample(id number);
    Table created.
    SQL> select table_name from user_tables where upper(table_name)='SAMPLE';
    TABLE_NAME
    SAMPLE
    SQL> create table "sample"(id number);
    Table created.
    SQL> select table_name from user_tables where upper(table_name)='SAMPLE';
    TABLE_NAME
    SAMPLE
    sample
    SQL>

  • Case Sensitivity of MySql Table Names

    I am using a MySql 5 db successfully transferred from MsSql
    with the MySql migration kit. It works just fine with my CF 8
    application, except for having to match the case of table names in
    all <cfquery> tags. My online host runs Linux for MySql.
    I have installed MySql on my local Windows development
    machine but notice that it has no such table name case sensitivity
    -- a problem since that means I cannot test locally.
    I have tried putting lower_case_table_names=0 in the MySql
    my.ini file but it has not effect.
    Any suggestions as to how to set up windows/CF 8? Is this
    something that the built in CF server can be modified to do?
    Thanks.

    Ortho wrote:
    > I have tried putting lower_case_table_names=0 in the
    MySql my.ini file but it
    > has not effect.
    regarding the lower_case_table_names setting, here's a quote
    from
    http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html
    " If you are using MySQL on only one platform, you don't
    normally have
    to change the lower_case_table_names variable. However, you
    may
    encounter difficulties if you want to transfer tables
    between platforms
    that differ in filesystem case sensitivity. For example, on
    Unix, you
    can have two different tables named my_table and MY_TABLE,
    but on
    Windows these two names are considered identical. To avoid
    data transfer
    problems stemming from lettercase of database or table
    names, you have
    two options:
    * Use lower_case_table_names=1 on all systems. The main
    disadvantage with this is that when you use SHOW TABLES or
    SHOW
    DATABASES, you don't see the names in their original
    lettercase.]
    * Use lower_case_table_names=0 on Unix and
    lower_case_table_names=2
    on Windows. This preserves the lettercase of database and
    table names.
    The disadvantage of this is that you must ensure that your
    statements
    always refer to your database and table names with the
    correct
    lettercase on Windows. If you transfer your statements to
    Unix, where
    lettercase is significant, they do not work if the
    lettercase is incorrect.
    Exception: If you are using InnoDB tables and you are trying
    to
    avoid these data transfer problems, you should set
    lower_case_table_names to 1 on all platforms to force names
    to be
    converted to lowercase.
    Note that if you plan to set the lower_case_table_names
    system variable
    to 1 on Unix, you must first convert your old database and
    table names
    to lowercase before restarting mysqld with the new variable
    setting. "
    Azadi Saryev
    Sabai-dee.com
    http://www.sabai-dee.com

  • Case sensitive field in to_date function

    update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)
    Here the OrderDate column is of type Date
    "Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
    when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input string
    So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
    where column1 is date field and field1 is varchar2 and this worked.
    So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.

    Hi,
    Welcome the the forum!
    882431 wrote:
    update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)It looks like you're missing a single-quote right before the last ')'.
    Here the OrderDate column is of type Date
    "Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
    when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input stringThat error occurs when when you have characters in the 1st argument that do not correspond to anything in the 2nd argument. For example:
    TO_DATE ( '30-Aug-2011 12:00'
         , 'dd-Mon-yyyy'
         )In this example, TO_DATE doesn;t know what to do with the ' 12:00' at the end of the 1st argument. According to the 2nd arguemnt, there's only supposed to be 11 characters in the string. So it raises the ORA-01830 error.
    So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
    where column1 is date field and field1 is varchar2 and this worked.
    So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.Case sensitive column names are a bad idea because they cause so amny problems, but I don't think this is one of those problems. It's more likely that you need to use SUBSTR (or some other string manipulation function) on "Order Date String" before using it in TO_DATE.
    Whenever you have a problem, please post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) from all tables, so people can re-create the problem and test their ideas.
    Also post the results you want from that data, and an explanation of how you get those results from that data, with specific examples.
    Always say which version of Oracle you're using.

Maybe you are looking for