---
title: "Oracle Implementation Details - Lasernet Keep General Information"
slug: "oracle-implementation-details"
description: "This article outlines the basic implementation details for using Oracle as the database management system for Lasernet Keep. This guide is for technical users."
tags: ["Database", "Lasernet Keep", "Oracle"]
updated: 2026-09-18T15:21:00Z
published: 2026-09-18T15:21:00Z
canonical: "kb.lasernetgroup.com/oracle-implementation-details"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Oracle Implementation Details

This article outlines the basic implementation details for using Oracle as the database management system for Lasernet Keep. This guide is for technical users who are already familiar with Oracle’s functionality and have the software installed.

## Prerequisites

Complete all steps while connected as an existing database administrator or admin user, and connected to the correct Oracle database or program database that Keep will use.

To ensure any tables, indexes, and permissions used specifically for the Keep application are operationally separate from any existing data in your Oracle database, we recommend creating the following:

- A new connecting user.
- A dedicated schema owned by that user is implicitly created by Oracle.
- A default tablespace or a quota on an existing, suitable tablespace can be used.

Then, grant the required permissions.

> [!NOTE]
> Note
> 
> In Oracle, a user and a schema are closely linked: each user owns a single schema with the same name as the user. Therefore, Oracle stores objects created by the `keep_app` user in the `keep_app` schema. For this reason, a separate `CREATE SCHEMA` step is not normally required.

### Create a User and Schema

To create a new connecting user, enter the following command within the Oracle terminal:

```ruleslanguage
CREATE USER keep_app IDENTIFIED BY "<strong-password>" 
  DEFAULT TABLESPACE keep_data 
  TEMPORARY TABLESPACE temp 
  QUOTA UNLIMITED ON keep_data;
```

Replace tablespace names and quota values with values appropriate for your environment.

> [!NOTE]
> Note
> 
> Since the WildFly datasource connects as `keep_app`, unqualified Keep table names will resolve to objects in the `keep_app` schema.

### Grant Required Permissions

Keep creates and upgrades its own database objects during installation and application upgrades. Therefore, the Oracle connecting user must have the necessary permissions to connect and to create tables, sequences, and triggers in its own schema.

To grant the necessary permissions to the Oracle user, enter the following commands within the Oracle terminal:

```ruleslanguage
GRANT CREATE SESSION TO keep_app; 

GRANT CREATE TABLE TO keep_app; 

GRANT CREATE SEQUENCE TO keep_app; 

GRANT CREATE TRIGGER TO keep_app; 

GRANT CREATE VIEW TO keep_app;
```

> [!NOTE]
> Note
> 
> No separate `CREATE INDEX` privilege is normally required for Keep, as the app creates indexes on tables in its own schema.
> 
> Keep also performs Data Definition Language (DDL) commands, such as `ALTER TABLE`, against objects it owns. Because `keep_app` owns the objects, additional `ALTER ANY TABLE` or similar cross-schema privileges should not be required.

## Authentication Methods

Keep connects to Oracle using username and password authentication.

## Troubleshooting

For information on troubleshooting and common Oracle errors, consult [the dedicated article](/v1/docs/datasource-and-configuration-issues-in-lasernet-keep).

For more general information on Oracle, consult [Oracle’s documentation](https://docs.oracle.com/en/).