Description of problem:

In oVirt 3.6 engine and aaa-jdbc extension providing 'internal' domain are both installed in the same database using same database user. Engine is installed by default into 'public' schema, aaa-jdbc extension providing 'internal' domain is installed into 'aaa_jdbc' schema. Unfortunately engine db infrastructure functions included in common_sp.sql doesn't work properly if 'aaa_jdbc' schema is present.

Version-Release number of selected component (if applicable):

Any 3.6 version or master

How reproducible:

100%

Steps to Reproduce:

This is reproducing steps for fn_db_add_column function:
1. Create an upgrade script which will try to add column 'password_valid_to' to engine 'users' table
2. Execute engine-setup
3. Column 'password_valid_to' is not added into engine 'users' table, because column of the same name already exists in aaa-jdbc 'users' table

Actual results:

Engine database infrastructure functions doesn't work correctly if multiple schemas are present in engine database

Expected results:

Engine database infrastructure function should use only 'public' schema

Additional info: