Recreate Remote DB
What are the steps to recreate a remote Aveksa DB?
We would like use the same application configuration, (workflows, connectors, collectors should be kept), but get a new and fresh DB(remove all the content of it)
- Community Thread
- database maintenance
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- Installation & Upgrade
- remote database
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
This really relies on what you have configured in the product because there some dependencies. If you use roles and want to transfer them you need to collect the data (identities / entitlements) before importing the roles.
Exporting the configuration is easy, importing the configuration you need to slice into different steps where you import part of the config first, then run that config before importing the next part of the config.
I would suggest to contact PS to help with the steps that are suitable for your situation
I am basically trying to figure out if I can do something like that-
1. Backup the configuration using one of RSA scripts
2. drop the DB schema
3. Recreate the DB
4. Restore the configuration using RSA script
is there an option?
I would say do it using the below steps.
- Export All MetaData (even if you do not want something, you may need it as a dependency while importing as Edwin mentioned).
- Stop the application.
- Drop AVUSER from the database.
- On the application server side make sure you backup then remove all encryption keys under /home/oracle/security (otherwise you might not be able to login with AveksaAdmin again after recreating the schema).
- Use all queries in the RSA Identity Governance and Lifecycle 7.1 Database Setup and Management Guide to re-create the AVUSER user (make sure you do all the Grants again).
- Start the application, it will detect that the schema is empty and re-create all the default tables ... etc.
- Once the application is up, login as AveksaAdmin/aveksa123.
- Now import whichever metadata you want (Choose the XML file and afterwards you can select which parts of the full XML you want to import).
- If you get errors while importing one part, it should state which dependancy is missing so you can go back and select it as well to import it.
Let me know if you still face any issues at the above steps.
It is more than just looking for errors. Some dependencies don't give you errors it makes the system do things you didn't want it to do yet. If you import your rules and activate them before you've collected your identities you could have a lot of change requests that start to provision access because you have a joiner rule setup. At step 8 is where it gets tricky
This document might help https://community.rsa.com/docs/DOC-86711