Installing Database in the same LPAR is ok in case of DEV.
But according to my knowledge having Database in different LPAR with dedicated hardware resources enables the performance stability in Production environment with huge number of records in MDM. As Database jobs need to have their own bandwidth without affecting the MDM hardware resource. Also application server i.e. MDM server can be restarted without affecting the Database server. Still it is upto your requirement about having a separate LPAR for database.
Separate LPAR database can be further used for different tools as well in future using the MCOD functionality.
Thanks Shambu again for the reply. My reply in line
But according to my knowledge having Database in different LPAR with dedicated hardware resources enables the performance stability in Production environment with huge number of records in MDM. As Database jobs need to have their own bandwidth without affecting the MDM hardware resource.
-Subin-> Since LPARS pool the resources in a box, why should there be an impact in performance?
Also application server i.e. MDM server can be restarted without affecting the Database server. Still it is upto your requirement about having a separate LPAR for database.
---> How would having both servers - db and MDM in same LPAR should impact each other during restarts.
Separate LPAR database can be further used for different tools as well in future using the MCOD functionality.
--> Not sure on this. by having different LPAR should not make any difference. am i right?
According to you what are the benefits of having LPAR?
-
Subin---> LPARs with shared resource pool has a huge benefit on the cost. I am still trying to dig out more info on LPAR in our current landscape from BASIS team, as i am myself new to the AIX systems.
If you have more info regarding the best practises please let me know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.