Dynamic prefix of schema name in PL/SQL objects

I have a requirement where schema name would be passed as a parameter to the procedure and I am supposed to write some DML statements on some of the fixed tables. The table names are common among any schemas, but then only the schema names change.
This weird requirment is because, here they do not maintain same names for schemas on DEV,QA,UAT and PROD databases, and I can not change that. My thoughts are that it can be acheived only using Dynamic SQL. I want to know whether any alternate ways exist since this is going to be the case on various packages and procedures. For example I have a package with around 80 procedures in it which have couple of DML statements in it. Now they want to pass the schema name to main procedure and want the 80 procedures to perform the DML on the schema name passed :)
So, should I change all the 80 procedures and make all the DML in it to Dynamic SQL (I am afraid I might end up doing that)? Please not that I can not change all the environments to same schema names (Not in my hands)
Please suggest.

You can make use of this inside you programs. We do this.
You can prefix the value before the object names.
When the procedure can run from same user who has privs on other schemas.
Just set the current_schema to HR , SCOTT or others.
You will not need to Pass Parameters for each procedure.
Current User can be same as the procedure run from or owner of the procedure.
SQL> SELECT sys_context('USERENV', 'CURRENT_SCHEMA') FROM dual;
SYS_CONTEXT('USERENV','CURRENT_SCHEMA')
SCOTT
SQL> alter session set current_schema=hr;
Session altered.
SQL> SELECT sys_context('USERENV', 'CURRENT_SCHEMA') FROM dual;
SYS_CONTEXT('USERENV','CURRENT_SCHEMA')
HR
SQL> alter session set current_schema=scott
Session altered.
SQL> SELECT sys_context('USERENV', 'CURRENT_SCHEMA') FROM dual;
SYS_CONTEXT('USERENV','CURRENT_SCHEMA')
SCOTTSS

Similar Messages

DatabaseProcedure with return type prefixed with schema name

Hi (Paco)
I have a question about the DatabaseProcedure class. We are using Oracle proxy users for our database connections.
Everything is accessed via a database role that are granted to the logged on user. All our database objects, tables etc are protected with this database role.
When I want to call a database function/procedure I need to add the schema name as a prefix to the custom database object that we uses for parameters/return types.
So far so good. I can also define a parameter prefixed with schema name via the DatabaseProcedure.registerArrayType ...
But when I try to define a function call that uses this parameter I get an error saying "Declaration is not valid".
The problem is located to the PROCEDURE_DEFINITION regular pattern:
private static final Pattern PROCEDURE_DEFINITION = Pattern.compile("\\s* (FUNCTION|PROCEDURE) \\s+ ([\\w.$]+) \\s* (?:\$(.*?)\$)? \\s* (?:RETURN\\s+(\\w+))? \\s* ;? \\s*", CASE_INSENSITIVE | COMMENTS | DOTALL); The return type cannot be prefixed with the schema name.
Any good suggestions or workarounds?!
I actually did change the pattern runtime via reflection to make it work - but I really don't like this solution in the long run!
/Torben
Edited by: Zonic on 2013-05-07 10:52

Hi Torben,
I think I have a workaround for the issue that might work for you. If you look at the source of DatabaseProcedure.registerArrayType you find that it actually calls DatabaseProcedure.registerCustomParamType.
public static void registerArrayType(String name)
registerCustomParamType(name, Types.ARRAY, Array.getORADataFactory(), name);
}As a workaround you could replace your calls to DatabaseProcedure.registerArrayType with calls to DatabaseProcedure.registerCustomParamType as follows.
// Instead of DatabaseProcedure.registerArrayType("NAME.WITH.DOTS") call:
DatabaseProcedure.registerCustomParamType("anyNameWithoutDots", Types.ARRAY, Array.getORADataFactory(), "NAME.WITH.DOTS"); // Don't forget to use uppercase here.
DatabaseProcedure dp = DatabaseProcedure.define("procedure my.procedure(param1 in out anyNameWithoutDots)");
DatabaseProcedure.ParamType type = dp.getParamDef(0).getType();
System.out.println(type.getName() + " is " + type.getTypeName()); // ANYNAMEWITHOUTDOTS is NAME.WITH.DOTSThis way you don't have to use the "illegal" name in the DatabaseProcedure definition.
Regards,
Paco van der Linden

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)

Schema name added to SQL query after SQL Command

Post Author: rickeb1
CA Forum: Data Connectivity and SQL
Hello,
I am using Crystal Reports XI. I have created a Crystal report in the usual manner using a set of tables from a given database schema. When I look at the SQL query that Crystal generates, there are no data schema qualifiers anywhere.
Then I added an SQL Command object that I use as an additional table. Now when I look at the generated SQL query, the data schema name is added to the beginning of the original query as well as to the new SQL Comand code. It also creates an EXTERNAL JOIN which uses this hard-coded schema name (not exactly sure what an "external join" is).
This hard-coding of the schema name is causing a problem when we try to migrate the report to a different environment. Is there some way to avoid having Crystal generate a query with the schema name imbedded in the query, or is there a way to remove it after it is generated?
Thanks!

Post Author: rickeb1
CA Forum: Data Connectivity and SQL
Actually, our problem may be related to this:
http://boardreader.com/t/Crystal_XI_249231/The_Show_SQL_Query_SQL_command_changes_89667.html
Any help greatly (and desparately) apapreciated!

Passing schema name at runtime in batch file

I am having a batch file where i am prompting users to tell the schema name to which they wish to connect at runtime. I am calling one .sql fil within that batch file to execute where i need user to connect to the specific schema at runtime
My batch file looks like as
set serveroutput on;
set linesize 500;
set scan on;
spool test_bat.log
Accept a PROMPT 'Enter the schema name you wish to connect: '
Accept a_pw PROMPT 'Enter the password?: ' HIDE
Accept a_connstr PROMPT 'Enter the connect string : '
conn &a/&a_pw@&a_connstr
Now after getting connected to the specified schema i would like to call some .sql file within the batch file which seems to be as
select count(*) from <schema entered above>.table_name
I want to use the above schema name (a) to get data from the tables.
Please let me know how to get this.
Thanks

user11200661 wrote:
That's fine but still i want to prefix the schema name within the .sql file. My .sql should contain the name of that parameter only as i want to get that parameter replaced by the schema name at runtime. Some other users are using the same .sql file and they have access to that specific schema only. i want to make the .sql file more general so that it can be used by everyone without altering it every time.Sorry, your requirement no longer makes sense.
If people have to access a specific schema because they need the script for general use, then you will have to hard code the schema name into it.
If the script is to prompt for the schema name and connect to that schema and then use that schema name inside the called sql script, then people would not be able to use it generically, as it would be reliant upon the schema name being passed in.
It sounds as if you're trying to write one generic thing that needs to do two different tasks.
Just have two scripts and make life simple.

SQL or PL/SQL : dynamically insert table name in a SQL Statement

Hi,
We have a strange requirement - we need to dynamically use the table names in a SQL Query. E.g:
select * from :table_name
The table_name will be chosen from a list. I have tried this in SQL as well as PL SQL - but, I have been unsuccessul so far.
Can you guys please help me solve this puzzle ?
I hope I have explained my quesion clearly - if not, please do let me know if some more details are necessary.
Regards,
Ramky

The following is the anonymous block that im using in a report in HTMLDB. My problem is Line Number 9. The bind variable contains the chosen table name at
the run time.
Variable "qry_stmt" contains the query to be returned, so that result set for that query will be displayed in the report.
If I hard code the table name(rather that passing it through bind variable) in the
qry_stmt string, Im getting the result sets for that query. But if I pass through
bind variable at run time, its still generating the string correctly( im printing
using a print statement at line number 14). But its returing the following report
error
report error:
ORA-01403: no data found
Please advice/help me in this.....
declare
qry_stmt varchar2(1000);
p_table varchar2(30) := 'EMP';
P_ENAME varchar2(1000);
begin
IF :p2_TABLE_NAMES IS NOT NULL THEN
qry_stmt := 'select * from '||TRIM(:P2_TABLE_NAMES); -- Line Num 9
execute immediate qry_stmt; --into P_ENAME;
ELSE
qry_stmt := 'SELECT 1 FROM dual ';
END IF;
htp.p(qry_stmt);--Line Num 14
return qry_stmt;
EXCEPTION WHEN NO_DATA_FOUND THEN
NULL;
end;
Thanks and Regards,
Ramky

