100 XDF-10001 to XDF-10564

XDF-10001: BstrapObject::readInputSXML(): Issue with bootstrap config file.: Cause: Incorrect Bootstrap config file; Action: Provide a correct Bootstrap config file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10002: BstrapObject::readFileToGetCommand(...): File {0} not found in the jar.: Cause: Missing a file in the applxdf.jar; Action: Check if the applxdf.jar is an valid jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10003: There was an error during XDF deployment(standalone=Y),check the log for detail: Cause: An error in XDF deployment; Action: Check the log for detail, fix the issue
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10004: There was an error running the SQL/PLSQL scripts, check the log for detail: Cause: An error running the SQL/PLSQL scripts; Action: Check the log for detail, fix the issue
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10005: There was an error during XDF deployment(standalone=N),check the log for detail: Cause: An error in XDF deployment; Action: Check the log for detail, fix the issue
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10006: BstrapObject::getConnection(): Could Not Get DB Connection: Cause: An error in database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10007: DataCollect::getMVLogTableSpace(...): Table space is null.: Cause: Table space is null; Action: Fix Table space error
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10008: DBObject::readInputSXML: Null or Empty XML Document.: Cause: Invalid SXML file; Action: Use an valid SXML object file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10010: DBObject::stripRowTag(...): SXML Object File is null!: Cause: Invalid SXML file; Action: Use an valid SXML Object file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10011: DBObject::stripRowTag(...): Could not get Object File Document Root!: Cause: Incorrect SXML file format; Action: Fix SXML file errors or select a correct SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10012: DBObject::stripRowTag(...): Invalid DB Object File Format!: Cause: Incorrect SXML file format; Action: Fix SXML file errors or select a correct SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10013: DBObject::executeDDLStmt: The statement is invalid and could not be executed!: Cause: An invalid DDL statement; Action: Check and fix Object file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10014: DBObjectComparision::doCompare(): The object type {0} is not recognized.: Cause: Incorrect object type; Action: Fix object type in the SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10015: DBUtil::executeConsDDLSt: No connection available!: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10016: DBUtil::executeConsDDLSt: The statement is invalid and could not be executed!: Cause: An invalid ConsDDL statement; Action: Fix the SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10017: The statement is invalid and could not be executed!: Cause: An invalid DDL statement; Action: Fix the SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10019: MViewObject::getRemapParameters(): Could not retrieve tablespace information for object {0}.: Cause: May be caused by an invalid tspaceconfig file; Action: Check if a valid tspaceconfig file in the applxdf.jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10020: MVLogObject::getRemapParameters(): Could not retrieve tablespace information for object {0}.: Cause: Error in getting tablespace from target database; Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10021: BstrapObject::executeDDLSt: No connection available!: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10022: DBUtil::returnsRecord(...): No connection available!: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10023: DBUtil::getConsFromDB(...): No connection available!: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10024: DBUtil::dropConst(...): No connection available!: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10025: DBUtil::getConsColsFromDB: No connection available!: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10026: DBUtil::isConsNameInDB: No connection available!: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10027: IndexObject::renameIndex(...):No DB connection available.: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10028: IndexObject::isIntable(): No DB connection available.: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10029: IndexObject::isUniqueMatch:No DB connection available.: Cause: NO database connection; Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10031: Value exceed {0} characters.: Cause: Too many characters or value to large; Action: Change value within the boundary
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10032: {0}={1}: Cause: Too many characters or value too large; Action: Change value within the boundary
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10033: The format for "{}" pair is incorrect. Please check.: Cause: Parameters incorrect errors; Action: Fix incorrect parameters
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10034: Argument {0} is not recognized: Cause: Incorrect parameters in XdfSchemaDeploy; Action: Remove an incorrect parameters from command line
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10036: No Object Mode be provided!: Cause: No Object Mode be provided; Action: Provide Object Mode in the command line
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10037: Invalid Object Mode!: Cause: Invalid Object Mode; Action: Provide the correct Object Mode
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10038: No JDBC DB Address be provided!: Cause: No JDBC Address is provided; Action: Provide JDBC address
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10039: No JDBC Protocol be provided!: Cause: No JDBC Protocol is provided; Action: Provide JDBC Protocol
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10040: No Apps User Name be provided!: Cause: No Apps User Name is provided; Action: Provide Apps User Name
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10041: No Owner User Name be provided!: Cause: No Owner User Name is provided; Action: Provide Owner User Name
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10042: Object File Name is blank.: Cause: Object File Name is blank; Action: Provide the Object File Name.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10043: Editioning View option contradicts with stand alone option!: Cause: Editioning View option can only be with standalone=n.; Action: Re-enter the options.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10046: IO Exception when getting password.: Cause: IO Exception when getting password.; Action: Try again
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10501: Error on getting the revoke Grants statement: {0}: Cause: UNKNOWN; Action: Follow the error message detail to debug
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10502: Error on giving grant to the role: {0}: Cause: UNKNOWN; Action: Follow the error message detail to debug
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10504: Error on revoking Grants: {0}: Cause: UNKNOWN; Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10519: XDFLogger::log: Date format error.: Cause: Date format error; Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10520: XDFLogger::levelMap: Level number format error.: Cause: Incorrect level number; Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10521: ViewObject::dropView: Error while dropping view {0}.{1}: Cause: Cannot drop a view; Action: Check drop a view permission
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10525: XdfSchemaDeploy::applyXDF: The Role deployment NOT in a valid context.: Cause: Role deployment not in schema separation context; Action: Make sure the deployment run in schema separation option
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10526: XdfSchemaDeploy::applyXDF: The object type {0} is not recognized.: Cause: Incorrect object type; Action: FIX object type and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10531: XMLUtil::processorSetParam: Invalid value type in the hash table.: Cause: XMLUtil::processorSetParam: Invalid value type; Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10535: Tablespace config file is null/empty. Exit the program ...: Cause: Tablespace config file is null/empty; Action: Check and use an valid applxdf.jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10536: Invalid Tablespace Config File Format!: Cause: Invalid Tablespace Config File Format; Action: Fix Tablespace config file and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10537: TspaceConfig::loadTspaceConfig(): Implicit classification not in correct format.: Cause: TspaceConfig: Implicit classification not in correct format; Action: Fix Tablespace config file and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10538: TspaceConfig::loadTspaceConfig(): Type-Value classification not in correct format.: Cause: TspaceConfig:Type-Value classification incorrect; Action: Fix Tablespace Type-Value classification and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10539: SQL Error: Missing FND_CLEANUP_PKG package in the target database.: Cause: Missing FND_CLEANUP_PKG package in the target database; Action: Re-run bootstrap mode to install FND_CLEANUP_PKG package
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10546: Unable to find Application Short Name.: Cause: No Application Short Name defined in the Object file; Action: Add Application Short Name
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10548: TableObject::getRemapParameters: Could not retrieve tablespace information for table {0}: Cause: Error in the process of getting tablespace information from config file; Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10549: Tablespace type from DB is null.: Cause: Incorrect Tablespace type; Action: Check if the tablespace exist in target DB.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10561: TableComparison::doObjectCmp:Executing comment statement: {0}: Cause: Failed executing comment statement; Action: Fix SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10562: Table SXML clob to xml doc processing error: {0}: Cause: UNKNOWN; Action: Follow the error message detail to debug
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10563: Alter Table Exception: {0}: Cause: Error in the alter table process, reason unknown; Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10564: DBUtil::isConsNameInDB: No connection available!: Cause: No database connection; Action: Fix database connection
Level: 1

Type: ERROR

Impact: Application Diagnostics