Index tablespace empty

Discussion created by frenkelj on May 21, 2014
Latest reply on Jun 3, 2014 by frenkelj
We have a number of user schemas in our enterprise geodatabase, and all of them have two tablespaces in our Oracle database, one for data and one for indexes. Recently a new user schema was created, but for some reason the indexes get stored in the tablespace reserved for the data. I guess the user schema has not been created correctly. Any ideas what could have gone wrong?

We usually do not use keywords, so the defaults are used. When creating indexes for feature classes in the other user schemas they are stored in the index tablespace, but not for this one which was created recently.

Joris Frenkel, Staatsbosbeheer, the Netherlands