Oracle® HTML DB

Create a marvel.conf File

If you have not previously configured Oracle HTTP Server to work with Oracle HTML DB, you need to create a marvel.conf file.

To create the marvel.conf file:

1. Use a text editor and create a file named marvel.conf.

   • For UNIX and Linux based systems, save to:

     ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf
     
     

   • For Windows based systems, save to:

     ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\
     
     

2. Copy the following into the marvel.conf file. Replace ORACLE_HOME, host, port, service_name, and htmldb_public_user_password with values appropriate for your environment.

   The following example assumes you specified the image directory alias as /i/ when you installed HTML DB. Note that the path listed is only an example. The path in your marvel.conf file should reference the images directory alias for your environment.

   Alias /i/ "ORACLE_BASE/ORACLE_HOME/htmldb/images/"
   AddType text/xml       xbl
   AddType text/x-component       htc
   
   <Location /pls/htmldb>
    Order deny,allow
    PlsqlDocumentPath docs
    AllowOverride None
    PlsqlDocumentProcedure      wwv_flow_file_manager.process_download
    PlsqlDatabaseConnectString  host:port:service_name ServiceNameFormat
    PlsqlNLSLanguage            AMERICAN_AMERICA.AL32UTF8
    PlsqlAuthenticationMode     Basic
    SetHandler                  pls_handler
    PlsqlDocumentTablename      wwv_flow_file_objects$
    PlsqlDatabaseUsername       HTMLDB_PUBLIC_USER
    PlsqlDefaultPage            htmldb
    PlsqlDatabasePassword       htmldb_public_user_password
    Allow from all
   </Location>
   
   

3. Save and exit the marvel.conf file.

Edit the httpd.conf File

Next, you need to edit the httpd.conf file to reference the marvel.conf configuration file.

To edit the httpd.conf file:

1. Use a text editor and open the httpd.conf file.

   • For UNIX and Linux based systems:

     ORACLE_BASE/ORACLE_HOME/Apache/Apache/conf/httpd.conf
     
     

   • For Windows based systems:

     ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\httpd.conf
     
     

2. Add an entry to reference the marvel.conf configuration file.

   include "ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf/marvel.conf"
   
   

3. Save and exit the httpd.conf file.

Stop and Restart Oracle HTTP Server

To stop and restart Oracle HTTP Server:

• For UNIX and Linux based systems, execute the following commands:

  ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
  ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
  
  

• For Windows based system, execute the following commands:

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

SQL Injection Analysis Reports

A SQL Injection analysis report is available in Oracle HTML DB 2.0, in the SQL Workshop Utilities. This feature enables you to compile PL/SQL functions, procedures and packages for analysis of SQL Injection vulnerabilities. Potential SQL Injection vulnerabilities can then be reviewed in the accompanying reports.

This feature is only available with Oracle Database 10g release 2 (10.2) or later. Additionally, this feature requires the installation of additional PL/SQL packages (DBMS_GLOBAL_DATAFLOW and DBMS_SQL_INJECTION_ANALYZER) which are not distributed with Database 10g release 2 (10.2.0.1). These required packages may be distributed by Oracle at a later date.

Session IDs Required in f?p URLs

In earlier releases of Oracle HTML DB, when a previously authenticated user attempted to use a link to an application that did not contain a session ID, the HTML DB engine would check if the user's browser had a session cookie that located a valid session for the link. If the HTML DB engine found a session cookie and located a valid session, the user could access the application using that session. Similarly, if an authenticated user attempted to use a link to the application and the link session ID did not match the current session, the user would still be allowed to access the page because of the presence of the session cookie for the currently authenticated session.

In Oracle HTML DB 2.0, page requests do not contain a session ID. If a session ID does not match the current session, the user will have to be repeat the authentication process, after which a new session will be assigned. Because of this change, you may notice changes in the way bookmarked links work. For example, the use of bookmarked links to pages that require authentication may result in the user being required to repeat the authentication process to the application.

As a best practice, developers should take special care to construct internal links between application pages so that they always contain the current session ID, using &APP_SESSION., v('APP_SESSION'), :APP_SESSION, or equivalent methods appropriate for the context in which the links are constructed.

Supported Web Browsers

