Script to Gather Information Required to Debug Single Sign-On Issues
(Doc ID 339016.1)
Last updated on AUGUST 01, 2024
Applies to:
Oracle Application Server Single Sign-On - Version 9.0.4 to 10.1.4 [Release 10gR1 to 10gR3]Information in this document applies to any platform.
Goal
In order to speed up the resolution of Single Sign-On SSO issues, the Oracle Support team has developed a perl script that can be used to collect relevant configuration and log files to aid in the troubleshooting process of SSO issues.
This perl script can be run in 3 different modes:
- The -collect parameter can be used to capture only the configuration and log files without having to enable/disable full debug mode in the various components. The script is often times run in this mode to see if the problem can be diagnosed without the need to fully enable debug mode. This is the default mode if no parameters are supplied.
- Supplying the -dbgon parameter will configure several AS components for debug mode. The script will backup the original files, enable debug mode, and then restart the necessary AS components. At this point, the issue that is being reported needs to be replicated so that the component log files can capture any errors generated.
- The -dbgoff parameter should be run after replicating a reported issue and will reconfigure the AS components back to the original configuration. It will zip up the resulting log and configuration files into a single file that should be uploaded to Metalink for Oracle Support to review.
On mid-tier HOMES (e.g., Portal) which do not have an SSO server installed, it is recommended to run this script ONLY in -collect mode.
If running from a mid-tier HOME that does NOT have the SSO server installed, then using the -dbgon and -dbgoff parameters will produce errors as there is no OC4J_SECURITY or OID components on this tier. If it is required to run the script in debug mode on a mid-tier that does not have SSO installed, then you will need to manually create the $ORACLE_HOME/sso/conf directory structure before running the script. There will still be errors trying to stop and start non-existent components but the script should run to completion and collect as much information as possible.
If running from a mid-tier HOME that does NOT have the SSO server installed, then using the -dbgon and -dbgoff parameters will produce errors as there is no OC4J_SECURITY or OID components on this tier. If it is required to run the script in debug mode on a mid-tier that does not have SSO installed, then you will need to manually create the $ORACLE_HOME/sso/conf directory structure before running the script. There will still be errors trying to stop and start non-existent components but the script should run to completion and collect as much information as possible.
The perl script can be downloaded from Metalink using the following link:
SSO Debug Script ... PDF file
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Requirements and Notes |
| Usage |
| Example Output |
| Upload Resulting File |