Primary key problem using with oc4j

Hi everyone
I have deployed my entity bean in the oc4j container without any problem.But when I use the search->primary key in the console,no results display.
detail:
Step1I open the oc4j console by typing java -jar orion.jar -console
the oc4j container is successfully built
and in the left part of my console I see my entity bean
step2 I click my entity bean and in the right of the console in the search->primary key I type the a number which exists in my table in the database.
but no results display.
the following is my datasource-file anf orion-ejb-jar file
data-sources.xml
<?xml version="1.0"?>
<!DOCTYPE data-sources PUBLIC "-//Evermind//- Data-sources configuration" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
<data-sources>
     <data-source
          class="com.evermind.sql.DriverManagerDataSource"
          name="jdbc/OracleDSCore"
          location="jdbc/OracleDSCore"
          pooled-location="jdbc/OracleDSPooled"
          xa-location="jdbc/xa/OracleDSXA"
          connection-driver="oracle.jdbc.driver.OracleDriver"
          username="SCOTT"
          password="TIGER"
          url="jdbc:oracle:thin:@localhost:1521:b2b"
     />
</data-sources>
orion-ejb-jar.xml
<?xml version = '1.0' encoding = 'GBK'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
<orion-ejb-jar>
<enterprise-beans>
<entity-deployment name="EMP" data-source="jdbc/OracleDSCore" table="EMP" >
<primkey-mapping>
<cmp-field-mapping>
<fields>
<cmp-field-mapping name="EMPNO"
persistence-name="EMPNO" persistence-type="VARCHAR2(4)"/>
</fields>
</cmp-field-mapping>
</primkey-mapping>
</entity-deployment>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping name="<default-ejb-caller-role>" impliesAll="true"/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>
Any answer is welcome. Thankou in advance!

Fernando,
I see you suffer a lot with ADF...write me at [email protected] and letÂ´s keep in touch.
Maybe we can do a Brazilian list for JDev/ADF.
Regards,
Marcelo Alcantara

Similar Messages

Primary key generation: Using CounterHome?

I can't find any documentation that talks about automatic primary key generation support on OC4J. I noticed the article on the Orion Support page that mentions their "Counter" bean. Is this the extent of support for automatic primary key generation in OC4J? When I searched for this class in the distribution, I only found it in a demo application in JDeveloper.
Is this something that is handled directly in the Oracle DB, which is why OC4J doesn't bother to support it?

Sorry I wasn't specific. By "going nowhere", I meant it went to an error page on the orion site. I don't know why it couldn't find it, because when I just now searched for the article with the title you just gave, the resulting URL was identical to what you gave me originally.
As to the "counter faq", I think I've seen that before, but I can't get to it right now (server overloaded or something). The one problem I remember with trying to pursue the "counter" solution was somewhat simple. I couldn't find the code. I didn't notice a download for the "Counter" class, and I can't find it in either the jdeveloper or oc4j distributions.
In any case, I ended up implementing the UUID solution, based on Floyd Marinescu's example in "EJB Design Patterns". I think this will work fine for our application.
I'd still like to know more about Orion's "Counter" solution, if there's any real code available to see.

Replication for Data on DEV and QA - bad idea - primary key problem now

I goofed. I tried to use replication to keep the data on my dev machine up to date with the live server. Now when I try to work on the database, adding new stuff, it fails. It says there is a primary key problem every time I try to add
a new item to a table with my program. I should have realized this would happen! Now, even though I've removed the replication, I'm having the problem. Can anyone help me get my database functional again :/ Or should I resort to a database
restore. Thanks!

So you have an IDENTITY column in your table? Run a
DBCC CHECKIDENT (Transact-SQL) command with option RESEED to fix the current identity value to see if it works then.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Unique or primary key on timestamp with timezone

