|
1. Module Error Codes The first two digits of the error code are the module code, representing the functional module to which the error belongs.
Main Module | Module Code | Common | 11 | Data Connection | 12 | Dataset | 13 | Data execution | 14 | Dashboard | 15 | Portfolio Dashboards | 16 | Portal | 17 | Scheduling Tasks | 18 | System Management | 19 | WebAPI | 20 | Dataset | 21 | Bloodline Analysis | 22 | In-depth analyses | 23 | Fill in the blanks | 24 | Process Approval | 25 | Desktop | 26 |
2. Detailed Error Codes 2.1 Data Connection 2.1.1 120000003
Error Code | Error content | 120000003 | Unable to connect to database, specific reason XXX |
Problem description: Cannot connect to the database. Troubleshooting method: Check the database driver version. Problem Cause: The driver version is too low, the driver that comes with the product does not correspond to the version of the database used. Solution: Customise and upload a new version of the driver.
2.1.2 120000016
Error Code | Error message content | 120000016 | Database driver XX was not found, please verify that the driver name is correct. |
Problem description: connection error g5.util.GRTException: database driver not found please verify the driver name is correct. Troubleshooting: 1)Go to the product deployment directory vividime\jdbcDriver\Default to check if the default driver exists. 2)On the Add Connection page, click "Driver Management" to check if the uploaded custom driver exists. Problem Cause: 1)The default driver was not found. 2)No custom driver is uploaded or the custom driver is invalid. Solution: add Connection page and re-upload the custom driver.
2.1.3 120000043
Error Code | Error Content | 120000043 | Unable to connect to Connection XX for specific reason XXX |
Problem description: database connection error Communications link failure. Troubleshooting: 1)Check the URL to see if it contains useSSL=false. Problem Cause: The customer locally uses the cenos8 system, which may involve security upgrades. Solution: Splicing &useSSL=false after the database connection URL. 2)First, test whether it is possible to communicate with the database through Ping and Telnet commands; check whether the firewall is closed; use database connection tools to test whether it is possible to connect successfully; check the product logs to see the corresponding error messages. Problem Cause: The product has the attribute conn.create.timeout=30000, the default time to try to connect to the database is 30 seconds, more than 30 seconds without connecting to the timeout prompt will pop up. Solution: Change the value of the property conn.create.timeout to a longer time, such as 2 minutes (120,000ms), restart the product, and then try to test the connection again.
2.2 Datasets 2.2.1 130000218
Error Code | Error content | 130000218 | Failed to execute SQL: XX |
Possible scenario: •Writing a stored procedure in an ORACLE database reports an error: PROBLEM CAUSE: The stored procedure name in the sql statement does not need to be identified with quotes. Solution: there is a difference whether identification is required or not, please consult the database related manuals. •Error returned by database problem when entering Data Mart load data. Problem Cause: Due to the database travelling problem causes load data error, such as: too many database connections cause this connection failure. Solution: According to the error information returned by the database, search for relevant solutions, such as changing the database connection limit, etc., or modify the sql to solve the problem.
2.2.1 130000034
Error Code | Error content | 130000034 | Failed to discard empty parameter: XX in XXX |
Problem description: Previewing a Dataset or Dashboard without passing values to the parameters will report an error. Troubleshooting: Firstly, confirm whether the parameter is referenced when customising the sql statement in the sql Dataset, for example: select * from table where ID > ? {param1}, in the execution of the data is not passed to the parameter value. Cause of the problem: the parameter is not passed a value. Solution: If you confirm that the current scenario is about not passing values to the parameters, go ahead and modify the sql to read: select * from table <param1> where ID > ? {param1} <param1>, for details, please refer to the first point in Parameter Usage in Dataset.
2.3 Data Execution 2.3.1 140000004
Error Code | Error content | 140000004 | Column does not exist: XX |
•Dataset column does not exist. Usually the self-service Dataset reports that the column does not exist, the troubleshooting steps are as follows: 1) Check from the end node forward to find the node that first reported the column does not exist. 2)Check to see if the column that reported the error exists in the metadata (remember to look at the hidden columns), if it does not exist, it is correct to report that the column does not exist, if the column exists, continue with the following steps. 3)Look at this node to see if there is a calculated column or filter, hidden one by one, to identify which calculated column or filter conditions reported that the column does not exist. 4)Edit the calculation column to see if the col in the calculation column is written correctly, and whether there are more spaces before and after, if there are spaces, it will not match with the column name, and it is correct to report that the column does not exist, and you can adjust the calculation column. 5)If the columns are all matched on the report still does not exist, the probability is a bug, you can mention the process. •Dashboard report columns do not exist Similar to the steps for troubleshooting non-existent columns in Dataset. 1)First confirm which component reported columns do not exist, you can view the log, the following figure, the log will show the name of the component that reported the error. 2)Delete irrelevant components to exclude the influence of other components. 3)Check if the column that reported the error exists in the metadata (remember to look at the hidden columns), if it does not exist, it is correct to report that the column does not exist, if the column exists, continue with the following steps. 4)Look at the Dashboard to see if there are any calculated columns, bind them one by one, and troubleshoot which one of the calculated columns is reported as not existing. 5)Edit the calculation column, check whether the col in the calculation column is written correctly, and whether there are more spaces before and after, if there are spaces, it will not match with the column name, and it is correct to report that the column does not exist, and you can adjust the calculation column. 6)If the columns are matched on the still report columns do not exist, may be a bug, you can mention the process. Summary: the problem of non-existent columns is usually related to the calculation of columns, calculation of columns multi-layer nesting, multi-layer nested Dataset or calculation of columns referenced by the original column to change the alias, will lead to find the columns reported columns do not exist, troubleshooting attention to see if the customer has done these operations.
2.4 Data Marts 2.4.1 110000057
Error Code | Error content | 110000057 | Column data type inconsistency: XX. |
Problem Cause: Datasets with different names but the same columns are incrementally imported into the same Dataset folder at the same time, but there are columns in the Dataset with inconsistent data types. Solution: Adjust the data column types to be consistent.
2.4.2 210000162
Error Code | Error content | 210000162 | Failed to divide data: xx. |
Problem Cause: Reason 1: The join process is exchanged to the disk by LINK resulting in insufficient disk space, and insufficient disk space triggers the program to delete some exchange files to ensure normal operation of the program. Solution: Increase disk space. Reason 2: Multi-threading problem Solution: Provide the bi log of the time period of the error report to track after the resale. Cause 3: Null pointer caused by the failure of the entry Mart, there are two stack logs that need to be analysed. Solution: Provide bi.log containing the error reporting stack for post-sale analysis. If the exception stack is not printed, you need to add -XX:-OmitStackTraceInFastThrow in the jvm parameters to ensure that the exception stack is printed.
2.4.3 210000120
Error Code | Error content | 210000120 | Failed to send MAP task: xx. |
Troubleshooting steps: 1) Whether single M node is down; check whether any of the M nodes are down under multiple M nodes, and whether the zb that failed to send MAP task is stored on the M node that is down; 2)Check whether the zb file of the failed map task is in the monitoring system - Mart folder information statistics, find the corresponding Mart folder, check whether the specific zb file exists, and the IP of the distribution machine is normal. 3) After the above checks are normal, then you need to provide bi.log to view the stack after the map task failed in order to locate exactly what problem caused the map task failure. Processing: It is necessary to provide the error stack in the log in order to locate the specific problem.
2.5 System Management 2.5.1 190000206
Error Code | Error content | 190000206 | Failed to write file, specific reason: XXXX. |
This error occurs when the database system is synchronised, the specific reason is reported when packet for query is too large: Reason: The default value of the max_allowed_packet attribute of the database is smaller than the actual uploaded data. Solution: You need to set max_allowed_packet in the database. Example: set global max_allowed_packet = 10*1024*1024*10.
2.5.2 190000080
Error Code | Error Code | 190000080 | The licence is not legal. |
If the licence is not legal, check the following: 1)Check whether there is a \ in the licence, if so, remove the \ and try again. 2)Check the mac, go to the authorisation verification page on the official website to verify if the license is legitimate and for how long. 3) Check the legality of the installation package: whether the installation package is normal and whether the version matches.
| 
