cannot insert NULL into ("QUARKDMS"."MAM_ASSETS"."INDEX_SOURCE")
stop trying to insert nullls into the column
It's import which is inserting. How can I control it. The column is BLOB type.
Structure of mam_assets is:
ID NOT NULL NUMBER(10)
ACL_ID NOT NULL NUMBER(10)
ASSET_GROUP_XID NOT NULL NUMBER(10)
CONTAINED_IN_COUNT NOT NULL NUMBER(6)
CONTAINER_OF_COUNT NOT NULL NUMBER(6)
RELATED_WITH_COUNT NOT NULL NUMBER(6)
ARCHIVE_STATUS NOT NULL NUMBER(1)
IS_CURRENT_VERSION NOT NULL NUMBER(1)
STORAGE_CHANGE_REQUEST NOT NULL NUMBER(1)
HAS_HISTORY NOT NULL NUMBER(1)
FAMILY_ID NOT NULL NUMBER(10)
FTS_TEXT NOT NULL CLOB
FTS_LANG NOT NULL VARCHAR2(3)
INDEX_SOURCE NOT NULL BLOB
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
I separately created the table MAM_ASSETS and removed NOT NULL from problematic columns. Then I used ignore=y option to import. But somewhere while importing, it creates NOT NULL constraints on these columns and I again start receiving the same error.
What can I do here? How could I remove the code from import that creates NOT NULL constraints?
Or as a workaround, I am able import only MAM_ASSETS table. But now the problem is that I don't want to import MAM_ASSETS while importing the rest of schema. IMP doesn't provide something like exclude as in IMPDP.
Last edited by mahajanakhil198; 05-13-2010 at 09:12 AM.
Akhil - look into constraints=n and indexes=n imp options.
how many tables you are trying to import? if you don't want to use constraints=n indexes=n then provide individual table names to imp excluding the one you have already imported.
Around 98 tables are there.
Is there a way to import constraints only later on If I use constraints=no?
I was thinking of some other workaround. Firstly import only MAM_ASSETS table with no constraints and indexes. Then, use import with ignore=n. When table MAM_ASSETS is reached, it will be skipped with error and its indexes and constraints should get imported. I wonder if it would work.
Last edited by mahajanakhil198; 05-13-2010 at 10:30 AM.
but, first place I am wordaring why imp is trying to insert null values. Because I am sure the NOT NULL constraint is there on the source table so no chance of having null values in source. Does it mean that the BLOB column data is not exported??
as the other poster said, drop that table with cascade constraints and let imp create the table and see how it goes.
Try hard to get what you like OR you will be forced to like what you get.