Hi,
I have been experimenting with a date column in a primary key, or actually I tried using a timestamp with time zone in a primary key.
While researching whether there was a way to avoid ORA-02329, I found the following:
K15> create table dumdum
2    (datum date not null
3    ,naamp varchar2( 30 ) not null);
Table created.
K15>
K15> alter table dumdum
2    add constraint d_pk
3        primary key
4          (datum, naamp)
5    using index;
Table altered.
K15>
K15> select ind.index_type
2 from   user_indexes ind
3 where ind.index_name = 'D_PK';
INDEX_TYPE
NORMAL
1 row selected.
K15>
K15> insert into dumdum
2    (datum
3    ,naamp )
4 select sysdate - (level/1440)
5 ,      'nomen nescio'
6 from   dual
7 connect by level < 1000
8 ;
999 rows created.
K15>
K15> analyze index d_pk validate structure;
Index analyzed.
K15> analyze table dumdum compute statistics;
Table analyzed.
K15>
K15> select naamp
2 from   dumdum
3 where datum > to_date('16-06-2011 15.46.16', 'dd-mm-yyyy hh24.mi.ss' )
4
K15> For the last select statement I get the following "explain plan":
SELECT STATEMENT CHOOSE
          Cost: 2 Bytes: 247 Cardinality: 13
     1 INDEX RANGE SCAN UNIQUE D_PK
                Cost: 3 Bytes: 247 Cardinality: 13 This behavior lived up to my expectations.
Then, I tried this:
K15> create table dumdum
2    (datum date not null
3    ,naamp varchar2( 30 ) not null);
Table created.
K15>
K15> alter table dumdum
2    add constraint d_pk
3        primary key
4          (datum, naamp)
5    using index;
Table altered.
K15>
K15> alter table dumdum
2        modify datum timestamp(6) with time zone;
Table altered.
K15>
K15> select ind.index_type
2 from   user_indexes ind
3 where ind.index_name = 'D_PK';
INDEX_TYPE
NORMAL
1 row selected.
K15>
K15> insert into dumdum
2    (datum
3    ,naamp )
4 select sysdate - (level/1440)
5 ,      'nomen nescio'
6 from   dual
7 connect by level < 1000
8 ;
999 rows created.
K15>
K15> analyze index d_pk validate structure;
Index analyzed.
K15> analyze table dumdum compute statistics;
Table analyzed.
K15>
K15> select naamp
2 from   dumdum
3 where datum > to_date('16-06-2011 15.46.16', 'dd-mm-yyyy hh24.mi.ss' )
4
K15> So, at first glance, the alter table statement to change the datatype from DATE to TIMESTAMP seems like a way of fooling Oracle. But the explain plan reveals a different story:
SELECT STATEMENT CHOOSE
          Cost: 4 Bytes: 1,25 Cardinality: 50
     1 TABLE ACCESS FULL DUMDUM
                Cost: 4 Bytes: 1,25 Cardinality: 50 I was only fooling myself. :-0
But I wasn't done with my research:
K15> create table dumdum
2    (datum timestamp(6) with time zone not null
3    ,naamp varchar2( 30 ) not null);
Table created.
K15>
K15> create unique index d_ind
2      on dumdum
3           (datum, naamp);
Index created.
K15>
K15>
K15> select ind.index_type
2 from   user_indexes ind
3 where ind.index_name = 'D_IND';
INDEX_TYPE
FUNCTION-BASED NORMAL
1 row selected.
K15>
K15> insert into dumdum
2    (datum
3    ,naamp )
4 select systimestamp - (level/1440)
5 ,      'nomen nescio'
6 from   dual
7 connect by level < 1000
8 ;
999 rows created.
K15>
K15> analyze index d_ind validate structure;
Index analyzed.
K15> analyze table dumdum compute statistics;
Table analyzed.
K15>
K15> select naamp
2 from   dumdum
3 where datum > to_date('16-06-2011 15.56.16', 'dd-mm-yyyy hh24.mi.ss' )
4
K15>Now, my explain plan looks fine:
SELECT STATEMENT CHOOSE
          Cost: 2 Bytes: 1,25 Cardinality: 50
     1 INDEX RANGE SCAN UNIQUE D_IND
          Cost: 3 Bytes: 1,25 Cardinality: 50 Why is Oracle so adamant about not allowing a timestamp with time zone in a unique key? And, given their position on the matter, where does their tolerance for a unique index come from?
By the way, if I had a say in it, I would not allow anything that even remotely looks like a date to be part of a primary key, but that's another discussion.
Thanks,
Remco
P.S. All this is on Oracle9i Enterprise Edition Release 9.2.0.8.0. Is it different on 10g or 11g?

