| Was just working on an article to include all causes of ora-06401
errors and found this one already done! Just a few comments:
1. The base note makes several references to DEC DB Int Gtwy.
Those should be changed to Rdb Transparent Gateway for Oracle.
2. Also the title is so long I doubt the error message itself (06401)
will show in STARS. The error message probably makes the best
search and product information is noted under "PRODUCTS" so I would
remove from the title and shorten to the error message itself:
TITLE: -LDRV-E-ORA_DB_SUPP, ORA-06401 Attaching to Oracle
3. Re: the following:
>5. Also be sure that the username issuing the attach statement has run the
> orauser.com file prior to issuing the attach. ORAUSER.COM is used to set
> up the Oracle environment and this must be run prior to trying to access
> the Oracle database.
I would mention that orauser.com sets up logicals one of which points to
tnsnames.ora. That is how item #5 relates to tnsname.ora. And all these
errors are caused by some problem with accessing tnsnames.ora as pointed
out in the beginning of the article.
Thanks, Diane
|
| From: BROKE::BITHER "Please reply to [email protected]" 26-FEB-1997 14:05:29.80
To: MEMORMAN, BASTINE
CC: BITHER
Subj: Revised STARS article of one sent to you by Renee - Thanks, Diane
Hi Mary,
Here is a revised STARS article of one sent to you by Renee. The
original title was "Attaching to Oracle Using Rdb Transparent Gateway
fails with ORA 06401." I've already technically reviewed the article
and made some modifications so please use the below article and not
the one previously sent. When the time comes to make the hardcopy review,
could you please send it to me to be reviewed since I've already
reviewed and tested it?
Thanks, Diane
------------------------------------------------------------------------
TITLE: -LDRV-E-ORA_DB_SUPP, ORA-06401 Attaching to Oracle
PRODUCT: Rdb Transparent Gateway to Oracle
OP/SYS: OpenVMS VAX and AXP
Digital UNIX
SOURCE: Oracle Worldwide Customer Support
PROBLEM:
Attaching to an Oracle database using Rdb Transparent Gateway to Oracle
results in the following error:
SQL> attach 'filename /type=oracle/node=proto/user=scott/pass=tiger';
.
.
.
-LDRV-E-ORA_DB_SUPP, ORA-06401: Unable to open message file (SQL-02113).
or
%LDRV-E-ORA_DB_SUPP, ORA-06401: (Cnct err, can't get err txt. See Servr Msgs
& Codes Manual)
SOLUTION:
The definition of the ORA-06401 error is the following:
06401, 00000, "NETCMN: invalid driver designator"
*Cause: The login (connect) string contains an invalid driver designator.
*Action: Correct the string and re-submit.
There have been several problems that we have seen that would cause this
error. All problems revolve around the tnsnames.ora file. If you encounter
this error, check your tnsnames.ora file for the following possible problems:
1. On UNIX systems, tnsnames.ora must reside in the /etc directory in
order for the Gateway to see it. So rename or copy tnsnames.ora
FROM: $ORACLE_HOME/network/admin/tnsnames.ora
TO: /etc/tnsnames.ora
on the node where Rdb Transparent Gateway to Oracle resides.
2. We have also seen this problem when non-privileged accounts cannot access
the tnsnames.ora file. Ensure that tnsnames.ora has world read and execute
file protections.
3. Be sure that the /NODE qualifier on your attach string is equal to a
service name defined in the tnsnames.ora file, not the physical node name
of the system where Oracle is installed.
4. Be sure that the tnsnames.ora file does not contain any errors when defining
a service. We have seen this error occur when there have been typographical
errors included in a service definition, and that service is then used for
access.
5. Also be sure that the username issuing the attach statement has run the
orauser.com file prior to issuing the attach. ORAUSER.COM is used to set
up the Oracle environment including the setup of a logical name that
points to the location of tnsnames.ora.
\
\
\ CONTRIBUTORS:
\
\ Technical: Renee Bastine
\ Technical Review: Diane Bither
\ Editorial:
|