Skip to Content
avatar image
Former Member

Managed Systems setup for non-SAP DB on solman7.1sp6


We have a few Non-SAP oracle DBs that we want to monitor via solman.

We have a solman 7.1 sp6 system.  I have setup the DBs to show up in LMDB via hostagent/Diagagent, setups, etc.

I can see the DBs in the "Managed System Configuration" for the Database(s) TAB.  The LMDB info looks perfect.

So I go to "configure database", within managed system setup..

step #1, the diagnostics agent is correctly assigned,

step #2 named "enter system parameters", I have added the DB host, service name, port number, TNS name,  and user name / pass.

But when I try to go "SAVE" or go to the next step, it checks those setting I entered, but I get the following error message:

Database connection (MYSID): User XXXXX does not have administrative or monitoring privileges.Connection already exists but without administrative or monitoring authority.Provide new user name and password with administrative or monitoring authority.

I mean, what is it looking for here?  this user definitely has what I think are privleges way beyond what any DB user would need.

But what does it need really?  what other logs can I look at to figure this out?  I have13 other DBs setup just like this, and they all get this error.

And, if I do need to open a message, what component would I use?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Jun 28, 2013 at 03:15 PM


    When setting up Non-SAP Oracle Databases, try running the following steps.

    1.)  Create user and user tablespace on the target database, ex SAPSR3 user, PSAPSR3 tablespace

    2.)  Download and run sapdba_role.sql user (where user is the user account created in prior step)

    3.)  From an Oracle sysdba session run, grant sapdba to user; (where user is the user account created in prior step)

    4.)  Add the Non-SAP Oracle target database to SolMan's tnsnames file

    5.)  Proceed with Managed System Configuration

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 20, 2013 at 07:52 PM

    Does User XXXXX have the correct security/rights setup on the DB server to log in?

    For my landscape the MS SQL admin had to allow login access from SolMan to the various DB instances; if your DBA reviews the logs in Oracle to verify what SolMan is attempting to access with the user account you are specifying.

    Review the following as this SCN member also had similar issues with DB cockpit connections; turned out to be a service pack issue on the application side, but some of the things I mentioned may help fix your issue.

    Message was edited by: Billy Warring - added the URL.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member


      thanks for the reply.  I looked at what you wrote as well and the other thread you referenced.  At this point, our oracle logs aren't giving us much info.  we're going to try to bump us the trace tomorrow on the oracle end to see if we can make any progress.


  • avatar image
    Former Member
    Jul 14, 2014 at 08:58 PM
    Add comment
    10|10000 characters needed characters exceeded