| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
When developing an application using data exported from DECmcc/ULTRIX
we have come across a few problems:
1. 48-bit counters are not exported when their values exceed the maximum
value ULTRIX/SQL integers can have (they are 32-bit signed integers). We
also suspect this applies to 64-bit counters as well. A more useful (for us
atleast) approach would be to export the lower 32 bits. This seems to be,
an undocumented restriction in the Exporter FM.
2. The background exporter process cease to put data in the database without
any visible error messages. Trying SHOW EXPORT reveals that Exporting state
is ACTIVE, Last export time is way further back in history than the Export
period would suggest and Last export failure reason is "N/A". HOW do we
troubleshoot this?(!)
5000-240 with Ultrix 4.3, ULTRIX/SQL 2.0 and MCC BMS 1.3.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5014.1 | TOOK::SHMUYLOVICH | Thu May 06 1993 10:33 | 13 | ||
1. You are right. The Exporter tries its best to map MCC data type into
data base supported data types. In the cases when it is impossible it
drops the value .
2. We saw this behavior when Exporter does MCC_call to obtain data and
this call is never come back. To verify if this is a case you can
do a Show all partitions (including statistics) for the exported entity.
SAm
| |||||