Thanks for the question, LT.
Asked: April 02, 2020 - 10:43 am UTC
Last updated: April 03, 2020 - 4:56 am UTC
Version: 12.1
Viewed 1000+ times
You Asked
Hi There,
This is regarding the error ora-26002 which we are facing since few days.
We have one table T1 which is having an index on one of the column.
This table T1 is being loaded through informatica using bulk mode option. (Without dropping an index and without making index unusable)
The data was getting loaded properly without any error.
Last week DBA has performed their maintenance activity.
Since then the we are getting this ORA-26002 table has index defined upon it error.
We have raised this concern with DBA but they are saying we did not perform any DDL or any other activities on this T1 table.
My question, do we have any other setting in oracle level to avoid this error.
Because earlier this was working fine, suddenly it is throwing an error.
Thanks,
LT
and Connor said...
You can get this error when *both* of the conditions below are true:
a) you are doing a *direct* (ie, bulk) load
b) you are doing the load in *parallel*
I would suspect that parallel has crept into the mix somehow, either in your bulk loading process or perhaps the table definition and Informatica is detecting that.
If you don't want to rebuild the index, you must either not use bulk or not use parallel.
Hope this helps
Is this answer out of date? If it is, please let us know via a Comment