ONoel wrote:Yes, they are -- the tarballs unpack to somewhere around 100GB or so, from memory. You do not require the yum.img and it'd be quite out of date now anyway. You can use the tools within Grid Control to recreate the yum repository, but you will need sufficient space for it. You can check the [Yum Repository Setup|http://www.oracle.com/technology/tech/linux/htdocs/yum-repository-setup.html] page for approximate sizing for each channel.
My question is: Are those sizes normal?
ONoel wrote:The Yum repository stores a mirror of the major channels from the Unbreakable Linux Network. You use it to patch your local Oracle Enterprise Linux servers instead of having them all download RPMs from the Internet.
So you are saying that I don't need the Yum repository provided with the template.
I'm still wondering what is its original use?
Do I absolutely have to recreate one by following the tutorial you linked me or can I import the template and create my OMS and OMR VMs without a Yum repository?You don't need to follow the tutorial -- I linked to it because it has a list of the sizes of each channel. Sorry, I didn't really make that clear, did I? :)
Our VM server doesn't have access to the INTERNET if it needs somehow to get Enterprise Linux RPMs (I assume it's the point of the local Yum repository)
ONoel wrote:I believe so. I haven't actually loaded up the 10.2.0.5 Template yet -- haven't had a chance! Been doing too many physical 10.2.0.5 deployments in the last few weeks.
Thank you also for your advice about the latest template but I don't want the 10.2.0.5 one because it creates one single server with both the OMS and the OMR on the same host. (If I'm right)
I'm going to update my 10.2.0.4 Grid Control to 10.2.0.5 afterwards.You can't update the 10.2.0.4 Template directly to 10.2.0.5 -- there are a few gotchas. Metalink Doc ID 805706.1 has instructions on how to upgrade the 10.2.0.4 template to 10.2.0.5.