| 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 |
Greetings,
I have the following configuration:
VS3100/M38
DECmcc V1.3.0
VMS V5.5-1
I have just installed all the layered products necessary for the
reports package:
RDB (RTO)
CDD/Repository
Datatrieve
DECgraph
When I try and start an export job I get the following message:
ADOWS1> @sys$manager:mcc_exporter_background.com sys$login:mcc_export.rdb 10
MCC Exporter writer process encountered the following SQL error:
%NONAME-F-NOMSG, Message number 0222BF4C
%MCC-E-ALERT_TERMREQ, thread termination requested
No .RDB file is created, but there is no other indication of a problem.
Can anyone please shed some light on this ?
Much appreciated.
Reece Boucher
Adelaide, Australia
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5463.1 | check SQL | SISE::SAM | Wed Aug 11 1993 10:13 | 16 | |
> MCC Exporter writer process encountered the following SQL error:
>
> %NONAME-F-NOMSG, Message number 0222BF4C
> %MCC-E-ALERT_TERMREQ, thread termination requested
The above message tells that one of the Exporter's processes (writer)
gets an error from SQL and therefore the Exporter Background terminates.
The "Message number 0222BF4C" message come from the SQL. It looks like
SQL is not installed properly. Sorry, I can not say more because SQL
message does not tell much. Did you install RDB/VMS Runtime kit? It's
required for the Exporter. You can try to invoke interactive SQL and see
what happens.
Sam
| |||||
| 5463.2 | Maybe bad RDB | TRKWSH::COMFORT | Here beside the rising tide | Wed Aug 11 1993 15:52 | 18 |
This may or may not be the problem, cause frankly I don't remeber the
exact SQL error, but...
When I last installed MCC on a system, I also had to put RDB runtime on
also. When doing the RDB runtime installation, I selected * at the
products prompt, after point the kit location to the May CD. What
ended up happening is that there are actually two version of RDB
runtime in the same kit directory and after it installed regular RDB
runtime, it installed some sort of multi-version version or something
like that. The exporter would not work and I after talking to internal
support, I found that I had to re-install RDB runtime, giving the
specific saveset name in vmsinstal.
Hope this can help.
Dave
| |||||