To view or develop Oracle HTML DB applications, Web browsers must support JavaScript and the HTML 4.0 and CSS 1.0 standards. The following browsers meet this requirement:

• Microsoft Internet Explorer 6.0 or higher (Windows only)

• Netscape Communicator 7.2 or higher

• Mozilla 1.2 or higher

• Firefox 1.0 or higher

Importing Spreadsheet Data Containing Quotation Marks

If you import spreadsheet data by copying and pasting and a column value contains a double quotation mark, the data will not import correctly (for example, 54" Plasma Flat Screen). To avoid this problem, you have two options:

• Option 1:

  1. Save the data in a delimited format (such as comma-delimited (.csv) or tab-delimited).

  2. Use Import Text Data wizard to upload and import the saved file.

• Option 2:

  1. Replace the quotation mark with two double quotation marks as shown in the following example:

     54"" Plasma Flat Screen
     
     

  2. Use the Import Spreadsheet Data wizard to import the file.

Column Attribute Format in Japanese

When you open the number or date format select popup dialog on the Column Attribute of a Page Definition in Application Builder, it always displays 'backslash'+ 5,234.10 in the dialog. It is expected that the symbol of 'yen' displays accurately in a Japanese environment.

Note that backslash and yen are the same character code point, but display differently depending on the selected font. Backslash is also displayed when applying the data format on the page in the application.

This issue is tracked with Oracle bug 3384664.

Creating an Item with a Japanese Item Name

If you create a form on a table or view based on an included column whose name is in Japanese using a wizard, the name of the new item will be included in Japanese.

This issue is tracked with Oracle bug 3393090.

Workaround:

To correct this problem, when you create new items on the Page Definition use alphanumeric characters A_Z, 0-9 and '_' for the item names. You may also need to changes item names to alphanumeric before you apply changes to the item.

Runtime Errors in an Application Imported from a Previous Release

If you export an application from an earlier Oracle HTML DB release and then import and install it using the installation pages in Application Builder, in rare situations you may encounter runtime errors after the application installs.

These errors often manifest themselves as PL/SQL parser or execution errors pertaining to blocks of PL/SQL code embedded within application components. The installation process sometimes splits strings greater than 200 characters into multiple lines. For example, lines may split between PL/SQL keywords, or at other places that cause parsing errors.

This issue is tracked with Oracle bug 3854874.

Workaround:

If you encounter these types of errors and suspect the installation process has split large strings:

1. Isolate the failing component containing the suspect PL/SQL within the application by editing the failing page in Application Builder.

2. Locate the blocks of code that appear to split incorrectly.

3. Attempt to split the blocks of code in more appropriate places, or insert white space with the lines until no runtime errors are observed.

4. Export the application, import the export file, and then reinstall it.

5. Retain the new export file as a permanent backup copy.

Creating a Web Reference on a WSDL that Has Input Parameters Defined as Arrays

If you create a Web service reference in Oracle HTML DB on a WSDL document that has input parameters defined as arrays, you will not be able to use built-in wizards to create a form or a form and report on that Web reference.

This issue is tracked with Oracle bug 3922270.

Workaround:

Oracle HTML DB does not provide a user interface for input parameters that are arrays. Output parameters that are defined as arrays are handled properly if you use the Form and Report on Web Service Wizard.

No Support for Corel SVG Viewer

Oracle HTML DB release 2.0 does not support the Corel SVG Viewer.

Enabling Triggers from within Object Browser

You cannot enable triggers from within Object Browser.

This issue is tracked with Oracle bug 4563602.

Workaround:

Use SQL Command Processor and enable triggers using standard Oracle syntax. For example:

ALTER TRIGGER trigger_name ENABLE

Downloading Triggers with Multibyte Names

If you download a trigger with a multibyte name from the Object Details view in Object Browser, the file name becomes corrupt.

This issue is tracked with Oracle bug 4581512.

Workaround:

Download triggers with multibyte names from the Code view.

Granting Specific Privileges on Materialized Views and Packages

You cannot grant specific privileges on materialized views and packages in Object Browser.

This issue is tracked with Oracle bug 4578016.

Workaround:

Grant a specific privilege on a Materialized view or package using standard Oracle syntax. For example:

GRANT SELECT ON materialized_view TO user

Creating Triggers Using Existing Names in Object Browser

You cannot create a trigger in Object Browser if the name already exists even if it contains different capitalization (for example, TRIGGER1 and trigger1).

This issue is tracked with Oracle bug 4578658.

Workaround:

Use SQL Command Processor to create a trigger using standard Oracle syntax. For example:

CREATE TRIGGER "trigger1" BEFORE INSERT ON ...

Exporting a SQL Script Always Includes the First Script File

Exporting SQL scripts using the Add to Export button always includes the first script regardless of whether it is currently selected.

This issue is tracked with Oracle bug 4583602.

Workaround:

To address this issue:

1. Select all scripts and click Add to Export.

2. Then, select those you do not wish to export and click Remove Checked.

Generate DDL Utility Corrupts Some Multibyte Table and Columns Names

In some character sets, multibyte table and columns names are corrupted when generating DDL.

This issue is tracked with Oracle bug 4579524.

Workaround:

Use the SQL view in Object Browser to create the DDL for any object that is corrupted by the Generate DDL utility.

Unsupported Commands in SQL Command Processor

SQL Command Processor does not support the SQL commands EXPLAIN PLAN and LOCK TABLE.

This issue is tracked with Oracle bug 4552205.

Workaround:

Use SQL*Plus or another SQL client to perform these actions.

Sorting Mixed Case Columns in a Query in Object Browser

The Query function in Object Browser does not currently support sorting of lower case or mixed case column names. If you are using the Query function in Object Browser, your table has mixed case or lower case column names, and you select a column to be used as an order by, the select fails.

This issue is tracked with Oracle bug 4601878.

Workaround:

Use the Query Builder to create and run your query.

Disabling Constraints Having Mixed Case or Lower Case Names

If you select a table in Object Browser, select the Constraints tab, and then attempt to disable a constraint whose name contains lower or mixed case letters, the disable will fail.

This issue is tracked with Oracle bug 4601636.

Workaround:

Use SQL Command Processor to disable or enable using standard Oracle syntax. For example:

ALTER CONSTRAINT "Constraint_Abc" DISABLE

No Support in Object Browser to Create an 'UPDATE OF' Trigger for Tables Having Lower or Mixed Case Names

Object Browser does not support the creation of "UPDATE OF" triggers for tables having lower or mixed case names. To create a trigger in Object Browser, you can either:

• Select a table, select the Triggers tab, and then click Create.

• Click Create in the upper right of Object Browser and select Trigger.

  If you set Options to update of, you will be prompted to select a column but the columns for lower or mixed case table names will not display.

This issue is tracked with Oracle bug 4601883.

Workaround:

Use SQL Command Processor to create the trigger using standard Oracle syntax. For example:

CREATE TRIGGER "Mixed_Case_Trigger" 
BEFORE 
UPDATE OF "Mixed_Column" ON "Mixed_Case_Table"
FOR EACH ROW
BEGIN
...

Oracle HTML DB Installation Guide Additions and Corrections

This section lists corrections in the Oracle HTML DB Installation Guide.

• The procedure described in "Configuring Oracle HTTP Server in a New Installation" was not included in the production version of the Oracle HTML DB Installation Guide.

• In section 2.5, "Oracle Text Requirement" the example that explains how to run the language preferences script for US English, drdefus.sql should read as follows:

  c:\> sqlplus ctxsys/CTXSYS_password
  SQL> @c:\oracle\product\10.2.0\db_1\ctx\admin\defaults\drdefus.sql
  
  

Oracle HTML DB User's Guide Corrections

This section lists corrections in the Oracle HTML DB User's Guide.

• In "What's New in Oracle HTML DB?" the following text is incorrect:

  "Use Object Browser to browse, create, and edit objects in multiple schemas in a single database. Object Browser includes a new PL/SQL editor. You can use this editor to edit and compile packages, procedures, functions, and triggers while taking advantage of syntax highlighting and error reporting."

  Syntax highlighting is not a feature of the PL/SQL editor in Object Browser.

• The section "About Transactions in the SQL Command Processor" explains that the user can specify the maximum amount of time a transactional command in the SQL Command Processor waits before timing out by configuring the system preference, SQL_COMMAND_MAX_INACTIVITY. This preference has been renamed SQL Commands Maximum Inactivity in minutes.