A Oracle Application Express Troubleshooting

This appendix contains information on troubleshooting.

This chapter contains these topics:

Reviewing a Log of an Installation Session
Cleaning Up After a Failed Installation
Images Displaying Incorrectly in Oracle Application Express
Online Help Not Working

A.1 Reviewing a Log of an Installation Session

The apexins.sql script creates a log file in the apex directory using the naming convention installYYYY-MM-DD_HH24-MI-SS.log. In a successful installation, the log file contains the following text:

Thank you for installing Oracle Application Express.
Oracle Application Express is installed in the FLOWS_020200 schema.

If the log file contains a few errors, it does not mean that your installation failed. Note that acceptable errors are noted as such in the log file.

A.2 Cleaning Up After a Failed Installation

In a successful installation the following banner displays at the end of the installation:

Thank you for installing Oracle Application Express.
Oracle Application Express is installed in the FLOWS_020200 schema.

To reinstall, you need to drop either one or two database schemas, depending upon the installation type.

A.2.1 After a Failed Upgrade Installation

In the case of a failed upgrade installation, you need to revert Oracle Application Express to a previous release and then remove the schemas associated with release 2.2.

A.2.1.1 Reverting to Previous Release

To revert to a previous Oracle Application Express release:

If you altered your images directory, you need to point the text alias /i/ back to images directory for release 1.5. See "Copying the Images Directory When Upgrading".

Execute the following command in SQL*Plus:

Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS or SYSTEM. For example:
```
c:\> sqlplus sys/SYS_password as sysdba
```

To revert to Oracle Application Express release 1.5, execute the following:

ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010500;
exec flows_010500.wwv_flow_upgrade.switch_schemas
('FLOWS_020200','FLOWS_010500');

To revert to Oracle Application Express release 1.6, execute the following:

ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010600;
exec flows_010600.wwv_flow_upgrade.switch_schemas
('FLOWS_020200','FLOWS_010600');

To revert to Oracle Application Express release 2.0, execute the following:

ALTER SESSION SET CURRENT_SCHEMA = FLOWS_020000;
exec flows_020000.wwv_flow_upgrade.switch_schemas
('FLOWS_020200','FLOWS_020000');

To remove the release 2.2 schema:

Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS or SYSTEM.
Execute the following commands:
```
DROP user FLOWS_020200 CASCADE;
```

A.2.2 After a Failed New Installation

To remove schemas after a failed new installation:

Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS or SYSTEM.

Execute the following commands:

drop user FLOWS_020200 cascade;
drop user FLOWS_FILES cascade;

A.3 Images Displaying Incorrectly in Oracle Application Express

In "Configuring Oracle HTTP Server in a New Installation", you added an alias entry that points to the file system path where you copied the images directory. If images in Oracle Application Express do not display correctly, you may have more than one definition of the /i/ alias. To address this issue:

If possible, rename the first instance of /i/ to a different alias name.
Alternatively, copy the images from the ORACLE_BASE\ORACLE_HOME\marvel\images directory to the directory defined by the first /i/ alias.

A.4 Online Help Not Working

If users are accessing Oracle Application Express through a Virtual Host, online Help will not work. Consider the following example:

The hostname of the Oracle HTTP Server where the Oracle Application Express DAD resides is internal.server.com and the port is 7777.
Users access Oracle Application Express through a Virtual Host. In their Web browsers, users see external.server.com and port 80.

In this example, Oracle Application Express online Help will not work if the users cannot access internal.server.com. To resolve this issue, add the following lines to the Oracle Application Express Database Access Descriptor (DAD) to override the CGI environment variables SERVER_NAME and SERVER_PORT:

PlsqlCGIEnvironmentList SERVER_NAME=external.server.com
PlsqlCGIEnvironmentList SERVER_PORT=80