My Oracle Support Banner

OAM 12.2.1.4 - Importing Back To DB Of Modified oam-config.xml Fails With Error - "oracle.security.am.migrate.util.StoreException: version-<number> cannot be imported to database" (Doc ID 3039925.1)

Last updated on AUGUST 06, 2024

Applies to:

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

Symptoms

On : 12.2.1.4.0 version,

ACTUAL BEHAVIOR
---------------

After exporting of oam-config.xml from DB and modifying it, on importing back, it failed with this error:

 

<date> oracle.security.am.migrate.main.command.CommandFactory getCommand
INFO: executable operation: import
<date> oracle.security.am.migrate.util.ConfigFileUtil replaceValue
INFO: <version_number> will be replaced by <version_number+1>
oracle.security.am.migrate.util.StoreException: version-<version_number+1> cannot be imported to database
  at oracle.security.am.migrate.util.DBStore.importConfig(DBStore.java:423)
  at oracle.security.am.migrate.operation.ImportConfigOperation.invoke(ImportConfigOperation.java:63)
  at oracle.security.am.migrate.main.command.AbstractCommand.invokeOperation(AbstractCommand.java:56)
  at oracle.security.am.migrate.main.command.impl.ImportCommand.executeCommand(ImportCommand.java:60)
  at oracle.security.am.migrate.main.ConfigCommand.execute(ConfigCommand.java:109)
  at oracle.security.am.migrate.main.ConfigCommand.main(ConfigCommand.java:85)
Caused by: oracle.security.am.migrate.util.StoreException: version-<version_number+1> cannot be imported to database
  at oracle.security.am.migrate.util.DBStore.importConfig(DBStore.java:415)
  ... 5 more

 

Cause

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
Symptoms
Cause
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.