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.
Thanks,
I am arranging some more disk space as I am running out of it. Though I dropped the entire schema and tried import again.
I will try to do it the way as I suggested in my previous post and then let you know.
1.I am not even able to import only MAM_ASSETS table without indexes and constraints. It gets stuck with the same error, probably because create table clause for MAM_ASSETS contains NOT NULL clause for columns INDEX_SOURCE and FTS_TEXT.
2. However, I also got the CREATE TABLE MAM_ASSETS using SHOW=Y option of imp. Using this, I manually created the MAM_ASSETS table and deleted the NOT NULL clauses for problematic columns. Then I tried to re-import the remaining data using IGNORE=Y option of IMP. Ideally, it should have imported the rows in MAM_ASSETS table but even it also returns the same error as posted in my first post.
Following this, I saw the description of MAM_ASSETS table to see if there is no NOT NULL constraint on the MAM_ASSETS table. To my surprise, these columns had NOT NULL constraint present on them. Should it have happened? I think no because the create table statement should have been ignored without errors and the rows should have gotten imported.
Please follow guide and spool off eveything you do - in case something happens we will appreciate to see whole session.
1- Drop MAM_ASSETS table
2- Create MAM_ASSETS - be sure no column has NOT NULL option
3- desc MAM_ASSETS
4- import MAM_ASSETS with options... ignore=y indexes=n constraints=n
5- desc MAM_ASSETS
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.
Please follow guide and spool off eveything you do - in case something happens we will appreciate to see whole session.
1- Drop MAM_ASSETS table
2- Create MAM_ASSETS - be sure no column has NOT NULL option
3- desc MAM_ASSETS
4- import MAM_ASSETS with options... ignore=y indexes=n constraints=n
5- desc MAM_ASSETS
Still receiving the same error.
But the NOT NULL constraints for columns don't come after importing rows of table. Attached is the spool file.
Some 8,28,000 rows get imported and the following error gets generated repetitively for 20-25 times during import.
Import: Release 10.1.0.2.0 - Production on Mon May 17 17:35:34 2010
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V09.02.00 via conventional path
Warning: the objects were exported by SYSTEM, not by you
Now that we can see... we can help better.
Are you running Ora10g 10.1? this matches bug #3467567
Check Metalink... if running on Ora10g 10.1 Oracle support may recommend to upgrade to Ora10g R2 - just my guess.
Last edited by PAVB; 05-17-2010 at 09:57 AM.
Reason: typo
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.
Now that we can see... we can help better.
Are you running Ora10g 10.1? this matches bug #3467567
Check Metalink... if running on Ora10g 10.1 Oracle support may recommend to upgrade to Ora10g R2 - just my guess.
Yes, it is 10g R1. I will check metalink.
Though, I forgot to thank you. Thanks for giving me this Bug ID.
Last edited by mahajanakhil198; 05-17-2010 at 11:32 AM.
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.