This chapter describes the installation, configuration, upgrade and migration issues associated with Oracle Forms and Reports.
The following sections are included:
This section describes installation and configuration changes, issues and their workarounds.
It includes the following topics:
After you have successfully installed and configured Forms Server 12.2.1.3.0 on IBM AIX, you might notice Forms server crashing while serving the user requests. You might also see the following error text:
exec(): 0509-036 Cannot load program frmweb because of the following errors: rtld: 0712-001 Symbol CreateIoCompletionPort was referenced from module $ORACLE_HOME/lib/libclntsh.so(), but a runtime definition of the symbol was not found.
Forms 12.2.1.3.0 is bundled with the IBM AIX Database Client 12.1.0.2.0 version. The issue is related to the IOCP API symbols dependency in Database 12.1.0.2 client library.
To resolve this issue for IBM AIX, enable the IOCP module in Forms Server installation machine.
On IBM AIX on POWER Systems (64-Bit), enable I/O completion ports (IOCP) before initiating the install process.
To check if the IOCP module is enabled, run the lsdev command: $ lsdev | grep iocp
The following sample output shows the IOCP status is set to Defined and hence not enabled: iocp0 Defined I/O Completion Ports
By default, IOCP is set to Defined.
To enable IOCP, set IOCP status to Available using the following procedure:
Log in as root and run the following command: # smitty iocp.
Select Change / Show Characteristics of I/O Completion Ports.
Change configured state at system restart from Defined to Available.
Available:
$ lsdev | grep iocp iocp0 Available I/O Completion Ports
Perform a system restart to make the changes permanent.
If you encounter a FORBIDDEN error when using One-Button-Run with any of the supported browsers other than Internet Explorer, verify if 127.0.0.1 (localhost) is in the proxy settings for your browser. If 127.0.0.1 is not in the exceptions list, then add it. This ensures that the browser will bypass the proxy server.
Oracle Forms 12c, when configured with Webutil at runtime, supports JACOB version 1.18-M2 to perform the client side OLE integration. Notice that this version of JACOB is different from the versions supported in the previous releases of Oracle Forms.
JACOB is a JAVA-COM bridge that enables you to call COM automation components from Java. It uses JNI to make native calls to the COM libraries. JACOB runs on x86 and x64 environments supporting 32 bit and 64 bit JVMs.
Oracle Forms 12c, colorscheme default value has been changed from TEAL to SWAN. This value has been set in the formsweb.cfg as part of the initial installation configuration.
colorScheme=SWAN
This colorscheme presents Forms with an updated and modernized look and feel. It also resembles the Fusion Middleware Control and all other components that are used to manage Forms12c. If you want the old colorscheme, change the value in the default section of the Forms Web Configuration (formsweb.cfg).
Oracle Forms uses time zone data to support the ADJUST_TZ built-in and to adjust the date/time displayed in DATETIME items. Values loaded from the database or set by application logic are interpreted as being in the "server" time zone, whereas values displayed in DATETIME items are converted from the server time zone to the end-user "local" time zone. The server time zone is specified by FORMS_DATETIME_SERVER_TZ, and defaults to GMT. The end-user local time zone is specified by FORMS_DATETIME_LOCAL_TZ, and defaults to the time zone of the java client. Notice that the default values for FORMS_DATETIME_SERVER_TZ and FORMS_DATETIME_LOCAL_TZ are usually different.
In previous release, Forms interpreted a null value for FORMS_TZFILE as an indication that no time zone adjustment should occur for DATETIME items. As of Forms 12c (12.2.1) release, FORMS_TZFILE is no longer inspected, so there is no specific mechanism for suppressing time zone adjustment of DATETIME items. Therefore, customers who were leaving FORMS_TZFILE unset will see a change in behavior compared to Forms 11g (11.1.2) and older unless they take some action to ensure that the end-user local time zone is identical to the server time zone. To ensure this you must add FORMS_DATETIME_LOCAL_TZ=GMT to the environment variable configuration file, for example, default.env.
FORMS_DATETIME_SERVER_TZ defaults to GMT, so there is no need to set it to GMT explicitly if you are planning to use the above procedure.
The following are the issues with Forms and Reports using database client:
Beginning with 12.2.1.3.0, installation is based on Oracle Database 12.1.0.2.0. As a result, all application modules must be regenerated prior to running. Once application modules have been regenerated in the new version, they (source or runtime files) will not be backward compatible to any earlier versions. Backup copies of application modules should be created before attempting to regenerate or open in the Forms Builder. This process cannot be reversed.
User exits should be regenerated using a version 12.1.0.2.0 pre-compiler.
If the domain being created (or extended) is to include Forms Application Deployment Service (FADS), the SqlDeveloper version installed in the associated Oracle Home must be upgraded to version 4.2.x or newer, but not to exceed version 17.4. This update must be completed before configuring the WLS domain to include FADS.
The Forms Application Deployment Service (FADS) web interface supports 100meg maximum archive (.far) file size limit. If you attempts to deploy files larger than 100meg may result in web server timeout errors and the deployment will fail. For large files, use client utility instead of the web interface.
Some of the ADF errors and/or warnings in Admin Server logs which are related to FADS can be ignored; unless FADS is not functioning properly.
Eclipse/Jetty version 9.4.5 is required for Forms Java Script Integration (WebSocketJSI). This jar file must be signed with a trusted and known certificate. For information on how to sign jar files see Java documentation. If using Java Web Start for deployment, add the Jetty jar reference to extensions.jnlp. The required files can be downloaded from the following locations:
This section describes issues associated with the upgrade and migration process of Oracle Forms and Reports.
It includes the following topics:
To view the list of Oracle Forms changed or obsolete features, see Preparing to Upgrade.
To upgrade from Oracle Forms 10g or Oracle Forms Services 11g (11.1.x), see: