This topic describes common issues with synchronizing data to Hologres by using DataWorks Data Integration and provides troubleshooting steps.
- How do I synchronize data to Hologres by using open source DataX?
- Error: Holohub does not support the binary type of Hologres for now
- Error: internal error: Connect timeout, Connection refused.
- Error: ERROR: insufficient data left in message; nested exception is org.postgresql.
- Error: ERROR:internal error :column 2501 is not found in SparseSchema.
- Error: ERROR Worker - should not happen.
- Error: Refresh meta timeout, target version is xxx but current version is yyy.
- Error: Data overflow occurs when converting a value to the long data type.
- Error: Rejected by ip white list xxx .
Synchronize data to Hologres with open source DataX
Use the open source Hologres Writer, which offers better performance than the traditional PostgreSQL Writer, to synchronize data to Hologres. This connector is open source. For more information, see Usage on GitHub.
Error: Holohub does not support the binary type of Hologres for now
- Cause: The write mode is set to SDK mode, which does not support the data type (such as JSONB) used to create the Hologres table.
- Solution: Change the write mode to INSERT mode.
Error: internal error: Connect timeout, Connection refused.
- Cause: A Hologres node restarted unexpectedly.
- Solution: Retry the failed task. If the error persists, contact technical support for assistance.
Error: ERROR: insufficient data left in message; nested exception is org.postgresql.
org.springframework.dao.DataAccessResourceFailureException: StatementCallback; SQL UPDATE xxx_user_v6jk3jdgt4zavy2btpkglwje SET first_version=C
xxx CE xxx _s_upd xxx
xxx ESCE( xxx ) xxx store 'Google' xxx : ERROR: insufficient data left in message; nested exc
eption is org.postgre xxx 11.PSQLException: ERROR: insufficient data left in message
at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:107)
- Cause: The source data contains dirty data.
- Solution: Check the source data and filter out any dirty data.
Error: ERROR:internal error :column 2501 is not found in SparseSchema.
org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [_TEMPLATE_xxx xxx_xxx xxx
xxx xxx
hema.xxx ']; SQL state [XX000]; error code [0]; ERROR: internal error: Column 2501 is not found in SparseSchema.
Where: [query_id:20011107142595326]; nested exception is org.postgresql.util.PSQLException ERROR: internal error: Column 2501 is not found in SparseSchema.
Where: [query_id:20011107142595326]
at org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTemplate.java:1542)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java xxx)
Solution: Retry the task. If the error persists, contact technical support.
Error: ERROR Worker - should not happen.
[embedded-holo-client-worker] ERROR Worker - should not happenjava.lang.NoSuchMethodError: org.postgresql.model.Column.setPrecision(I)V at com.alibaba.hologres.org.postgresql.util.MetaUtil.getRecordSchema(MetaUtil.java:274) ~[holo-client-1.2.16.3.jar:na]
- Cause: A conflict exists because the project includes two conflicting driver packages.
- Solution: Check the
Holo-ClientandPostgreSQL-Holopackages in your project. Remove thePostgreSQL-Holodependency and retain only one version ofHolo-Client.
Error: Refresh meta timeout, target version is xxx but current version is yyy.
- Cause: A Hologres node restart or frequent Data Definition Language (DDL) operations can cause this error by creating a metadata version mismatch between nodes.
- Solution: To quickly resolve this issue, restart the instance. Alternatively, find and terminate long-running queries. For more information, see Manage Queries.
Error: Data overflow during long type conversion
- Cause: The source data contains an unsupported data type, such as
BIGINT(20) UNSIGNEDfrom a MySQL source. - Solution: Modify the data type in the target Hologres table. For example, change the data type to
TEXT. For more information, see MySQL Data Type Mapping.
Error: Rejected by ip white list xxx .
- Cause: The Hologres instance's IP address whitelist is blocking write requests from unauthorized IP addresses.
- Solution:
- If the write mode is SDK mode, change it to INSERT mode.
- If the error persists in INSERT mode, the IP address whitelist is blocking the request. Add the IP address from the error message to the whitelist.
该文章对您有帮助吗?