My Oracle Support Banner

Oracle Access Manager (OAM) Note For Troubleshooting The PasteConfig Command After A Shared OPSS Schema Is Split (Doc ID 2705927.1)

Last updated on SEPTEMBER 13, 2023

Applies to:

Oracle Access Manager - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Goal

This is a specific use case were there were multiple issues related to the "PasteConfig" command after a Shared OPSS schema was split/separated and the WLS Managed OAM server not starting.

The splitting of the OSSP schema or Schema is typically seen when upgrading OAM and OIM in an environment were the OSSP Schema is shared from 11.1.2.3.x to 12.2.1.3.0

Common Symptoms

  • Split an OPSS schema by creating a new set of users for OAM (Create a new OPSS user for OAM via RCU.)
  • Pointed the WLS data source for new set of user
  • The WLS Admin Server starts
  • The WLS Managed OAM server does not start

 

Common Causes

  • Password files/Passphrase Files

Files for password were not created. There are several password files that need to be created before running the command, password for the users (data sources), keystore file password, LDAP server password. All of them need to be created. Only option to create a unique file is that all the password are the same.

  • Permissions

The WLS Admin Server was not able to start as the /tmp directory where the files for the T2P process did not have execution rights. This is very important as the Admin Server is re-started several times during the process. PasteConfig tmp directory must be created on a disk where the user (oracle user) has privileges to write/read/execute. Chmod just show the setting are right but the noexec was set to the /tmp

  • Alias on Admin Server

After right modification for password and directory the Admin was able to start and move to create the domain but then fail on restart. The Admin Server did not registered any call for shutdown

  • Extra JAVA_OPTIONS setting for Java Mission Control (JMC/JMX)
  • Other Issues

Issues with the Admin Server not able to login to the LDAP server

 

The KM notes provided in the Solution section are for specific issues that were seen related the "PasteConfig" command that caused the WLS Managed OAM server not to start and will provide a beginning point in trouble shooting the various issues.

 

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
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.