Regarding constraints

Hi Experts,
i have source model and target model, in my source model DIM_PRODUCT data store which contains 2000 records,i want to load 700 records to target datastore for that
in my source datastore in model level i applied a new condition on product_id,i applied CKM ON MODEL LEVEL,everything is fine but it loads 2000 records into target,how can i achieve
please guide me.
Regards
ksbabu

Did you enable flow control in your interface ? If yes it should load only the rows that meet your condition in the target table and load the remaining rows in an error table.
Isn't preferable to add a filter (on the model or in the interface) instead of using a condition. This will only filter data (regardless on wether or not flow control is enabled) but won't insert it into error table.
Regards,
JeromeFr

Similar Messages

Regarding Constraints in database ( increase or decrese performance)

Hi all
i want to ask one thing that should be use constraints in our tables?
I have a doubt that when we query that particular table then all the containts are also accessed...
In other case if we use less constraints then it will increse the performance or not ?
Regards
Gurmeet

Free cheese is only in mousetrap. For everything other you have to pay somehow. Including constraints. Including Oracle db as such. MySQL most probably will work faster than Oracle.
So choose either db with constraints and a bit slower DML (INSERTS, UPDATES, DELETES, and not queries, i.e. SELECTS), or data waste instead of data base.
Gints Plivna
http://www.gplivna.eu

Regarding Constraint Handling using Java

Hi,
I am currently trying to develop a system whereby the user can obtain a work schedule by stating the constraints such as public holiday etc.
I came across a language, Java Constraint Handling Rules (JCHR). From a overview, it will aid in defining the constraints.
However, there is simply too little references on the internet. Should any one has knowledge on it, please kindly reply me. I need help urgently. Thank you.
Tina

http://www.pms.informatik.uni-muenchen.de/software/jack/docu/jase.html

Using constraints w/nested tables

I read the documentation http://download-west.oracle.com/otndoc/oracle9i/901_doc/appdev.901/a88878/adobjbas.htm#454744 regarding constraints on nested tables. However, it supplies examples of unique and primary key constraints. Would someone please help with an example of a foreign key? Is that possible with a nested table?
Thanks!

Jesse,
Nested tables do have a system-generated NESTED_TABLE_ID column to correlate with their parent rows.
Regards,
Geoff
I read the documentation http://download-west.oracle.com/otndoc/oracle9i/901_doc/appdev.901/a88878/adobjbas.htm#454744 regarding constraints on nested tables. However, it supplies examples of unique and primary key constraints. Would someone please help with an example of a foreign key? Is that possible with a nested table?
Thanks!

Full Database Exp & Imp

Hi,
I am trying to Exp & Imp a full database. I am working on Oracle 9i & 10g on Solaris 9. I am not using Data Pump. Can anyone please help me with the following:
1. I am performing the full export using SYSTEM user.
1.a Does a Full export include (or backups up) the DATA DICTIONARY of the database?
1.b Does a Full export include the backup of SYS and SYSTEM objects?
I am using the following command to export
exp system/system@testdb file=$HOME/testdbfullexp.dmp full=y statistics=none
I have tried importing the FULL export to another database and i did see that SYS and SYSTEM objects were also being imported ( got some errors regarding constraints and inconsistencies).
I would like to ask like what are the ideal steps to follow to copy a database from DB1 to DB2 using EXP and IMP
Any information will be of a great help
Thanks,
Harris.

1 a) No, as the data dictionary will be automagicall recreated by implicit SQL.
This means any non dictionary objects under SYS will be lost
1 b) as above. SYSTEM however is a normal user.
any %SYS user will NOT be exported (CTXSYS, MDSYS, etc)
On import of SYSTEM there will be always errors, as SYSTEM is non-empty after initial database creation.
Sybrand Bakker
Senior Oracle DBA

Need to test if a column have unique values or not

Hi all,
in ETL process I need to check if some cols have unique values or not using sql or plsql.
Suppose we need to load a big file data with external table initially and then test if values
on one or more columns have unique values in order to proceed with ETL process.
What is the faster test I can execute to verify that a column have unique values or not?
It's better for the ETL performance, use:
a. techniques regard constraints like described on Ask tom forum
"ENABLE NOVALIDATE validating existing data"
(Ask Tom &quot;ENABLE NOVALIDATE validating existing da...&quot;)
b. "simply" query on the data?
like this:
select count(count(*)) distinct_count,
         sum(count(*)) total_count,
         sum(case when count(*) = 1 then 1 else null end) non_distinct_groups,
         sum(case when count(*) > 1 then 1 else null end) distinct_groups
