Assigning a default schema to a user.

In Oracle can I assign a default schema to a user without using the later session command?
Is there a ALTER USER setting where I can assign a user a default schema?

Buddy,
To answer to your question.
1. First grant select any table or "grant select on all tables of user 'ELLIPSE' to the user "094137".
2. Later to access schema ELLIPSE's objects, from "094137" user, you ll have to create public synonym to all of the tables in ELLIPSE schema.
3. This way, the user "094137" can access all tables in SCHEMA ELLIPSE, with out specifying(prefixing) the schema name
Hope this helps
Thanks
I would like the user "094137" to logon and have access to the tables in another schema "ELLIPSE" with out qualifying the table name with "ELLIPSE".
The user "094137" has no objects of her own and only accesses the object of the schema "ELLIPSE".
Is there a direct way of assigning a user (with no objects) to have a default schema of another users (without the alter session default schema statement)

Similar Messages

Assigning a default value to a user property

Hi everyone,
do you know how can I assign a default value to a user property? It would be great if I should be able to assign it from the administration without writing any code (like profile web services...).
Thank you!
Alberto Marchiaro

Hi Alberto,
I don't think you can currently do this. In other words you can't set a default value for some object property and have it subbed in when no better value is available.
You can however create a default profile, and set values for the object properties assigned to users (You do this by going to the "Default Profiles" manager). You can then edit the "Default Profile" that is already there (or create a new one), and edit the "Properties and Names". Set the value field to whatever you'd like to be copied by default.
Once done, all new users that are created via a User Synchronization job will have this default profile. The changes will not apply to users that were previously created. If you created a new Default Profile in the Default Profiles Manager, then you need to goto the Authentication Source that you are doing your sync's from and pick which profile you'd like to use for All Groups. You can also create custom Default Profiles for various groups.
Hope this helps,
Akash

Is there a way to change the default schema for a user?

I'd like to have, for example, user SCOTT access data from schema XYZ by default. From SQL Developer, I can do this via
alter session set current_schema = XYZ ;
But "alter" operations are not allowed via JDBC. How can I do this from the application layer?
Thanks.
-Tim

do it right the first time around, use synonyms. Don't be presumptive. There may be any number of reasons for choosing to change schema instead of using synonyms. Not the least of which is that it is a more robust approach because we don't have to keep synonyms in sync with an application owner's objects.
Of course the GRANT model has to be correct but that is true either way.
Cheers, APC

Confused about the default schema

Hi,
I am a little bit confused about the schema concept.
I want to create a new schema called APP and then create several users and roles based on the schema APP. The default schema for the users should be APP achema.
How can I make the schema APP the default schema for the new users that I am creating?
I feel that there are some schema design concepts that I have to learn. Is there any resource on the internet that I can read and learn more about oracle schema design best practices?
Any help would be appreciated,
Ali

A schema holds object definitions, and in the case of table & index objects the schema also holds the data.
A user owns the schema.
Therefore the user 'owns the definitions (including any functions, procedures, sequences, tabels, etc.)
Other users may be granted access to some, or all, of the objects in a schema. This is done through the 'GRANT ...' command. For example, consider the following steps:
1) create user app_owner
2) create table object test owned by the app_owwner
3) create user app_user
4) grant select, update, insert and delete on app_owner's test table to app_user
5) add synonyms to avoid needing to qualify the table's schema name.
done as follows:
oracle@fuzzy:~> sqlplus system
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Apr 3 20:07:32 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Create the app owner userid. Note there is no need to ever log in to that user, even to create tables.
SQL> create user app_owner
2 identified by xyz
3 account lock
4 quota unlimited on users
5 default tablespace users
6 temporary tablespace temp;
User created.
Creating objects in a schema can be done by providing the schema name, or by switching schema in newer versions of Oracle
SQL> create table app_owner.test ( t number );
Table created.
Create a userid that will access the table. Set that userid up to access the database and (for future) give it the capability to create it's own synonyms
SQL> create user app_user
2 identified by xyz
3 temporary tablespace temp;
User created.
SQL> grant create session to app_user;
Grant succeeded.
SQL> grant create synonym to app_user;
Grant succeeded.
Now give the user access to the objects
SQL> grant select, update, insert, delete on app_owner.test to app_user;
Grant succeeded.
Let's test it out. Insert by qualifying the schema name on the object, then create a synonym to avoid using schema, and try it all using the synonym
SQL> connect app_user/xyz
Connected.
SQL> insert into app_owner.test values (4);
1 row created.
SQL> create synonym test for app_owner.test;
Synonym created.
SQL> insert into test values (3);
1 row created.
SQL> select * from test;
         T
         4
         3
