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

Similar Messages

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

  • 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

  • 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 Sensitive ColumnNames

    Hello,
    When I have the following query as example:
    select sysdate "SystemDateTime" from dual;
    Retrieving the table columnname with MetaData::ATTR_NAME gives me "SYSDATETIME" in stead of "SystemDateTime". It doesn't give a case sensitive table columnname back although I mentioned it in the query.
    Is this normal behaviour?
    Rodger

    Can you post your code?. I get the correct mixed case column alias with this code :-
    Statement *stmt = conn->createStatement("select sysdate \"AbCd\" from dual");
    ResultSet *rs = stmt->executeQuery();
    vector<MetaData> md = rs->getColumnListMetaData();
    cout << "Column " << md[0].getString(MetaData::ATTR_NAME) << endl;
    Regards.

  • Case sensitive sql - table and field names

    I have a weird problem.
    I have a client which works with MS SQL SERVER 2000.
    database collation name is: Turkish_CI_AS
    at the beginning I have this sql statement:
    "select value from [OWNER].setting"
    but because this table exists in database as "SETTING", I get java.sql.SQLException -
    [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'setting'.
    while I change the sql statement to:
    "select VALUE from [OWNER].SETTING"
    it works ok.
    I uses also other databases, but it works ok with small letters.
    How can avoid this problem? should I change all the sql statements to
    upper case?
    I will appreciate any help.
    Thanks.

    I am not sure about case sensitivity of tables, but as a convention, I always use table names in UpperCase separated only by _.
    I don't remember this to be a problem with Oracle or Sybase.
    ***Annie***

  • Case sensitive filed in DB table, Filter needed ignoring case sensitivity

    Hi,
      Therse is a DB table with one of the fields marked to recognize case sensitivity. I have to do a filter on this field with a wild card pattern such that irrespective of the case, the record should be extracted as and when the pattern is found.
    One way of doing this is TRANSLATE field to UPPER CASE after extracting all the records to an internal table.
    But I see that this can be an expensive call as there are tons of records to be processed. Is there any performance efficient way to handle this?
    Example:
    Filed Name: XML_LINE.
    Field Content can be in any of the following formats:
    Format 1: break.
    Format 2: BREAK
    Format 3: BreaK.
    Format 4: breAK.
    Format 5: breAK-point.
    Format 6: breAK-POINT.
    The wild card pattern I would like to use here is on the word "break" irrespective of the case and extract only the relevant records.
    wild card pattern1: b*.
    wild card pattern:B*.
    Can count of the number of letters help here for the words "break." and "break-point." along with wild card patterns or is there any better way of doing this? 
    Thanks & Regards,
    Ranjini

    Hi,
    a solution is to create a second field without case sensitive ans stored word in UPER CASE.
    If you see in SAP (f.e. Customer or Creditor), SAP store NAME in a search field (in upper case). Make the same.
    Rgds

  • Table and Primary Key Case Sensitive in Automated Row Fetch

    Why are the table and primary key fields case sensitive in the Automated Row Fetch process? I'm debugging an error in this process and I'm not sure what the case should be.

    Russ - It's a defect of sorts. Use upper case in the process definition. I don't think these processes will work with tables or columns whose names are not known to the database as upper-case values, i.e., defined using double-quoted non-upper case.
    Scott

  • Table filtering is case sensitive

    ADF Version: Oracle JDeveloper 11 g Update 2 (Build 5205) (11.1.1.0.2)
    We are using an older version of ADF / jDeveloper for our application. We have run into the issue where all of the filter fields on our tables seem to be case sensitive. I am aware that in more recent versions of ADF you can simply use the FilterFeatures attribute of a column to control this behavior. Unfortunately our version of ADF does not support this feature.
    Is there anyway in our version of ADF that I can make it so the filtering is not case sensitive? What do I have to do, or what classes do I have to override to get the desired behavior? Is it even possible in this older release? Thanks in advance.

    Hi,
    you can create a custom query listener on the table, intercept the filter criteria and turn them as you need them. See example #30 at http://www.oracle.com/technetwork/developer-tools/adf/learnmore/index-101235.html . All you need to do is to intercept the table filter setting and execute a query on the WS so that the filter criteria values are used case insensitive
    Frank

  • How to make Values in Table maintenance to be case sensitive

    Table has only one field called link which is used to store the URL along mandt.
    Table is  maintained thru table maintenance
    When I give value say http://www.abc.com/ipr/input  into the table thru table maintenance, by default the contents are changed to caps
    HTTP://WW.ABC.COM/IPR/INPUT  like this
    I pass this link to the email content and it doesnu2019t navigate thru the path mentioned.
    While clicking the link in the content, it is changing to
    http://www.abc.com/IPR/INPUT  and asks to go to index page.
    Can you help me to change all the values to be maintained as case sensitive ?
    Thanks

    Hai,
    Use this Domain for yur URL data element TEXT150 or TEXT120 .
    Yur probelm solved.
    reward If  usefull.
    Thanks,
    Durai.V

  • 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

  • In ALV Report Filter selection should be case sensitive

    Dear All,
    since one field is case sensitive in database table , i have to fetch that in alv report , but when i am applying  filter on that field its is simply fetching data with case description.  if its in caps it should fetch caps data but in   smaal case report showing no data
    Regards,
    Pankaj Vashista

    Hi,
    All text datas are case sensitive.
    To make it work perfectly You have to Use the Keyword translate to Upper Case than display
    Now filter can work.
    Without Transalation to Upper Case filter will not work.
    Regards
    Arbind

Maybe you are looking for