from hr.employees a
group by A.JOB_ID
c. use analytics function?
d. use some feature directly on external table?
Bye in advance

Here is the example to handling the errrs using LOG_ERRORS into concept. You will check this and let me know if any doubt you have
DATAFILE:-
1000,ANN,ZZ105
1001,KARTHI,ZZ106
1002,PRAVEEN,ZZ109
1002,PARTHA,ZZ107
1003,SATHYA,ZZ108
1000,ANN,ZZ105
----- Original Table With unique constraints
SQL> CREATE TABLE tab_uniqtest(student_id     NUMBER(10) UNIQUE,
                          student_name   VARCHAR2(15),
                                                  course_name    VARCHAR2(15)
2    3    4
Table created.
----- External table
SQL> CREATE TABLE tab_extuniqtest(student_id     NUMBER(10),
2                               student_name   VARCHAR2(15),
3                                                  course_name    VARCHAR2(15)
4                              )
5 ORGANIZATION EXTERNAL
6 (
7 DEFAULT DIRECTORY ann_dir
8 ACCESS PARAMETERS
9 (
10    RECORDS DELIMITED BY NEWLINE
11    BADFILE 'tabextuniqtest_badfile.txt'
12    LOGFILE 'tabextuniqtest_logfile.txt'
13    FIELDS TERMINATED BY ','
14    MISSING FIELD VALUES ARE NULL
15    REJECT ROWS WITH ALL NULL FIELDS
16    (student_id,student_name,course_name)
17 )
18 LOCATION ('unique_check.csv')
19 )
20 REJECT LIMIT UNLIMITED;
Table created.
---- Error logging table to log the errors
SQL> CREATE TABLE dmlerrlog_uniqtest(ORA_ERR_NUMBER$     NUMBER ,
2                                 ORA_ERR_MESG$       VARCHAR2(2000),
3                                 ORA_ERR_ROWID$      ROWID,
4                                 ORA_ERR_OPTYP$      VARCHAR2(2),
5                                 ORA_ERR_TAG$        VARCHAR2(4000),
6                                 inserted_dt         VARCHAR2(50) DEFAULT TO_CHAR(SYSDATE,'YYYY-MM-DD'),
7                                 student_id              VARCHAR2(10)
8                                  );
Table created.
---- Procedure to insert from external table
SQL> CREATE OR REPLACE PROCEDURE proc_uniqtest
2 AS
3 v_errcnt NUMBER;
4 BEGIN
5      INSERT INTO tab_uniqtest
6      SELECT * FROM tab_extuniqtest
7      LOG ERRORS INTO dmlerrlog_uniqtest('PROC_UNIQTEST@TAB_UNIQTEST') REJECT LIMIT UNLIMITED;
8      SELECT COUNT(1) into v_errcnt
9      FROM dmlerrlog_uniqtest
10      WHERE ORA_ERR_TAG$ = 'PROC_UNIQTEST@TAB_UNIQTEST';
11       IF(v_errcnt > 0) THEN
12       ROLLBACK;
13      ELSE
14        COMMIT;
15       END IF;
16      DBMS_OUTPUT.PUT_LINE ( 'Procedure PROC_UNIQTEST is completed with ' || v_errcnt || ' errors') ;
17 EXCEPTION
18   WHEN OTHERS THEN
19    RAISE;
20 END proc_uniqtest;
21 /
Procedure created.
SQL> SET SERVEROUTPUT ON
SQL> EXEC proc_uniqtest;
Procedure PROC_UNIQTEST is completed with 2 errors
PL/SQL procedure successfully completed.
SQL> SELECT STUDENT_ID,ORA_ERR_MESG$ FROM dmlerrlog_uniqtest;
STUDENT_ID                     ORA_ERR_MESG$
1002                           ORA-00001: unique constraint (
                               SCOTT.SYS_C0037530) violated
1000                           ORA-00001: unique constraint (
                               SCOTT.SYS_C0037530) violated

Partitioning on tables

HI.
I can do new partiton table when creating new table.
CREATE TABLE zsat_dokumenti_saldakonti_bri1 PARTITION by list(id_organizacijske_enote_de)(PARTITION de_kc
VALUES('20') TABLESPACE users, PARTITION de_mo
VALUES('01') TABLESPACE users) AS
SELECT *
FROM zsat_dokumenti_saldakonti;
How can I add partition on existing table zsat_dokumenti_saldakonti_bri1 with add clouse (altre table zsat_dokumenti_saldakonti_bri1 add partition ???...)?
Thanks for unswers?
Vojko

Hi!
First u can rename ur old table. Then create a table with appropriate name with proper partition. Then drop the renamed table. But, this has some limitation regarding constraints.
Regards.
Satyaki De.

How CSSCAN determines which indexes need to be rebuild ?

Hi everybody,
i'm currently migrating 3 Oracle databases that contain CP1252 characters unproperly stored in WE8ISO8859P1 instances.
The key steps of the migration are :
1. ALTERing CHARACTERSET to WE8MSWIN1252
2. changing CHARACTER SEMANTIC LENGTH for CHAR and VARCHAR2 columns
3. truncating data stored in VARCHAR2(4000) columns
2. Full export
3. Full import in a ALL32UTF8 instance
To do all of this (and especially the step 3), i use the CSSCAN utility (very practical !!!).
And i have a question about CSSCAN: how CSSCAN determines which indexes need to be rebuild. What is the logic ?
Looking at the CSSCAN report, i have a lot of cells/columns that are affected by the characterset migration, and i have just a few index to rebuild.
Why would i like to understand the logic ? Because i would like to rebuild ONLY indexes that REALLY need to be rebuilt and i am not sure that all the indexes specified by CSSCAN really need to be rebuilt.
Thanks for any information about that.
(and sorry for my english)
NB: i have managed "function-based indexes" specifically: i drop them before the export, and i recreate them after the import. So my question mostly target the "regular indexes"

1. All indexes whose key contains at least one character column with convertible or exceptional data, excluding indexes with names equal to some constraint name for the same owner.
plus
2. All functional indexes on tables that have columns needing conversion, excluding indexes with names equal to some constraint name for the same owner.
The condition regarding constraints does not seem to be very fortunate but it comes from times when the appropriate flag in index metadata was not yet available.
But note that in your migration scenario, you do not actually have to care much about indexes. Step 1 & 2 do not need any modifications to the user data and hence to index contents. Step 3, if done through UPDATE, will modify affected indexes automatically. Step 4 does not affect the database. Step 5 will recreate all existing indexes anyway.
-- Sergiusz

Contraint States

This is a newbie question regarding constraint states. Can someone give a simple real world example of these items in action.
DISABLE VALIDATE - New & Existing data do not have to conform to constraint
DISABLE NOVALIDATE - Disallowing modification of constrained columns
ENABLE VALIDATE - New data conforms but existing data in unknown state
ENABLE NOVALIDATE - New & Existing data conform to constraint
I am guessing these are needed when performing several actions but to have real examples will help greatly. Any information is greatly appreciated.
Matt

Perhaps the most significant reason for having the enable/disable and validate/novalidate states for constraints it to allow you to add constraints to a table with minimum locking interference.
The following is a worked example, to show how you might work through various states as you add a new constraint. This was run from SQL*Plus, and the responses (after the first few appear as comments). The explanation is at the end.
drop table t1;
create table t1(v1 varchar2(10) not null);
insert into t1 values('abc');
alter table t1 add constraint t1_v1_upper
check(v1 = upper(v1))
disable novalidate
insert into t1 values('ghi');
-- 1 row created.
alter table t1 modify constraint t1_v1_upper validate;
alter table t1 modify constraint t1_v1_upper validate
ERROR at line 1:
ORA-02293: cannot validate (TEST_USER.T1_V1_UPPER) - check constraint violated
alter table t1 modify constraint t1_v1_upper enable;
alter table t1 modify constraint t1_v1_upper enable
ERROR at line 1:
ORA-02293: cannot validate (TEST_USER.T1_V1_UPPER) - check constraint violated
alter table t1 modify constraint t1_v1_upper enable novalidate;
-- Table altered.
insert into t1 values('ghi');
insert into t1 values('ghi')
ERROR at line 1:
ORA-02290: check constraint (TEST_USER.T1_V1_UPPER) violated
update t1 set v1 = 'xyz' where v1 = 'abc';
update t1 set v1 = 'xyz' where v1 = 'abc'
ERROR at line 1:
ORA-02290: check constraint (TEST_USER.T1_V1_UPPER) violated
update t1 set v1 = v1 where v1 = 'abc';
update t1 set v1 = v1 where v1 = 'abc'
ERROR at line 1:
ORA-02290: check constraint (TEST_USER.T1_V1_UPPER) violated
update t1 set v1 = upper(v1) where v1 != upper(v1);
-- 2 rows updated.
alter table t1 modify constraint t1_v1_upper validate;
-- Table altered.After creating the table with a single row, we add the constraint as disable novalidate. The old row is "illegal", but Oracle doesn't care because of the novalidate state.
We try to insert an "illegal" row, and succeed because the constraint is disabled.
We try to validate the constraint, and Oracle complains because it finds an existing illegal row.
We enable the constraint - and that's okay, because Oracle doesn't check for exsiting illegal rows. The constraint is now 'enable novalidate'.
We try to insert (the same valued) illegal row, and Oracle objects because the constraint is enabled.
We try to update an existing "illegal" row to a new, "illegal" value, and can't because the constraint is enabled. We can't even update an existing "illegal" value to itself.
We convert all lower case values to upper case.
We can now validate the constraint, which moves to state (enable validate).
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Give Me Some Information Regarding procedures and Constraints

HI Seniors
Please give me some idea about stand-alone procedures ..?
1)When to use Standalone procedure ?
2)What are the constraints in Pl/SQL ?When to use these constraints in pl/sql?
3)What is Named Notation ?
Best Regards
Busi

