Use of an RDBMS with the Infor System Console

The Infor System Console requires a database for storing information used by some of its features. This database can be an RDBMS or the Derby database. For information on installing the Derby database, see Installing the Derby Database.

For use of an RDBMS, you must follow the guidelines and requirements listed below. Be sure to note down the details for your database as you need to specify these values when running the installation program.

  • The supported RDBMS are the same as those for Infor Lawson System Foundation, with the exception of IBM DB2 for z/OS.
  • The Infor System Console must be a different database instance of the database you use for Infor Lawson System Foundation.
  • A database administrator should perform all database creation and setup procedures for the Infor System Console.

MS SQL Server 2012, 2014 and 2016 - Database Requirements

Setting Description
Database name The recommended database name is ISCDB.
Collation When creating the new database, set the collation to Latin1_General_BIN.
Schema A schema within the ISC database. The recommended name is ISCDBs.
Login A database login to use to connect to the SQL Server instance.
User A user to log in on the database and schema. This user should also be set as the database owner for the ISC database. Configure the user as follows:
  • When creating the user, map the user to the database login.
  • Set the user as the schema owner of the ISC schema.
  • Set the user as the "db_owner" of the ISC database.
SQL Server Browser This service must be enabled for Infor System Console to connect to the SQL Server instance. It should be enabled and running prior to the installation of the Infor System Console.

Oracle 11g, 12c R1 & R2 and 18c - Database Requirements

Setting Description
Tablespaces

Create two tablespaces, one for the data and one for the indexes.

Set their starting size to 100M.

Set an AUTOEXTEND value depending on the database configuration.
User

A user to log in to the Oracle instance. The user should be set as the schema owner. The recommended name is ISCDB.

Set the user's default tablespace with the ISC data tablespace.
Privileges

Grant the necessary privileges to the user/schema. Ideally, the user has schema owner privileges. A sample list of the necessary privileges needed by the user are below:

  • Alter user QUOTA to 0 on SYSTEM
  • Alter user QUOTA to UNLIMITED on user/schema tablespace
  • Alter user QUOTA to UNLIMITED on index tablespace
  • Grant CONNECT privilege
  • Grant CREATE SESSION
  • Grant CREATE SEQUENCE
  • Grant CREATE TRIGGER
  • Grant CREATE TABLE
  • Grant CREATE TYPE
  • Grant CREATE JOB
  • Grant CREATE ANY INDEX
  • Grant CREATE INDEXTYPE
  • Grant SELECT ON DBA_TABLES
  • Grant SELECT ON DBA_INDEXES
  • Grant SELECT ON DBA_TAB_COLUMNS
  • Grant SELECT ON DBA_IND_COLUMNS
  • Grant SELECT ON DBA_IND_EXPRESSIONS
  • Grant SELECT ON DBA_LOBS

IBM DB2 - Enterprise Edition 10.5/11.5

Setting Description
Database name

Create a database for ISC use only.

  • Set "Code page" to 1252.
  • Set "Code set" to IBM-1252.
  • Set "Sort order" to Binary (identity).
Schema A schema within the database. The recommended schema name is ISCDB.
Table spaces

Create two tablespaces, one for the data and one for the indexes.

Set AUTORESIZE to "yes".
User A user for ISC use only. The user should be set as the database owner for the ISC database.
Authorities and privileges

Grant the necessary authority to the user. Ideally, the user has database administrator authority or the least privileged authority. A sample list of the necessary authorities and privileges needed by the user are below:

  • CONNECTAUTH
  • CREATETABAUTH
  • DBADMAUTH
  • DATAACESSAUTH
  • IMPLSCHEMAAUTH
  • SELECT on all CATALOG VIEWS
IBM DB2 Client The DB2 client must be installed and configured to connect to the DB2 server.