Database Diff - Schema names

Hi I'm using very latest version of the SQL developer. I was using Database Diff feature . I found that it generates a script so I can use to synchronize. But I'm would be nice if it can add schema name infront of the object, which doesn't. Is there any option to show the schema name. This is diffecult when I compare multiple object from different schemas
thanks.

No, but you could request on the announced SQL Developer Exchange e.g. to have the same options as the ObjectViewer Parameters.
Regards,
K.

Schema Name Question

Dear all,
I am new to Oracle DB.
Currently I face a problem:
In the same database, I have create the 3 schema and have the following tables:
Schema A: Table123
Schema B: Table123
Schema C: Table456
And under the Schema C, when I select the table Table123,
(Select * from Table123), I get the data from Schema A by default. How can I config my oracle such that I will get the result from the Table123 in schema B when executing (Select * from Table123), without specifing the schema name in the SQL ?

This forum is for issues related to Oracle XML DB, not general questions. I suggest you try the General or SQL forum

Schema name in front of trigger name.

I have a doubt that all the triggers in my schema of the database of my application of about 200 users have the schema name before the trigger name. Say, if the trigger is 'Trig_1' & the schema is 'Schema_1', then the trigger name is like 'Schema_1.Trig_1'. But, today, i modified one trigger & created it without the schema extension like, say 'Trig_1' as per my eg. I hope, this does not create any problem.
I hope, my question is clear. Please help in solving the doubt as it is urgent.
Regards.

Please help in solving the doubt as it is urgent.This is a simple enough problem to test. If it's that urgent you would be better off investigating it yourself rather than waiting for a passing guru to pontificate. But as I happen to be in the area... ;)
Prefixing the object name with the schema name is a common enough practice in DDL scripts. When the schema name is omitted the object is created in the schema of the user running the command. If the schema name is included, the object is created in the schema specified. When this is the same as the user running the statement there is no difference. However, specifying the schema name does allow us to run installation scripts as power users i.e. those with privileges like CREATE ANY TABLE, CREATE ANY TRIGGER.
Why would we want to do this? Well, if we want to roll out a change to every schema it's a lot easier to log on as the power user account and run one script which installs a trigger in two hundred schemas than it is to log on as two hundred different accounts and run two hundred scripts.
Whether this reflects your situation is a question only you can answer. How is your application installed? If it's run from a single master script you need to include the schema owner in the DDL.
I hope my answer is clear.
Cheers, APC

Dynamic schema name in query

hi there,
who knows how to cheat a little and add schema name dynamically in report query?
curently trying PLSQL function body returning SQL
...from ' || '&P1_SCHEMA.' ||'.IM_INVOICES_V
where...
any bright thoughts?
crazy Simon

Hi,
You could try something like this...
CREATE OR REPLACE FORCE VIEW IM_INVOICES_V_VW AS
SELECT 'SCHEMA_1'.the_schema,
       IM_INVOICES_V.*
FROM   schema1.IM_INVOICES_V
UNION ALL
SELECT 'SCHEMA_2'.the_schema,
       IM_INVOICES_V.*
FROM   schema2.IM_INVOICES_V;
and then...
SELECT *
FROM   IM_INVOICES_V_VW
WHERE the_schema = :P1_SCHEMA
AND ...Cheers
Ben

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.

Issue with passing schema name as variable to sql file

