This appendix contains information on troubleshooting.
This chapter contains these topics:
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_030000 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.
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_030000 schema.
To reinstall, you need to drop either one or two database schemas, depending upon the installation type.
Topics in this section include:
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 3.0.
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 After an Upgrade".
Execute the following command in SQL*Plus:
Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS. For example:
SYSTEM_DRIVE:\ 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_030000','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_030000','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_030000','FLOWS_020000');
To revert to Oracle Application Express release 2.2, execute the following:
ALTER SESSION SET CURRENT_SCHEMA = FLOWS_020200;
exec flows_020200.wwv_flow_upgrade.switch_schemas
('FLOWS_030000','FLOWS_020200');
To remove the release 3.0 schema:
Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS. For example:
SYSTEM_DRIVE:\ sqlplus sys/SYS_password as sysdba
Execute the following commands:
DROP user FLOWS_030000 CASCADE;
To remove schemas after a failed new installation:
Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS. For example:
SYSTEM_DRIVE:\ sqlplus sys/SYS_password as sysdba
Execute the following commands:
drop user FLOWS_030000 cascade; drop user FLOWS_FILES cascade;
This section describes how to remove the Oracle Application Express schema, synonyms, and users from the database without deleting the database. If you are going to delete the database, then you do not need to complete these steps.
Note:
Do not follow these steps if you have upgraded your database from a prior release, and still want to use the prior release of Oracle Application Express. This script will determine if a prior release is installed, and will not drop theFLOWS_FILES or APEX_PUBLIC_USER user if a prior release is installed. For information about reverting to a prior release, see "A.2.1.1 Reverting to Previous Release" section of Oracle Database Installation Guide.To remove Oracle Application Express from the database:
Change your working directory to the apex directory where you unzipped the Application Express software.
Start SQL*Plus and connect to the database as the privileged user SYS, for example:
SYSTEM_DRIVE:\sqlplus sys/SYSpassword as sysdba
Execute the following command:
SQL> @apxremov.sql
In "About Configuring Oracle HTTP Server", 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\apex\images directory to the directory defined by the first /i/ alias.
This section describes issues
Topics in this section include:
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
See Also:
Oracle HTTP Server mod_plsql User's Guide for information on overriding the CGI environment variables and "Oracle Text Requirement"The underlying index that enables search capability in Oracle Application Express online Help is created upon first use. Note that this index must be created over a non-SSL link. If your connection is an SSL link, https displays in the URL. To index online help, access Oracle Application Express over a non-SSL link. Once the online Help index is created, you can revert to normal https access.