|
Oracle9i Application Server Release Notes Addendum,
Release 2 (9.0.2.0.1) for Solaris Operating System (SPARC) Part No. B10023-09 |
|
|
|
|
Oracle9i Application Server Release Notes Addendum,
Release 2 (9.0.2.0.1) for Solaris Operating System (SPARC) Part No. B10023-09 |
|
|
|
|
This chapter describes installation and migration issues and their workarounds. Topics include:
This section covers the following installation issues:
Simultaneous Installations Using Common Infrastructure May Result in Errors
Multiple Installations Using Same Installer Session May Result in Errors
Perform Additional Infrastructure Database Installations in a Serial Manner
Infrastructure Database Should Not Be Used During Infrastructure Installation
Oracle Enterprise Manager Web Site Must Be Shut Down Before Installation
Portal Configuration Issues During Portal and Wireless Upgrade
Help Information is Missing for Infrastructure Summary Screen
Oracle9iAS Metadata Repository Coexisting with Other Oracle Databases
Verify Permissions to /tmp, TEMP, and /var/tmp Directories Before Installation
Oracle9iAS Does Not Support Changing the Host Nameand IP Address After Installation
Information about Concurrent Portal and Wireless Installations
UM Configuration Assistant Fails if UM is Installed in Same Oracle Home as Portal and Wireless
Oracle9iAS Clickstream Intelligence Not Accessible After Upgrade
Installation of J2EE and Web Cache in Middle Tier Oracle Home Not Supported
Deinstalling Oracle9iAS Infrastructure After Business Intelligence and Forms Installation
If you perform multiple installations using the same Oracle9iAS Infrastructure, be sure to perform only one installation at a time. Simultaneous installations and configurations pointing to a common Oracle9iAS Infrastructure can result in a failure during OC4J deployment with some resource dead lock errors.
Following installation of Oracle9iAS, exit the installer before installing another instance of Oracle9iAS. If the same installer session is used to install another instance of Oracle9iAS, then SQLJ, JAZN, and Oracle Java Server Page applications may fail in the second instance with "URL not found" errors.
If you have an existing infrastructure and you want to install
additional Oracle9iAS Infrastructure databases, then perform
an infrastructure database-only installation and point it to the
existing Oracle9iAS Single Sign-On/Oracle Internet Directory.
To specify the global database name, the Oracle Universal Installer
searches Oracle Internet Directory and the local oratab file for the
names of existing databases. It then specifies the next global database
name incrementally. For example, if you have an existing infrastructure
which already includes databases named iasdb1 and iasdb2,
then it would specify iasdb3 as the global database name
for the next installation. This happens early in the installation
process during the dialog phase.
Later, toward the end of the installation process, the Database
Creation Assistant (DBCA) registers that global database name with the
directory. It does this by creating a distinguished name (DN), namely, cn=iasdb3,
cn=oraclecontext. This DN stores information about the
database, for example, the host name, listener string, listener port,
Oracle Home, and so on.
Now, suppose that you perform the new database installation and the
Oracle Universal Installer chooses iasdb3 as the global
database name. Suppose further that, before DBCA registers this
database in the directory, you perform a second database installation
on a different host. In the second installation, the installer would
likewise select iasdb3 as the global database name. This
is because, at the time of the second installation, the DBCA from the
first installation has not yet registered the DN of iasdb3
in the directory.
In this case, the DBCA from the second installation does not report an error when it sees that an another entry with the same DN is already present in the directory. Instead, it overwrites the entry from the first installation with its own values. This causes the first installation with the same simple name to fail.
To avoid this problem, perform any additional infrastructure database installations in a serial manner, that is, wait until the first installation has completed before beginning the second.
You should not use the Oracle9iAS Infrastructure database until the Oracle9iAS Infrastructure installation is complete. Using the Oracle9iAS Infrastructure database during installation may cause the installation to hang.
After accessing a large number of different module services or HTTP
adapter-based services (with JSP-based content sources hosted on the
same Java VM), some of the services fail with a 'service error'.
Accessing the target JSPs results in a 'NoClassDefFound'
exception. Restarting the server corrects the problem.
When an application is loaded for the first time, the OC4J classloaders read the class bytes in the library jars into memory; it does so even without the classes being instantiated (because the application instantiates classes from an in-memory array).
Class files resulting from compiling JSP files are loaded
dynamically. With time, the heap gets filled up and newer classes from
compiled JSPs cannot be read into the memory array(s), nor instantiated
on the heap. Hence the top-level classloaders fail with a 'NoClassDefFound'
exception. In subsequent lookups, the 'OutOfMemoryError'
is not thrown since the JDK classloader loadClass( )
implementation semantics prescribe NOT reloading classes that could not
deterministically be loaded earlier.
To determine if this is the case, check the number of OutOfMemoryErrors
in sys_panama.log. That number should be the same as the
number of times the server has been restarted.
If it is the case, increase the heap-size for the VM by modifying
the Java option subelement of the OC4J element corresponding to the instanceName
OC4J_Wireless.
From your browser, point to Oracle Enterprise Manager at http://<host>:1810.
Log in to Enterprise Manager as ias_admin/<password
supplied at install time>.
Select your middle tier instance.
Select OC4J_Wireless. The OC4J_Wireless screen appears.
Select "Server Properties" (located under Instance Properties at the bottom of the OC4J_Wireless page) to invoke the Server Properties page. A page with command-line options appears which includes an editable field for Java Options which you use to set the heap size.
Use the Java Options field to set the heap size.
Remove the option -noclassgc.
Click Apply.
|
See Also: "Setting the JVM Heap Size for OC4J Processes" section in the Oracle9i Application Server Performance Guide. |
If user1 installs Oracle9iAS in ORACLE_HOME1 (this is the Oracle home from which Oracle Enterprise Manager runs) and user2 attempts to install Oracle9iAS in ORACLE_HOME2, then the installation stops automatically because Oracle recommends doing multiple Oracle9iAS installs as the same O/S user.
However, if different users want to perform multiple installs on the same host, then the following preinstallation tasks are required before the second install begins:
|
Note: Be sure that both the users belong to the same group. |
Find out which ORACLE_HOME has the active EMD. To
do so, check for the ACTIVE_EMD_HOME entry in /tmp/emtab.
As user1, create a directory called ORACLE_HOME/install/lockdir
in ORACLE_HOME1.
Give user2 "write" privileges to this directory.
Start the second install as user2.
|
Warning: Using the above workaround will disable Oracle Enterprise Manager for the new instance you are installing. |
Before performing an installation on a machine that already has an Oracle9iAS instance, be sure to stop the Oracle Enterprise Manager Web site.
Use the following command to stop the Web site:
ORACLE_HOME/bin/emctl stop
If you install the J2EE and Web Cache install type and then install the Portal and Wireless install type over it, then the Portal runtime generates the following error when you click on the login link in the Portal home page:
"Error: You cannot login because there is no configuration information stored in the enabler configuration table. (WWC-41439)"
Complete the following steps as a workaround:
Open the launch.sh file in the ORACLE_HOME/assistants/opca
directory, and replace the SSL port number assigned to the variable http_port
with Oracle HTTP Server port (same as Oracle9iAS Web Cache
port) of the middle tier installation. Save and close the file.
For example, in the line set http_port = <value>,
the existing value should be replaced with the HTTP server port of the
middle tier installation.
Run the edited launch.sh file.
The help information for the infrastructure Summary screen is missing in the Oracle Universal Installer. The help screen should display the following:
The host for your Oracle9iAS installation is already associated with an Oracle9iAS Infrastructure. The host name and port number for associated Oracle9iAS Infrastructure components are listed on the Summary screen.
Your Oracle9iAS Metadata Repository, installed as part of the Oracle9iAS Infrastructure installation, can coexist with existing installations of either the Oracle 8.1.7 Database or Oracle9i Database.
The following steps describe how to enable coexistence of Oracle9iAS Metadata Repository with the existing Oracle databases:
Verify that you are a member of the administrative group for existing installations of either the Oracle 8.1.7 Database or Oracle9i Database.
Verify that your machine contains the following minimum hardware requirements for Oracle9iAS Metadata Repository installation and coexistence:
Disk space = 6 GB
TMP or swap space = 1 GB
Memory = 1 GB
Ensure the Oracle Home directory selection for your Oracle9iAS Metadata Repository installation is in a different Oracle home than the Oracle 8.1.7 Database and the Oracle9i Database installations.
Make sure the orahome and oraInventory
directories for the existing Oracle databases have read, write, and
execute permissions for both the group and user.
For coexistence with the Oracle 8.1.7 Database, make sure the oui.loc
file located in the existing Oracle products oraInventory
directory has write permission for your administrative group.
Make sure that the coexisting Oracle databases are running during Oracle9iAS Metadata Repository installation so that port conflicts can be resolved.
|
See Also: Oracle9i Application Server Installation Guide for information about using different port numbers. |
If you deinstall an instance that uses an Oracle9iAS Infrastructure, you cannot reuse the name of that deinstalled instance when installing subsequent instances.
As a workaround, manually delete the entry for the deinstalled instance in Oracle Internet Directory.
If you install more than one J2EE and Web Cache install type on a machine and the installations do not use Oracle9iAS Single Sign-On, then, during installation, you must verify that the instance name for each instance is unique.
This issue will not occur in the following cases:
J2EE and Web Cache installations use Oracle9iAS Single Sign-On.
You are installing any of the other Oracle9iAS install types.
For Java versions later than Java 1.1.n, Oracle Universal Installer 2.2.0.1.0 fails to come up if a monitor component has 16 colors. This is because monitors with 16 colors are not supported by Sun in JDK versions later than Java 1.1.n.
Make sure you have write access to the /tmp, TEMP,
and /var/tmp directories on your system before you start
installation of Oracle9iAS.
Oracle9iAS installation might report that you have insufficient swap space to proceed with the install, even if you have the required amount.
To work around this problem, unset the TMP environment
variable and restart the install.
The install checks to see if the fully qualified host name is present in the etc/hosts file on UNIX systems. If this check fails, an error message is displayed informing the user to fix the file and then restart the install.
If the etc/hosts file needs to be edited, then you
must reboot the machine after doing so before restarting the install.
Otherwise, the change may not take effect.
Oracle9iAS does not support changing the host nameand IP address after installation.
When installing Oracle9iAS on a machine that uses a number as the first character for the domain, instead of a letter, the install fails with the following error:
Invalid database domain name. The database domain name must start with an alphabetical character.
Keep the following in consideration when naming your host:
No blank or space characters are permitted as part of a domain name.
No distinction is made between upper and lower case.
The first character must be an alpha character.
The last character must not be a minus sign or period.
A host which serves as a GATEWAY should have "-GATEWAY"
or "-GW" as part of its name. Hosts which do not serve as
Internet gateways should not use "-GATEWAY" and "-GW"
as part of their names.
If your machine is not configured as per the instructions provided in the "Hostnames File Configuration" section of the "Getting Started" chapter of the Oracle9i Application Server Installation Guide, the installer stops the installation process with the following error:
Your /etc/hosts and other required files are not configured with the domain and the user may make the changes in the required files by following the docs.
However, neither the documentation nor the installer error specify that you must reboot the machine after making the changes. Reboot the machine at the point before continuing with the Oracle9iAS installs.
Although a reboot is necessary, the installation will continue at this point if you choose not to reboot the machine. However, after installation, if you reboot the machine after the host name changes were made, you will see problems such as the following in the infrastructure and middle tier:
Oracle HTTP Server will not start and you will see the following error in the OPMN logs.
"Syntax error on line 6 of OH/Apache/Apache/conf/mod_osso.conf:
Unable to deobfuscate the SSO server config file, <ORACLE_HOME>/Apache/Apache/conf/osso/osso.conf, error
Bad padding pattern detected in the last block."
Metadata repository API will not work resulting in most middle tier components failing to connect to Oracle Internet Directory/Database with the following error:
oracle.ias.repository.schema.SchemaException:Password could not be retrieved
If you get the above mentioned errors after the reboot, perform the following steps:
Start the infrastructure database.
Start the infrastructure Oracle Internet Directory.
Set the environment variable LD_LIBRARY_PATH to
include <ORACLE_HOME>/lib
to the beginning of the existing LD_LIBRARY_PATH.
Run the following command to reset the Oracle9iAS password:
resetiASpasswd.sh "cn=orcladmin" <password><ORACLE_HOME>
where
<password> is your Oracle Internet Directory
administration password and <ORACLE_HOME> is the
absolute path for Oracle home.
Run the following command to reregister mod_osso:
<ORACLE_HOME>/jdk/bin/java -jar <ORACLE_HOME>/sso/lib/ossoreg.jar -site_name
<iASInstanceName>.<FQDN> -success_url
http://<FQDN>:<ApachePort#>/osso_login_success -cancel_url
http://<FQDN>:<ApachePort#> -logout_url
http://<FQDN>:<ApachePort#>/osso_logout_success -home_url
http://<FQDN>:<ApachePort#> -config_mod_osso TRUE -oracle_home_path
<ORACLE_HOME> -u root -apache_server_root <ORACLE_HOME>/Apache/Apache
-config_file <ORACLE_HOME>/Apache/Apache/conf/osso/osso.conf
-sso_server_version v1.2
where
<ORACLE_HOME>: Absolute path for
Oracle home
<iASInstanceName>: Instance name
given during install
FQDN: Fully Qualified Host Name (foo.us.com)
ApachePort#: Oracle HTTP Server listen port
This workaround can also be used in cases where a machine crashes and the Oracle9iAS install must be restored on a different machine, assuming that machine is given the same hostname/IP address as the original machine.
If you install the Portal and Wireless install type on one machine and then deinstall it, and then install Portal and Wireless on a separate machine, then the password of the second installation will not work if both the Portal and Wireless installations were pointing to the same infrastructure.
Consider the following scenario:
Infrastructure is installed on machine A and Portal and Wireless is
installed on machine B, pointing to the infrastructure on machine A.
Portal and Wireless instance password is instance1. Then
the Portal and Wireless instance is deinstalled from machine B.
Now Portal and Wireless is installed on machine C, pointing to the
infrastructure on machine A. The instance password is instance2.
Here, it is not possible to login to portal using the latest instance
password, instance2. It is possible to login by the first
Portal and Wireless instance password, instance1, which
is connected to the infrastructure.
Multiple middle tiers of Portal and Wireless install type can be installed concurrently against the same infrastructure, the only requirement being that the first middle tier be installed with no other middle tier installation occurring against the infrastructure simultaneously. From then on, as in from the second middle tier onwards, any number of middle tiers can be installed at the same time.
If you have a Portal and Wireless installation and then install Unified Messaging in that Oracle home, then the Unified Messaging Configuration Assistant fails with the following error:
<ORACLE_HOME>/um/scripts/run_append_deploy.sh: /jdk/jre/bin/java: not found
Currently, there is no workaround for this issue.
Oracle9iAS Clickstream Intelligence is not accessible using the HTTP port when you upgrade an existing Oracle9iAS installation to Business Intelligence and Forms or Unified Messaging.
As a workaround, change the <ORACLE_HOME>/click/conf/click-apache.conf file with the Server SSL port, as shown below.
# Enable SSL for Runtime Administrator (config subdirectory)
#
<Location /click>
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule^(config/.*)$ https://%{SERVER_NAME}:<Server_SSL_Port>/click/$1 [R]
</Location>
Restart OPMN after the above changes are made.
Installation of Oracle9iAS J2EE and Web Cache, Release 2 (9.0.2.0.1), available only through Oracle Technology Network, in the Oracle home of any Release 2 (9.0.2.0.1) middle-tier installation is not supported.
Business Intelligence and Forms installation requires an Oracle9iAS Infrastructure. However, you can choose to deinstall the Oracle9iAS Infrastructure after Business Intelligence and Forms is installed.
Consider the following before deinstalling Oracle9iAS Infrastructure:
After deinstallation, if you want to use Oracle9iAS Infrastructure and its benefits, you will have to reinstall Oracle9iAS Infrastructure and Business Intelligence and Forms.
Forms and Reports patches can still be installed on top of the Business Intelligence and Forms installation after you have deinstalled Oracle9iAS Infrastructure.
After Oracle9iAS Infrastructure is deinstalled, Oracle9iAS Forms Services, Oracle9iAS Reports Services (non-secure), Oracle HTTP Server, OC4J, and Oracle Enterprise Manager are functional.
Oracle9iAS Reports Services must be used in non-secure mode after Oracle9iAS Infrastructure is deinstalled.
To place Oracle9iAS Reports Services into non-secure mode:
Locate your ORACLE_HOME/reports/conf/<servername>.conf file
Locate the job element in the <servername>.conf file. For example:
<job jobType="report" engineId="rwEng" securityId="rwSec"/>
<job jobType="report" engineId="rwEngURL" securityId="rwSec"/>
Remove the security id attributes from the job element specification.
Perform the following steps to deinstall Oracle9iAS Infrastructure:
Stop all Business Intelligence and Forms processes.
In your ias.properties file set the following
parameter:
InfrastructureUse=false
As the root user, execute the following command on the machine hosting Business Intelligence and Forms to disassociate from the Oracle9iAS Infrastructure:
<ORACLE_HOME>/dcm/bin/dcmctl leaveFarm
Rename <ORACLE_HOME>/j2ee/home/config/jazn.xml
to jazn.xml.orig to serve as a back up of your files.
In the same directory, create jazn.xml and add the following line:
<jazn provider="XML" location="<ORACLE_HOME>/j2ee/home/config/jazn-data.xml"/>
to point jazn to your Oracle9iAS middle-tier installation instead of Oracle9iAS Infrastructure.
Stop all processes running on Oracle9iAS Infrastructure, and deinstall Oracle9iAS Infrastructure using instructions provided in Oracle9i Application Server Installation Guide.
The Korn shell environment variable ENV can alter
variables set by Oracle9iAS scripts. If you are using the Korn
shell and the ENV environment variable is set, you must
unset the variable before starting installation Oracle9iAS.
The command to unset the ENV variable is unset
ENV.
This section covers the following postinstallation issues:
Oracle9iAS install does not configure JServ by default.
Perform configuration tasks using the Oracle Enterprise Manager Console
as a postinstallation task. Oracle Management Server has a reporting
servlet that runs within JServ. In order to access this reporting
servlet, configure JServ from the Oracle Enterprise
Manager Console.
Infrastructure installs do not have "JServ" listed as
an installed component in ORACLE_HOME/config/ias.properties.
Therefore, "JServ" is, by default, not configurable after
installation.
To make JServ configurable in the infrastructure
install, edit the ias.properties file from ORACLE_HOME/config
directory as below:
Change the following existing line (to append "JServ"
to "Components" entry) from:
Components=Apache,J2EE,WebCache,SSO,OID
to
Components=Apache,J2EE,WebCache,SSO,OID,JServ
After the end of installation, you must reset the SYS and SYSTEM
passwords for the infrastructure database for security. During install
time, the installer does not prompt you for new SYS and SYSTEM
passwords.
When you invoke NetCA to configure a directory, you might encounter an error. For example, when you:
Invoke NetCA.
Select "Directory Usage Configuration" and click Next.
Choose the second option, "Select the direct you want to use, and configure the directory server for Oracle usage" and click Next.
Select "Oracle Internet Directory" and click Next.
Enter the host name and port number and click Next.
On the next page titled "Oracle NetCA, Directory Usage Configuration, No Oracle Schema" you see the following:
The directory does not contain the required Oracle Schema. Directory usage cannot continue without the correct Oracle Schema. If you have the authorization to create a directory schema, then you can create the required Oracle Schema now. Would you like to add the required Oracle Schema to the directory.
Here, choose the option "Yes, I want to add the required Oracle Schema. I have the authorization to do so", and click Next.
In the next window, you will get the following message:
Oracle Schema Creation Complete
At this point, the window asking the user to enter the DN of the user and password is missing.
To fix this problem, download the 9.0.1.3 ARU 1742082 patch for Sun SPARC Solaris. Please refer to updates on ARU for more information.
This section covers these deinstallation issues:
Before deinstallation, perform the following steps to shut everything down:
On the Oracle Enterprise Manager Web site, perform a "stopall" to shutdown the instance. Exit the OEM Web site.
At a prompt, issue the following commands:
emctl stop
opmnctl stop
Your primary installation contains the active Oracle9iAS Administration Service. If you deinstall the primary installation and there are other installations of Oracle9iAS on your host, the Oracle Universal Installer will request that you designate one of the remaining Oracle9iAS installations to be the primary installation. The new primary installation will maintain the configuration information for the remaining Oracle9iAS installations on the host.
After Oracle9iAS is installed, use Oracle Universal Installer 2.1 or greater to deinstall, if required, any Oracle products installed on the system. This includes Oracle databases, version 8i and 9.0.1, and Oracle9iAS, versions 1.x.
|
Note: The deinstallation of Oracle databases, version 8i and 9.0.1, and Oracle9iAS, versions 1.x, should not be done in the same session as installation or deinstallation of Oracle9iAS. |
If you deinstall an instance and transfer the Oracle Enterprise Manager Web Site (also known as Oracle9iAS Administration Service) to a second instance, and then try to deinstall that second instance, you may see the following error:
"An inactive 9iAS Administration Service's control program is being executed Use ORACLE_HOME2/bin/emctl to administer the *active* 9iAS Administration Service"
To avoid the error, you must deactivate the Oracle Enterprise Manager Web Site from the second instance. You can do this by running the following command before deinstalling the second instance:
<ORACLE_HOME2>/bin/emctl switch
home <ORACLE_HOME2>
where ORACLE_HOME2 is the Oracle home of the
second instance.
If you have 9.0.2 or 9.0.3 and Release 2 (9.0.4) instances on the same computer, and you want to deinstall a 9.0.2 or 9.0.3 instance, perform these steps:
Apply patch 3234681 to your 9.0.2 or 9.0.3 instances. You can
download the patch from OracleMetaLink (http://metalink.oracle.com).
Stop all processes associated with the instance you want to deinstall.
Run the installer to deinstall the 9.0.2 or 9.0.3 instance. Make sure you run the installer for the 9.0.2 or 9.0.3 instance.
For 9.0.2 and 9.0.3 instances, the installer is located in the oui/install
directory at the same level as the Oracle home directory. For example,
if the 9.0.2 or 9.0.3 Oracle home is /opt/oracle/orahome902,
then the installer would be /opt/oracle/oui/install/runInstaller.
If you have multiple 9.0.2 and/or 9.0.3 instances on the same computer, these instances share an Oracle Enterprise Manager. This is the "active Oracle Enterprise Manager". When you deinstall the instance that contains the active Oracle Enterprise Manager using the installer, the installer needs to switch the active Oracle Enterprise Manager to one of the remaining instances. If there is only one remaining instance, then the installer automatically makes it the active Oracle Enterprise Manager. If more than one instance remain, the installer prompts you to select the instance to contain the active Oracle Enterprise Manager.
Unlike 9.0.2 or 9.0.3 instances, Oracle9i Application Server Release 2 (9.0.4) instances on the same computer do not share an Oracle Enterprise Manager. Each Release 2 (9.0.4) instance has its own Oracle Enterprise Manager.
Because Release 2 (9.0.4) instances do not share an Oracle Enterprise Manager, you must not select a Release 2 (9.0.4) instance to contain the active Oracle Enterprise Manager. You must select a 9.0.2 or 9.0.3 instance to contain the active Oracle Enterprise Manager.
If you select a Release 2 (9.0.4) instance, or if the installer automatically switches the active Oracle Enterprise Manager to a remaining instance that happens to be a Release 2 (9.0.4) instance, the installer overwrites files in the Release 2 (9.0.4) Oracle home with files from the 9.0.2 or 9.0.3 home. This causes Oracle Enterprise Manager to stop working.
The patch prevents the installer from automatically switching the active Oracle Enterprise Manager to a Release 2 (9.0.4) instance in the case where the only remaining instances are Release 2 (9.0.4) instances. It also prevents the installer from displaying Release 2 (9.0.4) instances in the list where you select the instance to contain the active Oracle Enterprise Manager.
If a Release 2 (9.0.4) instance becomes the active Oracle Enterprise Manager, Oracle Enterprise Manager will stop working.
To fix this, perform these steps in the Release 2 (9.0.4) Oracle home:
Shut down the Oracle Enterprise Manager Application Server Control.
prompt> emctl stop iasconsole
Rename the following files. Do not delete the files, because you
might need them in step 5. You can rename them
with an "active" suffix (for example, iasadmin.properties.active):
ORACLE_HOME/sysman/config/iasadmin.properties
ORACLE_HOME/sysman/emd/targets.xml
ORACLE_HOME/sysman/j2ee/config/jazn-data.xml
ORACLE_HOME/sysman/webapps/emd/WEB-INF/config/consoleConfig.xml
Copy the backup files for the files listed in the preceding step.
The backup files are in the same directory as the listed files.
The names of the backup files are suffixed with a digit (for example, iasadmin.properties.1).
Check the timestamp, or check the content, of the backup files to
determine the most recent backup file.
Start the Oracle Enterprise Manager Application Server Control.
prompt> emctl start iasconsole
If you have remaining 9.0.2/9.0.3 instances on the computer, you need to designate one of them to contain the active Oracle Enterprise Manager.
Copy the files listed in step 2
(which you renamed with the active suffix) to the
9.0.2/9.0.3 instance's Oracle home. Rename them back to the original
names (that is, remove the active suffix).
Edit /var/opt/oracle/emtab to set the DEFAULT
property to refer to the new active Oracle Enterprise Manager.
This section covers these migration issues:
The subscriber name argument to the ptgUpgradeRepository.sh
script must be the DNS subdomain that the machine is registered under
(that is, if the machine has a fully-qualified DNS name mymachine.foo.bar.com,
then the subscriber name argument is foo.). If for
example, it is mymachine.bar.com, then the subscriber
name argument would be bar.
After migrating services that are based on the URL adapter, ensure that the input parameters are still valid. If not, modify them from the Service Designer:
Click the radio-button next to the service to select it.
Click Edit.
Choose "Input parameters" from the side tab.
Enter the new URL.
Typically URLs that were hosted on the old instance itself, such as http://mymachine.foo.com:7777/portal/URLtest.jsp
may not be valid anymore. In this particular instance, a solution could
be to copy URLtest.jsp to <New_Oracle_Home>/j2ee/applications/webtool/webtool-web
and modify the service referring to it, following the above-mentioned
steps.
