Database requirements
The Nexeed Industrial Application System requires access to databases for data management. Different databases are supported. Module specific configurations are documented in the module’s operations manual.
This chapter describes the basic requirements and configurations of the various databases.
Supported databases
IAS modules support different database vendors. The following table provides an overview which vendors are supported by which module.
| Module | Oracle | MSSQL | Additional DB required |
|---|---|---|---|
Multitenant Access Control |
yes |
yes |
|
Web Portal |
yes |
yes |
|
Master Data Management |
yes |
yes |
|
Ticket Management |
yes |
yes |
|
Direct Data Link |
no |
yes |
|
Data Publisher |
yes |
yes |
|
Notification Service |
yes |
yes |
|
Orchestrator |
yes |
yes |
|
AI Services |
yes |
yes |
|
Nexeed Gateway |
yes |
yes |
|
Engineering UI |
yes |
yes |
|
ID Builder |
yes |
yes |
|
ERP Connectivity |
yes |
yes |
|
Order Management |
yes |
no |
|
Line Control* |
yes |
yes (2016) |
|
Packaging Control* |
yes |
no |
|
Block Management |
yes |
yes |
|
Product Setup Management |
yes |
yes |
|
Material Management |
yes |
no |
|
Stock Management |
no |
no |
MongoDB |
Transport Management w. AGV Transport Orders |
no |
no |
MongoDB |
AGV Control Center |
yes |
yes |
|
KPI Reporting |
yes |
no |
|
Global Production Overview |
yes |
yes |
|
Shift Book |
yes |
no |
|
Andon Live |
yes |
no |
|
Deviation Processor |
yes |
yes |
|
Operational Routines |
yes |
yes |
|
Process Quality |
yes |
yes |
InfluxDB |
Part Traceability w. Archiving Bridge* |
yes |
no |
|
Setup Specs |
yes |
yes |
|
Condition Monitoring |
yes |
yes |
InfluxDB |
Maintenance Management |
no |
yes |
|
Tool Management |
yes |
yes |
Depends on the use case. For details see module’s operations manual.
Oracle database
Recommended version: Oracle 19c (most recent RU) EE
Instance parameters
| Parameter | Value | Notice |
|---|---|---|
Character Set |
AL32UTF8 |
WE8MSWIN1252 supported for existing installations |
MAXDATAFILES |
256 |
recommended |
MAXLOGFILES |
30 |
recommended |
MAXLOGMEMBERS |
3 |
recommended |
MAXINSTANCES |
8 |
recommended |
MAXLOGHISTORY |
100 |
recommended |
Local File Storage |
256 |
required |
DB_FILE_MULTIBLOCK_READ_COUNT |
16 |
required |
CURSOR_SHARING |
force |
required |
OPEN_CURSORS |
>= 1000 |
required |
OPTIMIZER_INDEX_COST_ADJ |
>= 30 |
required |
PGA_AGGREGATE_TARGET |
>= 500 MByte |
required |
SGA_TARGET |
>= 8GByte |
required |
DB_CACHE_SIZE |
>= 60% SGA_TARGET |
required |
SHARED_POOL_SIZE |
>= 30% SGA_TARGET |
required |
UNDO_RETENTION |
16000 |
required |
OPTIMIZER_ADAPTIVE_PLANS |
false |
required |
OPTIMIZER_ADAPTIVE_STATISICS |
false |
required |
OPTIMIZER_ADAPTIVE_REPORTING_ONLY |
true |
required |
DBTIMEZONE |
Europe/Berlin |
required |
USE_NS_PROBES_FOR_DCD |
false |
recommended |
LOG_FILE_SIZE |
> 500 MByte |
recommended |
REDO_LOG_FILES |
> 3 |
recommended |
Optimizer Statistics Gathering |
enabled |
recommended |
Segment Advisor |
disabled |
recommended |
Automatic SQL Tuning |
disalbed |
recommended |
Note: The Timezone format should be "Europe/Berlin" or similar (depending on the customer location) but not an offset +02:00. The timezone can be check with the following oracle query: SELECT DBTIMEZONE FROM dual;