EF Wizard Error: The given key was not present in the dictionary.

EF Wizard Error: The given key was not present in the dictionary.

Postby kingalef » Fri 08 Feb 2008 13:00

Hi,
I am trying to generate a EF model but I get this error:

Error
---------------------------
Value cannot be null.
Parameter name: storeEntityContainer
Generator warnings:
Error Code: 6003
Severity: Error
Message: The given key was not present in the dictionary.

I tried generating the model on the full DB or just one table and both approaches return the same error.
The one table I tried against is this:

CREATE TABLE MASTNAME (
LNAME VARCHAR2(40),
FNAME VARCHAR2(15),
RECNUM NUMBER NOT NULL,
MIDDLE VARCHAR2(15),
NICKNAME VARCHAR2(15),
HOUSE NUMBER,
NSEW VARCHAR2(2),
STREET VARCHAR2(25),
ADDRESS2 VARCHAR2(30),
CITY VARCHAR2(20),
ST VARCHAR2(3),
ZIP VARCHAR2(10),
PHONE VARCHAR2(14),
SSN VARCHAR2(11),
DOB DATE,
AGE NUMBER,
SEX VARCHAR2(1),
RACE VARCHAR2(2),
ETHNIC VARCHAR2(1),
HGT NUMBER,
WGT NUMBER,
EYES VARCHAR2(6),
HAIR VARCHAR2(6),
GLASSES VARCHAR2(1) DEFAULT 'N',
FACIALHAIR VARCHAR2(6),
POB VARCHAR2(35),
HOUSECHECK VARCHAR2(1) DEFAULT 'N',
ALARM VARCHAR2(1) DEFAULT 'N',
ARREST_NUM VARCHAR2(12),
FBI VARCHAR2(15),
SBI VARCHAR2(15),
SBI_ST VARCHAR2(3),
DRLIC VARCHAR2(20),
DRLIC_ST VARCHAR2(3),
SOUND_N VARCHAR2(5),
SOUND_A VARCHAR2(5),
CREATED_ON DATE,
CREATED_BY VARCHAR2(7),
UPDATED_ON DATE,
UPDATED_BY VARCHAR2(7),
CUSTOM_CODE_01 VARCHAR2(6),
CUSTOM_CODE_02 VARCHAR2(6),
CUSTOM_DATE_01 DATE,
CUSTOM_DATE_02 DATE,
CUSTOM_DATE_03 DATE,
CUSTOM_DATE_04 DATE,
CUSTOM_NUM_01 NUMBER,
CUSTOM_NUM_02 NUMBER,
CUSTOM_NUM_03 NUMBER,
CUSTOM_NUM_04 NUMBER,
CUSTOM_TEXT_01 VARCHAR2(25),
CUSTOM_TEXT_02 VARCHAR2(25),
CUSTOM_TEXT_03 VARCHAR2(25),
CUSTOM_TEXT_04 VARCHAR2(25),
KNOWN_OFFENDER VARCHAR2(1) DEFAULT 'N',
JUVENILE VARCHAR2(1) DEFAULT 'N',
PICT1FILE VARCHAR2(50),
PICT2FILE VARCHAR2(50),
PICT3FILE VARCHAR2(50),
PICT4FILE VARCHAR2(50),
PICT1COMT VARCHAR2(255),
PICT2COMT VARCHAR2(255),
PICT3COMT VARCHAR2(255),
PICT4COMT VARCHAR2(255),
BUILD VARCHAR2(6),
COMPLEXION VARCHAR2(6),
HAIR_LENGTH VARCHAR2(6),
JG_NAME VARCHAR2(35),
JG_ADDR VARCHAR2(35),
JG_CSZ VARCHAR2(35),
JG_PHN1 VARCHAR2(14),
JG_PHN2 VARCHAR2(14),
JM_NAME VARCHAR2(35),
JM_ADDR VARCHAR2(35),
JM_CSZ VARCHAR2(35),
JM_PHN1 VARCHAR2(14),
JM_PHN2 VARCHAR2(14),
JF_ADDR VARCHAR2(35),
JF_NAME VARCHAR2(35),
JF_CSZ VARCHAR2(35),
JF_PHN1 VARCHAR2(14),
JF_PHN2 VARCHAR2(14),
J_SCHOOL VARCHAR2(35),
J_GRDE VARCHAR2(14),
ALARM_ID VARCHAR2(12),
NAMEFLD VARCHAR2(36),
NAME_TYPE VARCHAR2(6),
RESISTER VARCHAR2(1),
WEAPONS_FLAG VARCHAR2(1),
DISPFLAG VARCHAR2(1),
MARITAL_STATUS VARCHAR2(6),
OCCUPATION VARCHAR2(6),
PHONE_2 VARCHAR2(14),
WAR_FLAG VARCHAR2(1),
COBRA_WARN NUMBER,
COBRA_DATE DATE,
COBRA_BY VARCHAR2(7),
SUFX VARCHAR2(6),
FACIALJEWELRY VARCHAR2(6),
AMPUTATIONS VARCHAR2(6),
GANG VARCHAR2(6),
EYECHAR VARCHAR2(6),
TEETH VARCHAR2(6),
HAIRSTYLE VARCHAR2(6),
MEGANS_LAW VARCHAR2(1),
JVIS VARCHAR2(1),
JVIC VARCHAR2(1),
OWNPROG VARCHAR2(1) DEFAULT 'R',
OWNAGCY VARCHAR2(3),
DUP_REC NUMBER,
EMAIL VARCHAR2(50),
POB_ST VARCHAR2(3),
POB_CNTRY VARCHAR2(6),
BUSN VARCHAR2(1),
EIN VARCHAR2(11),
BIRTH_CERT VARCHAR2(20),
PASSPORT VARCHAR2(20),
INS_NUMBER VARCHAR2(20),
WEB_ADDR VARCHAR2(100),
CITIZEN VARCHAR2(2),
DSI_SYSID NUMBER,
DSI_PCP VARCHAR2(12),
DSI_IMG_SYSID NUMBER,
CBI VARCHAR2(15),
CCN VARCHAR2(7),
MO_CODE VARCHAR2(4),
ORIG_ADDRESS VARCHAR2(67),
ALERT_1 VARCHAR2(1),
ALERT_2 VARCHAR2(1),
ALERT_3 VARCHAR2(1),
ALERT_4 VARCHAR2(1),
ALERT_DATE_1 DATE,
ALERT_DATE_2 DATE,
ALERT_DATE_3 DATE,
ALERT_DATE_4 DATE,
PHONE_3 VARCHAR2(14),
PHONE_4 VARCHAR2(14),
PHONE_5 VARCHAR2(14),
DECEASED VARCHAR2(1),
DECEASED_DATE DATE,
DRLIC_CLASS VARCHAR2(10),
DRLIC_DATE DATE,
FPRINT_DATE DATE,
PHOTO_DATE DATE);

