4 Configuration Tasks When Installing from the Database

4.4.2.1 Running the apxconf.sql Configuration Script

In a new installation, you configure the embedded PL/SQL gateway by running the configuration script apxconf.sql. Then, you unlock the ANONYMOUS account.

To run the apxconf.sql configuration script:

1. Change your working directory to ORACLE_BASE\ORACLE_HOME\apex or whatever convention used to indicate the Oracle home.

2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password 
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password 
     

3. Run apxconf.sql as shown in the following example:

   @apxconf
   

4. When prompted, enter a password for the Application Express Admin account.

   Be sure to make a note of the password you enter. You will use this password to log in to Oracle Application Express Administration Services.

5. When prompted, enter the port for the Oracle XML DB HTTP server. The default port number is 8080.

6. Enter the following statement to unlock the ANONYMOUS account:

   ALTER USER ANONYMOUS ACCOUNT UNLOCK;
   

4.4.2.2 Verifying the Oracle XML DB HTTP Server Port

The embedded PL/SQL gateway runs in the Oracle XML DB HTTP server in the Oracle database. You can determine if the Oracle XML DB HTTP server is enabled by verifying the associated port number.

To verify the port number where the Oracle XML DB HTTP Server is running:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

2. Enter the following statement to verify the port number:

   SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;
   

   If the port number returns 0, the Oracle XML DB HTTP Server is disabled.

3. To enable it, follow the instructions in "Enabling Oracle XML DB HTTP Server".

4.4.2.3 Enabling Oracle XML DB HTTP Server

The embedded PL/SQL gateway runs in the Oracle XML DB HTTP server in the Oracle database.

To enable Oracle XML DB HTTP server:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:

   • Windows:

     DRIVE_LETTER:\> sqlplus /nolog
     SQL> SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password 
     

   • UNIX and Linux:

     $ sqlplus /nolog
     SQL> SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password 
     

2. Run the following statements:

   EXEC DBMS_XDB.SETHTTPPORT(port);
   COMMIT;
   

   For example:

   EXEC DBMS_XDB.SETHTTPPORT(8080);
   COMMIT;
   

4.4.2.4 Disabling Oracle XML DB HTTP Server

The embedded PL/SQL gateway runs in the Oracle XML DB HTTP server in the Oracle database. To disable Oracle XML DB HTTP server:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:

   • Windows:

     DRIVE_LETTER:\> sqlplus /nolog
     SQL> SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password 
     

   • UNIX and Linux:

     $ sqlplus /nolog
     SQL> SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password 
     

2. Run the following statements:

   EXEC DBMS_XDB.SETHTTPPORT(0);
   COMMIT;
   

4.4.3.1 Granting Connect Privileges

The following example demonstrates how to grant connect privileges to any host for the APEX_030200 database user. This example assumes you connected to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role.

DECLARE
  ACL_PATH  VARCHAR2(4000);
  ACL_ID    RAW(16);
BEGIN
  -- Look for the ACL currently assigned to '*' and give APEX_030200
  -- the "connect" privilege if APEX_030200 does not have the privilege yet.

  SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
   WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;

  -- Before checking the privilege, ensure that the ACL is valid
  -- (for example, does not contain stale references to dropped users).
  -- If it does, the following exception will be raised:
  --
  -- ORA-44416: Invalid ACL: Unresolved principal 'APEX_030200'
  -- ORA-06512: at "XDB.DBMS_XDBZ", line ...
  --
  SELECT SYS_OP_R2O(extractValue(P.RES, '/Resource/XMLRef')) INTO ACL_ID
    FROM XDB.XDB$ACL A, PATH_VIEW P
   WHERE extractValue(P.RES, '/Resource/XMLRef') = REF(A) AND
         EQUALS_PATH(P.RES, ACL_PATH) = 1;

  DBMS_XDBZ.ValidateACL(ACL_ID);
   IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'APEX_030200', 
     'connect') IS NULL THEN 
      DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH, 
     'APEX_030200', TRUE, 'connect'); 
  END IF;

