I believe you will find that the ARServer will not be able to connect to the DB if you clear the PW from the config file.
If you've removed the Db-password entry from the ar.cfg then, when you restart the server, it will not be able to connect to the database and won't be able to run. Then you will have to either reset the db password to the Remedy default of AR#Admin# or add the Db-password entry back with the previous encrypted value or the current password in plain text and then reset it via the Admin console once the server is up.
In that case, if we clone a database and rename the DB-Server(ar.cfg file) to that new name and without changing the db-password field, will the new set up can connect to new database.
My objective is : If I have to move the database(from SQL A to SQL B) , then what steps I need to take in ar,cfg file ? SQL B will be cloned as SQL A and SQL A do not have default password ?
3 of 3 people found this helpful
If you clone the DB and clone the user, it'll have the same password, so the same value in the ar.cfg will work for the new db, after changing the DB-Name, correct.
My objective is : If I have to move the database(from SQL A to SQL B) , then what steps I need to take in ar,cfg file ? SQL B will be cloned as SQL A and SQL A do not have default password ?---> in AR.Cfg file whatever password is of SQL A put that in plain text, Once you restart the ARS it will be encrypted.
If you want to use default password for Cloned DB B then ..
You/DBA need to fire an alter user command to Change the Password of ARADMIN and then Put default password in ar.cfg.
Answer depends on how you clone the database. If you are taking snapshot of the whole database VM and then use it as a cloned DB server then there should not be any issue.
If you are going to create new DB instance on SQL B and import the DB backup from the SQL A then you need to take care of ARAdmin user. (roles, ownership etc). SQL B server should not have existing ARAdmin user otherwise you may face issue with DB ownership.
Once it is done, you just need to update the 'Db-name' parameter value and restart the ARserver services.