DBACOCKPIT for SQL DB

[Former Member]

Hi !

We're running the Managed System Config for a Java NW 7.4 SP 7 system on Solman 7.1 SP12.

In the DB extractor step, I see the below error as a result of which DBACOCKPIT Monitoring also stops working.

(The Monitoring from DBACOCKPIT works when we enter the parameters in Step 4 & select create DB connection...but after a few minutes, due to this extractor issue it probably stops)...

Both Solman & the satellite system have their DB'S under one named SQL 2012 instance.

I've tried to run the scripts manually from DBACOCKPIT, but it gives me the below error:

The DBACOCKPIT connection still works...its only the Monitoring part that's affected.....

Please help advise....

Thanks a lot !

saba.

[former_member204529]

Hi Saba

Please check the following note to see if there is a missing step

1388700 - SolMan 7.0 EHP1 Database Warehouse for MSSQL

Regards

Gülsen

[Former Member]

Hi Everyone,

Thanks a ton for all your help !!!

There's this beautiful Note:1941524 which when implemented on Solman worked like magic

Thanks !

saba.

[former_member204529]

Hello Saba

Please check this note

1860361 - The Database extractors are missing for a Managed System - Solution Manager 7.10

Regards

Gülsen

[Former Member]

Hi Guys,

Thanks a lot for the help

I'm a little finicky about implementing Note 1963503, since DBACOCKPIT monitoring for other connected systems works well from Solman.

The only difference is this is a Java stack.

I've entered the below details in MSC:

Where Monitor login name is: SID_SAPMonitor.......

Am I doing something wrong ?

Thanks !

saba.

[Former Member]

Hi Saba,

I would suggest you go ahead and implement the note. This note has correction for only one report/include . Which is only concerned with MSS objects or Sql server.

It should not cause problem with any of the already configured databases in dbacockpit.

Thanks

Amit

[divyanshu_srivastava3]

Hi Saba,

I don't really see corrections relevant on this note.

Also, for applying this, you have to take into account other dependencies too.

Perhaps, you should check with SAP support on this.

Either we have done anything wrong or there is a correction for this, check with SAP.

And yes, you MSC info holds good.

Regards,

[Former Member]

Hi,

Which note you are saying has no relevant corrections , this  1963503??

Thanks

Amit

[divyanshu_srivastava3]

Hi Amit,

Thanks for asking me, I picked a wrong note while searching and gave my reply.

The corrections delivered through the above notes looks good.

Might be, applying this on solution manager may work.

The reasons stated in note are viable.

The problem which she is getting and modification made to form in this include look on same stage. Infact, the object invalided is very specific.

However, It seems to me as if error is just suppressed, without any justification.

Applying has no harm, but getting this from SAP is much better is such cases.

Regards,

[Former Member]

Hi Saba,

Try the information in this KBA  and the steps mentioned it in sequence.

1803619 - Database Extractor Setup fails with: Wrong number of input parameters [sap_set_para:GET_IN...

This should help you I think .

Thanks

Amit

[Former Member]

Hi Amit,

As per this Note, I tried to rerun the scripts from the cockpit directly, but ran into screenshot 2 error

Thanks a lot, anyway

-s.

[Former Member]

Hi Saba,

What about this note. Did you try this one.

1963503 - Objects erroneously dropped and created in the 'dbo' schema due to an error

Thanks

Amit