See if this helps. You can create primary key for TIMESTAMP WITH LOCAL TIME ZONE datatype.
SQL>CREATE TABLE Mytimezone(Localtimezone TIMESTAMP WITH LOCAL TIME ZONE primary key, Location varchar2(20) );
Table created.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch4datetime.htm#i1006169
TIMESTAMP WITH LOCAL TIME ZONE Datatype
TIMESTAMP WITH LOCAL TIME ZONE is another variant of TIMESTAMP. It differs from TIMESTAMP WITH TIME ZONE as follows: data stored in the database is normalized to the database time zone, and the time zone offset is not stored as part of the column data. When users retrieve the data, Oracle returns it in the users' local session time zone. The time zone offset is the difference (in hours and minutes) between local time and UTC (Coordinated Universal Time, formerly Greenwich Mean Time).
Thanks
http://swervedba.wordpress.com/

Generating a Primary Key WITHOUT using a Sequence Number

Hi Everyone:
I am trying to generate a primary key without using a sequence number or row count. What the user wants is the maximum value of the highest primary key already in the row set plus 1.
For example, this is a Oracle Table (eg. named BatchSubmit) used to initiate batch job submission, and the primary key is an integer named "Runcard_Number". If there are 4 rows in this table and the Runcard_Numbers are 2, 6, 8 & 12, then the next generated Runcard_Number would be 13.
I have looked throughout this forum and see how to generate numbers using a DBSequence, but the user does not want that. The numbers mean something to them, and they don't want them randomly assigned other than the max in the rowset plus 1. To do it in SQL it would be - select max(Runcard_Number) + 1 from BatchSubmit;
I have been looking at using a hasnext loop and moving the maximum value to the new Runcard_Number, but I am very new to JHeadstart/JDev and I do not know where to put this. I am assuming the BatchSubmitImpl.java, but I'm not sure where to put it or which method to utilize
I would appreciate any assistance.
Mary
U o Windsor

