Connect Oracle

Connect your Oracle source to Bigeye.

1. Create a read-only user in Oracle

Bigeye only requires a read-only user for connecting to your database. Here is a sample for creating one, along with the permission to connect:

CREATE USER bigeye_read_only
IDENTIFIED BY <your_password_here>

GRANT CREATE SESSION to bigeye_read_only;

-- The grants below are for lineage
GRANT SELECT ANY DICTIONARY TO bigeye_read_only;
-- The grant below allows visibility into stored procedures and function text
GRANT SELECT ON SYS.DBA_SOURCE TO bigeye_read_only;

2. Grant select privileges to the schemas that Bigeye can access

BEGIN
  FOR x IN (SELECT  owner,object_name FROM dba_objects WHERE owner IN ('SCHEMA_1', 'SCHEMA_2', 'SCHEMA_N') and object_type in ('TABLE','VIEW'))
  LOOP
   EXECUTE IMMEDIATE 'GRANT SELECT ON '||x.owner||'.'|| x.object_name ||' TO BIGEYE_READ_ONLY';
  END LOOP;
END;

3. Review the Oracle connector notes below

Note that:

Since Bigeye monitoring uses multiple sessions during connections, ensure that you have an appropriate number of connections configured. For more information on sessions and how to alter them, read here.
You can enforce limits to database resources by creating a profile for the Bigeye user. Since connections can sit idle, enforce a low IDLE_TIME. For more information, read here.
If your Oracle instance is deployed in the cloud, allow all of Bigeye's Static IP addresses access.

Below are the objects accessed by the Oracle lineage connector.

SYS.all_arguments
SYS.all_cluster_hash_expressions
SYS.all_clusters
SYS.all_col_privs
SYS.all_cons_columns
SYS.all_constraints
SYS.all_db_links
SYS.all_errors
SYS.all_ind_columns
SYS.all_ind_expressions
SYS.all_indexes
SYS.all_mviews
SYS.all_object_tables
SYS.all_objects
SYS.all_sequences
SYS.all_synonyms
SYS.all_tab_columns
SYS.all_tab_privs_made
SYS.all_tables
SYS.all_triggers
SYS.all_type_attrs
SYS.all_type_methods
SYS.all_types
SYS.all_users
SYS.all_views
SYS.dba_data_files
SYS.dba_profiles
SYS.dba_role_privs
SYS.dba_roles
SYS.dba_rollback_segs
SYS.dba_tablespaces

4. Next Steps

After you've configured the source, Bigeye loads and profiles your tables. It can take up to 24 hours for the profiling to complete and your autometrics and autothresholds to populate. See how to deploy autometrics in the Getting Started guide.