Public synonym in Expdp

Similar Questions

• 4.1EA2 - overview of Code does not take into account public synonyms

  Hello there,

  I think that the completion of the tablenames in the modified spreadsheet of sort it ignores now public synonyms.

  When I type

  Select * from user_

  and press CTRL-space I get SYS.user_tables SYS.user_tab_columns etc. It's a little embarrassing.

  Now the question is, can I code insight also offer public synonyms? And if not can I at least get the usernames lowercase?

  Kind regards

  dhalek

  Run

  the hidden value of param querySynonyms = true

  command to activate the thesaurus in code insight. This has changed due to the execution of view poor synonyms dictionary in 12 c with insight omitting guest more important objects tables, views and pl/sql modules.

  Also, make sure that

  Preferences-> completion Insight-> change case as long as you type = None

  then the object names would be in the same case that they extracted from the dictionary (upper case).

• Public synonyms in a pluggable database deletion

  I have a base Oracle container 12 c with pluggable databases in it.  In a pluggable data bases, I uninstalled OLAP by running the following scripts:

  SQL > @%oracle_home%/olap/admin/catnoamd.sql

  SQL > @ /olap/admin/olapidrp.plb% oracle_home %

  SQL > @ /olap/admin/catnoxoq.sql% oracle_home %

  SQL > @ /olap/admin/catnoaps.sql% oracle_home %

  After you run the scripts, I then generated SQL statements to remove invalid OLAP synonyms, by executing the following:

  Select ' drop public synonym ' | object_name | ';'

  from dba_objects

  where <>of status "VALID."

  and owner = 'PUBLIC '.

  and object_type = 'SYNONYM '.

  and object_name like '% OLAP % ';

  When I run the SQL statements resulting in the snap-in data base, I get the following error for each of them:

  ERROR on line 1:

  ORA-65040: operation not allowed a pluggable database

  If I switch back to the ROOT of PEH container $ and executes the same statements, I get the following error:

  ERROR on line 1:

  ORA-01432: due public synonym being abandoned does not exist

  How can I remove these invalid public synonyms for my snap-in database?

  I think you're right. I re-read the note that I mentioned above. Even uninstalling an option is not supported for a CBD so far. Only option is to disable it. Second option is to create a non - CBD, uninstall option is not required and then plug it into a CBD.

  Salman

  ----------

  http://salmandba.blogspot.com

• Privileging the public synonym over schema object

  Hello

  I have a request.

  I logged in a scheme called "SCOTT."

  I have a table called 'EMP '.

  Now, I created a view called "EMP_D" with the addition of more of a few columns.

  Now I create a public synonym 'EMP' pointing to display "EMP_D".

  Now, I'm pulled the query in the schema "SCOTT."

  Select * from EMP

  I want that data to the EMP_D view.

  How to get there?

  Thanks in advance

  S. Jean-Charles

  user629814 wrote:

  My question is

  is it possible to prioritize the resulting public synonym of the same schema?

  Its only for a solution.

  This is called "name resolution" and is documented here: http://docs.oracle.com/cd/B28359_01/server.111/b28310/general008.htm#ADMIN11561

  1 oracle database attempts to qualify the first piece of the name referenced in the SQL statement. For example, in scott.emp , scott is the first piece. If there is only one piece, the piece is considered to be the first piece.

  1. In the current schema, the database looking for an object whose name matches the first part of the name of the object. If it does not find such an object, it continues with step b.
  2. The database looking for a public synonym that matches the first part of the name. If it does not find one, it continues with stepc.
  3. ...
     

  So if you have a schema object with the same name as a public synonym, oracle will always use first the schema object.

  Your only chance would be to rename the schema object or use another schema.

• 2 various CARS: same Public Synonyms on the same 2 diagrams - any interaction?

  I'm having a senior moment.

  I have not worked with public synonyms that often, so I just want to make sure I got it right.

  If you have two instances: Instance1 and Instance2

  They both live on the same Oracle RAC cluster.

  Intance1 and Instance2 have a schema named FRED.  Both of them have a synonym Public THISTABLE for FRED. THISTABLE

  Now, I want to just make sure that the public synonyms do NOT connect between two different, although instances on the same RAC system, right?

  Someone on Instance2 inserting in fred.thistable is ONLY for this instance, instance1 do not affect all, correct?

  You would have to do something like this, essentially a database link between them and could have a public link THISTABLE on Instance2 pointing to FRED. THISTABLE on Instance1... but simply want to make sure that I understand that only a dblink between two patterns on the two bodies will... allow traffic/access between the two bodies and public synonyms on their own will not cross the instance gap, even with two instances on the same cluster.

  Once again, senior moment here and just want to make sure I have it directly.

  Thanks in advance,

  Cayenne

  This case I put in place the same pattern of FRED and the same FRED table name. TABLEAUCETTE on the database instance instsqa... There is no link between the two with this public synonym on instdev. The only way you could link the two instances and schemas for the table would be by a... correct database link?

  Yes. You got right.

  Take CARS out of it.  It's the same as if you had 2 databases one-off names instdev and instqa.

  Post edited by: Brian Bontrager

• public synonyms

  Hello
  
  my database name is sch.in I have two patterns named ownr and database user.
  
  I've created tables, packages in ownr. I have to offer subsidies to these tables and packages to the schema of the user.
  
  If I create public synonyms for all tables and packages in the ownr schema are there the subsidies needed to access these objects from the user scehma?

  user10447332 wrote:
  Hello

  my database name is sch.in I have two patterns named ownr and database user.

  I've created tables, packages in ownr. I have to offer subsidies to these tables and packages to the schema of the user.

  If I create public synonyms for all tables and packages in the ownr schema are there the subsidies needed to access these objects from the user scehma?

  YES, in all THAT Oracle is FORBIDDEN; except as explicitly granted.

  SYNONYM is NOT a GRANT

  Handle: user10447332
  Status level: Beginner
  Join date: October 20, 2008
  Messages total: 322
  Total Questions: 215 (194 pending)

  Why so MANY unanswered questions?

• How to revoke all privileges on a public synonym of a user

  How to revoke all privileges on a public synonym of a user in 9i?

  you know the difference between PRIVATE and PUBLIC means?

  Public synonyms are accessible to all users.
  Private is accessible only inside its schema.

  If you do not want this user, use this synonym drop it and create a synonym in other schemas where users need.

• How to check what are the objects using this public synonym?

  Hi Experts
  
  Currently, I have a public synonym, WORK that is created for WORK table in the schema of the BRAND: "synonym PUBLIC EMPLOYMENT BRAND. JOB. "
  SELECT THIS OPTION. WORK is granted to the TOM_UPDATE (a role): GRANT SELECT ON MARK. JOBS AT TOM_UPDATE;
  
  I am using TOAD 9.6.1.1 and I wanted to drop the public synonym but I am not able to see that another object in the database uses this public synonym, JOB.
  
  Help, please.

  moslee wrote:
  Hi Experts

  Currently, I have a public synonym, WORK that is created for WORK table in the schema of the BRAND: "synonym PUBLIC EMPLOYMENT BRAND. JOB. "
  SELECT THIS OPTION. WORK is granted to the TOM_UPDATE (a role): GRANT SELECT ON MARK. JOBS AT TOM_UPDATE;

  I am using TOAD 9.6.1.1 and I wanted to drop the public synonym but
  I am not able to see that another object in the database uses this public synonym, JOB.

  The objects are not "use the synonym".
  The code use synonym to access object.

  use grep allows you to browse the source code that resides in your repository

