Sync Failed due to normalisation failure!! *Last a...
# replication-troubleshooting
f
Sync Failed due to normalisation failure!! *Last attempt:*106.2 MB210,806 emitted records210,806 committed records1m 54s Failure Origin: normalization, Message: Normalization failed during the dbt run. This may indicate a problem with the data itself.
Copy code
2022-12-05 21:45:37 normalization > Completed with 2 errors and 0 warnings:
2022-12-05 21:45:37 normalization > Database Error in model employees_stg (models/generated/airbyte_incremental/jisr_rr/employees_stg.sql)
2022-12-05 21:45:37 normalization >   time zone displacement out of range: "+105454-01-01"
2022-12-05 21:45:37 normalization > Database Error in model payruns_stg (models/generated/airbyte_incremental/jisr_rr/payruns_stg.sql)
2022-12-05 21:45:37 normalization >   time zone displacement out of range: "+20225-08-25T09:18:47.000000"
2022-12-05 21:45:37 normalization >   CONTEXT:  parallel worker
2022-12-05 21:45:37 normalization > Done. PASS=39 WARN=0 ERROR=2 SKIP=4 TOTAL=45
2022-12-05 21:45:37 INFO i.a.w.g.DefaultNormalizationWorker(run):93 - Normalization executed in 47 seconds.
2022-12-05 21:45:37 ERROR i.a.w.g.DefaultNormalizationWorker(run):101 - Normalization Failed.
2022-12-05 21:45:37 INFO i.a.w.g.DefaultNormalizationWorker(run):106 - Normalization summary: io.airbyte.config.NormalizationSummary@7552a195[startTime=1670276689822,endTime=1670276737454,failures=[io.airbyte.config.FailureReason@50b1ff7[failureOrigin=normalization,failureType=system_error,internalMessage=time zone displacement out of range: "+105454-01-01",externalMessage=Normalization failed during the dbt run. This may indicate a problem with the data itself.,metadata=io.airbyte.config.Metadata@552949c2[additionalProperties={attemptNumber=2, jobId=79, from_trace_message=true}],stacktrace=AirbyteDbtError: 
9 of 45 ERROR creating incremental model _airbyte_jisr_rr.employees_stg................................................. [ERROR in 1.08s]
Upon working to produce the error from the source tables (aws postgres), none of the date/timestamp columns could through this error. Did anyone face this issue?
u
Hello Faris, it's been a while without an update from us. Are you still having problems or did you find a solution?
f
My only work around was to replicate the tables that has the same problem as raw json and do normalisations with dbt (strangely that didn’t run into the issues airbyte basic normalisations faced)
s
Thanks for the update Faris, hopefully this helps other users who face the same issue. I’m not exactly sure why normalization failed in this case but happy to hear that you were able to do the normalizations using dbt yourself
g
yeah same problem here, no problems with any timezone aware date columns, but still getting this error I'll def try to load it as raw json then normalize with dbt myself, tks!