|
Term
|
Comment
|
|---|---|
|
Database
|
A database is a collection of data, usually in the form of tables or files, under the control of a database management system (DBMS).
In Oracle, a database is often called 'Instance'. Each running instance is associated to a specific process.
|
|
Database server (hardware)
|
A database server is a machine providing database services to other machines. In this document the database server is a machine running relational database management systems. A database server can host one or several instances.
Example:
• Server 'iba.company.com'
• Server '192.888.777.666'
• Server 'SQL02'
|
|
DBA
|
The DataBase Administrator is responsible for administering, monitoring, and maintaining the database.
|
|
DBMS
|
A DataBase Management System (DBMS) is a set of software programs that controls the organization, storage, management, and retrieval of data in a database.
Example: GBMS, Oracle…
|
|
GBMS
|
GBMS is MEGA's historical proprietary DBMS.
|
|
Instant client
|
Oracle technology. It enables running your applications without installing the standard Oracle client or having an ORACLE_HOME.
Oracle instant client is embedded in HOPEX installations from MEGA 2009 SP1 and higher.
|
|
HOPEX Environment
|
On RDBMS installations, an environment is a group of directories where HOPEX generates documents, log files, etc.
|
|
RDBMS
|
Relational DataBase Management System.
Examples: Oracle, SQL Server, DB2 Universal Database,…
|
|
Repository
|
A repository is a structured collection of data.
A HOPEX repository is a collection of HOPEX data. Data is structured in relation to a metamodel. Object names are often unique within the repository or with a namespace of the repository.
|
|
Schema
|
A schema object is a logical data storage structure.
In Oracle, it is a collection of objects (example: tables, views, indexes, procedures, functions…) mapped to an Oracle user. A schema is stored in one/several tablespace objects of the database.
It is strongly recommended to isolate each HOPEX Repository in a separate Oracle schema (User Repositories AND SystemDb repository)
|
|
SID
|
Oracle term. System Identifier. It enables identifying instances (database)
|
|
Storage format
|
HOPEX term. It defines the type of DBMS storing HOPEX data.
Possible values are:
o GBMS: storage in HOPEX historical DBMS
o Oracle: storage in Oracle DBMS
o SQL Server: storage in SQL Server DBMS
|
|
SystemDb repository
|
HOPEX Term. It is a HOPEX repository that stores system data, such as, user definition, metamodel definition, template definitions, queries, diagram configuration. This data can be shared by all user repositories within a HOPEX environment. A SystemDb repository is associated to one/several user repositories.
|
|
Tablespace
|
Oracle term. A tablespace is a logical group of data within a database. A tablespace usually groups table and/or index objects.
|
|
User repository
|
HOPEX Term. This is a HOPEX repository storing data, such as diagrams, org-units...
|