Hi,
I have a scenario wherein from SYS a Java process (Process_1) is invoking SQL files and executing the same in SQLPLUS mode.
DB: Oracle 11.2.3.0
Platform: Oracle Linux 5 (64-bit)
Call_1.sql is being invoked by Java which contains the below content:-
ALTER SESSION SET CURRENT_SCHEMA=&&1;
UPDATE <table1> SET <Column1> = &&1;
COMMIT;
@Filename_1.sql
Another process (Process_2) again from SYS user is also accessing Filename_1.sql.
The content of Filename_1.sql is:-
DECLARE
cnt NUMBER := 0;
BEGIN
SELECT COUNT(1) INTO cnt FROM all_tables WHERE table_name = 'TEST' AND owner = '&Schema_name';
IF cnt = 1 THEN
BEGIN
 EXECUTE IMMEDIATE 'DROP TABLE TEST';
 dbms_output.put_line('Table dropped with success');
END;
END IF;
SELECT COUNT(1) INTO cnt FROM all_tables WHERE table_name = 'TEST' AND owner = '&Schema_name';
IF cnt = 0 THEN
BEGIN
 EXECUTE IMMEDIATE 'CREATE TABLE TEST (name VARCHAR2(100) , ID NUMBER)';
 dbms_output.put_line('Table created with success');
END;
END IF;
End;
Process_2 uses "&Schema_Name" identifier to populate the owner name in Filename_1.sql. But Process_1 needs to use "&&1" to populate the owner name. This is where I am looking a way to modify Call_1.sql file so that it can accommodate both "&&1" to populate owner name values in Filename_1.sql (with avoiding making any changes to Filename_1.sql).
Any help would be appreciated.
Thanks.

Bad day for good code. Have yet to spot any posted today... Sadly, yours is just another ugly hack.
The appropriate method for using SQL*Plus substitution variables (in an automated fashion), is as command line parameters. Not as static/global variables defined by some other script ran prior.
So if a script is, for example, to create a schema, it should look something as follows:
-- usage: create-schema.sql <schema_name>
set verify off
set define on
create user &1 identified by .. default tablespace .. quota ... ;
grant ... to &1;
--eof
If script 1 wants to call it direct then:
-- script 1
@create-schema SCOTT
If script 2 want to call it using an existing variable:
-- script 2
@create-schema &SCHEMA
Please - when hacking in this fashion, make an attempt to understand why the hack is needed and how it works. (and yes, the majority of SQL*Plus scripts fall into the CLI hack category). There's nothing simple, beautiful, or elegant about SQL*Plus scripts and their mainframe roots.

Dynamic table name in native SQL

Hi,
How can i use dynamic table name in native SQL?
My req is to select data from a external database table , but the table name will be only poulated during runtime.
How can i acheive this?
Regards,
Arun.

It should work OK - see demo below.
Jonathan
report zsdn_jc_adbc_test.
start-of-selection.
perform demo_lookup.
form demo_lookup.
data:
    l_error_msg          type string,
    ls_t001              type t001, "Company
    ls_t003              type t003. "Doc types
perform dynamic_lookup
    using
      'T001'
    changing
      ls_t001
      l_error_msg.
write: / l_error_msg.
perform dynamic_lookup
    using
      'T003'
    changing
      ls_t003
      l_error_msg.
write: / l_error_msg.
endform.
form dynamic_lookup
using
    i_tabname            type tabname
changing
    os_data              type any
    o_error_msg          type string.
* Use ADBC to select data
data:
    l_mandt_ref          type ref to data,
    l_result_ref         type ref to data,
    l_mandt              type symandt,
    l_tabname            type tabname,
    l_sql_statement      type string,
    lo_cx_root           type ref to cx_root,
    lo_cx_sql            type ref to cx_sql_exception,
    lo_connection        type ref to cl_sql_connection,
    lo_statement         type ref to cl_sql_statement,
    lo_result_set        type ref to cl_sql_result_set.
clear: os_data, o_error_msg.
get reference of l_mandt into l_mandt_ref.
get reference of os_data into l_result_ref.
l_mandt   = '222'.   "i.e. select from client 222
l_tabname = i_tabname.
try.
      lo_connection = cl_sql_connection=>get_connection( ).
      lo_statement = lo_connection->create_statement( ).
* Set criteria for select:
      lo_statement->set_param( l_mandt_ref ).
      concatenate
        'select * from' l_tabname
        'where mandt = ?'
        into l_sql_statement separated by space.