SQL> Note that some people want to use PUBLIC grants and PUBLIC synonyms. This is a real bad idea if you want to ensure long term security of the data and want to host several different applications in the same Oracle instance.
This, and a whole lot more, is in the 'Concepts' manual for your version of the database at http://docs.oracle.com

Changing Users default Schema

Hello,
I'm trying to add a new user to my DB giving him the Schema of an old user as his default Schema.
Can somebody tell me how to change User2's default schema to User1?
Thanks in advance,
Gregor

Coolhands_99 wrote:
I created all the users from the command line and I used -k legacy option for the calendar. At this point everything is working fine the user calendars I imported from Cal server 6.0 schema 1 all show up and work like they should. Once I assign a service package to a user account it changes their default calendar to the hosted format. Now my users have two calendars their default (hosted format) which is blank and their imported (legacy format) that has all the calendar entries. It sounds like you missed this step during your move to calendar server 6.2/schema 2:
http://docs.sun.com/app/docs/doc/819-2656/6n4ua512a?a=view
"Configuring Calendar Server for Hosted Domain Support"
I've changed /opt/SUNWcomm/data/WEB-INF/classes/sun/comm/cli/server/servlet/ resource.properties from switch-caltype=hosted to switch-caltype=legacy and restarted the web container but no luck.These settings control how UWC log's into calendar server, i.e. as uid (legacy) or [email protected] (hosted) - it sounds that your problem is related to how calendar server stores to data instead.
Regards,
Shane.

Assigning Default Role to New Users created

Hi
How can we assign a default Role to any new User created.
This Role should automatically get assigned whenever a new User is created.
Regards

Hello,
for ABAP Stack users you can just create a reference user with the according roles and copy new users from it.
Regards
Christian

Schema not imported to the default tablespace of the user

I exported a schema. Then when I tried to import it in an existing schema, all the objects are successfully imported. But they are not imported in the default tablespace of that particular user. Why? How can I force the import to the default tablespace of that user?

Did you attempt to import the objects into a new schema or into the existing one? If you are attempting to migrate the objects to a new schema you need to use the parameters:
fromuser=<old_schema> touser=<new_schema>
Or if you are attempting to migrate the objects to a new tablespace pre-create them as described above and import with the ignore=y.
Message was edited by:
klichten

How to Assign a default value and Increement in my Target table ........?

Hi,
In my target table I want to Increment a value and store it in the table ........
the increement shud start frm ...........5001,5002,5003..................etc
How can I achieve this...........?
I created an numeric Variable and in assigned the default as 5000 nad action as Historize.........
In the target Datastore ......I assigned VAR+1.......
but in the Target column I got 5001 for all the columns........
Which way is the best way to deal with the Variables.......
Thanks
AK
Message was edited by:
AK2008

Hi Gurusank and Micropole,
Thanks for reply and info.....
I am trying out one of the solutions first........
Gurusank,
I have created a sequence........whether I need to mention the schema and table name ,column.........also ( I gave all the information) and Increement column =1 and saved it .......
Then I follwed the procedure as u have mentioned .....
And in the Target field also I gave the same the same.......for tat column I gave choose (target for execution).
And I directly ran the interface ..........
I got the folowing Error:
287 : 42000 : java.sql.SQLException: ORA-02287: sequence number not allowed here
java.sql.SQLException: ORA-02287: sequence number not allowed here
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)
     at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:633)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1086)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2984)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3057)
     at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execStdOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.g.y(g.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Thread.java:534)
Could u plz let me know where I am doing the mistake
Thanks
AK

How to assign the default value to search parameter

Hi Experts,
I am using search view , In this I have 5 parameter lets say Transaction Type, Partner No. etc... Now I want to assign a default value to transaction type ( lets say TA) . User should be able to see this default value in the transaction type field before pressing search button.
How can I do it?
My second problem is: I have configured this search view using configuration tool but I want to assign only one value to transaction type (i.e. user should not be able to add new row in the search criteria for the transaction type by using + sign) but in rest 4 fields he can add new row and search based on that.
Note: I am using only "Is" criteria .
Any pointer will be helpful for me
Thanks and regards,
Sandeep

