In 19.1.1 under the site pref SMAT tab the database is set to encrypted by default and there’s no option for no encryption. I have not set a key. Is there a default key?
Lynda:
Were the SMAT files created in 19.1? If not you may need to use the hcismatcrypt command to migrate.
Note: You can also validate your password here. Also you can change the password but you must know existing password.
If you cannot figure out what your password is contact Support. They have methods to determine password which I would rather not discuss in this open forum.
I’m on 6.2 going to 2022.09, trying to use the command hcismatcrypt migrate and I’m stuck. If I take 1 smatfile from site A on 6.2 and move it to site B on 2022.02, place it in the exec file on site B, what should my command look like? On site A the encryption key is the site name, on the site B the encryption key will be site name, however site name is diff. I have many files that need to be migrated, so trying to figure out the best way to do this. I need to be able to search these 6.2 smats within 2022.09 for a few months, then I move them off line for also another few months, I sometimes have to pull back from offline to live, etc.
In case anyone needs this. Found that this worked for me.
I did migrate first. I believe you can do this on 6.2 before you move it or on new 2022.
Hcismatcrypt migrate (your smat file name from 6.2) (key which is usually your site on 6.2)
after I ran above, I moved migrated smat file from 6.2 to 2022 directory and changed encryption key to be the new 2022 site
Hcismatcrypt rekey (your new 2022 site name) (6.2 key passowrd which is usualy the 6.2 site name) (smatfile name from 6.2) (new encryption key which would be your 2022 site name) (here you can keep empty if you want your smatfile name to remane the same or provide a new file name I’m assuming, i left mine the same)
.
.