Friend :
Once time ago, i had a problem with remote connection.
So, i had solved it putting the ip of other machine in the file called by
"hosts".
This file is located in the o OS directory.
I were using sqlplus with client installed in the station.
You can try to connect using the server datab
So,
there is no way ...to sole it out,
Regards
Arvind
-Original Message-
Sent: Friday, August 09, 2002 10:23 AM
To: Multiple recipients of list ORACLE-L
Hi Arvind
From the error message it is clear that remote tables ae having some
object type columns which is not permitted.
--
Hi Arvind
From the error message it is clear that remote tables ae having some
object type columns which is not permitted.
-Original Message-
Sent: Friday, August 09, 2002 9:58 AM
To: Multiple recipients of list ORACLE-L
Dear All,
i have created a DB link to remote database its
n sense will not accomplish great things. Simply become insane and
> desperate."
>
> > -Original Message-
> > From: Suzy Vordos [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, March 14, 2002 9:59 AM
> > To: Multiple recipients of list ORACLE-L
> &g
> -Original Message-
> > From: Suzy Vordos [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, March 14, 2002 9:59 AM
> > To: Multiple recipients of list ORACLE-L
> > Subject: Re: DB Link Problem
> >
> >
> > If using Replication, init.ora must hav
sense will not accomplish great things. Simply become insane and
desperate."
> -Original Message-
> From: Suzy Vordos [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, March 14, 2002 9:59 AM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: DB Link Problem
>
erate."
> -Original Message-
> From: Paul Baumgartel [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, March 14, 2002 9:59 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: DB Link Problem
>
> Yes, setting GLOBAL_NAMES = FALSE will allow the DB link to work,
If using Replication, init.ora must have global_names=TRUE. So in that
case you'd either want to execute 'alter session set global_names=FALSE'
at connect time, or create the database link as 'create database link
maxtest.tfmc.co.za ...'.
> Rodd Holman wrote:
>
> In your init.ora file add the
Yes, setting GLOBAL_NAMES = FALSE will allow the DB link to work, but
if you are using Advanced Replication, GLOBAL_NAMES must be set to TRUE
and your DB links must conform to the requirement that it imposes.
Paul Baumgartel
--- [EMAIL PROTECTED] wrote:
> set GLOBAL_NAMES to false from sql promp
I always set the global_name manually, with an update statement.
It does have to match, or it won't work.
Denham Eva wrote:
Hello List,
Have a problem,
Oracle 817
Win3K sp6
Trying to create a DB link between
the production and the test dbs.
The db_link creates fine ( so
it appears).
However wh
Title: DB Link Problem
In your init.ora file add the following:
global_names = FALSE
Then it won't care. All it will want at that point is to have a correct and working tnsnames.ora entry in the USING clause of the dblink create statement.
Rodd
On Thu, 2002-03-14 at 07:03, Denham
set GLOBAL_NAMES to false from sql prompt and in the init.ora file.
Scott Shafer
San Antonio, TX
210-581-6217
"Common sense will not accomplish great things. Simply become insane and
desperate."
> -Original Message-
> From: Denham Eva [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, March 14,
Title: DB Link Problem
did
you make sure there's a tns entry on the db server for the remote db being
accessed by the link?
-Original Message-From: Denham Eva
[mailto:[EMAIL PROTECTED]]Sent: Thu, March 14, 2002 8:03
AMTo: Multiple recipients of list ORACLE-LSubject: DB
Link
Title: DB Link Problem
Try
setting the GLOBAL_NAMES init parameter to FALSE.
HTHMark
P.S.
WOW you have Win3K! ;P
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Denham EvaSent: 14
March 2002 13:03To: Multiple recipients of list
ORACLE-L
14 matches
Mail list logo
