Grid errors 3333 and 3334 when the grid is attached with the wrong number of parameters (Doc ID 1626639.1)

Last updated on FEBRUARY 27, 2016

Applies to:

Oracle TimesTen In-Memory Database - Version 11.2.2.4.0 and later
Information in this document applies to any platform.

Symptoms

See the following example of how to get into these errors:

 

node1/host1: active;
node2/host2: standby

global dynamic awt cg is created.

active:
=======
Command> call ttgridattach(1,'cache1','host1',5001,'cache2',5002);  <<==Not including node2 name intentionally
Command> call ttgridnodestatus;                                                 
< MYGRID, 1, 1, T, host1, MYGRID_cache1_1A, 12.34.56.140, 5001, F,  , MYGRID_cache2_1B, 5002, 0 >
1 row found.
Command> call ttrepstateget;
< ACTIVE, AVAILABLE >

<<As you can see above, there is "0" at the end and no ip address listed for node2>>

Standby:
=========
ttrepadmin -duplicate
Command> call ttrepstart;
Command> call ttgridattach(2,'cache1','host1',5001,'cache2','host2',5002);
3333: Time out waiting for a response from member MYGRID_cache1_1A
The command failed.

<<Got timeout, but it was partially attached still>>

And this is the gridnodestatus after the timeout error:
Command> call ttgridnodestatus;
< MYGRID, 1, 1, T, host1, MYGRID_cache1_1A, 12.34.56.140, 5001, T, host2, MYGRID_cache2_1B, 12.34.56.141, 5002 >
1 row found.

It doesn't have the "0" any longer.  And node2 has "T" status.


Active:
======
Command> call ttgriddetach;
Command> call ttgridnodestatus;
< MYGRID, 1, 1, T, host1, MYGRID_cache1_1A, 12.34.56.140, 5001, T, host2, MYGRID_cache2_1B, 12.34.56.141, 5002 >
1 row found.

<<ttgriddetach wasnt completely successful in detaching the node because it left it in state "T">>

Attach it this time again with the right parameters including the node2 info:
Command> call ttgridattach(1,'cache1','host1',5001,'cache2','host2',5002);
Command> call ttgridnodestatus;                                                 
< MYGRID, 1, 1, T, host1, MYGRID_cache1_1A, 12.34.56.140, 5001, T, host2, MYGRID_cache2_1B, 12.34.56.141, 5002 >
1 row found.

Command> call ttgriddetach;  << detach again so I can attach it again with the wrong parameter later
Command> call ttgridnodestatus;
< MYGRID, 1, 1, F, host1, MYGRID_cache1_1A, 12.34.56.140, 5001, T, host2, MYGRID_cache2_1B, 12.34.56.141, 5002 >
1 row found.
<detach is successful, got "F" status for node1>>

attach with the wrong parameter again:
Command> call ttgridattach(1,'cache1','host1',5001,'cache2',5002);
Command> call ttgridnodestatus;                                                

< MYGRID, 1, 1, T, host1, MYGRID_cache1_1A, 12.34.56.140, 5001, T, host2, MYGRID_cache2_1B, 5002, 0 >
1 row found.

Now, you can see the active and standby are both attached, but with the strange state of "0", and no ipaddr2 info

Standby:
========
Try to attach again, and now got the same port/ip conflict:

Command> call ttgridattach(2,'cache1','host1',5001,'cache2','host2',5002);
5107: Oracle(OCI) warning in OCIStmtExecute(): ORA-24345: A Truncation or null fetch error occurred rc = 1
3334: Specified IP address and port number combination has been used
The command failed.



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