Technical Monitoring - DBA Connection red (failure)

[Private_Member_19084]

Hi experts,

I have the following problem.

In technical monitoring I have one managed system, on which the DB availability check is not working.

The DB is a Sybase ASE 15.7

In solman_setup->system config the DB connection is configured well (green status).

Also if I open the dbacockpit of solution manager, I can see the DB of the managed system and the connection checks are working fine.

But in technical monitoring, I get the alert that the DB is not available and also that "DBA Cokcpit Connection Status" = failure.

If I go to the details of the alert, I also can't see the problem.

I did already remove and add the system more often. Further I also did remove the connection in dbacockcpit and created it again.

But now I don't have any further ideas.

Hopefuly somebody can help me.

Thank you

[divyanshu_srivastava3 · Accepted solution]

Hi Christian,

1st let us find the error related to this.

Follow below KBA to find out the error that is causing the issue.

2016715 - Metric Troubleshoot using MAI Tools

Since, you are motioning a remote ASE database, make sure the below KBA is read and applied.

1532253 - SYB: Remote DB Monitoring for SAP Sybase ASE

Regards,

[Private_Member_19084 · Accepted solution]

I've already checked the second note.

I also checked MAI_TOOLS, but can't find any problem there.

I find some entries but not for this system and problem.

Kind regards

[divyanshu_srivastava3 · Accepted solution]

May be you should check the template assigned to it.

There are two DB template for ASE - one is ASE other is for 15.7(obsolete)

Run the managed system config again for this, esp the BI part and copy and assign the other template and see if this works.

Also, check extractor framework for any issues.

[roland_hennessy · Accepted solution]

Hi,

I know you are saying the DB Cockpit is ok but can you check the SAP note

1605680 -SYB: Troubleshoot the setup of the DBA Cockpit on Sybase ASE to see if all okay?

Thanks,

Roland

[Private_Member_19084 · Accepted solution]

Thx for the note.

What is confusing me, is that the connection name is alwasy <SID>00001 instead of just <SID>.

Maybe this is the problem?

But I have no idea, where this name is coming from, when I configure again with SOLMAN_SETUP.

Because in SLD and LMDB the name is always just <SID>.

Any idea?

[divyanshu_srivastava3 · Accepted solution]

Hi Christian,

In such cases which you have duplicate extended ID, you should do a complete cleanup. Always better to remove bith SID's for once from lmdb to smsy, and re sync it.

Regards

[Private_Member_19084 · Accepted solution]

Hello Divyanshu,

I already did this

[divyanshu_srivastava3 · Accepted solution]

Duplicate SIDs comes when you have multiple source or you have created one of the entry manually.

To find this, use search option in smsy to do a cleanup.

Stop the SLD data supplier until all the cleaning is done. Once sid and extended ids are removed, repeat msc and tech mon setup.

[Private_Member_19084 · Accepted solution]

hmmm found it, in SMSY there is a attribute called "Remote Database Connection", which is having the value "<SID>00001".

But how can I change this?
Because in LMDB I can't find this attribute.

KR

[Private_Member_19084 · Accepted solution]

The value I can find in lmdb->db->details, in the description there is a value "dbc_name".

But no change possibility there.

[Private_Member_19084 · Accepted solution]

ehmmmm.....now the dba cockpit is ok, but DBA is still offline displayed.

I will open a ticket now.

kind regards

[Private_Member_19084]

Hello Together,

so the problem seems to be solvednow.

I've done everything again.

Updated CIM again, also applied all systems again and also connected the DAA again.

Now the check seems to be ok.

No idea what was wrong.

Thank you to everybody for help.

[Former Member]

Hi Christian, did you check the file dev_sapdbctrl in the folder /usr/sap/hostctrl/work?

Best Regards,

Josue Neto

[Private_Member_19084]

Nothing special in that log on solman side.

[roland_hennessy]

Hi

Can you check if the notes 1783711 and 1788320 help here?

Kind regards,

Roland

[roland_hennessy]

Hi Christian,

Can you attach screenshot of the issue as this will help here? What is you SP level? Please also make sure Content is updated.

Kind regards,

Roland

[Private_Member_19084]

Hi Roland,

thank you for your help

SP 8 I will update the content, but should be ok because other managed systems are working with same structure.

Kind regarsd

[Private_Member_19084]

So, now it is also red on the left side in dbacockpit of Solman.

But I can't find any error.

Error log is everything green. Also all connections are working....

[roland_hennessy]

HI Christian,

Can you access the context menu by clicking on the small triangle
next to the red metrics. Then select "Metric Troubleshooting" or "check data collection" whichever shows up.

You'll see a list of checks performed on the metric which
should tell us where things went wrong. Please can you attach this?

Thanks,

Roland

[Private_Member_19084]

Hello Roland,

no I can not, because the check seems to be successfully.

The monitor thinks, that the DB is really not available.

Therefore I just get the items like "metric configuration, metric documentation and copy value" in the context menu.

If I go to documentation, I just get the info that I should check dbacockpit.

Kind regards

[Former Member]

Hi Christian,

Can you check DBA extractors in "Extractors administration".Keep filter on your managedsystem and on DBA ,find out which extrators failing ,if will get the log of extractor once you click on failed extractors.

Post us log of failed extractors.

Thanks,

Prakash

[Private_Member_19084]

What do you mean exactly?

Is it in dbacockpit? because there I can only find the "collector configuration", which is ok.

In Workcenter Extractor Framework also the DBMS extractors are green.