EXCEPTION
  -- When no ACL has been assigned to '*'.
  WHEN NO_DATA_FOUND THEN
  DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('power_users.xml',
    'ACL that lets power users to connect to everywhere',
    'APEX_030200', TRUE, 'connect');
  DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('power_users.xml','*');
END;
/
COMMIT;

The following example demonstrates how to provide less privileged access to local network resources. This example would enable indexing the Oracle Application Express Online Help and could possibly enable email and PDF printing if those servers were also on the local host.

DECLARE
  ACL_PATH  VARCHAR2(4000);
  ACL_ID    RAW(16);
BEGIN
  -- Look for the ACL currently assigned to 'localhost' and give APEX_030200
  -- the "connect" privilege if APEX_030200 does not have the privilege yet.
  SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
   WHERE HOST = 'localhost' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;

  -- Before checking the privilege, ensure that the ACL is valid
  -- (for example, does not contain stale references to dropped users).
  -- If it does, the following exception will be raised:
  --
  -- ORA-44416: Invalid ACL: Unresolved principal 'APEX_030200'
  -- ORA-06512: at "XDB.DBMS_XDBZ", line ...
  --

  SELECT SYS_OP_R2O(extractValue(P.RES, '/Resource/XMLRef')) INTO ACL_ID
    FROM XDB.XDB$ACL A, PATH_VIEW P
   WHERE extractValue(P.RES, '/Resource/XMLRef') = REF(A) AND
         EQUALS_PATH(P.RES, ACL_PATH) = 1;

  DBMS_XDBZ.ValidateACL(ACL_ID);
   IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'APEX_030200', 
     'connect') IS NULL THEN 
      DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH, 
     'APEX_030200', TRUE, 'connect'); 
  END IF;

EXCEPTION
  -- When no ACL has been assigned to 'localhost'.
  WHEN NO_DATA_FOUND THEN
  DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('local-access-users.xml',
    'ACL that lets power users to connect to everywhere',
    'APEX_030200', TRUE, 'connect');
  DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('local-access-users.xml','localhost');
END;
/
COMMIT;

4.4.3.2 Troubleshooting an Invalid ACL Error

If you receive an ORA-44416: Invalid ACL error after running the previous script, use the following query to identify the invalid ACL:

REM Show the dangling references to dropped users in the ACL that is assigned
REM to '*'.

SELECT ACL, PRINCIPAL
  FROM DBA_NETWORK_ACLS NACL, XDS_ACE ACE
 WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL AND
       NACL.ACLID = ACE.ACLID AND
       NOT EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);

Next, run the following code to fix the ACL:

DECLARE
  ACL_ID   RAW(16);
  CNT      NUMBER;
BEGIN
  -- Look for the object ID of the ACL currently assigned to '*'
  SELECT ACLID INTO ACL_ID FROM DBA_NETWORK_ACLS
   WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;

  -- If just some users referenced in the ACL are invalid, remove just those
  -- users in the ACL. Otherwise, drop the ACL completely.
  SELECT COUNT(PRINCIPAL) INTO CNT FROM XDS_ACE
   WHERE ACLID = ACL_ID AND
         EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);

  IF (CNT > 0) THEN

    FOR R IN (SELECT PRINCIPAL FROM XDS_ACE
               WHERE ACLID = ACL_ID AND
                     NOT EXISTS (SELECT NULL FROM ALL_USERS
                                  WHERE USERNAME = PRINCIPAL)) LOOP
      UPDATE XDB.XDB$ACL
         SET OBJECT_VALUE =
               DELETEXML(OBJECT_VALUE,
                         '/ACL/ACE[PRINCIPAL="'||R.PRINCIPAL||'"]')
       WHERE OBJECT_ID = ACL_ID;
    END LOOP;

  ELSE
    DELETE FROM XDB.XDB$ACL WHERE OBJECT_ID = ACL_ID;
  END IF;

END;
/

REM commit the changes.

COMMIT;

Once the ACL has been fixed, you must run the first script in this section to apply the ACL to the APEX_030200 user. See "Granting Connect Privileges".

4.4.6.1 Installing a Translated Version of Oracle Application Express

