I am running a CA IDM 12.6 sp2 set-up (integrated with CA Siteminder 12.51) on JBoss 5.1 GA AS. I am using MS SQL Server 2008 as the DB. Unfortunately, my SQL server installation went corrupt and after troubleshooting it for a while, it appears that the only way to get it back up is to uninstall and re-install. I have been searching in the CA IDM resources to find any suitable resource to deal with this situation. However, I have not been able to find anything that could help me understand if I could reinstall MS SQL Server without having to re-install CA IDM. I am still a learner when it comes to these technologies. Could anyone please look into this one and at least point me to some resource to help me get started?
Many thanks for reading this post-
I first started using Microsoft SQL Server in 1997 with version 6.5. I have a ton of experience with it, including my own "uh-oh" moments, which means I also have experience in recovering from "uh-oh" moments. I began using CA Identity Manager in 2011 with 12.5 SP9 and now use 12.6 SP2. Your statement that your SQL Server install "went corrupt" means there are some caveats to my response, namely:
Any of these (and probably others that I haven't thought of yet) could significantly change what actions you need to take to get back in operation. I am assuming that your user store is in CA Directory or some other LDAP directory, but even if your user store is part of your SQL Server install that part should not radically change what you need to do. You aren't finding information on this in the CA documentation because this is outside the scope of Identity Manager. In this situation, the Microsoft SQL Server Books Online is your friend. I can also recommend online resources like the SQL Server / Windows Users Group (SSWUG) - http://www.sswug.org/.
I recommend these steps to recover your system:
What Eric said
If this is a non-production system, and you wish to quickly rebuild the tables for IM, you may drop the database login/app ID with the associated tables, then recreate the database login/app ID
IM, when it restarts, will check and rebuild or update the database schema for the six (6) IM databases.
Example for Oracle (used in SQL statement or paste in SQL command line window), to start the solution's DB in a "clean state".
(Below example uses a db login ID idmdba001 that will own a database called "idmdba001"
drop user idmdba001 cascade;
create user idmdba001 identified by Password01;
grant connect, resource to idmdba001;
grant create table, create view, create session, create trigger, create sequence to idmdba001;
grant create tablespace, drop tablespace, manage tablespace, unlimited tablespace to idmdba001;