Hi Neville,
1) In the production system, can we create all the dbspaces on RAW partitions and only have the SDS_TEMPDBS parameter as normal/cooked file ?
You can use either cooked files or raw partitions. All my Informix customers are using raw partitions for SDS temporary dbspaces.
2) On a system which has both the PRIMARY and SDS instances are on the same system (VM), do we necessarily have to give
separate values (i.e. separate destination files) for the
SDS_TEMPDBS parameter ?
I think it's a good idea to use separate files for each PRIMARY and SDS instance. If a PRIMARY server fail occurs, the SDS node switches to the PRIMARY server, with the files specified in SDS_TEMPDBS still online.
If the primary server in a high-availability cluster fails and an SD secondary server takes over as the primary server, then the
value set for the SDS_TEMPDBS configuration parameter on the SD secondary server is used for temporary dbspaces until
the server is restarted. You should ensure that the value specified for the SDS_TEMPDBS configuration parameter on the SD
secondary server is different than the value specified on the primary server. After the SD secondary server is restarted, the
DBSPACETEMP configuration parameter is used.
https://www.ibm.com/support/knowledgecenter/en/SSGU8G_12.1.0/com.ibm.adref.doc/ids_adr_0151.htm
3) In a production environment of Primary and SDS instances, the rootdbs, the dbspace containing the physical log, the dbspace containing the logical logs, all the user dbspaces, blobspaces, sbspaces etc ... have to point at the same target files (i.e. destination files). I wanted to know, which parameters in the ONCONFIG files of Primary and SDS instances, have to necessarily have DIFFERENT values from each other.
At a minimum, the onconfig parameter below must be set differently for both PRIMARY and SDS. And if your instances are on the same host, you should also consider the SERVERNUM setting.
MSGPATH
CONSOLE
DBSERVERNAME
SDS_TEMPDBS
------------------------------
SangGyu Jeong
Software Engineer
Infrasoft
Seoul Korea, Republic of
------------------------------
Original Message:
Sent: Thu January 09, 2020 08:30 AM
From: Neville Monteiro
Subject: SDS
I am trying to setup SDS systems and therefore needed help in clearing certain doubts.
1) In the production system, can we create all the dbspaces on RAW partitions and only have the SDS_TEMPDBS parameter as normal/cooked file ?
2) On a system which has both the PRIMARY and SDS instances are on the same system (VM), do we necessarily have to give separate values (i.e. separate destination files) for the SDS_TEMPDBS parameter ?
3) In a production environment of Primary and SDS instances, the rootdbs, the dbspace containing the physical log, the dbspace containing the logical logs, all the user dbspaces, blobspaces, sbspaces etc ... have to point at the same target files (i.e. destination files). I wanted to know, which parameters in the ONCONFIG files of Primary and SDS instances, have to necessarily have DIFFERENT values from each other.
------------------------------
Neville Monteiro
------------------------------
#Informix