Different Schema's

Hi All,
I have recently joined a new company, have a unique issue.
This company started out with a single schema for a survery they were conducting, developed an application using Oracle forms and reports. very soon they had to conduct another survey so they copied say schema A as schema B and copied the forms and reports made neccessary changes to the table, forms and reports as required and the new application say B was up and running. Now with time they have almost 75 schemas and 75 applications.
The issue is that they want one standard shcema and one application to be used for all those previous and future survey's to be conducted.
All past schema's are in use, the structure of every shcema is different and so is the design of Forms and reports.
Is this possible? if so what method?
Any help is appriciated...
Habeeb

Hi,
First of I would like to say that, you have messed the things. Any how as you said that schema's are different, First ask them to Conduct the Analysis of Existing Schemas and Review it till the Schema which is present one (till date) and make re-design of the schema's in such way that they use the One proper standard Schema.
Here in the First the Design in Important.
Note :- As the design is developed parallel, you have to make sure, feasibility of migratining the Existing data to the New Standard Schema should be done with out any problems and data definicency should not happened.
It's takes, but efficient.
Next thing, is that as you said that in future they want to use this schema for future developments. The design should be in such a way that if they want to use any new component to the Application in the Front End, then from Back end point of it should be like a Pluggable Component When ever you want you can make changes to the respective component which should not effect the nature of Applicatoion.
Once these things are done, then create a TEST DB, then test the migration of DATA with Custom Scripts as per your design and test the application in every aspect whether it's working or not.
That is the thing which should be followed. This is my experience.
I hope this help's you.
- Pavan Kumar N

Similar Messages

JDBC Lookup - Import table data from a different schema in same DB

Hi XI Experts,
We are facing an issue while importing a Database table into the external definition in PI 7.1.
The details are as below:
I have configured user 'A' in PI communication channel to access the database. But the table that I want to access is present in schema "B". Due to this, I am unable to view the table that I have to import in the list available.
In other words, I am trying to access a table present in a different schema in the same database. Please note that my user has been given all the required permissions to access different schema. Even then, I am unable to access the table in different schema.
Kindly provide your valuable suggestions as to how I can import table which is present in another schema but in the same Database.
Regards,
Subbu

If you are using PI 7.1, then you can do JDBC Lookup to import JDBC meta data (table structures from DB). Configure a jdbc receiver communication channel where you specify username and password which has permission to access schema A and Schema B of database. Specify database name in the connection string. Then you might have access to import both schema.
Please refer these links
SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
How to use JDBC Lookup in PI 7.1 ?

Accessing tables from different schema in CDS and AMDP

Hi All,
We are working on a HANA system which has several schema replicated from SAP R/3/Non SAP systems. We have BW 7.4 SP9 deployed on the same system and accessing the HANA views using latest BW virtual objects such as Open ODS , Composite providers etc.
We are also using the BW system for few ABAP based data processing developments. We are currently accessing HANA views in ABAP programs by creating dictionary views based on external HANA views.
We would like to however use recent possibilities of CDS and AMDP for better life cycle management of ABAP based solutions. The open SAP course on this subject was of very good help. Thanks a lot "open SAP team" for that. I would however have few open questions,
As I understand AMDP gives us full flexibility of writing sql procedures within ABAP development environment, but can we access tables from different schema into AMDP code. If yes, then sample code would help.
If the answer of first question is yes, then how do we manage transports between development and production systems where the schema names would be different. Currently in open HANA developments, such transport is manged using Schema mapping.
Can I also use different schema tables in CDS views.
We are updating few tables in ABAP dictionary after applying processing logic in ABAP program as detailed in step 1. With the new approach using AMDP, can we directly update database schema tables which will give us an optimization advantage.
New ABAP HANA program interfaces are quite promising and we would like to use them to optimize many data intensive applications.
Thanks & Regards,
Anil