Why wouldn't read Documentation ?
Rgds.

Regarding ORA-00001: unique constraint violation error

Hi ,
This is Venkat. I am new to OWB.
When I run the mapping I am getting the ORA-00001: unique constraint violation error.
My loading type is Update/Insert.
My target table Primarykey is combination of 3 keys.
Please give me the suggestions. It is very urgent.
Thanks,
Venkat

1) If you can disable/drop the indexes on the table, you can load the data and then do a SQL query grouping by the PK/UI to show which rows have a count > 1 i.e. the duplicates.
2) If you can't alter the target table, perhaps create a dummy copy of the table without pk/indexes and load to that and then do above query.
3) Run the mapping via the debugger and set a breakpoint just before your target table and examine the data to see if you can spot the duplicates.
4) Put a deduplicator into the mapping (just before target table), this may allow you to load data but doesn't solve the real problem as to why you have duplicates.
Si

Regarding OIA 16 GB RAM Size constraint

Hi
Can Any one Please help me to understand quickly on Oracle Idetity Anlytics 11g (11.1.1.5) Ram size needed
Ram Size needed for OIA installation on solaris mechine?
Some docs say its 16 GB Ram, is it needed, but that much space,is going to kill the cpu usage with Garbage collector process.
If 16 GB is compulsory then can we split into 4 app server clusters wtih 4 GB RAM for each?
Thanks
Edited by: user13658730 on Feb 27, 2012 11:07 PM

