This page lists the error codes returned by the BMC TrueSight Capacity Optimization platform.
Installer
Error code | Description | Solution |
|---|---|---|
BCO_INST_FAIL101 | OS not Supported. Please check list of supported platforms. | Refer to the list of supported Operating Systems. |
BCO_INST_FAIL102 | CPU architecture detected is not compatible with this installer. | Ensure that you are using a Linux or Solaris architecture. |
BCO_INST_FAIL103 | Legacy BMC TrueSight Capacity Optimization version is disallowed for upgrade. | Upgrade to BMC TrueSight Capacity Optimization version 4.0, and re-execute the installation file. |
BCO_INST_FAIL104 | Failure validating Oracle client: JDBC library not found. | Verify that the JDBC library is present at %ORACLE_HOME%/jdbc/lib |
BCO_INST_FAIL105 | Failed to create new BCO user. | |
BCO_INST_FAIL106 | Failed to unmount shared repository. | Check if all BMC TrueSight Capacity Optimization services have been stopped properly before the shared repository unmount. |
BCO_INST_FAIL107 | Failed to mount shared repository. | |
BCO_INST_FAIL108 | The user name you have provided is not valid. | Provide a valid BMC TrueSight Capacity Optimization user name. |
| BCO_INST_FAIL109 | Failure installing Web Console. | Ensure the connection to <LocalHostName>:8888/console works properly after the Web Server service has been started. |
BCO_INST_FAIL111 | Failed to validate Database instance: Database user name is not valid. | |
BCO_INST_FAIL113 | Failed to validate Oracle SQL*Plus. Oracle Client installation is missing sqlplus component. | Ensure a valid Oracle Home has been provided. |
BCO_INST_FAIL114 | Failed to validate Oracle SQL*Loader. | Ensure a valid Oracle Home has been provided. |
BCO_INST_FAIL115 | Failed to validate Oracle SQL*Loader: execution failed for the specified User. | Check the Oracle SQL*Loader log at $LOGDIR/sqlldr_test.log. If the database table used for test is already created, drop it and retry with SQL*loader test. |
BCO_INST_FAIL116 | Oracle SQL*Loader data test failed for the specified User. | |
BCO_INST_FAIL117 | Failure detected while storing shared repository information in database. | Check the database connection. |
BCO_INST_FAIL118 | Failed to Create key and certificate for HTTPS. | |
BCO_INST_FAIL119 | Failed to register BCO components to Web Console. | Check whether the Web Server service on the first AS machine is running. |
BCO_INST_FAIL120 | Failed to validate component registration. | |
BCO_INST_FAIL121 | Failure occurred during component configuration, possibly due to filesystem problems. | |
BCO_INST_FAIL122 | Failure during preparation of database schema and initial population, possibly due to SQL errors, network connectivity problems or database instance problems. | Check the logs at |
BCO_INST_FAIL124 | Web Server failed to start. | Check the services_start_<date>.log file to investigate the root cause. |
BCO_INST_FAIL125 | Failed to install Web Console: Views initialization failed, possibly due to timeout. | This could be caused due to a slow database. |
BCO_INST_FAIL126 | Failed to create repository data structure. | |
BCO_INST_FAIL127 | Failed to install Web Console: Views initialization failed, autodeploy folder does not contain initial Views files. | Check if the <install_folder>/web/autodeploy directory contains a file with extension .tbi. |
BCO_INST_FAIL128 | Failed to install Web Console: Views initialization failed, unable to deploy Views initialization files. | Check if <install_folder>/web/autodeploy directory contains a file with extension .tbi.err. If this happens, rename the extension .tbi.err to .tbi and restart the Web server service. |
BCO_INST_FAIL129 | Failed to install DataHub. Possibly due to missing backend services installation files. | Check if the <install_folder>/ directory contains all .war service files, that are properly deployed. |
BCO_INST_FAIL130 | Failed to check BCO user name existence. | |
BCO_INST_FAIL131 | Failed to check BCO user group name existence. | |
BCO_INST_FAIL132 | Failed to assign BCO user ownership to installation directory. | |
BCO_INST_FAIL133 | Software requirement failure: openssl not found. | |
BCO_INST_FAIL134 | Failure detected while storing web server configuration in database. | Check your database connection. |
BCO_INST_FAIL136 | CIFS repository is not supported on Solaris 10. | Use NFS as the network file system. |
BCO_INST_FAIL138 | Failed to detect host Operating System. | Clean all the folder/tmp and remove all files and folders related to the installation. If you still get this error, ask your system administration about the mount option for the temporary folder (/tmp for Linux). If the directory is mounted with the noexec option, remove this option, and redo the mount. |
BCO_INST_FAIL139 | BCO Operating System Image is not allowed to run on current host Operating System. Please provide a valid OS Installation kit in order to proceed. | |
| BCO_INST_FAIL140 | Failed to de-register BCO components from Web Console. Possible cause: Web Console is not responding. | |
| BCO_INST_FAIL141 | SQL Error: Error while executing SQL command (Caution: Database may have partially installed!!). | Consult with your Database Administrator for this error. If you need to re-install, ensure you perform a database cleanup first. |
| BCO_INST_FAIL142 | Database schema population error: Database alignment failed to execute. | |
| BCO_INST_FAIL143 | Failed to deploy third party libraries. | At <installation_folder>/3rd_party directory, manually extract all files and restart the httpd service. |
| BCO_INST_FAIL144 | Error occurred while preparing report templates folder for the selected Database type | |
BCO_INST_ERR001 | Failed to connect to database | Ensure valid details have been provided. |
BCO_INST_ERR101 | Error while validating Database instance: Database is not empty for the specified user. | Clear the database component selection, if already installed or cleanup the Database for the specified user before proceeding. |
BCO_INST_ERR102 | Error while validating Database hostname: underscore (_) is not a valid character for Oracle Database hostname. | Modify the current Hostname. |
BCO_INST_ERR103 | Error while validating Database instance: Users and Tablespaces are already created. | Clear the Create Database Users and Tablespaces and Cleanup Database Users and Tablespaces options. |
BCO_INST_ERR104 | Error while validating Database instance: specified Database Users and Tablespaces are not present in database. | Select the Create Database Users and Tablespaces option or create it before running the installer. |
BCO_INST_ERR105 | The specified server address cannot be contacted. | |
BCO_INST_ERR106 | Error while validating Database instance: invalid Oracle Home. | Check if the path provided for Oracle Home is valid. |
BCO_INST_ERR107 | Error while validating Database instance: invalid Oracle Alias. | Check if the tnsnames.ora file contains the specified Oracle alias. |
BCO_INST_ERR108 | Error while validating Database instance: invalid or empty Listener port. | The specified port is empty or not included between 0 and 65535. |
BCO_INST_ERR109 | Error while validating Database instance: Database port must contain only numbers. | |
BCO_INST_ERR110 | Error while validating Database advanced inputs: specified advanced inputs are empty. | Ensure the specific inputs have been provided. |
BCO_INST_ERR111 | Application Server date and Database date are not aligned. | To proceed with the installation, select the previous button, and provide a valid Application Server date. |
BCO_INST_ERR112 | An error occurred while trying to install the specified features. | Ensure your environment has the Allowed Features already installed to proceed with the installation. |
BCO_INST_ERR113 | Error while validating Database instance: Oracle Service Name is empty. | |
BCO_INST_ERR114 | Error while validating Database instance: Database Host Name is empty or not valid. | |
BCO_INST_ERR115 | An error occurred while creating partitions for Datawarehouse. | The Database Space Manager script needs to be run to create partitions. |
BCO_INST_ERR116 | Error while validating Database instance: Oracle TNS Alias validation failed. | Ensure a valid Oracle Home and Oracle Alias have been provided. |
BCO_INST_ERR117 | Error while validating connection to Database using the specified user. User doesn’t have ‘SYSDBA’ privileges. | Add sysdba privileges to the user. |
| BCO_INST_ERR118 | Error while validating Database instance: Database tablespaces creation cannot happen due to wrong datafile path. | Check if the provided datafile path is correct. |
| BCO_INST_ERR119 | Error while validating Database instance: Username is not valid. | Check the Database user name for the connection. |
| BCO_INST_ERR120 | Error while validating Database instance: Password is not valid. | Check the Database password for the connection. |
| BCO_INST_ERR121 | Database schema is already upgraded to BMC TrueSight Capacity Optimization 9.0 version. | Clear the Database schema component selection and try again. |
| BCO_INST_ERR122 | Database error. Possible causes: SYSDBA Permission or Password Policy Violated issue. | |
| BCO_INST_ERR123 | Shared repository is not writable by BCO user. | Add correct permissions to network shared filesystem. |
| BCO_INST_ERR124 | NFS server is not reachable. | Verify host network connection. The NFS server name must be resolved and reachable via ping command |
| BCO_INST_ERR125 | Error while validating available space on current host probably due to insufficient space on temporary directory. | Check the host space available in the temporary directory. |
| BCO_INST_ERR126 | Error while validating Database instance: The specified tablespace does not have enough space. | Contact your DBA to fix the tablespace free space requirements. |
| BCO_INST_ERR127 | Error while validating installation folder: Installing directory must be writable. | Ensure the current user has the required permissions on selected installation folder. |
| BCO_INST_ERR128 | Error while validating installation folder: Installing directory must be an absolute path. | |
| BCO_INST_ERR129 | Error while validating installation folder: Installing directory must be specified. | |
| BCO_INST_ERR130 | Error while validating installation folder: Installing directory can only contain alphanumeric characters - no special or multibyte characters can be used. | |
| BCO_INST_ERR131 | Error while validating installation folder: Installing directory may not contain spaces. | |
| BCO_INST_ERR132 | Error while validating space at installation folder: The features you have selected require more space on disk. | |
| BCO_INST_ERR133 | Error while validating space at temporary folder: The features you have selected require more space on temporary folder. | |
| BCO_INST_ERR134 | Error while validating connection to Database using JDBC URL. Please provide valid connection details. | |
| BCO_INST_ERR135 | Error while creating backup folder for log installation files. Unable to copy files from OS temporary directory. | |
| BCO_INST_ERR136 | Error while validating Database Roles and Tablespaces: specified objects do not exist. | |
| BCO_INST_ERR137 | Error while validating Database instance: user does not have privileges to access Oracle Home folder. | |
| BCO_INST_ERR138 | Error while validating Database instance: Some Database session is still open. | Check if there are open sessions on the selected Database, stop them to continue. |
| BCO_INST_ERR139 | Error while validating Database instance: Database TNS listener does not currently know of service requested in connect descriptor. | Specify a valid Oracle SID/Service name. |
| BCO_INST_ERR140 | Error occurred while moving migration archive file to <installation_folder>/migration_backup directory | |
| BCO_INST_ERR141 | Repository package not found while performing server migration | Make sure the co_repository file has been correctly moved to the installation folder or make a different choice to proceed. |
| BCO_INST_WARN301 | Database schema population warning: some Data loading failed while DB alignment. | Verify the DB alignment logs at /tmp/database_$DATE.log. |
| BCO_INST_WARN302 | Failed to stop BCO services. | Check the log script at /tmp/services_stop_$DATE.log. |
| BCO_INST_WARN303 | Failed to clean crontab entries. | |
| BCO_INST_WARN304 | An error occurred while configuring Aging for Datawarehouse. | The Aging configuration can be reconfigured after installation by navigating to Administration > Data Warehouse > Aging configuration. |
| BCO_INST_WARN305 | Failed to create BCO symlinks. | |
| BCO_INST_WARN306 | Failed to start the specified BCO service. | Check the log script at /tmp/services_start_$DATE.log. |
| BCO_INST_WARN307 | Database schema population warning: some Database constraints seem disabled. | Check the DB alignment logs at /tmp/database_$DATE.log. |
| BCO_INST_WARN308 | Error occurred while configuring OS user. Installer cannot properly execute OS commands needed to configure the user. | |
| BCO_INST_WARN309 | Error occurred while removing R Server folder from installation directory. | Manually remove the RServer folder from the installation directory. |
| BCO_INST_WARN310 | Error occurred while trying to drop Database schema and its content. | Connect to the database as sysdba and drop the schema manually. |
| BCO_INST_WARN311 | Error while validating OS user: unable to validate user limits. | Limits for the installation user are not set according to recommendations. Verify the ‘open files’ property by typing ulimit –a. The recommended limit is 10240. For Solaris, configure the process.max-file-descriptor property. |
| BCO_INST_WARN312 | Error occurred on shared repository mount: Cannot persist mount information. File system mount file is not available. | |
| BCO_INST_WARN313 | Error occurred on shared repository mount: Cannot persist mount information due to an error. | |
| BCO_INST_WARN314 | Error occurred while removing repository folder probably due to sharing options. | Unmount and remove the repository folder manually. |
| BCO_INST_WARN315 | Unable to connect to Database using the specified SYSDBA credentials. | Specify the sysdba credentials or click Proceed to only drop the database content. |
| BCO_INST_WARN316 | Error while removing the specified backup folder from installation directory. | |
| BCO_INST_WARN317 | Error while cleaning dash-autodeploy folder. | |
| BCO_INST_WARN318 | Cannot mount repository to the specified directory. Filesystem is already mounted. | |
| BCO_INST_WARN319 | Database schema population warning: error occurred while trying to re-enable Database constraints. | |
| BCO_INST_WARN320 | Error while validating Database instance: Oracle TNS Alias validation failed. | Check Oracle TNSNAMES.ORA file contains proper entry for selected Database server instance. |
| BCO_INST_WARN321 | Repository package not found on server migration. | The repository package was not found. To complete the migration process, you must perform a manual repository restore after the migration. |
| BCO_INST_WARN322 | Error while validating Database instance: Oracle sqlnet.ora File location validation failed. | |
| BCO_INST_WARN323 | Error while validating Database instance: Oracle ldap.ora File location validation failed. | |
| BCO_INST_WARN324 | Error while validating Database instance: Oracle sqlnet.ora file is not properly configured. | |
| BCO_INST_WARN325 | Integration with BMC Atrium Single-Sign-On (SSO) has been found enabled while performing upgrade to newer version. | Please go to Web Console on "Administration > System > Global configuration" page and disable BMC Atrium SSO before proceeding with upgrade process. At the end of upgrade, BMC Atrium SSO needs to be re-activated from Web Console in order to have it working on the setup. |
Database
Error code | Description | Solution |
|---|---|---|
BCO_Database_FAIL101 | Database storage problem | Check the database tablespaces saturation and other database logs and data storage space. |
BCO_Database_FAIL102 | Memory saturation | Check the memory configuration of the database instance. |
BCO_Database_FAIL103 | Availability/connectivity: The Database instance seems to be down or not reachable. | Check the database instance sanity and connectivity. |
BCO_Database_FAIL104 | Database configuration problem. One or more parameters are limiting the instance health. | Review the database configuration. |
BCO_Database_FAIL105 | Invalid database access credentials | Check if the account is locked or if the database password was changed. |
BCO_Database_ERR111 | A component reported an attempt to write on a missing partition; probably Database partitions are misconfigured or not correctly created. | |
BCO_Database_WARN301 | Database resource contention: potential overload. | Check the database resources and/or reduce the input load parallelism |
Capacity-Aware Placement Advice Service
Error code | Description | Solution |
|---|---|---|
BCO_PAS_FAIL001 | PAS reported an issue on the Application Server file system (probably disk is full). | Check the Application Server disk space status. |
BCO_PAS_FAIL002 | PAS reported an Out-of-Memory issue on the Application Server. | |
| BCO_PAS_FAIL003 | PAS reported a No Space Left on device issue. Disk is full | |
BCO_PAS_ERR011 | PAS reported a generic issue in the component. | |
BCO_PAS_ERR012 | PAS reported a query issue. | |
BCO_PAS_ERR014 | PAS reported a data dependent issue in a query. | |
BCO_PAS_ERR015 | PAS exhausted the connection pool to the database. | |
BCO_PAS_ERR112 | Insufficient capacity based on PPA. | PAS was not able to complete placement because of lack of capacity based on PPA. Check capacity status of your Cloud Infrastructure, counting PPAs. Also check the Scenario PPA Time Validity option in CLM Placement Advice preparation task configuration: this should be aligned with performance ETL Saver Period. |
BCO_PAS_ERR113 | Scenario lookup failed. | Check that Placement Advice models and scenarios have been created in “Administration domains” section. If they are missing, check that CLM Placement Advice preparation task is up and running and it is scheduled to run continuously |
BCO_PAS_ERR114 | Invalid scenarioid. | See BCO_PAS_ERR113 |
BCO_PAS_ERR115 | Invalid/malformed parameter. | |
BCO_PAS_ERR116 | No valid targets | If BMC CLM page / Calls log is reporting “Unknown System” as targets: Check that: 1. Integration with BMC - Cloud Lifecycle Management additional component has been correctly deployed 2. CLM Infrastructure Extractor has been correctly deployed and log doesn’t show errors 3. Tasks CLM Placement Advice Preparation, CLM Cloud infrastructure extractor Queue Waiter, CLM Cloud Infrastructure Hierarchy Manager have been correctly deployed and are in “green” status 4. Placement Advice Preparation Chain has been deployed and scheduled, it is up and running and includes all of the above in points 2. and 3. 5. CLM Infrastructure Extractor is referring to the correct Cloud configuration If BMC CLM page / Calls log is reporting targets with their correct names: - Check Targets metrics availability: to be valid, a target must have at least CPU_TOTAL_MHZ and TOTAL_REAL_MEM for Compute placements and DSTORE_SIZE and DSTORE_FREE for Storage placements |
| BCO_PAS_ERR117 | Insufficient capacity but no failure because of user configuration - Fallback | PAS was not able to complete placement because of lack of capacity: check capacity status of your Cloud Infrastructure. Because of the dedicated option in CLM Placement Advice preparation task configuration, VM/vDisk provisioning in CLM was not stopped (target system has been chosen randomly) |
BCO_PAS_ERR211 | Insufficient capacity - Stop provisioning. | PAS was not able to complete placement because of lack of capacity: check capacity status of your Cloud Infrastructure. VM/vDisk provisioning in CLM has been stopped |
| BCO_PAS_ERR218 | Insufficient capacity possibly due to affinity settings - Stop provisioning. | PAS was not able to complete placement because of affinity setting violation. Check Capacity status of chosen targets in previous placements, coming from the same SOI/VM (according to the selected affinity constraint).VM/vDisk provisioning in CLM has been stopped |
| BCO_PAS_ERR219 | Insufficient capacity detected or anticipated with pending provisioning actions - Configured to stop provisioning. | PAS was not able to complete placement because of lack of capacity based on PPA. Check capacity status of your Cloud Infrastructure, counting PPAs. Check also Scenario PPA Time Validity option in CLM Placement Advice preparation task configuration: this should be aligned with performance ETL Saver Period. Due to configuration provisioning in CLM has been stopped |
BCO_PAS_WARN301 | Target utilization (performance) data are missing. | Check Performance metrics of this target: CPU_UTILMHZ and MEM_CONSUMED for Compute placements, DSTORE_FREE for Storage placements |
BCO_PAS_WARN302 | Target configuration data are missing. | Check Configuration of this target: CPU_TOTAL_MHZ and TOTAL_REAL_MEM for Compute placements and DSTORE_SIZE for Storage placements |
BCO_PAS_WARN303 | Target lookup failed. | Check that CLM Placement Advice preparation task is up and running and it is scheduled to run continuously |
BCO_PAS_WARN304 | Candidate utilization (performance) data is missing. | |
BCO_PAS_WARN305 | Candidate configuration data is missing. | |
BCO_PAS_WARN306 | Candidate lookup failed. | |
BCO_PAS_WARN307 | Performance data was last refreshed at a time instant that was older than 2 times the configured refresh interval. | See BCO_PAS_WARN303 |
BCO_PAS_WARN308 | Performance data was last refreshed at a time instant that was older than 4 times the configured refresh interval. | See BCO_PAS_WARN303 |
BCO_PAS_WARN309 | No PAS scenarios have been found. | Check that: 1. Integration with BMC - Cloud Lifecycle Management additional component has been correctly deployed 2. CLM Infrastructure Extractor has been correctly deployed and log doesn’t show errors 3. Tasks CLM Placement Advice Preparation, CLM Cloud infrastructure extractor Queue Waiter, CLM Cloud infrastructure Hierarchy Manager have been correctly deployed and are in “green” status 4. Placement Advice Preparation Chain has been deployed and scheduled, it is up and running and includes all of the above in points 2. and 3. 5. CLM Infrastructure Extractor is referring to the correct Cloud configuration |
DataHub
Error code | Description |
|---|---|
BCO_DH_FAIL001 | DataHub reported an issue on the Application Server file system (probably disk is full). |
BCO_DH_FAIL002 | DataHub reported an Out-of-memory issue on the Application Server. |
| BCO_DH_FAIL003 | DataHub reported a no space left on device issue. |
BCO_DH_FAIL101 | DataHub services are not responding correctly; a client reported that the connection cannot be established. |
BCO_DH_ERR011 | DataHub reported a generic issue in the component. |
BCO_DH_ERR012 | DataHub reported a query issue. |
BCO_DH_ERR014 | DataHub reported a data-dependent issue in a query. |
BCO_DH_ERR015 | DataHub exhausted the connection pool to the database. |
| BCO_DH_ERR016 | DataHub tried to send an email but the configured SMTP host is unknow. |
ETL tasks
Error code | Description | |
|---|---|---|
BCO_ETL_FAIL001 | An ETL reported an issue on the file system (probably disk is full). | |
BCO_ETL_FAIL002 | An ETL reported an Out-of-Memory issue. | |
BCO_ETL_FAIL003 | An ETL reported a "No Space Left on device" issue. Disk is full. | |
BCO_ETL_FAIL101 | An ETL discovered a malformed URL specified for connecting to a data source exposing HTTP or SOAP API. | |
BCO_ETL_FAIL102 | An ETL did not recognize data source, or wrong parameters were specified for connecting to a data source. For example, the connector supports VMware 4 while the datasource reports VMware 3, or the connector supports NetApp Manageability (NM) SDK, while the URL provided is EMC2. | |
BCO_ETL_FAIL103 | An ETL reported a user access denial; wrong user or password specified for connecting to a datasource. | |
BCO_ETL_FAIL104 | An ETL reported that wrong database connection parameters were specified, or it was unable to open a connection to the database (database not reachable) for connecting to a datasource with a SQL connection. | |
BCO_ETL_FAIL105 | An ETL specified a wrong directory for file extraction (directory not found). | |
BCO_ETL_FAIL106 | An ETL reported that all files processed are malformed (datasource or format not recognized). | |
BCO_ETL_FAIL107 | An ETL reported a failure loading data to BMC TrueSight Capacity Optimization data warehouse (no data could be loaded for the datasource) due to a fatal problem in the load phase. | |
| BCO_ETL_FAIL108 | An ETL cannot be started due to misconfiguration or operating system problems. | |
| BCO_ETL_FAIL109 | An ETL reported a failure due to connection to a non supported external datasource or datasource/program version. | |
| BCO_ETL_FAIL110 | A vCenter service ETL is reporting critical errors during data extraction. | |
| BCO_ETL_FAIL111 | A service ETL is reporting critical errors during data extraction. | |
| BCO_ETL_FAIL112 | A service ETL is reporting critical errors during data load to Capacity Optimization database. | |
| BCO_ETL_FAIL113 | A VMware ETL is unable to connect to the vCenter as the server certificate does not conform to expected JVM security constraints. Resolution: Change the vCenter SSL key to use a self-signed certificate. For more information, refer to the VMware documentation. | |
| BCO_ETL_FAIL114 | An ETL detected an error in network name resolution for a given host | |
| BCO_ETL_FAIL115 | Provided query is not a read-only query. Aborting query execution | |
BCO_ETL_ERR011 | An ETL reported a generic issue in the component. |
Internal error. If you get the error for one of the OOTB ETLs, call Customer Support. If you get the error for a custom ETL, check with the ETL developer. |
BCO_ETL_ERR012 | An ETL reported a query issue. | |
BCO_ETL_ERR014 | An ETL reported a data-dependent issue in a query. | |
BCO_ETL_ERR015 | An ETL exhausted the connection pool to the database. | |
| BCO_ETL_ERR016 | An unsupported operation was attempted by the current login user for example, current configured user has no sufficient rights to perform an operation. | |
| BCO_ETL_ERR117 | The ETL has detected a problem while populating data into the BMC TrueSight Capacity Optimization database. This could be due to a database problem, or malformed data. | |
| BCO_ETL_ERR104 | The requested system template cannot be looked up using the ID and/or name provided in the call | Check the lookup name of the specified system templates |
| BCO_ETL_ERR107 | The template/capacity pool/ capacity container element has not been selected for reservations | Select the element for reservations from the UI |
| BCO_ETL_ERR108 | The input XML file is malformed or does not conform to XSD | Review the syntax in the XML file and ensure it conforms to the XSD |
BCO_ETL_WARN301 | An ETL execution took longer than expected. | |
BCO_ETL_WARN302 | An ETL reported that some records were discarded during load to BMC TrueSight Capacity Optimization Data Warehouse, probably due to malformed data. | |
BCO_ETL_WARN303 | An ETL reported that some of the files processed are malformed and have been excluded. | |
| BCO_ETL_WARN304 | An ETL reported that the database table or view or column is missing. | |
| BCO_ETL_WARN305 | An ETL reported that a dataset is wrongly populated. Check ETL dataset population. | Internal error. If you get the error for one of the OOTB ETLs, call Customer Support. If you get the error for a custom ETL, check with the ETL developer. |
| BCO_ETL_WARN306 | An ETL reported that No Data are available for the requested time intervals | |
| BCO_ETL_WARN307 | ETL reported that directory specified for data parsing is empty or does not contain any valid file |
System tasks
Error code | Description |
|---|---|
BCO_TASK_FAIL001 | A system task reported an issue on the file system (probably disk is full). |
BCO_TASK_FAIL002 | A system task reported an Out-of-Memory issue. |
BCO_TASK_FAIL003 | A system task reported a "No Space Left on device" issue. Disk is full. |
| BCO_TASK_FAIL004 | It is not possible to retrieve the Task's configuration. |
| BCO_TASK_FAIL005 | Task fails due to an unrecoverable error . |
BCO_TASK_FAIL101 | Report executor task reported that the connection to Database cannot be established (probably the configuration is incorrect). |
| BCO_TASK_FAIL102 | Auto Analyses task reported that the connection to Database cannot be established (probably the configuration is incorrect). |
| BCO_TASK_FAIL103 | On Demand Analyses executor task reported that the connection to Database cannot be established (probably the configuration is incorrect) |
| BCO_TASK_FAIL104 | On Demand Model Solver task reported that the connection to Database cannot be established (probably the configuration is incorrect). |
| BCO_TASK_FAIL105 | Deployment Task is not able to find the deployment file to perform. |
| BCO_TASK_FAIL106 | Deployment Task is not able to copy custom ETL module into ETL engine. |
| BCO_TASK_FAIL107 | Deployment Task manual run. |
| BCO_TASK_FAIL108 | Cyclical dependency detected in two or more hierarchy rules. Maximum number of iteration exceeded. |
| BCO_TASK_FAIL109 | Process terminated abnormally. |
| BCO_TASK_FAIL110 | Search Index Updater is not able to build index. |
| BCO_TASK_FAIL111 | Search Index Updater is not able to update index. |
| BCO_TASK_FAIL112 | A system task execution took more than expected, and has been terminated (it was configured to die on timeout expiration). |
| BCO_TASK_FAIL113 | Optimizer task execution fails due to an internal exception. |
| BCO_TASK_FAIL114 | Impossible to complete the cleaning of All Dismissed Objects. |
| BCO_TASK_FAIL115 | Deployment file not valid |
| BCO_TASK_FAIL116 | Maintenance activities auto-deploy fails because container folder is missing. |
BCO_TASK_ERR011 | A system task reported a generic issue in the component. |
BCO_TASK_ERR012 | A system task reported a query issue. |
BCO_TASK_ERR014 | A system task reported a data dependent issue in a query. |
BCO_TASK_ERR015 | A system task exhausted the connection pool to the database. |
| BCO_TASK_ERR101 | Optimizer task execution reported an exception during heuristic execution. |
| BCO_TASK_ERR102 | Optimizer task execution reported a generic exception. |
| BCO_TASK_ERR103 | Hierarchy Task mixing Change mode and Asset mode. |
| BCO_TASK_ERR104 | Hierarchy Task found an unexpected number of row in the OBJ_REL_STAGE. Transaction ignored. |
BCO_TASK_WARN301 | A system task execution took longer than expected. |
| BCO_TASK_WARN302 | Hierarchy manager task found duplicate statements in a OBJREL transaction |
Console
Error code | Description |
|---|---|
BCO_WEB_FAIL001 | Console reported an issue on the Application Server file system (probably disk is full). |
BCO_WEB_FAIL002 | Console reported an Out-of-Memory issue on the Application Server. |
| BCO_WEB_FAIL003 | Console reported a "No Space Left on device" issue. Disk is full |
BCO_WEB_FAIL101 | Console service unavailable. (Probably, the database is unreachable or the configuration is incorrect.) |
BCO_WEB_FAIL102 | LDAP server not responding. (Probably, the LDAP server is unreachable or the configuration is incorrect.) |
BCO_WEB_FAIL103 | SSO server not responding. (Probably the BMC Atrium SSO server is unreachable or the configuration is incorrect.) |
BCO_WEB_FAIL104 | Console reported that reports cannot be generated because the connection to Database cannot be established. (Probably the configuration is incorrect.) |
BCO_WEB_ERR011 | Console reported a generic issue in the component. |
BCO_WEB_ERR012 | Console reported a query issue. |
BCO_WEB_ERR014 | Console reported a data dependent issue in a query. |
BCO_WEB_ERR015 | Console exhausted the connection pool to the database. This error can be caused due to abrupt termination of the Database connection, and can be verified using the cpit.log file. Collect the log files using the Log grabber and contact BMC Customer Support. |
BCO_WEB_ERR016 | Console tried to send an email but the configured SMTP host is unknown. |
BCO_WEB_ERR111 | A SQL query of an out-of-the-box View has failed. (Probably Database server is unreachable or Database configuration is incorrect.) |
BCO_WEB_ERR112 | Unable to open the online help, probably caused due to connectivity issues. If the BMC TrueSight Capacity Optimization application server is not connected to the Internet, update the Global configuration setting, Help mode, to use the Local version Navigate to Administration > System > Global Configuration and select the General tab. From the Help mode drop down, select Local version. |
BCO_WEB_WARN301 | Nonexistent user or wrong password. Please check your credentials. |
BCO_WEB_WARN302 | You have exceeded the maximum number of sessions assigned to your account. Select the checkbox below to force the most outdated session for this account to be terminated and initiate a new session. |
| BCO_WEB_WARN303 | The SQL query references a not existent table. (Probably some SQL data marts were not materialized yet.) |
Scheduler
Error code | Description |
|---|---|
BCO_SCH_FAIL001 | Scheduler reported an issue on the file system (probably disk is full). |
BCO_SCH_FAIL002 | Scheduler reported an Out-o- Memory issue. |
| BCO_SCH_FAIL003 | Scheduler reported a No Space Left on device issue. Disk is full |
| BCO_SCH_FAIL004 | Scheduler reported that a program cannot be started. Program can be not executable, file doesn't exists or path to executable is wrong. |
BCO_SCH_FAIL101 | Scheduler reported an issue on a specific file system. File system utilization is over the threshold. |
| BCO_SCH_FAIL102 | Scheduler reported a linkage issue. This could be caused by compilation error/broken build or wrongly applied patch/corrupted patch. |
BCO_SCH_ERR011 | Scheduler reported a generic issue in the component. |
BCO_SCH_ERR012 | Scheduler reported a query issue. |
BCO_SCH_ERR014 | Scheduler reported a data-dependent issue in a query. |
BCO_SCH_ERR015 | Scheduler exhausted the connection pool to the database. |
BCO_SCH_ERR016 | Scheduler tried to send an email message but the configured SMTP host is unknown. |
BCO_SCH_ERR112 | The database date is not aligned with the application server. |
Chargeback service
ERROR CODE | DESCRIPTION |
|---|---|
BCO_CHGS_FAIL001 | Chargeback service reported an issue on the file system (probably disk is full). |
BCO_CHGS_FAIL002 | Chargeback service reported an Out Of Memory issue. |
BCO_CHGS_FAIL003 | Chargeback reported a No Space Left on device issue. |
BCO_CHGS_ERR011 | Chargeback service reported a generic issue in the component. |
BCO_CHGS_ERR012 | Chargeback service reported a query issue. |
BCO_CHGS_ERR014 | Chargeback service reported a data dependent issue in a query. |
BCO_CHGS_ERR015 | Chargeback service exhausted the connection pool to the database. |
BCO_CHGS_ERR111 | Bad Request: Your client has issued a malformed or illegal request. |
BCO_CHGS_ERR112 | Incomplete relation: Some chargeback objects, that have been specified by the client do not provide a mandatory reference. |
BCO_CHGS_ERR113 | Invalid object: This error occurred when an object (specified by the client) does not provide a valid status. |
BCO_CHGS_ERR114 | Bad check: This is a particular condition (may be a coding problem) that makes a control not applicable. |
BCO_CHGS_ERR115 | Client failure: an object notification to BMC TrueSight Capacity Optimization returns an error. The error occurred during the rest call. |
BCO_CHGS_ERR116 | Chargeback client encountered unexpected problem and it was able to complete this task. |
BCO_CHGS_WARN301 | Client failure: A unit of measure in BMC Cloud Lifecycle Management has no associated BMC TrueSight Capacity Optimization metric in the chargeback configuration file.Update the configuration file and rerun the ETL. |
Warehouse service
Error code | Description | Solution |
|---|---|---|
BCO_WHS_ERR111 | Out-of-partition sample found. | Verify that the aging configuration and Database Space Manager task are healthy. Also, verify the ETL date recognition for file parser. |
BCO_WHS_ERR112 | Partitions not defined. | Verify that the Database Space Manager task is healthy. Also, verify the Database Instance tablespaces and file system free space |
| BCO_WHS_WARN301 | Timeout expired while waiting for threads termination: please investigate on possible database locks or network issues. | |
| BCO_WHS_FAIL101 | Near-real-time Warehouse service has detected a potential locking condition preventing to process new data. Please refers to service logs for further details. |
Analysis service
| ERROR CODE | DESCRIPTION |
|---|---|
| BCO_ANS_ERR011 | Analysis Service reported a generic issue in the component. |
| BCO_ANS_WARN301 | Analysis Service could not complete properly the execution due to the lack of data. |
Auto Forecasting Service
| ERROR CODE | DESCRIPTION | SOLUTION |
|---|---|---|
BCO_AFS_FAIL101 | Auto Forecasting Service is not responding correctly, a client reported that the connection cannot be established. | Check Data Hub and Auto Forecasting Service status. |
Reservations
| ERROR CODE | DESCRIPTION | SOLUTION |
|---|---|---|
| BCO_RSV_ERR011 | Reservation Service reported a generic issue in the component | |
| BCO_RSV_ERR012 | Reservation Service reported a query issue | |
| BCO_RSV_ERR014 | Reservation Service reported a data dependent issue in a query | |
| BCO_RSV_ERR015 | Reservation Service exhausted the connection pool to the database | |
| BCO_RSV_ERR101 | The request is invalid | Check the type specified for the parameters |
| BCO_RSV_ERR102 | The request is missing one or more mandatory parameters | Check the parameters |
| BCO_RSV_ERR103 | The requested reservation/onboarding/item/template could not be found by ID. | Check if the specified entity ID exists |
| BCO_RSV_ERR104 | The requested system template cannot be looked up using the ID and/or name provided in the call | Check the specified entity lookup field (For example, call to list) |
| BCO_RSV_ERR105 | The system template cannot be deleted because it is used in a reservation or in a model | Remove the dependencies that are using the system template before removing the system template |
| BCO_RSV_ERR106 | The reservation status cannot be changed | |
| BCO_RSV_ERR107 | The template/capacity pool/ capacity container element has not been selected for reservations. | Select the respective element for the reservations from the UI |
| BCO_RSV_ERR108 | System template lookup name is already used for another template | Specify a unique lookup name for the template |
| BCO_RSV_ERR109 | Multiple tag type entries are detected with the same type name | Use a type name that corresponds to a single tag_type entry |
| BCO_RSV_ERR110 | Lookup by name or lookup fields returns more than one system | Specify lookup by ID to clearly identify the system. |
| BCO_RSV_ERR111 | The type of existing system templates cannot be changed | Provide the same value that was used to generate the system template in the entypenm field |
| BCO_RSV_ERR112 | The onboarding cannot be deleted | Check if it is an hypothetical container with some items placed on it |
| BCO_RSV_ERR113 | The reservation will be infeasible because a reservation target is no longer valid | |
| BCO_RSV_ERR114 | The reservation will be infeasible because another reservation will exhaust the capacity | |
| BCO_RSV_ERR115 | The associated tenant is no longer a child of root domain | |
| BCO_RSV_ERR116 | Reservation Target resource consumption exceeds error threshold | |
| BCO_RSV_ERR117 | At least one Reservation Target resource consumption exceeds error threshold | |
| BCO_RSV_ERR118 | You cannot assign a Reservation to a Tenant because the required Reservation setting (Associate reservations with tenants) is not enabled. | You must enable association of reservations with tenants from the console. For more information, see Reservation Settings |
| BCO_RSV_ERR119 | Resource instance type is not supported. | Use a resource instance that is of supported type. |
| BCO_RSV_FAIL001 | Reservation Service reported an issue on the Application Server file system (probably disk is full) | Check the Application Server disk space status |
| BCO_RSV_FAIL002 | Reservation Service reported an Out Of Memory issue | Check the memory available |
| BCO_RSV_FAIL003 | Reservation Service reported a No Space Left on device issue. Disk is full | Check the space available |
| BCO_RSV_WARN301 | The resources and items specified in update of reservation are not consistent | Check the resources and items section and ensure they represent the same view of used templates. |
| BCO_RSV_WARN302 | The reservation will be infeasible because the reservation will exhaust the capacity | |
| BCO_RSV_WARN303 | Realization mode is manual. The start date is passed but the reservation is still not placed. | |
| BCO_RSV_WARN304 | Realization mode is manual. The start date is passed but the reservation is still not realized. | |
| BCO_RSV_WARN305 | Realization mode is manual. The end date is passed but the reservation is still not expired. | |
| BCO_RSV_WARN306 | Tenant resource allocation exceeds allocated quota | |
| BCO_RSV_WARN307 | Tenant resource allocation will exceed allocated quota | |
| BCO_RSV_WARN308 | Tenant is associated to the current reservation but the root domain is not specified | |
| BCO_RSV_WARN309 | Reservation Target resource consumption exceeds warning threshold | |
| BCO_RSV_WARN310 | At least one Reservation Target resource consumption exceeds warning threshold | |
| BCO_RSV_WARN311 | A reservation item has been replaced with another one with a different technology and it was removed from its reservation target | |
| BCO_RSV_WARN312 | This reservation is not assigned to any capacity pool compatible with technology of reservation items |
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks