| 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 |
I am trying to export some data from some SNMP entities to RDB.
I export some private MIB variables of FDDI concentrators and bridges:
counters for entries in those table:
SNMP * dec ema decMIBextension elanext ebridge ebrInterfaces ebrIfTable
SNMP * dec ema decMIBextension elanext ebridge ebrInterfaces ebrIffddiTable
SNMP * dec ema decMIBextension elanext ebridge ebrInterfaces ebrIfethTable
The export works, but I only get one table created:
SQL> show tables
User tables in schema with filename
MCCENDESA_DISK:[MCCENDESA.MCCEXPORT]MCC_EXPORT.RDB
MCC_BRIDGE
MCC_BRIDGE_LINE
MCC_BRIDGE_LINE_REP01
MCC_NODE4
MCC_NODE4_CIRCUIT
MCC_NODE4_LINE
MCC_SNMP
MCC_SNMP_FDDI_FDDIM_FDDIM_FDDIM
MCC_SNM_DEC_EMA_DEC_EL_EB_EB_EB <<<<
MCC_TRANSLAN
MCC_TRANSLAN_LINE
This table corresponds to the first "export". I have been looking at
the log files of the export batch processess, and everything seems to
be OK ("Exporting completed" for all of them)
A shot in the dark: Since the 31 name for the table is automatically
generated from the entity name, and in the three cases it is quite
similar, could this be a bug ?
We are stuck in a customer project because of that, so any help would
be greatly appreciated
Regards
Luis
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 6148.1 | Call it a feature... | BIKINI::KRAUSE | CSC Network Management/Hubs | Wed Nov 09 1994 04:37 | 16 |
> SNMP * dec ema decMIBextension elanext ebridge ebrInterfaces ebrIfTable > SNMP * dec ema decMIBextension elanext ebridge ebrInterfaces ebrIffddiTable > SNMP * dec ema decMIBextension elanext ebridge ebrInterfaces ebrIfethTable > MCC_SNM_DEC_EMA_DEC_EL_EB_EB_EB <<<< > > A shot in the dark: Since the 31 name for the table is automatically > generated from the entity name, and in the three cases it is quite > similar, could this be a bug ? Well, I'd call it a feature ;-) There is not much that could be done about it aside from changing the 'name translator' routine to a more intelligent algorithm - which might break on other name constructs. You should escalate the problem so that engineering is aware of it. *Robert | |||||
| 6148.2 | A workaround | GOYA::GONZALEZ | Thu Mar 02 1995 21:08 | 7 | |
Well, a little too late for a reply, but thanks a lot anyway
BTW, as a workaround what I did was to export each partition to a
different RDB, and in this case the export is OK. Obviously this
complicates a bit the reports, but not too much
Luis
| |||||