Configuring Oracle Databases

This chapter explains how to create a new server configuration and Oracle schema user for use with Atlas Hub. Atlas Hub stores everything except for file archives and server startup information in the schema user.

This chapter also provides an overview of the tuning and maintenance SQL scripts that are provided with Atlas Hub and explains how to use them.

When you create a server configuration, Atlas Hub can automatically create the tablespace and schema user. However, if you prefer, you can create the tablespace and schema user manually.

Note: All of the tablespaces created using Atlas Hub automatically create locally-managed tablespaces. All tablespaces created by Atlas Hub use AUTOALLOCATE. Atlas Hub supports Oracle Universal Installer for client. Consult with your database administrator for more information.


When this chapter uses the terms "database instance" and "schema user", it uses Oracle terminology. Each database instance can manage a number of different schema users. Each Atlas Hub configuration has its own schema user. Elsewhere in the documentation you will find the terminology common to the other databases that Atlas Hub supports. For example, when you install Microsoft SQL Server on a computer, you can run several instances of it. Each instance can manage a number of different databases. Therefore, when you see the term “database” in other parts of these manuals, think “schema user”.

Logging Onto Schema Users

It is highly recommended that you use a dedicated Atlas Hub user account to run or log onto Atlas Hub schema users. System administrator accounts usually have unlimited privileges. Any anomalies or errors that occur while logged in as the system administrator may result in unrecoverable damage to the Atlas Hub schema users and other schema users managed by the same database.