Whether you are installing for the first time or upgrading from a previous release, you must run the load_lang.sql script to run a translated version of Oracle Application Express.

The installation scripts are located in subdirectories identified by a language code in the unzipped distribution apex/builder. For example, the German version is located in apex/builder/de and the Japanese version is located in apex/builder/ja. Within each of directory, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).

To install a translated version of Oracle Application Express:

1. Set the NLS_LANG environment variable, making sure that the character set is AL32UTF8. For example:

   • Bourne or Korn shell:

     NLS_LANG=American_America.AL32UTF8
     export NLS_LANG
     

   • C shell:

     setenv NLS_LANG American_America.AL32UTF8
     

   • For Windows based systems:

     set NLS_LANG=American_America.AL32UTF8
     

2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

3. Execute the following statement:

   ALTER SESSION SET CURRENT_SCHEMA = APEX_030200;
   

4. Execute the appropriate language specific script. For example:

   @load_lang.sql
   

   Where lang is the specific language (for example, load_de.sql for German or load_ja.sql for Japanese).

4.4.7.1 Viewing the Number of JOB_QUEUE_PROCESSES

There are currently three ways to view the number of JOB_QUEUE_PROCESSES:

• In the installation log file

• On the About Application Express page in Oracle Application Express

• From SQL*Plus

SELECT VALUE FROM v$parameter WHERE NAME = 'job_queue_processes'

4.4.7.2 Changing the Number of JOB_QUEUE_PROCESSES

You can change the number of JOB_QUEUE_PROCESSES by running a SQL statement in SQL*Plus:

To update the number of JOB_QUEUE_PROCESSES:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

2. In SQL*Plus run the following SQL statement:

   ALTER SYSTEM SET JOB_QUEUE_PROCESSES = <number>
   

   For example, running the statement ALTER SYSTEM SET JOB_QUEUE_PROCESSES = 20 sets JOB_QUEUE_PROCESSES to 20.

4.4.9.1 Creating a Workspace Manually

To create an Oracle Application Express workspace manually:

1. Log in to Oracle Application Express Administration Services. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance. You log in using the ADMIN account and password created or reset during the installation process.

   1. In a Web browser, navigate to the Oracle Application Express Administration Services application.

      If your setup uses the embedded PL/SQL gateway, go to:

      http://hostname:port/apex/apex_admin
      

      Where:

      hostname is the name of the system where Oracle XML DB HTTP server is installed.

      port is the port number assigned to Oracle XML DB HTTP server. In a default installation, this number is 8080.

      apex is the database access descriptor (DAD) defined in the configuration file.

   2. On the Login page:

      • In Username, enter admin.

      • In Password, enter the Oracle Application Express administrator account password you specified when you installed Oracle Application Express.

      • Click Login.

   See Also:

   See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.

   Next, create a workspace.

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Create Workspace.

   The Create Workspace Wizard appears.

4. For Identify Workspace, enter a workspace name and description and click Next.

5. For Identify Schema, select the Oracle Forms application schema.

   1. For Re-use existing schema, select Yes.

   2. Select a schema from the list.

   3. Click Next.

6. For Identify Administrator, enter the Workspace administrator information and click Next.

7. Confirm your selections and click Create.

4.4.9.2 Creating Oracle Application Express Users

To create an Oracle Application Express user account:

1. Log in to Oracle Application Express Administration Services as described in the previous section. See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Manage Developers and Users.

   The Manage Developers and Users page appears.

4. Click Create.

   The Create/Edit User page appears.

5. Under User Attributes, enter the appropriate information. Fields marked with an asterisk are required.

   Tip:

   To learn more about a specific attribute, click the item label. When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark.

6. Under Password, type a case-sensitive password for this account.

   If your organization has set up a password policy, be sure the password meets the requirements.

7. Under Developer Privileges, select the appropriate privileges:

   • User is a developer - To add this user as a developer or Workspace administrator, select Yes. For end users, select No.

     Developers can create and modify applications and database objects as well as view developer activity, session state, workspace activity, application, and schema reports.

   • User is a workspace administrator - To add this user as a Workspace administrator, select Yes. For developers or end users, select No.

     In addition to having developer privileges, workspace administrators can create and edit user accounts, manage groups, alter passwords of users within the same workspace, and manage development services.

