65 ODF-10000 to ODF-15222

ODF-10000: Unable to add incident file {0} for incident {1}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10002: Encountered error during diagnostic test run: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10004: An error occurred during looking up credentials from credential store.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10400: An error has occurred: {0} Please consult the Diagnostic engine log file for more details.: Cause: An error has occurred in the Diagnostics commandline utility.; Action: Check the diagnostics log for details on this error.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10401: Invalid username or password.: Cause: The Diagnostics command line utility requires a userid and password; Action: Please supply a valid username and password or get your Adminstrator to create you new ones.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10427: Found unexpected parameter "{0}" for command "{1}".: Cause: The specified command does not have the listed paramater.; Action: Run the specified command with no parameters for a list of supported parameters.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10428: Found multiple values for parameter "{0}" for command "{1}".: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10436: Unable to read required security configuration file "{0}".: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10800: Unable to load class: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10801: Type mismatch for parameter "{0}". Expected type is {1} but found {2}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10802: Unsupported type {0} for parameter "{1}": Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11200: An error occurred when loading diagnostics engine configuration from file {0}: {1}: Cause: Diagnostics engine configuration could not be loaded because the configuration file could not be opened.; Action: Please make sure the configuration file exists and has read permissions.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11201: An error occurred when loading diagnostics engine configuration from deployed resource {0}: {1}: Cause: Diagnostics engine configuration could not be loaded because the default configuration file inside DiagEngine.jar could not be opened.; Action: Please make sure the configuration properties file exists inside the DiagEngine.jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11202: Unable to locate configuration properties resource at {0}.: Cause: Diagnostics engine configuration could not be loaded because the default configuration file inside DiagEngine.jar could not be opened.; Action: Please make sure the configuration properties file exists inside the DiagEngine.jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11203: Values are not set for the following configuration properties: {0}: Cause: One or more required configuration properties for the Diagnostics Engine do not have values in the configuration file.; Action: Specify values for the required configuration properties in the configuration file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11204: Unknown NLS Bundle: {0}: Cause: NLS Bundle specified by a Diagnostic Test cannot be loaded. This can normally happen if the NLS Bundle is a resource bundle that does not exist or cannot be loaded.; Action: Ensure that the NLS Bundle specified within the Diagnostic Test is a valid resource bundle class.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11205: Unable to create an external URL. linkURI is not specified.: Cause: A link to an external website could not be created in the diagnostic test report because the 'linkURI' attribute was not specified by the diagnostic test when adding the link to the report.; Action: Correct the diagnostic test to specify the 'linkURI' attribute required when adding external links to the test report.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11206: Unable to create an URL for Metalink note. Metalink document ID is not specified.: Cause: A link to a Metalink Document could not be created in the diagnostic test report because the document ID was not specified by the diagnostic test when adding the link to the report.; Action: Correct the diagnostic test to specify the document ID when adding links to Metalink documents to the test report.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11207: Unable to create an internal URL. functionName is not specified.: Cause: A link to an internal application page within the applications system could not be created in the diagnostic test report because the name for the page was not specified by the diagnostic test when adding the link to the report.; Action: Correct the diagnostic test to specify the page name / function name when adding internal links to the test report.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11208: Unable to load the FND Message Service due to an error: {0}: Cause: The Diagnostics Engine was unable to connect to the Message Service. This could happen if Message Service cannot connect to the applications database.; Action: Ensure that the applicatoins database datasource is configured correctly and that the database is running.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11209: Unable to get JPS context. Following exception is thrown : {0}: Cause: An error occurred when attempting to get the JpsContext from JpsContextFactory. This could happen if JPS is not configured properly in the server where diagnostics is running.; Action: Ensure that the JPS is properly configured on the server where diagnostics is running. Also check the managed server log files to determine the underlying root cause for the error.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11210: No privilige to get credentials with key : {0}: Cause: Diagnostics Engine does not have appropriate privilege to read from the credential store.; Action: Ensure that the DiagEngine.jar file is granted appropriate privilege to read from the credential store.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11211: Credential being set in credentials store is invalid. Please refer error message : {0}: Cause: Could not save credential to credential store because the credential was invalid.; Action: Ensure that valid credentials are specified when saving to the credential store.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11212: Unable to retrieve problems for ADR Home {0} on server {1}. Please refer error message : {2}: Cause: This can occur if the diagnostics engine is unable to establish connection with the underlying IncidentManagerProxy MXBean in the domain to retrieve problems.; Action: Ensure that the AdminServer for the domain is up and running. Also check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11213: Unable to retrieve incidents for a problem from ADR system. Please refer error message : {0}: Cause: This can occur if the diagnostics engine is unable to establish connection with the underlying IncidentManagerProxy MXBean in the domain to retrieve incidents.; Action: Ensure that the AdminServer for the domain is up and running. Also check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11214: Unable to register a diagnostics test run with incident in ADR system. Please refer error message : {0}: Cause: This can occur if the diagnostics engine is unable to establish connection with the underlying IncidentManagerProxy MXBean in the domain while adding a diagnostic test run to an incident in the ADR system.; Action: Ensure that the AdminServer for the domain is up and running. Also check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11215: Unable to close JMX connector. Please refer error message : {0}: Cause: Diagnostic Engine was able to perform the mbean operation but encountered an error when attempting to close the JMX connection.; Action: Check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11216: Unable to obtain connection provider.: Cause: Diagnostic Engine was unable to connect to the AdminServer.; Action: Ensure that the AdminServer is up and running. Also check the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11217: Invalid Problem object passed for querying incidents.: Cause: Invalid or null Problem argument was passed when querying for incidents.; Action: Ensure that a valid Problem argument is passed when querying for incidents.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11218: Invalid incident or diagnostics test report provided.: Cause: One or more of the following parameters were not specified when attempting to add diagnostic test report to an incident in ADR: incident ID, test report file path, server name, ADR Home; Action: Ensure that valid parameters are specified when adding diagnostic test report to an incident in ADR.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11219: You do not have sufficient privileges to execute the test with name ''{0}''.: Cause: User did not have sufficient privileges to execute the diagnostic test.; Action: Ensure that the user belongs to an appropriate role with the execute test privilege required for executing diagnostic tests.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11220: You do not have sufficient privileges to view report details for this execution.: Cause: User does not have sufficient privileges to view a diagnostic test report.; Action: Ensure that the user belongs to an appropriate role with the view test report privilege required for viewing test reports.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11221: You do not have sufficient privileges to update the test with name ''{0}''.: Cause: User does not have sufficient privileges to update the definition of a diagnostic test.; Action: Ensure that the user belongs to an appropriate role with the update test privilege required for updating test definition.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11222: You do not have sufficient privileges to update the tag with name ''{0}''.: Cause: User does not have sufficient privileges to update the diagnostic tag.; Action: Ensure that the user belongs to an appropriate role with the update tag privilege required for updating diagnositc tags.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11223: You do not have sufficient privileges to delete the tag with name ''{0}''.: Cause: User does not have sufficient privileges to delete a tag.; Action: Ensure that the user belongs to an appropriate role with the delete tag privilege required for deleting diagnostic tags.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11224: Could not obtain the security subject of the currently logged in user.: Cause: Diagnostics Engine was unable to get the security subject for the current user.; Action: Ensure that JPS is configured properly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11225: Could not obtain the user name of the currently logged in user, could not find the user principal matching class "{0}".: Cause: Diagnostics Engine was unable to determine username for the current user.; Action: Ensure that JPS is configured properly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11226: Could not obtain the user name and or GUID of the currently logged in user.: Cause: Diagnostics Engine was unable to get the user name or the GUID of the current user.; Action: Ensure that JPS is configured properly. Check the underlying error trace in the server log file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11227: Unable to obtain the module_id for the Diagnostics Logical Business Area (LBA).: Cause: An error occurred when querying the module_id for the Diagnostics LBA from the database.; Action: Ensure that the Diagnostics LBA seed data exists in the database and that the database is running. Also check for the underlying error trace in the server log file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11228: Unable to obtain the menu_id for the FND menu with name ''{0}''.: Cause: An error occurred when querying the menu_id for a FND menu from the database.; Action: Ensure that the Diagnostics data security seed data exists in the database and that the database is running. Also check for the underlying error trace in the server log file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11229: Unable to obtain the object_id for the FND object with name ''{0}''.: Cause: An error occurred when querying the object_id for an FND Object from the database.; Action: Ensure that the Diagnostics data security seed data exists in the database and that the database is running. Also check for the underlying error trace in the server log file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11230: The execution of the PL/SQL procedure name validation method failed to return any values.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11231: The execution of the PL/SQL procedure name validation method has failed.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11233: Unable to create connection because one or more of the following properties are not specified: {0}: Cause: One or more properties required for creating a database connection were not specified.; Action: Specify the missing properties required for creating the database connection.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11234: Unable to load connection properties: Cause: No properties were loaded from the properties file specified using the APPCONNFILE system property.; Action: Ensure that the properties file specified using the APPCONNFILE system property exists and contains the required properties.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11235: System property "{0}" not specified.: Cause: A particular system property required for the Diagnostics Engine was not specified.; Action: Ensure that the system property referenced in the error message is specified using JVM arguments for the managed server or the command-line interface.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11236: Unable to read APPCONNFILE: {0}: Cause: Diagnostics engine was unable to read the file specified by the APPCONNFILE system property.; Action: Ensure that the properties file specified using the APPCONNFILE system property exists and has read permissions.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11237: Unable to load properties from APPCONNFILE: {0}: Cause: Configuration properties could not be loaded from the properties file specified using the APPCONNFILE system property.; Action: Ensure that the properties file specified using the APPCONNFILE system property exists, is readable, and contains the required properties.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11238: The session was not attached due to an error during FND Session initialize: {0}: Cause: An error occurred during initialization of the FND Session the database connection.; Action: Refer to the associated error message and the server log files for more information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11239: The session was not detached due to an error during FND Session detach: {0}: Cause: An error occurred during detaching of the FND Session from the datbaase connection.; Action: Refer to the associated error message and the server log files for more information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11240: Unable to lookup or obtain a connection from data source: {0}: Cause: This error generally occurs if the database does not exist or is not configured properly.; Action: Ensure that the datasource exists in the domain and is configured correctly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11241: An error occurred while streaming contents from file {0} to incident {1} on server {2}: {3}: Cause: An error occurred while copying the contents of a file to an incident directory on a managed server.; Action: Refer to the associated error message and the server log files for more information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11242: An error occurred while fetching value for profile option {0}: {1}: Cause: An error occurred while querying value of a profile option from the database.; Action: Refer to the associated error message and the server log files for more information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11243: The profile option "{0}" is not set. Unable to compute report URL.: Cause: The Diagnostics Dashboard URL Profile Option is not set.; Action: Set the Diagnostics Dashboard URL Profile Option to point to your Diagnositcs Dashboard Application URL.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11244: The value "{0}" for profile option "{1}" is invalid. Unable to compute report URL.: Cause: The Diagnostics Dashboard URL Profile Option is set to an invalid value.; Action: Set the Diagnostics Dashboard URL Profile Option to point to your Diagnositcs Dashboard Application URL.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11245: Unable to evaluate value for expression: {0}: Cause: This generally occurs if the expression is invalid or if the system property specified in the expression is not set.; Action: Ensure that the expression is valid and the system property specified in the expresion is set.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11246: Null connection returned from ApplSessionUtil.: Cause: ApplicationDB data source returned a null connection.; Action: Ensure that the ApplicationDB data source is configured properly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11247: Unable to access field : {0} in class: {1} with bundle name: {2}: Cause: Unable to access the field with the given name from the given resource bundle class.; Action: Ensure that the field exists in the given resource bundle class.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11251: Could not obtain the application roles for the currently logged in user.: Cause: Diagnostics Engine was unable to determine the aplication roles for the current user.; Action: Ensure that JPS is configured properly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11252: An error occurred while attempting to retrieve the list of ADR Homes: {0}: Cause: This can occur if the diagnostics engine is unable to establish connection with the underlying IncidentManagerProxy MXBean in the domain to retrieve the list of ADR Homes.; Action: Ensure that the AdminServer for the domain is up and running. Also check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11253: You do not have sufficient privileges to execute this JMX API. Please ensure that the user ''{0}'' is a member of one of the Fusion Applications Diagnostics Application ID enterprise roles.: Cause: This can occur if the user attempting to invoke the JMX API is not a member of one of the required Diagnostics Application ID enterprise roles.; Action: Ensure that the user is a member of one or more of the Diagnostics Application ID enterprise roles.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11254: You do not have sufficient privileges to delete the test with name ''{0}''.: Cause: User does not have sufficient privileges to delete the definition of a diagnostic test.; Action: Ensure that the user belongs to an appropriate role with the delete test privilege required for deleting test definition.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11600: An error occurred when setting save point {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11601: An error occurred when saving definition for test {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11602: An error occurred when saving inputset {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11603: Invalid prerequisite entity for test '{0}'. A prerequisite for a test must have a test ID or a tag value ID.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11604: An error occured while extracting or loading test definition for test id: {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11605: An error occured while extracting or loading test definition for test name {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11606: An error occured while fetching test id for test name: {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11607: An error occured while fetching test name for test id: {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11608: An error occured while fetching tag value data for tag value id: {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11609: An error occured while fetching tag value data for tag name, tag value: {0} : {1}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11610: An error occured while fetching tag data for tag id: {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11611: An error occured while fetching tag data for tag name: {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11612: An error occurred when saving definition for test stats {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11613: An error occurred while fetching test stats for test id: {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11614: An error occurred while getting test stats for testname: {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11615: A cycle has been detected between Source Id: Prereq Id - {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11616: An error occurred while executing SQL query: {0} with parameters: {1} {2}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11617: An error occurred when saving definition for tag {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11618: An error occurred when saving definition for tag {0} and value {1}: {2}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11619: An error occurred when associating tag {0} and value {1} with tests {2}: {3}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11620: An error occurred when removing tag {0} and value {1} from tests {2} : {3}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11621: An error occurred when removing tag value {0} : {1} : {2}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11622: An error occurred when removing tag {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11623: An error occurred when updating the params to inactive for test id: {0}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11624: An error occurred when updating the prereqs to inactive for test id: {0}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11625: An error occurred when updating the test tag value associations to inactive for test id: {0}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11626: Attempted rollback to savepoint: {0} failed.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11627: An error occurred when freeing temporary clob: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11628: An error occurred when deleting test definition {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12000: Error when saving a test execution for run id {0} with execution id {1}: {2}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12001: Error when saving a test run for run id {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12002: Error when querying test execution id {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12003: Error when loading a test run id {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12004: Error when loading a test executions for run id {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12005: Error when loading nested child test executions for execution id {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12006: Error when fetching run id for run name {0}: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12007: Cannot find run ID {0} to lock for update.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12008: Cannot find execution ID {0} to lock for update.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12009: Found unexpected status code {0} for run ID {1}. Expected status code was {2}. Aborted status update.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12010: An error occurred when updating status for run ID {0} to {1}: {2}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12011: An error occurred when deleting run with run ID {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12408: Thread {0}: An error occurred while executing test: {1}: {2}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12409: Thread {0}: An error has occurred during execution of run command: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12437: An error occurred fetching user/role information: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12800: Unable to load XML: {0}: Cause: XML file not found or has invalid XML syntax.; Action: Locate the existance of XML file {0}. Correct the XML syntax errors.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12801: Encountered validation event while processing {0} at line {1}, column {2}: {3}: Cause: Encountered error at indicated Line in Syntax or missing objects; Action: Correct any syntax errors. Ensure objects indicated exist and are valid.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12802: Cannot load test metadata. Null or empty Java class name.: Cause: Java classname not provided; Action: Provide a classname that can be found in the system.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12803: Cannot load test metadata. Null or empty file path.: Cause: file path not found to load metadata; Action: Provide a file path that exists in the system for this metadata
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12804: Test file not found: {0}: Cause: Test file not found in current file system or jar; Action: Ensure test files exists in current file system or jar. Ensure test properties points to the correct jar for this system
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12805: Test file must be a xml file. Unsupported test file type: {0}: Cause: XML is the only supported file type for Tests in this release; Action: Provide an XML file type for this test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12806: Found duplicate input parameter "{0}" in test "{1}".: Cause: Test metadata and/or input parameter has a duplicate definition; Action: Correct test definition. Provide different input parameters that does not have a duplicate input parameter
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12807: Found duplicate output parameter "{0}" in test "{1}".: Cause: Test metadata and/or output parameter has a duplicate definition; Action: Correct test definition. Provide a different output parameter that does not have a dpulicate output parameter
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12808: Found duplicate step "{0}" in test "{1}".: Cause: Test metatdata has a duplicate step definition; Action: Correct tests metadata so it doesn't has a duplicate step definition. Remove one of the steps.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12809: Found duplicate step definition "{0}" in test "{1}".: Cause: Test metatdata has a duplicate step name in the definition; Action: Correct tests metadata so it doesn't has a duplicate step definition name. Remove one of the steps.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12810: Corresponding step definitions not found for the following steps in test "{0}": {1}: Cause: Test step does not have a definition; Action: Add a step definition in this Test
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12811: Input parameter "{0}" in test "{1}" is required but does not have a default value.: Cause: Required Input parameter in this test has not been provided with a default value; Action: Provide a default Input value for this parameter in this test or remove required settings
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12812: Default value "{0}" for parameter "{1}" in test "{2}" cannot be converted to specified type "{3}".: Cause: The data type associated with the Default value for this parameter is not valid for type defined for the parameter; Action: Changed the Default value or change the Type on the Parameter definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12813: Value "{0}" for parameter "{1}" in test "{2}" cannot be converted to specified type "{3}".: Cause: The data type associated with the value for this parameter is not valid for type defined for the parameter; Action: Changed the value or change the Type on the Parameter definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12814: Value "{0}" for parameter "{1}" in test "{2}" is of type "{3}" and cannot be converted to expected type "{4}".: Cause: The data type associated with the value for this parameter is not valid for type defined for the parameter; Action: Changed the value or change the Type on the Parameter definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12815: Test "{0}" specifies default value for java.util.Date parameter "{1}" however the dateFormat attribute is not specified. Please specify a Java date format as value for the dateFormat attribute.: Cause: This parameter requires a date format and a non-date format was specified; Action: Provide an accepted date format. Check locale for date format.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12816: Default value "{0}" for parameter "{1}" in test "{2}" cannot be converted to specified type "{3}" using format "{4}".: Cause: This Default value requires a date format and a non-date format was specified; Action: Provide an accepted date format. Check locale for date format.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12817: Value "{0}" for parameter "{1}" in test "{2}" cannot be converted to specified type "{3}" using format "{4}".: Cause: This date value requires a date format and a non-date format was specified; Action: Provide an accepted date format. Check locale for date format.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12818: The following prerequisite tests for test "{0}" could not be located in the test repository: {1}: Cause: The test definition requires a prerequisite test(s) to be run which could not be found; Action: Ensure the test is located in the test repository or remove the prerequisite requirement from the test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12819: The following tag name values for test "{0}" could not be located in the test repository: {1}: Cause: The test specified has tag name value defined for it that don't exist in the test repository; Action: Ensure the tag name value definitions exist in the repository by creating new ones or remove the tag name value from the specified test
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12820: The following referenced tests in steps for test "{0}" could not be located in the test repository: {1}: Cause: The specified test has steps that reference tests not found in the test repository; Action: Ensure the tests referred to in the steps are located in the test repository or remove the tests from the steps or remove the steps.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12821: The following prerequisite tag value IDs for test "{0}" could not be located in the test repository: {1}: Cause: The test definition requires prerequisite tag value IDs which could not be found; Action: Ensure the tag value IDs are located in the test repository or remove the prerequisite requirement from the test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12822: The following tag value IDs for test "{0}" could not be located in the test repository: {1}: Cause: The test definition requires tag value IDs which could not be found; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12823: Invalid token "{0}" in binding for parameter "{1}" in step "{2}" in test "{3}". Must specify a parameter name.: Cause: Missing a parameter name for the listed step in this test.; Action: Provide the correct parameter name for this test step.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12824: Invalid parameter reference in token "{0}" in binding for parameter "{1}" in step "{2}" in test "{3}". Referenced parameter is not defined.: Cause: Parameter reference listed in not valid.; Action: Check the test step listed for the correct parameter definition.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12825: At least one of the following parameters must be specified for test registration: {0}: Cause: This test requires parameters for it to be registered.; Action: Check the test definition for the parameters that should be specified.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12826: The specified directory does not exist: {0}: Cause: The filesystem doesn't have the specified directory; Action: Specify a valid directory from the current filesystem
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12827: The specified directory is not a directory: {0}: Cause: The filesystem doesn't have the specified directory; Action: Specify a valid directory from the current filesystem. Don't specify a filename in this case
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12828: The specified file does not exist: {0}: Cause: The filesystem doesn't have the specified filename; Action: Specify a valid filename from the current filesystem.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12829: The test ID or test name must be set in order to fetch test definition.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12830: The run ID or run name must be set in order to fetch test run information.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12831: The run ID or run name must be set in order to cancel a test run.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12832: The run ID or run name must be set in order to delete a test run.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12833: The execution ID must be set in order to fetch test execution information.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12834: The following cyclic test reference encountered : {0}: Cause: A cyclic test reference means the test is not runnable.; Action: A cyclic test reference can be caused by prerequsites or steps referring to tests in a non-sequential manner
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12835: An error occurred while validating nested test {0}: {1} with nested heirarchy {2}: Cause: This test has references to other tests in steps or prerequisites; Action: Remove the invalid nested test in this test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12836: Current execution ID is not set.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12837: Current step name is not set.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12838: Value not set for required parameter: {0}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12839: Invalid value for parameter {0} : {1}. Value must be Y or N.: Cause: This is a boolean parameter value; Action: Change eht parameter value to Y or N
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12840: The following cyclic reference encountered for tag value id {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12841: Run name {0} already exists. Please specify a different run name.: Cause: Only unique run names can be used; Action: Change the run name or add a prefix or postfix that makes it unique
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12842: Invalid value for parameter {0} : {1}. Value must be an integer.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12843: Invalid value for parameter {0} : {1}. Value must be a positive integer.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12844: Invalid value for parameter {0} : {1}. Value must be less than {2}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12845: Value not set for parameter: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12846: Invalid tag name value parameter: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12847: Invalid input name value parameter: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12848: Invalid test name : {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12849: Invalid module ID: {0}: Cause: The module ID is not a known value; Action: Use a module ID found from the Taxonomy tables
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12850: Invalid App product code: {0}: Cause: This App product code is not a known value; Action: Use an App code found from the Taxonomy tables.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12851: Invalid module key: {0}: Cause: The Module key is not a known value.; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12852: Invalid tag name value {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12853: The input parameters for test execution do not resolve to any registered test. Ensure at least one of the following parameters (in CLI or API) must be specified and not empty: {0}: Cause: This Test requires input parameters and none were found.; Action: Supply input parameters as defined by the Test definition and rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12854: At least one of the following parameters must be specified: {0}: Cause: This test requires parameters that were not supplied with the tests; Action: Supply input parameters as defined by the Test definition and rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12856: An unexpected error occured during test execution.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12857: Exactly one of the following parameters must be specified: {0}. Values for more than one parameters were specified: {1}.: Cause: The test was run with the incorrect number of parameters; Action: Rerun this test with exactly one parameters as specified by the test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12858: Invalid value "{0}" for parameter "{1}". Value must be one of the following: {2}: Cause: The test was run with invalid parameter values.; Action: Rerun this test with parameters values specified in the message
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12859: Test run with ID "{0}" not found in the repository.: Cause: Test run ID not found or has been deleted.; Action: Use a test run ID found in the repository
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12860: Test run with name "{0}" not found in the repository.: Cause: Test run name does not exist in the repository or was deleted.; Action: No further action required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12861: Test execution with ID "{0}" not found in the repository.: Cause: Test execution ID does not exist in the repository or was deleted.; Action: No further action required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12862: Unable to create destination directory "{0}". Please ensure that appropriate permissions are set to create this directory or specify a different destination directory using the "destdir" parameter.: Cause: A destination directory exists in a filesystem where write or create permission is not available for the current owner; Action: Change the write and create privileges for the parent directory.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12863: Unable to create a file under directory "{0}". Please ensure that appropriate permissions are set to create this directory or specify a different destination directory using the "destdir" parameter.: Cause: A file in a destination directory in the filesystem where write or create permission is not available for the current owner; Action: Change the write and create privileges for the parent directory.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12864: "{0}" already exists and is not a directory. Please specify a different destination directory using the "destdir" parameter.: Cause: The name specified already exists as a directory.; Action: Use a different name for this directory or remove the existing directory
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12865: "{0}" already exists. Attempt to rename it failed.: Cause: The name specified already exists as a directory.; Action: Use a different name for this directory or remove the existing directory
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12866: Failed to create directory "{0}".: Cause: Directory already exists or parent directory has no write and create permissions; Action: Remove the existing directory, change the permission on the parent directory or use a different directory name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12867: Unable to perform translation. NLS Bundle is not specified.: Cause: Specify the correct NLS bundle name; Action: Specify the correct NLS bundle name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12868: No value specified for parameter "{0}": Cause: This Parameter requires a value which was not specified; Action: Provide a value for the specified parameter
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12869: Report not found for run ID "{0}": Cause: Report was not generated because the Run had an error or the test didn't complete; Action: Check the report status and correct any errors. Rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12870: Report not found for run name "{0}": Cause: Report was not generated because the Run had an error or the test didn't complete; Action: Check the report status and correct any errors. Rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12871: Report not found for execution ID "{0}": Cause: Report was not generated because the Run had an error or the test didn't complete; Action: Check the report status and correct any errors. Rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12872: An input set with name "{0}" already exists for test "{1}": Cause: The input set name already exists in the repository.; Action: Specify a different name for the input set
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12873: Required parameter "{0}" does not have a value to run with.: Cause: Required must have values and the value is missing.; Action: Provide a value for the required parameter specified and rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12874: Value "{0}" not in list of valid values for parameter "{1}".: Cause: This parameter is validated with an LOV that does not have the value specified.; Action: Provide a different value for the parameter specified.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12875: Validation error occurred for input value "{0}" for parameter "{1}": {2}: Cause: This parameter fails validation rules for the input value.; Action: Provide a different value for the parameter specified.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12885: Filter operator "{0}" is not supported for parameter "{1}": Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12886: Taxonomy module ID "{0}" not found.: Cause: A taxomony module ID was provided that does not exist in the taxonomy definitions; Action: Provide a different taxonomy module ID
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12887: Null or empty tag name.: Cause: A tag name is required in this context; Action: Provide a tag name.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12888: Null or empty module ID: Cause: A module ID is required in this context; Action: Require a module ID. Module IDs are found in Taxonomy tables
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12889: Tag with name "{0}" already exists.: Cause: Duplicate tag names are not supported; Action: Provide a different tag name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12890: Null or empty tag value.: Cause: Tag values are required in this context; Action: Provide a tag value
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12891: Tag with name "{0}" does not exist.: Cause: A tag name was provided that was not created or was deleted; Action: Create the tag name first or use a different tag name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12892: Tag with name "{0}" and value "{1}" already exists.: Cause: A tag name was provided that was not created or was deleted; Action: Create the tag name first or use a different tag name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12893: At least one criteria must be specified.: Cause: Criteria are required in this context; Action: Supply criteria
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12894: Unable to delete Test Run(s). Cannot delete a test run {0} that is currently in progress.: Cause: A test is still running and can't be deleted; Action: Cancel the test run or wait for the test to complete before deleting it
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12895: Found one or more Runs with null Run ID.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12896: Tag {0} with Value {1} does not exist.: Cause: Tag value was deleted or never created for this tag name; Action: Create the tag value for this tag name or use a tag value that already exists
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12897: Cannot remove tag {0} created by Oracle.: Cause: Oracle tags are seeded tags that can't be deleted; Action: No futher action required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12898: Cannot remove tag name value {0}:{1} created by Oracle.: Cause: Oracle tag values are seeded tag values that can't be deleted; Action: No futher action required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12899: Unable to register Executor Mbean for Web Application {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12900: Unable to unregister Executor Mbean for Web Application {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12901: Could not invoke test. Reasons could be because (a) The associated application {0} is not running (b) Credential Store and Permissions have not been set up correctly (c) The test is being invoked from outside the J2EE context.: Cause: See message for cause; Action: Setup and install credentials and permissons.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12902: Since "WEB_APP_NAME" tag is present, test must have attribute "requiresApplicationCode" set to "Y".: Cause: This test requires a specific application to run; Action: Set the requiresApplicationCode flag to Y or remove the WEB_APP_NAME tag
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12903: Since "requiresApplicationCode" is set to "Y", test must have a tag for "WEB_APP_NAME".: Cause: This test requires a specific application to run; Action: Remove the requiresApplicationCode flag or supply the WEB_APP_NAME tag with the application name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12904: Could not connect to the Domain Runtime MBean Server. Reasons could be because (a) Credential Store and Permissions have not been set up correctly (b) The test is being invoked from outside the J2EE context.: Cause: See message for cause; Action: Setup and install credentials and permissons.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12905: Could not execute diagnostic test that requires application code.: Cause: This test requires code that exists in a specific application to run; Action: Ensure the specified application is also running when you run this test
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12906: Cannot invoke diagnostic test {0} from CLI since it requires application code. The Diagnostics UI can be used to run this type of test.: Cause: This test requires code that exists in a specific application to run; Action: Run this test from the Diagnostic Testing Dashboard. Ensure the specified application is also running when you run this test
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12907: Cannot start the web application because neither display-name nor "fusion.odf.metadata.webappname" context-param was found in web.xml. The context-param(recommended) or display-name is necessary when Diagnostics Tests requiring applications code are present.: Cause: This test requires code that exists in a specific application to run; Action: Action is specified in the message
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12908: Could not find the required attribute "{0}" in the user context object provided to the mbean invocation.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12909: Could not find the user name of the currently logged in user.: Cause: User name not found; Action: Supply a different user name, or ensure the current user name is setup correctly for Diagnistics credentials
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12910: Could not establish a valid subject for user name "{0}". Please check to make sure all necessary code source permissions have been granted for the oracle.appltest.diagfwk.executor shared library.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12911: Could not establish a valid subject for user name "{0}". Please check to make sure all necessary code source permissions have been granted for the Diagnostics-JmxApi application.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12912: All nested tests that depend on a Web Application must use the same Web Application.: Cause: The Web Application is defined using the WEB_APP_NAME tag and is not pointing to the same app; Action: Add the app for these nested tests to the WEB_APP_NAME tag
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12913: A compound test that contains nested tests which depend on a Web Application must also be tagged to depend on the same Web Application.: Cause: The Web Application is defined using the WEB_APP_NAME tag and is not pointing to the same app; Action: Add the app for these nested tests to the WEB_APP_NAME tag
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12914: Only one value for the "WEB_APP_NAME" tag can be associated with a test.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12915: The number of tag names does not match the number of tag values.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12916: Unable to register MBean which provides access to diagnostics test execution: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12917: Unable to unregister MBean which provides access to diagnostics test execution: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12918: Error occured while initializing the context information for the PL/SQL Step: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12919: Error occured during execution of the Init test procedure of the PL/SQL Step: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12920: Error occured during execution of the RunTest test procedure of the PL/SQL Step: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12921: Error occured during execution of the Cleanup test procedure of the PL/SQL Step: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12922: Error occured while carrying out post-execution steps of the PL/SQL Step: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12923: The PL/SQL procedure ''{0}'' is either not defined or is defined with one or more formal parameters when it should have none.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12932: An error occurred while adding information about execution error to the report: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12933: Failed to create a Diagnostic Test for class: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12934: Found parameter ''{0}'' without parameter definition metadata.: Cause: Inconsistent Test metadata from the parameter definition; Action: Edit the test definition and add a parameter definition for the specified parameter or remove the parameter in the test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12935: Threadpool still may have running threads. Attempting force shutdown.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12936: Failed to delete touched file: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12937: Invalid monitoring interval: {0} Will run with default: {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12938: An error occurred while saving status: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12939: Monitoring interrupted for: {0}: Cause: This is an informative message; Action: No actions required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12940: Diagnostics Engine skipping authentication because subject is empty and username or password null. Engine will execute as the anonymous user which makes having permission to run a test or view a report VERY UNLIKELY.: Cause: No userid provided for this session; Action: Login using a valid diagnostics userid and password
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12962: Insufficient privileges to perform action {0}.: Cause: The login user does not have the security rights for this action; Action: Login using a userid with the appropriates rights or add those rights for this user
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13200: Unable to load the annotated class file: ''{0}'': Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13201: Missing value. The annotation ''{0}'' must have a value.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13202: Unable to find the required annotation ''{0}''.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13203: Unable to find the Module ID for the Module Key ''{0}'': Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13600: Encountered an unrecognized PL/SQL report instruction: ''{0}'': Cause: The report could not be processed because of an invalid instruction; Action: Check the PL/SQL in the report for validity. Try the PL/SQL in a compiler first.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13601: Some PL/SQL instruction set values are missing: Cause: This PL/SQL instruction set requires values.; Action: Check the documentation for this instruction set and it's required values.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13602: Execution of the SQL query failed. SQL query was: ''{0}'': Cause: Invalid SQL causes this problem.; Action: Check the SQL syntax and make corrections before rerunning this test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13603: The report section was not found. The ''{0}'' procedure can only be called after a section is created via the FND_DIAG_SDK_API.START_REPORT_SECTION procedure.: Cause: The listed procedure doesn't have a start report section.; Action: Correct the PL/SQL report by adding a start report section before the listed procedure.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14000: Unable to configure transformation for xsl: ''{0}'': Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14001: Unable to transform xml: ''{0}'': Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14002: Error printing html output: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14003: XSL resource not found: {0}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14400: Error in method {0} : {1}: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14800: Failed to retrieve OS name. The following OS string returned from System.getProperty("os.name") is unknown: {0}: Cause: OS name is incorrect in properties or profile for this system.; Action: Correct the OS name in the property file or profile for this system.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14801: Could not create URL for {0}.: Cause: TODO; Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14802: Could not retrieve domain name for current system.: Cause: Domain name is incorrect.; Action: Ensure the Domain was created correctly and is in properties correctly
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14803: File does not exists {0}. Unable to retrieve owner/group owner for node.: Cause: Owner/Group is not valid for the server node; Action: Ensure the Owner/Group has been created for this installation
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14804: Unable to stat file {0} for ownership details: Cause: There is a problem with the specified file; Action: Ensure the specified file exists and has the proper access rights.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14805: Unable to stat file {0} for group ownership details: Cause: There is a problem with the specified file for this group owner; Action: Ensure the specified file exists and has the proper access rights for this group owner.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15200: Unable to obtain connection to the EM Repository.: Cause: Unable to obtain connection to the EM Repository.; Action: Check the connection information or try again.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15201: Unable to find required property ''{0}''.: Cause: The property could not be found.; Action: Make sure all required properties have been set.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15202: Property ''{0}'' has an invalid type - expected ''{1}'', found ''{2}''.: Cause: The property's type is invalid.; Action: Check the property's type to make sure it conforms to expectations.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15203: Property ''{0}'' cannot be converted to an integer.: Cause: The property could not be converted.; Action: Make sure the value of the property is an integer.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15204: Unable to find required parameter ''{0}''.: Cause: The parameter could not be found.; Action: Make sure all required parameters have been provided.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15205: Parameter ''{0}'' has an invalid type - expected ''{1}'', found ''{2}''.: Cause: The parameter's type is invalid.; Action: Check the parameter's type to make sure it conforms to expectations.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15206: Parameter ''{0}'' cannot be converted to an integer.: Cause: The parameter could not be converted.; Action: Make sure the value of the parameter is an integer.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15207: Property ''{0}'' cannot be converted to a long.: Cause: The property could not be converted.; Action: Make sure the value of the property is a long (integer).
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15208: Parameter ''{0}'' cannot be converted to a long.: Cause: The parameter could not be converted.; Action: Make sure the value of the parameter is a long (integer).
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15209: Required credentials missing for target name ''{0}'', type ''{1}''.: Cause: The required credentials for the operation could not be found.; Action: Make sure the required credentials have been provided.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15210: Unexpected credential column ''{0}'' for target name ''{1}'', type ''{2}''.: Cause: An unexpected credential column was found.; Action: Make sure the credentials provided conform to the expected format.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15211: Required credential column ''{0}'' missing for target name ''{1}'', type ''{2}''.: Cause: The required credential column could not be found.; Action: Make sure the required credentials have been provided.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15212: Unable to obtain connection to the Apps Database for corresponding EM target name ''{0}'', type ''{1}''.: Cause: Unable to obtain connection to the Apps Database.; Action: Check the connection information or try again.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15213: The operation cannot complete because a valid EM Target was not provided.: Cause: A valid EM Target was not provided.; Action: Make sure the EM Target provided is valid.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15214: The requested operation requires {0} EM Targets, {1} were provided.: Cause: An unexpected number of EM Targets were provided.; Action: Make sure the EM Targets provided are appropriate for the operation.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15220: Cannot load resource bundle for {0} with locale {1}.: Cause: The resource bundle could not be loaded.; Action: Make sure the resource bundle exists for the required locale.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15221: Unexpected exception localizing bundle '{0}', key '{1}': {2}: Cause: An entry in the bundle could not be localized.; Action: Check the entry for the provided key as well as the exception details provided.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15222: Key '{0}' not found in bundle '{1}'.: Cause: The required entry was not found in the resource bundle.; Action: Make sure the requested key exists in the resource bundle.
Level: 1

Type: ERROR

Impact: Application Diagnostics