that might be interesting for someone....
NOTES:
1. Take a backup of the Media Manager database.
2. Make sure Media Manager license is present
3. Here, we assume the Media Manager database is good.
4. If needed, restore the Media Manager database after reinstall
5. If the rpms are not in /var/cache/avaya/apps, you can obtain them from the ISO image for the version you are using and transfer them using WINSCP.
6. After reinstall, make sure the MediaManager service is started in WebControl and that it is set to start automatically upon reboot (checkbox)
________________________________________
UNINSTALL MEDIA MANAGER:
[root]# service mediamanager stop
[root]# rpm -e Primary
[root]# rpm -e MediaManager
REINSTALL MEDIA MANAGER:
[root]# cd /var/cache/avaya/apps
[root]# rpm -ivh MediaManager-11.0.4600-18.noarch.rpm
Preparing... ########################################### [100%]
starting pre-install process
Database Already Present
1:MediaManager ########################################### [100%]
starting post install process
Adding user tomcat to group disk
Adding user tomcat to group cdrom
[root]# rpm -ivh Primary-11.0.4600-18.el6.noarch.rpm
Preparing... ########################################### [100%]1

rimary ########################################### [100%]
[root]# service mediamanager start
Potsgres is already running
MediaManager server is starting
[root]# service mediamanager status
Media Manager is running
CPU Usage: 4.8 %, Memory Usage: 577480 KB, Uptime: 00:07
After reinstall, make sure the MediaManager service is started in WebControl and that it is set to start automatically upon reboot (checkbox)