8. Under Account Control, specify the following:

   • Account Availability - Select Unlocked to enable a user to log in to this account.

   • Require Change of Password on First Use - Select Yes to require the user to change the password immediately after logging in with the current, temporary password. Otherwise, select No.

9. Click Create User or Create and Create Another.

4.4.9.3 Logging in to Your Oracle Application Express Workspace

Once you create a workspace, you must log in to it using your login credentials (that is, the workspace name, user name, and password).

To log in to a workspace:

1. In a Web browser, navigate to the Oracle Application Express Login page.

   If your setup uses the embedded PL/SQL gateway, go to:

   http://hostname:port/apex
   

   Where:

   • hostname is the name of the system where Oracle XML DB HTTP server is installed.

   • port is the port number assigned to Oracle XML DB HTTP server. In a default installation, this number is 8080.

   • apex is the database access descriptor (DAD) defined in the configuration file.

     For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.

   The Login page appears.

2. Under Login, enter the following:

   • Workspace field - Enter the name of your workspace.

   • Username field - Enteryour user name.

   • Password field - Enter your case-sensitive password.

3. Click Login.

   Note that, depending on your setup, you might be required to change your password when you log in for the first time.

4.5.2.1 Change the Password for the ADMIN Account

First, change the password for the Oracle Application Express ADMIN account.

To change the password for the ADMIN account:

1. Change your working directory to ORACLE_BASE\ORACLE_HOME\apex or whatever convention used to indicate the Oracle home.

2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

3. Run apxchpwd.sql. For example:

   @apxchpwd.sql
   

   When prompted enter a password for the ADMIN account.

4.5.2.2 Unlock the APEX_PUBLIC_USER Database User

When configuring Oracle HTTP Server for Oracle Application Express in a new installation, the database user APEX_PUBLIC_USER must be an unlocked account. To unlock the account for database user APEX_PUBLIC_USER, execute the following steps:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

2. Run the following statement:

   ALTER USER APEX_PUBLIC_USER ACCOUNT UNLOCK
   

4.5.2.3 Change the Password for the APEX_PUBLIC_USER Database User

In order to specify the password in the DAD file, you have to change the password for the database user APEX_PUBLIC_USER. Please use the following steps to change the password for the APEX_PUBLIC_USER database user:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

2. Run the following statement:

   SQL> PASSWORD APEX_PUBLIC_USER
   Changing password for APEX_PUBLIC_USER
   New password: password
   Retype new password: password
   

4.5.2.4 Copy the Images Directory

Whether you are loading a new installation or upgrading from a previous release, you must copy the images directory from the top level of the apex\images directory to the location on the file system containing the Oracle home for Oracle HTTP Server.

Topics in this section include:

• Copying the Images Directory After an Upgrade

• Copying the Images Directory in a New Installation

DRIVE_LETTER:\> xcopy /E /I ORACLE_HOME\apex\images ORACLE_HTTPSERVER_HOME\ohs\images

4.5.2.5 Configure Oracle HTTP Server 11g or Oracle Application Server 10g

Perform the following postinstallation steps if:

• You are running Oracle HTTP Server distributed with Oracle Database 11g or Oracle Application Server 10g.

• Oracle HTTP Server is installed in an Oracle home.

Note that these instructions do not apply if you are running Oracle HTTP Server release 9.0.3. To learn more, see "Configuring Oracle HTTP Server Distributed with Oracle9i Release 2".

Topics in this section include:

• Editing the dads.conf File

• Stopping and Restarting Oracle HTTP Server

ORACLE_BASE\ORACLE_HTTPSERVER_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server
ORACLE_BASE\ORACLE_HTTPSERVER_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server

4.5.3.1 Granting Connect Privileges

The following example demonstrates how to grant connect privileges to any host for the APEX_030200 database user. This example assumes you connected to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role.

DECLARE
  ACL_PATH  VARCHAR2(4000);
  ACL_ID    RAW(16);