Hi Sandeep,
For the default search values, here is a solution. You have to redefine the method GET_VALUE1 of the context node
For example if it is the BP search (component BP_HEAD_SEARCH) context node is your enhanced class: ZL_BP_HEAD__MAINSEARCH_CN00
METHOD get_value1.
CALL METHOD super->get_value1
    EXPORTING
      attribute_path = attribute_path
      iterator       = iterator
    RECEIVING
      value          = value.
TRY.
*     Delegate operation to selection parameter
      DATA: current TYPE REF TO if_bol_bo_property_access.
      IF iterator IS BOUND.
        current = iterator->get_current( ).
      ELSE.
        current = me->parameter_collection->get_current( ).
      ENDIF.
      IF current->get_property_as_string( iv_attr_name = 'ATTR_NAME' ) EQ 'XXX'.
        IF value IS INITIAL.
          value = 'Your default value'.
        ENDIF.
      ENDIF.
    CATCH cx_root.
ENDTRY.
ENDMETHOD.
where XXX is the name of the field.
Default value will then appear in your search field, but you are still able to modify it if you want...
Regards,
Fabian

How to assign a default value to a query variable

If I create a query, and it contains a variable that I want the user to input, can I also assign a default to that variable which the user will see when they run the query? If they make no selection it would use the default instead of the user input?
Thanks

Hello Peter - One way might be by using the "CASE" function inside the SQL.
It might be good for you to post your curent SQL here in the forum and a bit more explanation of what you are looking for. That way folks can review and provide suggestions on how to accomplish on how it can be done...
Zal

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

How grant all the privilege of a specific schema to a user?

How grant all the privilege of a specific schema to a user?
I already create a new schema and import the neccessary data for that schema.
Now I want to assign all the privilege for that schema to user HR (let user HR become the owner of that schema). How to deal with it?
Edited by: qkc on May 13, 2011 10:45 AM

qkc wrote:
How grant all the privilege of a specific schema to a user?
I already create a new schema and import the neccessary data for that schema.
Now I want to assign all the privilege for that schema to user HR (let user HR become the owner of that schema). How to deal with it?
Edited by: qkc on May 13, 2011 10:45 AMThere is no way - by definition - that one user can "become the owner" of another schema. A schema is, by definition, the collection of objects that belong to one owner.
but perhaps that is just semantics in the context of what you really want.
use sql to build sql:
spool doit.sql
select 'grant select on someuser.' || table_name || ' to someotheruser;'
from dba_tables
where owner = 'SOMEUSER';
spool off

LT31 - Default print code at User Level

Dear All,
Is it possible to default PRINT CODE(Print control data) in LT31 t-code at user level. Thanks in advance.
Regards
Ramprakash

In WM is in general no user-specific printing, but SAP offers 2 workarounds see the details in the KBA 1847818 - Unable to assign a specific printer to a user when printing Transfer Orders in WM

Change default schema

HI All,
We are in process of deploying "SAP Business Intelligence Adoption rapid-deployment solution" and we have a schema which is already created and didn't use the option "Allow multiple usage" during the time of creation, once we import modules provided by SAP there are some models which are named by SAP predefined schema,
I need to know what is the role I need to grant to out BW developers to change the default schema of these models.
Thanks in advance,
Shanaka.

All of the application data is in one schema. e.g. APPDATA. however I don't have the password for the APPDATA user, it is controlled by the DBAs. As a developer, I have a DEVUSER account and password. And the DEVUSER is configured with the appropriate access to the APPDATA schema by the DBAs.
The way I work right now, I connect to the database using the DEVUSER username/password, and I can navigate to the APPDATA schema through the "Other Schemas". I would like an option in the Connection properties that I can specify that APPDATA is my default schema, and the DEVUSER schema would be accessible from "Other Schemas".
I see this field as optional. If it is not entered, then the user's schema is used.
I hope that better explains things.
Randy

Changing default schema

Hi:
I would like to know if there is a way to change the default schema a user references. For example, I login as user "bill" with a schema associated with that user. But I want to reference the tables in someone else's schema, maybe user joe's schema, as the default when I write my queries.
I can do it with something like...
select col1 from joe.tbl1 where col2 > 5;
Is there a way to change the default schema to "joe" so that I don't have to prefix every table name reference with "joe."?
Thanks in Advance

You can use
ALTER SESSION SET CURRENT_SCHEMA = joe
This will not give you any access to any object owned by joe that you could not already access by using joe.name, but you will not need to add the joe.
HTH
John

Assigning a default schema to a user.

Similar Messages

Maybe you are looking for