Quantcast
Viewing all articles
Browse latest Browse all 92

prim10875:On Oracle single-instance database: “Error: Invalid Database. The database you are connecting to is not a Project Manager database.”

Solution ID: prim10875
On Oracle single-instance database: "Error: Invalid Database. The database you are connecting to is not a Project Manager database."
Status: Reviewed
Version(s): 4.0

Fact: Single instance  oracle database
Problem: When connecting to a single-instance oracle database the following error is received:
 ”Error: Invalid Database. The database you are connecting to is not a Project Manager database.”

Image may be NSFW.
Clik here to view.
 


or:


“Error: Invalid Database. The database you are connecting to is not a Methodology Manager database’ when connecting to a database via Methodology Manager.”



Image may be NSFW.
Clik here to view.


 The database can be connected to successfully when configuring the database connection.

Cause: This message will be returned if connecting to a Methodology Manager database via the Project Manager client or vice versa. See: prim1552 - Error: Invalid Database. The database you are connecting to is not a Project Manager database.

However, on a single-instance oracle installation the issue is likely to be caused by the ‘Private database logins’ being incorrectly configured.


For security purposes there are three database level usernames and passwords that are used for various purposes within the application. These are:



  • Admuser – This is used to create the tables/table spaces etc. and administer the database instance. Only to be used by an experienced DBA.

  • pubuser  – This is used by the ‘end user’ to ‘connect’ to the database.

  • privuser  – This is used by the application to connect to the tables within the database to read and write data.

When a client logs into the Project Manager application, the application connects to the database using ‘pubuser’ and reads the ‘private’ database user details.
The application then logs in (at the database level) using the private username and password, ‘privuser’ which is associated with the ‘pubuser’ username.
By default, in a single instance configuration, ‘privuser’ is associated with the ‘PMDB’ – Project Manager’ database.  Therefore, by logging into the database as ‘privuser’ the application connects to the PMDB schema.


When a client logs into the Methodology Manager application, the application connects to the database using ‘pubuser1‘ and reads the ‘private’ database user details.
The application then logs in (at the database level) using the private username and password, ‘privuser1‘ which is associated with the ‘pubuser1‘ username.
By default, in a single instance configuration, ‘privuser1‘ is associated with the ‘MMDB’ – Methodology Manager’ database.  Therefore, by logging into the database as ‘privuser1‘ the application connects to the MMDB schema.


The issue above can occur when the database names get ‘confused’.


E.g. If the ‘pubuser1‘ login becomes associated with the ‘privuser’ database login then an error will occur.


Please follow the instructions below to resolve the issue.

Fix: For Project Manager:

  1. Launch the ‘DBConfig for Project Manager’.

  2. Hit the Next button at the ‘welcome’ screen.

  3. Select the ‘Administration’ radio-button, and hit ‘Next’.

  4. Select the ‘Administer Private database logins’ radio button and hit next.

  5. Ensure the correct alias is selected and hit the ”Next’ button on the ‘select or create alias’ screen.
    Note: if the incorrect alias is selected, please:
     


    1. Close the DBConfig wizard.

    2. Launch Project Manager and select the correct alias.

    3. Close the Project Manager and re-launch the DBConfig wizard.
       

  6. On the ‘Login as Administrative user’ screen select to login as ‘privuser’ with the associated password.

  7. Hit ‘Next’ on the ‘Administer private database users’ information page.

  8. Ensure that:


  • The ‘Public group id’ = 1

  • The ‘DB username’ is ‘privuser’

  • The ‘Password’ is the appropriate password for ‘Privuser’

    Image may be NSFW.
    Clik here to view.

     

  • ‘Hit ‘Next’ once the details are correct.

  • Hit ‘Finish’ to close the Database configuration Wizard.
     

  • Login to Project Manager to test the connection.

  • From Methodology Manager:



    1. Launch the ‘DBConfig for Methodology Manager’.

    2. Hit the Next button at the ‘welcome’ screen.

    3. Select the ‘Administration’ radio-button, and hit ‘Next’.

    4. Select the ‘Administer Private database logins’ radio button and hit next.

    5. Ensure the correct alias is selected and hit the ”Next’ button on the ‘select or create alias’ screen.
      Note: if the incorrect alias is selected, please:
       


      1. Close the DBConfig wizard.

      2. Launch Methodology Manager and select the correct alias.

      3. Close Methodology Manager and re-launch the ‘DBConfig for Methodology Manager’ wizard.
         

    6. On the ‘Login as Administrative user’ screen select to login as ‘privuser1′ with the associated password:
      Image may be NSFW.
      Clik here to view.

       

    7. Hit ‘Next’ on the ‘Administer private database users’ information page.

    8. Ensure that:


    • The ‘Public group id’ = 1

    • The ‘DB username’ is ‘privuser1

    • The ‘Password’ is the appropriate password for ‘Privuser1

      Image may be NSFW.
      Clik here to view.

       

  • ‘Hit ‘Next’ once the details are correct.

  • Hit ‘Finish’ to close the Database configuration Wizard.
     

  • Login to Methodology Manager to test the connection.

  • Viewing all articles
    Browse latest Browse all 92

    Trending Articles