Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments. Click here to view the documentation for the current version.

3.3.00.001: Patch 1 for version 3.3.00

This topic contains information about fixes and updates in Patch 1 (product version 3.3.00.001), and provides instructions for downloading and installing the patch.

Tip

For information about issues corrected in this patch, see  Known and corrected issues.

Updates

Patch 1 for MyIT Service Broker 3.3.00 includes various fixes for product issues.

Installing and upgrading

Patch 1 improves the installation experience:

  • Removes the requirement for a large /tmp folder allocation by extracting the installer resource files at the same time as the installation package.
  • Allows for installing the application into precreated database tables.
  • Supports high availability server cluster installation with a new BMC_AR_SERVER_ROLE parameter in the options.txt file.

Password security enhanced

Patch 1 contains a platform update to enforce password security. Passwords must meet the following minimum conditions:

  • 8 to 30 characters in length
  • Upper case letters
  • Lower case letters
  • Numeric characters
  • Special characters from the list ~!@#$%^&*_-

After running the post-installation scripts to create a tenant, the following user is created:

  • Login name: hannah_admin@<domain.com>
  • Password: Passw0rd! (the 0 is a zero)

Service management

Issues when importing an exported zip file have been resolved.

Service bundling

Patch 1 extends the service bundling experience:

  • When creating a bundle, the administrator may toggle optional items on or off.
  • Expanded documentation for creating simple bundles and bundles with custom workflows. See Service bundles.

General product issues

For information about issues that were corrected in this patch, see Known and corrected issues.

 

Downloading the patch

Patch 1 for version 3.3.00 includes the following installers, which you can download from the BMC Electronic Product Distribution (EPD) website:

  • MyIT Service Broker 3.3.00.001 full installer
  • Integration patch for Remedy IT Service Management (Linux)
  • Integration patch for Remedy IT Service Management (Windows)

For full download instructions, see Downloading the installation files.

Installing the patch as a fresh product installation

The download file for patch 1 can be used to install a full application. Follow the instructions in Installing.

Upgrading to the patch

To upgrade from release 3.3.00 or later

You can upgrade to this patch from 3.3.00 or later version, including hotfixes.

Some parameters in the options.txt file have been removed from to streamline the installation and upgrading process.

Do not add missing parameters when you copy the values from the options.txt used in the original installation.

Enter the following values to set upgrade mode:

  • -J BMC_ARSYSTEM_INSTALL_OPTION=Upgrade

  • -J BMC_DATABASE_OPTION=  (leave blank)

To upgrade from release 3.2

You cannot upgrade in place from an earlier release. If you are an existing user of MyIT Service Broker 3.2 or earlier, contact BMC Support to request technical assistance with migrating your existing data into the latest release.

For more information, see Upgrading.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Adrian Grancea

    Hello,

    During installation of fresh 3.3 patch 1 on oracle db the following error is received:

    (Apr 06 2017 10:50:03.866 AM +0200),SEVERE,com.bmc.install.product.arsuitekit.platforms.arsystemservers.arserver.ARServerOracleManageDatabaseTask,
    LOG EVENT {Description=[[SQLERROR] [DESCRIPTION] Failed to execute SQL statement],Detail=[[SQLERRORCODE]=1031 [SQLMESSAGE]=ORA-01031: insufficient privileges
    [SQLSTATEMENT]=GRANT ALTER SESSION, CREATE CLUSTER, CREATE DATABASE LINK, CREATE SEQUENCE, CREATE SESSION, CREATE SYNONYM, CREATE TABLE, CREATE VIEW, CREATE PROCEDURE, CREATE TRIGGER, QUERY REWRITE TO ARADMINROLE]}
    (Apr 06 2017 10:50:03.867 AM +0200),SEVERE,com.bmc.install.product.arsuitekit.platforms.arsystemservers.arserver.ARServerOracleManageDatabaseTask,
    THROWABLE EVENT {Description=[Failed to execute processDBVendorSqlFile ]},
    Throwable=[java.sql.SQLException: ORA-01031: insufficient privileges
    oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:133)
    oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:115)
    oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:221)
    oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:467)
    oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:417)
    oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1084)
    oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:187)
    oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1215)
    oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1515)
    oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:2283)
    oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:2226)
    oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:807)
    com.bmc.install.utility.jdbc.impl.AbstractDatabaseHelperImpl.executeStatement(AbstractDatabaseHelperImpl.java:526)
    com.bmc.install.utility.jdbc.DatabaseHelper.executeStatement(DatabaseHelper.java:651)
    com.bmc.install.utility.jdbc.SQLScriptRunner.executeSQL(SQLScriptRunner.java:339)
    com.bmc.install.utility.jdbc.SQLScriptRunner.executeSQL(SQLScriptRunner.java:278)
    com.bmc.install.product.arsuitekit.platforms.arsystemservers.arserver.ARServerManageDatabaseBusinessTask.processDBVendorSqlFile(ARServerManageDatabaseBusinessTask.java:1217)
    com.bmc.install.product.arsuitekit.platforms.arsystemservers.arserver.ARServerManageDatabaseBusinessTask.execute(ARServerManageDatabaseBusinessTask.java:126)
    com.bmc.install.task.InstallationTask.run(InstallationTask.java:93)
    java.lang.Thread.run(Thread.java:745)]
    (Apr 06 2017 10:50:03.872 AM +0200),SEVERE,com.bmc.install.task.InstallationStateHelper,
    LOG EVENT {Description=[AR System Server failed],Detail=[featureARServer]}
    (Apr 06 2017 10:50:03.872 AM +0200),CONFIG,com.bmc.install.task.InstallationPropertiesHelper,
    LOG EVENT {Description=[SET PROPERTY FAILED_INSTALL_FEATURES],Detail=[featureARServer]}

     

    In this case user with sys db has been used, after manually run the grant sql with the same db user configured in option.txt no issues encountered during install.

    May 05, 2017 06:55
  2. Tony Chung

    Hi Adrian,

    This sounds very much like an Oracle configuration issue. This is one of the reasons why, for the 3.3 release, the installation process has been changed to recommend creating the database tablespaces in advance.

    Also, the options.txt file is significantly different from 3.2 and slightly modified from 3.3.00. You can usually use the same values, but you must use as a base the options.txt file that is packaged with the installer.

    -Tony

    May 05, 2017 12:35
  3. Adrian Grancea

    Hi Tony,

    I have used the option.txt file that is with the installer. Also tried one time on a different instance with created application tablespace in advanced and also got failed installation. The installer failed because it tried to create a new db tablespace with the same name. I think create table space section should be in sync with installation worksheet.

    For example if i use in option.txt the values used during create tablespace in advance the installer will fail and if i use different values there is no point in creating tablespace in advance (smile).

    I think it should be better to have explanations of options.txt in cases when allow installer to create app_db user/tablespaces and in case when this are created in advance.

    Thanks,

    Adrian

     

    May 05, 2017 01:02
  4. Tony Chung
    May 05, 2017 02:17