Skip Headers

# Migration Utility Exceptions (26001 - 26020)

Previous

Next

`MigrationUtilityException` is a run-time exception that is raised when an error is encountered during the use of the TopLink migration utility.

Format

    EXCEPTION [TOPLINK – error code]: Exception name
    EXCEPTION DESCRIPTION: Message

Migration Utility Exception

    EXCEPTION [TOPLINK – 26002]: oracle.toplink.exceptions.MigrationUtilityException
    EXCEPTION DESCRIPTION: The program security manager prevents the migration utility from creating a JAR class loader for the JAR file.

26001: WLS_MULTIPLE_JARS_WITH_INPUT_ORION_NOT_SUPPORTED
  Cause: WLS->OC4J TopLink migration exception: There are multiple migratable JARs in the input EAR file, and the `orion-ejb-jar.xml` is also provided in the input. The migration utility only supports a single migratable JAR file in an EAR file if the `orion-ejb-jar.xml` file is also in the input.
  Action: Remove the `orion-ejb-jar.xml` file from the input directory, or keep only one migratable JAR file in the input EAR file.

26002: FAILED_TO_CREATE_JAR_CLASSLOADER
  Cause: The program security manager prevents the migration utility from creating a JAR class loader for the JAR file.
  Action: Configure the program security manager to grant permission on the program to create the JAR class loader.

26003: FAILED_TO_CREATE_DIRECTORY
  Cause: The program security manager prevents the migration utility from creating a directory.
  Action: Configure the program security manager to grant permission on the program to create a local directory.

26004: FILE_NOT_ACCESSIBLE
  Cause: The file is not accessible by the migration utility.
  Action: Check to ensure that the file is on the specified path and is readable.

26005: FILE_NOT_DELETABLE
  Cause: The program security manager prevents the migration utility from deleting a directory.
  Action: Configure the program security manager to grant permission to the program to delete files.

26006: FAILED_TO_READ_INPUTSTREAM
  Cause: A `java.io.IOException` occurred when reading data from an input stream.
  Action: Check to ensure that the file is not locked and is accessible.

26007: FAILED_TO_CLOSE_STREAM
  Cause: A `java.io.IOException` occurred when closing data from an input or output stream.
  Action: Check to ensure that the file is not locked and is accessible.

26008: FAILED_TO_CLOSE_ZIPFILE
  Cause: A `java.io.IOException` occurred when closing data from a zip file.
  Action: Check to ensure that the zip file is not locked and is accessible.

26009: JAR_FILE_NOT_ACCESSIBLE
  Cause: The JAR file was not found or was not accessible on the specified path.
  Action: Check to ensure that the JAR file is not locked and is accessible.

26010: QUERY_NOT_WELL_DEFINED
  Cause: Query method with parameters of the entity defined in the `ejb-jar.xml` file is not well defined as it does not start with `find` or `ejbSelect`.
  Action: Check the `ejb-jar.xml` file to ensure that the finder name starts with either `find` or `ejbSelect` according to the EJB spec.

26011: FAIL_TO_LOAD_CLASS_FOR_QUERY
  Cause: The class defined as a parameter type of the query of the entity in `ejb-jar.xml` could not be loaded.
  Action: Ensure that the bean class is included on the classpath.

26012: FINDER_NOT_DEFINED_IN_ENTITY_HOME
  Cause: The `finder` method with parameters defined in the `ejb-jar.xml` file is not defined at the entity's local and/or remote home interface.
  Action: Check the `ejb-jar.xml` file and the bean home to ensure that the `finder` method parameter types are properly defined.

26013: EJB_SELECT_NOT_DEFINED_IN_ENTITY_BEAN_CLASS
  Cause: The `ejbSelect` method with parameters defined in the `ejb-jar.xml` file is not defined at the entity's bean class.
  Action: Check the `ejb-jar.xml` file and the bean class to ensure that the `ejbSelect` method parameter types are properly defined.

26014: ENTITY_IN_WLS_CMP_JAR_NOT_DEFINED_IN_WLS_EJB_JAR
  Cause: The entity specified in the `weblogic-cmp-jar.xml` file is not defined in the `weblogic-ejb-jar.xml` file.
  Action: Ensure that the entity is consistently defined in the deployment descriptor files.

26015: NO_ENTITY_DEFINED_IN_WLS_CMP_JAR
  Cause: No entity element is defined in the `weblogic-cmp-rdbms-jar.xml` file.
  Action: Ensure that all entities defined in the `ejb-jar.xml` file are mapped in the WebLogic CMP descriptor file.

26016: WLS_CMP_DESCRIPTOR_FILE_NOT_FOUND
  Cause: The WebLogic CMP descriptor file specified in the `weblogic-ejb-jar.xml` file was not found in the directory.
  Action: Ensure that the WebLogic CMP descriptor file, specified in the `weblogic-ejb-jar.xml` file, is included in the input directory.

26017: CMP_DESCRIPTOR_NOT_FOUND_IN_JAR
  Cause: The CMP descriptor file is not found in the JAR file to be migrated.
  Action: Ensure that the WebLogic CMP descriptor file, specified in the `weblogic-ejb-jar.xml` file, is included in the input archive JAR file.

26018: NOT_ALL_ENTITIES_IN_EJB_JAR_MAPPED_IN_ORION
  Cause: Some of the entity beans `EntityBeanClassName`-s defined in the `ejb-jar.xml` file in the jar `jarName` are not explicitly mapped in the `orion-ejb-jar.xml` file.
  Action: Provide the completely mapped `orion-ejb-jar.xml` file to the migration tool. You can obtain the completely mapped `orion-ejb-jar.xml` file from the `/application-deployment` directory after deploying the application.

26019: ENTITY_NOT_MAPPED_IN_ORION
  Cause: The entity `EntityName` in the `orion-ejb-jar.xml` file is not mapped, because no table is specified.
  Action: Provide the completely mapped `orion-ejb-jar.xml` file to the migration tool. You can obtain the completely mapped `orion-ejb-jar.xml` file from the `/application-deployment` directory after deploying the application.

26020: ENTITY_IN_ORION_NOT_IN_EJB_JAR
  Cause: The entity EntityName specified in the `orion-ejb-jar.xml` file is not defined in the `ejb-jar.xml` file.
  Action: Define this entity in the `ejb-jar.xml` file.

For more information, see Integrating TopLink With an Application Server.