ECC Data Load Request Ends with CANCELLED Status

When an ECC Data Load concurrent request ends with a ‘CANCELLED’ status, it suggests an issue that prevents the load from finalizing, often deep within the ECC or database layers . You should refer to Oracle Support Document 2649008.1, which covers similar symptoms . The key action for troubleshooting is checking the database alert log immediately following the failure of the data load request . Errors in the database alert log often provide clues regarding resource contention, connection loss, or specific data handling failures.

You should check the ECC managed server logs, typically the `ecc.log` file . While the concurrent request shows ‘CANCELLED’ in EBS, the ECC logs may contain detailed stack traces or error messages related to the Solr index update or data processing . If the error points to a ‘Read timed out’ (`java.lang.InterruptedException: Read timed out`), as seen in some logs, it suggests a connectivity or timing issue between ECC components during the heavy collection registration phase .

Yes, for the initial data extraction, you should specify the Load Type as `FULL_LOAD` . While the default log level is typically acceptable, setting the Log Level parameter to ‘Error’ is usually standard for initial runs . Note that the concurrent program short code is `ECCRUNDL` (‘ECC Run Data Load’) .

The ‘No Data to display’ error can occur if the required security roles have not been properly assigned to the user’s responsibility . Even after a successful data load, users need product-specific roles (e.g., `UMX|FA_M_ECC_ACCESS_ROLE` for Fixed Assets) to access the Command Center functionality and view the data , . You must ensure the necessary UMX assignments were completed using the appropriate role assignment script or method , .