You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
does anyone know, how to dig into the python code of dbt-oracle?
The following situation makes me want to dive deeper into the code:
A running version of dbt-oracle processes a project sucessfully inside a python container on vm a. Since the vm's os needs an update we need to migrate from vm a to vm b. The only thing that changes is the os and the python container (same version) and the dbt versions (dbt-core and abt-oracle) and the projects stay the same.
In case of a materialized=table config the project won't run. The error message is: ORA-00955 name is already used by an existing object
What we found out is that the regular process is:
create a temporay table named xyz__dbt_tmp
rename target table in xyz__dbt_backup
rename xyz__dbt_tmp into target table name (xyz)
delete backup table
In our case step 2 is not processed and therefore we get the error, since the target table was never renamed and the alter statement is trying to rename the temp table to the target table which is still existing.
Now we're trying to figure out what exactly makes the process skip that one command because we analyzed the legacy and the new setup but didn't find differences. We even tried variing parameters, versions etc. but nothing helped.
Any suggestions on which python-part is responsible to do the alter statements so I can try to find diffs or reasons in the code?
Or better, any ideas why this is happening?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
does anyone know, how to dig into the python code of dbt-oracle?
The following situation makes me want to dive deeper into the code:
A running version of dbt-oracle processes a project sucessfully inside a python container on vm a. Since the vm's os needs an update we need to migrate from vm a to vm b. The only thing that changes is the os and the python container (same version) and the dbt versions (dbt-core and abt-oracle) and the projects stay the same.
In case of a materialized=table config the project won't run. The error message is:
ORA-00955 name is already used by an existing object
What we found out is that the regular process is:
In our case step 2 is not processed and therefore we get the error, since the target table was never renamed and the alter statement is trying to rename the temp table to the target table which is still existing.
Now we're trying to figure out what exactly makes the process skip that one command because we analyzed the legacy and the new setup but didn't find differences. We even tried variing parameters, versions etc. but nothing helped.
Any suggestions on which python-part is responsible to do the alter statements so I can try to find diffs or reasons in the code?
Or better, any ideas why this is happening?
Many thanks
Beta Was this translation helpful? Give feedback.
All reactions