|
|
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|
| Oracle9i Forms Developer and Forms Services Release 9.0.2 |
|
April 2002
This document summarizes updates to Oracle9i Forms Developer and Oracle9iAS Forms Services:
You can also obtain the latest edition of these Release Notes and other Oracle9i Forms production information at:
http://otn.oracle.com/docs/products/forms/content.html.
This section describes general issues and their workarounds for Oracle 9i Forms Developer and Oracle9iAS Forms Services.
With Oracle9i Forms, Oracle no longer ships the Open Client Adaptor (OCA) for accessing databases through ODBC rather than SQL*Net. The stated replacement for OCA is to use the Oracle Transparent Gateways as a way to access data in databases such as Microsoft SQL Server or IBM DB2. In the initial releases of Forms 9i, however, we cannot support access via the transparent gateways due to the lack of support in the gateways for "Select For Update" to enable row level locking. This deficiency will be addressed in a future release of Oracle Forms.
(2258527) The following excerpt is in Chapter 3 of the Oracle9iAS Forms Services Deployment Guide Release 9.0.2:
"If you are using the test certificate supplied with Oracle9iAS for test purposes, you must edit the JInitiator certdb.txt file and append the contents of the demo root certificate, which is located in <9iAS oracle_home/Apache/Apache/conf/ssl.crt/demoCAcert.txt."
The demoCAcert.txt file no longer exists. If you are running with Oracle9iAS Web Cache enabled (which is usually the case), you should use the file <9iAS oracle_home>/webcache/wallets/default/b60certificate.txt instead. If you are not running with Web Cache (that is, you are accessing the Oracle HTTP Server directly) you will need to create the demo root certificate file as follows:
Once you have the required certificate file, you should follow the instructions in the Oracle9iAS Forms Services Deployment Guide to configure JInitiator to use the certificate (appending it to JInitiator's certdb.txt file).
(2275360) In the Online Help, F1 links to obsolete built-ins, properties, triggers, and constants give the following error message "FRM-10063: Cannot find the help file or help file is damaged". This error occurs because obsolete information has been removed from the help system. See Oracle9i Forms Developer and Forms Services: Migrating Forms Applications from Forms6i, part number A92183-01, for migration and obsolescence information.
(2205868)You can download the latest JDAPI Javadoc from:
http://otn.oracle.com/docs/products/forms/content.html.
You can download the latest XMLTOOLS Javadoc from:
http://otn.oracle.com/docs/products/forms/content.html.
You can download the latest graphical user interface (GUI) version of the Migration Tool at:
http://otn.oracle.com/software/products/forms/content.html.
Documentation for the GUI version of the Migration Tool is available at:
http://otn.oracle.com/docs/products/forms/content.html.
This section describes configuration issues and their workarounds for Oracle 9i Forms Developer and Oracle9iAS Forms Services.
(2266745) Graphics, such as a chart, may not appear when a Form runs. As a workaround, modify the g90runm.sh to set TK_PRINTER to the actual $PRINTER value.
(2298868) The PATH environment variable in default.env must be set to:
%ORACLE_HOME%/bin
in the 9i Oracle Home.
Forms Accessibility scripts and the latest information for them is available at:
http://otn.oracle.com/software/products/forms/content.html.
It is our goal to make Oracle Products, Services, and supporting documentation accessible to the entire community. Forms Developer and AS Forms Services support accessibility features. To make the best use of our accessibility features, Oracle Corporation recommends the following software configuration:
For additional accessibility information for Oracle products, visit http://www.oracle.com/accessibility
For the latest configuration information or for information on addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at: http://www.oracle.com/accessibility/faq.html.
Oracle9iDS Forms Japanese documentation is not available for this release. It will be available in the Japanese Oracle9iDS Forms 9.0.2 release.
Java Access Bridge is not installed by default in Oracle9i Forms Developer and Oracle9iAS Forms Services. You will need to obtain Access Bridge from:
http://java.sun.com/products/accessbridge/.
JAWS, a Windows screen reader, may not always correctly read the code examples in the documentation. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.
You can change the Look-and-Feel for the Property Inspector and Navigator to the Forms6i look-and-feel to enable color accessibility by setting the registry variable SET FORMS90_CLAF to value 1 under Oracle Home.
(2118498) For JAWS to work in any of the Debug Windows, the requirements are:
Some side effects for setting the FORMS90_SEPARATE_DEBUGGER variable to enable JAWS include:
ORARRP is not supported. In the Oracle9i Forms Developer and Forms Services: Migrating Forms Applications from Forms6i manual (P/N A92183-01), the following converter.properties options are not supported:
You can ignore these options.
(2278644, 2280598) As a workaround when you receive this error, add the following to the default.env file:
REPORTS_CLASSPATH=%FORMS_ORACLE_HOME%/jlib/zrclient.jar;%FORMS_ORACLE_ HOME%/rep orts/jlib/rwrun.jar
(2228305) As a workaround, modify the file f90desm.sh and uncomment the line that calls reports.sh.
(2262949, 2268090) On Solaris platforms, the formsweb.cfg file contains VM parameters that are not supported for deployment in a production environment. The 1.3 Sun Java plug-in is not supported as a client platform for runtime deployment. The entry in the formsweb.cfg file for this plug-in is included only for use with Oracle9iDS Forms Developer on Unix platforms, when running or debugging a form.
In JInitator 1.3, you set the JAR cache size in the "cache" tab of the JInitiator control panel, which has a default size of 50MB.
To deploy Oracle9i Forms applications on Oracle9iAS, you must configure the forms90.conf file. Oracle9iAS Forms Services use OC4J, via mod_OC4J, for the Forms Servlet and the Forms Listener Servlet only. All other file handling, such as downloading client Java archives and JInitiator, is performed directly by the Oracle HTTP Server. the forms90.conf file is automatically configured during product installation. See the Oracle9iAS Forms Services Deployment Guide (part number A92175-01) for information about the forms90.conf file.
Because there is no Apache HTTP Listener on Oracle9iDS, however, Forms uses OC4J directly for design-time deployment and for downloading client archive files.
FRM-93000: Servlet internal error. Cause: A servlet error occurred, or runtime did not start propery. Action: See the error messages in the servlet (OC4J) log file for clarification.
You can find the OC4J log file at:
<ORACLE_HOME>/j2ee/OC4J_BI_Forms/application-deployments/forms90app
The log file is called application.log, and is usually in a subdirectory like OC4J_BI_Forms_default_island_1, depending on how iAS has been configured.
(2161032) If you use OTHERPARAMS in a named configuration section in the formsweb.cfg file, you overwrite the default the OTHERPARAMS parameter, which contains the DEBUG parameter.
For example, suppose you have a named configuration that looks like this:
[MyApp] otherparams=usesdi=yes
Then you are overriding the default OTHERPARAMS, which looks like this:
otherparams=debug=%debug% host=%host% port=%port%
Therefore, if you use the debugger with the MyApp configuration, the debugger will not run. This behavior also occurs if the Application Server URL is modified in the Form preferences to use the MyApp configuration.
The workaround is to put DEBUG, HOST, and PORT as separate parameters. Modify the appropriate base.html file and the three separate parameters. Make sure to also add them in the default section of formsweb.cfg. Then, remove them from OTHERPARAMS.
To use Run Form on UNIX platforms, do the following:
Note The Web Browser should not be a symbolic link; if so Run Form will hang.
(2293330) To enable HTTPS and Single Sign-On (SSO) with Oracle 9i Forms, do the following:
$ORACLE_HOME/jdk/bin/java -jar $ORACLE HOME/sso/lib/ossoreg.jar -oracle_ home_path %MIDTIER_ORACLE_HOME% -host %<INFRASTRUCTRE_MACHINE_NAME>% -port 1521 -sid iasdb -site_name %<INFRASTRUCTRE_MACHINE_NAME>%:1521 -success_url https://midtierserver.us.oracle.com:4443/osso_login_ success-logout_url https://midtierserver.us.oracle.com:4443/osso_logout_ success-cancel_url https://midtierserver.us.oracle.com:4443/-home_url https://midtierserver.us.oracle.com:4443/-config_mod_osso TRUE -u root -sso_server_version v1.2
If you want to run a form with Jinitiator, append the b64certificate.txt file to certdb.txt. If you want to run a Form natively in Internet Explorer, import this file into Internet Explorer.
The following sections describe known issues in Oracle9i Forms components:
(2190329) The Forms Server is doing necessary clean-up work, such as cleaning up memory allocations. The same effect happens when the Form process is killed from the command line.
(2171120) If you modify the formsweb.cfg file using Enterprise Manager, and then submit the changes, all comments that were in the formsweb.cfg file are removed. This behavior does not occur until you submit the changes; therefore, viewing is safe.
(2247822) Users can no longer specify the log name for the Forms Trace file in a URL. This behavior prevents a user from accidentally writing a file to an invalid location. If a user specifies log=<filename> in the URL, the URL will be ignored. The file will be named forms_<pid>.trc where <pid> is the process ID on the server. The file will be created in the directory specified by the environment variable FORMS90_TRACE_PATH, which is specified on the server.
(2296258) If you specify record=otrace, the Form will fail to start. This issue will be resolved in the next patch set to Oracle9i Forms.
(1983066) When creating a simple form and saving it to a directory such as C:\Program Files\Oracle\test.fmb, and when you click the Run Form icon, an error dialog appears:
FRM-40010 : Cannot read form C:\Program.
This error message appears when there is a space in the URL.
The following keyboard shortcuts have changed:
The following sections describe known bugs in Oracle9i Forms and suggested workaround where available:
(2105230) There is a known problem with conversion of dates prior to November 18, 1883 between different time zones - e.g. US/Eastern to GMT. The wrong result can be returned in these circumstances. This problem will be addressed in a future patch of Oracle9i Forms.
(2060602) Data in NCHAR or NVARCHAR2 columns may not be correct. When a Form is running against a database that has non-Unicode NLS_CHARACTERSET, data can be mangled when inserting or updating from a CHAR item in the Form into an NCHAR or NVARCHAR2 column in the database, even when the server hosting the Form specifies the UTF8 character set for NLS_LANG.
Data can also be mangled when querying from NCHAR or NVARCHAR2 columns.
(2175919) After querying records into a data block, and if the ONETIMEWHERE property is set for the data block, Forms crashes while retrieving the ONETIMEWHERE property.
As a workaround, if you set the ONETIMEWHERE property on a block, then execute the query, do not get the ONETIMEWHERE property.
(1960603) In a Web environment, icons are either.GIF or.JPG files. However, in the Layout Editor in the Forms Builder, ICO files are still used to display icons. These icons are used for design-time only. At runtime, GIF and JPG files are used. A future version of Oracle9i Forms should support GIF and JPG files in the Form Builder at design-time.
(2235125) In the Import Java Classes dialog, you cannot navigate using keys to the Select Java Classes field.
(2234624) If the Form Builder is not running, and when you double click a .fmb file, the Form Builder will start but the file will not load (you'll receive an error message.) However, if the Form Builder is running, double clicking a .fmb file opens it in the Form Builder.
(2250726) DATA_PARAMETER that is used with Run_Product to call Reports cannot be passed to Reports via Run_Report_Object. The migration assistant issues a warning that if this is used in Conjunction with RUN_PRODUCT() for Reports then it will no longer work.
(2116895 and 2116644) The migration of a PLL file is unsuccessful if the PLL contains either the keyword "language" or "userenv('LANG')". As a workaround, we have fixed the Migration Assistant so that if it finds the occurrence of either of these words inside the PLL, it will abort the migration process with an error message. The error message is different for each keyword, and looks something like:
ERROR: <OBJECT_NAME>: Invalid PL/SQL variable name "language" found. This variable should be renamed. ERROR: <OBJECT_NAME>: Invalid PL/SQL construct "userenv('LANG')" found. ora_nls.get_lang_str(ora_nls.language_abbr) should be used instead.
ERROR: Stop word(s) found. Rolling back changes and aborting migration.
Unfortunately, the occurrences of these stop words inside comments also cause migration to be aborted. If you don't want to abort migration of the PLL, you can comment out the userenv and language category lines in the search_replace.properties file.
(2175830) Compile After Conversion (default.generateruntime) is still valid, and is a true/false property. If it is set to "true", the module is compiled after conversion (i.e .fmx or .mmx or .plx file is generated). In the case of PLL files, the PLX file is always generated, irrespective of the default.generateruntime property. This behavior is incorrect, and bug 2175830 has been filed for it.
(2069317) When you compile PL/SQL in Forms, a dialog is raised with a scrollable region with all of the errors listed. This dialog is accessible with the exception of scrolling the errors. As a result, you can only see one error at a time. However, you can use the generator (a separate executable) to output all of the errors.
(2115836) The property palette has four icons that show if a property is default, user-set, inherited, or user-set over inherited. JAWS does not read anything that distinguishes these properties as having these characteristics.
As a workaround, look at the Edit | Inherit menu. It will be disabled if the property in question has a grey dot; otherwise, it is enabled. When it is enabled, you can look at the Subclass Information property, navigate to the property class, and see if the property is inherited or not and compare values.
Alternatively, you can convert the .fmb file to XML and look at the properties there. Only overwritten properties will be displayed in the XML.
(2015489 and 2068572) If you are using JAWS, and you close Internet Explorer, the Windows Task Manager reports the IE process as running because JAWS has an active thread holding IE. The IE process can be killed from the Task Manager.
(2238679) If you open the Form Builder Preferences dialog, JAWS does not read out the tab names. As a workaround, press the F1 key to open the Online Help to explain the structure of the Preferences dialog.
(2127609 and 2145774) If you close the browser while your Forms application is suspended, the runtime process on the server will be orphaned. It will remain until the timeout period is reached, which is 15 minutes by default.
A Forms application is suspended when the client applet is not active. For example,
(2258275) When the RUN_PRODUCT Built-in to invoke a second Web-deployed Forms application, you may receive the error:
Connection from a new browser window not supported
Also, the original Form session may freeze when the newly created one is exited. As a workaround, use the "open_form" PL/SQL built-in to run another (or the same) Form instance in a new session instead of using run_product. This is the recommended way of running multiple Forms sessions in one browser window.
(2254547) After assigning a valid bean name in the Implementation Class Property, Forms returns the following error:
FRM-13008: cannot find javabean with name 'mypackage.PJCBeanWrapper'.
Make sure all the dependent class files are available to Forms builder. If you have created the bean using JDeveloper PJC Wizard, add jdev-rt.jar, f90all.jar and the jar containing the bean classes to FORMS90_BUILDER_CLASSPATH as a workaround.
(2258187) On Solaris, you won't see a new object in the Layout Editor after a valid bean name is set in the Implementation Class property. Unlike the Windows version of the Layout Editor, the Solaris version does not give any user feedback.
Since no feedback is given, and if you've set the classpath incorrectly, or an invalid Bean name is set in the Implementation Class property, you won't know about the error until you run the Form module.
(2252171) After converting an Oracle9i Forms module to its XML equivalent and then back to a Forms module, the canvases may not display correctly because custom color palettes are not preserved in the conversion.
(2061461) When doing an XML to FMB conversion on an Oracle9i Form that contains a graphics object of type IMAGE, and the image file is not found, the conversion utility provides no warning. When this Form is loaded into the Forms Builder and the canvas containing that object is opened, the Form Builder crashes.
(2255174) When using the XML converter on a Oracle9i Form with an attached PLL file, and if the PLL file is not in the FORMS90_PATH, the XML Converter throws an exception. Instead of a clear message which indicates the PLL file that is causing the problem, the user gets an ambiguous error:
Processing XML module vec0005_fmb.xml
@ ERROR - an exception has been encountered:
@ oracle.forms.jdapi.JdapiException: _jni_attach_lib failed
However, the XML Converter will continue without the library.
(2114805) This behavior happens even if the word "CALL" is used elsewhere, such as in comments.
(2116969) The PL/SQL Converter shows warnings about obsolete Built-ins that are commented out.
(2215797) Internally, Forms uses uppercase characters for Oracle9i Form objects. Since Java is case-sensitive, it is important to use uppercase when referring to Forms objects using JDAPI.
This section describes known issues with national language support.
(2055224) This following messages related to the upgrade of obsolete menu item types are not present in non-English versions of the message file.
The following messages were added to the message file:
2500,0, "PLUS-type menu items are not supported in this version of Forms.\n" 2501,0, "FORM-type menu items are not supported in this version of Forms.\n" 2502,0, "MACRO-type menu items are not supported in this version of Forms.\n" 2503,0, "This menu item has been converted to a PL/SQL-type menu item.\nThe old command text is shown within comments below.\n" 2504,0, "Consider using the HOST built-in with the original text." 2505,0, "Consider using the CALL_FORM built-in with the original text." 2506,0, "Consider using the MACRO built-in with the original text."
(1994138 and 1961840) Multibyte or bidirectional characters in query parameters in a URL used to invoke the Forms Servlet may not be handled correctly. For example, attempting to run a form whose (fmx) file name contains multibyte characters using a URL like
http://myserver/forms90/f90servlet?form=abcXX
may fail with an error saying the form module was not found (where XX represent multibyte or bidirectional characters). Also, specifying a multibyte form name in the formsweb.cfg file may fail in the same way too. The workaround is to rename the Form fmx file to a name not containing multibyte characters. These issues will be addressed in a future release.
(194001) Multibyte or bidirectional characters in the environment file (usually called default.env) may not be read correctly. For example, if the FORMS90_PATH variable contains such characters the form may not be found (case where path to the form includes directories whose names contain multibyte characters). The workaround on Windows is to define the FORMS90_PATH setting in the Windows registry instead (using regedit) and remove it from the environment file. Another possible workaround, for all platforms, is to place the form module under directories with names which only include single byte characters.A workaround is to place the form module under directories with names which only include single byte characters.
The following issues relate to TranslationHub:
Individual users of TranslationHub, working in remote sites, might need to use Oracle8i Personal Edition as the local database to store TranslationHub projects.
While installing Oracle8i Personal Edition, use the following notes:
To install Oracle8i Personal Edition on a non-western European language version of Windows NT:
Refer to the Oracle8i Personal Edition Installation Guide for detailed information on installing Oracle8i Personal Edition.
This section describes known errors in the Oracle9i Forms documentation set:
In the Online Help topic "About Debugging", the sixth bullet in the list incorrectly mentions that you can browse instantiated PL/SQL package global variables. These variables cannot be seen in the debugger.
(2278996) The Online Help topic for the Alert Property "Default Alert Button Property" describes the property as optional when in fact it is required.
(2281042) On page FORMS90_DEFAULTFONT, the description for FORMS90_DEFAULTFONT is incorrectly written as FORMS60_DEFAULTFONT.
(2249678) In the Online Help topic "Java Importer", in the C.3 Installation Requirements section, there is an incorrect path:
ORACLE_HOME/TOOLS/COMMON60/JAVA/importer.jar
The correct path is:
ORACLE_HOME/JLIB/importer.jar.
(2215338) The Online Help topic "Starting A Jdapi Session" contains the following piece of Java code:
import oracle.forms.jdapi.*; // Jdapi.startup() does not need to be called because we are starting // the Jdapi in default mode. // public class JdapiSessionExample { public static void main(String[] args) { // suppress errors from missing subclassed modules Jdapi.setFailSubclassLoad(true); // suppress errors from missing PLLs Jdapi.setFailLibraryLoad(true); // This line will cause initialisation FormModule. fmb = new FormModule("myform.fmb");FormModule. fmb = new FormModule("myform.fmb");// program code goes here ... // finally, free API resources Jdapi.shutdown(); } }
The bold line has a period following FormModule; therefore, Java will not compile with that period there.
(2170544) In the Online Help topic "Low-level Subclassing Using Parent Properties", the following line of code:
blockA.setParentModuleStorage(JdapiTypes.PAMO_FILESYSTEM_CTID);
causes a compilation error:
cannot resolve symbol
symbol: variable PAMO_FILESYSTEM_CTID
blockA.setParentModuleStorage(JdapiTypes.PAMO_FILESYSTEM_CTID);
The solution is to comment out this line of code and the example will compile.
(2273363) In the Online Help topic "Including a JavaBean and Custom Controls", the following source code will not compile:
XPos := CurrentValue; get_parameter_attr(BeanValListHdl,'MouseY',ParamType, CurrentValue); YPos := CurrentValue; MsgBox('If you click at '||to_Char(XPos)||'/'||to_Char(YPos)||' again I may drop these beans');
In the bold line, replace "message" for "MsgBox" and the code will compile.
(2257223) In the Online Help topic for the EXIT_FORM Built-in, the description for DO_COMMIT states:
"Forms validates the changes, performs a commit, and exits the current Form without prompting the operator."
The actual behavior is that Forms validates the changes, performs a commit, and exits the current Form without prompting the operator if they want to commit the changes.
(2242622) In the Online Help topic "Modifying a Variable Value", the first step says:
However, it should read:
ORACLE_HOME/forms90/server/forms90.conf file.
<IfModule mod_osso.c>* <Location forms90/f90servlet> require valid-user authType Basic </Location> </IfModule>*
Oracle is a registered trademark, and Oracle9i is a trademark or registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 2002 Oracle Corporation.
All Rights Reserved.
|
|
Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|