Hi Anil,
I can only answer 1. and 2. (and would be interested into 3. as well):
1.
Yes you can access tables from a different schema and also HANA views. In this case no 'using' is needed.
Examples:
    RESULT = SELECT
    FROM
          "SAP_ECC"."T441V" AS t,
          "_SYS_BIC"."tmp.package/AFPO" AS a.
    WHERE ...
2. In this case, if you need schema mapping: You could use HANA (projection) views which just forward to a different schema, also see example.
Best regards,
Christoph

How to restore a single table from a DP Export from a different schema?

Environment:
Oracle 11.2.0.3 EE on Solaris
I was looking at the documentation on DP Import trying to find the correct syntax to import a single table from a DP Export of a different schema.
So, I want to load table USER1.TABLE1 into USER2.TABLE1 from a DP Export.
Looking at the REMAP_TABLE options:
REMAP_TABLE=[schema.]old_tablename[.partition]:new_tablename
OR
REMAP_TABLE=[schema.]old_tablename[:partition]:new_tablenameI can't see where to specify the target schema name. The examples had the new table name residing in the same schema with just a new name.
I looked at the REMAP_SCHEMA but the docs say that will import the entire schema into the new schema and I only want one (1) table.
Any suggestions are most welcome!
-gary

I thought I tried that combination and it seemed to me that the REMAP_SCHEMA somehow over-rode the TABLES= parameter >and started loading all the objects.If it does fail (and it should not) then please post the details here and I will try to see what is happening.
Let me get back into the sandbox and try it again. I admit I was in a bit of a hurry when I did it the first time.We are all in a hurry, no worries. If it fails, please post the details and the log file.
Does it make any sense that one parameter would override another?No, this should never happen. We have tons of checks to make sure the job can't have multiple meanings. For example, you can't say
full=y schemas=foo --- Which do you want, a full export or a list of schema exports, etc.
Your suggestion was the first thing I thought would work.This should work. If not, please post the log file with the command and the results.
Dean
Thanks again for the help and stay tuned for my new attempt.
-gary

Moving Subpartitions to a duplicate table in a different schema.

+NOTE: I asked this question on the PL/SQL and SQL forum, but have moved it here as I think it's more appropriate to this forum. I've placed a pointer to this post on the original post.+
Hello Ladies and Gentlemen.
We're currently involved in an exercise at my workplace where we are in the process of attempting to logically organise our data by global region. For information, our production database is currently at version 10.2.0.3 and will shortly be upgraded to 10.2.0.5.
At the moment, all our data 'lives' in the same schema. We are in the process of producing a proof of concept to migrate this data to identically structured (and named) tables in separate database schemas; each schema to represent a global region.
In our current schema, our data is range-partitioned on date, and then list-partitioned on a column named OFFICE. I want to move the OFFICE subpartitions from one schema into an identically named and structured table in a new schema. The tablespace will remain the same for both identically-named tables across both schemas.
Do any of you have an opinion on the best way to do this? Ideally in the new schema, I'd like to create each new table as an empty table with the appropriate range and list partitions defined. I have been doing some testing in our development environment with the EXCHANGE PARTITION statement, but this requires the destination table to be non-partitioned.
I just wondered if, for partition migration across schemas with the table name and tablespace remaining constant, there is an official "best practice" method of accomplishing such a subpartition move neatly, quickly and elegantly?
Any helpful replies welcome.
Cheers.
James

