Hi all,
it's exactly the same here. It seems to be normal.
Primary:
120d5da40 4 0x4a001 4 1 2048 N UBA informix sbspacetemp
120c1c028 4 4 0 1000000 932620 932620 POSB-- /var/informix/dev/db1c004
SDS:
10fd5ea40 4 0x248001 4 1 2048 N WBA informix sbspacetemp
10fdab028 4 4 0 1000000 -1 -1 POSB-- /var/informix/dev/db1c004
Art, Alexandre: He asked for a Primary and a (read only) SDS, not for a HA-Cluster or RSS.
SangGyu: A SDS cannot write to the storage, even a Writable SDS. Only the primary is allowed for write operations. May be thats the reason.
HTH, Reinhard.
------------------------------
Reinhard Habichtsberg
------------------------------
Original Message:
Sent: Tue October 29, 2019 10:21 AM
From: SangGyu Jeong
Subject: Questions about using temporary smart-blob space on SDS nodes
Hi, Alexandre and Art.
Thanks for your replies.
Below is the result of executing onstat -g smb c command on Primary and SDS nodes.
The results of the command run on the SDS node did not show any information about the chunks of the temporary sblob-space.
------------------------------
SangGyu Jeong
Software Engineer
Infrasoft
Seoul Korea, Republic of
Original Message:
Sent: Tue October 29, 2019 09:53 AM
From: Alexandre Marini
Subject: Questions about using temporary smart-blob space on SDS nodes
Ok Art, thank you so much for poiting that out. My mistake.
Anyway, I think that onstat command would help him, right? Hope so....
------------------------------
Alexandre Marini
Original Message:
Sent: Tue October 29, 2019 09:42 AM
From: Art Kagel
Subject: Questions about using temporary smart-blob space on SDS nodes
Alexandre:
If you only have RSS and/or SDS secondaries and no HDR secondary then the primary can be in standalone mode and does not have to be in primary mode, so the onstat -d outputs that the OP posted are indeed consistent with a primary in standalone mode and an SDS secondary with no HDR secondary. There is nothing wrong with the data he displayed.
Art
------------------------------
Art Kagel
Original Message:
Sent: Tue October 29, 2019 08:50 AM
From: Alexandre Marini
Subject: Questions about using temporary smart-blob space on SDS nodes
Hi SangGyu.
I think there is some confusion on your question.
The first output is not from the same cluster of 2nd (notice that a cluster primary should show "On-Line (Prim)" on the header
Your output is got from a single instance, not a cluster ok?
Check that again, please, and post here.
If it keeps showing the same "-1" value, you can use
onstat -g smb c
which should show you everything.
Manual page: https://www.ibm.com/support/knowledgecenter/en/SSGU8G_14.1.0/com.ibm.admin.doc/ids_admin_0637.htm
HTH
------------------------------
Alexandre Marini
Original Message:
Sent: Tue October 29, 2019 03:27 AM
From: SangGyu Jeong
Subject: Questions about using temporary smart-blob space on SDS nodes
My customer is using Informix with two nodes, Primary and Shared Disk Secondary.
When I run the onstat -d command on the SDS Secondary node, the free and bpages values for the temporary smart-blob space are displayed as -1.
Below is the result of onstat -d in my test environment.
Similarly, the chunk of the temporary smart blobspace shows a value of -1.
<Primary>
<SDS Secondary>
Is this normal?
If so, can't we use temporary smart-blob space on SDS Secondary nodes?
Thanks,
------------------------------
SangGyu Jeong
Software Engineer
Infrasoft
Seoul Korea, Republic of
------------------------------
#Informix