Liquibase run/generated query consumes all TEMP space, resulted oracle thrown an error.

Liquibase Development
1

While spring boot runs the liquibase, it does execute the below query and results “Unable to extend by 128 in tablespace TEMP”. Since our database has 200+ schemas, the all * views consumes lot of TEMP memory and throws error.


SELECT NULL AS TABLE_CAT, atc.OWNER AS TABLE_SCHEMA, atc.OWNER, atc.TABLE_NAME, atc.COLUMN_NAME, NULLABLE, ac.VALIDATED as VALIDATED, ac.SEARCH_CONDITION, ac.CONSTRAINT_NAME FROM **ALL_TAB_COLS** atc JOIN **all_cons_columns** acc ON atc.OWNER = acc.OWNER AND atc.TABLE_NAME = acc.TABLE_NAME AND atc.COLUMN_NAME = acc.COLUMN_NAME JOIN all_constraints ac ON atc.OWNER = ac.OWNER AND atc.TABLE_NAME = ac.TABLE_NAME AND acc.CONSTRAINT_NAME = ac.CONSTRAINT_NAME WHERE atc.OWNER='XXXX' AND atc.hidden_column='NO' AND ac.CONSTRAINT_TYPE='C' and ac.search_condition is not null AND atc.TABLE_NAME='DATABASECHANGELOG'

Why liquibase checking all * views in the database instead of the specific schema? is there a solution which fixes this issue?

2

@rajasekar.m , have a look at liquibase-tablespace-name | Liquibase Docs, might help with your current issue and overall setup.

Regards,
Eduard

3

@rajasekar.m I think this just boils down to a design decision to use ALL_* views instead of USER_* views to search for executed changesets (I think that is the intent of the query) in the database.