You CAN exchange a subpartition into another table using a "temporary" (staging) table as an intermediary.
See :
SQL> drop table part_subpart purge;
Table dropped.
SQL> drop table NEW_part_subpart purge;
Table dropped.
SQL> drop table STG_part_subpart purge;
Table dropped.
SQL>
SQL> create table part_subpart(col_1 number not null, col_2 varchar2(30))
2 partition by range (col_1) subpartition by list (col_2)
3 (
4 partition p_1 values less than (10) (subpartition p_1_s_1 values ('A'), subpartition p_1_s_2 values ('B'), subpartition p_1_s_3 values ('C'))
5 ,
6 partition p_2 values less than (20) (subpartition p_2_s_1 values ('A'), subpartition p_2_s_2 values ('B'), subpartition p_2_s_3 values ('C'))
7 )
8 /
Table created.
SQL>
SQL> create index part_subpart_ndx on part_subpart(col_1) local;
Index created.
SQL>
SQL>
SQL> insert into part_subpart values (1,'A');
1 row created.
SQL> insert into part_subpart values (2,'A');
1 row created.
SQL> insert into part_subpart values (2,'B');
1 row created.
SQL> insert into part_subpart values (2,'B');
1 row created.
SQL> insert into part_subpart values (2,'C');
1 row created.
SQL> insert into part_subpart values (11,'A');
1 row created.
SQL> insert into part_subpart values (11,'C');
1 row created.
SQL>
SQL> commit;
Commit complete.
SQL>
SQL> create table NEW_part_subpart(col_1 number not null, col_2 varchar2(30))
2 partition by range (col_1) subpartition by list (col_2)
3 (
4 partition n_p_1 values less than (10) (subpartition n_p_1_s_1 values ('A'), subpartition n_p_1_s_2 values ('B'), subpartition n_p_1_s_3 values ('C'))
5 ,
6 partition n_p_2 values less than (20) (subpartition n_p_2_s_1 values ('A'), subpartition n_p_2_s_2 values ('B'), subpartition n_p_2_s_3 values ('C'))
7 )
8 /
Table created.
SQL>
SQL> create table STG_part_subpart(col_1 number not null, col_2 varchar2(30))
2 /
Table created.
SQL>
SQL> -- ensure that the Staging table is empty
SQL> truncate table STG_part_subpart;
Table truncated.
SQL> -- exchanging a subpart out of part_subpart
SQL> alter table part_subpart exchange subpartition
2 p_2_s_1 with table STG_part_subpart;
Table altered.
SQL> -- exchanging the subpart into NEW_part_subpart
SQL> alter table NEW_part_subpart exchange subpartition
2 n_p_2_s_1 with table STG_part_subpart;
Table altered.
SQL>
SQL>
SQL> select * from NEW_part_subpart subpartition (n_p_2_s_1);
COL_1 COL_2
11 A
SQL>
SQL> select * from part_subpart subpartition (p_2_s_1);
no rows selected
SQL>I have exchanged subpartition p_2_s_1 out of the table part_subpart into the table NEW_part_subpart -- even with a different name for the subpartition (n_p_2_s_1) if so desired.
NOTE : Since your source and target tables are in different schemas, you will have to move (or copy) the staging table STG_part_subpart from the first schema to the second schema after the first "exchange subpartition" is done. You will have to do this for every subpartition to be exchanged.
Hemant K Chitale
Edited by: Hemant K Chitale on Apr 4, 2011 10:19 AM
Added clarification for cross-schema exchange.

MapViewer metadata problem - accessing spatial data in a different schema.

I have a MapViewer application that uses data from three different schemas.
1. Dynamic Themes come from schema A.
2. Static Themes come from schema B.
3. A newly added static theme in B whose data comes from schema C.
The mapviewer datasource points to schema B where the static themes, data and metadata are defined while the dynamic themes have their own datasource specified as part of addJDBCTheme(...).
To get the newly added map to work I've had to add a view in schema B that points to C instead of referencing directly the table and I've had to add the metadata twice, once for schema B and once for schema C.
If I put the metadata in just one of the two schemas I get the following errors.
08/11/21 13:58:57 ERROR [oracle.sdovis.ThemeTable] cannot find entry in ALL_SDO_GEOM_METADATA table for theme: AMBITOS_REST
08/11/21 13:58:57 ERROR [oracle.sdovis.ThemeTable] java.sql.SQLException: Invalid column index
OR
08/11/21 13:53:39 ERROR [oracle.sdovis.theme.pgtp] java.sql.SQLException: ORA-29902: error in executing ODCIIndexStart() routine
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
It's not a big deal but I'd like to know if anyone else has has similar problems.
Saludos,
Lew.
Edited by: Lew2 on Nov 21, 2008 6:42 AM

