|
Hi,
I discover that the error -DBI-E-ATTLNKERR also occurs at interactive
SQL only at the second attach in the same sql session i.e. the select
statement immediately follows the second attach. NOTE the select
statement after the first attach is alright.
Please refer to log below:
attach 'filename norm_dbi';
show version
Current version of SQL is: DEC SQL V6.1-04
Underlying versions are:
Database with filename norm_dbi
DBI V3.1-00
Rdb/Dispatch V6.1-04 (OpenVMS VAX)
show link
User links in database with filename norm_dbi
Link MAXCIM_DB_LINK
Connection information: /TYPE=NSDS/PATHNAME=norm_src:NORM_MAXCIM_GW.CDO
To database type: DB Access for RMS (NSDS)
State: Inactive
Link NORM_DB_LINK
Connection information: norm_db
To database type: DEC Rdb
State: Inactive
Link REVCON_DB_LINK
Connection information: /type=nsds/path=norm_src:NORM_REVCON_GW.CDO
To database type: DB Access for RMS (NSDS)
State: Inactive
Link SAI_DB_LINK
Connection information: sai_db
To database type: DEC Rdb
State: Inactive
Link SERIAL_TAG_DB_LINK
Connection information: /type=nsds/path=norm_src:SERIAL_TAG_GW.CDO
To database type: DB Access for RMS (NSDS)
State: Inactive
@norm_log:tmp.sql
SELECT BUN FROM NEXT_DIRTY_ORDER_VIEW LEFT OUTER JOIN ZZMHS ON BUN = BUN_NUMBER WHERE BUN_NUMBER IS NULL AND ASSMBLY_LINE_ID = '001' ORDER BY BUN_PRRTY_ID DESC, SCHDLD_RLES_DT ASC, ORDER_TYPE_PRRTY_ID ASC,CPU_TYPE_PRRTY_ID ASC LIMIT TO 1 ROW
;
NEXT_DIRTY_ORDER_VIEW.BUN
F00056
1 row selected
finish;
%SQL-I-DEPR_FEATURE, Deprecated Feature: FINISH is replaced by DISCONNECT
attach 'filename norm_dbi'; -- second attach
@norm_log:tmp.sql
SELECT BUN FROM NEXT_DIRTY_ORDER_VIEW LEFT OUTER JOIN ZZMHS ON BUN = BUN_NUMBER WHERE BUN_NUMBER IS NULL AND ASSMBLY_LINE_ID = '001' ORDER BY BUN_PRRTY_ID DESC, SCHDLD_RLES_DT ASC, ORDER_TYPE_PRRTY_ID ASC,CPU_TYPE_PRRTY_ID ASC LIMIT TO 1 ROW
;
%RDB-F-SYS_REQUEST, error from system services request
-DBI-E-ATTLNKERR, Error attaching database, Link name='MAXCIM_DB_LINK', Connect string='/TYPE=NSDS/PATHNAME=norm_src:NORM_MAXCIM_GW.CDO'
-RDB-I-TEXT, -RDB-F-IO_ERROR, input or output error
-RDB-I-TEXT, -COSI-F-NOTNETDEV, not a network communication device
exit
2. The error does not occur if you issue a simple select statement and
then issue the complex select statement.
attach 'filename norm_dbi';
@norm_log:tmp.sql;
SELECT BUN FROM NEXT_DIRTY_ORDER_VIEW LEFT OUTER JOIN ZZMHS ON BUN = BUN_NUMBER WHERE BUN_NUMBER IS NULL AND ASSMBLY_LINE_ID = '001' ORDER BY BUN_PRRTY_ID DESC, SCHDLD_RLES_DT ASC, ORDER_TYPE_PRRTY_ID ASC,CPU_TYPE_PRRTY_ID ASC LIMIT TO 1 ROW
;
NEXT_DIRTY_ORDER_VIEW.BUN
F00044
1 row selected
finish;
%SQL-I-DEPR_FEATURE, Deprecated Feature: FINISH is replaced by DISCONNECT
attach 'filename norm_dbi';
select * from zzmhs; ======> this is the simple select statement
0 rows selected
@norm_log:tmp.sql;
SELECT BUN FROM NEXT_DIRTY_ORDER_VIEW LEFT OUTER JOIN ZZMHS ON BUN = BUN_NUMBER WHERE BUN_NUMBER IS NULL AND ASSMBLY_LINE_ID = '001' ORDER BY BUN_PRRTY_ID DESC, SCHDLD_RLES_DT ASC, ORDER_TYPE_PRRTY_ID ASC,CPU_TYPE_PRRTY_ID ASC LIMIT TO 1 ROW
;
NEXT_DIRTY_ORDER_VIEW.BUN
F00044
1 row selected
finish;
%SQL-I-DEPR_FEATURE, Deprecated Feature: FINISH is replaced by DISCONNECT
attach 'filename norm_dbi';
@norm_log:tmp.sql;
SELECT BUN FROM NEXT_DIRTY_ORDER_VIEW LEFT OUTER JOIN ZZMHS ON BUN = BUN_NUMBER WHERE BUN_NUMBER IS NULL AND ASSMBLY_LINE_ID = '001' ORDER BY BUN_PRRTY_ID DESC, SCHDLD_RLES_DT ASC, ORDER_TYPE_PRRTY_ID ASC,CPU_TYPE_PRRTY_ID ASC LIMIT TO 1 ROW
;
%RDB-F-SYS_REQUEST, error from system services request
-DBI-E-ATTLNKERR, Error attaching database, Link name='MAXCIM_DB_LINK', Connect string='/TYPE=NSDS/PATHNAME=norm_src:NORM_MAXCIM_GW.CDO'
-RDB-I-TEXT, -RDB-F-IO_ERROR, input or output error
-RDB-I-TEXT, -COSI-F-NOTNETDEV, not a network communication device
exit
|
| Hi,
The same result appear whether you rmu/convert or create the catalog
again. Later I managed to resolve the interactive sql problem by
$define dbi_dsri_under "F"
From the STARS database, this will switch off the asynchronous
feature in DBI and that V5.1 RDB/Dispatch does not support the asynch
calls that 6.1 support. However for my environment the RDB dispatch
is version 6.1. So my question is why does it happen in this case ?
Rgds,
Yan Noi
|
| > From the STARS database, this will switch off the asynchronous
> feature in DBI and that V5.1 RDB/Dispatch does not support the asynch
> calls that 6.1 support. However for my environment the RDB dispatch
> is version 6.1. So my question is why does it happen in this case ?
Sounds like you have more than one version of Dispatch on your system and
the wrong one is being used when accessing this table. Check the links
to these tables to be sure that the link string issues a login that sets
the appropriate Rdb environment up for the attach.
For instance:
If you have multiversion installed on your system and the link still points
to a 6.0 database, then the link from the Rdb 6.1 DBI catalog should look
like this:
dbs400::sys$common:[sqluser60]personnel/REMOTE
You need to force a remote login, so that the new process created will use
the "standard" version of RDB when accessing the data, or use a username
and password so that that user's login is run which would set the appropriate
version of the Rdb with a @sys$library:decrdb$setver 6.0 command.
Renee
|
| Did you double check to be sure you only had one version of
RDB$SHARE.EXE in SYS$LIBRARY? Do you have some other versions like:
RDB$SHARE60.EXE
You may have said already, and I don't remember, what version of NSDS are
you running? You can get the version by using the following command:
anal/image/interactive sys$library:nsds$shr.exe
Hit return 4 times, and the version will be on that screen.
Thanks,
Renee
|