Identity Management (MOSC)

MOSC Banner

OAM 12C: oam-config.xml file got corrupted - how to handle version when doing import of older file?

in Identity Management (MOSC) 5 commentsAnswered ✓

Hi,

The oam-config.xml file in one of our OAM 12c environments somehow got corrupted (a section of an authentication module got changed).

We have backups of all the exported oam-config.xml file, and we found the most recent uncorrupted version, and we want to try to import it into the Oracle DB, but we are not sure what to do about the Version number in the uncorrupted file when we try to import that file, since the Version number in the uncorrupted file is lower than the number that is in the Oracle DB?

Besides that, the Version number in the oam-config.xml that is in the config/fmwconfig directory is higher than the one that is in the Oracle DB.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center