Mary you're in luck, 'cause, I've been playing with the same thing, these days and found that..
You can do that in two ways (that I know):
- by calling a stored function that does max+1 (you can look it up in Dev's guide for Forms&4GLDevs 10g chapter 25.5 Invoking Stored Procedures and Functions)
- by calling hardcoded or dinamicaly written statement, that does the same
public Number callStatement(String stmt)
Number id = new Number(0);
Row idRow = getDBTransaction().createViewObjectFromQueryStmt(stmt).next();
if(idRow != null)
Object o = idRow.getAttribute(0);
if(o != null)
if(o instanceof Number)
id = (Number)o;
else
throw new JboException("Conversion error!");
return id;
You should call it in
protected void doDML(int operation, TransactionEvent transactionEvent)
switch (operation)
case DML_INSERT:
// call here
super.doDML(operation, transactionEvent);
break;
case DML_UPDATE:
super.doDML(operation, transactionEvent);
break;
case DML_DELETE:
super.doDML(operation, transactionEvent);
break;
Enjoy!
S. Julijan

Help with primary key problem

Oracle 9.2.0 on Red Hat Linux advanced server 2.1
(There are a number of large tables that this applies to)
I have a partitioned table where during the creation of the table a Primary key was declared and was placed 'using index tablespace primary_key'. So the table is created, and the primary key is set to use the 'primary_key' tablespace.
Since our loads are quite large, we disable constraints during the load process, then enable them after the load has completed. Here's the problem, when the constraints are enabled, the tablespace for constraints change to the default tablespace of the schema owner.
We have a specific tablespace created to hold the primary keys of the various tables, called 'primary_key'. The schema owner has his own default tablespace called 'POWER1'. When the schema owner runs the enable script to enable the primary keys, they all start being placed in 'POWER1' which is not nearly as large as 'primary_key' and as a result the first couple primary keys are created in 'POWER1' and then 'unable to extend segment in tablespace POWER1' pops up and the rest of the primary keys fail to enable.
The workaround for this is to set the default tablespace for the schema owner to to be 'primary_key' but that is not what we really want.
any feedback on this is appreciated, thanks

In the old days, when we disabled a primary constraint, Oracle dropped the index. When we re-enabled the constraint the index was built again. But, if we didn't specify the index tablspace when we re-enabled the constraint the index was built in the default tablespace. Which is what is happening to you now.
In 9i Oracle added the KEEP INDEX clause, which allowed us to retain the index even though the primary key was no longer enforced. However, as your aim is to increase the speed of data take on, you in fact want the index dropped. So, what you need to do is:
ALTER TABLE whatever DISABLE PRIMARY KEY
DROP INDEX;
ALTER TABLE whatever ENABLE PRIMARY KEY
USING INDEX TABLESPACE indx;Cheers, APC

CMP with Auto-increment Primary Key problem

I'm trying to set a column as IDENTITY in PointBase and have the app server utilize this in the CMP beans. I followed the instructions from the tutorial:
- In the deployment descriptor, the primary key class is defined as a java.lang.Object. The primary key field is not specified.
- In the home interface, the argument of the findByPrimaryKey method must be java.lang.Object.
- In the entity bean class, the return type of the ejbCreate method must be a java.lang.Object.
Below is (a fragment of) my deployment descriptor:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<display-name>CMPModule</display-name>
<enterprise-beans>
<entity>
<display-name>DocState</display-name>
<ejb-name>DocState</ejb-name>
<home>com.sun.itstar.j2ee.projectdocmgt.ejb.DocStateHome</home>
<remote>com.sun.itstar.j2ee.projectdocmgt.ejb.DocState</remote>
<local-home>com.sun.itstar.j2ee.projectdocmgt.ejb.LocalDocStateHome</local-home>
<local>com.sun.itstar.j2ee.projectdocmgt.ejb.LocalDocState</local>
<ejb-class>com.sun.itstar.j2ee.projectdocmgt.ejb.DocStateBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Object</prim-key-class>
<reentrant>False</reentrant>
<abstract-schema-name>DocState</abstract-schema-name>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>description</field-name>
</cmp-field>
<cmp-field>
<field-name>color</field-name>
</cmp-field>
</entity>
In the admin-serv/logs directory I get the follow message (bad place for the logs, took me a while to find where it was putting it!):
[24/Sep/2002:16:33:57] WARNING ( 4165): Validation error in bean DocumentType: Warning: All primary key columns in primary table DOCUMENT_TYPE of the bean corresponding to the generated class com.sun.itstar.j2ee.projectdocmgt.ejb.DocumentTypeBean_387898907_JDOState must be mapped to key fields.
Map the following primary key columns to key fields: DOCUMENT_TYPE.ID. If you already have fields mapped to these columns, verify that they are key fields.

Great! This worked. Here are some clear steps:
1. delete the field from the CMP
2. delete any business methods that you might have for the field
3. go to the properties of the bean, find the primary key property. Set the property to Unkown Primey Key Class (java.lang.Object)
Now there is a bigger problem. CMR fields. In ejbPostCreate() the bean gets its own pk and looks up other related beans. Now that I have removed the accessor to the pk field (and the pk field from the bean), how do I lookup the relationships?
I need some method that I can call from within ejbPostCreate() that will return the primary key...
I tried adding the field back in but not as the primary key. That generated an exception that said you cannot do that. If the field is the pk it must be marked as the pk.
Any ideas?

Primary Key problem in 11g - Known issue 6894412

Hi Everyone:
We are on JDeveloper 11.1.1.4, and JHeadstart 11.1.1.2.46. This thread originally started on the JHeadstart forum and can be seen at: Problem with LOV's in 11g
We are converting our 10g application to 11g. We have an established Oracle database that does not use pre-populated primary keys that are sequence number. Our database has composite keys and the integrity of those composite keys are established by foreign key constraints to edit tables. This approach has worked extremely well for us for over a decade, the logic of the database has been designed so that the database protects itself through the elimination of cascade deletes where necessary, and cascade deletes as the business logic dictates. This will not be changing.
In the database tables in which the 10g application has been displayed in the table format, after conversion to 11g, the LOV pop-ups are not working unless the SAVE button (or refresh of the browser) has been pressed. The first LOV pop-up will work, but as soon as you select a value from it, the next LOV pop-ups will not execute until the SAVE or REFRESH is done. This is only in table format. If the display format is form, our primary key LOV's work fine. In 10g, this functionality worked fine as long as we didn't use an "ADD ROW" button on a table format. The Add Row button caused the primary key values to be returned to the application, but not be displayed on the screen. A refresh would then show them.
From the initial investigation in the JHeadstart forum, I realize that we are hitting the "Primary Keys from Model" 6894412 problem that is listed in the 11.1.1.4 Release Notes. We have spent many, many hours establishing a re-usable .jar file of all of the entities of this very large database as suggested by JDeveloper Best Practises (http://download.oracle.com/docs/cd/B31017_01/web.1013/b25947/bcadvgen007.htm). This has worked very well for us in 10g - define all the entity specifics in one place, once, then every application can re-use them. Productivity at its finest. Therefore, we cannot make fake columns in our database in order to fix this "limitation" in 11g. We have many complex parent/child/child tables to put into our application which will not work unless our entities have the primary keys properly defined. I have tried to implement the workaround that was found in the release notes, but have been unable to get it to work.
I have created a testcase with the HRSchema by adding a table to that Schema that I can provide the SQL commands for, but I do not know who in Oracle support to send it to. Could someone please provide me with the information on who to contact. I have, I believe, taken all the steps as established in the release notes for this problem and have clearly documented the changes in the .jsff page, but the problem still exists. Clearly, I am doing something wrong, or need more information.
Thank you in advance
Mary
UofW

Frank:
I thank you for your reply.
I have been working on the JHeadstart forums for so long, I actually forgot how to submit things to Metalink, and now that I have done it again...SR #3-3101357281 for this issue....I realize why I blocked out using Metalink from my memory.
It took me an incredible amount of time to fill that SR in, then after completing everything, I was sent a request by the person assigned to the SR to repeat the instructions of how to run my testcase. I had already filled out all of the instructions on how to run the testcase in the "Notes to Oracle" section of the upload step. Almost every time I send something to Metalink, I have to repeat things. It seems as though they aren't read fully and any reason at all is used to send them back to the client.
My dealings with Metalink have been very, very frustrating. My colleagues share this sentiment.
Mary
UofW

Primary key problem - Urgent! PLEASE, HELP!

Hi all,
I'm new here, and I have a stupid problem, I think. If someone could help me, I'll be grateful.
I have to build a very simple JSP application using a few database tables, providing the base functionality: insert, update, delete, search.
I'm using Oracle 8.1.7, and JDeveloper 9.0.3
One table looks like that:
CREATE TABLE TEST (
     sPrimaryKey varchar2(30) not null,
     sField varchar2(100)
ALTER TABLE TEST
ADD ( CONSTRAINT test_id_pk
          PRIMARY KEY (sPrimaryKey)
I'm using a sequence for generating primary key...
CREATE SEQUENCE test_seq
START WITH 100
INCREMENT BY 1
NOCACHE
NOCYCLE;
... and a trigger before insert for seting the new value of the primary key.
CREATE OR REPLACE TRIGGER BI_TEST
BEFORE INSERT ON TEST
FOR EACH ROW
DECLARE
     new_id integer;
BEGIN
     select test_seq.nextval into new_id from dual;
     :new.sPrimaryKey := 'AAA' || new_id;
END;
I have created a BC4J. How can I insert a new row into that table without providing the primary key, by hand, and let the trigger and sequence do that?
Thank you!
Razvan

In the attribute settings editor for the Attribute TestIdPk in Entity Test:
select Updateable Never
deselect Mandatory
select Refresh After Update & Refresh After Insert
HTH.
Thanks, George

How can we export the Primary key values (along with other data) from an Advantage database?

One of our customers is moving from our application (which uses Advantage Database Server) to another application (which uses other database technology). They have asked us to help export their data, so that they can migrate it to another database system. So far, we have used the Advantage Data Architect (ARC32) "Export Table Structures as Code" functionality to generate SQL. We used the "Include existing data" option. The SQL contains the necessary code to recreate the tables and indexes. The customer's IT staff will alter the SQL statements as necessary for their new system.
However, there is an issue with the Primary Keys in these table. The resulting INSERT statements use AutoInc as the type for the Primary Key in each Table. These INSERT statements contains "DEFAULT" for the value of each of these AutoInc fields. The customer would like to output an integer value for each of these Primary Key values in order to maintain referential integrity in their new system.
So far, I have not found any feature of ARC32 that allows us to export the Primary Key values. We had been using an older version of ARC32, since our application does not use the latest version of ADS. I did download the latest version of ARC32 (11.10), but it does not appear to include any new functionality that would facilitate doing this sort of export.
Can somebody tell me if there is such a feature in ARC32?
Or, is there is another Advantage tool to facilitate what we are trying to accomplish?
If there are no Advantage tools to provide such functionality, what else would you suggest?

George,
It sounds like the approach you are using is the correct one. This seems to be the cleanest solution to me especially since the customer is able to modify the generated SQL statements for their new system.
In order to preserve the AutoInc values I would recommend altering the table and changing the field datatype from AutoInc to Integer. Then export the table as code which will export the actual values. After the tables have been created on the new system they can change the field datatype back to an AutoInc type if necessary.
Regards,
Chris Franz

Entity bean - Unknow primary key problem

Hi,
We are using entity bean with unknown primary key option to generate the primary key automatically. It works for all the tables except one table. What we observe is, auto generated primary key is less than the max value in the table and is clashing with one existing record. Any thoughts on what could be wrong?
Your help is highly appreciated.
Regards,
Chandra
Edited by: Chandrashekhar Singh on Mar 3, 2008 6:39 PM

Hi,
I think Vladimir's answer can help you.
[Entity bean - getting Duplicate Key Exception on ejbCreate;
Regards
Pavel

Could I try to use with OC4J another XML transformer factory than default?

Hello, the masters of masterpieces.
The application was written and deployed on TomCat 4.0 with standard xalan.jar and xerces.jar from Apache projects?
I want to run it on OC4J-instance.
Could I try to use different XML transformer factory than default with OC4J? If I use Apache's jars inside
classpath it can't help, really: every time request goes to oracle xml-transformer. Please, any advices or
comments. I'll appreciate every advice which can't destroy the functionality of AppServer.
Thanks. Regards. Igor.

Hi,
I had this same problem where I needed Xalan (more robust). Step I took:
1) Unjar oc4j.jar into a clean directory
2) Modify ParserManager.properties to
defaultParser = xerces
3) Modify MANIFEST.MF such that xerces.jar and xalan.jar are early on the classpath
Class -Path ejb.jar xerces.jar xalan.jar ...
4) Then re-jar the file back up
jar -cfm oc4j.jar META-INF/MANIFEST.MF .
5) Copy oc4j.jar as well as xerces.jar and xalan.jar into your j2ee/home directory (making a backup of your previous oc4j.jar to play it safe).
Larry

