| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3901.1 | start with simple example | TOOK::SHMUYLOVICH | | Thu Oct 15 1992 10:38 | 45 |
|
Gary,
It works in opposite order:
- Firstly you have to export data to the RDB using Exporter;
- Secondly you can access exported data.
Your problem is that the export command returns an exception telling
that it can not export data. I think that even RDB file are not created
( you can check this by "dir mcc_export:routers.rdb").
The simplest case when you can receive this exception is when MCC
process does not have required privileges (you can find them in the
release notes for Exporter).
If this is not your case I would recommend to simplify an export
command, for example in the command:
> MCC> export node4 .rh.rh2dms export target=mcc_export:routers.rdb, begin
> time "whatever", end time "whatever", in domain=mcc.alderley_park
in the "export target" argument your customer uses a logical mcc_export.
Does this logical points to correct directory specification?
Is this logical defined as a system wide logical?
In the Historical Services Use manual you can find a description how
we recommend to use logicals in the export command.
Does your customer have experience with Exporter? I think not because
he/she uses "in domain" qualifier in the export command. May be there is
a reason at least in the beginning to avoid logicals in "export target"
argument.
You can ask him/her to specify some thing simple like:
export node .rh.rh2dms export target=routers.rdb, export period = 00:05:00
This command should create an RDB files in the current directory.
If every thing is OK try to use logicals. If not it will be easier for us
to understand your customer problem.
Good luck,
Sam
|
| 3901.2 | Thankyou !! | PLUNDR::LOWEG | Don't believe a word | Fri Oct 16 1992 11:27 | 6 |
|
Thankyou for your reply I am trying it..
I will let you know how I get on..
Gary Lowe.. NUK CSC comms
|
| 3901.3 | Still a problem.. | PLUNDR::LOWEG | Don't believe a word | Mon Oct 19 1992 13:41 | 31 |
|
Tried your recomendations but still failed to get it to work..
all privileges set then went into datatrieve..
dtr> show mcc_export
Unable to show _CDD$TOP.DECMCC.MCC_EXPORT relational database,
%RDB-E-BAD_DB_FORMAT, UD1:[MCC.EXPORTED_DATA]ROUTERS.RDB does not
reference a database known to rdb
-RMS-E-FNF, file not found
dtr> exit
$ man/ent
DECmcc (V1.2.0)
MCC> export node4 .rh.rh2dms export target=router.rdb, export period
00:05:00
Node4 LOCAL_NS:.rh.rh2dms
AT 19-OCT-1992 14:07:22
Repositories do not exist
MCC> exit
Any other thoughts or have we missed something out ??
Gary Lowe NUK CSC comms..
|
| 3901.4 | AAAAAAAAAAAAAAAAggggggggggggghhhhhhhhhh | PLUNDR::LOWEG | Don't believe a word | Tue Oct 20 1992 12:04 | 9 |
|
Am I right in believing that the .RDB file is the repositery that
doesn't exist. If so then this should be able to be easily fixed if
someone can tell me how to create a .RDB file..
Here's hoping....
Gary Lowe NUK CSC..
|
| 3901.5 | Thanks Sam you put me on the right tracks.. | PLUNDR::LOWEG | Don't believe a word | Tue Oct 20 1992 14:28 | 15 |
|
I have sussed it out.. It was a problem with protection on the batch
que running the exporter background task. I changed from the
recommended values to s:rwed o:rwed g:rwed w:rwed and it worked.
I think it is significant to get the /owner qualifier correct but I
decided to open it up to everybody and work it out later.
However imagine my distress when I told the customer I had cracked it
and then he told me that he was exporting historical data which
apparently doesn't use a background process..
Something I don't know so I am going back to the drawing board..
Gary Lowe.. NUK CSC..
|