Loss of SQL connectivity – a problem with the wetware

The problem

I lost SQL connectivity to all databases between about 11.29 and 12.06 today (21st June).

According to the trace files whereas normally the Names servers are addressed as follows:

[000001 19-MAY-2005 14:11:16:517] NAMES.PREFERRED_SERVERS = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = vAlias1)(PORT = 101)) (ADDRESS = (PROTOCOL = TCP)(HOST = vAlias2)(PORT = 101)))

during this period they were addressed:

[000001 21-JUN-2005 11:43:34:114] NAMES.PREFERRED_SERVERS = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 46.2.3.44499)(PORT = 101)) (ADDRESS = (PROTOCOL = TCP)(HOST = 46.2.3.44599)(PORT = 101)))

The IP addresses in the incorrect address are the correct addresses (for dbs18 and dbs15) respectively, but with a ’99’ appended. And ‘normally’ the trace file shows the alias anyway.

Empirix didn’t show any issues – it could have just been me, but I didn’t make any changes that might have caused, or fixed, it.

Oracles (correct) response

I don’t think this is a DNS issue. I would have to say that the sqlnet.ora has been changed. The beginning of the trace shows the sqlnet.ora after it has been read, but before it has been parsed at all. This shows the invalid value already there.

Your two traces differ in that the ‘incorrect’ one appears to be reading its sqlnet.ora from C:Tempsqlnet.ora

Presumably I was in c:temp when I was kicking off sql.

As I say it was a problem with the wetware

Advertisements