Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
SangGyu Jeong saw -1 free and bpages values for the temporary smart-blob space on an SDS secondary in onstat -d. Alexandre Marini suggested onstat -g smb c; Art Kagel noted the output matched a standalone primary with SDS. Reinhard Habichtsberg saw the same and said only the primary can write to shared storage. Andreas Legner explained the temp sbspace is shared while SDS_TEMPDBS is private; a feature request may be needed.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
SangGyu Jeong — source: IBM Community (ConnectedCommunity.org) Informix forum
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
↪ replying to SangGyu Jeong
Alexandre Marini — source: IBM Community (ConnectedCommunity.org) Informix forum
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 cwhich 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
------------------------------
↪ replying to Alexandre Marini
Art Kagel — source: IBM Community (ConnectedCommunity.org) Informix forum
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
------------------------------
↪ replying to Art Kagel
Alexandre Marini — source: IBM Community (ConnectedCommunity.org) Informix forum
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
------------------------------
↪ replying to Alexandre Marini
SangGyu Jeong — source: IBM Community (ConnectedCommunity.org) Informix forum
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
------------------------------
↪ replying to SangGyu Jeong
Reinhard Habichtsberg — source: IBM Community (ConnectedCommunity.org) Informix forum
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
------------------------------
↪ replying to Reinhard Habichtsberg
SangGyu Jeong — source: IBM Community (ConnectedCommunity.org) Informix forum
Hi Reinhard,
Thanks you for your reply.
As you said, there seems to be a limitation on the SDS node.
I was wondering why the temporary dbspace specified in the onconfig parameter SDS_TEMPDBS on the sds node is available while the sblob temporary space is not available.
I haven't found yet whether the IBM documentation mentions this restriction.
------------------------------
SangGyu Jeong
Software Engineer
Infrasoft
Seoul Korea, Republic of
------------------------------
↪ replying to SangGyu Jeong
Andreas Legner — source: IBM Community (ConnectedCommunity.org) Informix forum
Hi
SangGyu,
the difference is that a temp sbspace is on shared storage (only writable by SDS primary) while SDS_TEMPDBS is private storage on each SDS.
From a systematic point of view, what's missing is an SDS_TEMP
SBS
option... not sure a feature request (RFE/AHA idea) exists for this already.
BR,
Andreas
------------------------------
Andreas Legner
------------------------------
↪ replying to Andreas Legner
SangGyu Jeong — source: IBM Community (ConnectedCommunity.org) Informix forum
Thank you for answer. Andreas.
My customer does not need the feature to use temporary sblob-space on the SDS node right away.
I just wanted to know if this is normal for SDS.
But I might need to request a feature later. ;)
------------------------------
SangGyu Jeong
Software Engineer
Infrasoft
Seoul Korea, Republic of
------------------------------
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.