Constraint names hardcoded !!!

we generated entity and view objects based on a table and tested the application module which was working fine. now we have created a new user by firing the scripts again. as a result, validations on the entity object (eg. not null etc) have started failing. on examining, we found that the system generated constraint names like SYSC000101 for not null columns, have been hardcoded in the XML file and these differ now in the newly generated scheme. what is the solution to this.
what will happen when we go to the client site and fire our scripts there??? will all my entity objects stop working???

I have a master and a child table that are linked by a foreign key (name is CITY_STATE_FK). this was working fine in the original schema. but in the new schema, when i try to insert a new city(child), it gives the error "failed to find or invalidate owning entity". In the default association that jdeveloper has made, if i uncheck the Composition check box in the properties of the association, insert is allowed. But why is it forcing me to remove Composition. In this case i have my user defined FK name that is same in the 2 schemas.

Similar Messages

How to modify a column name & How to modify a constraint name

How to modify a column name?
How to modify a primary key constraint name if the pk has been referenced by another foreign key?
Thanks.

Hi,
What version of oracle are you using? If it is 9i,
then you can the command
alter table <table_name> rename column <column_name> to <new_column>;
if it is 8i or earlier, you can create a view with the required names.
hth
Always post the oracle version and the platform you are using to get better response.

Find column name from constraint name

How to fetch the column name from a constraint name to which the constraint is applied?.
I only know the name of the constraint and can get the table name from "dba_constraints". How can I know to which column in the table this constraint is applied.
Thanks

What about this?
satyaki>
satyaki>
satyaki>desc user_cons_columns;
Name                                      Null?    Type
OWNER                                     NOT NULL VARCHAR2(30)
CONSTRAINT_NAME                           NOT NULL VARCHAR2(30)
TABLE_NAME                                NOT NULL VARCHAR2(30)
COLUMN_NAME                                        VARCHAR2(4000)
POSITION                                           NUMBER
satyaki>
satyaki>Regards.
Satyaki De.

Check Constraint names aren't synced when engineering to logical

Just learned about this tool at OOW and ran into an issue involving check constraint names being compared but not synced when engineering from the relational model to the logical model. When I set the constraint names in the logical model (and perform one last "Engineer to Logical Model") after that the compare dialog shows the table and entities match. Is this a bug?
Steps to reproduce:
1. importing a relational data model from data dictionary which contains a table with a column level check constraint
2. perform "Engineer to Logical model" to produce the logical model
Issue:
Perform another "Engineer to Logical model" which will show the table with the column level check constraint as being out of sync with the logical model's equivalent entity, when you drill down into the diff in the compare dialog box you see the check constraint name has a value in the relational model and the name is null in the logical model
Verify:
Looking in logical model at the constraint (<Entity>/Attributes/Attribute Properties/Default and Constraint/Constraint Name) the value is empty
Work Around:
Set the constraint name in the spot from verify above and perform "Engineer to Logical model" twice. The first time it will show the same issue, the second time it will show the table and entity match

Hi Bo,
thanks for feedback. It's fixed now and you'll get the fix in version 3.0.
Another( probably better workaround) - in engineering dialog - "Compare/Copy options" tab - uncheck "Don't use for new objects" option.
Philip

Getting the constraint name with sql%bulk_exceptions

Hello folks,
Is there any way to get the constraint name that was violated using sql%bulk_exceptions.
I've a parent table and it's two children tables. When I try to delete from parent using forall, save exceptions, I want to know what constraint violated at what iteration of a bulk operation.
I've following script.
set serveroutput on
drop table chld;
drop table chld2;
drop table prnt;
create table prnt(n number primary key);
insert into prnt select level from dual connect by level<11;
create table chld(cn number references prnt(n));
insert into chld select level from dual connect by level<3;
create table chld2(cn number references prnt(n));
insert into chld2 select level*3 from dual connect by level<3;
select * from prnt;
select * from chld;
select * from chld2;
commit;
declare
type t_prnt_obj is table of prnt.n%type index by pls_integer;
t_prnt_tab t_prnt_obj;
l_exp_cnt integer;
begin
select n bulk collect into t_prnt_tab from prnt order by n;
dbms_output.put_line('t_prnt_tab.count -- '||t_prnt_tab.count);
forall i in t_prnt_tab.first .. t_prnt_tab.last save exceptions
    delete prnt where n = t_prnt_tab(i);