BEGIN
  -- Look for the ACL currently assigned to '*' and give APEX_030200
  -- the "connect" privilege if APEX_030200 does not have the privilege yet.

  SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
   WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;

  -- Before checking the privilege, ensure that the ACL is valid
  -- (for example, does not contain stale references to dropped users).
  -- If it does, the following exception will be raised:
  --
  -- ORA-44416: Invalid ACL: Unresolved principal 'APEX_030200'
  -- ORA-06512: at "XDB.DBMS_XDBZ", line ...
  --
  SELECT SYS_OP_R2O(extractValue(P.RES, '/Resource/XMLRef')) INTO ACL_ID
    FROM XDB.XDB$ACL A, PATH_VIEW P
   WHERE extractValue(P.RES, '/Resource/XMLRef') = REF(A) AND
         EQUALS_PATH(P.RES, ACL_PATH) = 1;

  DBMS_XDBZ.ValidateACL(ACL_ID);
   IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'APEX_030200', 
     'connect') IS NULL THEN 
      DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH, 
     'APEX_030200', TRUE, 'connect'); 
  END IF;

EXCEPTION
  -- When no ACL has been assigned to '*'.
  WHEN NO_DATA_FOUND THEN
  DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('power_users.xml',
    'ACL that lets power users to connect to everywhere',
    'APEX_030200', TRUE, 'connect');
  DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('power_users.xml','*');
END;
/
COMMIT;

The following example demonstrates how to provide less privileged access to local network resources. This example would enable indexing the Oracle Application Express Online Help and could possibly enable email and PDF printing if those servers were also on the local host.

DECLARE
  ACL_PATH  VARCHAR2(4000);
  ACL_ID    RAW(16);
BEGIN
  -- Look for the ACL currently assigned to 'localhost' and give APEX_030200
  -- the "connect" privilege if APEX_030200 does not have the privilege yet.
  SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
   WHERE HOST = 'localhost' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;

  -- Before checking the privilege, ensure that the ACL is valid
  -- (for example, does not contain stale references to dropped users).
  -- If it does, the following exception will be raised:
  --
  -- ORA-44416: Invalid ACL: Unresolved principal 'APEX_030200'
  -- ORA-06512: at "XDB.DBMS_XDBZ", line ...
  --

  SELECT SYS_OP_R2O(extractValue(P.RES, '/Resource/XMLRef')) INTO ACL_ID
    FROM XDB.XDB$ACL A, PATH_VIEW P
   WHERE extractValue(P.RES, '/Resource/XMLRef') = REF(A) AND
         EQUALS_PATH(P.RES, ACL_PATH) = 1;

  DBMS_XDBZ.ValidateACL(ACL_ID);
   IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'APEX_030200', 
     'connect') IS NULL THEN 
      DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH, 
     'APEX_030200', TRUE, 'connect'); 
  END IF;

EXCEPTION
  -- When no ACL has been assigned to 'localhost'.
  WHEN NO_DATA_FOUND THEN
  DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('local-access-users.xml',
    'ACL that lets power users to connect to everywhere',
    'APEX_030200', TRUE, 'connect');
  DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('local-access-users.xml','localhost');
END;
/
COMMIT;

4.5.3.2 Troubleshooting an Invalid ACL Error

If you receive an ORA-44416: Invalid ACL error after running the previous script, use the following query to identify the invalid ACL:

REM Show the dangling references to dropped users in the ACL that is assigned
REM to '*'.

SELECT ACL, PRINCIPAL
  FROM DBA_NETWORK_ACLS NACL, XDS_ACE ACE
 WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL AND
       NACL.ACLID = ACE.ACLID AND
       NOT EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);

Next, run the following code to fix the ACL:

DECLARE
  ACL_ID   RAW(16);
  CNT      NUMBER;
