MaxDB: Corrupted DBCON entry for local system
[ADA] [boxfile corrupted] [corrupted] [DBCON] [dll corrupted] [file corrupted] [Local] [MAXDB] [SDB] [System]
- Custom Control, Event: string param. corrupted at backendSymptom A custom control fires an event. SAP GUI send this event to the backend. In some cases it can happen, that the string parameter of the sent event received at the...
Symptom
The DBCON entry for the local system is corrupted and therefore, the database monitoring is disabled.
Other terms
MAXDB SDB ADA CORRUPTED DBCON LOCAL SYSTEM
Reason and Prerequisites
A program updates the DBCON table and produces an invalid entry for the local connection.
This problem can only occurr if the local system has a MaxDB database and the DBA Cockpit is used to monitor another database platform than MaxDB.
Solution
Apply the attached correction instruction and repair the DBCON entry for the local system by implementing the following instructions:
1. Open the DBA Cockpit by calling transaction DBACOCKPIT.2. Switch to another database other than MaxDB.3. Choose the database connection maintenance screen in the DBA Cockpit.4. Restart DBA Cockpit.
The DBCON entry is now repaired by the DBA Cockpit and the local monitoring should be available.
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}