VMware Cloud Community
gaganvmware
Enthusiast
Enthusiast
‎05-19-2014 10:26 AM

Vcenter Database user issue RSA_DBA & RSA_user

We installed vcenter 5.1 U2 but created only one RSA_DBA Database ID for everything ( DDL & DML ). We did not create separate RSA_USER for DML as per VMware ( RSA_DBA is used for creating the schema (DDL) and requires DBO permissions. RSA_USER reads and writes data (only DML).  we just created one DB ID RSA_DBA for DDL & DML. Now we are going to use same RSA_DBA DB id for installing Update manager .


1 ) What issues we can face in future if we follow above path .. one  RSA_DBA DB ID for everything?


2 ) Can we use same RSA_DBA DB for everything like we did above ?

3)  we used RSA_DBA for vcenter for complete vcenter installation except update manager . Can we now create & use  separate RSA_USER for update manager or need to use same RSA_DBA that we used for vcenter installation.



4 Replies
rcporto
Leadership
Leadership
‎05-19-2014 10:43 AM

vCenter Update Manager requires a dedicated database, you cannot use same database of Single Sign-On for vCenter Update Manager... anyway you can user the same database user, since you give appropriate permissions on vCenter Update Manager database, but my recomendation is to create another user and not use the same of SSO.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
vThinkBeyondVM
VMware Employee
VMware Employee
‎05-19-2014 11:14 AM

Hi Friend,

Just one suggestion:

If possible, plz upgrade to 5.5, SSO is re-architect-ed and you do not have RSA_DBA/USER hassle any more. SSO has its default capable DB. Just you need to configure VC DB. If you could go for upgrade plz go for latest 5.5U1 + patch.


----------------------------------------------------------------
Thanks & Regards
Vikas, VCP70, MCTS on AD, SCJP6.0, VCF, vSphere with Tanzu specialist.
https://vThinkBeyondVM.com/about
-----------------------------------------------------------------
Disclaimer: Any views or opinions expressed here are strictly my own. I am solely responsible for all content published here. Content published here is not read, reviewed or approved in advance by VMware and does not necessarily represent or reflect the views or opinions of VMware.

gaganvmware
Enthusiast
Enthusiast
‎05-19-2014 12:55 PM

1 ) What issues we can face in future if we follow above path .. one  RSA_DBA DB ID for everything?


2 ) Can we use same RSA_DBA DB for everything like we did above ?

3)  we used RSA_DBA for vcenter for complete vcenter installation except update manager . Can we now create & use  separate RSA_USER for update manager or need to use same RSA_DBA that we used for vcenter installation.

0 Kudos
gaganvmware
Enthusiast
Enthusiast
‎05-19-2014 12:56 PM

1 ) What issues we can face in future if we follow above path .. one  RSA_DBA DB ID for everything?


2 ) Can we use same RSA_DBA DB for everything like we did above ?

3)  we used RSA_DBA for vcenter for complete vcenter installation except update manager . Can we now create & use  separate RSA_USER for update manager or need to use same RSA_DBA that we used for vcenter installation.

0 Kudos