exception
when others
then
    l_exp_cnt := sql%bulk_exceptions.count;
    dbms_output.put_line('Total exceptions:'|| l_exp_cnt);
    for k in 1 .. l_exp_cnt
    loop
      dbms_output.put_line('Error '||k|| ' - Collection Index: '||sql%bulk_exceptions(k).error_index||' - Error Code: '|| sql%bulk_exceptions(k).error_code||' - Message: '||SQLERRM(- sql%bulk_exceptions(k).error_code) );
    end loop;
end;I get the output as below:
t_prnt_tab.count -- 10
Total exceptions:4
Error 1 - Collection Index: 1 - Error Code: 2292 - Message: ORA-02292: integrity constraint (.) violated - child record found
Error 2 - Collection Index: 2 - Error Code: 2292 - Message: ORA-02292: integrity constraint (.) violated - child record found
Error 3 - Collection Index: 3 - Error Code: 2292 - Message: ORA-02292: integrity constraint (.) violated - child record found
Error 4 - Collection Index: 6 - Error Code: 2292 - Message: ORA-02292: integrity constraint (.) violated - child record foundInstead, I want to get in output with the constraint_name added. Like below:
t_prnt_tab.count -- 10
Total exceptions:4
Error 1 - Collection Index: 1 - Error Code: 2292 - Message: ORA-02292: integrity constraint (GK.CP_FK) violated - child record found
Error 1 - Collection Index: 1 - Error Code: 2292 - Message: ORA-02292: integrity constraint (GK.CP_FK) violated - child record found
Error 1 - Collection Index: 1 - Error Code: 2292 - Message: ORA-02292: integrity constraint (GK.C2P_FK) violated - child record found
Error 1 - Collection Index: 1 - Error Code: 2292 - Message: ORA-02292: integrity constraint (GK.C2P_FK) violated - child record foundIs it possible, if so how do I get it?
Thanks in advance for you help.
Girish

This is phenomenal, Manik. It surely eased the work am doing at the moment.
Thanks to you and many more to, Tom!
Cheers!
Girish

Problem with constraint names

Hi to all, I have a problem with the constraint names. I need to delete the table name that is used like prefix in the constraint name.
Example:
- Actual : DBO_MYDATABASE_FK_Ho_Ka
- Desired : FK_Ho_Ka
The constraint names are FK_Ho_Ka in the creation database script, but if I import the database schema, I have DBO_MYDATABASE_FK_Ho_Ka, but I only need the constraint name.
Thanks so much :)

Thanks for your time :)
I did a migration from Microsoft SQL Server 2005 to Oracle 11g database. Then, I need to use the same Entity Framework model to use with Sql Server and Oracle. Then, I need that the constraint names must be the same in the two databases.
I did the migration with Oracle Sql Developer and all works fine. The resulted migration script has the constraint name like FK_UJ_UK (that it's OK) but when I import the database schema or do the Entity Framework model, I have this constraint name DBO_MYDATABASE_FK_UJ_UK.
Edited by: Bluegene on Dec 11, 2008 9:35 AM

Constraint names - Modeling Naming Options

Can anyone advise me which group(under Model Options -> Naming Conventions) controls the max code length for the below in a physical data model.
FK Constraints
PK Constraints
UK Constraints
The context sensitive help from this window does not describe what physical objects some of these impact. For instance, I thought Reference would control FK Constraints, but it is not. I have FK Constraints being generated longer than 30 characters, which is the max that Oracle allows. Other objects is a catch all that I did not restrict to 30 as that then shortens lot of other things that I don't even know and might want to.
I tried looking in the PD Meta model help under "Libraries -> PdPDM -> Model Options", but I don't understand much of what is described there.
I have following in the Oracle 11g DBMS Resource file under the branch "ORA11GR1::Script\Objects\Reference\ConstName".
I need this so that I have FK constraints generated with a sequence number suffix. Maybe the Model naming options don't apply when this is used and I need to figure out the syntax to chop the table name so that to 24 as FK_ and _1 will use up 6 characters in the constraint name.
FK_%TABLE%_%REFRNO%

Hi Stefan,
It is still ending up generating Unique key constraint names longer than 30 characters.
I do have a rule for constraint name creation as well.
So right now in my Oracle 11 Resource file, I have this.
ORA11GR1::Script\Objects\Key\ConstName is set to UK_%TABLE%_%.U-18.1:AKEY%
I am wondering if I should change it to UK_%U.25:TABLE%_%.U-18.1:AKEY% so that it takes only 25 characters from table name and that is restricted to 30 characters max.
I also have MaxConstLen at two levels and both are set to 30
ORA11GR1::Script\Objects
ORA11GR1::Script\Objects\Key
It is getting really frustrating that I cannot get same results as I did with Erwin DDL generation. I wish SAP made it easy and had a setting for Constraint names in Model Naming options.

How to restrict the generated constraint name with Model Driven Development

Hello
I have a database that has tables INSTRUMENT and EXCHANGE. There has to be a foreign key field called primaryExchange inside INSTRUMENT table that points to the ID of EXCHANGE table. In my fml file, my tables are called Instrument and Exchange. When I create this relation between the two tables in the model and deploy it to LCDS, it tries to create a FK constraint by the name of "FK_Instrument_primaryExchange_TO_Exchage" which fails with ORA-00972 - Identifier is too long. Obviously the generated FK name is more than 30 chars and hence the oracle erorr. The only way to resolve this is to reduce the name of the table/field in the fml file while keeping the database table/field name intact. So the FK might be called FK_Instr_primExch_TO_Exch and which will work but the problem is that in the fml model file, I am loosing the meaningful names of the tables and thus the data services that are generated have truncated names. For this particular example, the truncated name might still be okay but in a large database, it is causing much grief. I would really prefer decent descriptive names for table like MarketOrder instead of MO. Pls advise how I can customize the generated constraint name while keeping the tables names still informative.
Now I edit my DB tables to have a field called ID which is unique to that table but while deploying I get hibernate and fiber exceptions :-
2011-03-10 16:30:44,042 INFO [STDOUT] (http-0.0.0.0-8180-1) [UlltraWebServer]Exception trying to build hibernate's session factory: org.hibernate.MappingException: Repeated column in mapping for entity: UlltraWebServer.package4.Client column: ID (should be mapped with insert="false" update="false")
2011-03-10 16:30:44,116 INFO [STDOUT] (http-0.0.0.0-8180-1) [UlltraWebServer]Error instantiating application scoped instance of type 'fiber.data.assemblers.FiberAssembler' for destination 'UlltraWebServer.Holiday'.
org.hibernate.MappingException: Repeated column in mapping for entity: UlltraWebServer.package4.Client column: ID (should be mapped with insert="false" update="false")
2011-03-10 16:30:44,229 INFO [STDOUT] (http-0.0.0.0-8180-1) [UlltraWebServer]Exception trying to build hibernate's session factory: org.hibernate.MappingException: Repeated column in mapping for entity: UlltraWebServer.package4.Client column: ID (should be mapped with insert="false" update="false")
The above suggests that it does not like the same name for the fields in multiple tables, they all have to be unique like Holiday.holidayID, Client.clientID etc which causes the above constraint length violation issue..
thanks

You should be able to achieve what you want with an explicit criteria filter on your entity.
In the Modeler Design view, select your entity and add a filter. You'll see that there is a an "Order By" field in the Properties view.
Enter the value you want there and then save and redeploy your model. When you don't enter anything in the "Criteria" field, you create a getAll fill.
Here's an example of an entity created with this type of filter; it is sorted by price in ascending order:
<entity name="Product" persistent="true">
<annotation name="ServerProperties" ServerType="LCDS"/>
<annotation name="DMS" Table="PRODUCT"/>
<annotation name="RDS" introspectedColumns="PRODUCTID,DESCRIPTION,PRICE,PRODUCTNAME"/>
<annotation name="VisualModeler" width="115" height="110" x="364" y="203"/>
<id name="productid" type="integer">
<annotation name="DMS" ColumnName="PRODUCTID"/>
</id>
<property name="description" type="string" length="255">
<annotation name="DMS" ColumnName="DESCRIPTION"/>
</property>
<property name="price" type="float">
<annotation name="DMS" ColumnName="PRICE"/>
</property>
<property name="productname" type="string" length="255">
<annotation name="DMS" ColumnName="PRODUCTNAME"/>
</property>
<filter name="MyFill" order="price ASC"/>
</entity>

SQL*Modeler forgets check constraint names

SQL*Modeler Version 2.0.0. Build 584
If I create named check constraints under the Relational Model/Tables/Table level Constraints then generate the model I have the constraints correctly named. Exit the model and reload, the constraints appear to be correct but when I look at the physical model under tables/table check constraints I see generated names such as TCC4, TCC5 etc.
At this point I can change the name but this is not stored it is just thown away.
If I go back to Relational Model/Tables/Table level Constraints and simply Apply no changes then the constraint names appear correctly in the generated model. However, I have many tables and this is not a practial solution each time I generate the model.

Hi Ian,
thanks for feedback. Fix will be available in next release.
Philip

How can i get the column name   for assigned constraint name from the user_constraints   table?????

Hi ,
I have a table so many constraints   on so many columns. I need to know which column has which constraint plsql dev?? like below...
table_name -------- col_name ------ constraint_name_of_that_col
    xxxxxx              xxxxxxx              xxxxxxxxxxxxxxxx
or else please let me know how can i get the corresponding col_name for a particular constraint name???

My be this can give you a help:
[code]
SELECT *
FROM   ALL_CONSTRAINTS
WHERE R_CONSTRAINT_NAME IN (SELECT CONSTRAINT_NAME
                                                           FROM   ALL_CONSTRAINTS
                                                           WHERE TABLE_NAME = 'TABLE_NAME'
[/code]

VIEWING CONSTRAINT NAME IN QUERY TOOL

hi ,
i am using oracle lite 10g database lite R3 in windows platform . Now i have done a fresh client setup and datadownload in my machine. i am using query tool to view the datas . how to get
the constraint names in the query tool of a particular table.

Which tool are you using?
SELECT * FROM ALL_CONSTRAINTS WHERE TABLE_NAME = :TABLE_NAME

Domain range constraint name

HI all,
I have created a domain which has a range list. When this constraint is applied to the column in the relational model it has no associated name so a system name is generated. If I enter a name for the constraint in the attribute properties -> default and constraint this is not used by the relational model. Is there any way to assign a pre-defined name to a column constraint in the logical model that is also used by the relational model or do I have just to change the names for all the columns which use that particular domain?
thanks
Magnus

Hi Philip,
thanks for that. I was taking the FK names from the logical model so didnt think to apply the naming conventions as I didnt want to use the generated FK's as some of them are too long, but I see you can pick which constraint names to generate,
thanks
Magnus

Updating pk constraint name

Hi all
is thr any simple way to remane all primary key constraint names,
like if i have all pk constraints with name say in_abcd
and i want to update them all to pk_asdf,
how can we achieve this.
Thanks :)

[http://www.oracle-base.com/articles/9i/RenamingColumnsAndConstraints9i.php]
ALTER TABLE test RENAME CONSTRAINT test1_pk TO pk_test;

Import of table with proper constraint name

in my database i have named the constraints, i took an export of the database and tried to import to another database, but in the new database the user named constraint is changed to system named constraints.
Can any one let me know can this happen, but for indexes it remains the same.
Thanks in advance
Farzana

In databaseA (version oracle9i) i created the primary and foreign keys with corresponding table name.
when i imported the same dump on databaseB (version oracle10g), i saw that the name of the constraint has been changed to system generated one.
Can any one explain on it

How to get constraint name and table and column names

Hi Team,
I am a junior DBA. I want to check how many columns are under PRIMARY KEY constraint.
I used dba_constraints view. Please find below details.
SQL> select OWNER,CONSTRAINT_NAME,CONSTRAINT_TYPE,TABLE_NAME from dba_constraints
2 where TABLE_NAME='DSET_PRODUCT_S';
OWNER CONSTRAINT_NAME C TABLE_NAME
SCOTT SYS_C10202456 C EMPLOYEE
SCOTT SYS_C234576 C DEPT
Please suggest any one.
Regards,

Do you want to list the columns under a primary key?
This is listing index and columns:
SELECT cn.owner, cn.constraint_name, cn.constraint_type, cn.table_name
       , cn.index_owner, cn.index_name, ix.column_position, ix.column_name
    FROM dba_constraints cn, dba_ind_columns ix
   WHERE     cn.table_name = 'DSET_PRODUCT_S'
         AND cn.constraint_type = 'P'
         AND cn.index_owner = ix.index_owner
         AND cn.index_name = ix.index_name
ORDER BY cn.owner, cn.table_name, cn.index_owner, cn.index_name
       , ix.column_position;
{code}
Regards.
Al

Constraint names hardcoded !!!

Similar Messages

Maybe you are looking for