So the question is This question is Assumed Answered. without any reply. Does it mean you found your own answer?
In this case you maybe don't want to forget the concept of Community forum: you get and you give. You found your answer? Share it to help others having the same issue. If you don't, why would others invest their time in helping you next time?
This was my 1st time using the tool so mistakenly cliked something as i was not aware. Let me know how to revert that option.
Apologies in advance
Ok, so you still have the question, that's the important piece
As your screenshot doesn't expand "dbo", are you saying that underneath "dbo" you have an existing "ADW12_XX" schema with already a bunch of tables inside?
Yes, dbo have an existing schema "ADW12_XX" with already a bunch of tables. when i am importing the tables or column from existing schema by Oracle Datawarehouse connection pool. the table(ex: ABC_CLASS_TMP) importing to under "ADW12_XX" schema which is newly generated.
Table ABC_CLASS_TMP should be import existing schema under "dbo" but it's not..
Could you please help me explain why this happens.
Thanks in advance..
What you see isn't really wrong, and not a big deal.
A Catalog is (based on the doc) :
Physical layer catalogs are optional ways to group different schemas.
A catalog contains all the schemas (metadata) for a physical database object. A schema contains only the metadata information for a particular user or application.
Therefore it isn't a real database object, it's just an artifact. When you import a new table OBIEE add it where it naturally belongs to: a table into a schema right underneath the database object. But once it's imported you can move the table where you want it. You must easily be able to move it in the right location and delete leftovers.
The advantage of the import is mainly to create all the columns etc., so if you have to move the imported object it isn't a big deal versus all the time you spare compared if you had to create everything by hand.