FDM uses the FDM Oracle account to access the FDM Oracle database. FDM can use Windows Integrated Security or the Oracle account that you specify. If FDM is accessed from the Web and Windows Integrated Security is used to access the Oracle database, the Application Server account is used to log on to the Oracle database. If Workbench is used, the user name that you used to log on to Workbench is used to log on to the Oracle database.
You can connect through Windows Integrated Security only if Oracle is configured to enable such connections. By default, the sqlnet.ora file contains the entry that enables operating system authentication. The SQLNET.AUTHENTICATION_SERVICES= (NTS) entry enables authentication by the operating system.
To create an Oracle account that can connect using Windows Integrated Security, you must know the value of the os_authent_prefix parameter. Oracle uses this parameter when it authenticates external users. The value of this parameter is prefixed to the operating system user name. The default value is OPS$, but the value may be different on your system. If the value is OPS$, the Oracle account is formatted as OPS$hostname\username, where hostname is the machine name or domain name, and username is the Windows user name.
New FDM accounts must be granted the DBA role or the following system privileges:
The default tablespace used by FDM is the Users tablespace. Oracle recommends creating a new tablespace for Default. The account should have an appropriate quota set on each tablespace used to allow for future data growth. If you want to ensure that the user does not exceed a space-used threshold or if you have any questions about the appropriate value for the quota, consult the database administrator.