Hi Max,

> FBOwnerMigrator looks like it will probably help me out with my owner
> problems, but I'm not 100% sure of this. The database in question is
> currently owned by sysdba. The system tables in the database are owned
> by sysdba, but the other objects are either owned by user1 or user2. I
> would like the database to be owned by user2 and all the objects within
> it to have their creator set to user2.

FBOwnerMigrator is able to handle that.

> There are a few complications here. Firstly, I think FBOwnerMigrator
> assumes that one user is both the database owner and the creator of the
> objects within that database.

Nope. There can be several different owners in your database. FBOM
should be able to handle this. You need to make sure, that each owner is
present as a user in the user database, because FBOM will loop through
all owners and you need to connect with each owner at a given time.

If I restore the database as user2

Then user2 is the owner of the database and the owner of the system tables.

and

> then tell FBOwnerMigrator to migrate from user1 to user2, will this end
> up with all objects being owned by user2 (as desired)

Yes.

or will it get

> confused by the fact that the system tables are owned by sysdba and that
> some objects are already owned by user2?
>
> Secondly, the user1 account that owns some of the objects has actually
> been deleted. Will it be sufficient for me to simply create another
> account with the same name and a known password?

Yes.

FBOM allows you to migrate a database with 1..n owner to one particular
owner which owns both the database and the objects included in the database.


--
HTH,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com