8.9.02: Service Pack 2 for version 8.9.00

Option to create a separate disk group for GIMR data (Applies to Oracle 12.2.0.1 only)

Starting with version 8.9.02, you can create a separate disk group for the Grid Infrastructure Management Repository (GIMR) data to segregate it from the Cluster Ready Services (CRS) data. For more information, see Creating-an-Oracle-cluster.

In addition to GUI, while creating RAC databases through the command line, you can use a template that includes content to create a separate GIMR disk group. For more information, see Creating a separate disk group for GIMR data.

Option to retain or delete the Oracle Home directory

With this release, you have an option to retain or delete the Oracle Home directory when deleting its last associated Oracle database by using the delete_homes_prompt parameter in the d2500_config file. For more information, see the following topics:

• Removing-a-single-instance-Oracle-database-on-Linux-and-UNIX
• Removing-a-single-instance-Oracle-database-on-Windows
• Removing-an-Oracle-RAC-database

Defining custom fields for database options

Starting with this release, you can define custom fields for the database options present on the Database Options page while adding a database on Windows and Linux. The value of that database option is derived from the value of corresponding custom field specified on the Custom Fields page. For more information about defining custom fields, see To add a custom field for a database option to a template.

Running actions having scope as Oracle PDB through cmdutils

Starting with version 8.9.02, cmdutils enables you to run an action having scope as Oracle Pluggable Database (PDB). 

Accessing BDA GUI by using non-default ports

Starting with version 8.9.02, you can access the BDA GUI by using a non-default port in the URL. For more information, see Configuring-non-default-ports-for-accessing-GUI.

Access to BDA GUI not allowed using logical names

Starting with version 8.9.02, you cannot access the BDA GUI by using logical name as the host name. To access the server, it is mandatory to provide host name or fully qualified domain name. If you want to still want to allow access by a logical name, set the value of the is_http_referrer_check_disabled parameter to true in the /app/clarity/dmanager/etc/d2500_config file. Keep in mind that allowing the logical name exposes BDA to security threats.

Support for additional operating systems for Oracle version 12.2.0.1

Oracle 12.2.0.1 Single Instance is now supported on the following operating systems:

• Oracle Solaris 10 and Solaris 11
• Windows Server 2012 R2

For complete database support, see Databases-supported.

Discontinued support for operating systems and databases

Starting from version, BDA discontinues support for the following operating systems:

• Red Hat Enterprise Linux 4
• IBM AIX 6.1
• Oracle Linux 5
• SuSE Linux Enterprise Server 10
• Oracle Solaris 9

For complete operating system support, see OS-requirements.

Starting from version, BDA discontinues support for the following databases:

• MySQL 5.1.59
• Oracle 11g R1
• SAP Adaptive Server Enterprise (ASE) Dataserver versions 12.5.4 and 15.0.2

For complete database support, see Databases-supported.

Pre-staging of patches

Starting from version 8.9.02, you can divide the patch application process in the following phases to optimize the patch application process: 

• Pre-stage the patch: This step copies the patch media to nodes and extracts it. For information about the pre-staging process, see Managing-patching. 
• Apply the patch: Compares if the patch media is already present on the node. If the media exists, it is compared with the patch media to be copied using checksum. If the checksum matches, then the patch is applied to the node. If the media is not present or checksum does not match, the media is first copied and then patch is applied to the node. For more information see, Patching-a-database.

You can pre-stage a patch outside the patch window, which typically has bandwidth and time constraints. After pre-staging, you can apply the patch in patch window. For pre-staging instructions, see Pre-staging-a-patch-package.

Viewing the verified jobs in the job list

Now on the Jobs page, you can see the jobs that ran only till the pre-verification phase. Use the Verified option in the Status filter to view such jobs. For more information, see To monitor a job or view the details of a completed job.

Overwriting templates and actions forcefully while importing

While importing an action or a template through the following scripts, you can overwrite it forcefully by using the force option if an action or a template with the same name exists in the BMC Database Automation Manager:

• import_action_archive.pl: Imports actions. 
• import_template_archive.pl: Imports templates.
• import_all.sh: Imports actions, templates, and patches.

Note: A patch is always overwritten if a patch with the same name exists in the Manager.For more information about these scripts and the force option, see the command line help.

Support for Perl version 5.24.1

In version 8.9.02, the Perl library has been upgraded to version 5.24.1. As a result, version 8.9.02 of the Manager is not compatible with earlier version of the agent. The Manager version 8.9.02 is compatible with the agent version 8.9.02 only. 

BMC Cloud Lifecycle Management

4.6.05

BMC Atrium Orchestrator Platform

7.8.00

BMC Atrium Orchestrator Content

20.16.03

BMC Decision Support - Database Automation

8.9.02

BMC Remedy ITSM Suite 

9.0