| Import Data [message #71330] |
Wed, 16 October 2002 19:00  |
GH Yap
Messages: 3
Registered: October 2002
|
Junior Member |
|
|
I'd done an import, and got the following error:
import done in UTF8 character set and UTF8 NCHAR character set
. importing LRSDBA's objects into MITAFPBP
. . importing table "CODE"
IMP-00058: ORACLE error 904 encountered
ORA-00904: invalid column name
About to enable constraints...
Import terminated successfully with warnings.
The import had done with the following parameteseetings:
NLS_LANG=AMERICAN_AMERICA.UTF8; export NLS_LANG
exp userid/passwd@abcprod FULL=n FILE=/a/b/abcprod_bkup.dmp log=abcprod.log
consistent=y buffer=200000000
The structure of my code table is as follow:
CREATE TABLE CODE (
COD_CODETYPE VARCHAR2(10) NOT NULL,
COD_CODE VARCHAR2(10) NOT NULL,
COD_DESC VARCHAR2(200),
COD_RANK NUMBER(5),
COD_STATUS VARCHAR2(1),
COD_REMARKS VARCHAR2(100),
COD_DATECREATE DATE,
COD_DATEUPDATE DATE,
COD_CREATEBY VARCHAR2(8),
COD_UPDATEDY VARCHAR2(8),
PRIMARY KEY(COD_CODETYPE, COD_CODE)
);
I'd checked the table and column names, they do not contain any reserved words.
Please help. It's urgent.
Thanks in advance.
|
|
|
|
| Re: Import Data [message #71397 is a reply to message #71330] |
Sun, 27 October 2002 22:16  |
Trifon Anguelov
Messages: 514
Registered: June 2002
|
Senior Member |
|
|
Your export data dictionary objects are not valid or screwed some how. Run the catexp.sql from $ORACLE_HOME/rdbms/admin
Also you can try with direct=n, but do the catexp.sql first.
Hope that helps,
clio_usa
OCP - DBA
Visit our Web site
|
|
|
|
| Re: Import Data [message #71407 is a reply to message #71330] |
Tue, 29 October 2002 11:44 |
Aaron
Messages: 13
Registered: January 2002
|
Junior Member |
|
|
From viewing the table table information that you have provided. You seem to be building the table with a column level constraint, defined at the table level.
Trying building the table again and define the constraint at the table level
CREATE TABLE CODE (
COD_CODETYPE VARCHAR2(10) NOT NULL,
COD_CODE VARCHAR2(10) NOT NULL,
COD_DESC VARCHAR2(200),
COD_RANK NUMBER(5),
COD_STATUS VARCHAR2(1),
COD_REMARKS VARCHAR2(100),
COD_DATECREATE DATE,
COD_DATEUPDATE DATE,
COD_CREATEBY VARCHAR2(8),
COD_UPDATEDY VARCHAR2(8),
CONSTRAINT cod_type_code_pk PRIMARY KEY(COD_CODETYPE, COD_CODE)
);
That should i believe eliminate your problem with the invalid column name.
Hope that helps
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
