Tasks the Oracle administrator must complete

To store the Microsoft Dynamics AX data in an Oracle database, you must work with an Oracle database administrator to perform the following tasks. To set up multiple Microsoft Dynamics AX databases, follow the procedures below and create each database under a different schema.

Set up an Oracle database and grant rights

On the Oracle database server, the Oracle administrator must perform the following steps.

  1. Set up Oracle Database 10g with the following settings for tablespaces and indexspaces.



    Database name (required)

    Any valid Oracle database name

    Tablespace (recommended)

    Create tablespaces for Microsoft Dynamics AX to use. For example:

    • AXTAB (for tables)

    • AXIDX (for indexes)

    • AXTMP (for temporary tables)

    The Microsoft Dynamics AX administrator will configure the tablespaces after Microsoft Dynamics AX has been fully installed.

    If you are upgrading, you must use the same tablespace names in the previous version and the new version.

    Collation (required)

    Microsoft Dynamics AX supports Unicode collations. If you are setting up a new Microsoft Dynamics AX installation, we recommend that you select a Windows collation for your locale. For more information about choosing a collation for an Oracle database, see the Oracle documentation.

  2. Create a database user for the Microsoft Dynamics AX administrator to use when installing an AOS instance. Setup uses the Windows account of the installing user to connect to the Oracle database and to write stored procedures to the Oracle database. Set the following rights:

    • Add the network account of the person who will install the AOS to the database administrators group in Oracle.

    • Set Oracle to use Windows authentication.

  3. Optional: Create database users for the service accounts of all AOS instances. Grant the database users the following rights in the database:

    GRANT CREATE USER TO "<AOSaccount_name>";
    GRANT SELECT ANY CATALOG TO "<AOSaccount_name>";
    GRANT CREATE PROCEDURE TO "<AOSaccount_name>";

    If you do not perform this step, Setup grants the following rights to the current AOS instance:



  4. Optional: Create a schema (user account) for each database instance and grant the rights listed in Rights for a manually created Oracle schema.

    If you do not perform this step, Setup grants the following rights to the schema.




  5. Optional: Import the Setup stored procedures. You can find the stored procedures OracleCreateServerSessions and OracleCreateUserSessions in the Support folder on the Microsoft Dynamics AX DVD. The stored procedures have been wrapped. If you do not perform this step manually, it will be performed by Microsoft Dynamics AX Setup.

Configure rights outside of Oracle

On the computer that runs Oracle, the Oracle administrator must configure the following rights.

  1. Enable Windows remote authentication. Add the following entry to the SQLNET.ORA file.


  2. If some users that log on from clients are not on the same domain as the database, you must also set REMOTE_OS_AUTHENT to true, and restart the Oracle service.

Install the Oracle client

On the computer where the AOS instance will be installed, the Oracle administrator must install the Oracle client.

  1. Install an Oracle Database Client (10g release), Administrator version.

  2. If the system uses a TNS Names connection, open the TNSNames.ora file, add the following statements to it, and then save the file:

                    DatabaseName =
        (ADDRESS = 
            (PROTOCOL = TCP)(HOST = serverhostname)(PORT = portnumber)
        (CONNECT_DATA =
            (SERVER = DEDICATED)
            (SERVICE_NAME = databasename)