Hi Lew,
if you are using a recent version (10.1.3.1 or later) there is no need to use a view and to create the metadata in both schemas.
You need to grant selection on tables between the schemas.
You can try the following. Assume you have the MVDEMO schema (from MapViewer kit) and SCOTT schema.
1) grant select on MVDEMO Counties table to SCOTT
SQL> grant select on counties to scott;
2) Now you are ready to create a predefined theme in schema SCOTT using the MVDEMO Counties table.
- Open MapBuilder and loads the SCOTT schema.
- On the Data navigator (bottom left tree), go to Geometry tables and you should see the MVDEMO node and the COUNTIES node inside it.
- Start a wizard to create a geometry theme based on this Counties table.
- At the end you should see that the base table name is MVDEMO.COUNTIES. Therefore MapViewer will use the metadata in MVDEMO schema and there is no need to replicate it in SCOTT schema.
Joao

HTML DB application using table in a different schema

I need to create a new HTML DB application. The table is in a different schema than mine. The DBA granted me rights to see it and I can see it from iSQL. HTML DB does not give the alternative of selecting this table.

This thread covers your issue.
New to HTML DB, have questions about service admin and schemas
Ask your DBA to add workspace to schema mapping.
Sergio

Dbms_sql in a different schema from query table-error ** ORA-00942

Oracle Experts,
I think I am having problems with using DBMS_SQL in which the function was created in one schema and the query table was created in a different schema.
We have 2 schemas: S1, S2
We have 2 tables:
T1 in Schema S1
T2 in Schema S2
We have a function F1 created by DBA in schema S1 that uses the dbms_sql as:
CREATE OR REPLACE FUNCTION S1.F1(v1 in VARCHAR2) return NUMBER IS
cursor1 INTEGER;
BEGIN
cursor1 := dbms_sql.open_cursor;
dbms_sql.parse(cursor1, v1, dbms_sql.NATIVE);
dbms_sql.close_cursor(cursor1);
return (0);
EXCEPTION
when others then
dbms_sql.close_cursor(cursor1);
return (1) ;
END;
I am using jdeveloper 11G. We have an Oracle DB 11g.
We have a java program which uses jdbc to talk to our Oracle DB.
Basically, in my java program, I call function F1 to check if the query is valid.
If it is, it returns 0. Otherwise, returns 1:
oracle.jdbc.OracleCallableStatement cstmt = (oracle.jdbc.OracleCallableStatement) connection.prepareCall ("begin ? := S1.F1 (?); end;");
cstmt.registerOutParameter (1, java.sql.Types.INTEGER);
cstmt.setString(2, "Select * from S2.T2");
cstmt.execute ();
Since the table that I run the query is T2, created in different schema than F1 was created in, I have the error:
** ORA-00942: table or view does not exist
So my questions are these:
- I am using Oracle DB 11g, if I run the query on a table that created in a different schema from the one that the function (which uses dbms_sql) was created in, I would get the error ORA-00942?
- If I runs the query on table T1 in the same schema as the function F1, would I have the same problem(The reason I ask is I cannot create any table in schema S1 because the DBA has to do it; I am not a DBA)
- This is not a problem, but a security feature because of SQL injection?
- How to resolve this issue other than creating the table in the same schema as the function that utilizes DBMS_SQL?
Regards,
Binh

Definer rights (default) stored objects run under owner's security domain and ignore role based privileges. So regardless what user you are logged in as, function S1.F1 always executes as user S1 and ignores user S1 roles. Therefore exeuting statement within S1.F1:
Select * from S2.T2requires user S1 to have SELECT privilege on S2.T2 granted to S1 directly, not via role.
SY.

Create trigger on view belong to different schema of same db

Hi Guru's,
I have two different schema in the same DB.
Example : schema1 and schema2
I have one view on schema1 and i have grant select to schema2 and create synonym for that view.
Now i need to create trigger on synonym which created from view in schema1 and insert the data into different table from trigger when insert happen on view.
first of all , is it possible?
if its possible then do i need to give create any trigger on view to schema2.
Or is there any other we can get this done..
Many thanks.

