Db links within view failing

Question

DB Version 10.2.0.3 on Linux pointing to another 10.2.0.3 DB on a remote Linux box...
myUnixPrompt> echo $ORACLE_SID
mydb
myUnixPrompt>sqlplus /nolog
SQL> connect someschema/somepassword;
SQL> create database link the_link connect to remote_id identified by thepassword using hello.world.com;
SQL> create or replace view someschema.test_view as select * from dual@the_link;
SQL> grant select on someschema.test_view to public;
SQL> connect theuser/theuserspassword;
SQL> select * from someschema.test_view;
ERROR at line 1:
ORA-12154: TNS:could not resolve the connect identifier specified
SQL> connect theuser@mydb/theuserspassword
SQL> select * from someschema.test_view;
D
X
Okay...So why does Oracle work when I connect to the same user, same sqlplus executable, same linux environmental variable using the @, but fails when the user connects using the oracle_sid?
Thoughts?

Answer 1

Excellent point, not really germane to the question posed, however you are correct definer rights prevail.
Consider this, if the view and the private db link are owned by the same user, then the view does have permissions on the link. In the same way a db package in the same schema and the private db link would be able to hide the db link from the calling user.
More to the point of my original example was the fact the same user, "theuser", can select from the view depending on the manner in which the connection was made to the database.
Failing case, "theuser" connected to the database via sqlplus on the db server as: theuser/theuserspassword
Success case, "theuser" connected to the database via the same sqlplus executable as the failing case, but as: theuser@mydb/password
The @ made a difference in the name resolution of the connect to database defined in the private database link.
Yes, Oracle support should be contacted, but getting the answer is like dental work, slow and painful. I had hoped someone else had encountered this scenario.
Additional information for this,
the sqlnet.ora file used is the same whether a direct connect or via @, however the sqlnet.ora has the name resolution in the following order: LDAP, ONAMES, TNSNAMES. In the case of connection via @, LDAP succeeds, however a direct connection always results in TNSNAMES resolution.
So, if the observation is correct, why is LDAP not being used when a direct connect, but only for @?
Thx...
-Scott