ALTER TABLE MASTNAME ADD (
PRIMARY KEY (RECNUM));

CREATE INDEX MASTNAME_SEX ON MASTNAME (SEX);

CREATE INDEX MASTNAME_NICKNAME ON MASTNAME (NICKNAME);

CREATE INDEX MASTNAME_PHONE ON MASTNAME (PHONE);

CREATE INDEX MASTNAME_SSN ON MASTNAME (SSN);

CREATE INDEX MASTNAME_NAMEFLD ON MASTNAME (NAMEFLD);

CREATE INDEX NAME_DSI ON MASTNAME (DSI_SYSID);

CREATE INDEX MASTNAME_SOUNDA ON MASTNAME (SOUND_A);

CREATE INDEX MASTNAME_CCN ON MASTNAME (CCN);

CREATE INDEX MASTNAME_JVIS ON MASTNAME (JVIS);

CREATE INDEX MASTNAME_JVIC ON MASTNAME (JVIC);

CREATE INDEX MASTNAME_FNAME ON MASTNAME (FNAME);

CREATE INDEX MASTNAME_STREET ON MASTNAME (STREET, HOUSE, NSEW);

CREATE INDEX MASTNAME_ARRNUM ON MASTNAME (ARREST_NUM);

CREATE INDEX MASTNAME_LNAME ON MASTNAME (LNAME);

CREATE INDEX MASTNAME_MIDDLE ON MASTNAME (MIDDLE);

CREATE INDEX MASTNAME_DRLIC ON MASTNAME (DRLIC);

CREATE INDEX MASTNAME_SOUNDN ON MASTNAME (SOUND_N);

CREATE INDEX MASTNAME_DOB ON MASTNAME (DOB);

CREATE INDEX MASTNAME_CITY ON MASTNAME (CITY);

CREATE INDEX MASTNAME_ZIP ON MASTNAME (ZIP);

There are also some triggers attached to the table, but I dont think that makes any difference...

Thanks,
Alessandro Federici
kingalef
 
Posts: 5
Joined: Wed 30 Jan 2008 20:40

Postby Alexey.mdr » Fri 08 Feb 2008 14:55

We have reproduced the error.
Now our developers are investigating the source of the problem.
We will fix the issue in the next build.
Alexey.mdr
 
Posts: 729
Joined: Thu 13 Dec 2007 10:24


Return to dotConnect for Oracle