Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Before installing a SQL an Oracle agent (collector), check Precise for MS-SQL Oracle requirements.

If the SQL Oracle instance is part of a an SAP or PeopleSoft application, check the full installation guide for further details.

Internationalization

To facilitate SQL Server Internationalization, verify that:

  • the locale of the PMDB, FocalPoint, PMDB instances, and servers with monitored SQL instances are valid (and are the same for all servers),
  • the instance and database collation of the PMDB and monitored SQL instances are the same, and support chosen locale, and
  • the PMDB database is case sensitive.

Adding a SQL instance for monitoring

Installing on Oracle Multitenant architecture (Containerized databases)

You can install Precise on Oracle Multitenant architecture (containerized databases) on Oracle 12c R2 and later.

Precise monitors the container root and all of the open pluggable databases.

At the time of installing the Precise for Oracle collector for a containerized Oracle instance, all pluggable databases (PDBs) should be open and not in restricted mode. Any PDBs that are in a closed state or in restricted mode at the time of instance installation are ignored for collector schema creation. If, and when such PDBs are opened, the Precise for Oracle collector schema must be manually created on those PDBs using manual schema scripts.

When a new PDB is added to an Oracle instance monitored with Precise, the Precise for Oracle schema must be created on it based on the instructions for Precise for Oracle manual schema collector installation and the Precise for Oracle collectors must be restarted.

Installing an Oracle cluster

Configuring a cluster is supported for Oracle RAC (Real Application Clusters). For more information on how to install an Oracle instance for RAC, see the Installing the Oracle instance section. The Cluster setting dialog is available only in case you have Oracle clusters or instances. For information on editing or removing an existing instance, see Editing or removing tier instances or clusters.

Adding an Oracle instance for monitoring

You can add a new tier instance on the AdminPoint Instances screen. Before adding a tier instance, create a list of all required inputs based on the following information.

To add a tier instance To add a SQL instance for monitoring

  1. From the AdminPoint tab, select Installation. A list of applications appears.
  2. If the application already exists , click Edit to make changes. If the application does not exist , click Add, and then add the application.
    Image Added
  3. Once the Applications tab opens, click Oracle.
  4. On the Oracle tab, click Add.
    Image Added
  5. If the Oracle instance is new, then select Add. If the Oracle instance already exists, then click Add Existing.
Info

It is important that you always refresh AdminPoint after adding an instance.

Defining Oracle property settings

To add properties for an Oracle tier instance

  1. From the available drop-down menu, select the server containing the Oracle instance.
  2. Click Add to type the name of a server not in the bottom right-hand corner, as shown in the following image.
    Image Removed
    The APMInstanceInstaller.exe opens.
  3. Click Open APMInstaller.exe, and the Precise Application Installer opens.
    Image Removed
  4. Select the appropriate Application NameApplication Type, and Database Vendor, and then click Next.
    Image Removed
  5. In the Install Tiers area for the applications, select SQL Server, and then click Add.
    Image Removed
  6. In the Properties tab, add the following SQL instance details:
    1. SQL Server instance name or <Host>,<Port>
    2. the server from which you want the instance monitored (local or remote monitoring)
    3. Windows or SQL authentication
    4. service credentials
      Image Removed
  7. Click Next. The Preview tab appears.
    Image Removed
  8. Review the details, and then click Install. The installation starts and installs all components for the SQL instance.
  9. Once the installation is complete, the Finish tab appears.
    Image Removed
  10. Click Finish.
  11. Review the Application tab to make sure that the new instance appears.
    Image Removed
  12. Repeat these steps to add more instances, and then click Finish
  13. Refresh the applications and note that the new application appears.
    Image Removed
  14. Select the Applications tab, and the new application appears with the added SQL Server instance(s).
    Image Removed
  15. the list. For more information about adding a server, see Adding a new server.
    Image Added
  16. Select the Oracle SID from the drop-down list, If this is a container database, this must be the CDB name.
  17. Verify the Oracle home folder path. If this is not correct, use the browse (...) feature to search for, and then select the appropriate location.
  18. Select the appropriate Oracle release version for the instance.
  19. Select the appropriate Oracle listener port.
  20. Type the appropriate user name, and then type the associated password. This is the name of the Oracle user account that has DBA privileges. This account is used for the initial connection with the Oracle database and to create a user account named, "precise" in the database. The DBA user is used only for these tasks during installation and it not used after that process. The password is not saved by Precise.
  21. In the Connect As field, select the method of connection.
    • The Oracle Tier installation requires creating objects (views and packages) in the SYS schema and requires privileged access to the SYS schema. This option allows connecting to your Oracle instance with a user that has SYSDBA privileges.
    • If you did not use the manual schema installation, you must connect using a DBA user as 'SYSDBA'. For more information about using the manual schema, see Manually installing Precise for Oracle database schemas.
    • To connect as 'SYSDBA,' type the Oracle initialization parameter remote_login_passwordfile as a password file, meaning that this parameter must be set to share or exclusive. You also must grant SYSDBA privileges to the DBA user for the Oracle Tier installation.
  22. Click Next.

Entering a user for an Oracle schema credential

Image Added

To enter a new user for an Oracle Schema credential

  1. Select Create a new user.
  2. Type the user name. If this is installed in an Oracle Container Database, the user must be prefixed C##.
  3. Type and then confirm the password associated with the user account.
  4. If you want to see the tablespaces definition, click Advanced.
  5. Click Next.

To enter an existing user for an Oracle Schema credential

  1. Select Use an existing user.
  2. Click Find User to locate an existing user name.
  3. On the Find User window, click Find to filter for an existing (available) user name.
  4. Select an available user name, and then click OK. If this is installed in an Oracle Container Database, the user must be prefixed C##.
    The selected user name now appears on the Oracle Schema credential screen.
  5. On the Oracle Schema credential screen, type the password associated with the existing user.
  6. If you want to see the tablespaces definition, click Advanced.
  7. Click Next.

About the tablespace creation page

The tablespace creation script page enables the user to activate default tablespace creation, or to create customized tablespaces.

Image Added

Image Added

Click Next to activate default tablespace creation.

If you want to modify Oracle instance tablespace creation, copy the text that appears on the screen to SQL*PLUS and run as you wish. Then click Next to continue installation while using the tablespaces you have created.

Oracle tier installation Preview page

The Preview page signifies that the AdminPoint Tier installer gathered enough information to begin installation.

Image Added

The Preview page displays the following details before installation begins:

  • server name or IP address
  • name of the monitored server
  • actions queued in their respective order
  • location of the installation folder
  • required disk space
  • currently-available disk space

You can make any necessary changes at this point. Click Back to go to the appropriate screen to make a change, and then click Next to continue installation. Click Cancel to stop the installation process.

Oracle tier Installation progress page

This page appears when the AdminPoint Tier installer is performing the installation and displays the progress of actual installation on selected servers. The installation process may take several minutes. 

Image Added

Oracle tier installation complete page

This page appears when the AdminPoint tier installer completes installation of all tier instances.

Image Added

If there are no action items, click Finish to complete the instance installation. If there are action items, click Next.

To add additional instances, repeat the steps above, otherwise click Finish.

Refresh the applications and the new application is visible.

Image Added

Select the Applications tab and the new application appears with the Oracle instance(s) added.

Image Added


Scroll Ignore
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmltrue
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
 | 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
 
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
 | 
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/precise/
 | 
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
 
|
 
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
 | 
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
 
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse