{"id":81,"date":"2005-08-05T16:09:59","date_gmt":"2005-08-05T23:09:59","guid":{"rendered":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/?p=81"},"modified":"2005-08-05T16:09:59","modified_gmt":"2005-08-05T23:09:59","slug":"using-a-different-schema-than-username-in-owb","status":"publish","type":"post","link":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/2005\/08\/05\/using-a-different-schema-than-username-in-owb\/","title":{"rendered":"Using a different schema than username in OWB"},"content":{"rendered":"<p>It&#8217;s not uncommon to set up a special Oracle account to access data in another schema.  This is common practice and a good practice, especially when it comes to reporting users.<\/p>\n<p>You want to give a reporting user a limited view of the system; only SELECT access on known interface tables or only SELECT on tables in exactly one other schema.  This helps protect the usually powerful schema owner (<b>ACTUAL_SCHEMA<\/b>) from being widely disseminated.  This won&#8217;t be new to any bayon blog readers.<\/p>\n<p>The question is:<\/p>\n<blockquote><p>How does one set up an OWB Oracle Data Source Module (<b>ACTUAL_SCHEMA<\/b>) that uses one username and password (<b>LOW_PRIV_USER<\/b>) for authentication but access the objects needed (<b>ACTUAL_SCHEMA<\/b>)?\n<\/p><\/blockquote>\n<p>The answer is:<\/p>\n<blockquote><p>You can&#8217;t in OWB 10gR1, but you can in OWB 10gR2 (in beta).  <i>Note: OWB Product Management emailed a solution in 10gR1 (see below)<\/i>\n<\/p><\/blockquote>\n<p>I&#8217;d love to be wrong, so if anyone would like to send along a solution I&#8217;d be happy to post it here.<\/p>\n<p>I reviewed the link area (for importing metdata), nothing!  Ok, so perhaps it&#8217;s just for metadata.  It&#8217;s not the end of the world as long as we can register when a different username\/schema pair.<br \/>\n<img decoding=\"async\" src=\"\/entry_images\/owb_10gR2_schema_user_r1_link.jpg\" border=\"0\"><\/p>\n<p>However, you can&#8217;t register using a different schema than the user either.<br \/>\n<img decoding=\"async\" src=\"\/entry_images\/owb_10gR2_schema_user_r1_reg.jpg\" border=\"0\"><\/p>\n<p>Last thought was to try and &#8220;Configure&#8221; a location, but you can&#8217;t do that.<br \/>\n<img decoding=\"async\" src=\"\/entry_images\/owb_10gR2_schema_user_r1_grey_config.jpg\" border=\"0\"><\/p>\n<p>I&#8217;m starting to sound like an Oracle employee, but the next version is great.  This whole process was a snap with Paris.<br \/>\n<img decoding=\"async\" src=\"\/entry_images\/owb_10gR2_schema_user.jpg\" border=\"0\"><\/p>\n<p>If anyone has figured out how to do it in 10gR1 please <a href=\"mailto:ngoodman@bayontechnologies.com\">email me<\/a> and let me know.<\/p>\n<p><i>UPDATE: The way to accomplish this in OWB 10gR1 is to configure the <b>mapping<\/b> to not use the LOCATION but to use a custom DBLink or schema prefix instead.  I&#8217;ll try it and add a screenshot of this process, but basically this allows you to override the location for every mapping.  Thanks Nikolai! <\/i><\/p>\n","protected":false},"excerpt":{"rendered":"<p>It&#8217;s not uncommon to set up a special Oracle account to access data in another schema. This is common practice and a good practice, especially when it comes to reporting users. You want to give a reporting user a limited view of the system; only SELECT access on known interface tables or only SELECT on [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[10],"tags":[],"_links":{"self":[{"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/posts\/81"}],"collection":[{"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/comments?post=81"}],"version-history":[{"count":0,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/posts\/81\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/media?parent=81"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/categories?post=81"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/tags?post=81"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}