on 08-18-2017 4:13 PM
Hi All,
We are getting the latest version of datastore from central repository, but some developers are not aware and they run the jobs and after 3 attempts the datastore user gets locked. The IT DBA team then unlocks the datastore user and sends out notification to the developers that they need to get the latest version of the object(datastore).
Is there some better way to make sure that the datastore doesnt get locked frequently
Regards
Arun Sasi
I would hire more intelligent developers. If you don't have the budget, you could consider creating an .atl file with datastore definitions only. Each and every time the datastore credentials change, create a new version of the file and import it into all repositories. This process can be automated using the al_engine command line interface.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.