Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1)
E10113-01
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

46 OAMCFG-60001 to OAMCFG-60033

OAMCFG-60001: Error in initializing logging.
Cause: System error
Action: Check Java system logger settings.

Level: 1

Type: ERROR

Impact: Logging

OAMCFG-60002: Unable to establish connection to directory.
Cause: Incorrect input for ldap server parameters.
Action: Verify input parameters: ldap_host, ldap_port, ldap_userdn & ldap_userpassword

Level: 1

Type: ERROR

Impact: Network

OAMCFG-60003: Error in parsing command line parameters.
Cause: One or more required parameters are missing.
Action: Provide required parameters. Use -help option to get the list of parameters.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60004: Cannot write LDIF to console.
Cause: Request to write LDIF file to console
Action: Specify proper file name using output_ldif_file parameter.

Level: 1

Type: ERROR

Impact: Files

OAMCFG-60005: Cannot specify the same file name for log file and the output file
Cause: Specified same file name for output_ldif_file and log_file settings parameters.
Action: Specify different file names.

Level: 1

Type: ERROR

Impact: Files

OAMCFG-60006: In validate mode, test username is mandatory
Cause: test_username parameter is not specified
Action: Specify test_username parameter

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60007: In validate mode, test_userpassword is mandatory
Cause: test_userpassword parameter was not specificed.
Action: specify the test_userpassword parameter.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60008: Cannot configure version {0} of OAM.
Cause: Unsupported version of OAM specified on command line.
Action: Specify supported version. Download configuration tool that supports the desired version.

Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60009: APP_DOMAIN parameter not specified.
Cause: APP_DOMAIN parameter is mandatory in all modes.
Action: Specify APP_DOMAIN parameter

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60010: The LDAP port number specified is invalid
Cause: Invalid LDAP port specified.
Action: Specify valid LDAP port.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60011: LDAP_USERDN parameter not specified
Cause: LDAP_USERDN parameter is mandatory.
Action: Specify LDAP_USERDN parameter.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60012: The OAM port number specified is invalid
Cause: Invalid OAM port number specified.
Action: Specify correct OAM port number.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60013: Incompatible OAM version {0} found.
Cause: The tool found an incompatible OAM version configured in the directory.
Action: Use the tool with a compatible OAM version.

Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60014: OAM is not configured against this directory.
Cause: OAM not configured against given directory.
Action: Configure OAM against specified directory and retry.

Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60015: Could not match the oam_aaa_host and oam_aaa_port parameters to a configured OAM server. Please verify input
Cause: Could not match user specified oam details to configuration.
Action: Specify valid OAM host and port.

Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60016: Error in closing file handles.
Cause: There was an error in closing file handles used by the tool.
Action: Please ensure the file system is checked for consistency.

Level: 1

Type: ERROR

Impact: Files

OAMCFG-60017: Cannot decode URI : {0} due to its length. Actual length: {1}
Cause: Encountered illegal length for URI in directory. Encoded URI length must always be even.
Action: Contact OAM administrator to correct or delete URI in directory.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60018: Cannot decode URI :{0}
Cause: Encountered illegal hexadecimal characters for the URI.
Action: Contact OAM administrator to correct or delete URI in directory.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60019: Could not send cache flush request to server {0} running on port {1} in mode {2}.
Cause: OAM Access server is down.
Action: Please ensure OAM Access server is running.

Level: 1

Type: ERROR

Impact: Network

OAMCFG-60020: Cannot send cache flush to OAM server in desired mode {0}.
Cause: OAM Access server is not available in desired mode.
Action: Please ensure OAM Access server is running in desired mode.

Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60021: Found multiple policy stores in the directory:: {0}.
Cause: Multiple Access Server Policy Stores are configured in the directory.
Action: Use ldap_base parameter to localize search.

Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60022: Access Manager component is not configured in this directory.
Cause: Access Manager/Server was not configured.
Action: Configure Access Manager/Server and retry.

Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60023: Error in communicating with LDAP server.
Cause: LDAP server is down.
Action: Please ensure LDAP server is up and retry.

Level: 1

Type: ERROR

Impact: Network

OAMCFG-60024: This LDAP operation failed.
Cause: Incorrect configuration and/or input parameters.
Action: Please check input parameters and retry.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60025: Error in fetching OAM host.
Cause: Could not fetch OAM host due to an error.
Action: Check OAM parameters and retry.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60026: Cannot get Global Sequence Number in the given OAM policy store: {0}.
Cause: The configuration data in LDAP is missing Global Sequence Number information.
Action: Re-configure OAM against LDAP and retry.

Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60027: Found {0} entries that match the name: {1}.
Cause: Multiple names matched a given name.
Action: Specify a unique name and retry.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60028: Found no entries that match the name:{0} of type:{1}.
Cause: Could not find entries matching name
Action: None required.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60029: Error while loading template:{0} to LDAP
Cause: Not all information could be loaded to LDAP
Action: Use Policy Manager to validate that all data has been loaded.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60030: APP_AGENT_PASSWORD parameter is required.
Cause: APP_AGENT_PASSWORD is a mandatory parameter when creating a Web Domain
Action: Specify APP_AGENT_PASSWORD and rerun tool.

Level: 1

Type: ERROR

Impact: Data

OAMCFG-60031: Could not locate the template file {0}
Cause: The specified template could not be found in either the filesystem or the Jar file.
Action: Please donwload the Jar file again. If you have customized the template, ensure it is in the expected filesystem location.

Level: 1

Type: ERROR

Impact: Files

OAMCFG-60032: Error while trying to read template file {0} from filesystem.
Cause: The template file and/or filesystem is corrupted.
Action: Ensure template file and/or filesystem error has been fixed.

Level: 1

Type: ERROR

Impact: Files

OAMCFG-60033: Error while trying to locate template file in JARs:{0}
Cause: The JAR file does not contain required templates.
Action: Please ensure that the correct JAR file is specified in CLASSPATH.

Level: 1

Type: ERROR

Impact: Files