The Oracle database has an SDE geodatabase. I have set up a new Oracle user with the appropriate privileges. When I run sdesetup with the following parameters, it states that, "Current user does not have privilege to install geodatabase instance."
sdesetup -o install -d oracle11g -i 5151:development -u development
I have logged into Oracle with an admin account and successfully granted all of the privileges that the error asks for, and I have done so twice. I have confirmed that the user has those privileges by checking Oracle's sqldeveloper gui program. Is there something I have missed?
Did you grant the 'development' user all the permissions that the SDE user requires for initial setup? I generally just grant DBA for long enough to install or upgrade, but the documentation is quite clear on what is required. Ironically, the user-schema geodatabase user requires *more* permissions than SDE after install, since the SDE user shouldn't ever own spatial data.
I realize the the documentation says that user-schema geodatabases are a great way to have dev, test, and production data in one instance, but that is as about as wrong as the documentation gets -- you don't get the benefit of isolation, and you can't limit the impact on production, and the naming must be different between "instances". In reality, only separate instances give the isolation that most shops require to distinguish between dev and production, so I urge you to be careful on how you utilize user-schema geodatabases.
Did you grant the 'development' user all the permissions that the SDE user requires for initial setup? I generally just grant DBA for long enough to install or upgrade, but the documentation is quite clear on what is required. Ironically, the user-schema geodatabase user requires *more* permissions than SDE after install, since the SDE user shouldn't ever own spatial data.
I realize the the documentation says that user-schema geodatabases are a great way to have dev, test, and production data in one instance, but that is as about as wrong as the documentation gets -- you don't get the benefit of isolation, and you can't limit the impact on production, and the naming must be different between "instances". In reality, only separate instances give the isolation that most shops require to distinguish between dev and production, so I urge you to be careful on how you utilize user-schema geodatabases.