Hi,
user590978 wrote:
Hi Guru's,
I have two different schema in the same DB.
Example : schema1 and schema2
I have one view on schema1 and i have grant select to schema2 and create synonym for that view.
Now i need to create trigger on synonym I'm not sure I understand you.
Triggers operate on tables and views (but I'll just say "table" from now on). It doesn't matter if the statement that caused the trigger to fire used the actual table name or a synonym.
which created from view in schema1 and insert the data into different table from trigger when insert happen on view.
first of all , is it possible?I'm not sure I understand you here, either.
It is possible to have a trigger on a view in schema1, which INSERTs data into a table. That table can be in any schema, just so long as the trigger owner has privilges on INSERT into it.
if its possible then do i need to give create any trigger on view to schema2.It's very dangerous, and usually a terrible idea, to grant the CREATE ANY privileges to users.
Schema2 needs the CREATE ANY TRIGGER system privilege only to create a trigger in another schema, such as schema1. There's probably no reason to do that. Let schmea1 create the objects in its own schema.
Post a test script that shows what you want to do. Include CREATE TABLE, CREATE VIEW, CREATE TRIGGER, CONNECT and INSERT statements, and the results you want (the contents of tables where the trigger INSERTed data). If you don't know how to code something, post the closest thing you can, and explain what you really want to do in that place.

Altering index unuseable from a different schema.

I'm sure I'm overlooking something.
I was recently tasked with taking an existing ETL process that was in several different schemas and centralize it so the controlling procedures and functions are all in one schema, and the tables that are being loaded are in various schemas.
We're using a dirrect load, with insert (/* append*/) which is much fast than any other method we've found to load the tables. The trouble I'm having is in disabling the indexes. It's used to be that the procedure that altered the indexes was owned by the same schema that owned the indexes. That was working fine.
So,
Schema 'A' owns the table and indexes.
Schema 'B' owns the procedure that will alter the indexes to set them to unuseable.
Schema B has been granted GRANT ALTER, INSERT, SELECT, UPDATE, DELETE to all tables in Schema 'A'
I am logged in a Schema 'B' and I run the following command...
ALTER INDEX A.PROC_DETAILS_ENC_ID_IDX UNUSABLE
I get ....
Index altered.
However if I run the same thing in a function, I get ...
ORA-01418: specified index does not exist
That seems odd to me that I can run it from toad, but not in a function?

user12221955 wrote:
That seems odd to me that I can run it from toad, but not in a function?Check role-based vs direct grant privileges. PL/SQL does not like role-based privileges and tends to ignore them while running. Directly granted privileges are not so affected. Directly grant the privileges you want to the PL/SQL procedure owner.

How can i import tables from a different schema into the existing relational model... to add these tables in the existing model? plss help

how can i import tables from a different schema into the existing relational model... to add these tables in the existing relational/logical model? plss help
note; I already have the relational/logical model ready from one schema... and I need to add few more tables to this relational/logical model
can I import the same way as I did previously??
but even if I do the same how can I add it in the model?? as the logical model has already been engineered..
please help ...
thanks

Hi,
Before you start, you should probably take a backup copy of your design (the .dmd file and associated folder), in case the update does not work out as you had hoped.
You need to use Import > Data Dictionary again, to start the Data Dictionary Import Wizard.
In step 1 use a suitable database connection that can access the relevant table definitions.
In step 2 select the schema (or schemas) to import. The "Import to" field in the lower left part of the main panel allows you to select which existing Relational Model to import into (or to specify that a new Relational Model is to be created).
In step 3 select the tables to import. (Note that if there are an Foreign Key constraints between the new tables and any tables you had previously imported, you should also include the previous tables, otherwise the Foreign Key constraints will not be imported.)
After the import itself has completed, the "Compare Models" dialog is displayed. This shows the differences between the model being imported and the previous state of the model, and allows you to select which changes are to be applied.
Just selecting the Merge button should apply all the additions and changes in the new import.
Having updated your Relational Model, you can then update your Logical Model. To do this you repeat the "Engineer to Logical Model". This displays the "Engineer to Logical Model" dialog, which shows the changes which will be applied to the Logical Model, and allows you to select which changes are to be applied.
Just selecting the Engineer button should apply all the additions and changes.
I hope this helps you achieve what you want.
David

Import of BaseView to a different schema in database

Hi All,
We have developed some bam reports. Now the base view, meta view are referring to a schema name (say SchemaName1) in database.
In the plans we are using "SQL query" to get data from database. So we have queries like "Select SchemaName1.table1.column1 ... from ......".
Now we have taken a export of the base view, meta view ,plans and all other components of BAM.
All is fine till now... But now i need to import all these stuff in a different database. My problem is that in the new database instance i cannot use the same schema name (i.e. SchemaName1 ). I have a different schema name(say SchemaName2) there and i need to use that......There is no way i can use SchemaName1.
Will the import of Base view/Meta view/plans work or we need to do some configuration changes during import??
Do we have to create Base view for the new schema names from scratch or the imported code can be used??
The plans have sql queries referring to SchemaName1 but we need it to refer to the Other schema(SchemaName2 )...What is the possible way of referring to the new schema without developing the plan again??
Waiting for your valuable feedback...

***Backup your repository database***
***Please review all steps before attempting***
Sarputil Export
1.     Start | Run, type sarputil
2.     Do a partial export. (Note down directory that will contain files to be exported.).
3.     Select your Baseview, Metaview, Security:Login Profile, and Plan. (Note, the check boxes are in front of each object name and might appear very light on some clients.)
4.     On the XML dialog and with the question on what you would like to do select Execute Now.
5.     Finish the wizard and from the directory noted above, verify .csv files were created. (Typically C:\OracleBAM\EnterpriseLink\Data\rp\export).
6.     Copy all .csv files and paste to different temporary folder on 2nd server.
Sarputil Import
1.     Start | Run, type sarputil on the 2nd server where youll import into.
2.     Partial import
3.     Under Repository Information dialog, set the Data Source information on the right and remember to change the directory now containing your .csv files.
4.     Like before, select Execute now and Finish the wizard.
Oracle BAM Admin
Modify connect string (host string or tns name) if you need to:
1.     Connect in Oracle BAM Admin
2.     Expand Baseviews and select the imported Baseview
3.     Check under Server on the left if the connect string is correct.
4.     If not, click Modify button and change.
Modify Baseview Login if you need to:
1.     With your Baseview still selected on the left side, click on Baseview Logins tab
2.     Logins on the left correspond to actual database user ids and password. Add a new Login with a database User ID and Password to access the new schema.
3.     Associate or Set the new Login (right) to the BAM User on the left.
Sarpbv Modification
Use sarpbv utility to change references of the old schema name to a new schema name.
General syntax for Oracle:
sarpbv /R"username:pwd:Oracle:TNS Name::DB UserID:DBUser pwd /B"BaseView name" /O"NewSchema"
**Use Capital letters for New Schema name!
**Notice 2 colons (::) after TNS Name (because you do not have a database name in Oracle).
1.     Open DOS
2.     Type your sarpbv command. Below is an example where I changed a Baseview called scott to use a new schema name called Jack.
sarpbv /R"sa::ORACLE:baminst::sagent:sagent" /B"scott" /O"JACK"
3.     Open Design Studio, locate the plan and check the SQL Query now reflects the new schema.
4.     Test the plan to ensure its pulling data correctly from the new schema.

Materialized view with tables in different schemas

Hello,
I want to create a materialized view with a table from a different schema in the SELECT statement. For materialized view I would like to apply the "REFRESH COMPLETE ON COMMIT" option.
Here the code:
CREATE MATERIALIZED VIEW S1.MV_EXAMPLE
TABLESPACE TS1
PCTFREE 0
BUILD IMMEDIATE
REFRESH COMPLETE ON COMMIT
AS
SELECT T.COLUMN1 COLUMN
FROM S2.TABLE1 T
I can't execute this SQL because I get an "insufficient privileges" error to this table:
FROM S2.TABLE1 T
FEHLER in Zeile 9:
ORA-01031: Insufficient privileges
User S1 has the following privileges:
CREATE SESSION
CREATE SNAPSHOT
CREATE TABLE
CREATE QUERY REWRITE
SELECT ANY TABLE
User S2 has the following privileges:
CREATE SESSION
CREATE SNAPSHOT
CREATE TABLE
CREATE QUERY REWRITE
ALTER ANY SNAPSHOT
Which privileges are missing?
Thanks, Mathias

Thanks Kamal for your answer!
S1 has the grant select directly. But I solveld the problem. The system privilege "ON COMMIT REFRESH" was missing for S1. This has to be set if any of the tables are outside the owner's schema of the materialized view (ORACLE documentation - Data Warehouse Guide).
But one thing is not clear to me yet and the ORACLE documentation doesn't give me an answer. I can set the refresh-attribute ON COMMIT on a materialized view containing only joins when a group by clause is set. If the group by clause is missing I can't! Why?
Regards, Mathias

Sinlge select query in different schemas for same table(Indentical Structu)

Scenario :
Table XYZ is created in Schema A
After an year, the old data from the previous year would be moved to different schema. However in the other schema the same table name would be used.
For eg
Schema A contains table XYZ with data of 2012 yr
Schema B contains table XYZ with data of 2011 yr
Table XYZ in both the schemas have identical structure.
So can we fire a single select query to read the data from both the tables in effective way.
Eg select * from XYZ where date range between 15-Oct-2011 to 15-Mar-2012.
However the data resides in 2 different schema altogether.

Thanks for the reply
Creating an view is an option.
But my problem, there is ORM layer(either Hibernate or Eclipse Top Link) between the application and the database.
So the queries would be formed by the ORM layer and are not hand generated.
So i cannot use view.
So is there any option that would allow me to use single query on different schema's ?

How to change all fk constraints in schema to refer to different schema

Hi,
We wish to change all the fk constraints which point to tables on one schema to same table names but owned by a different schema.
Is this possible?
Thinking of query user_constraints
select *
from user_constraints r
where r.constraint_type = 'R'
and r.r_owner = 'REF'
can put this inside loop but can you modify fk constriant to refer to table owned by different schema
11.2.0.3
Don't really want to need to drop and recreate.
Thanks
Edited by: user5716448 on 06-Apr-2012 04:26

Yes. You need to drop the constraint and recreate it using the clause 'new_schema.objct_name' in the constraint creation statement.
For example, if you want to change the constraint cons_1 to point to some column col_1 in schema sch_2 then the sequence of statements will be like,
ALTER TABLE TAB_1 DROP CONSTRAINT CONS_1;
ALTER TABLE TAB_1 ADD CONSTRAINT CONS_1 FOREIGN KEY COL_1 REFERENCES SCH_2.TAB_1(COL_1);
Remember, you have to have all the privileges required to use/reference the table in schema_2.

How do I write into multiple target tables in DIFFERENT schemas?

It is easy to have a mapping that writes into 2 or more tables it's results. I now need that all these tables are in different schemas!
When I create a 2nd warehouse target with a 2nd location and configure this location to be a different schema on the database, validation tells me, that everything is okay.
When I generate it, there are several warnings, when I execute it, it doesn't work :( It complains that it cannot find <something>.
I'm sorry, I don't have the error-message at hand :(
I've you got an idea, how I could have different schemas for my tables, please let me know!

Art,
Could it be that the target schema into which you install the runtime components does not have privileges on the tables in the other schemas? You have to have at least the right privileges (INSERT, UPDATE, DELETE) on the target tables in the other schemas in order for this to work. However, then there should be no reason, assuming your tables are in different modules related to different locations.
Thanks,
Mark.

Different Schema's

Similar Messages

Maybe you are looking for