I think what you're trying to say is that operator logs (stored in some SNP tables) are getting purged every 7 days. Correct me if I'm wrong. To retain logs for a longer time, open the generated (or predefined) load plan and set "Keep Log History (Days)" to a higher number. Note that since you're retaining logs for a…

Please check the operator log and confirm if its the "Perform Update" step itself which is taking 15-30 mins. I ask this because there is a possibility of other table maintenance tasks which could be dropping / re-building indexes and could be adding to task's overall execution time.

Hi, How are you running this after making the change in model. Are you running the task through LP or standalone scenario. I ask this because if run through LP, there is a step in Initialize Batch Load phase which refreshes a metadata table that has all index definitions. It is from there that I believe it picks up these…

Hi Amit, Navigate to the datastore in ODI Designer -> Models accordion. Locate the target table, expand constraints -> find WC_RECEIPT_F_U1. Open it and go to flexfields tab. Flexfield named OBI Bitmap Index will probably be Y. If you change this to N, it will not use BITMAP clause when creating index.

You don't need to generate LP again. However, it will not work if you restart the same failed session again either. During next LP when new session for this task gets created, it should work fine.

It is picking the path from Physical schema mapped to the logical schema DW_BIAPPS11G_LOG_FILES. Physical schema will most likely have value like this - C:\\oracle\\Middleware\\instances\\instance1\biapps/log Change this log location path in ODI topology to use forward slash /biapps instead of back slash \biapps. Issue…