sdsGetSecondaryProxy

sdsGetSecondaryProxy(name:  String;
                     proxy: JadeDynamicObject input);

The sdsGetSecondaryProxy method of the JadeDatabaseAdmin class, valid only at the primary database system, creates and populates an SDSSecondaryProxy object for the secondary system or RPS node specified in the name parameter and returns the secondary or RPS proxy dynamic object in the proxy parameter.

The SDSSecondaryProxy object returned by the sdsGetSecondaryProxy method contains a subset of the SDSSecondary dynamic object attributes, including nextJournalNumber.

The secondary or RPS proxy object:

You should call this method to first get a secondary or RPS proxy object and check the connectionState attribute value before calling the sdsGetSecondaryInfo method.

Use this method in conjunction with the JadeDatabaseAdmin class getCurrentJournalOffset method to determine the amount of journal data that has not been sent to the secondary.

The SDSSecondaryProxy dynamic object has a JadeDynamicObject class name attribute value of SDSSecondaryProxy and type attribute value of SDS_SecondaryProxyType (2).

The dynamic attributes that are returned are listed in the following table.

Name Type Description
connectionCheckInterval Integer Number of seconds at which the secondary database or RPS node polls the primary to determine reachability via the communication paths, specified in the ConnectionPollInterval parameter in the [SyncDbService] section of the Jade initialization file
connectionState Integer State of the connection to the primary
hostName String Computer name of the secondary or RPS proxy host on the primary
lastErrorCode Integer Number of the last error that occurred
myName String Name of the secondary or RPS proxy on the primary, specified in the MyName parameter in the [SyncDbService] section of the Jade initialization file
nextJournalNumber Integer Next journal the primary sends if the secondary or RPS node is catching up or the next write journal when the secondary or RPS node is mirroring writes from the current journal. It remains valid when the secondary or RPS node is disconnected.
primaryServerName String Name of the primary, specified in the PrimaryServerName parameter in the [SyncDbService] section of the Jade initialization file
subrole Integer Database role
syncMode Integer Mode of journal synchronization, specified in the SyncMode parameter in the [SyncDbService] section of the Jade initialization file
totalSends Integer64 Count of messages sent to the secondary
totalBlocksSent Integer64 Count of journal blocks sent to the secondary (there can be from 1 through 16 blocks per message)
totalBytesSent Integer64 Count of bytes sent to the secondary; that is, the total size of all messages sent
totalUncompressedBytes Integer64 Count of bytes sent to the secondary if compression was disabled
lastRecordSentJournal Integer64 Journal number of the last journal record sent
lastRecordSentOffset Integer64 Byte offset of the last journal record sent

The values of the subrole attribute are represented by one of the SDSDatabaseRoles category global constants listed in the following table.

Global Constant Integer Value Description
SDS_SubroleNative 1 Native Jade Object Manager database
SDS_SubroleRelational 2 Relational database

The values of the syncMode attribute are represented by one of the SDSSecondaryState category global constants listed in the following table.

Global Constant Integer Value
SDS_BlockWrite 2
SDS_JournalSwitch 1

The caller is responsible for deletion of these transient dynamic objects. Deletion is best achieved by purging the object when the entry has been processed.