| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1182.1 | check database file specification | QUANTZ::SHMUYLOVICH | | Mon Jun 24 1991 13:33 | 17 |
|
It looks like you have problem with database file specification
( Final status code: 0222994C - SQL_F_ERRCRESCH: error creating schema
filename). What do you use as database name? Please, check if you have
required privileges into specified directory.
> The only thing i noticed was
>that depending on if the export target database file existed or not I got
>different termination status.
How you deleted en existing database? Did you delete <database_name>.SNP
file? IF not it can give you this problem (Final status code: 0138801A -
RDB_E_BAD_FORMAT:reference to unknown database).
Sam
|
| 1182.2 | OK, But wat about RWMBX | ANTIK::WESTERBERG | Stefan Westerberg CS Stockholm | Mon Jun 24 1991 19:57 | 25 |
| >How you deleted en existing database? Did you delete <database_name>.SNP
>file? IF not it can give you this problem (Final status code: 0138801A -
>RDB_E_BAD_FORMAT:reference to unknown database).
Yes ,that was the problem. When I deleted MCC_EXPORT.SNP the background job
started without any problem.
Ok but now the problem that led me into this mess.......
I have had the recording running for a while now, and the data that I have
recorded I now want to export to a RDB database. But ..... after that I have
typed in a mcc export command the process just hungs in RWMBX.
I don't have any problem using the show commands to look at the data I have
collected.
I have tried this on diffrent enitys (bridge,node4 and Translan) all with the
same resulte.
I have seend this behaviour on four different installations, and two of those
at customer site.
My question is now... I'am doing some thing wrong or what ?????
/Stefan
|
| 1182.3 | What about future time Export | TOOK::SHMUYLOVICH | | Tue Jun 25 1991 10:20 | 19 |
|
As I understood you are trying to export past time data. Did you
try regular (future time) export? If not I would recommend do it to be
sure that RDB_writer works.
More questions:
1. Are tables created in the RDB?
2. Are there at least one row from past time export?
3. What do you use as "export target" argument in the export
command and what is your argument to the background process.
4. How Record and Export commands look like?
Sam
|
| 1182.4 | ok back online..... | ANTIK::WESTERBERG | Stefan Westerberg CS Stockholm | Thu Jun 27 1991 13:01 | 47 |
|
> As I understood you are trying to export past time data. Did you
>try regular (future time) export? If not I would recommend do it to be
>sure that RDB_writer works.
Yes i have tried future export and that works just fine.
> More questions:
> 1. Are tables created in the RDB?
> 2. Are there at least one row from past time export?
I used RDO and DECdecision and couldn't find any trace of input to the
database.
> 3. What do you use as "export target" argument in the export
> command and what is your argument to the background process.
I used the default: SYS$LOGIN:MCC_EXPORT.RDB
4. How Record and Export commands look like?
Record command was done from DECwindows and there I specified the following
fields:
Partition: Counters
polling period: 0:15:0
keep age: 45 0:0:0
Export command looked loke this:
At 17:00
MCC> export node4 stkrt1 cir syn-0 export period 1:0:0,-
_MCC> begin time 01:00,end time 16:00,-
_MCC> sequence name node4_stkrt1_circuit_syn_0,in domain history
and after carrige return the processes hungs forever.......
with his subprocess in RWMBX mode.
I have tried other export commands with the same result.
If I use show commands to look at the recorded data every thing works fine.
Any ideas ?
/Stefan
|
| 1182.5 | Same observation | LEMAN::BIRO | Georges Biro - SR/ACT | Fri Jun 28 1991 01:32 | 4 |
| I am experiencing the same RWMBX symptoma when trying to export past
data. Future data works.
Georges.
|
| 1182.6 | try Export Target = RDB_FILE_NAME | TOOK::SHMUYLOVICH | | Fri Jun 28 1991 14:01 | 3 |
| Try to use "export target" argument in the past time export directive
and enter filename specification in UPPER case. Please note that this
argument must be the same as for background process.
|
| 1182.7 | More trouble following that command.... | ANTIK::WESTERBERG | Stefan Westerberg CS Stockholm | Fri Jun 28 1991 18:57 | 60 |
| > Try to use "export target" argument in the past time export directive
> and enter filename specification in UPPER case. Please note that this
> argument must be the same as for background process.
At 23:00 I tried the folloing command:
MCC> EXPORT NODE4 STKRT1 CIR SYN-0 EXPORT PERIOD 1:0:0,-
_MCC> BEGIN TIME 01:00,END TIME 18:00,-
_MCC> SEQUENCE NAME NODE4_STKRT1_CIRCUIT_SYN_0,-
_MCC> EXPORT TARGET SYS$LOGIN:MCC_EXPORT.RDB, IN DOMAIN HISTORY
.....and that really got me into problem.
First as usal the I got the RWMBX and then the mcc_exporter_background job
terminated with the folloing log file:
$! SYLOGIN.COM
$ SET NOVERIFY
%MCC-F-NOATTREXIST, specified attribute record does not exist
%MCC-E-NOATTREXIST, specified attribute record does not exist
WESTERBERG job terminated at 28-JUN-1991 22:46:47.64
Accounting information:
Buffered I/O count: 178 Peak working set size: 2456
Direct I/O count: 111 Peak page file size: 8850
Page faults: 1706 Mounted volumes: 0
Charged CPU time: 0 00:00:03.57 Elapsed time: 0 00:01:15.39
.... and after stoping the RWMBX process I went into MCC and checked what it
had to say about "show export node4 stkrt1 circuit *"
Node4 stkrt1 Circuit *
AT 28-JUN-1991 23:09:41
The requested operation cannot be completed
Entity Existence Info = Entity Existence Cannot Be Determined,
MCC Routine Error = %MCC, specified attribute record
does not exist
When I tried the same command before I did the export command I got a respons
like this:
Node4 stkrt1 Circuit *
AT 28-JUN-1991 23:32:47
No exporting for the specified entity
But still both show node4 stkrt1 circuit syn-0 and show record node4 circuit
syn-0 partition *, in domain history works.
Then when I tried to start the background job again (after deleting all old
database file from the previus job) it terminates with the same error messages
as above !
Very confused.............. any ideas ????
/Stefan
|
| 1182.8 | can not reproduce past time export problem | TOOK::SHMUYLOVICH | | Wed Jul 03 1991 13:52 | 274 |
| Hi Stefan,
Sorry for the delay with my response.
Firstly I was NOT right telling that "past time" export requires a running
background process. When the user requests "past time" exporting the
foreground exporter creates its own child subprocess which writes in the
RDB. So please do not look at child subprocess created by the background
process (MWAIT - is its normal condition).
Secondly I could not reproduce your problem!
I created a new domain, recorded counters, and exporter them. Everything
looks good.
Could you please do one more experiment:
- create a new domain;
- start Historian background process for this domain;
- record data ( please do not specify more then 10 polls:
historical data processing in the Exporter takes time and
it will be easier to understand your problem);
- when recording operation is done start past time export for
new RDB file ( do not start Exporter background process).
The following is a log file with my command I did in MCC. I used SQL to
verify data in the RDB file. May be it helps.
Sam
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++RUDONE>man/en
DECmcc (V1.1.0)
MCC> record node4 rudone partition = counters, poll per = 00:02:00, end t=10:50:00, in domain test
Node4 4.773
AT 3-JUL-1991 10:34:48
Recording of "Counters" partition started
MCC> show record node4 rudone partition = counters, in domain test
Node4 rudone
AT 3-JUL-1991 10:52:03
Recording parameters for the partition "Counters" :
Recording state = SUSPENDED,
State since = 3-JUL-1991 10:47:04.69,
Polling period = 0 00:02:00.00,
Begin time = 3-JUL-1991 10:34:48.76,
End time = 3-JUL-1991 10:50:00.74,
Keep age = 45 00:00:00.00,
Request time = 3-JUL-1991 10:34:48.76,
Requested by = "SHMUYLOVICH",
Time of last successful poll = " 3-JUL-1991 10:49:04.47",
Number of successful polls = 8,
Time of last failed poll = "NONE",
Last poll failure reason = "N/A",
Number of failed polls = 0,
Last historical expiration time = " 3-JUL-1991 10:49:04.47",
Time of last expiration failure = "NONE",
Last expiration failure reason = "N/A",
Number of expiration failures = 0
MCC> show node4 rudone all counters,for start 10:35:00 duration 00:15:00,in domain test
Node4 rudone
AT 3-JUL-1991 10:35:05 Counters
Examination of Attributes shows:
Counter Creation Time = 3-JUL-1991 09:54:53.13
Seconds Since Last Zeroed = 2412 Seconds
User Bytes Received = 86289 Bytes
User Bytes Sent = 86274 Bytes
Total Messages Received = 682 Messages
Total Messages Sent = 687 Messages
Connects Received = 5 Connects
Connects Sent = 5 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 11 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
Node4 rudone
AT 3-JUL-1991 10:37:04 Counters
Examination of Attributes shows:
Counter Creation Time = 3-JUL-1991 09:54:53.47
Seconds Since Last Zeroed = 2531 Seconds
User Bytes Received = 86289 Bytes
User Bytes Sent = 86274 Bytes
Total Messages Received = 682 Messages
Total Messages Sent = 687 Messages
Connects Received = 5 Connects
Connects Sent = 5 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 11 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
Node4 rudone
AT 3-JUL-1991 10:39:04 Counters
Examination of Attributes shows:
Counter Creation Time = 3-JUL-1991 09:54:53.48
Seconds Since Last Zeroed = 2651 Seconds
User Bytes Received = 86289 Bytes
User Bytes Sent = 86274 Bytes
Total Messages Received = 682 Messages
Total Messages Sent = 687 Messages
Connects Received = 5 Connects
Connects Sent = 5 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 11 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
Node4 rudone
AT 3-JUL-1991 10:41:04 Counters
Examination of Attributes shows:
Counter Creation Time = 3-JUL-1991 09:54:53.50
Seconds Since Last Zeroed = 2771 Seconds
User Bytes Received = 86289 Bytes
User Bytes Sent = 86274 Bytes
Total Messages Received = 682 Messages
Total Messages Sent = 687 Messages
Connects Received = 5 Connects
Connects Sent = 5 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 11 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
Node4 rudone
AT 3-JUL-1991 10:43:04 Counters
Examination of Attributes shows:
Counter Creation Time = 3-JUL-1991 09:54:53.47
Seconds Since Last Zeroed = 2891 Seconds
User Bytes Received = 86289 Bytes
User Bytes Sent = 86274 Bytes
Total Messages Received = 682 Messages
Total Messages Sent = 687 Messages
Connects Received = 5 Connects
Connects Sent = 5 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 11 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
Node4 rudone
AT 3-JUL-1991 10:45:04 Counters
Examination of Attributes shows:
Counter Creation Time = 3-JUL-1991 09:54:53.47
Seconds Since Last Zeroed = 3011 Seconds
User Bytes Received = 86289 Bytes
User Bytes Sent = 86274 Bytes
Total Messages Received = 682 Messages
Total Messages Sent = 687 Messages
Connects Received = 5 Connects
Connects Sent = 5 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 11 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
Node4 rudone
AT 3-JUL-1991 10:47:04 Counters
Examination of Attributes shows:
Counter Creation Time = 3-JUL-1991 09:54:53.47
Seconds Since Last Zeroed = 3131 Seconds
User Bytes Received = 86289 Bytes
User Bytes Sent = 86274 Bytes
Total Messages Received = 682 Messages
Total Messages Sent = 687 Messages
Connects Received = 5 Connects
Connects Sent = 5 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 11 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
Node4 rudone
AT 3-JUL-1991 10:49:04 Counters
Examination of Attributes shows:
Counter Creation Time = 3-JUL-1991 09:54:53.47
Seconds Since Last Zeroed = 3251 Seconds
User Bytes Received = 86289 Bytes
User Bytes Sent = 86274 Bytes
Total Messages Received = 682 Messages
Total Messages Sent = 687 Messages
Connects Received = 5 Connects
Connects Sent = 5 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 11 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
MCC> export node4 rudone exp tar=past_time_test.rdb,begin t=10:35:00, end t=10:50:00,exp per=00:02:00,in domain test
Node4 4.773
AT 3-JUL-1991 11:00:44
Exporting started <----- WRONG MESSAGE IT HAS TO BE "Exporting complited" /Sam
MCC> exit
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SQL> declare schema filename PAST_TIME_TEST.RDB;
SQL> select node4,time_counters, User_Bytes_Sent from mcc_node4;
NODE4 TIME_COUNTERS USER_BYTES_SENT
4.773 3-JUL-1991 10:35:05:24 86274
4.773 3-JUL-1991 10:37:04.47 86274
4.773 3-JUL-1991 10:39:04.48 86274
4.773 3-JUL-1991 10:41:04.50 86274
4.773 3-JUL-1991 10:43:04.47 86274
4.773 3-JUL-1991 10:45:04.47 86274
4.773 3-JUL-1991 10:47:04.47 86274
4.773 3-JUL-1991 10:49:04.47 86274
8 rows selected
SQL>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
|
| 1182.9 | No change...... | ANTIK::WESTERBERG | Stefan Westerberg CS Stockholm | Thu Jul 04 1991 09:10 | 10 |
| Ok I done what you suggested but,no change.....
The process from where I do the export command hungs in RWMBX and the
subprocess created run for a will but very soon hungs in HIB state.
Every command except the export command works ok.
No RDB database is created and no error message i received.
The exporter backround wasn't running when I did the past time export command.
/Stefan
|
| 1182.10 | More Details ... | MAYDAY::ANDRADE | The sentinel (.)(.) | Thu Jul 04 1991 12:25 | 44 |
| I too have this problem. As I reported before...
This serious bug, is either going to force me to both record and export
the same data at the same time, or to give up recording data altogether.
Acting on the idea that something must have gotten mixed up along the
line. I re-did everything from the beginning, I deleted the .RDB &.SNP
files, I resubmited the exporter background process. And tried again.
First: To export future data, it worked fine.
Then: To export past data, and once again both the process and the
subprocess hanged. In addition the background process, died with a
"Thread termination requested" error message.
Here the exact command used:
" export node4 sunny1 cir syn-1 begin time = 4-jun - "
" ,end time = 11-jun-1991-17:00, in domain area-51 "
** I wonder if the fact that this is a sub-entity and not a global
entity had anything to do with these failures. I guess I could delete
everything and try that.
After resubmiting the background process, tried to export future data
again for the same entity (node4 name cir syn-1) and this time the
command failed with "% Entity Existence cannot be determined". Only for
this circuit, it accepted future export commands for all other entities.
BUT none of these export commands did anything. Because the background
process, never did start processing again. I submit it, and a minute
later it dies with the following error:
"%MCC-F-NOATTREXIST, specified attribute record does not exist"
Just doing a "show export" for this entity I get this:
" MCC Routine Error = %MCC-E-INV_HANDLE_STAT, "
" software error: invalid handle state, "
" Entity Existence Info = Entity Existence Cannot Be Determined "
Gil
|
| 1182.11 | SAME PROBLEM | ZUR01::SCHNEIDERR | | Tue Jul 09 1991 08:30 | 11 |
| Hello,
We have the same problem: after a "set display" and trying to export historical
data the process hangs and the windows dispear.
I read the notes and I was lucky to find the note 1182. But at the end there is
no solution or supposition.
Does somebody some investigation about this problem or have we to live with it?
Regards Roland
|
| 1182.12 | SAME PROBLEM | DRAC::ASUNCION | | Wed Jul 10 1991 05:36 | 11 |
|
Hello,
I have exactly the same problem. I get the same messages, and the
same results (process in RWMBX, specified atributte does not exist...)
I would like to know if the only solution at the moment is to export
data and not to use the historian.
Asun Ariza
|
| 1182.13 | Any News ... | MAYDAY::ANDRADE | The sentinel (.)(.) | Tue Jul 23 1991 05:21 | 1 |
|
|
| 1182.14 | please, do NOT use past export until investigation is completed | TOOK::SHMUYLOVICH | | Thu Jul 25 1991 18:31 | 1 |
|
|
| 1182.15 | Any update? | GRANMA::JPARKER | | Wed Aug 07 1991 19:50 | 16 |
|
Just for the record...
I've experienced the same trouble: export past 'recorded' data.
Circuit counter partition. Real time export is Ok. Process goes PFW,
then RWMBX. Record directive (IMPM) works Ok, according to show
recording. No old .rdb/.snp files left around. No Exporter background
batch job running. No .rdb/.snp files created. etc, etc.
As of reading this note today, I'm avoiding the record+export
processing until further notice. This is of interest to my customer
for 're-playing' weekend activity, etc.
Any update?
Regards,
Jeff.
|
| 1182.16 | One More | NETCUR::WADE | Bill Wade T&N Course Development | Mon Aug 12 1991 11:29 | 3 |
| Add one more to the export past data RWMBX problem. Really stange
because I'm sure that this has worked for me before.
|
| 1182.17 | Another RWMBX - any progress? | BAHTAT::BOND | | Thu Oct 31 1991 04:49 | 33 |
| Yes - we too are having some problems with the exporter background
process sticking in RWMBX state - but the subprocess then seems to be
doing nothing at all. Suspend or delete exporting commands eventually
give "request queue full - check background process" and you have to
kill it off in the end. Has any progress been made with this whole
RWMBX issue? I know Sam in a previous note implied this was 'normal'
but it seems to me that when the exporter is working normally, it
HIBernates; when it gets stuck in this RWMBX state and never comes out
it is dead! Perhaps somebody could explain how it should all work?
At our customer site, we were trying to export NODE, LINE and CIRCUIT
counters from 54 DECrouter nodes with 2 to 4 lines on each. This gave
398 exporting jobs to 1 database. We found that the background process
would never properly start; it would compute for 10 minutes or so
gradually increasing its virtual address space and working set to some
45000 and 16000 pages (WSEXTENT) respectively and then finally stick in
RWMBX after about another 10 to 15 minutes. Approaching this time, it
would begin to flit into RWMBX more and more until finally it never
came out.
We then reduced the number of nodes being monitored to a Core set of 22
which only have 2 lines on them giving 110 exporting jobs. With this
reduced load, the background process seems to start ok - it still flits
into RWMBX wait when the working set has got to 16000 pages but it
always gets out again. It still takes about 15 minutes to get to this
state and then happily remains in HIB state except when it is working.
So, it seems to me that the exporter seems to be running out of
something when it is asked to do many more jobs and then gets stuck in
RWMBX. Anybody any idea what it is? I have checked FILLM (500),
BYTLIM (200000) and there is plenty of non-paged pool.
The system is a VS3100 model 76 with 32Mb memory.
|
| 1182.18 | Any progress before a CLD ? | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Sun Mar 15 1992 19:14 | 13 |
| Re .14 -< please ,do NOT use past export until investigation is completed >-
What is the result of the investigation ? I have customer reporting export
process going into RWMBX state . A cursory look in SDA shows that process in
RWMBX runs image MCC_MAIN.EXE. The mailbox in question has outstanding messages.
The process that has channel to the same mailbox runs image
MCC_EXPORTER_FM_WRITER.EXE and does have an outstanding read to the mailbox.
A crash dump is available if anyone is interested.
will CLD this if receive no response .
I should say that MCC is V1.1
Andrew
|
| 1182.19 | Informal reply | TOOK::R_SPENCE | Nets don't fail me now... | Mon Mar 16 1992 17:53 | 9 |
| Exporting of Historical Data doesn't work in V1.1
The problem was too complex to fix with a patch so the correction
was rolled into V1.2
If you are looking for an official response before submitting a CLD
then you are asking in the wrong place. This is not the official
problem reporting mechanisim.
s/rob
|
| 1182.20 | thanks | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Mon Mar 16 1992 19:06 | 7 |
| Thanks for the "unofficial reply"
>Exporting of Historical Data doesn't work in V1.1
>The problem was too complex to fix with a patch so the correction
>was rolled into V1.2
I suspect this was going to be the answer
|