9 Compatibility with Earlier Versions

This chapter outlines the compatibility matrix, known issues and workarounds that you should be aware of when you have a configuration that includes different versions of Oracle Forms and Oracle Reports with Oracle Application Server 10g Release 2 (10.1.2) Forms and Reports Services in the following topics:

Compatibility with Earlier Versions and Release 10g (10.1.2)
Interoperability Issues and Workarounds

9.1 Compatibility with Earlier Versions and Release 10g (10.1.2)

Table 9-1 shows a compatibility matrix of earlier versions of Oracle Forms and Oracle Reports.

Notes about the table:

The Clients column refers to all the clients of Oracle Reports and Oracle Forms.
The Reports/Forms Server column refers to the different releases of Oracle Forms and Oracle Reports server.
The Supported column refers to backward compatibility between client and server.

Table 9-1 Forms and Reports Services Compatibility Matrix

Clients Reports/Forms Server Supported? Comments

Clients	Reports/Forms Server	Supported?	Comments
Oracle6i Reports `rwcgi60` `rwcli60` `rwrqv60` `rwservlet`	AS 10g Release 2 (10.1.2) Reports Services	No	None
Oracle9i Reports (9.0.2) Clients `rwcgi` `rwclient` `rwrqv` `rwservlet`	AS 10g Release 2 (10.1.2) Reports Services	No	None
Oracle Reports 10g Release 1 (9.0.4) Clients `rwcgi` `rwclient` `rwrqv` `rwservlet`	AS 10g Release 2 (10.1.2) Reports Services	Yes	None

Oracle6i Reports

rwcgi60
rwcli60
rwrqv60
rwservlet

AS 10g Release 2 (10.1.2) Reports Services

None

Oracle9i Reports (9.0.2) Clients

rwcgi
rwclient
rwrqv
rwservlet

AS 10g Release 2 (10.1.2) Reports Services

None

Oracle Reports 10g Release 1 (9.0.4) Clients

rwcgi
rwclient
rwrqv
rwservlet

AS 10g Release 2 (10.1.2) Reports Services

Yes

None

9.2 Interoperability Issues and Workarounds

This section describes the known issues and workarounds that you should be aware of when you have a configuration that includes different versions of Oracle Application Server instances:

Oracle Enterprise Manager for 9.0.2, 9.0.3, or 9.0.4 and 10g Release 2 (10.1.2) Uses the Same Port (Port 1810)
dcmctl getState Command from an Oracle Application Server Forms Services Instance Cannot Be Used With 9.0.2, 9.0.3, and 9.0.4 Instances
Oracle Enterprise Manager: No Rollup Metrics for 9.0.2 Middle Tiers

9.2.1 Oracle Enterprise Manager for 9.0.2, 9.0.3, or 9.0.4 and 10g Release 2 (10.1.2) Uses the Same Port (Port 1810)

In 9.0.2, 9.0.3, and 9.0.4, the installer assigns port 1810 to the Oracle Enterprise Manager Web Site, regardless of whether or not the port is already in use. If the computer on which you plan to install the 10g Release 2 (10.1.2) instance already has a 9.0.2, 9.0.3, or 9.0.4 instance, the Application Server Control component for the 10g Release 2 (10.1.2) instance might already be using port 1810.

Tip:

In 10g Release 2 (10.1.2), you can specify custom port numbers to use for each component. See Section 3.5.3, "Using Custom Port Numbers (the Static Ports Feature)".

For the case where Oracle Enterprise Manager 9.0.2, 9.0.3, or 9.0.4, and 10g Release 2 (10.1.2) are configured on the same port (1810), you can change the port used by the 10g Release 2 (10.1.2) Oracle Enterprise Manager to a different port. You can then run both Oracle Enterprise Managers at the same time. To change the port on the Oracle Enterprise Manager Release 10g, perform these steps:

In the 10g Release 2 (10.1.2) home, edit the ORACLE_HOME/sysman/j2ee/config/emd-web-site.xml file and change the port value from 1810 to an unused port. The following example sets the port to 1814:
```
<web-site host="[ALL]" port="1814" display-name="Oracle Enterprise Manager
 iAS Console Website" secure="false">
```
If the 9.0.2/9.0.3/9.0.4 instance is using 1810, it is also likely that the instance is using port 1811 for RMI operations. With the 9.0.2, 9.0.3, or 9.0.4 Oracle Enterprise Manager running, check which port in the 1810-1829 range is unused, and use this value.

You can run the netstat command to determine which ports are in use. The following example checks if port 1814 is in use.
```
prompt> netstat -n | grep 1814
```

Also in the 10g Release 2 (10.1.2) home, enter the same port number in the ORACLE_HOME/sysman/emd/targets.xml file. The port number is specified in the StandaloneConsoleURL property of the oracle_ias target.

<Target TYPE="oracle_ias" NAME="infra.myhost.oracle.com" VERSION="1.0">
   ... lines not shown ...
   <Property NAME="StandaloneConsoleURL"
            VALUE="http://myhost.oracle.com:1814/emd/console"/>

Once you have updated these two files, you can run BOTH the 9.0.2, 9.0.3, or 9.0.4 and Oracle Enterprise Manager 10g Release 2 (10.1.2) at the same time.

9.2.2 dcmctl getState Command from an Oracle Application Server Forms Services Instance Cannot Be Used With 9.0.2, 9.0.3, and 9.0.4 Instances

If you run the dcmctl getState command from an OracleAS Forms Services instance to get information on a 9.0.2, 9.0.3, or 9.0.4 instance, you will get an ADMN-604104 error:

prompt> dcmctl getState -i name_of_902_or_903_instance
ADMN-604104 Unable to connect to the OPMN process to obtain process status table

To get information on 9.0.2, 9.0.3, or 9.0.4 instances using the dcmctl command, use the 9.0.2, 9.0.3, or 9.0.4 dcmctl command.

9.2.3 Oracle Enterprise Manager: No Rollup Metrics for 9.0.2 Middle Tiers

Oracle Enterprise Manager Application Server Control does not monitor 9.0.2.x or 9.0.3.x instances. You have to use Oracle Enterprise Manager 9.0.2 or 9.0.3 to manage these instances.