Installing the MVMM Server Fix Pack
Before you begin
Make sure that the v.r.sss GA or Server Fix Pack from the last release is installed.
- Review the Fix Pack's notes and instructions. You can extract the README.txt file from the downloaded Fix Pack zip file by running the following command for your service platform:
- Windows
unzip -o FixPackvr.sss_Server.zip FixPackvr.sss_Server\README.txt - Unix
unzip -o FixPackvr.sss_Server.zip FixPackvr.sss_Server/README.txt
- Windows
To install the MVMM Server Fix Pack
(Recommended) Create a directory named FixPacks under your server installation directory (if it does not already exist).
- Download the Fix Pack file (FixPackv.r.sss_Server.zip) to the FixPacks directory.
Unzip the archive.
You should now have a directory named FixPackv.r.sss_Server in the FixPacks directory.
- Stop the services and verify that they have stopped. If you are installing this Fix Pack immediately after installing MVMM, the services have probably not been started.
Run the Fix Pack installation script. It doesn't matter which directory you are in when you run the script. The default action is to install the Fix Pack. To see the help, run the script with the --help option.
If you choose to unpack the FixPack9100.nnn_Server.zip file in a different location, then you must specify the product location when running the installation script.
- Check the output of the script and its log file, correct any issues, and repeat step 6. If you encounter any issues that you cannot resolve, contact BMC Support.
(Windows customers only) Install the required Microsoft runtime libraries by running the following command in the installation directory:
vcredist_x64 /install /quiet /log vcredist_x64_install.log- If you are installing MVMM for the first time, follow the steps in Installing-the-core-components-of-the-product after applying the Fix Pack. Otherwise, continue with the steps that follow. Run the dbschema_sync command to apply DB schema corrections. For information about the command parameters, see find_sql_rollup-and-dbschema_sync-command-parameters.
If you choose to use a user who is a member of the database_login group, follow these steps:
In the installation directory run the command for your service platform:
- UNIX
./qpas -j - Windows
qpas -j
The command continues to run.
- UNIX
- In another command window, access the installation directory and run the command for your service platform:
- UNIX
./dbschema_sync userid -i [-p password | -s] - Windows
dbschema_sync userid -i [-p password | -s]
- UNIX
- Check the output of the command. If any issues exists, correct them. If required, repeat these steps. If you encounter any issues that you cannot resolve, contact BMC Support.
- To stop the qpas command initiated in step a, press Ctrl+C.
If you choose to use your DB credentials, follow these steps:
- In the installation directory, run the command for your service platform:
- UNIX
./dbschema_sync -i -d db_type db_name db_userid [-p db_password | -s] - Windows
dbschema_sync -i -d db_type db_name db_userid [-p db_password | -s]
- UNIX
- Check the output of the command. If any issues exists, correct them. If required, repeat these steps. If you encounter any issues that you cannot resolve, contact BMC Support.
- Start the MVMM services.
- For each client system follow these steps:
- For a client system on which a Java Web Start Monitor Console is being used:
- Flush the Java cache by running the following command: javaws -Xclearcache
- Refresh the Management Console by pointing the web browser to the application service and selecting Management Console from the entry page.
- For a client system on which the stand-alone Monitor Console is being used:
- If you have previously used a Java Web Start Monitor Console but no longer need to, flush the Java cache (which also removes the desktop shortcut) by running the following command: javaws -Xclearcache
- Download and install the updated stand-alone Monitor Console. For more information, see Accessing-the-Monitor-Console.
- For a client system on which a Java Web Start Monitor Console is being used: