Oracle® Advanced Support Gateway: User's Guide
Oracle® Advanced Support Gateway: User's Guide
[1]
User’s Guide
F58615-01
December 2024
Oracle Advanced Support Gateway User’s Guide
F58615-01
This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find
any errors, please report them to us in writing.
If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related
documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any
programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle
computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
computer software," "commercial computer software documentation," or "limited rights data" pursuant to the
applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use,
reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation
of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or
activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii)
other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such
services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its
affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle®, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners. Intel and Intel Inside are trademarks or registered trademarks of Intel
Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC
International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an
applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss,
costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth
in an applicable agreement between you and Oracle.
Contents
Preface ................................................................................................................................................................. 5
Audience......................................................................................................................................................... 5
Related Documentation .................................................................................................................................. 5
Getting Help ................................................................................................................................................... 6
Documentation Accessibility ......................................................................................................................... 6
2 Using Dashboards
About Dashboards...................................................................................................................................... 2-1
Accessing the Dashboard ........................................................................................................................... 2-2
About Widgets ............................................................................................................................................ 2-2
Adding a Dashboard .................................................................................................................................. 2-3
Adding a Widget ......................................................................................................................................... 2-4
Managing Widgets...................................................................................................................................... 2-5
Removing a Widget from a Dashboard................................................................................................. 2-5
Configuring a Widget............................................................................................................................ 2-5
Reviewing Information about a Widget................................................................................................ 2-6
3 Managing Users
About User Management........................................................................................................................... 3-1
Managing Users .......................................................................................................................................... 3-1
Viewing Users....................................................................................................................................... 3-1
Adding Users......................................................................................................................................... 3-2
Activating Users.................................................................................................................................... 3-3
Updating Users...................................................................................................................................... 3-4
Deleting Users....................................................................................................................................... 3-4
Resetting User Passwords ..................................................................................................................... 3-5
1
4 Managing Credentials and Passwords
About Credential Management................................................................................................................. 4-1
About Oracle Platinum Services Customer Requirements ................................................................... 4-1
Displaying Credentials.......................................................................................................................... 4-2
Using Credential Management.............................................................................................................. 4-2
About Credentials....................................................................................................................................... 4-2
About Required Credentials.................................................................................................................. 4-2
About Recommended Credentials ........................................................................................................ 4-3
About Additional Credentials ............................................................................................................... 4-4
About Selected Targets and their Associated Credentials .................................................................... 4-4
Viewing Credentials ................................................................................................................................... 4-4
Viewing Credentials for Target Children.............................................................................................. 4-6
Editing Credentials..................................................................................................................................... 4-6
Editing Credentials................................................................................................................................ 4-6
Editing Credentials in Bulk................................................................................................................... 4-7
Creating Credentials .................................................................................................................................. 4-8
About Credential Reports.......................................................................................................................... 4-9
Viewing Target Credentials .................................................................................................................. 4-9
6 Activating Services
About Activating Services.......................................................................................................................... 6-1
Selecting a Service for Activation.............................................................................................................. 6-2
Viewing Discovered Databases.................................................................................................................. 6-8
Deactivating Services ................................................................................................................................. 6-8
7 Validating Connections
About Gateway Connectivity .................................................................................................................... 7-1
About System Tests..................................................................................................................................... 7-2
About Internal System Tests ................................................................................................................. 7-2
About External System Tests ................................................................................................................ 7-2
2
About ILOM Tests ................................................................................................................................ 7-2
Viewing System Test Status ....................................................................................................................... 7-2
Verifying the External Connection .......................................................................................................... 7-3
Specifying a HTTP Proxy ..................................................................................................................... 7-4
Verifying an Internal Connection ............................................................................................................ 7-5
Verifying an ILOM Connection ............................................................................................................... 7-8
Configuring New System Test Targets...................................................................................................... 7-9
3
12 Setting the HTTP Proxy Server
About the HTTP Proxy Server............................................................................................................... 12-1
Specifying the HTTP Proxy Server Setting........................................................................................... 12-1
Specifying a HTTP Proxy During Connectivity Tests....................................................................... 12-2
4
Preface
Audience
This guide is intended for Oracle Advanced Support Gateway customer users.
Oracle Advanced Support Gateway is a multiservice platform that is deployed in customer
networks to simplify network connectivity and access for Oracle in the delivery of Oracle
services including Platinum Services, ACS Services, Advanced Monitoring and Resolution, and
Premier Support.
The Gateway platform is a software appliance, based on the Oracle Linux operating system and
hosts a full stack of Oracle software, including Automated Service Request (ASR), Oracle
Enterprise Manager, Oracle Configuration Manager (OCM), patch management (such as YUM
services), and a suite of Java applications. Together, these applications aggregate and route
telemetry messages from the customer environment to the Oracle Support Services
infrastructure.
The Gateway provides remote access for Oracle engineers to access the customer network (with
customer permission) and to carry out approved actions on the customer's monitored systems.
In short, the Gateway allows simplification of the network requirements and a single point of
access for the provision and delivery of Oracle connected services.
The Gateway is typically located in the customer data center DMZ behind a firewall, with
network access to the infrastructure it is monitoring. It is not directly exposed to the Internet,
but it should be continuously accessible from Oracle Cloud Operations infrastructure, using a
TLS/VPN tunnel.
Related Documentation
For more information, see the following documents in the Oracle Advanced Support Gateway
documentation set:
? Oracle Advanced Support Gateway Installation Guide: Describes how to build
the Gateway both in the Cloud (using Oracle Cloud Infrastructure, or OCI) and in an
on-premises configuration. The document also provides requirements for installing the
5
Gateway, installation procedures, and post-installation tasks. Also provides information on
activating the Gateway on which various services are installed and supported.
? Oracle Advanced Support Gateway Security Guide: Describes security
information and instructions for the Gateway. Includes the requirements for deploying the
Gateway into the customer environment to support the delivery of Oracle Connected
Services. The Gateway is an important part of the Oracle delivery architecture for Oracle
Connected Services and its placement must be carefully considered in order for Oracle to
deliver Oracle Connected Services. This document outlines network configuration options
when integrating the Gateway device within the customer environment.
Getting Help
If you require assistance using the Gateway, please contact the Oracle Support Services contact
with whom you have been engaged for review.
Alternatively, you can use your CSI (Customer Support Identifier) to access My Oracle Support
at:
https://support.oracle.com/.
Thank you for choosing Oracle Advanced Support Gateway.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility
Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
6
1
1 About the Oracle Advanced Support Gateway
User Interface
This chapter offers an introduction to the Oracle Advanced Support Gateway user interface and
its principal features.
It includes the following topics:
? Logging onto the Gateway
? About the Gateway User Interface
Refer to the following sections that describe the individual elements of the Gateway user
interface:
? About the Navigation Menu
? About the My Services Menu
? About the Dashboard Menu
? About the Gateway Menu
? About the Admin Menu
? Viewing Legal and Copyright Information
Related Information
Selecting a Service
Selecting a Service Feature
Activating Services
Selecting a Service
To select a supported service:
1. Log on to the portal as outlined in "Logging onto the Gateway."
2. From the My Services menu, select All Services.
The My Services page appears. It displays a list of services tailored to the customer
contract.
Note: A number of images in this and other chapters may not be applicable to
particular customers who do not have features or functionality associated with
particular services.
3. From the My Services page, select the required service by clicking it.
Related Information
Using Dashboards
For example, in the table of Gateway users, In the Search field on the menu bar, enter the
contact’s e-mail address, phone number, type, notification only, user status, applications, or
first or last name. You can also use the wildcard symbol. Then click the Search icon. The
Users page is refreshed, displaying the contact(s) matching the full or partial entry.
? Re-order - To reorder a list, use the arrows to alter the display.
? Customize the page - In the top right of the page or table, use the menu items under the
wheel icon to perform the following actions:
? Click Column Visibility to deselect column names.
? Click Print to print the contents of the page.
? Click Excel to save the contents of the page in Microsoft Excel format.
? Click CSV to save the contents of the page in comma-separated variable format.
Among the tasks that the Gateway menu enables you to perform are:
? Validating Connections
? Managing Server and ILOM Certificates
? Managing Credentials and Passwords
Among the tasks that the Admin menu enables you to perform are:
? Proxy Setting: Setting the HTTP Proxy Server
This chapter provides information about using Oracle Advanced Support Gateway to configure
and use dashboards.
This chapter consists of the following sections:
? About Dashboards
? Accessing the Dashboard
? About Widgets
? Adding a Dashboard
? Adding a Widget
? Managing Widgets
About Dashboards
An Oracle Advanced Support Gateway dashboard is a customizable service dashboard
framework that provides an overview of your services and enables you to focus on selected
items of interest. The dashboard is made up of a series of data windows called widgets as
shown in Figure 2–1.
Figure 2–1, "Viewing the Dashboard" shows a customer service dashboard that displays the
status and statistics relating to their systems, hosts, or databases, as well as information about
security compliance. Each widget provides one-click access to additional, detailed information
about the data presented in the widget.
The dashboard provides a layout to display multiple widgets on one page. You can create
multiple (up to five) dashboard pages, with each page made up of multiple widgets. You can
use the dashboard to add, remove, or rename pages or widgets.
Related Information
Accessing the Dashboard
About Widgets
Related Information
About Dashboards
Adding a Dashboard
About Widgets
A widget is a data window that provides information about a service, such as database version
or status, patch compliance, and so on.
The widgets listed as available are based on the user's role and the services available on the
gateway. For example, the Patch Compliance widget is available only if Platinum Services are
installed on the gateway.
You can add and remove widgets from a dashboard, reposition widgets on the screen, and drill
down into a widget to view the underlying information.
The Gateway widgets include:
? Database Status: Displays the status counts of the databases activated for a specific
service.
? Database Versions: Displays the counts of the databases activated for a specific service by
their installed database version.
? Patch Compliance: Displays the compliance summary for all Oracle Engineered Systems
activated under Platinum Services. See Chapter 9, "Managing Databases and Database
Patches."
? Patch Requests Displays scheduled patch requests details. See Chapter 9, "Managing
Databases and Database Patches."
Related Information
Adding a Widget
Adding a Dashboard
To use Oracle Advanced Support Gateway to add a dashboard:
1. Log on to the Oracle Advanced Support Gateway portal.
2. From the top level menu, select Dashboard.
3. Click the + icon to add a dashboard page.
4. Provide a meaningful name for the dashboard page, and click Create.
The dashboard page appears.
You can create up to a total of five dashboards per Gateway instance.
Related Information
Accessing the Dashboard
Adding a Widget
To use Oracle Advanced Support Gateway to add a widget:
1. Click Add Widget as shown in Figure 2–6.
2. From the available widgets, click Add to select the required widget. See Figure 2–7.
Related Information
Accessing the Dashboard
Managing Widgets
Each widget provides one-click access to additional, detailed information about the data
presented in the widget.
You can perform a number of actions on a widget.
To perform an action on a widget:
1. Click the icon associated with a widget as shown in Figure 2–8 to display the actions
available on the widget.
Related Information
Removing a Widget from a Dashboard
Configuring a Widget
Reviewing Information about a Widget
Configuring a Widget
To configure a widget:
1. Click the icon shown in Figure 2–8 to display the actions available on the widget.
2. Click Configure.
3. Perform the configuration required on the widget.
Note: Only certain widgets can be configured in this way.
Related Information
Adding a Widget
This chapter describes how to manage accounts for customer users and customer administrators
in Oracle Advanced Support Gateway.
It includes the following topics:
? About User Management
? Managing Users
Managing Users
The Gateway enables customer administrators (CUAs) to add, update, or delete customer users
for their organizations. This section contains the following topics:
? Viewing Users
? Adding Users
? Activating Users
? Updating Users
? Deleting Users
? Resetting User Passwords
Viewing Users
The Users page enables you to view and maintain all of your organization’s Gateway users and
contacts on one page, where:
Prerequisites
? A user has an account in the Gateway, enabling the user to access the Gateway.
? A contact is an individual who is involved with Oracle connected services and packages
and whose details have been registered in the Gateway. Contacts may or may not have
access to the Gateway.
To view Gateway users:
1. Log in to the Gateway.
The Gateway Home page appears.
2. From the Admin menu, click User List.
The Users page appears, displaying the following information for all entries:
Field Description
Name The user name for this Gateway account.
Status Indicates whether the user status is:
? Enabled, where a Gateway user account has been added and activated. Users with
this user status can log in to the Gateway.
? Inactive, where a Gateway user account has been deactivated due to inactivity.
Users with this user status cannot log in to the Gateway.
Email The user’s e-mail address, as registered in the Gateway.
User Type Indicates whether the user type is:
? Customer, where a Gateway user is a customer.
? Oracle, where a Gateway user is a provider. Oracle users are notified as certain
events relating to the user occur.
Note: Oracle users are not visible to customer users.
Role The user’s role; for example, Generic Customer or Generic Customer Admin.
Actions>Invite Invite an individual to become a Gateway user.
Note: This action is not available to Generic Customer users.
Actions>Edit Edit the details of a Gateway user.
Actions>Remove Remove the user from the Gateway.
Note: This action is not available to Generic Customer users.
Adding Users
This section describes how you can add a new user to the Gateway.
Prerequisites
? The individual is not already a contact for this customer organization in the Gateway.
? You are a customer administrator for your organization, that is, you have been assigned the
Generic Customer Admin role.
To add a new user of the Gateway:
1. Log in to the Gateway.
The Gateway Home page appears.
2. From the Admin menu, click User List.
The Users page appears.
3. Click Create User.
Field Description
User ID The user identifier associated with this user.
Note: Only letters, numbers, and underscores are allowed. System users are reserved.
First Name The first name of the user.
Last Name The last name of the user.
E-mail address The user’s e-mail address.
Note: Ensure that the email address is valid and that the user can access it to receive an
activation email.
Phone (Optional) The user’s telephone number, including country and area codes.
Status The status of the user, whether Active or Inactive.
An Inactive user is one that has been created, but is not yet activated and hence cannot
log on to the Gateway. To activate a user, see "Activating Users".
Date format The format to be used when displaying dates for this user.
Time format The format to be used when displaying times for this user.
User Type Type of user:
? Customer - creates a customer user.
Note: Oracle users may be created on Oracle Advanced Support Platform, but are
not visible to customer users.
User Role Select the type of role (or roles) associated with the user.
? Generic Customer User: This is a business role.
A user with the Customer role can log in to the Gateway. Users with this role can
also review connectivity checks (that is, the Netcheck functionality.)
See Chapter 7, "Validating Connections."
? Generic Customer Admin This is an administrative role. A user with the
Customer Administrator role can manage customer users and perform all
customer-facing functions such as password management.
This is the default role.
Note: Selecting the Generic Customer Admin role ensures that the new user can
create other users.
Activating Users
This section describes how you can activate a Gateway user.
Prerequisites
? The user is successfully created on the Gateway.
Updating Users
This section describes how you can update a Gateway user.
This function may be required, for example, after creating a new user, where the user cannot
log in to the Gateway, and is shown as an Inactive user on the Maintain Users page (as denoted
by a grayed out symbol.) An inactive user is one that is created, but is not yet activated and
hence can't log on to the Gateway.
Prerequisites
? The individual is a contact or user for this customer organization in the Gateway.
? You are a customer administrator for this customer organization in the Gateway.
Customers require the customer admin role.
To update a Gateway user:
1. Log in to the Gateway.
The Gateway Home page appears.
2. From the Admin menu, click User List.
The Users page appears.
3. From the list, click the name of the user that you want to update, or select the Edit icon
associated with the user in the Actions column.
The Users form appears for the individual user.
4. Edit the information in the table in "Adding Users":
5. Click Save to update the user (or click Cancel to quit without saving.)
The Users page appears, showing information about the user in the user table.
In the case of an inactive user, after revising the user's data (for example, email address),
click Send Invite to resend the activation email.
Deleting Users
This section describes how you can delete a Gateway user.
Prerequisites
? The individual is a contact or user for this customer organization in the Gateway.
? You are a customer administrator for this customer organization in the Gateway.
To delete a Gateway user:
1. Log in to the Gateway.
The Gateway Home page appears.
2. From the Admin menu, click User List.
The Users page appears.
3. Select the Delete icon associated with the user in the Actions column.
When prompted, click Yes to confirm that you want to delete this user.
The Users page appears, with a message that the user has been deleted.
Prerequisites
? The individual is a contact or user for this customer organization in the Gateway.
? You are a customer administrator for this customer organization in the Gateway.
To update the password of a Gateway user:
1. Log in to the Gateway.
The Gateway Home page appears.
2. From the Admin menu, click User List.
The Users page appears.
3. From the list, click the name of the user that you want to update, or select the Edit icon
associated with the user in the Actions column.
The Users form appears for the individual user.
4. Click Reset Password to send the user a form for resetting the password.
5. A confirmation message appears. Click Yes to confirm or click No to cancel.
This chapter describes how to view and manage customer credentials for hosts or targets
associated to at least one service running on the Gateway production system.
It includes the following topics:
? About Credential Management
? About Credentials
? Viewing Credentials
? Editing Credentials
? Creating Credentials
? About Credential Reports
Platinum Configuration during delivery of Oracle Platinum Services, as described in the Oracle
Platinum Services Technical Support Policy. The Appendix provides a table describing the user
account access required by Oracle during the implementation and ongoing delivery of Oracle
Platinum Services.
Displaying Credentials
Credential sets are displayed by target type. The Password Management page lists the managed
accounts used by your Oracle Advanced Support Gateway implementation team for which
passwords are currently stored in Oracle Password Vault.
About Credentials
There are different types of credential defined in the Gateway:
? Required credentials. See "About Required Credentials."
? Recommended credentials. See "About Recommended Credentials."
? Additional credentials. See "About Additional Credentials."
You can directly configure credentials using the Credential Management page. These
credentials are then updated in Oracle Password Vault as well as in OEM.
These credentials can be viewed and edited singly, or in bulk.
So, for example, in Figure 4–1, for this particular target, required credentials are required for
default access by a number of Oracle Support Services.
Related Information
Activating Services
About Recommended Credentials
About Selected Targets and their Associated Credentials
Related Information
About Required Credentials
Related Information
About Recommended Credentials
About Required Credentials
About Selected Targets and their Associated Credentials
Viewing Credentials
To view credentials by target type:
1. Log on to the portal.
See "Logging onto the Gateway."
The Oracle Advanced Support Gateway home page appears.
Related Information
Viewing Credentials for Target Children
Editing Credentials
You can edit credentials singly, or in bulk. Refer to the following sections:
? "Editing Credentials"
? "Editing Credentials in Bulk"
Editing Credentials
To edit a credential:
1. Log in to Oracle Advanced Support Gateway.
The Oracle Advanced Support Gateway Home page appears.
2. From the Gateway menu, select Password Management.
The Password Management page appears.
3. Drill down to the level of the target, or child of the target, as required.
Select the required credential.
Click Edit.
The credential page appears. See Figure 4–5.
4. For the Required Credential, provide a password for username orarom (which has sudo
privileges) or root. Ensure you provide passwords for all compute nodes.
Edit the following fields as required:
? Username: Enter the username of the target.
? Password: Enter the password associated with the target username.
? Confirm Password: Re-enter the password associated with the target username.
? (Optional) Validate on Save: Select the Yes check box to validate the password prior
to saving.
Note: This field is not present for monitoring access, ILOM access, or ASM access.
? (Recommended Credentials Only)
Role: Select the role associated with the user.
The options include Normal (the default) or SUDO. For other target types, the roles
may vary; for example: for ASM access, the options are SYSASM or SYSDBA.
? (Recommended Credentials Only)
Run as: Select the user to run as.
5. For the Recommended Credential, perform the same action: complete the credential either
with orarom (which has sudo privileges) or the user root.
6. Click Save (or click Validate and Save).
Once the passwords are updated and validated, each nodes displays a green check mark.
Creating Credentials
The Create New Credential page enables you to create an additional credential on a target.
To create a credential:
1. Log in to Oracle Advanced Support Gateway.
The Oracle Advanced Support Gateway Home page appears.
2. From the Gateway menu, select Password Management.
The Password Management page appears.
3. Drill down to the level of the target, or child of the target, as required.
In the Additional Credentials section, click Create New.
The Create New Credential page appears. See Figure 4–7.
This chapter provides information about using Oracle Advanced Support Gateway to manage
systems and hosts as well as requesting activations of new systems and the addition of new
hosts.
This chapter consists of the following sections:
? About Managing Systems and Hosts
? Adding a New System
? About Adding a New Engineered System
? Viewing Target Configurations
? Managing System Passwords
? Deactivating Services
Related Information
About Patching Requests
Managing Databases and Database Patches
This wizard will help you install monitoring agents on standalone systems or create a
request for the monitoring of an Engineered System. As part of the wizard workflow you
will be requested to provide the following:
? Privileged host credentials;
? For standalone systems: IP addresses and their fully qualified domain names (FQDN);
? For Engineered Systems: The Engineered System's schematic file, serial number,
CSI/MOS ID (and in the case of users of the Platinum Service, the associated Platinum
implementation service request (PISR) number);
? Additional custom install settings.
The wizard performs the following checks before taking any actions:
? Validate the network connectivity between the Gateway and the hosts;
? Test credentials; the self-service activation process enables users to enter credentials
for individual nodes;
? Check each host meets minimum prerequisites for agent installation.
Service activation on multiple targets continues after a single target failure. During
service activation, all targets are shown, together with any reason why a target is not
eligible for activation.
Before you get started:
? Please review the Oracle Advanced Support Gateway Security Guide
As part of the wizard workflow, users are requested to provide IP address details and
passwords for the required Engineered System. Checks are then performed to validate the
network connectivity and passwords before a Service Request (SR) is created and
submitted for an Oracle engineer to complete the remaining tasks.
4. (Optional) Select the Don’t show message again check box so that the Welcome Message
page is not displayed in future as part of the Add Agent workflow.
5. Click Get Started.
The Add System page appears.
12. Review the connectivity checks (Netcheck) back to the Gateway for all of the targets
uploaded through the schematic file. Expand the type sections, for example, Exadata
Storage Servers, to review the details.
Note: If any mandatory test fails, it is not possible to proceed to the next stage of adding
the Engineered System.
A typical message advises that “Mandatory tests failed and must be resolved to continue.
Please check Oracle Advanced Support Gateway Security Guide”.
Note: If any non-mandatory test fails, you should review the warning message and take
appropriate action before proceeding to the next stage of adding the Engineered System.
a. (Optional) Click Back to change system details.
b. (Optional) Click Retest to run the connectivity tests again.
c. Click Next.
The Set Credentials page appears.
a. Click Start to begin the validation process for the target group, that is, database
servers or compute nodes.
b. (Optional) In the Credentials field, select the Same for All check box to apply the
credentials to all servers of the same type (database servers).
c. In the Host Username field, enter the name of the system.
d. In the Host Password field, enter the password associated with the system.
(Optional) Toggle the eye icon to view or hide the details.
e. In the Priv Mode field, select the mode to be used to gain the required root level
privilege on the system. The options are sudo, su, and pfexec.
f. In the Root Password field, enter the root password associated with the system.
(Optional) Toggle the eye icon to view or hide the details.
g. In the ILOM Username field, enter the ILOM username.
h. In the ILOM Password field, enter the password associated with the ILOM.
(Optional) Toggle the eye icon to view or hide the details.
In the Monitoring Credentials credentials section, you need to provide details for
monitoring that are saved for future usage but which are not validated.
Complete the following fields to configure monitoring credentials for the Physical
Compute Nodes:
a. In the Database field, enter the database name.
b. In the DBSNMP Password field, enter the SNMP password associated with the
database.
(Optional) Toggle the eye icon to view or hide the details.
c. In the ASM Cluster Name field, enter the name of the Automatic Storage
Management (ASM) Cluster.
d. In the ASMSNMP Password field, enter the SNMP password associated with the
Automatic Storage Management (ASM) Cluster.
(Optional) Toggle the eye icon to view or hide the details.
e. Click Next.
A warning popup appears: supplying incorrect passwords may result in being locked
out of your account.
g. Click Continue.
The validation check is run and a message appears, stating that the credentials have
been validated.
h. Click Next.
The Check Network Connectivity page appears.
All network connections (that is, to or from the Gateway to the device) are checked.
If a connection is not made, then a status of Failed is displayed as shown for the
Physical Compute Nodes in Figure 5–8.
Expand the Physical Compute Nodes to view the node, in this case,
aeldb3db04.acs.oracle.com, that is failing the connectivity check. See Figure 5–9.
Reconfigure the failing connection and validate it before continuing. When all
connectivity passes, continue to the next step.
i. Click Next.
The Compliance Check page appears.
b. Click Next.
A warning message appears stating that the compliance check is successful, and
asking whether you would like to proceed.
c. Click Yes.
The Submit Provisioning Request to Oracle page appears.
This page states that the system precheck has been completed (that is, all system
information has been validated.)
To proceed with system installation, submit the provisioning request for the
Engineered System to Oracle.
15. Click Submit Details to Oracle.
A provisioning request is submitted to Oracle. You will be notified when it is completed.
The System Install Successful page appears.
16. A service activation request summary is sent to the customer contact by email. It states:
Dear Customer,
We have received your request and will start the planning process for
<Service Name> Activation on your Exadata sytem <Exa_system_name>.
Below is a summary of your Service Activation request.
See the following table which provides a sample summary response from Oracle.
Note: Certain values in the table have been obfuscated for security reasons.
17. At this point, you can perform one of the following actions:
? Select Continue to Add new System to install a monitoring agent on a standalone
system or to create a request for the monitoring of an Oracle Engineered System.
? Select Continue to Systems to revert to the Systems and Hosts page.
See Chapter 5, "Managing Systems and Hosts."
d. In the Priv Mode field, select the mode to be used to gain the required root level
privilege on the system. The options are sudo, su, and pfexec.
e. In the Root Password field, enter the root password associated with the system.
(Optional) Toggle the eye icon to view or hide the details.
f. In the ILOM Username field, enter the ILOM username.
g. In the ILOM Password field, enter the password associated with the ILOM.
(Optional) Toggle the eye icon to view or hide the details.
h. In the Retain Credentials and Access section in the top-right corner of the page, select
the Password Vault check-box to upload the credentials into Oracle Password Vault
once validation is complete.
i. Click Validate.
A warning popup appears: supplying incorrect passwords may result in being locked
out of your account.
j. Click Continue.
The validation check is run and a message appears, stating that the credentials have
been validated.
k. Click Next.
The Check Network Connectivity page appears.
14. To check end-to-end connectivity:
a. All network connections (that is, to or from the Gateway to the device) are checked.
If a connection is not made, then a status of Failed is displayed.
Reconfigure the failing connection and validate it before continuing. When all
connectivity passes, continue to the next step.
b. Click Next.
The Compliance Check page appears.
15. To enable Oracle to validate system compliance and network connections:
a. Click Start.
A progress bar measures the rate of system validation. When it reaches 100%, system
status displays as complete and a message appears stating that the compliance check
passed successfully.
b. Click Next.
A warning message appears stating that the compliance check is successful, and
asking whether you would like to proceed.
c. Click Yes.
The Submit Provisioning Request to Oracle page appears.
16. Click Submit Details to Oracle.
The System Install Successful page appears.
System prechecks are complete, and a provisioning request is submitted to Oracle.
A service activation request summary is sent to the customer contact by email.
? Cisco switch
To add a Cisco switch, complete the Admin Name, Admin IP and System Type fields.
9. Click Next.
The View System Information page appears.
10. Confirm the information collected from the source file.
a. All network connections (that is, to or from the Gateway to the device) are checked.
If a connection is not made, then a status of Failed is displayed.
Reconfigure the failing connection and validate it before continuing. When all
connectivity passes, continue to the next step.
b. Click Next.
The Compliance Check page appears.
15. To enable Oracle to validate system compliance and network connections:
a. Click Start.
A progress bar measures the rate of system validation. When it reaches 100%, system
status displays as complete and a message appears stating that the compliance check
passed successfully.
b. Click Next.
A warning message appears stating that the compliance check is successful, and
asking whether you would like to proceed.
c. Click Yes.
The Submit Provisioning Request to Oracle page appears.
16. Click Submit Details to Oracle.
System prechecks have been completed, and a provisioning request is submitted to Oracle.
The System Install Successful page appears.
17. A service activation request summary is sent to the customer contact by email.
18. At this point, you can perform one of the following actions:
? Select Continue to Add new System to install a monitoring agent on a standalone
host or to create a request for the monitoring of an Oracle Engineered System.
? Select Exit to revert to the Systems and Hosts page.
To add an InfiniBand switch, complete the Admin Name, Admin IP and System Type
fields.
? Power Distribution Unit (PDU)
To add a PDU, complete the Admin Name, Admin IP and System Type fields.
? Cisco switch
To add a Cisco switch, complete the Admin Name, Admin IP and System Type fields.
11. Click Next.
The Check Network Connectivity page appears.
12. Review the connectivity checks (Netcheck) back to the Gateway for all of the targets
uploaded through the schematic file. Expand the type sections, such as ZFS Storage or
Compute Nodes, to review the details.
Note: If any mandatory test fails, it is not possible to proceed to the next stage of adding
the Engineered System.
A typical message advises that “Mandatory tests failed and must be resolved to continue.
Please check Oracle Advanced Support Gateway Security Guide”.
Note: If any non-mandatory test fails, you should review the warning message and take
appropriate action before proceeding to the next stage of adding the Engineered System.
a. (Optional) Click Back to revise the system details.
b. (Optional) Click Retest to run the connectivity tests again.
c. Click Next.
The Set Credentials page appears.
13. Supply user credentials for each target to perform validation.
For database servers:
a. (Optional) In the Credentials field, select the Same for All check box to apply the
credentials to all servers of the same type (database servers).
b. In the Host Username field, enter the name of the system.
c. In the Host Password field, enter the password associated with the system.
(Optional) Toggle the eye icon to view or hide the details.
d. In the Priv Mode field, select the mode to be used to gain the required root level
privilege on the system. The options are sudo, su, and pfexec.
e. In the Root Password field, enter the root password associated with the system.
(Optional) Toggle the eye icon to view or hide the details.
f. In the ILOM Username field, enter the ILOM username.
g. In the ILOM Password field, enter the password associated with the ILOM.
(Optional) Toggle the eye icon to view or hide the details.
For Exadata storage servers and ZFS storage arrays:
a. (Optional) In the Credentials field, select the Same for All check box to apply the
credentials to all servers of the same type (Exadata storage servers).
b. The Host Username field contains the value, root. This field cannot be edited.
c. In the Host Password field, enter the root password.
a. Click Start.
A progress bar measures the rate of system validation. When it reaches 100%, system
status displays as complete and a message appears stating that the compliance check
passed successfully.
b. Click Next.
A warning message appears stating that the compliance check is successful, and
asking whether you would like to proceed.
c. Click Yes.
The Submit Provisioning Request to Oracle page appears.
16. Click Submit Details to Oracle.
System prechecks have been completed, and a provisioning request is submitted to Oracle.
The System Install Successful page appears.
17. A service activation request summary is sent to the customer contact by email.
18. At this point, you can perform one of the following actions:
? Select Continue to Add new System to install a monitoring agent on a standalone
host or to create a request for the monitoring of an Oracle Engineered System.
? Select Continue to Systems to revert to the Systems and Hosts page.
? Select Exit to revert to the Systems and Hosts page.
Viewing Statistics
You can expand the Statistics window to review and track CPU, memory, and storage
utilization values for the chosen host. See Figure 5–15.
Use the arrows beside the date value to select the required date.
Hover the cursor over the graphs to review further details about the host series CPU group, the
host series memory group, and the exact utilization percentages.
Viewing Recommendations
Recommendations are made following a review by an Oracle engineer of a current customer
scenario or engagement.
Note: Recommendations apply only to certain, paid, customer engagements, services, and
scenarios.
A typical scenario might involve a customer engaging Oracle for a paid performance review,
for example, of a number of database instances. The engineer investigates the system and issues
a set of results and a series of recommendations.
You can expand the Recommendations window to review:
? Findings: The results of the review of the system or host by an Oracle engineer. For
example, CPU usage was consistently high and was a bottleneck;
? Recommendations: The solution proposed by an Oracle engineer to any issues in the
findings; for example, in response to the high CPU usage, the recommendation is to add
another CPU.
Deactivating Services
You can use Oracle Advanced Support Gateway to deactivate an Engineered System, that is, to
stop monitoring of, for example, an Oracle Exadata Database Machine (Exadata), or Oracle
Database Machine.
You can only deactivate a service on a target (system or host) on which services are running.
To deactivate an Engineered System:
1. From the Systems and Hosts page, select a target on which a service is running.
In the example shown in Figure 5–17, the dm01db01.acs.oracle.com host is selected for
deactivation.
2. From the Actions column, click the Deactivate (X) icon, as highlighted.
A warning dialog asks you to confirm deactivation.
Click Yes to confirm. The host is deactivated.
This chapter provides information about using Oracle Advanced Support Gateway to activate
services.
This chapter consists of the following sections:
? About Activating Services
? Selecting a Service for Activation
? Viewing Discovered Databases
? Deactivating Services
b. In the Monitoring Level field, select the monitoring level associated with the
database. Monitoring levels are restricted to valid monitoring levels for the target, for
example, None, Low, Regular, High, or Intensive.
c. (Optional; depending on the target type) In the DBSNMP field, enter the SNMP
password associated with the database.
d. (Optional; depending on the target type) In the ASMSNMP Password field, enter the
Automatic Storage Management (ASM) SNMP password associated with the
database.
e. (Optional) You can copy credentials from row to row by clicking the arrows icon in
the Actions section of the page.
Note: Users are notified if a credential has already been entered for a particular target.
9. Click Next.
The Service Activation: Review page appears.
Select whether to use the activation wizard to activate the service now, or postpone
completion:
a. Activate Service, or
b. Complete Later
If you select (a), continue to step 10.
If you select (b), continue to "Viewing Discovered Databases".
10. Click Activate Service.
After activating the service, tests are triggered for all untested databases. This may take a
few minutes.
Results are displayed at the top of the page. See Figure 6–4.
13. Select the hosts where you would like to install options by choosing one of the following:
? All Hosts, which is the standard installation option, or
? Specific Hosts, which enables you to customize installation options
14. Click Next.
The Enter Credentials page appears.
Create or update credentials for the following hosts to run diagnostics. Enter root
credentials or a user that has sudo privileges:
a. In the Privilege field, select the mode to be used to gain the required level privilege on
the host. The options are sudo, Normal, and None.
b. In the Username field, enter the password associated with the host.
c. In the Password field, enter the password associated with the host.
15. Click Next.
To add a database:
a. Select the check box associated with the database.
(To add multiple databases, select all associated check boxes.)
Note: If the database you need to activate is not on the list, you need to contact Oracle
to complete the manual installation of the agent and perform a discovery. To request
Oracle discoveries, contact My Oracle Support (MOS).
b. Click Next.
The Service Promotion: Databases page appears.
You use this page to provide credentials for all database targets:
In the Role field, select the role associated with the database. The options are Normal
or SYSDBA.
In the Username field, enter the username associated with the database.
In the Password field, enter the password associated with the database.
c. Click Validate & Next.
The Service Activation: Promoted page appears. Use this page to specify
service-specific options.
As highlighted in the Status column in the example in Figure 6–10, the database lcs12c02 is up,
denoted by the check mark on its database icon, while lcs12c03 is unreachable, denoted by the
gray circle.
Once the databases are activated, monitoring commences.
Deactivating Services
You can use Oracle Advanced Support Gateway to deactivate a service, that is, to deactivate the
targets on which the service is running.
Note: Oracle recommends that Platinum Service customers first refer to their Oracle
representative before deactivating a service on an Engineered System. When a service is
deactivated, the databases remain in the list of managed databases, but no longer have a service
associated with them. To formally remove a database from the list of managed databases,
please refer to your Platinum Infrastructure Team representative.
To deactivate a service:
1. Log on to Oracle Advanced Support Gateway.
The Oracle Advanced Support Gateway Home page appears.
2. From the My Services menu, click Deactivate Service.
This chapter provides information about using the Connectivity Tests (Netcheck) to validate
whether the required firewall ports and connections between Oracle Advanced Support
Gateway and the Oracle database, Engineered System, ILOM or individual component, such as
cell node or InfiniBand, are open.
This chapter consists of the following sections:
? About Gateway Connectivity
? About System Tests
? Viewing System Test Status
? Verifying the External Connection
? Verifying an Internal Connection
? Verifying an ILOM Connection
? Configuring New System Test Targets
These tests help to secure and successfully complete the implementation of services running on
the Gateway.
Related Information
Verifying the External Connection
Verifying an Internal Connection
Verifying an ILOM Connection
Related Information
Verifying an Internal Connection
Related Information
Verifying the External Connection
Related Information
Verifying an ILOM Connection
This page provides a summary of all external (that is, connections to Oracle) and internal
connectivity tests. From this page, you can perform a number of actions:
? Verify the external connection between the Gateway and Oracle. See "Verifying the
External Connection."
? Verify a connection between the Gateway and its ILOM. See "Verifying an ILOM
Connection."
? Verify an internal connection between the Gateway and the Engineered System. See
"Verifying an Internal Connection."
? View a detailed table of internal connectivity tests. See "Verifying an Internal
Connection."
This page displays test results for the external connection to Oracle by service. As shown
in Figure 7–2, five of the supported service connections are up.
4. Click Retest to verify the connection to Oracle.
If the connection is validated, a success message appears.
5. Complete the following parameters on the HTTP Proxy server if http-proxy is required for
outbound communication.
a. (Optional) If HTTP Proxy mode is required, select the Proxy check-box.
b. In the IP Address field, enter your customer IP address.
You can use the hostname or fully-qualified domain name (FQDN) as Oracle
Advanced Support Gateway is configured to use Domain Name Service (DNS.)
c. In the Port field, enter the port associated with the HTTP proxy server.
d. (Optional) If authentication is required for the HTTP proxy server, select the
Authentication check-box, and then enter the proxy username and password.
e. (Optional) If you want to overwrite the global proxy mode, select the Overwrite
Global Proxy check-box.
f. Click Save to complete the HTTP proxy configuration.
5. Click the test name to list all components of the system test. This might include databases,
cell nodes, InfiniBand switches, and so on.
The Status column provides a visual indicator whether an individual component test passed
or failed. The filters also provide a snapshot of successful, failed, skipped, or in progress
tests.
The Direction column provides a visual indicator whether the connection is to or from the
Gateway.
Oracle recommends that the network administrator should resolve any failed tests.
Click Retest to run the system test again.
Click Back to Internal Test Results to return to the Connection Verification: Internal
Systems page.
Related Information
About Gateway Connectivity
About System Tests
Related Information
About Gateway Connectivity
About System Tests
ZFS=zfs,StorageHead,\.*ZFS\.*Storage\.*
ETHERNET_SWITCH=ethernet_switch
ZFS_ORACLE_ENDPOINTS=zfs_oracle_endpoints[root@ct-testimadsi-59 setup]#
This chapter provides information about using the Gateway to monitor and manage Service
Requests (SRs).
This chapter consists of the following sections:
? Viewing Service Requests
? Viewing Service Requests Associated with a Managed System
Click the Service Requests badge to display a table of SRs as shown in Figure 8–2.
You use this page to manage service requests associated with a particular managed system.
3. Expand an individual SR.
The example in Figure 8–3 shows an open SR associated with a target, DB Machine. The
SR listing provides a link to the SR in MOS, the SR type, its current status and severity, a
description of the SR, and the host machine.
This chapter provides information about using the Oracle Advanced Support Gateway to
manage databases and database patches.
This chapter consists of the following sections:
? About Database Management
? Activating a Service on a Database
? About Patching Requests
? Managing Database Patch Compliance
Oracle Advanced Support Gateway and used to analyze and collect data on the health
of database infrastructure.
? Type - Database Instance, Cluster Database, Cluster ASM, Cluster, Cluster Database
Container, and so on - each type denoted by a different icon.
? Status: Displays whether the database is currently up, down, or unreachable.
? Host: Displays the database host name.
? Lifecycle: Displays the lifecycle associated with the database. The values are Test,
Production, Stage, or Development.
? Services: Displays the number of services running on the database. Hover over the
number to display a list of individual services. Refer to Figure 9–3 that shows two
separate Platinum Services instances running on the database.
Related Information
Editing Managed Databases
? Use the Edit list to edit databases, including bulk edits on multiple databases.
See "Editing Managed Databases Using the Edit Icon".
? Use the icons in the Actions column for a particular database to set the database lifecycle
or fault monitoring level, edit its DBSNMP or ASMSNMP passwords, or validate the
Platinum service running on the target.
See "Editing Managed Databases Using the Actions List".
? Edit monitoring configuration details such as Oracle Home, the database lifecycle,
database monitoring level, service name, listener host and listener port.
See "Editing the Monitoring Configuration".
Note: If there are no services running on the selected target, you are unable to edit the
monitoring level.
? Lifecycle: The lifecycle associated with the database. Select from the following
values: Test, Production, Stage, Development, or None. See
? DBSNMP Password: Change the DBSNMP password in Oracle Password Vault to
reflect the database password.
? ASMSNMP Password: Change the ASMSNMP password in Oracle Password Vault
to reflect the database password.
? Validate Activation: Select a database which has at least one Platinum service
activated on it. Enter the credentials for the root user on the host, specify the privilege,
for example, sudo, and click Validate to validate the service running on the database
by performing a JDBC connection test.
Note: Service validation applies only to databases on which at least one Platinum
service is running.
? Manage Tags: Add and apply custom tags such as test to the database.
Customer requests for patching are then automatically assigned to Oracle Engineers based on
their availability, and this information is visible on the Gateway. Requests for patches from
patch coordinators for any date, irrespective of availability, are also accepted. In this case,
Engineers are not assigned.
Furthermore, the Resource Manager can create Platinum Resource Teams and Members to
manage the Engineer time table associated with each day. Assignment hours for Engineers
working in Patching Requests can be assigned, deassigned, updated, or reviewed. Additionally,
Engineers can be assigned to non-delivery activities such as holidays, training, internal
meetings, etc.
Patching automation provides significant features such as:
? Automatic SR creation from the Gateway portal as soon as the patching request is created.
This is a hardware SR using the CSI of the Engineered System that has been scheduled for
application of the patch.
? Automated running of EXAchk scripts against the Exadata target 4 weeks prior to the
Patching event date.
? Following the implementation of the EXAchk scripts, the EXAchk output is automatically
attached to the Patching SR to enable customers and Oracle users to view it and take
appropriate action.
? The ability to create, update, and test Patching Scenarios on the Oracle Advanced Support
Platform portal. As patching scenarios are created or modified, they are transferred to all
connected Gateways.
NOTE: SR creation takes place about 10 minutes after the successful creation of a patching
request.
However, you can manually create an SR by clicking an action button on the Gateway user
interface. In this case, SR creation is instantaneous.
Furthermore, there is also a workaround of manually running EXAchk by clicking an action
button on the Gateway user interface.
2. From the My Services menu, click All Services, and then select a service, for example,
Platinum (ID: XXXXXX).
The service page appears.
3. Click Patch Requests/Patch Compliance.
The Current Requests/Patch Compliance page appears.
You use this page to review the prerequisites to creating a patching request. So, for
Platinum for example:
? The Platinum Patch Scheduling tool supports the creation of Exadata/ZDLRA
patching requests for Gateways connected using SSLVPN, IPSec, or Virtual Private
Network (VPN).
If your Gateway has the Remote Access Control (“Green Button”) feature enabled,
ensure the VPN is enabled before proceeding to create the Patch Request.
? The tool displays only the hosts and database targets currently monitored by the
Oracle Enterprise Manager of the Gateway. If you wish to patch targets not under
Platinum Monitoring, kindly create a service request (SR) to add them under Platinum
Monitoring before you continue.
? By creating this request, you are authorizing Oracle to push the latest Trace File
Analyzer (TFA) software to the database node and run the EXAchk report.
The TFA tools bundle runs on all managed hosts on which you want to run health
checks. The TFA contains the ORAchk, EXAchk, and Diagnostics Logs tools.
ORAchk and EXAchk are lightweight Oracle tools integrated into Oracle Advanced
Support Gateway that are used to analyze and collect data on the health of your system
infrastructure.
Please ensure relevant passwords are updated directly on the Gateway. Refer to the
document Password Management on Platinum Gateway Portal (MOS article
2285834.1.
? Ensure the CSI and MOSID combination is valid for the rack to be patched.
Note: For any questions please reach out to your designated patch coordinator.
For more details about fulfilling the prerequisites, refer to MOS article 2190010.1.
5. Click Accept and Continue.
The Engineered Systems page appears.
You use this page to select an Exadata or ZDLRA machine from the list of non-compliant
machines to initiate a patching request submission.
(Optional) Select More OJVM Patching Details to display a MOS Knowledge Base
article on “Oracle JavaVM Component Database PSU” (OJVM PSU) Patches”.
8. Click Next.
The Virtual Racks and Homes page appears.
9. In the Virtual Rack page, select virtual racks (to a maximum of 4).
a. Expand the required virtual rack by clicking the appropriate Select checkbox:
b. (Optional) Select the components on a particular Virtual Rack that require patching:
? In the Select Oracle Grid Homes field, select databases (to a maximum number of
Grid Homes, depending on the customer contract).
The available Grid Homes are displayed on the Homes page showing Grid Home
location, and providing a bundle patch application option and (if applicable) an
upgrade option.
For the Grid Home, select whether to apply a bundle patch.
A bundle patch is a cumulative collection of fixes for a specific product or component.
A patch of this type is released as needed depending on the product's requirements.
You may also know a bundle patch as: maintenance pack, service pack, MLRs,
cumulative patch, or update release.
For the Grid Home, select whether to apply an upgrade.
If you select to upgrade, provide a new name for the Grid Home and choose the target
grid version.
? In the Select Oracle Homes section, select databases (to a maximum number of
Oracle Homes, depending on the customer contract).
Select from the following options:
a. Select individual databases by clicking Select in the Oracle Home column.
b. (Optional) Select the components on a particular Oracle Home that require
patching or update the Oracle Home configuration as follows:
Select BP to apply a bundle patch.
A bundle patch is a cumulative collection of fixes for a specific product or com-
ponent. A patch of this type is released as needed depending on the product's
requirements. You may also know a bundle patch by one of the following names:
maintenance pack, service pack, MLRs, cumulative patch, or update release.
Figure 9–10 Selecting the Oracle Homes, Grid Homes, and Databases to be Patched
11. In the Select Oracle Homes section, select databases (to a maximum number of Oracle
Homes, depending on the customer contract).
Select from the following options:
a. In the System Function field, select the functional nature of the patch, for example,
production, development, test, and so on.
b. In the OJVM Options field, select from the following options:
Note: Mitigation and OJVM patches can coexist. The mitigation patch can be turned
on and off, at will.
Review My Oracle Support (MOS) note 1929745.1 and select one of the options
below (applying the OJVM requires approximately one (1) hour of downtime per
RAC for both primary and stand-by environments):
Option 1: Apply the OJVM patch (This is the recommended option.)
Option 2: Apply a Mitigation patch.
This process can interfere with other Java applications and is recommended for
short-term patching only if OJVM downtime is not possible.
Option 3: Apply no patch. This option is not recommended.
c. In the text box labeled Owner and Group details of Grid & Oracle Homes to be
patched*, enter the owner and group of Grid & Oracle Home.
d. Execute the following command as the root/sudo user in the first database node of the
cluster:
egrep -v *^#|^$|agent* /etc/oratab | cut -d ":" -f2 | sort | uniq | while read
home;do echo -n "$home==>"; stat -c %U:%G $home/inventory;done
e. In the text box labeled Agent Details*, enter information about the agent.
f. Execute the following command as the root/sudo user in the first database node of the
cluster:
ps -ef | grep agent | grep java | sed 's/\s\+/ /g' |cut -d " " -f 1,8 | sed 's/\/jdk.*//
g. In the EBS database home present in the environment field, select Yes if an EBS
database home is present, or select No if this option is not applicable in this instance.
If you select Yes, please provide in the text box any special instructions that need to be
taken in consideration for EBS patching.
Note: First review the relevant MOS document, ID 1392527.1.
h. In the SAP database home present in the environment field, select Yes if a SAP
database home is present, or select No if this is not applicable in this instance.
i. In the Redundancy* field, select Normal or High.
Note: For rolling events, high redundancy is recommended.
16. Click Next.
The Patching Request: Patch Option page appears.
You use this page to select a patching scenario based on database, patch type, and time.
17. Select the applicable patch option using a combination of the following parameters:
a. The Patch Option column displays the patch type.
b. The Estimated Duration column displays the time taken for the patching process.
c. The Outage Window column displays the outage time for the device.
d. The Description column provides a full explanation of the patch types listed in the
Patch Option column, using the following abbreviations:
NR = Non-Rolling, R = Rolling, M = Maintenance Mode, P = Production Mode
(Optional) Click More to display the full details of the patch type.
For example, In Hybrid - 4 Mode, OS and DB done rolling and Cells and IB
non-rolling. Compute Nodes = R, Grid Home = R, Database Homes= R, Catbundles
= P, Storage Cells = NR, IB Switch = M and OJVM = NR Modified at 2.41.
18. Click Next.
The Patching Request: Schedule page appears.
You use this page to set the patching time and date. All estimates may vary and the final
period may change.
19. Select the time and date for the patching request using the following parameters:
? Schedule a patching date a minimum of four (4) weeks from the present date
? Use the calendar to select available dates within an estimated period.
? You cannot schedule a patch within 90 days of an existing Patch Request on the same
database.
If you attempt to generate a conflicting patch request, an error message appears,
requesting you to cancel previous patch request(s) before scheduling another one.
? Complete all required fields successfully (you cannot submit a patching request in the
next step until the configuration is complete)
Note: Preferred time and date formats are based on the browser time zone.
Note: If you receive a message stating that a system error has occurred, please contact your
patch coordinator for help. See "Contacting the Patch Coordinator".
20. Click Next.
The Review Patching Request page appears.
This page requires you to review and confirm the details of the patching request prior to
submission.
The page lists the machine name and patch version. It specifies the components to be
patched, such as computer nodes, cell nodes, switches, databases, and so on.
Furthermore, the page specifies the estimated duration and outage window associated with
the patching process, the period during which it is likely to take place, the start time, the
nature of the patch process, for example, whether rolling or non-rolling, and so on.
Finally, the applicable Oracle Homes, (Grid Homes), and databases are listed.
21. Click Submit Request.
Note: Do not close the window until submission is completed and the confirmation page
appears.
The Complete Patching Request page appears.
This page displays a message stating that the patch creation has been successful:
Request #123456 submitted successfully. Please wait for 15 minutes for SR to appear on
the Current Requests page.
The Complete Patching Request page also provides details of the patching request as
outlined in Step 20.
22. As the patching Request has been created successfully, click Continue to Current
Requests to review the list of current patching requests.
The Current Requests page appears.
Related Information
Editing the CM for a Patching Request
Canceling Patching Requests
4. For a request for which an SR has already been created, for example, the request numbered
10081, under the CM# column, click Edit.
An Assign CM# dialog box appears.
Related Information
Assigning an SR for a Patching Request
Canceling Patching Requests
Related Information
Canceling Patching Requests
4. Select the checkboxes corresponding to scheduled requests for which SRs have already
been created, for example, the requests numbered 1000322 and 1000301 in Figure 9–21.
5. From the Bulk Actions dropdown, click Cancel.
A cancellation request dialog box appears.
6. In the Cancellation Reason field, enter a justification for canceling the patching requests.
7. Click Yes.
The Current Requests table is refreshed and the patching request status changes to
Canceled in the Progress column.
Related Information
Editing the CM for a Patching Request
2. Select Contact Oracle Support. The Patch Coordinator Contact Details dialog appears,
displaying the patch coordinator name and email address.
Related Information
Creating a Patching Request
This chapter provides information about using Oracle Advanced Support Gateway to manage
database blackouts.
It includes the following topics:
? About Database Blackouts
? Creating Database Blackouts
? Managing Database Blackouts
See "Managing Database Blackouts" for more information about editing scheduled
blackouts.
From the list of blackouts, you can search for a particular blackout instance, create a new
blackout, edit or cancel an existing blackout, and so on.
From the list of completed blackouts, you can search for a particular blackout instance,
review the dates between which a blackout occurred, and view the affected databases.
Editing Blackouts
You can use Oracle Advanced Support Gateway to edit an existing database blackout.
To use Oracle Advanced Support Gateway to edit a blackout:
1. Log on to the Oracle Advanced Support Gateway portal.
The dashboard screen appears.
2. From the top-level Admin menu, select Scheduled Blackouts.
3. For the selected database, click the Edit icon as highlighted in Figure 10–5.
Canceling Blackouts
To cancel a blackout:
1. Log on to the Oracle Advanced Support Gateway portal.
The dashboard screen appears.
2. From the top-level Admin menu, select Scheduled Blackouts.
The Scheduled Blackouts page appears.
3. For the selected database, click the Cancel icon as highlighted in Figure 10–7.
A warning message appears asking you to confirm that you wish to cancel the blackout.
4. Click Yes to confirm.
This chapter provides information about managing the Oracle Advanced Support Gateway
database entitlements.
Note: This chapter applies only to the Patching Service.
This chapter consists of the following sections:
? About Database Entitlements
? About the High Water Mark
? Viewing Database Entitlements
4. Over the remainder of August, the customer user can add further hardware to reach the
maximum core usage of 60. However, even if core usage never exceeds the current high
water mark of 16, billing is for 60 cores per month.
5. When the August cycle ends, the current usage on the first day of September becomes the
initial high water mark for September.
The sample customer entitlement contract shown is for 12 purchased cores over a one-month
duration.
You can also view the entitlement usage over time, so that you can determine, for example, the
time of month when the demand for cores is highest.
Cores used over the limit are displayed in red.
This chapter provides information about optionally configuring the HTTP Proxy server if
http-proxy is required for outbound communication from the Oracle Advanced Support
Gateway. Details of the server IP address and port number can be provided by the customer's
network administrator.
It includes the following topics:
? About the HTTP Proxy Server
? Specifying the HTTP Proxy Server Setting
This chapter describes how to manage and generate server and ILOM certificates for Oracle
Advanced Support Gateway.
It includes the following topics:
? About Server and ILOM Certificates
? Viewing Server Certificates
? Managing Server Certificates
Paste the text of the certificate into the Certificate String field.
Continue to step 7.
6. (To upload a local certificate)
Click Browse.
Select the required certificate from your local server.
Click Open.
7. Click Apply Certificate to complete the replacement of the certificate.
This chapter provides information about enabling remote VPN access to the Oracle Advanced
Support Gateway.
It includes the following topics:
? About the Remote Access Icon
? Enabling Remote Access
? Disabling Remote Access
? Viewing Remote Access History
The icon is a toggle button that controls VPN connectivity and enables a customer to check
VPN connectivity status.
When you click the Remote Access icon, you can enable or disable the remote access session,
or view a history of remote access control sessions.
3. (Optional) Complete the following parameters to specify the VPN duration, and provide a
justification for enabling the VPN.
a. In the Duration field, enter the VPN duration in minutes.
b. In the Justification field, enter a reason for enabling the VPN.
c. Click Save to complete the configuration of the VPN.
Note: On subsequent sessions, when you click Enable, the saved VPN settings are used by
default, and the Gateway VPN Settings page is not displayed.