BEGIN
  -- Look for the object ID of the ACL currently assigned to '*'
  SELECT ACLID INTO ACL_ID FROM DBA_NETWORK_ACLS
   WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;

  -- If just some users referenced in the ACL are invalid, remove just those
  -- users in the ACL. Otherwise, drop the ACL completely.
  SELECT COUNT(PRINCIPAL) INTO CNT FROM XDS_ACE
   WHERE ACLID = ACL_ID AND
         EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);

  IF (CNT > 0) THEN

    FOR R IN (SELECT PRINCIPAL FROM XDS_ACE
               WHERE ACLID = ACL_ID AND
                     NOT EXISTS (SELECT NULL FROM ALL_USERS
                                  WHERE USERNAME = PRINCIPAL)) LOOP
      UPDATE XDB.XDB$ACL
         SET OBJECT_VALUE =
               DELETEXML(OBJECT_VALUE,
                         '/ACL/ACE[PRINCIPAL="'||R.PRINCIPAL||'"]')
       WHERE OBJECT_ID = ACL_ID;
    END LOOP;

  ELSE
    DELETE FROM XDB.XDB$ACL WHERE OBJECT_ID = ACL_ID;
  END IF;

END;
/

REM commit the changes.

COMMIT;

Once the ACL has been fixed, you must run the first script in this section to apply the ACL to the APEX_030200 user. See "Granting Connect Privileges".

4.5.6.1 Installing a Translated Version of Oracle Application Express

Whether you are installing for the first time or upgrading from a previous release, you must run the load_lang.sql script to run a translated version of Oracle Application Express.

The installation scripts are located in subdirectories identified by a language code in the unzipped distribution apex/builder. For example, the German version is located in apex/builder/de and the Japanese version is located in apex/builder/ja. Within each of directory, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).

To install a translated version of Oracle Application Express:

1. Set the NLS_LANG environment variable, making sure that the character set is AL32UTF8. For example:

   • Bourne or Korn shell:

     NLS_LANG=American_America.AL32UTF8
     export NLS_LANG
     

   • C shell:

     setenv NLS_LANG American_America.AL32UTF8
     

   • For Windows based systems:

     set NLS_LANG=American_America.AL32UTF8
     

2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

3. Execute the following statement:

   ALTER SESSION SET CURRENT_SCHEMA = APEX_030200;
   

4. Execute the appropriate language specific script. For example:

   @load_lang.sql
   

   Where lang is the specific language (for example, load_de.sql for German or load_ja.sql for Japanese).

4.5.7.1 Viewing the Number of JOB_QUEUE_PROCESSES

There are currently three ways to view the number of JOB_QUEUE_PROCESSES:

• In the installation log file

• On the About Application Express page in Oracle Application Express

• From SQL*Plus

SELECT VALUE FROM v$parameter WHERE NAME = 'job_queue_processes'

4.5.7.2 Changing the Number of JOB_QUEUE_PROCESSES

You can change the number of JOB_QUEUE_PROCESSES by running a SQL statement in SQL*Plus:

To update the number of JOB_QUEUE_PROCESSES:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

2. In SQL*Plus run the following SQL statement:

   ALTER SYSTEM SET JOB_QUEUE_PROCESSES = <number>
   

   For example, running the statement ALTER SYSTEM SET JOB_QUEUE_PROCESSES = 20 sets JOB_QUEUE_PROCESSES to 20.

4.5.8.1 Obfuscating Passwords

To obfuscate passwords, run dadTool.pl by following the instructions in the dadTool.README file.

4.5.9.1 Creating a Workspace Manually

To create an Oracle Application Express workspace manually:

1. Log in to Oracle Application Express Administration Services. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance. You log in using the ADMIN account and password created or reset during the installation process.

   If your setup uses Apache and mod_plsql, go to:

   http://hostname:port/pls/apex/apex_admin
   

   Where:

   hostname is the name of the system where Oracle HTTP Server is installed.

   port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777.

   pls is the indicator to use the mod_plsql cartridge.

   apex is the database access descriptor (DAD) defined in the mod_plsql configuration file.

   See Also:

   See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.

   Next, create a workspace.

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Create Workspace.

   The Create Workspace Wizard appears.

4. For Identify Workspace, enter a workspace name and description and click Next.

