Oracle® Application Server Release Notes
10g (9.0.4) for Solaris Operating System (SPARC) Part No. B10629-15 |
|
![]() Previous |
![]() Next |
This chapter describes installation, migration, and upgrade issues and their workarounds associated with Oracle Application Server. It includes the following topics:
This section describes preinstallation issues. It includes the following topics:
Section 3.1.4, "All OracleAS Active Failover Cluster Nodes Must Be Up When Installing Middle Tiers"
Section 3.1.7, "Install Type Restrictions for Spanish Locales"
Section 3.1.8, "Do Not Set NLS_LANG Environment Variable Before Invoking MRCA"
When installing an OracleAS Metadata Repository, you are prompted for the global database name for the repository. This typically is in the form sid.domainname
. The domainname
portion of the global database name cannot contain the "-" character.
Note that it is not required for the database domain name to match your host network domain name; your host network domain name can have the "-" character.
If you create a Metadata Repository by running OracleAS RepCA on an Oracle9i Release 1 (9.0.1.5) database, then install Identity Management and configure it to use that Metadata Repository, some configuration assistants may hang. The problem most commonly occurs with the Oracle Ultra Search Configuration Assistant and the mod_osso
Configuration Assistant, at times of high system load.
To prevent this problem, disable the Resource Manager in the Metadata Repository before you start the Identity Management installation. You can accomplish this by commenting out the resource_manager_plan
entry in the init.ora
file in ORACLE_HOME
/admin/
SID
/pfile
.
If you use OracleAS Active Failover Cluster for your Metadata Repository, registered with Identity Management, make sure the database and Net listener are running on all AFC nodes before you install a middle-tier instance to use the Identity Management and AFC Metadata Repository. Otherwise, the middle-tier installation will fail with the error: Invalid Database or Database Not Running.
The following instances of Oracle Application Server 10g (9.0.4) and Oracle9i Application Server Release 1 (1.0.2.2.x) can coexist on the same computer:
1.0.2.2.x Minimal Edition and 9.0.4 J2EE and Web Cache
1.0.2.2.x Minimal Edition and 9.0.4 Portal and Wireless
1.0.2.2.x Minimal Edition and 9.0.4 Business Intelligence and Forms
1.0.2.2.x Standard Edition and 9.0.4 J2EE and Web Cache
1.0.2.2.x Standard Edition and 9.0.4 Portal and Wireless
1.0.2.2.x Enterprise Edition and 9.0.4 J2EE and Web Cache
1.0.2.2.x Enterprise Edition and 9.0.4 Portal and Wireless
The following instances of Oracle Application Server 10g (9.0.4) and Oracle9i Application Server Release 1 (1.0.2.2.x) can coexist on the same computer only after Oracle9iAS Discoverer has been shutdown in the Oracle9iAS Release 1 (1.0.2.2.x) Oracle home:
1.0.2.2.x Standard Edition and 9.0.4 Business Intelligence and Forms
1.0.2.2.x Enterprise Edition and 9.0.4 Business Intelligence and Forms
1.0.2.2.x Standard Edition and 9.0.4 Forms and Reports Services.
1.0.2.2.x Enterprise Edition and 9.0.4 Forms and Reports Services.
OC4J instance names and J2EE application names should not contain the Host name, the Oracle home or IP address of the computer containing the Oracle Application Server installation. In a clustered environment, this applies to the Host name, Oracle home, IP address of any Oracle Application Server installation in the cluster.For example, if your computer has the hostname of foo.company.com
, you should not create a new OC4J instance or J2EE application that is foo.company.com
or contains foo.company.com
. This rule also applies to the Oracle home directory path or the IP address of the computer.
The following Oracle Application Server install types can not be installed successfully when the server locale is Spanish:
J2EE and Web Cache
Portal and Wireless
The Oracle Universal Installer will fail if either of the listed install types are selected for installation in a Spanish locale. The Java Security Configuration Assistant fails and the jaznca.log contains java.lang.reflect.InvocationTargetException.
If you need to install these install types in a Spanish locale, perform the following steps after receiving the exception in the jaznca.log:
Backup the ORACLE_HOME
/config/ias.properties
file.
Edit the ORACLE_HOME
/config/ias.properties
file and replace the string "Caché de Web"
in Components field with "WebCache"
.
Save the file.
Retry the configuration Assistant from the Oracle Universal Installer session.
If the NLS_LANG
environment variable is set to a non-English locale before the Metadata Repository Configuration Assistant (MRCA) is invoked, the loading of the Oracle Workflow schema will return a PL/SQL error of:
ORA-01403 : "no data found"
Do not set NLS_LANG before MRCA is invoked. However, you can set NLS_LANG to american_america.us7ascii
before MRCA is invoked.
This section describes installation issues. It includes the following topics:
Section 3.2.3, "emracutil Script Contains Incorrect Value for Host Name"
Section 3.2.4, "targets.xml on Remote Hosts contain Incorrect ConnectDescriptor Information"
Section 3.2.6, "Net Listener Version for OracleAS Infrastructure 10g"
Section 3.2.8, "OPMN Configuration Assistant - Start Oracle Certificate Authority Failure"
Section 3.2.11, "Remove Registration Entries from Oracle Internet Directory"
Section 3.2.12, "Problem Using OracleAS RepCA on Existing Database"
Section 3.2.13, "Installation Failure Due to Unavailable Ports"
Section 3.2.14, "OracleAS Metadata Repository Only Installation Issue"
Section 3.2.15, "query_rewrite_integrity Must be Set to trusted or enforced for Running RepCA"
Section 3.2.16, "Mid-Tier with Oracle Internet Directory Installation Restriction"
Section 3.2.17, "Avoid Using Same OracleAS Metadata Repository During Multi Installation"
Section 3.2.19, "Erratic Installation Behavior with Input Method Editor System"
Section 3.2.21, "Migrate Data Before Performing Re-association"
Section 3.2.22, "Security Practices During Silent or Non-interactive Installations"
Section 3.2.24, "No Need to Register OracleAS Metadata Repository"
Section 3.2.25, "Incorrect Listing on Select Configuration Options Screen"
Section 3.2.26, "Use .bak Files for Non-interactive or Silent Installation"
Section 3.2.27, "OracleAS Metadata Repository Naming Restriction"
Section 3.2.28, "Oracle Internet Directory v1.0.2.2.x Coexistence with OracleAS Infrastructure 10g"
Section 3.2.29, "Tablespaces Created by OracleAS RepCA Set Up with Autoextend On"
Section 3.2.32, "Oracle10g Database Installations Require Manual Knowledge Base Install"
Section 3.2.35, "Help Information Not Available for Error Message"
Section 3.2.36, "Realm Value Not Used If You Log In as the Oracle Internet Directory Superuser"
Section 3.2.37, "Intel Xeon Processor Certified with Oracle Application Server Components"
Section 3.2.38, "Oracle Certificate Authority Configuration Assistant"
Your Oracle Application Server instance name cannot use the following characters:
#, @, |, &, ", :, ? and a blank space.
This only affects the OracleAS Infrastructure 10g installation in an Active Failover Cluster (AFC) environment.
An incorrect hostname value is entered in the EMD_URL
entry in $ORACLE_HOME/sysman/config/emd.properties
file on remote nodes of the AFC. To workaround this issue, run the ORACLE_HOME/bin/emracutil
command to update the hostname in the emd.properties
file on all hosts in the cluster. You run the command on the host where you ran the installer.
prompt> cd $ORACLE_HOME/binprompt> emracutil synchronize $ORACLE_HOME/sysman/config/emd.properties
This command uses the local host emd.properties
file as a template and substitutes the names of the hosts in the cluster in the file and copies the file to the respective hosts. After copying the file to all the hosts in the cluster, it reloads the agent on the remote hosts so that the agent reads the updated file.
This issue only affects the OracleAS Infrastructure installation in an AFC environment.
The $ORACLE_HOME/bin/emracutil
script contains an incorrect value for the HOST_NAME
variable on the remote hosts of the AFC.
Update the HOST_NAME
variable in the $ORACLE_HOME/bin/emracutil
script to the current host name.
This issue only affect the OracleAS Infrastructure installation in an AFC environment.
The $ORACLE_HOME/sysman/emd/targets.xml
on remote hosts of the AFC contains incorrect ConnectDescriptor
information for the oracle_ldap
target in the $ORACLE_HOME/sysman/emd/targets.xml
file. The ADDRESS_LIST
of the ConnectDescriptor
contains ADDRESSES
that point to the remote host.
To workaround this issue the ConnectDescriptor
must reference all hosts of the AFC.
Update the $ORACLE_HOME/sysman/emd/targets.xml
on remote hosts of the AFC with correct HOST
information for the ADDRESS_LIST
attribute.
In an AFC infrastructure installation, Oracle Delegated Administration Service (DAS) will be enabled only on the installation host.
In order to configure DAS on other hosts, perform the following workaround on each additional host:
Create an ldif
(das_enable.ldif
) file with the following entry:
--- BEGIN LDIF file contents--- dn: cn=Associated Mid-tiers,orclApplicationCommonName=DASApp, cn=DAS, cn=Products,cn=OracleContext changetype: modify add: uniquemember uniquemember: orclApplicationCommonName=<InstanceName>.<node>,cn=IAS Instances, cn=IAS,cn=Products, cn=OracleContext ---END LDIF file contents------
Run the following ldapmodify command:
ldapmodify -p <OIDPort> -h <Load Balancer Name> -D cn=orcladmin -w Instance Password> -v -f das_enable.ldif
DAS should now be configured on the additional hosts.
If you wish to configure the OracleAS Infrastructure 10g to use the Net listener from the 64-bit release of the Oracle database, the listener must be version 9.0.1.4 or higher (for the 9.0.1.x release of the database) or 9.2.0.3 or higher (for the 9.2.0.x release of the database).
If you declare a value for a variable at the command line when launching Oracle Universal Installer, the variable's value will not be retained if you subsequently back out of an install session.
For example, if you provide a filename and location for the public variable s_staticPorts
, this value will be reset to null if you go back to the Select Products screen and either select the same or another install type to install.
Oracle Universal Installer will reset all command line variables to null in anticipation of your redirection to another product where that variable's value may be incorrect or irrelevant. If you wish to retain these values, cancel your Oracle Universal Installer session and launch the session again with the appropriate command line parameters.
If you re-run the OPMN Configuration Assistant - start Oracle Certificate Authority may fail if your Oracle Certificate Authority instance is running.
To prevent this from happening, stop the Oracle Certificate Authority instance with the following command:
ORACLE_HOME/opmnctl/bin/opmnctl stopproc ias-component=OC4J instancename=oca
Then rerun OPMN Configuration Assistant - start Oracle Certificate Authority.
Turning Oracle Net Listener Cross registration on between instances of the AFC turns server side load balancing on. However, this breaks in OracleAS Metadata Repository and load balancing of new connections across the Oracle Application Server instances in the cluster is not even.
Alternatively, client side load balancing is sufficient for the kind of traffic anticipated for the AFC infrastructure.
Since listener cross registration is enabled by default in the OracleAS Metadata Repository, we must turn it off following installation.
To disable listener cross registration for the OracleAS Metadata Repository active failover instance execute the following commands:
Login into sqlplus
as sysdba
to any one of the infrastructure database instances deployed as part of the AFC installation.
Execute the following SQL
command:
SQL> alter system set remote_listener='' scope=spfile;
Restart all Oracle Application Server instances.
OracleAS Metadata Repository registration with Oracle Internet Directory, using the runRepca -Register
option during installation by OracleAS RepCA creates a stack trace in the repca.log
file.
The generated stack trace is benign and can be ignored.
If you use the OracleAS RepCA to register an OracleAS Metadata Repository and the database repository is subsequently deleted, the registration entries must be removed from the Oracle Internet Directory associated with the database repository.
Subsequent attempt to run the OracleAS RepCA against a database repository having the same name and using the same Oracle Internet Directory will fail.
After you have removed the registration entries from Oracle Internet Directory, re-run the OracleAS RepCA with the -REGISTER
option.
When using OracleAS RepCA on an existing database, you will encounter the Register with Oracle Internet Directory screen during installation. The registration validation will hang if you either:
check the SSL check box and provide a non-SSL port for registration.
uncheck the SSL check box and provide a SSL port for registration.
To workaround this issues, when the busy bar dialog appears, press the Cancel button. You must then rectify the problem by either:
checking the SSL check box and providing a SSL port for registration.
unchecking the SSL check box and providing a non-SSL port for registration.
If you are installing Oracle Application Server on a computer that has ports unavailable in the specified port range, the installation will fail during the configuration phase of the install.
Before you install Oracle Application Server, confirm that at least one port in the recommend range for each Oracle Application Server component is available.
Please refer to the Oracle Application Server 10g Administrator's Guide for more port information.
When you perform an OracleAS Metadata Repository only installation without Oracle Internet Directory registration, you will encounter an installation screen asking if you would like to register your OracleAS Metadata Repository with an existing Oracle Internet Directory. If you mistakenly choose to register the OracleAS Metadata Repository, you cannot return to the registration screen and change to the option which skips the registration. You must exit the current installation and restart Oracle Universal Installer.
Otherwise, if you continue the mod_osso
Configuration Assistant will fail at the end of the OracleAS Metadata Repository only installation.
If query_rewrite_integrity
is not set properly in the database initialization parameters, OracleAS RepCA will give an error that this parameter must be set to "trusted". However, OracleAS RepCA will function properly if this parameter is set to either "trusted" or "enforced".
If you perform an installation of Oracle Application Server middle-tier and you specify that components connect to Oracle Internet Directory only through SSL connections, you will be unable to expand your middle-tier installation at a later time.
For example: you will be unable to expand from a J2EE and Web Cache install type to a Portal and Wireless install type.
If you perform a simultaneous multi, more than one, installation of a Portal and Wireless or Business Intelligence and Forms install type using the same OracleAS Metadata Repository you may see the following error message from the OracleAS Portal home page:
Unexpected error encountered in wwsec_app_priv.process_signon (User-Defined @ Exception) (WWC-41417) An exception was raised when accessing the Oracle Internet Directory: 49: Invalid credentials Details Operation: dbms_ldap.simple_bind_s
Oracle recommends performing the installation one after the other, not simultaneously.
The repCA/repca/clean/cleanMR
script on the OracleAS RepCA/Utilities CD is intended to be used in cases where a OracleAS configuration assistant has failed and you wish to return your database to its original state. The cleanMR
script drops various user schemas. Therefore, make sure all users are disconnected from the database before running the script.
When you install Oracle Application Server on a system using an Input Method Editor (IME), Oracle Universal Installer may not start properly or crash. (Languages that use an IME are typically multibyte Asian languages.)
If you are encountering this problem, please obtain a patch for bug 3293516 from Oracle support. A readme file that accompanies the patch contains installation instructions.
The Oracle Universal Installer checks for minimum operating system requirements. One type of requirement is system parameters. If you set a system parameter to use a different value, then replace the current value with the value in the system parameter file. The system parameter file is located in /etc/system
.
In the system parameter file, do not comment out the existing line for the system parameter and add a new line. Oracle Universal Installer will not recognize the existing line as a comment line and will use the value on the comment line. An error will occur when Oracle Universal Installer checks minimum operating system requirements.
If your installation involves the following scenario:
Install OracleAS Metadata Repository on computer 1
Install Oracle9iAS Infrastructure Identity Management components on computer 2 and associate the component with the OracleAS Metadata Repository on computer 1
Install Oracle Application Server mid-tier on computer 3 and associate the components with the Identity Management installation on computer 2 and the OracleAS Metadata Repository on computer 1
Install an additional OracleAS Metadata Repository on computer 4
Following this installation configuration you will be able re-associate the Identity Management components on computer 2 and the Oracle Application Server mid-tier on computer 3 with the OracleAS Metadata Repository on computer 4 using Oracle Enterprise Manager.
However, you must migrate the data on computer 2 and computer 3 to computer 4 before performing the re-association steps with Oracle Enterprise Manager.
When installing Oracle Application Server in silent or non-interactive mode, you must supply a text response file to the Oracle Universal Installer. The response file provides the relevant inputs for your installation. One of the inputs in the response file that is required is your installation password. The password information must be in clear text.
To address potential security issues regarding the response file password, Oracle recommends the following security practice when using response files for installation:
Permissions on the response files should be set so that they are readable only by the operating system user who will be performing the silent or non-interactive installation.
If possible, the response files should be removed from the system after the silent or non-interactive installation is completed.
If you are performing a OracleAS Metadata Repository installation in silent or non-interactive mode, then the install will create the following two log files:
ORACLE_HOME/admin/<ORACLE_SID>/create/<ORACLE_SID>.log
ORACLE_HOME/cfgtoollogs/<ORACLE_SID>.log
where <ORACLE_SID>
is the value of your ORACLE_SID
.
The two listed log files contain database password information. They should be removed from the system if possible after you have reviewed their contents.
The two log files are not required for operation of OracleAS Metadata Repository.
To determine the minimum value for the semmns parameter:
If you are installing the OracleAS Metadata Repository on a computer that is not already running an Oracle database (that is, the OracleAS Metadata Repository will be the only Oracle database running on the computer), set the semmns parameter to a minimum of 256.
If you are installing the OracleAS Metadata Repository on a computer that is already running an Oracle database, set the semmns parameter to the sum of the processes initialization parameter for each Oracle database (including the OracleAS Metadata Repository), adding the largest one twice, and then adding an additional 10 for each database.
The default value of the processes parameter for the OracleAS Metadata Repository database is 150.
Example: The computer is already running an Oracle database, and its processes parameter is set at 200. In this case, you must set the semmns parameter to at least 770:
Sum of the processes parameter for all Oracle database: 200 for the existing database + 150 for the OracleAS Metadata Repository that you are installing = 350
Add the largest one twice: 200 + 200 = 400
Add 10 for each database: 10 + 10 = 20
Total: 350 + 400 + 20 = 770
To determine the value of the processes parameter for an Oracle database, run the following command in SQL*Plus:
@ prompt> sqlplus "sys/password as sysdba" SQL> show parameters processes
@ password
specifies the password for the SYS user.
You do not need to register OracleAS Metadata Repository when it is created using the OracleAS RepCA and it is used solely for Managed Oracle Application Server clusters or Central Management.
The Select Configuration Options screen that appears during installation of OracleAS Metadata Repository provides the ability to select High Availability Addressing. This is an incorrect; the High Availability Addressing is not available through an OracleAS Metadata Repository installation.
For non-interactive or silent installations of Oracle Application Server you must use the .bak file templates available in the stage/Response directory on Disk1 of your Oracle Application Server CD-ROM. The .bak response file templates are available for the following install types:
Portal and Wireless (oracle.iappserver.iapptop.Portals.bak
)
Business Intelligence and Forms (oracle.iappserver.iapptop.Business.bak
)
OracleAS Infrastructure 10g: Identity Management and OracleAS Metadata Repository (oracle.iappserver.infrastructure.Infrastructure.bak
)
OracleAS Infrastructure 10g: Identity Management (oracle.iappserver.infrastructure.Infrastructure_ID.bak
)
OracleAS Infrastructure 10g: OracleAS Metadata Repository (oracle.iappserver.infrastructure.Infrastructure_Meta.bak
)
OracleAS Developer Kits 10g (oracle.iappserver.devcorner.DevKit.bak
)
The database name used for the OracleAS Metadata Repository cannot have either the name PORT or HOST, in uppercase, embedded in it. An Oracle Application Server mid-tier installation will fail with an error message of "Error:*** Alert: Error validating repository on multiple hosts and ports. A database hostname or port is missing. ***."
Your Oracle Internet Directory v1.0.2.2.x may be become inoperable following installation of OracleAS Infrastructure 10g on the same computer. If you are running an Oracle 8.1.7 Database and an Oracle Internet Directory v1.0.2.2.x on a computer on which you are installing OracleAS Infrastructure 10g, the Oracle 8.1.7 listener and the Oracle Application Server v9.0.4 listener will not be able to co-exist. During the OracleAS Infrastructure 10g installation, Oracle Universal Installer will prompt you to stop the Oracle 8.1.7 listener or to change the Oracle 8.1.7 listener port to something other than port 1521. If the Oracle 8.1.7 listener port is changed, then the Oracle Internet Directory v1.0.2.2.x may not start after the OracleAS Infrastructure 10g installation.To workaround this problem shut down Oracle 8.1.7 listener during the OracleAS Infrastructure 10g installation.
The tablespaces created by Oracle Application Server Repository Creation Assistant (OracleAS RepCA) are set up with autoextend on. The tablespaces will grow automatically in size if needed.
If this is not desired behavior and you do not want the tablespaces to grow in size automatically, you can turn off autoextend on the tablespaces created by OracleAS RepCA.
If you plan to use OracleAS RepCA to register the Metadata Repository with Oracle Internet Directory in SSL mode, you need to apply patch number 3143899 to the database first. This patch is required if your database is version 9.2.0.4.You can download the patch from OracleMetaLink (http://metalink.oracle.com
).Instructions for installing the patch can be found in the README for the patch.
If you use the Repository Creation Assistant (RepCA) to install the Application Server metadata repository, including the OracleAS Portal repository, in a Customer Database, you must manually configure SQL*Net settings, so that the Infrastructure Database for the ORASSO_PS schema can be contacted.
If you do not perform this configuration, errors are displayed in OracleAS Portal when using the OracleAS Single Sign-On (SSO) administration portlet.
The error is caused by the DB link used by OracleAS Portal to connect to the ORASSO_PS schema for external application functionality. The DB link is resolved using the SQL*Net settings configured in the database home where the Application Server metadata repository resides. (In this case the Portal schema (part of the Application Server metadata repository) is installed in a separate standalone database).As a workaround, manually update the sqlnet.ora file located at
$ORACLE_HOME/network/admin/
This is in the database home where the Application Server metadata repository is installed. Add LDAP
to the NAMES.DIRECTORY_PATH
entry as follows:
NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, ONAMES, HOSTNAME)
You must manually install the Knowledge Base from the Companion CD under the following circumstances:
Before installing OracleAS Portal on a new Oracle10g database.
After upgrading an existing OracleAS Portal repository to run on an Oracle10g database.
If the Knowledge Base is not installed, the following error is displayed when searching in OracleAS Portal with the Oracle Text Enable Themes and Gists option selected:
Error: The file could be not filtered. (WWS-32024)
The requirement to install the Knowledge Base manually is omitted from the cause and action message text.
If you plan to use an Oracle 9.0.1.x RAC database you need to apply Automatic Release Update (ARU) patch 5147755.
To fix this issue, you must download the patch from OracleMetalink (http://metalink.oracle.com
).The ARU patch number is 5147755.
If you receive the following error message:
Error ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
while installing the OracleAS Metadata Repository in a Release 2 (9.2.0.4) Real Application Clusters database that uses raw devices, complete the following steps:
Apply one of the following patches to your database:
patch 3229141
The ARU numbers for this patch are:
ARU 5211167 for Solaris Operating System (SPARC 32-bit)
ARU 5564273 completed for Solaris Operating System (SPARC 64-bit)
the 9.2.0.5 patchset (patch number 3501955)
You can download these patches from OracleMetalink (http://metalink.oracle.com
)
Verify that the space management for the UNDO tablespace is set to AUTO.
You can do this by running the following SQL statement:
SQL> select tablespace_name, status, segment_space_management from dba_tablespaces;
Rerun the OracleAS Repository Creation Assistant to load the metadata repository in your database.
When you arrive at the Oracle Managed Files Directory screen during OracleAS RepCA installation and do not select a disk group, when you click Next, an error message will appear. If you click on Help on this error message display, no Help information will be displayed. Clicking on the Help button will produce a Java error.
In OracleAS RepCA, if you log into Oracle Internet Directory that contains multiple realms as the superuser (cn=orcladmin
), the realm value is not used because the superuser does not belong to any realm. The realm value is used only if you log in using a simple name.
The Intel Xeon processor is certified for Oracle Application Server. However, during installation, the Oracle Universal Installer pre-requisite check fails on a computer using the Xeon processor. You can ignore this pre-requisite check failure and continue with the installation of Oracle Application Server.
The description for the Oracle Certificate Authority (OCA) Configuration Assistant is missing from Table B-1 in the Oracle Application Server 10g Installation Guide.
The OCA Configuration Assistant configures a self signed certificate authority, integrated with Oracle Single Sign-On for authentication.
Oracle Internet Directory, OracleAS Metadata Repository, the Repository API and OracleAS Single Sign-On must be configured before you can use this configuration assistant.
The log files for this configuration assistant are located in the following location:
ORACLE_HOME/cfgtoollogs/configtools<time.stamp>.log
This section describes deinstallation issues. It includes the following topic:
If you deinstall the OracleAS Infrastructure 10g Identity Management Install Type, you may observe the following error message:
"Error: can not remove, there is no ias component with that ID :OID"
The error message is benign and you can proceed with the deinstallation.
Following deinstallation of OracleAS Developer Kits 10g, the following error messages may be present in the InstallActions.log
file:
The following error messages were seen in the InstallActions log file: ------------------------------------------------------------------- Exception in thread "main" java.util.zip.ZipException: No such file or directory at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:112) at java.util.jar.JarFile.<init>(JarFile.java:117) at java.util.jar.JarFile.<init>(JarFile.java:55) ------------------------------------------------------------------ ADMN-100999 See base exception for details. Base Exception: java.lang.ClassNotFoundException:oracle.sysman.emSDK.emd.dtd.TargetInstance . See base exception for details. java.lang.ClassNotFoundException: oracle.sysman.emSDK.emd.dtd.TargetInstance at java.net.URLClassLoader$1.run(URLClassLoader.java:198) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:186) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) -------------------------------------------------------------------- Exception in thread "main" java.lang.NoClassDefFoundError: oracle/ias/opmn/smiplugin/CompDeInst .
Additionally, the following Oracle Application Server processes remain up and running:
OPMN
EMWD
$ORACLE_HOME/jdk/bin/java -Xmx256m -DORACLE_HOME=/private1/iasins
The error messages and the running Oracle Application Server processes are benign; the deinstallation of OracleAS Developer Kits 10g was successful.
You can stop the ongoing Oracle Application Server using the following command:
kill -9 <process_id>
This section describe post installation issues. It includes the following topic:
Section 3.4.2, "Reset Passwords for Oracle Application Server Components"
Section 3.4.3, "Do Not Configure HTTP SSL Port Using the staticport.ini File"
Section 3.4.5, "Manually Start OC4J in OracleAS Infrastructure 10g Home Instance"
Section 3.4.6, "No Need to Specify XServer or DISPLAY Settings"
After you configure Oracle Application Server components using Oracle Enterprise Manager, upon executing a start or stop command from the Oracle Application Server component page an error message is displayed.
To avoid this problem, start, and then stop the Application Server Control following configuration of the Oracle Application Server component using the following commands:
emctl stop iasconsole emctl start iasconsole
By default, all passwords in Oracle Application Server 10g (with the exception of the OracleAS Metadata Repository passwords) are set to be the same as the Oracle Application Server instance password. For security reasons, Oracle recommends that after installation completes, the Oracle Application Server administrator reset the passwords of the various server components to have different values.
Please refer to the Oracle Application Server Documentation Library for details on how to properly alter the passwords for the components of Oracle Application Server which you have installed.
Do not configure HTTP SSL port using the staticport.ini
file. Apache is not initially configured for SSL.
You can use port 443 using the staticports.ini
file using the steps described in the Oracle Application Server 10g Administrator's Guide.
OracleAS Web Cache requires the seminfo_shmmin
kernel parameter to be set to 1. Otherwise OPMN will fail to start OracleAS Web Cache. Set seminfo_shmmin
to 1 in your /etc/system
file. After you set the parameter, reboot your computer.
The OC4J instance in an OracleAS Infrastructure 10g home instance does not start using opmnctl startall
or the startall command in the Oracle Enterprise Manager Central Console. You must manually start the OC4J instance.
In Oracle Application Server 10g, you do not need to specify your XServer or DISPLAY settings in the opmn.xml
file.
If you wish to specify your XServer or DISPLAY setting comment out the following file element:
-Djava.awt.headless=true
The default FBR diskcache size is set as 32MB in the ORACLE_HOME/dcm/config/dcmCache.xml
file. The default size may not be sufficient for deploying large EAR file (example: >10MB).
In the event where FBR diskcache size is not sufficient, application deployment would fail with the following error message:
<SUPPL_DETAIL><![CDATA[oracle.ias.sysmgmt.exception.CachePersistenceException: The exception 202001, has occurred in the cache layer of the persistence manager "Persistence operation failed.Root Cause: The exception 202500, has occurred in the cache layer of the persistence manager"An exception occurred in the method CacheAccess.get CacheAddress". Resolution: check the details of the base exception.". Resolution: Please, refer to the base exception for the details: at oracle.ias.sysmgmt.persistence.cache.CacheTxnManager.commitTx(Unknown Source) at oracle.ias.sysmgmt.persistence.cache.CachePersistence.commitTx(Unknown Source) at oracle.ias.sysmgmt.persistence.PersistenceManager.commitTx(Unknown Source) at oracle.ias.sysmgmt.task.TaskMaster.sync_evaluate(Unknown Source) at oracle.ias.sysmgmt.task.TaskMaster.internal_evaluate(Unknown Source) at oracle.ias.sysmgmt.task.RemoteEvaluate.execCommand(Unknown Source) at oracle.ias.sysmgmt.task.DaemonWorker.run(Unknown Source)
To workaround this problem:
Shutdown the Application Server Control, the dcmctl
shell, and the dcm-daemon
.
rm -rf $ORACLE_HOME/dcm/diskcache/*
Update ORACLE_HOME/dcm/config/dcmCache.xml file and increase the default value of the <diskcache>
element from 32 to 256.
Start the dcm-daemon
, the dcmctl
shell, and the Application Server Control.
Repeat the steps for other Oracle Application Server instances.
This section describes upgrade issues. It features the following topic:
Section 3.5.1, "Confirm ORACLE_HOME value before Performing Upgrade"
Section 3.5.4, "Some DAS Dependent Applications May Not Work Following Upgrade"
Section 3.5.5, "Upgrade of Oracle9iAS 9.0.2 or 9.0.3 Middle Tiers"
Section 3.5.6, "Verifying the Execution of mrc.pl during the Metadata Repository Upgrade"
Section 3.5.7, "Prerequisite Before Upgrading an OracleAS Infrastructure 9.0.2 to 9.0.4"
During upgrade of an Oracle9iAS Infrastructure 9.0.2 to OracleAS Infrastructure 10g-Identity Management, the Oracle Data Migration Assistant may display a Succeeded message even though the upgrade did not occur.
To ensure a successful upgrade, make sure that the database directory contains the same ORACLE_HOME value as the value listed in the /var/opt/oracle/oratab
file.
When you perform an Identity Management upgrade of your Oracle9iAS Infrastructure 9.0.2 database, you must be logged in as a member of the DBA group for the database.
If you do not login you may see the following error message in the $904_ORACLE_HOME/assistants/dbma/logs/trace.log
file:
oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-01031: insufficient privileges
Perform the following steps to upgrade the Oracle Workflow schema for the OracleAS Metadata Repository:
Determine the password for the Workflow (OWF_MGR
) schema using the following command:
ldapsearch -h oidhostname -p oidport -D cn=orcladmin -w passwd -b "orclReferenceName=globalDatabaseName,cn=IAS Infrastructure Databases, cn=IAS,cn=Products,cn=oraclecontext" "orclresourcename=OWF_MGR" orclpasswordattribute
Use the following values in the command:
oidhostname
- name of the computer running Oracle Internet Directory. For example: dbmachine.mydomain.com
.
oidport
- port number on which Oracle Internet Directory is listening. For example: 389
.
passwd
- password for orcladmin
. For example: welcome1
.
globalDatabaseName
- global database name for the Oracle9iAS Metadata Repository used by Oracle9iAS 9.0.2 Single Sign-On. This value is stored in the InfrastructureDBCommonName
field in the ORACLE_HOME/config/ias.properties
file, where ORACLE_HOME is the Oracle home directory for the Oracle9iAS Infrastructure 9.0.2.
Run the workflow upgrade script from the OracleAS RepCA/Utilities CD at repCA/wf/install/wfupg.csh
. The script has the following syntax:
wfupg.csh sys_password repca_home ORACLE_HOME "connect_descriptor" log_directory owf_mgr_password
where the parameters are:
sys_password
- password of the SYS user in the database
repca home
- the repCA directory of the OracleAS RepCA/Utilities CD, <mount point>/repCA
ORACLE_HOME
- the ORACLE_HOME of the Oracle9iAS 9.0.2 Infrastructure
connect_descriptor
- the Oracle Net connect descriptor for the Oracle9iAS 9.0.2 Infrastructure database. This can be either a full net descriptor, or an alias from the $ORACLE_HOME/network/admin/tnsnames.ora
file that points to the Infrastructure database.
log_directory
- directory where the workflow.log
file will be written.
owf_mgr_password
- password for the OWF_MGR
schema obtained from step 1.
Recompile all plsql procedures in the database by running the script at $ORACLE_HOME/rdbms/admin/utlrp.sql
as the SYS user.
If Oracle Internet Directory is upgraded from version 9.0.2 to the Identity Management version 9.0.4, and DAS existing in the midtier is the 9.0.2 version, then user and group management functionality's from some DAS dependent applications such as OracleAS Portal may not work. This problem is resolved by the installing version 9.0.4 DAS to replace the version 9.0.2 DAS.
This issue often occurs if there is a time lag before replacement of the version 9.0.2 DAS to the version 9.0.4 DAS and Oracle Internet Directory is upgraded to version 9.0.4.
To resolve this issue, execute the following steps:
Create an ldif
file called das904_to_902.ldif
with following data:
dn: cn=Create User, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppCreateUserInfoAdmin dn: cn=Edit User, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppEditUserSpecifyAdmin dn: cn=Edit Group, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppEditGroupSpecifyAdmin dn: cn=Create Group, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppCreateGroupInfoAdmin dn: cn=DeleteUserGivenGUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppDeleteUserAdmin dn: cn=User Privilege Given GUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppUserPrivAdmin dn: cn=Group Privilege Given GUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppGroupPrivAdmin dn: cn=DeleteGroupGivenGUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppDeleteGroupAdmin dn: cn=Edit GroupGivenGUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppEditGroupAdmin dn: cn=DeleteUser, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppDeleteUserSpecifyAdmin dn: cn=User Privilege, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppUserPrivSpecifyAdmin dn: cn=DeleteGroup, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppDeleteGroupSpecifyAdmin dn: cn=Edit UserGivenGUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppEditUserAdmin dn: cn=Group Privilege, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/admin/AppGroupPrivSpecifyAdmin dn: cn=DAS Application, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/mypage/ViewMyPage
Run the following ldapmodify
command:
$ORACLE_HOME/bin/ldapmodify -h <OID host> -p <OID port> @ -D <OID superuser> -w <OID superuser password> -v -f das904_to_902.ldif
After version 9.0.2 DAS is replaced by version 9.0.4 DAS (Oracle Internet Directory is also version 9.0.4), create an ldif
file called das902_to_904.ldif
with following data
dn: cn=Create User, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/user/AppCreateUserInfoAdmin dn: cn=Edit User, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/user/AppEditUserSpecifyAdmin dn: cn=Edit Group, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/group/AppEditGroupSpecifyAdmin dn: cn=Create Group, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/group/AppCreateGroupInfoAdmin dn: cn=DeleteUserGivenGUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/user/AppDeleteUserAdmin dn: cn=User Privilege Given GUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/user/AppUserPrivAdmin dn: cn=Group Privilege Given GUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/group/AppGroupPrivAdmin dn: cn=DeleteGroupGivenGUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/group/AppDeleteGroupAdmin dn: cn=Edit GroupGivenGUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/group/AppEditGroupAdmin dn: cn=DeleteUser, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/user/AppDeleteUserSpecifyAdmin dn: cn=User Privilege, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/user/AppUserPrivSpecifyAdmin dn: cn=DeleteGroup, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/group/AppDeleteGroupSpecifyAdmin dn: cn=Edit UserGivenGUID, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/user/AppEditUserAdmin dn: cn=Group Privilege, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oracle/ldap/das/group/AppGroupPrivSpecifyAdmin dn: cn=DAS Application, cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext changetype: modify replace: orcldasurl orcldasurl: oiddas/ui/oiddashome
Run the following ldapmodify command:
$ORACLE_HOME/bin/ldapmodify -h <OID host> -p <OID port> @ -D <OID superuser> -w <OID superuser password> -v -f das902_to_904.ldif
During upgrade from Oracle9iAS 9.0.2 or 9.0.3 to Oracle Application Server 10g (9.0.4), the default managing Oracle9iAS 9.0.2 or 9.0.3 Oracle Enterprise Manager (Enterprise Manager) process must be shutdown instead of the Oracle9iAS 9.0.2 or 9.0.3 Enterprise Manager in the source instance.
For example, if there is an Oracle9iAS 9.0.2 Infrastructure and an Oracle9iAS 9.0.2 middle-tier on the same host, then the Oracle Enterprise Manager from the 9.0.2 Infrastructure will be the managing Enterprise Manager. In this case, Oracle9iAS 9.0.2 Infrastructure Enterprise Manager should be shutdown during the upgrade.
Oracle Application Server 10g (9.0.4.0.1) for Solaris introduced a new verification argument for the mrc.pl
script, which is used to upgrade the Metadata Repository Container from 9.0.2 to 9.0.4.
The mrc.pl
script is documented in both the Windows and UNIX versions of the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide. However, only the Windows version of the guide includes the steps for verifying the execution of the mrc.pl
script.
If you are using the UNIX version of the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide, review section 4.2.3, "Upgrading the Metadata Repository Container," and then use the following procedure to determine whether or not the mrc.pl has executed successfully, or whether or not it has been executed before:
Ensure that the database, listener, and Oracle Internet Directory server are running.
Ensure that the ORACLE_HOME
environment variable is set to <Infra_OH>
and the ORACLE_SID
environment variable is set to the Infrastructure database SID. If they are not, follow the instructions in Section 4.2.1, "Setting the Environment for Upgrading the Metadata Repository" in the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide.
Change directories to <repCA_CD>\repCA\mrc\upgrade
.
Use one of the following commands to determine whether the mrc.pl
has executed successfully, or whether it has been executed before:
If you are executing mrc.pl for New Schema Creation only, enter this command:
If you are executing mrc.pl for New Schema Creation and Oracle Internet Directory Entry Update:
<Infra_OH>/perl/bin/perl mrc.pl duv -dbpwd <SYS user password> -dspace <tablespace directory> -ousr <oid admin user name> -opwd <oid admin user password> -connstring <database connect string>
Note the "v" argument, which is included immediately after the "d" or "du" arguments to the mrc.pl
script. When you include the "v" argument, the script will provide information about whether or not the mrc.pl
script has been run before and whether or not it has run successfully.
If you have multiple Oracle9iAS instances (9.0.2x or 9.0.3) on a computer, then you must be careful when you upgrade an instance to 9.0.4 because all the instances on the computer share the same active Oracle Enterprise Manager.
You need to ensure that you do not deinstall an instance that contains the active Oracle Enterprise Manager.
Before you upgrade an instance on a machine that contains multiple Oracle9iAS instances:
Determine which Oracle9iAS instance contains the active Oracle Enterprise Manager.
Check the ACTIVE_EMD_HOME
entry in the /var/opt/oracle/emtab
file.
If the instance you want to upgrade contains the active Oracle Enterprise Manager, switch the active Oracle Enterprise Manager to a remaining instance.
If you have a remaining instance that is of Oracle9iAS 9.0.3, you must switch your active Oracle Enterprise Manager to that instance. Otherwise, you can switch to an instance that is of Oracle9iAS 9.0.2x:
prompt> ORACLE_HOME/bin/emctl switch home
This displays a dialog where you can select another Oracle9iAS instance that contains the active Oracle Enterprise Manager.
Alternatively, use the -silent
argument and provide the path to the Oracle home where the new active Enterprise Manager Web site resides:
prompt> ORACLE_HOME/bin/emctl switch home - silent <remaining_oracle_home>
You can now upgrade the instance to 9.0.4.
This section describes documentation errata. It includes the following topics:
Section 3.6.1, "Incorrect Link to OTN in Troubleshooting Chapter"
Section 3.6.2, "Optional: Increasing JVM Memory for Large OC4J Upgrades"
Section 3.6.5, "Missing Note in Oracle Application Server 10g Upgrading to 10g (9.0.4) Guide"
Section 3.6.6, "Mislabeled Command in Oracle Application Server 10g Upgrading to 10g (9.0.4) Guide"
Section 3.6.7, "Incorrect text in Oracle Application Server 10g Upgrading to 10g (9.0.4) Guide"
Section 3.6.8, "Incorrect Syntax in Oracle Application Server 10g Upgrading to 10g (9.0.4) Guide"
Section 3.6.10, "Incorrect Parameter in Example Non-interactive Response File"
Section 3.6.12, "Incorrect Information Regarding Configuring Data Sources"
Section 3.6.13, "Mislabeled Section in Oracle Application Server 10g Upgrading to 10g (9.0.4)"
The Troubleshooting chapter of the Oracle Application Server 10g Installation Guide provides an incorrect link to OTN. The correct link is:
http://otn.oracle.com/documentation/appserver10g.html
Section 3.2.2 Optional: Increasing JVM Memory for Large OC4J Upgrades of the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide indicates that the JavaVM property is in the <destination_ MT_OH>/ias/upgrade/Oc4jPlugin.cfg
file when it is actually <destination_MT_OH>/upgrade/Oc4jPlugin.cfg
file.
The following instructions are missing from the Oracle Application Server 10g Upgrading to 10g (9.0.4) Guide.
Follow these steps to create support for new schemas in the metadata repository:
Ensure that the database and listener are running.
Ensure that the ORACLE_HOME environment variable is set to <
Infra_OH
>
and the ORACLE_SID environment variable is set to the Infrastructure database SID. If they are not, follow the instructions in Oracle Application Server 10g Upgrading to 10g (9.0.4) Guide.
Change directories to <
repCA_CD
>\repCA\mrc\upgrade
.
Ensure that there is an existing directory with write permission enabled in which to create new database files for the new tablespaces. (You will specify this directory as part of the command to start the script.)
Issue this command:
<Infra_OH>\perl\5.6.1\bin\MSWin32-x86\perl mrc.pl d -dbpwd <SYS user password> -connstring <conn string> -dspace <dir>
where:
<
SYS user password
>
is the dba password
<
conn string
>
is the database connect string in the format host:port:SID
<
dir
>
is the directory in which you want to create the new database files that contain the new tablespaces
for example:
<
Infra_OH
>\perl\5.6.1\bin\MSWin32-x86\perl mrc.pl d -dbpwd "change_on_install" -connstring "mycompany.com:1521:iasdb2" -dspace c:\oracle1\mydir\ORA_IAS_902
You need not specify all of the above parameters on the command line. The script will prompt you to enter any parameters for which a default value is not available. For example, you may prefer not to type the password on the command line, but enter it only when prompted, so it is not displayed on the screen in clear text.
If creation of new schemas was successful, the following message appears:
Creation of new schemas was successful
Steps shown in Section 4.4.3.3.2 Executing the Schema Configuration Script of the Oracle Application Server 10g Upgrading to 10g (9.0.4) Guide should be as follows:
Follow these steps to configure Oracle Ultra Search to use the OracleAS Infrastructure 10g OracleHome.
Set the ORACLE_HOME environment variable to the <destination_Infra_OH>.
Set the ORACLE_SID environment variable to the OracleAS Infrastructure 10g database.
Change directories to <destination_Infra_OH>/ultrasearch/admin>.
Issue this command:
sqlplus "sys/<SYS user password> as sysdba"
Issue this command:
wk0config.sql <WKSYSPW> <JDBC_CONNSTR> <LAUNCH_ANYWHERE> <NET_SERVICE_NAME>
where:
<WKSYSPW>
is the password for the WKSYS
schema. If you don't know the password, then you can perform the following steps to obtain the password:
Start Oracle Directory Manager with the following command:
ORACLE_HOME/bin/oidadmin
Log in to Oracle Directory Manager as the orcladmin user.
In the System Objects frame, expand Entry Management, expand cn=OracleContext
, expand cn=Products
, expand cn=IAS
, expand cn=IAS Infrastructure Databases
, and expand the orclReferenceName for the Metadata Repository.
Select the OrclResourceName entry for schema WKSYS
.
In the Properties tab, you can view the password in the orclpasswordattribute
field.
<JDBC_CONNSTR>
is the JDBC connection string. Use the following format [hostname]:[port]:[sid]
if the database is not in a Real Application Clusters (RAC) environment. For example, machine1:1521:iasdb
. If the database is in a RAC environment, you should use the TNS keyword-value format rather than the [hostname]:[port]:[sid]
format. Because it allows connection to any node of the system. For example,
"(DESCRIPTION=(LOAD_ BALANCE=yes)(ADDRESS=(PROTOCOL=TCP)(HOST=cls02a)(PORT=3001))(ADDRESS=(PROTOCOL=TCP )(HOST=cls02b)(PORT=3001)))(CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)))"
Reference to the Oracle Net Services Reference Guide for more details on the syntax of the TNS entry.
<LAUNCH_ANYWHERE>
is the mode of the OracleAS Metadata Repository. Setting it to TRUE
indicates that the OracleAS Metadata Repository is in RAC mode. For this procedure, you should set it to FALSE
.
<NET_SERVICE_NAME>
is the network service name used by wk0config.sql
to establish the database connection. Setting it to ""
(empty string) when you run wk0config.sql
from the database host means there is no need to specify the network service name.
The following is an example for running the command in a non-RAC environment:
wk0config.sql welcome1 machine1:1521:iasdb FALSE ""
The following is an example for running the command in a RAC environment:
wk0config.sql welcome1 "(DESCRIPTION=(LOAD_BALANCE=yes)(ADDRESS=(PROTOCOL=TCP)(HOST=cls02a)(PORT=3001))(ADDRESS=(PROTOCOL= TCP)(HOST=cls02b)(PORT=3001)))(CONNECT_DATA=(SERVICE_NAME=s ales.us.acme.com)))" FALSE ""
Note: Completing this procedure resets the crawler cache directory and crawler log directory to the default values. You can use the Oracle Ultra Search Administration tool to update these values. |
Following Step 6 in section 5.3 the following note is missing and shown below:
Note: The 9.2.0.4 metadata repository is in the original 9.2.0.4 Oracle Internet Directory database Oracle Home. So you can connect from the 9.0.4 Oracle Internet Directory Oracle Home only using the connect identifier. For example:
where |
Section 5.4.1.4 in the Oracle Application Server 10g Upgrading to 10g (9.0.4) Guide contains the following instruction:
Issue this command:
@ sqlplus ods/<ods password>@<net service name for OID database>
@ <destination_Infra_OH>/ldap/admin/oidpu904.sql
for example:
sqlplus ods/welcome1@iasdb@<destination_Infra_OH>/ldap/admin/oidpu904.sql
This should read as:
Issue this command:
@ sqlplus ods/<ods password> @<net service name for OID database> @<destination_Infra_OH>/ldap/admin/oidpu904.sql
for example:
sqlplus ods/welcome1@iasdb @<destination_Infra_OH>/ldap/admin/oidpu904.sql
Section 3.5.3, "Starting the OracleAS Upgrade Assistant To Use Multiple Oracle Universal Installer Inventory Locations" contains the follow incorrect paragraph:
"The Oracle Universal Installer creates an inventory file, /var/opt/oracle/oraInst.loc
, when it installs Oracle products. This file contains the location (full path) of the Oracle Application Server instance, and the group name of the user who installed it. The OracleAS Upgrade Assistant populates its source Oracle home drop-down list (shown in Figure 3–2, "OracleAS Upgrade Assistant Oracle Homes Screen") with the information from this file, the default inventory file. Additional inventory files are sometimes created after installation for the purpose of managing Oracle homes independently (thereby circumventing the Oracle Universal Installer features that track all Oracle homes in a single inventory)."
It should read:
"The Oracle Universal Installer creates an inventory file, /var/opt/oracle/oraInst.loc
(or etc/orainst.loc on Linux and AIX)
, when it installs Oracle products. This file contains the location (full path) of the Oracle Universal Installer directory, and the group name of the user who installed it. The OracleAS Upgrade Assistant populates its source Oracle home drop-down list (shown in Figure 3–2, "OracleAS Upgrade Assistant Oracle Homes Screen") with the information from this directory, the default inventory. Additional inventories files are sometimes created after installation for the purpose of managing Oracle homes independently (thereby circumventing the Oracle Universal Installer features that track all Oracle homes in a single inventory)."
Section 4.4.3.3.1, "Installing the Java Runtime Environment (JRE) 1.4 and Configuring Oracle Ultra Search to Use JRE 1.4" of the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide, contains the following incorrect syntax for the <new java execution path>:
<JRE 1.4 directory>/jre/1.4.1/bin/java -ms16m -mx256m -Djava.library.path=<destination_Infra_OH>/lib
The syntax should be:
<JRE 1.4 directory>/jre/1.4.1/bin/java -ms16m -mx256m -Djava.library.path=<source_Infra_OH>/lib
Table 4-4, "Values for Kernel Parameters" in the Oracle Application Server 10g Installation Guide contains the following four incorrect shared memory values in the second column of the table, "Line in /etc/system
showing minimum value ":
set shmsys:seminfo_shmmax=4294967295
set shmsys:seminfo_shmmin=1
set shmsys:seminfo_shmmni=512
set shmsys:seminfo_shmseg=150
The values should be:
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=512
set shmsys:shminfo_shmseg=150
A file listing in Section D.5.1.3, "Portal and Wireless" of the Oracle Application Server 10g Installation Guide contains the following incorrect file parameter:
szl_RepositoryUserInput={"domain.com:1521:iasdb:iasdb.domain.com"}.
It should be:
szl_RepositoryUserInput={"hostname.domain:1521:iasdb:iasdb.domain"}
The procedure in section C.1.8 "Removing Oracle Ultra Search Entries from Oracle Internet Directory", in the Oracle Application Server 10g Installation Guide needs to be peformed only if you are deinstalling the OracleAS Infrastructure. Do not perform this procedure if you are deinstalling middle tiers.
In the Oracle Application Server 10g Migrating from WebLogic guide, in the section titled "Configuring Data Sources in the Application Server," the parameter pooled-location
is described. ejb-location
should be used instead of pooled-location
.
In the Oracle Application Server 10g Migrating from WebSphere guide, in the section titled ""Migrating JDBC Applications"," the parameter pooled-location
is described. ejb-location
should be used instead of pooled-location
.
Section 5.4.1.4, "Recommended Performance Enhancement Tasks" of the Oracle Application Server 10g Upgrading to 10g (9.0.4) is mislabeled. Section 5.4.1.4 should be titled "Requirements for Upgrade Task". The steps listed in Section 54.1.4 must be completed; otherwise your instance of Oracle Identity Management will not function correctly.
In Chapter 5, Section 5.8, "The ias_admin User and Restrictions on its Password" of the Oracle Application Server 10g Installation Guide, there is reference to the Oracle Application Server 10g Administrator's Guide for the steps to reset the administrator (ias_admin
) password. Unfortunately, this information reference is invalid.
The steps to resetting the ias_admin
password are as follows:
Log in as the user who installed the Oracle Application Server instance:
Stop the Application Server Control.
On UNIX systems, enter the following command in the Oracle home of the application server instance:
ORACLE_HOME/bin/emctl stop iasconsole
On Windows systems, use the Services control panel to stop the Application Server Control service.
Locate and open the following file in a text editor:
ORACLE_HOME/sysman/j2ee/config/jazn-data.xml
Locate the line that defines the credentials property for the ias_admin
user.
The following example shows the section of jazn-data.xml
with the encrypted credentials
entry in boldface type:
<realm>
<name>enterprise-manager</name>
<users>
<user>
<name>ias_admin</name>
<credentials>{903}buG0lUsQqTq0nQjdaKQRECL1kbs192mP</credentials>
</user>
.
.
Replace the existing encrypted password with the new password.
Be sure to prefix the password with an exclamation point (!). For example:
<credentials>!mynewpassword123</credentials>
The password for the ias_admin
user should conform to following guidelines:
The minimum length is five alphanumeric characters.
At least one of the characters must be a number.
Passwords must be shorter than 30 characters.
Passwords can contain only alphanumeric characters from your database character set, the underscore (_), the dollar sign ($), and the number sign (#).
Passwords must begin with an alphabetic character. It cannot begin with a number, the underscore (_), the dollar sign ($), or the number sign (#).
See Also: "The ias_admin User and Restrictions on its Password" in the Oracle Application Server 10g Installation Guide |
Start the Application Server Control.
After the restart, the Application Server Control will use your new Administrator (ias_admin
) password, which will be stored in encrypted format within the jazn-data.xml
file.