| > Can my customer do a copy from their dictionary, which is on a remote
> node?
> Would they at least need a license on the local node for CDD?
> At the moment, when they try on a local Alpha accessing a remote
> dictionary on a VAX they get:-
> %lib-e-keynotfou, ...
I found some references in the CDD release notes to remote access, but
nothing that I could see specifically related to accessing a dictionary
on a VAX from an Alpha and getting KEYNOTFOU.
******************************
SYS$COMMON:[SYSHLP]CDD070.RELEASE_NOTES;3
2.1 Remote Attach Problem Corrected.................. 2-1
4.2 Known Problems with Remote Access................ 4-1
***************
2.1 Remote Attach Problem Corrected
In versions of Oracle CDD/Repository prior to Version
7.0, if a standalone machine has a cluster alias and the
repository anchor is on a disk that is not mounted so that
the disk is shared by the cluster (by using the OpenVMS DCL
MOUNT command with the /CLUSTER parameter), a remote attach
to that repository from the same node occurs if you specify
the node name in the path name.
This behavior has been corrected for Oracle CDD/Repository
Version 7.0.
***************
3.1 Restrictions Related to CDO
3.1.31 Quoted Passwords in Pathnames Unsupported
To access a remote repository (a repository running on
a system other than your host), you must obtain a proxy
account. Oracle CDD/Repository does not support quoted
passwords in Oracle CDD/Repository pathnames.
For example, if you wanted to copy an element to or from
a remote repository and you specify your password in the
name string used in the copy command, you will get an error
message similar to the following:
CDO> copy node1"cddtest password"::[cddtest.server.adircdd]f1 f1
copy node1"cddtest password"::[cddtest.server.adircdd]f1 f1
^
%CDO-E-KWSYNTAX, syntax error in command line at or near F1
CDO> copy node1"account password"::[cddtest.server.adircdd]
%CDO-E-ERRCOPY, error copying an object
-CDD-F-IDPC, invalid directory path component in name 'NODE1"CDDTEST'
***************
4.2 Known Problems with Remote Access
The following are known problems that apply to remote
access:
o Attempts to change an object using a remote operation in
the following configuration will not work:
Nodes A and B are in the same cluster.
Node C is standalone.
Repository C was created on Node C.
Repository A was created on Node A.
From Node C, a user invokes CDO, then sets default to
Node_B::Repository_A. This causes a remote attach to
Node B.
Attempts to change objects in Repository A do not
work.
o Remote verify operations are not supported.
o Some forms of recovery from error conditions (network
errors or Oracle Rdb setup errors) are unsuccessful.
o Error messages over the network are sometimes garbled.
o In some cases, cross-repository DEFINE operations, where
a record contains a field that was created on a remote
node, have failed.
You will still see the following errors if the server node
is running Oracle CDD/Repository Version 7.0 or earlier:
%CDO-E-ERRDIRE, error during directory
-CDD-F-ERRFETNEXT, error fetching next stream entity
-SYSTEM-F-ACCVIO, access violation, reason mask=00,
virtual address=002AED3D, PC=03C00000, PSL=00000000
%CDO-E-ERRDIRE, error during directory
-CDO-E-ERRSTARTSESS, error starting a CDD/Plus session
******************************
SYS$COMMON:[SYSHLP]CDD061.RELEASE_NOTES;1
2.54 Remote Access Corrections........................ 2-28
2.54.1 Setup Details for Remote Access ............... 2-30
2.54.2 Remote Access Operations ...................... 2-32
2.54.3 Setup Errors ................................. 2-33
2.54.4 Errors You May See During Remote Operations ... 2-35
|