Primary key columns dropped with cascade constraint

Hi,
My developer dropped one column from table which was having primary key . (primary key on two columns now one column is there)
he used SQL > alter table table_name drop columns cascade constraints.
Now i want to enable the constraint. the constraint is not there. if i am creating the primary key with the existing single column alone.
My question how do i know which was the dependency it had? (like foreign key / child tables it had?) and how to rebuild the relationship?
Thanks
--Raman

Hemangi,
i am just wondering before dropping the column we had primary key. (as i mentioned earlier the primary key was created for two columns ) .
now if i am re-building by just adding primary key to the existinc column alone i am facing this error.
Let me see if there is any null or duplicate values in the column.
Thanks
--Raman

Oracle 10g express edition primary key problem

Hi , i have a database with varchar as primary key eg.SEG. however after i insert row and set priamry key as SEG , the primary key will be displayed as number eg.1 and not SEG. Why is it so?

835401 wrote:
Table Data Indexes Model Constraints Grants Statistics UI Defaults Triggers Dependencies SQL
CREATE TABLE "TEST_DEPARTMENT"
(     "DEPT_CODE" VARCHAR2(10) NOT NULL ENABLE,
     "DEPT_NAME" VARCHAR2(50),
     CONSTRAINT "TEST_DEPARTMENT_PK" PRIMARY KEY ("DEPT_CODE") ENABLE
CREATE OR REPLACE TRIGGER "BI_TEST_DEPARTMENT"
before insert on "TEST_DEPARTMENT"
for each row
begin
select "TEST_DEPARTMENT_SEQ".nextval into :NEW.DEPT_CODE from dual;
end;
ALTER TRIGGER "BI_TEST_DEPARTMENT" ENABLE
This is my SQLSo why is DEPT_CODE defined as VARCHAR2(10) when you are going to populate it (via the trigger) with a NUMBER?

Cannot insert null into a Primary Key Column using Entity Framework

I have to insert data into UserPreferences Table which has a primary key. This I am doing with Oracle Entity Framework Provider.
It is unable to do it though i have set the StoreGeneratedPattern = "Identity". But while saving changes it is saying a null error is being inserted into the primary key.

I exported the same package to BIDS and ran it but still unable to get the issue. It is running fine.
Also then same package is running fine in other environments.
Thanks
Thats strange
Are you pointing to same databases itself while executing from server?
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Primary key problem using with oc4j

Similar Messages

Maybe you are looking for