Schema name & user name

Hi All,
I have a question that can a username and schema name can be diffrent for a single user. For example when we connect with SYSOPER we connect with PUBLIC schema but the user is SYS.
Is there any syntax to create the same.
Thanks
Bhupinder

You can grant access for any user to "public", however, it's bad for security.
Example-
connect scott/tiger@mydb
create table TomTable (main_id number);
grant select on tomtable to public;
connect newuser/newpass@mydb
select * from scott.tomtable;
This gives "newuser" access to Scott's "tomtable" table.
You can also create public synonyms...
As scott/tiger-
create public synonym tomtable for scott.tomtable;
connect newuse/newpass@mydb
select * from tomtable;
Now "newuser" doesn't need to include the schema name when they reference "tomtable".
It's much safer to grant access to objects based on a role... otherwise, anyone with a login can get to "public" tables. One thing to be careful of when using roles; some things can't be done- as in, you can't create a view on a table, if you only have access to the table via a role. You'd need explicit access on the table.
When you query all_tables, who is the real owner of the tables? Your username and schema name are one and the same, but you're allowed to have access into other schemas. SYS wins big-time because of the "select any table" system privilege. The only way a normal user can get to another schema's objects is by "grant select/update/insert/delete/etc on schema.object".
-Thomas H

Similar Messages

  • How to configure the schema name dynamically based on user input.

    configure the schema name dynamically based on user input.
    For ex:
    We have two schemas:
    Schema1  - base schema having 15 tables.
    Schema2 -  tables which is specific to modules. Having only 10 tables which is also available in Schema1
    Login to application using Schema 1
    Access a particlular module and select the country. Here country selection is identified.
    Based on the country selection, we need to connect the schema respectively.
    If the user selects France --> It should connect Schema1
    If the user selects Germeny --> It should connect schema2.
    Used: Eclipselink

    You may want to have a different persistence unit for each country, then you just need to switch persistence units, and can put the schema in your orm.xml file.
    You may also want to investigate EclipseLink multi-tenant support,
    http://www.eclipse.org/eclipselink/documentation/2.5/jpa/extensions/a_multitenant.htm
    You can the schema in a persistence unit in code using a SessionCustomizer and the tableQualifier.

  • User & Schema name of Export dump file

    I have an exported dump file. I dont have any log file of that export. I want to Import it in another system. How do I know concerned user or schema name of that dump file.
    Is there any way to know it???

    dbanirav wrote:
    I have an exported dump file. I dont have any log file of that export. I want to Import it in another system. How do I know concerned user or schema name of that dump file.
    Is there any way to know it???made with exp or expdp?
    what OS name & version?
    How do I ask a question on the forums?
    SQL and PL/SQL FAQ

  • Change schema's user name

    Isthere any way to change schema's user name. I have looked but couldnt find how to change. With "Alter user" name cant be changed.
    Thanks for the help...

    Hi,
    SQL> host exp system/oracle owner=scott file=c:\scottschema.dmp log=c:\scott.log
    Export: Release 10.1.0.2.0 - Production on Tue Dec 12 09:36:37 2006
    Copyright (c) 1982, 2004, Oracle.
    All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 -
    ProductionWith the Partitioning, OLAP and Data Mining options
    Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
    About to export specified users ....
    exporting pre-schema procedural objects and actions.
    exporting foreign function library names for user SCOTT.
    exporting PUBLIC type synonyms.
    exporting private type synonyms.
    exporting object type definitions for user SCOTT
    About to export SCOTT's objects ....
    exporting database links.
    exporting sequence numbers.
    exporting cluster definitions.
    about to export SCOTT's tables via Conventional Path .... .
    exporting table A 0 rows exported. .
    exporting table ABCDEFGHIJKLMNOPQRSTUVWXYZ 0 rows exported. .
    exporting table ABCDEFGHIJKLMNOPQRSTUVWXYZ1234 0 rows exported. .
    exporting table A_12345678901234567890123456$# 0 rows exported. .
    exporting table B 100 rows exported. .
    exporting table BIG 46968 rows exported. .
    exporting table BIG_TABLE 46967 rows exported. .
    exporting table BONUS 0 rows exported. .
    exporting table C 1000 rows exported. .
    exporting table D 1000 rows exported. .
    exporting table DEPT 4 rows exported. .
    exporting table E 1000 rows exported. .
    exporting table EMP 14 rows exported. .
    exporting table FINAL_OUTPUT. .
    exporting table Q 10000 rows exported. .
    exporting table SALGRADE 5 rows exported. .
    exporting table T 1000 rows exported. .
    exporting table TEST 7 rows exported.
    exporting synonyms.
    exporting views.
    exporting stored procedures.
    exporting operators.
    exporting referential integrity constraints.
    exporting triggers. exporting indextypes.
    exporting bitmap, functional and extensible indexes.
    exporting posttables actions.
    exporting materialized views.
    exporting snapshot logs.
    exporting job queues.
    exporting refresh groups and children.
    exporting dimensions.
    exporting post-schema procedural objects and actions.
    exporting statistics
    Export terminated successfully without warnings.
    SQL> select user_id,username from user_users;
    USER_ID USERNAME
    57 SCOTT
    SQL> select count(*) from session_privs;
    COUNT(*)
    81
    SQL> select count(*) from session_roles;
    COUNT(*)
    6
    SQL> set echo off
    SQL> set feedback off
    SQL> set heading off
    SQL> spool c:\scottpriv.sql
    SQL> select 'grant 'privilege' to newscott;' from session_privs;
    SQL>spool off
    SQL> spool c:\scottroles.sql
    SQL> select 'grant 'role' to newscott;' from session_roles;
    grant CONNECT to newscott;
    grant RESOURCE to newscott;
    grant IMP_FULL_DATABASE to newscott;
    grant SELECT_CATALOG_ROLE to newscott;
    grant HS_ADMIN_ROLE to newscott;
    grant EXECUTE_CATALOG_ROLE to newscott;
    SQL> spool off
    SQL> set heading on
    SQL> set feedback on
    SQL> set echo on
    SQL> select default_tablespace from user_users;
    DEFAULT_TABLESPACE
    TEST
    1 row selected.
    SQL> conn system/oracleConnected.
    SQL> create user newscott identified by newscott default tablespace test;
    User created.
    SQL>@c:\scottpriv.sql <>
    SQL>@c:\scottroles.sql <>
    SQL> host imp system/oracle fromuser=scott touser=newscott file=c:\scottschema.dmp log=scottimp.log
    Import: Release 10.1.0.2.0 - Production on Tue Dec 12 09:54:39 2006Copyright (c) 1982, 2004, Oracle.
    All rights reserved.Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - ProductionWith the Partitioning, OLAP and Data Mining optionsExport file created by EXPORT:V10.01.00 via conventional pathimport done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set. importing SCOTT's objects into NEWSCOTT. .
    importing table "A" 0 rows imported. . importing table "ABCDEFGHIJKLMNOPQRSTUVWXYZ" 0 rows imported. .
    importing table "ABCDEFGHIJKLMNOPQRSTUVWXYZ1234" 0 rows imported
    SQL>drop user scott cascade;
    SQL> select username,user_id from user_users;
    USERNAME USER_ID
    NEWSCOTT 5
    81 row selected.
    SQL> select count(*) from session_privs;
    COUNT(*)
    81
    1 row selected.
    SQL> select count(*) from session_roles;
    COUNT(*)
    6
    1 row selected.
    SQL>Try above scripts if it is help
    regards
    Taj
    Message was edited by:
    M. Taj

  • How to get the current schema name

    Hi,
    Can anybody please tell me how to get the current schema name, there is some inbuilt function for this,but i am not getting that. Please help me.
    Thanks
    Jogesh

    ok folks, I found the answer at Tom's as usual.
    http://asktom.oracle.com/tkyte/who_called_me/index.html
    I rewrote it into a function for kicks. just pass the results of DBMS_UTILITY.FORMAT_CALL_STACK to this function and you will get back the owner of the code making the call as well some extra goodies like the name of the code and the type of code depending on the parameter. This ignores the AUTHID CURRENT_USER issues which muddles the schemaid. Quick question, does the average user always have access to DBMS_UTILITY.FORMAT_CALL_STACK or does this get locked down on some systems?
    cheers,
    paul
    create or replace
    FUNCTION SELF_EXAM (
       p_call_stack VARCHAR2,
       p_type VARCHAR2 DEFAULT 'SCHEMA'
    ) RETURN VARCHAR2
    AS
       str_stack   VARCHAR2(4000);
       int_n       PLS_INTEGER;
       str_line    VARCHAR2(255);
       found_stack BOOLEAN DEFAULT FALSE;
       int_cnt     PLS_INTEGER := 0;
       str_caller  VARCHAR2(30);
       str_name    VARCHAR2(30);
       str_owner   VARCHAR2(30);
       str_type    VARCHAR2(30);
    BEGIN
       str_stack := p_call_stack;
       -- Loop through each line of the call stack
       LOOP
         int_n := INSTR( str_stack, chr(10) );
         EXIT WHEN int_cnt = 3 OR int_n IS NULL OR int_n = 0;
         -- get the line
         str_line := SUBSTR( str_stack, 1, int_n - 1 );
         -- remove the line from the stack str
         str_stack := substr( str_stack, int_n + 1 );
         IF NOT found_stack
         THEN
            IF str_line like '%handle%number%name%'
            THEN
               found_stack := TRUE;
            END IF;
         ELSE
            int_cnt := int_cnt + 1;
             -- cnt = 1 is ME
             -- cnt = 2 is MY Caller
             -- cnt = 3 is Their Caller
             IF int_cnt = 1
             THEN
                str_line := SUBSTR( str_line, 22 );
                dbms_output.put_line('->' || str_line);
                IF str_line LIKE 'pr%'
                THEN
                   int_n := LENGTH('procedure ');
                ELSIF str_line LIKE 'fun%'
                THEN
                   int_n := LENGTH('function ');
                ELSIF str_line LIKE 'package body%'
                THEN
                   int_n := LENGTH('package body ');
                ELSIF str_line LIKE 'pack%'
                THEN
                   int_n := LENGTH('package ');
                ELSIF str_line LIKE 'anonymous%'
                THEN
                   int_n := LENGTH('anonymous block ');
                ELSE
                   int_n := null;
                END IF;
                IF int_n IS NOT NULL
                THEN
                   str_type := LTRIM(RTRIM(UPPER(SUBSTR( str_line, 1, int_n - 1 ))));
                 ELSE
                   str_type := 'TRIGGER';
                 END IF;
                 str_line  := SUBSTR( str_line, NVL(int_n,1) );
                 int_n     := INSTR( str_line, '.' );
                 str_owner := LTRIM(RTRIM(SUBSTR( str_line, 1, int_n - 1 )));
                 str_name  := LTRIM(RTRIM(SUBSTR( str_line, int_n + 1 )));
              END IF;
           END IF;
       END LOOP;
       IF UPPER(p_type) = 'NAME'
       THEN
          RETURN str_name;
       ELSIF UPPER(p_type) = 'SCHEMA.NAME'
       OR    UPPER(p_type) = 'OWNER.NAME'
       THEN
          RETURN str_owner || '.' || str_name;
       ELSIF UPPER(p_type) = 'TYPE'
       THEN
          RETURN str_type;
       ELSE
          RETURN str_owner;
       END IF;
    END SELF_EXAM;

  • Schema name not present on filename for "Save Package Spec and Body"

    In versions previous to 3.0 EA, the filename defaulted to schema.object.sql when using the "Save Package Spec and Body" on the right click of the package/body. This appears to have disappeared. Also, it now defaults to the .PLS ext/type, which I prefer to save them as .SQL (which i can override, but it would be nice in the file type dropdown). Also, I had posted a suggestion about the actual file not including the schema name prefixing the object name when using the "Save Package Spec and Body". i.e. it does create or replace package reader_package instead of what it should be doing which is create or replace package schema.reader_package

    Would be nice indeed having the real name as default, and all supported PL/SQL types (as in the preferences) in the extensions dropdown.
    As for the schema name inside, I reckon that would do damage for more users than it would do good for others. But a preference would be best of course.
    K.

  • Need to include table name,schema name in select output

    I need to output the table name and schema name of the current user into a table.. I have tried including
    within a select statement..
    table_name,
    from user_tables
    where table_name='mnme';
    no rows returned

    Hi,
    Its in upper case 'MNME'
    Best.
    EA

  • To get rid of Schema name in output using DBMS_METADATA

    Hi all,
    Would someone be able to tell me how to get rid of the schema name output given by the below select stmt.
    Query
    Select Dbms_metadata.Get_ddl('FUNCTION','ACCOUNT_CODE')
    from dual;
    Result
    CREATE OR REPLACE FUNCTION "GOINGLIVE"."ACCOUNT_CODE" (PTransCode VarChar2,.............
    I checked for the documentation, but could manage to eliminate only storage clauses, tablespace etc. but not teh schema name.
    Please provide your advise on this.
    Thanks
    - Sandeep

    Which version are you on?
    In 10g, you can use DBMS_METADATA.SET_REMAP_PARAM to get rid of schema name:
    SQL> create table md_test(x int, y varchar2(10));
    Table created.
    SQL> declare
      2    l_ctx number;
      3    l_ctxt number;
      4    l_ddl sys.ku$_ddls;
      5  begin
      6    l_ctx := dbms_metadata.open('TABLE');
      7    dbms_metadata.set_filter(l_ctx, 'NAME', 'MD_TEST');
      8    l_ctxt := dbms_metadata.add_transform(l_ctx, 'MODIFY');
      9    dbms_metadata.set_remap_param(l_ctxt, 'REMAP_SCHEMA', user, null);
    10    l_ctxt := dbms_metadata.add_transform(l_ctx, 'DDL');
    11    dbms_metadata.set_transform_param(l_ctxt, 'SEGMENT_ATTRIBUTES', false);
    12    l_ddl := dbms_metadata.fetch_ddl(l_ctx);
    13    dbms_output.put_line(l_ddl(1).ddltext);
    14    dbms_metadata.close(l_ctx);
    15  end;
    16  /
    CREATE TABLE "MD_TEST"
       (    "X" NUMBER(*,0),
            "Y" VARCHAR2(10)
    PL/SQL procedure successfully completed.In 9i, you have to resort to some manual tricks (with REPLACE, probably):
    SQL> create table md_test(x int, y varchar2(10));
    Table created.
    SQL> declare
      2    l_ctx number;
      3    l_ctxt number;
      4    l_ddl sys.ku$_ddls;
      5  begin
      6    l_ctx := dbms_metadata.open('TABLE');
      7    dbms_metadata.set_filter(l_ctx, 'NAME', 'MD_TEST');
      8    l_ctxt := dbms_metadata.add_transform(l_ctx, 'DDL');
      9    dbms_metadata.set_transform_param(l_ctxt, 'SEGMENT_ATTRIBUTES', false);
    10    l_ddl := dbms_metadata.fetch_ddl(l_ctx);
    11    dbms_output.put_line(
    12      replace(l_ddl(1).ddltext, '"' || user || '".'));
    13    dbms_metadata.close(l_ctx);
    14  end;
    15  /
    CREATE TABLE "MD_TEST"
       (    "X" NUMBER(*,0),
            "Y" VARCHAR2(10)
    PL/SQL procedure successfully completed.
    SQL> select * from v$version where rownum = 1;
    BANNER
    Oracle9i Enterprise Edition Release 9.2.0.6.0 - ProductionHope this helps,
    Andrew.

  • What is table schema name?

    Hi,
    I was looking at DatabaseMetaData::getColumns() while searching for a way to get a table's column names and I run into these ugly params catalog and schemaPattern. Of course nowhere on the sun's site could I find a definition of these terms although they're used quite often in the API documentation. So I turned to a specific DBMS provider and found out that catalog is a fancy term for the system metadata. But what about the String schema param? I usually see a table's schema referred to as the "structure" of the table, what columns it contains of which types. But I've never known this "schema" can have a string name. Anyone so kind to explain it to me or better point me to a text that has definitions and explanations of the concepts used in the JDBC API documentation? And more generally for JDK where do you folks usually go when you want a simple explanation of how things work, not the dry listing of function and parameter names? Look at MSDN for example, it is both a good reference and a reasonable self-contained tutorial. Not that I praise Microsoft but...
    BTW I found that probably ResultSetMetaData is more suitable for my initial purposes, but still the questions bother me. So if you have any suggestion please let me know.
    Thank you in advance

    To answer your question, what is a table schema name?, it is the name of the schema that the table belongs to. If you have an Oracle database, MYDB, it will have at the very least two users which are SYS and SYSTEM, these are schema names, there are objects that exists in their schema. If you create a new user, JAKE, and then create a bunch of objects as JAKE, these objects are said to belong to the JAKE schema. All objects are like this, not just tables (indexes, sequence tables, triggers, etc.).

  • How to determine the schema name from stored function or procedure

    Hi all
    I need to find the way to determine the name of shema in which the given stored procedure residing. This SP is created with AUTHID CURRENT_USER what means that expression like SYS_CONTEXT('USERENV','CURRENT_USER') or SYS_CONTEXT('USERENV','CURRENT_SCHEMA') will be return the name of user or schema of user which calls given SP.
    can somebody help me?

    What is the problem you are trying to solve?
    Presumably, when you're creating a stored procedure, you know what schema owns it. So it's pretty trivial to simply create a local variable L_OWNER in your procedure, assign it the value of the schema owner, and then use that owner. Most people don't really need to figure out at runtime what they already knew at compile time.
    Barring that, you could inspect the data dictionary as user130038 suggested. That requires that you know the name of the procedure (which would likely also have to be a local variable that is initialized to a hard-coded value. And if there are multiple users that own procedures with the same name, it may not be reliable.
    Inspecting the call stack is the most reliable and dynamic approach. But it is also the most costly in terms or runtime performance and in terms of code complexity.
    Justin

  • Default schema names in multi-tier landscape

    Hi folks,
    We have an interesting problem due to having different named default schemas in each of our 3 hana systems.  For example lets say these are our default schemas in our development, staging, and production HANA systems;
    DEV_SCHEMA
    QA_SCHEMA
    PROD_SCHEMA
    Each of these replicating data from their corresponding SAP source systems.
    Now, we have a view that is developed on DEV hana box and uses DEV_SCHEMA.  When this view content is imported to QA or PROD we handle easily with schema mapping.  All is well and good although we are not really a fan of this different naming and us developers did not choose this naming (self defense plea here for us brilliant developers whom never make such mistakes... PS: HI LARS! - Go Germany!)
    Now we are setting up a connection from BW into HANA using system connection and inside this is a parameter called 'db user'.  Although it's called db user it's actually looking for a SCHEMA name.  If BW DEV is querying from HANA DEV this schema name would be DEV_SCHEMA.  However if BW_QA is querying from HANA_QA then the name would need to be QA_SCHEMA but in our BW landscape we are locked in QA and PROD and normally can not and/or do not want to edit objects in non-native systems.  Ideally what we need is our default schemas in HANA to have the same exact name throughout the HANA landscape.
    All this said, I can see that it would be great to re-name our entire HANA landscape however that would be a HUGE monumental undertaking as all systems would need to be re-replicated again (at least I think).
    Just curious if anybody else has named their schemas differently on each tier?  What are most people doing?  Naming the default schemas the same consistently or are you using schema mapping?
    Thanks,
    -Patrick

    Hi Luke,
    I am new to the project and there seems to be no original version.  At some point a bunch of the destination field names were changed on the admin console and errors resulted from it both due to mismatched joins and the use of two word field names.  I have documentation of the names for the set of tables in the function area but am having trouble with how everything matches up in the bottom half..  I'll keep working on it
    Z

  • OWB 10.1 Deploy Mgr. - Registration - schema name is grayed out, sometimes

    Environment:
    Repository - OWB 10.1.0.2 on UNIX (AIX 5.2)
    Target - Oracle 9.2.0.4 on UNIX (AIX 5.2)
    Question: I have several locations that have been registered in the past. When I right click a location and click on 'Register' in some cases the schema name comes up grayed out and I am unable to change it and other times it is open.
    Why is that and how do I change the schema name of a location?
    I have installed the new schema as a target through the runtime assistant and there is a working runtime repository in that instance.
    Any help is greatly appreciated.
    P.S. Yes, we are making plans to upgrade to 10.2 soon but not soon enough ;-)>
    -gary

    Hi,
    In order to edit/delete a location you need to unregister the location from all the Control Centers. A location might be registered to more than one Control Centers.
    Having said that if you have registered location A to Schema B in Control Center C, you need to unregister the location A from Control Center C.
    In case you have accidentally dropped the Schema B without unregistering the location A, then even if you unregister the location A from Control Center C, you will still see the user name and password fields grayed out. In that case you need to re-create the schema B, register the location A and then again unregister the location and then you will be able to edit it. Seems to be a bug in OWB.
    Regards
    -AP

  • Bug: numeric schema names not managed correctly

    If a schema name consists of numbers, the generated SQL will always fail.
    In this case, it should put double-quotes around the schema name.
    For example, dragging a table over to the query pane will generate a select statement,
    but since it does not enclose the schema name in double-quotes, the error
    "invalid table name" will be received when trying to run that query.
    I am using version 1.2.1 Build MAIN-32.13.
    Thank you.

    Well, checking the documentation (we are on 10gR2), I do note the following:
    "Nonquoted identifiers must begin with an alphabetic character...".
    So you are right. Alas, this was not something with which I was involved.
    Given that however, it would be a very user-friendly tweak to the product
    to make it more usable - remember, this is a circumstance in which the SQL
    generated by the tool is wrong, which does look bad as it is an Oracle product.

  • How to programatically change schema name for an application ? JDev10g

    I am using JDeveloper 10g 10.1.3.4
    What I am trying to do is: while connecting to the database instace with login/passwd credentials for a specific schema, being able to take in
    schema as a separate paramter and connect to that schema.
    Connecting to a database instace ORCL to the hr schema say with hr/hr
    supply a paramter schema_name: scott. and connect to the scott schema as the hr schema user.
    In SQL Plus* all you do is
    connect as hr/hr
    and then
    alter session set current_schema = scott.
    While developing an application that autheticates against database username/pwd credentials I was using the methodology
    as described on http://www.oracle.com/technology/products/jdev/howtos/10g/dynamicjdbchowto.html
    and http://radio.weblogs.com/0118231/stories/2004/09/23/notYetDocumentedAdfSampleApplications.htmlexample 14.*[Dynamic JDBC Credentials for Model 1 and Model 2|http://otn.oracle.com/products/jdev/tips/muench/dynamiccredentials/DynamicCredentials1013.zip]* [10.1.3.3] 2006, Upd: 17-MAY-2007 by Steve Muench
    In the DynamicJDBCBindingFilter that in the doFilter() method, I was trying to find a way to be able to specify the schema name
    as in sessoion.setAttribute(Configuration.&lt;SomeProperty&gt;, schema);
    is there any property/parameter that can be set to change the schema within the context of the application?
    because in all the code that i see there are attributes of 'Configuration' that are being set.
    So I don't think there is way for me to just write straight up jdbc code to
    create a connection and run the statement "alter session set current_schema = scott"
    and be able to pass the login credentials
    and connect to the schema I want to.
    Any help would be appreciated.

    Hi,
    I am not sure if JDBC really supports this. I found
    JDBC alter session set ...
    but this never got a success/failure statement.
    If you want to use a singe connection but different schema for users then you may want to have a look at proxy user authentication, which is exatly doing what you want - use a single user to get into the database and then have him mapped to his own schema to work in
    Frank

  • Prefixing sequence with schema name in generated sql on oracle

    Hi,
    We use kodo 3.4 with an oracle database in a J2EE environment.
    When we put on the kodo tracing during on of our testcases we see statements being generated like :
    select LOOPBAANPERIODESEQUENCE.NEXTVAL from DUAL
    When we check the rest of the statements we see :
    SELECT * FROM PC52290.EINDELOOPBAAN (EINDELOOPBAAN being a table)
    Is there any way to make kodo generate the following statement ?
    select PC52290.LOOPBAANPERIODESEQUENCE.NEXTVAL from DUAL
    Our kodo.properties we use :
    javax.jdo.PersistenceManagerFactoryClass=kodo.jdbc.runtime.JDBCPersistenceManagerFactory
    javax.jdo.option.Optimistic=true
    javax.jdo.option.RetainValues=true
    javax.jdo.option.NontransactionalRead=true
    kodo.jdbc.DBDictionary=kodo.jdbc.sql.OracleDictionary
    kodo.jdbc.ForeignKeyConstraints=true
    kodo.LicenseKey=<VALID_LICENSE_HERE>
    kodo.Log=DefaultLevel=WARN,SQL=TRACE,Runtime=WARN,Configuration=WARN
    kodo.jdbc.Schemas=PC52290
    kodo.PersistentClasses= ...
    An example of our mapping :
              <class name="LoopbaanPeriode">
                   <extension vendor-name="kodo" key="jdbc-sequence-factory" value="native"/>
                   <extension vendor-name="kodo" key="jdbc-sequence-name" value="LOOPBAANPERIODESEQUENCE"/>
    <extension vendor-name="kodo" key="jdbc-class-ind-value" value="1"/>
    <field name="beginDatum"           persistence-modifier="persistent" />
    <field name="statuut" persistence-modifier="persistent" />
    <field name="loopbaan"                     persistence-modifier="persistent"/>
    </class>
    regards,
    David De Schepper.

    Hi David,
    When faced with a similar problem, I wrote my own subclass of DBDictionary
    (in my case actually a subclass of OracleDictionary), and plugged it into
    kodo using the kodo.jdbc.DBDictionary property. My class overrode the
    following methods:
    public String getFullName(Table, boolean);
    public String getFullName(Index);
    Then at runtime, these methods stuffed in the correct Schema name for
    certain tables and indexes, based on values yoinked from some user
    properties.
    Not sure if this will help or not in your case.
    Cheers!
    .droo.
    On 4/9/06 2:48 PM, in article [email protected], "David De
    Schepper" <David De Schepper> wrote:
    yes that works but that is not an option for us.
    We have an oracle schema for each developer on our team and don't want to
    hardcode it in our mapping file (for obvious reasons)
    FYI : kodo 4.0.1 does it correctly (generates PC52290.LOOPBAANPERIODESEQUENCE)
    but since i have problems doing the upgrade to kodo 4.0 (with as few code
    changes as possible) i'm going to have to advice my company not to do the
    upgrade.
    (In case you are intersted or have some time :
    http://forums.bea.com/bea/thread.jspa?forumID=500000029&threadID=600017073&mes
    sageID=600041994#600041994)

Maybe you are looking for