For each Fabasoft Folio COO Service, an Oracle user has to be created. As default tablespace, use the corresponding previously created tablespace. See chapter “Tablespace Creation” for more details.
Note: If container databases are used, each COO Service user must be created in the desired pluggable database before the installation starts. Additionally, the tnsnames.ora file on the backend servers must point to the this PDB. During the Fabasoft setup, the option “Use an existing database user” must be selected and as COO Service users the created database users must be used.
These users should have the following roles:
Additionally, the following right should be granted to the Oracle users for the Fabasoft Folio COO Services:
GRANT SELECT ON DBA_PENDING_TRANSACTIONS TO <service user>
It is also possible to grant the right DBA_PENDING_TRANSACTIONS to all Oracle users as these tables do not contain any security relevant data.
GRANT SELECT ON DBA_PENDING_TRANSACTIONS TO PUBLIC
Note: Fabasoft Folio COO services connect to Oracle using the Oracle XA interface. Therefore, limitations of characters usable in usernames and passwords apply. Besides the unsupported characters “+” and “=” documented by Oracle, the database may impose further restrictions.