• Which granted CREATE a PUBLIC SYNONYM for user SCOTT?

  version: 11.2.0.3
  Operating system: Solaris 10
  
  Auditing is enabled in our database.
  

  SQL> show parameter audit_trail
   
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  audit_trail                          string      DB

  Of DBA_SYS_PRIVS, we have confirmed that one of our DBA colleagues gave some risky privileges like CREATE PUBLIC SYNONYM, SELECT ANY TABLE... etc. to the user SCOTT.
  
  We would like to find out 2 things
  1. the SQL GRANT
  2. the date and time on which the statetement GRANT was pulled
  
  
  How can we find it?

  Y.Ramlet wrote:
  version: 11.2.0.3
  Operating system: Solaris 10

  Auditing is enabled in our database.

  SQL> show parameter audit_trail
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  audit_trail                          string      DB
  

  Of DBA_SYS_PRIVS, we have confirmed that one of our DBA colleagues gave some risky privileges like CREATE PUBLIC SYNONYM, SELECT ANY TABLE... etc. to the user SCOTT.

  We would like to find out 2 things
  1. the SQL GRANT

  You will have no SQL in the audit trail, because you have not configured the parameter correctly. You must audit_trail = db, extended to get the SQL code.

  2. the date and time on which the statetement GRANT was pulled

  You will have anything unless you have enabled auditing for the instruction given with
  Check create public synonym;

  How can we find it?

  You can't until you configure the audit in an appropriate manner.

• Public synonym for DBA only?

  Is it true that only DBA can create public synonyms?
  Or is it better for a DBA to publish it rather than other users? Is it because it is the responsibility of the DBA or what? Thank you.
  
  Published by: 801264 on December 17, 2010 20:35

  Everyone can 'CREATE a PUBLIC SYNONYM':
  http://download.Oracle.com/docs/CD/E11882_01/server.112/e17118/statements_9013.htm#i2155015

  And it should be someone who knows what is happening in all of the database. Sometimes it's s/n, but above all, there is a technical project manager who knows the need for application much better.

• PUBLIC SYNONYM - strange behavior

  I just organized a test on SQL queries for my students.
  
  It is based on four tables in a schema, and I created public synonyms for each table and read privilege to the PUBLIC, for example
  
  Staff CREATE a PUBLIC SYNONYM FOR testuser.staff
  GRANT SELECT ON testuser.staff to PUBLIC
  
  All the 150 + of my students have exactly the same roles and privileges, and yet two could not access the table of personnel without to refer to him as testuser.staff. They were able to access as provided for in the past.
  
  Has anyone encountered this before? I can't imagine that it's something to do with 60 students hit the synonym even at the same time, but I wonder.
  
  Brian
  
  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
  PL/SQL Release 11.2.0.1.0 - Production
  CORE 11.2.0.1.0 Production
  AMT for 64-bit Windows: Version 11.2.0.1.0 - Production
  NLSRTL Version 11.2.0.1.0 - Production

  Hello

  Both users apparently have their own tables (views, synonyms, or other objects) called the STAFF.

  What kind of results do get when they use the unqualified name, like this

  SELECT  last_name
  FROM    staff;
  

  ? "If they get"ORA-00904"'Name': invalid identifier", it might be because their own staffing table is not a column named LAST_NAME.

  A name to your own schema takes precedence over a PUBLIC synonym. It makes sense: you don't want all your own queries on your own STAFFING table to stop just because someone used the same name for a public synonym.

• name of the permission for ' drop public synonym '.

  We fall synonymous public as:

  GRANT DROP PUBLIC SYNONYM TO User1;

  How the permission/role is named to run this statement?
  What table I can query to see if my connected user has this right?
  I googled but did not.

  You must DROP PUBLIC SYNONYM privilege.

  You can determine if your username has this privilege by running the following query:

  SELECT *
  FROM   dba_sys_privs
  WHERE  grantee   = 'your user here'
  AND    privilege = 'DROP PUBLIC SYNONYM'
  ;
  

• no access Public Synonym

  create or replace procedure proc_s
  -return varchar2
  is
  v_Name varchar2 (20);
  Start
  -immediate execution "select name from r_temp where id = back 4: I ' using v_name;"
  SELECT name in v_name from r_temp where id = 4;
  -return (v_name);
  dbms_output.put_line (v_Name);
  end;
  
  r_temp is the public synonym but this code generates the PL/SQL compilation error: ORA-00942: table or view does not exist
  While that select * from r_temp code to return all rows

  But: the synonym is pointing to an underlying object: table.

  "You can reference only synonymous with another user by using the privileges of the object that you got." For example, if you have the right to SELECT for the synonym of jward.emp, then you can query the synonym of jward.emp, but you cannot insert rows using the synonym of jward.emp. »
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/views.htm#sthref3138
  Where my previous question.

• What can I do for the creation of a public synonym view?

  Hi people,
  I create a public synonym of another object to users
  
  SQL > create public synonym PAPD for scott.dept;
  
  
  The synonym is created.
  
  so I tend to create a view of this public syn
  
  SQL > create view vpdep in select * from PAPD.
  Create view vpdep in select * from PAPD
  *
  ERROR on line 1:
  ORA-01031: insufficient privileges
  
  I have the privilege to create view.also, I can create views of a public synonym for my own ex objects.for,
  
  SQL > create public synonym cdep for dept.
  
  The synonym is created.
  
  SQL > create view vcdep in select * from cdep;
  
  Created view.
  
  What could be the reason behind this? is there any privilege required to me.pls suggest me.
  
  Concerning
  VIDS

  Hi vidusnat!

  It is onlinedocumentation to Oracle:
  >
  Privileges required to create views

  To create a view, you must meet the following requirements:

  You must have been granted one of the following system privileges, either explicitly, or by a role:
  o CREATE The VIEW system privilege (to create views in your schema)
  o The CREATE ANY VIEW system privilege (to create a view of another user schema)
  You must explicitly obtained one of the following privileges:
  o the SELECT, INSERT, UPDATE, or DELETE object privileges on all objects in the view's underlying base
  o SELECT it ANY TABLE, INSERT a WHOLE TABLE, UPDATE ANY TABLE or DELETE ANY TABLE access privileges

  In addition, in order to grant access to your display of other users, you must have privileges to object to the base with the OPTION GIVING clause objects or system privileges with ADMIN OPTION clause. If you do not, users cannot access your view.
  >

  I hope that this will bring a little light in the darkness!

  Yours sincerely

  Florian W.

• How Public synonym works.

  When a search is done in data in a table via a public synonym, not the associated table, the index is used or not. I think he did, but I want to be sure, can someone also confirms this.
  
  Thank you

  Hello

  Yes, of course public synonyms use underlying indices. Its very simple test.

  SQL> select * from v$version;
  
  BANNER
  ----------------------------------------------------------------
  Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
  PL/SQL Release 10.2.0.4.0 - Production
  CORE    10.2.0.4.0      Production
  TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
  NLSRTL Version 10.2.0.4.0 - Production
  
  SQL>
  SQL>
  SQL> create table t as select rownum x from dual connect by level <=10000;
  
  Table created.
  
  SQL> exec dbms_stats.gather_table_stats(user, 't');
  
  PL/SQL procedure successfully completed.
  
  SQL> create index t_idx on t(x);
  
  Index created.
  
  SQL> create public synonym pub_t for test.t;
  
  Synonym created.
  
  SQL> set autotrace traceonly exp
  SQL> select * from t where x = 5;
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 2946670127
  
  --------------------------------------------------------------------------
  | Id  | Operation        | Name  | Rows  | Bytes | Cost (%CPU)| Time     |
  --------------------------------------------------------------------------
  |   0 | SELECT STATEMENT |       |     1 |     3 |     1   (0)| 00:00:01 |
  |*  1 |  INDEX RANGE SCAN| T_IDX |     1 |     3 |     1   (0)| 00:00:01 |
  --------------------------------------------------------------------------
  
  Predicate Information (identified by operation id):
  ---------------------------------------------------
  
     1 - access("X"=5)
  
  SQL> select * from pub_t where x = 5;
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 2946670127
  
  --------------------------------------------------------------------------
  | Id  | Operation        | Name  | Rows  | Bytes | Cost (%CPU)| Time     |
  --------------------------------------------------------------------------
  |   0 | SELECT STATEMENT |       |     1 |     3 |     1   (0)| 00:00:01 |
  |*  1 |  INDEX RANGE SCAN| T_IDX |     1 |     3 |     1   (0)| 00:00:01 |
  --------------------------------------------------------------------------
  
  Predicate Information (identified by operation id):
  ---------------------------------------------------
  
     1 - access("X"=5)
  
  SQL> set autotrace off;
  SQL>