hope below link will clarify your doubt
http://www.oracle.com/technetwork/middleware/id-mgmt/oia-sizing-guide-130482.pdf
--nayan

Difference Between Unique Index vs Unique Constraint

Can you tell me
what is the Difference Between Unique Index vs Unique Constraint.
and
Difference Between Unique Index and bitmap index.
Edited by: Nilesh Hole,Pune, India on Aug 22, 2009 10:33 AM

Nilesh Hole,Pune, India wrote:
Can you tell me
what is the Difference Between Unique Index vs Unique Constraint.http://www.jlcomp.demon.co.uk/faq/uk_idx_con.html
and
Difference Between Unique Index and bitmap index.The documentation is your friend:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28318/schema.htm#CNCPT1157
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/schema.htm#sthref1008
Regards,
Rob.

Constraint table in sql server7

i have a database in sql server7 and i want to see all the constraints that are applied on that table manually i.e. through sql query.please tell me what is the sql query that i can use to see all the constraints applied on the table.
same thing i want to do with ms-access ,tell me if i can use any query to see the constraints on ms-access table.

Hi, this is Oracle Forum, you must go to Microsoft Forum for add this Post, please take the next reference.
http://forums.microsoft.com/
Regards.

How to apply the constraint ONLY to new rows

Hi, Gurus:
   I have one question as follows:
   We need to migrate a legacy system to a new production server. I am required to add two columns to every table in order to record who updates the row most recently through triggers, and I should apply not null constraint to the columns . However, since legacy system already has data for every table, and old data does not have value for the 2 new columns. If we apply the constraint, all of existing rows will raise exception. I wonder if there is possibility to apply the constraint ONLY to new rows to come in future.
Thanks.
Sam

   We need to migrate a legacy system to a new production server. I am required to add two columns to every table in order to record who updates the row most recently through triggers, and I should apply not null constraint to the columns .
The best suggestion I can give you is that you make sure management documents the name of the person that came up with that hair-brained requirement so they can be sufficiently punished in the future for the tremendous waste of human and database resources they caused for which they got virtually NOTHING in return.
I have seen many systems over the past 25+years that have added columns such as those: CREATED_DATE, CREATED_BY, MODIFIED_DATE, MODIFIED_BY.
I have yet to see even ONE system where that information is actually useful for any real purpose. Many systems have application/schema users and those users can modify the data. Also, any DBA can modify the data and many of them can connect as the schema owner to do that.
Many tables also get updated by other applications or bulk load processes and those processes use generic connections that can NOT be tied back to any particular system.
The net result is that those columns will be populated by user names that are utterly useless for any auditing purposes.
If a user is allowed to modify a table they are allowed to modify a table. If you want to track that you should implement a proper security strategy using Oracle's AUDIT functionality.
Cluttering up ALL, or even many, of your tables with such columns is a TERRIBLE idea. Worse is adding triggers that server no other purpose but capture useless infomation but, because they are PL/SQL cause performance impacts just aggravates the total impact.
It is certainly appropriate to be concerned about the security and auditability of your important data. But adding columns and triggers such as those proposed is NOT the proper solution to achieve that security.
Before your organization makes such an idiotic decision you should propose that the same steps be taken before adding that functionality that you should take before the addition of ANY MAJOR structural or application changes:
1. document the actual requirement
2. document and justify the business reasons for that requirement
3. perform testing that shows the impact of that requirement on the production system
4. determine the resource cost (people, storage, etc) of implementing that requirement
5. demonstrate how that information will actually be used EFFECTIVELY for some business purpose
As regards items #1 and #2 above the requirement should be stated in terms of the PROBLEM to be solved, not some preconceived notion of the solution that should be used.
Your org should also talk to other orgs or other depts in your same org that have used your proposed solution and find out how useful it has been for them. If you do this research you will likely find that it hasn't met their needs at all.
And in your own org there are likely some applications with tables that already have such columns. Has anyone there EVER used those columns and found them invaluable for identifying and resolving any actual problem?
If you can't use them and their data for some important process why add them to begin with?
IMHO it is a total waste of time and resources to add such columns to ALL of your tables. Any such approach to auditing or security should, at most, be limited to those tables with key data that needs to be protected and only then when you cannot implement the proper 'best practices' auditing.
A migration is difficult enough without adding useless additional requirements like those. You have FAR more important things you can do with the resources you have available:
1. Capture ALL DDL for the existing system into a version control system
2. Train your developers on using the version control system
3. Determining the proper configuration of the new server and system. It is almost a CERTAINTY that settings will get changed and performance will suffer even though you don't think you have changed anything at all.
4. Validating that the data has been migrated successfully. That can involve extensive querying and comparison to make sure data has not been altered during the migration. The process of validating a SINGLE TABLE is more difficult if the table structures are not the same. And they won't be if you add two columns to every table; every single query you do will have to specify the columns by name in order to EXCLUDE your two new columns.
5. Validating the performance of the app on the new system. There WILL BE problems where things don't work like they used to. You need to find those problems and fix them
6. Capturing the proper statistics after the data has been migrated and all of the indexes have been rebuilt.
7. Capturing the new execution plans to use a a baseline for when things go wrong in the future.
If it is worth doing it is worth doing right.

Regarding constraints

Similar Messages

Maybe you are looking for