Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OBIEE 12.2.1 metadata import does not show freshly created user from a pluggable database

Received Response
1
Views
2
Comments
LaszloGal-Oracle
LaszloGal-Oracle Rank 1 - Community Starter

Using SampleApp V607 OVA image did the following steps

  1. log in to pdborcl container via the SQLDeveloper in the image using the connection: 'SYSTEM - Admin123 --pdborcl'
  2. Creating user in the pluggable datababase: create user NEWDBUSER identified by Admin123;
  3. starting OBIEE Client Admin tool v12.2.1.3.0 client (however v12.2.1.1.0 does the same)
  4. creating new database and connection pool in the physical layer: TESTDB, TESTCONNECTIONPOOL with the necessary connections
  5. right click on the connection pool and select Import Metadata, then leave everything default and click Next.
  6. The user list appears and there are many users in the list (not all of them though that are visible in the pdborcl via SQL connections) but the newly created user cannot be seen.

I wonder if there is a special additional setup for a freshly created new database user that needs to be done in order to make the user noticable to the OBIEE Admin tool's metadata import or not.

Any advice would be greatly appreciated

Answers

  • First thing to keep in mind: don't mix versions. Use the Admintool of the same version as the server or your RPD will be saved with a wrong version and you go straight into issues.

    Did you create objects in your new schema? In your description you just added a schema (user), but you don't say you added things inside.

    The import metadata is to load tables/views, so if you don't have anything you can't blame the tool for showing you only not-empty schemas.

    In your step 4) did you use the newly created user credentials?

  • LaszloGal-Oracle
    LaszloGal-Oracle Rank 1 - Community Starter

    Gianni,

    • Yes, I did create a table and a view.
    • Admin tool version:
      The server on the SampleApp V607 is 12.2.1.1.0
      The client version is 12.2.1.1.0
    • Yes I have used both SYSTEM and the newly created USER ID with their respective passwords. The connection did happen in both cases and the symptom is there.

    Further playing with the system I think I've accidentally found the reason why certain users are listed and others not.

    When I created a table under a user it did not appear.

    When I created a table and a view together, the user appeared on the list.

    There might be a bug here in the import of the metadata where it checks with the existence of both a table and view at least. This may need further investigation but so far this works for me.