Re: Remote database server problem!

Hmmm, I have always relied on a function like that TestConnection, however using a remote function LocalSysdate to calculate the time difference. Note that in my function I do not actually call a remote procedure, but only use the remote dual table. Like I said: the sysdate you'll get is your local time, not the time of the remote server. Could be that the query is still in the cache, and therefore the function returns true while it should have returned false. Maybe you should create a real function on the remote database and change the TestConnection to really call a remote function. Or perfom a select count(*) from user_tables_at_my_dblink.

On the remote server:

    create or replace LocalSysdate return date     as
    begin
      return sysdate;
    end LocalSysdate;

In TestConnection change the select statement into

    select LocalSysdate_at_my_dblink
    into v_Dummy
    from dual;

Arjan.

>when I close the session after the database was
>shut down, and then start a new session, and then executing the remote
>procedure, nothing happens i.e. UI hangs.
Received on Thu Jul 23 1998 - 14:19:25 CDT