F.4 deinstallation problems and solutions, Deinstallation problems, F.4.1 – Oracle B32100-01 User Manual
Page 249: Obsolete partn, Section f.4.1, "obsolete partner urls
Deinstallation Problems and Solutions
Troubleshooting
F-11
Solution
Perform the following steps to correct the problem:
1.
Start Oracle Directory Manager.
prompt> cd ORACLE_HOME/bin
prompt> ./oidadmin
2.
Navigate to the entry:
orclApplicationCommonName=ORASSO_SSOSERVER,cn=SSO,cn=Products,cn=OracleContext
3.
Remove the instance name of the failed middle tier from the values of the attribute
labeledURI
.
4.
If there are no more instance names listed in the values of the attribute
labeledURI
, then remove the entry:
orclApplicationCommonName=ORASSO_SSOSERVER,cn=SSO,cn=Products,cn=OracleContext
F.4 Deinstallation Problems and Solutions
This section describes common problems related to deinstallation:
■
■
Section F.4.2, "Unable to Reuse Instance Name of a Deleted Instance"
■
Section F.4.3, "Unable to Reuse Database Name"
■
Section F.4.4, "Deconfiguration Failed on Distributed OracleAS Cluster (Identity
Management)"
F.4.1 Obsolete Partner URLs Still Remain on the OracleAS Single Sign-On
Administration Screen
Problem
After deinstallation, some partner application entries that are obsolete remain on the
OracleAS Single Sign-On Administration screen.
Solution
Run the command to de-register the entries for the obsolete partner applications. The
command is similar to the command for registration, except that the -update_mode
parameter is set to DELETE.
Make sure your LD_LIBRARY_PATH environment variable contains $ORACLE_
HOME/lib32
, and that your LD_LIBRARY_PATH_64 environment variable contains
$ORACLE_HOME/lib
. Then run the command (all on one line):
prompt> $ORACLE_HOME/jdk/bin/java
-jar $ORACLE_HOME/sso/lib/ossoreg.jar
-oracle_home_path $ORACLE_HOME
-site_name hostname.domain
-config_mod_osso TRUE
-mod_osso_url http://hostname.domain:port
-u userid
-update_mode DELETE