* Execute
      call method lo_statement->execute_query
        exporting
          statement   = l_sql_statement
          hold_cursor = space
        receiving
          result_set = lo_result_set.
* Get the data from the resultset.
      lo_result_set->set_param_struct( l_result_ref ).
      while lo_result_set->next( ) > 0.
        write: / os_data.
      endwhile.
* Tidy up:
      lo_result_set->close( ).
      lo_connection->close( ).
    catch cx_sql_exception into lo_cx_sql.
      o_error_msg = lo_cx_sql->get_text( ).
    catch cx_root into lo_cx_root.
      o_error_msg = lo_cx_root->get_text( ).
endtry.
endform.

SQL Developer 4.0 - Database Diff - turn off schema name in generated script

SQL Developer 4 / RDBMS 11GR2
I know SQL Developer 4 is EA, but maybe the question has the same answer in 3.3. Also if 4.0 EA questions need to be asked in a different forum, please advise.
I am new to SQL Developer and I admit to using brand Z (TOAD) for many, many years.
(1) When using Database Diff, is there a setting to turn off the schema name that is displayed in the scripts that are generated? I looked in PREFERENCES, but if it is there, I did not see it.
(2) While I have found good resources on SQL Developer, is there a FAQ on Database DIff that answers a lot of these silly type questions?
Thanks in advance

On the first screen of the DIFF wizard there's a check box for 'Schema' - uncheck that.

I want to use a dynamic schema name in the from clause but its not working.

DECLARE
     vblQueryName VARCHAR2(20);
     vblSchemaName VARCHAR2(20);
BEGIN
     SELECT CurrentSchemaName INTO vblSchemaName FROM HR_989_SCHEMA;
     vblQueryName:='060_525_020';
     INSERT /*+ APPEND(HP_ELIGIBILITIES,4) */ INTO HP_ELIGIBILITIES
          LVL1ID,
          LVL1Desc,
          LVL2ID,
          LVL2Desc,
          LVL3ID,
          LVL3Desc,
          LVL4ID,
          LVL4Desc
     SELECT /*+ PARALLEL(a,4) */
          LVL1ID,
          LVL1Desc,
          LVL2ID,
          LVL2Desc,
          LVL3ID,
          LVL3Desc,
          LVL4ID,
          LVL4Desc
     FROM
     bold     vblSchemaName.HP_ELIGIBILITIES a
     WHERE
          UPPER(LVL2ID) = 'XX' ;
     COMMIT;
DBMS_OUTPUT.PUT_LINE( 'Query Executed: ' || vblqueryName);
INSERT INTO HP_QUERYEXECLOG(QueryName) VALUES(vblQueryName);
EXCEPTION WHEN NO_DATA_FOUND THEN NULL;
END;
I want to create a rules table so that the schema name in front of the table name in the from clause can be controlled by a separate table that is maintained but its not working . Help and your valuable inputs needed for this issue

I want to use a dynamic schema name in the from clauseyou can alternatively set the current schema as e.g. in:
declare
   vblqueryname    varchar2 (20);
   vblschemaname   varchar2 (20);
begin
   select currentschemaname into vblschemaname from hr_989_schema;
   vblqueryname := '060_525_020';
   execute immediate 'alter session set current_schema=' || vblschemaname;
   insert /*+ APPEND(HP_ELIGIBILITIES,4) */
         into hp_eligibilities (lvl1id,
                                lvl1desc,
                                lvl2id,
                                lvl2desc,
                                lvl3id,
                                lvl3desc,
                                lvl4id,
                                lvl4desc
      select /*+ PARALLEL(a,4) */
            lvl1id,
             lvl1desc,
             lvl2id,
             lvl2desc,
             lvl3id,
             lvl3desc,
             lvl4id,
             lvl4desc
        from hp_eligibilities a
       where upper (lvl2id) = 'XX';
   commit;
   dbms_output.put_line ('Query Executed: ' || vblqueryname);
   insert into hp_queryexeclog (queryname)
   values (vblqueryname);
exception
   when no_data_found
   then
      null;
end;

Dynamic prefix of schema name in PL/SQL objects

Similar Messages

Maybe you are looking for