I am Anisim and i am big trouble. I installed Oracle 11gR2 and ArcSDE 10.1. I created an Enterprise Geodatabase with <Create Enterprise Geodatabase>, then I added a Database Connection on the new geodatabase.
We found that the database is not empty! There are many tables oracle!
I requested the table list as ASCII in the post because others could then search on the table names and find this thread. Attachments are not searchable, so no one will find the references to these SCOTT, IX, OE, SH, or HR tables.
If you install Oracle from scratch, rather than using the pre-built database filled with samples, and disable the capabilities you don't need, there will be far fewer "junk" tables clogging up your instance. These tables have nothing to do with ArcSDE or geodatabase functionality, so you may ignore them, or drop the users (with CASCADE), or reinstall Oracle as you see fit. But I would recommend some Oracle training, so you can better recognize trouble when it arrives.
The SDE user should own all the tables specified in the documentation to implement the geodatabase. The ArcSDE API hides these tables as well as most system tables to reduce confusion, but other packages in your install may create nominal tables to which PUBLIC access has been granted. Seeing these isn't "big trouble".
You shouldn't ever use the SDE user for data creation; instead create one or more tablespaces and one or more users with access to those tablespaces for geo data management.
Hi, I try to create a new <Tablespace> and a new <User> and run <Create Enterprise Geodatabase> Tool, but this trouble still exist. Oracle tables appear on this new connection.
I do not know where I'm wrong? For me still a big trouble!
I requested the table list as ASCII in the post because others could then search on the table names and find this thread. Attachments are not searchable, so no one will find the references to these SCOTT, IX, OE, SH, or HR tables.
If you install Oracle from scratch, rather than using the pre-built database filled with samples, and disable the capabilities you don't need, there will be far fewer "junk" tables clogging up your instance. These tables have nothing to do with ArcSDE or geodatabase functionality, so you may ignore them, or drop the users (with CASCADE), or reinstall Oracle as you see fit. But I would recommend some Oracle training, so you can better recognize trouble when it arrives.