Re: problem with ORA-02019

spamdump_at_nospam.noway.nohow (Ed Stevens) wrote in message news:<3d77a09a.77577089_at_ausnews.austin.ibm.com>...
> Platform: Oracle SE 8.1.7 on NT4
>
> Any ideas of what I'm seeing here?
>
> I'm not sure when this started, but I'm finding in one of my test/development
> databases (alert log) the following series of messages:
>
> Errors in file e:\oradmin\xctt\bdump\xcttRECO.TRC:
> ORA-02019: connection description for remote database not found
> ORA-01017: invalid username/password; logon denied
> ORA-02063: preceding line from LN_DB2T
>
> These have occurred at ever increasing intervals, beginning less than a minute
> after completion of database startup:
>
> Thu Sep 05 09:51:00 2002
> Thu Sep 05 09:51:36 2002
> Thu Sep 05 09:52:29 2002
> Thu Sep 05 09:53:50 2002
> Thu Sep 05 09:55:50 2002
> Thu Sep 05 09:58:53 2002
> Thu Sep 05 10:03:25 2002
> Thu Sep 05 10:10:22 2002
> Thu Sep 05 10:20:38 2002
> Thu Sep 05 10:36:24 2002
> Thu Sep 05 10:59:43 2002
> Thu Sep 05 11:34:47 2002
> Thu Sep 05 12:27:47 2002
>
> If I bounce the database, the pattern starts over again. Once I started chasing
> this down I made sure that the users (developers) were off the database, so that
> the errors are coming from some internal db activity, rather than connected user
> activity.
>
> The object LN_DB2T referenced in the ORA-02063 is a database link to an Oracle
> Transparent Gateway associated with a DB2 region on our mainframe. When I test
> that link myself, it seems to be functioning, as shown in this spool from
> SQL*Plus:
>
> SQL*Plus: Release 8.1.7.0.0 - Production on Thu Sep 5 12:53:15 2002
>
> (c) Copyright 2000 Oracle Corporation. All rights reserved.
>
> SQL> connect system_at_xcttdb
> Enter password: ******
> Connected.
> SQL> select count(*) from nmm.online_user_at_LN_DB2T;
>
> COUNT(*)
> ----------
> 3993
>
> SQL>
>
> This tells me (??) that the link in the database and the TNSNAMES entry
> referencing the DB2 region are both defined correctly.
>
> The listener log doesn't show any irregularities, and none of the connections
> listed there coincide with the errors reported in the alert log.

Looks like there might be a background job which is trying to access LN_DB2T instance which may have a wrong username/password defined in it. Query DBA_JOBS.

//Rauf Sarwar Received on Thu Sep 05 2002 - 18:14:44 CDT