5. For Identify Schema, select the Oracle Forms application schema.

   1. For Re-use existing schema, select Yes.

   2. Select a schema from the list.

   3. Click Next.

6. For Identify Administrator, enter the Workspace administrator information and click Next.

7. Confirm your selections and click Create.

4.5.9.2 Creating Oracle Application Express Users

To create an Oracle Application Express user account:

1. Log in to Oracle Application Express Administration Services as described in the previous section. See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Manage Developers and Users.

   The Manage Developers and Users page appears.

4. Click Create.

   The Create/Edit User page appears.

5. Under User Attributes, enter the appropriate information. Fields marked with an asterisk are required.

   Tip:

   To learn more about a specific attribute, click the item label. When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark.

6. Under Password, type a case-sensitive password for this account.

   If your organization has set up a password policy, be sure the password meets the requirements.

7. Under Developer Privileges, select the appropriate privileges:

   • User is a developer - To add this user as a developer or Workspace administrator, select Yes. For end users, select No.

     Developers can create and modify applications and database objects as well as view developer activity, session state, workspace activity, application, and schema reports.

   • User is a workspace administrator - To add this user as a Workspace administrator, select Yes. For developers or end users, select No.

     In addition to having developer privileges, workspace administrators can create and edit user accounts, manage groups, alter passwords of users within the same workspace, and manage development services.

8. Under Account Control, specify the following:

   • Account Availability - Select Unlocked to enable a user to log in to this account.

   • Require Change of Password on First Use - Select Yes to require the user to change the password immediately after logging in with the current, temporary password. Otherwise, select No.

9. Click Create User or Create and Create Another.

4.5.9.3 Logging in to Your Oracle Application Express Workspace

Once you create a workspace, you must log in to it using your login credentials (that is, the workspace name, user name, and password).

To log in to a workspace:

1. In a Web browser, navigate to the Oracle Application Express Login page. By default, Oracle Application Express installs to the following location:

   If your setup uses Oracle HTTP Server (Apache) and mod_plsql, go to:

   http://hostname:port/pls/apex
   

   Where:

   • hostname is the name of the system where Oracle HTTP Server is installed.

   • port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. You can find information about your Oracle HTTP Server installation's port number from either of the following files:

     ORACLE_BASE\ORACLE_HOME\install\portlist.ini
     ORACLE_BASE\ORACLE_HTTPSERVER_HOME\Apache\Apache\conf\httpd.conf
     

     Be aware that if you change a port number, it is not updated in the portlist.ini file. You can only rely on this file immediately after installation.

   • pls is the indicator to use the mod_plsql cartridge.

   • apex is the database access descriptor (DAD) defined in the mod_plsql configuration file.

     For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.

   The Login page appears.

2. Under Login, enter the following:

   • Workspace field - Enter the name of your workspace.

   • Username field - Enteryour user name.

   • Password field - Enter your case-sensitive password.

3. Click Login.

   Note that, depending on your setup, you might be required to change your password when you log in for the first time.

4.6.1.1 Verify if Prior Installation Exist

To verify if prior installations exist:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password 
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password 
     

2. Run the following query:

   SELECT username
      FROM dba_users 
    WHERE (username LIKE 'FLOWS_%' OR USERNAME LIKE 'APEX_%') 
      AND USERNAME NOT IN (
           SELECT 'FLOWS_FILES' 
             FROM DUAL 
            UNION 
           SELECT 'APEX_PUBLIC_USER' FROM DUAL 
            UNION
           SELECT SCHEMA s 
              FROM dba_registry
            WHERE comp_id = 'APEX');
   

If the results contain entries in the form FLOWS_XXXXXX or APEX_XXXXXX where XXXXXX represents six numbers, those entries are candidates for removal.

4.6.1.2 Remove Schemas from Prior Installations

To remove schemas from prior installations:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:

   • On Windows:

     SYSTEM_DRIVE:\ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

   • On UNIX and Linux:

     $ sqlplus /nolog
     SQL> CONNECT SYS as SYSDBA
     Enter password: SYS_password
     

2. Execute a statement connected similar to the following example:

   DROP USER FLOWS_030000 CASCADE;