We use SSIS mainly to extract data from an oracle DB and import into our data warehouse which is in SQL Server. We use an Oracle DB connection in each SSIS package. Recently, we needed to change the password on the account we use to connect to the Oracle DB with. This account is also used in a purchased web application that sits on top of the Oracle DB. If that account gets locked, no one has access to the DB...
hence the problem...
I opened an SSIS package that does a bunch of things and uses the Oracle connection in several spots. It immediately tried to validate those connections and failed each time because the Oracle account password had changed. Unfortunately, this account is configured such that once three unsuccessful login attempts have been made, the account being accessed is locked out - which is exactly what happened - and we started getting helpdesk calls. No one could access anything in this application all of a sudden!
I did some research and could not find a global SSIS setting to turn this off BUT I did find a way to edit each .dtsx using notepad and do a global search and replace on DelayValidation">0< and replace with DelayValidation">1< which changes the "DelayValidation" setting to TRUE instead of the default of FALSE. I then saved the package and it seems to work. THe problem is we have lots of backed up SSIS packages - from each time we have made changes and if I or someone else happens to forget to do this global change before opening it, that Oracle account will get locked out again and the helpdesk will get very busy!!
Does anyone know of a way to set that globally in SSIS somewhere so that you do NOT need to do this global search and replace each time you open an older package that may have the incorrect password?? I worry because my memory sure isn't what it used to be and if one is in a hurry to correct an issue, I know I could easily forget to do this before it's too late!!!
Thanks, Brad
Brad Pears IT Services True North Log Homes Bracebridge, Ont. Canada
