Encrypt Network Traffic
Looker strongly recommends encrypting network traffic between the Looker application and your database. Consider one of the options described here.
If you’re interested in using SSL encryption, see the Oracle documentation.
Create a Looker User
First, create a designated Looker user:
Next, give the new Looker user the ability to create sessions:
Finally, give the Looker user the appropriate
SELECT permissions for the data tables you plan to access from Looker. If you want to access additional tables in the future, you will need to grant
SELECT on those new tables as well.
Ensure Looker Can See All Tables
Looker may not be able to identify tables (especially empty tables) without first collecting statistics in Oracle. If tables you need do not appear in generated LookML or SQL Runner, try executing:
For alternative methods, consult your Oracle documentation.
Set Up Main Database Objects
Your Oracle DBA must set up the following objects and permissions on Oracle. The following commands create
LOOKER_SQL as synonyms for
Run the following commands as the root user to complete this setup. These examples assume that the Looker user’s name is
Set Up Symmetric Aggregates
Your Oracle DBA must set up the
LOOKER_HASH function to enable Symmetric Aggregates. The
LOOKER_HASH function is a synonym for the Oracle
dbms_crypto.hash function. The DBA must also create the associated synonym and privileges. The following commands assume that the Looker user’s name is
.sysprefix on the command above may not be required for your Oracle configuration.
Set Up Persistent Derived Tables
In order to enable Persistent Derived Tables, give the Looker user the
unlimited tablespace and
create table permissions. The following commands assume that the Looker user’s name is
Set Up Query Killing
Follow the instructions below to configure query killing for either a traditional Oracle deployment or an Amazon RDS deployment. For an Amazon RDS employment, there are additional instructions in the next section.
Traditional Oracle and Amazon RDS Deployments
To set up query killing in traditional Oracle deployments the Oracle DBA must create the
LOOKER_KILL_QUERY procedure as a synonym of
ALTER SYSTEM KILL SESSION. To do this, execute the following command:
The DBA will also need to run these related commands:
.sysprefix on the commands above may not be required for your Oracle configuration.
Amazon RDS Deployments Only
For Amazon RDS deployments, you’ll need to utilize parameter groups.
Once completed, PDTs can be enabled by setting the temp database on the Edit Connection screen of your Looker instance. Use the same name as the user you created for Looker. The following example assumes that the Looker user is named
Looker’s ability to provide some features depends on whether the database dialect can support them.
In the current Looker release, Oracle supports the following Looker features:
After completing the database configuration, you can connect to the database from Looker using these directions.