ORA-12569 While Trying To Query SYS.DBA_AUDIT_TRAIL Via Oracle Net (Doc ID 815165.1)

Last updated on APRIL 08, 2016

Applies to:

Oracle Net Services - Version: 10.1.0.4.0 to 10.2.0.4.0
This problem can occur on any platform.

Symptoms

The following error gets thrown while trying to access the sys.dba_audit_trail from a remote client via Oracle net.


ORA-12569 TNS:packet checksum failure

The following is an example of the detail captured in matching client / server Oracle Net traces.  The packet of information is some data from the COMMENT$TEXT column in the audit table.  It includes the address from a client which was authenticated.  Please note that the ip address has been changed for the purpose of this example.

Server trace:

[25-JUN-2008 17:37:29:248] nttwr: socket 9168 had bytes written=211
[25-JUN-2008 17:37:29:248] nttwr: exit
[25-JUN-2008 17:37:29:248] nspsend: packet dump
[25-JUN-2008 17:37:29:248] nspsend: 00 D3 00 00 06 00 00 00  |........|
[25-JUN-2008 17:37:29:248] nspsend: 00 00 35 32 29 29 07 63  |..52)).c|
[25-JUN-2008 17:37:29:248] nspsend: 41 75 74 68 65 6E 74 69  |Authenti|
[25-JUN-2008 17:37:29:248] nspsend: 63 61 74 65 64 20 62 79  |cated.by|
[25-JUN-2008 17:37:29:248] nspsend: 3A 20 44 41 54 41 42 41  |:.DATABA|
[25-JUN-2008 17:37:29:248] nspsend: 53 45 3B 20 43 6C 69 65  |SE;.Clie|
[25-JUN-2008 17:37:29:248] nspsend: 6E 74 20 61 64 64 72 65  |nt.addre|
[25-JUN-2008 17:37:29:248] nspsend: 73 73 3A 20 28 41 44 44  |ss:.(ADD|
[25-JUN-2008 17:37:29:248] nspsend: 52 45 53 53 3D 28 50 52  |RESS=(PR|
[25-JUN-2008 17:37:29:248] nspsend: 4F 54 4F 43 4F 4C 3D 74  |OTOCOL=t|
[25-JUN-2008 17:37:29:248] nspsend: 63 70 29 28 48 4F 53 54  |cp)(HOST|
[25-JUN-2008 17:37:29:248] nspsend: 3D 31 35 30 2E 31 35 32  |=123.123|
[25-JUN-2008 17:37:29:248] nspsend: 2E 34 36 2E 37 35 29 28  |.12.12)(|
[25-JUN-2008 17:37:29:248] nspsend: 50 4F 52 54 3D 32 38 38  |PORT=288|
[25-JUN-2008 17:37:29:248] nspsend: 36 29 29 04 01 00 00 00  |6)).....|

Note the size of the packet at the top:  socket 9168 had bytes written=211.  Notice also the port number is 2886.

The matching client trace shows:

[25-JUN-2008 17:37:14:197] nttrd: socket 244 had bytes read=212
[25-JUN-2008 17:37:14:197] nttrd: exit
[25-JUN-2008 17:37:14:197] nsprecv: 212 bytes from transport
[25-JUN-2008 17:37:14:197] nsprecv: tlen=212, plen=211, type=6
[25-JUN-2008 17:37:14:197] nsprecv: 1 bytes to leftover
[25-JUN-2008 17:37:14:197] nsprecv: packet dump
[25-JUN-2008 17:37:14:197] nsprecv: 00 D3 00 00 06 00 00 00  |........|
[25-JUN-2008 17:37:14:197] nsprecv: 00 00 35 32 29 29 07 63  |..52)).c|
[25-JUN-2008 17:37:14:197] nsprecv: 41 75 74 68 65 6E 74 69  |Authenti|
[25-JUN-2008 17:37:14:197] nsprecv: 63 61 74 65 64 20 62 79  |cated.by|
[25-JUN-2008 17:37:14:197] nsprecv: 3A 20 44 41 54 41 42 41  |:.DATABA|
[25-JUN-2008 17:37:14:197] nsprecv: 53 45 3B 20 43 6C 69 65  |SE;.Clie|
[25-JUN-2008 17:37:14:197] nsprecv: 6E 74 20 61 64 64 72 65  |nt.addre|
[25-JUN-2008 17:37:14:197] nsprecv: 73 73 3A 20 28 41 44 44  |ss:.(ADD|
[25-JUN-2008 17:37:14:197] nsprecv: 52 45 53 53 3D 28 50 52  |RESS=(PR|
[25-JUN-2008 17:37:14:197] nsprecv: 4F 54 4F 43 4F 4C 3D 74  |OTOCOL=t|
[25-JUN-2008 17:37:14:197] nsprecv: 63 70 29 28 48 4F 53 54  |cp)(HOST|
[25-JUN-2008 17:37:14:197] nsprecv: 3D 31 35 30 2E 31 35 32  |=123.123|
[25-JUN-2008 17:37:14:197] nsprecv: 2E 34 36 2E 37 35 29 28  |.12.12)(|
[25-JUN-2008 17:37:14:197] nsprecv: 50 4F 52 54 3D 32 34 31  |PORT=241|
[25-JUN-2008 17:37:14:197] nsprecv: 33 34 29 29 04 01 00 00  |34))....|

Again, note the size of the packet:  socket 244 had bytes read=212 .   The packet has changed between the server and the client.  It was sent from the server at a size of 211 bytes.  It arrived at the client with a size of 212 bytes.  If you look carefully, you'll notice that the port has been changed inside the data packet.   The original data packet shows port 2886.   When the packet reached the client, the port had been altered to 24134

Here we see the "1 bytes to leftover":

[25-JUN-2008 17:37:14:197] nsprecv: tlen=212, plen=211, type=6 
[25-JUN-2008 17:37:14:197] nsprecv: 1 bytes to leftover 


Shortly thereafter, the checksum ns=12569 error will occur:

nsprecv: header checksum error 
nsprecv: packet hdr 
nsprecv: 42 30 07 DB 00 00 00 00 |B0......| 
nserror: entry 
nserror: nsres: id=0, op=68, ns=12569, ns2=0; nt[0]=0, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0 





Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms