[Bug] Renaming the old_relation does not work in Oracle 12c+ when using DBT table materialization with missing database name in profiles.yml

[ThoSap]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

1 of 1 START table model staging.test.......................................................................... [RUN]
1 of 1 ERROR creating table model staging.test................................................................. [ERROR in 0.96s]
oracle adapter: Oracle error: ORA-00955: name is already used by an existing object

Finished running 1 table models in 0.96s.

Completed with 1 errors and 0 warnings:

Database Error in model test (models/generated/airbyte_tables/staging/test.sql)
  ORA-00955: name is already used by an existing object
  compiled SQL at ../build/run/airbyte_utils/models/generated/airbyte_tables/staging/test.sql

Done. PASS=0 WARN=0 ERROR=1 SKIP=0 TOTAL=1

Expected Behavior

1 of 1 OK created table model staging.test..................................................................... [OK in 1.45s]

Finished running 1 table models in 1.45s.

Completed successfully

Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

Steps To Reproduce

Run the DBT table materialization twice.

Relevant log output using --debug flag enabled

No response

Environment

- OS: Oracle Linux Server 8.5
- Python: 3.9.9
- dbt: 1.0.6

What Oracle database version are you using dbt with?

Tested using

• Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
  and
• Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Additional Context

Pull request fix #3

[geoHeil]

I can confirm to have the same problem

[ThoSap]

@geoHeil what is your take on this #3 (comment)?
Please reply in the PR so we have everything in one place 😉