Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

FREE TRIALS

Foglight for Oracle (Cartridge) 6.0.0.10 - Deployment Guide

Table of Contents

Deployment pre-requisites

Architecture Deployment in Centralized vs Distributed Hardware requirements

SQL PI configured All-in-One Installation SQL PI not configured Manual configuration requirement for SQL PI Repository

Supported monitoring platforms Supported monitored databases Supported monitored BI services PI aggregation and retention Permissions for SQL Server Based PI Repository Database Permissions for monitored databases

Permissions for Oracle databases

Additional configurations for Amazon RDS for Oracle instances

Permissions for SQL Server databases Permissions for SAP ASE databases Permissions for DB2 for LUW databases Permissions for Azure SQL Database

Permissions for monitored operating systems

Install the DB cartridge and DB agent

Install the DB cartridge Install a single DB agent

Install a single SQL Server or Oracle agent Install a single DB2 agent Install a single SAP ASE agent Install an Azure SQL DB agent

Special configurations

Foglight Upgrades High Availability Federation Concentrator (Proxy)

Permissions for SQL Server Based PI Repository Database

If you are using SQL Server Based PI Repository®, ensure that these permissions are set.

Table 10. SQL Server Permissions for Creating a New PI Repository Database
Instance Level		Database Level
CREATE ANY DATABASE	Granted for: Creating SQL PI Database	db_owner	Granted for: Insert/delete PI records


	NOTE: The “CREATE ANY DATABASE” permission can be removed after the SQL PI database is created. The SQL PI user should be the database owner of the new created SQL PI database.

Table 11. SQL Server Permissions for Using an Existing PI Repository Database
Instance Level		Database Level
VIEW ANY DATABASE	Granted for: Select Existing Database	db_owner	Granted for: Insert/delete PI records

Permissions for monitored databases

Ensure that you set the permissions required, based on which database you are using:

•

Permissions for Oracle databases

•

Permissions for SQL Server databases

•

Permissions for SAP ASE databases

•

Permissions for DB2 for LUW databases

•

Permissions for Azure SQL Database

Permissions for Oracle databases

If you are using Oracle®, ensure that these permissions are set.

Grant Select on the following dictionary views:


	NOTE: For Oracle 12c and above, replace all the dba_* dictionary views with the cdb prefix (cdb_*)

Table 12. Oracle views requiring Select permission
Dictionary view	Dictionary view	Dictionary view
dba_constraints dba_data_files dba_db_links dba_directories dba_extents	gv_$session gv_$session_wait gv_$sort_segment gv_$spparameter gv_$sql	v_$logfile v_$open_cursor v_$osstat v_$parameter v_$pgastat
dba_free_space dba_indexes dba_jobs dba_jobs_running dba_libraries	gv_$sysstat gv_$temp_extent_pool gv_$undostat obj$ recyclebin$	v_$pq_sysstat v_$process v_$recovery_file_dest v_$resource v_$result_cache_statistics
dba_objects dba_profiles dba_role_privs dba_roles dba_rollback_segs	ts$ uet$ user$ v_$archive_dest v_$archived_log	v_$rman_status v_$rowcache v_$segstat v_$segment_statistics v_$sess_time_model
dba_scheduler_jobs dba_scheduler_running_jobs dba_segments dba_sequences dba_sequences	v_$asm_disk v_$asm_disk_stat v_$asm_diskgroup v_$asm_diskgroup v_$asm_diskgroup_stat	v_$session v_$session_wait v_$sesstat v_$sga v_$sga_dynamic_components
dba_synonyms dba_sys_privs dba_tab_columns dba_tab_privs dba_tables	v_$asm_operation v_$asm_template v_$cell v_$controlfile v_$database	v_$sgainfo v_$sgastat v_$spparameter v_$sql v_$sql_plan
dba_tablespaces dba_temp_files dba_temp_free_space dba_undo_extents dba_users	v_$datafile v_$dataguard_status v_$dbfile v_$dispatcher v_$enqueue_stat	v_$sqlarea v_$sqltext_with_newlines v_$standby_log v_$statname v_$sysmetric
dba_views dba_recyclebin fet$ file$ gv_$archive_dest	v_$enqueue_statistics v_$event_name v_$filestat v_$fixed_table v_$flash_recovery_area_usage	v_$sysstat v_$system_event v_$system_parameter v_$tablespace v_$temp_extent_pool
gv_$archived_log gv_$instance gv_$instance_cache_transfer gv_$lock	v_$instance v_$instance_cache_transfer v_$iostat_file v_$librarycache	v_$temp_space_header v_$tempfile v_$tempstat v_$transaction
gv_$pq_sysstat gv_$rman_configuration gv_$rman_output	v_$lock v_$log v_$log_history v_$undostat	v_$memory_target_advice v_$pga_target_advice v_$sga_target_advice v_$sql_shared_cursor
gv_$archive_dest_status gv_$dataguard_stats gv_$dataguard_status	v_$flashback_database_log v_$dataguard_config	v_$backup_set_details v_$session_event v_$services

Additional configurations for Amazon RDS for Oracle instances

There are two user credential options for monitoring Amazon RDS for Oracle instances:

•

Master predefined user that comes as part of Amazon RDS for Oracle instance

•

Separate user who has either of the following:

•

SELECT_CATALOG_ROLE or SELECT ANY TABLE system privilege

•

Grant additional permissions by manually executing the following commands from the master user:

•

EXEC RDSADMIN.RDSADMIN_UTIL.GRANT_SYS_OBJECT(p_obj_name=>'FET$',p_grantee =>'TEST', p_privilege => 'SELECT');

•

EXEC RDSADMIN.RDSADMIN_UTIL.GRANT_SYS_OBJECT(p_obj_name=>'UET$',p_grantee =>'TEST', p_privilege => 'SELECT');

•

EXEC RDSADMIN.RDSADMIN_UTIL.GRANT_SYS_OBJECT(p_obj_name=>'FILE$',p_grantee =>'TEST', p_privilege => 'SELECT');

•

EXEC RDSADMIN.RDSADMIN_UTIL.GRANT_SYS_OBJECT(p_obj_name=>'OBJ$',p_grantee =>'TEST', p_privilege => 'SELECT');

•

EXEC RDSADMIN.RDSADMIN_UTIL.GRANT_SYS_OBJECT(p_obj_name=>'TS$',p_grantee =>'TEST', p_privilege => 'SELECT');

•

EXEC RDSADMIN.RDSADMIN_UTIL.GRANT_SYS_OBJECT(p_obj_name=>'USER$',p_grantee =>'TEST', p_privilege => 'SELECT');

•

EXEC RDSADMIN.RDSADMIN_UTIL.GRANT_SYS_OBJECT(p_obj_name=>'RECYCLEBIN$',p_grantee =>'TEST', p_privilege => 'SELECT');

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating