Here are some ideas to try. Some of these may increase the speed of posting in your environment, and some may not. Choose the ones that work for you.
Tune the target database, are the correct indexes being used? Do you have too many indexes? Remember that on an update to an indexed column the index will go through a delete and insert, two operations on the index for every update to the key.
Add indexes on the source. Shareplex builds a key e.g. "where clause" when you activate. Shareplex does this only at activation. The problem is that shareplex will use all columns in a table minus columns with the long datatype on tables without primary key or unique indexes. The order of key selection is primary key then the shortest unique key and lastly all columns minus columns with the long datatype.
Create an oracle "hint" and put it in the Shareplex hints file located in the $VARDIR/data directory. See Implimentation guide for directions.
Remove constraints on the target. These are not needed on a reporting instance since they are validated on the source. This can't be done on dual master-master installations
Increase the post read release interval. This parameter read releases the data in the queue that have already been applied to the target. Better performance can be expected by doing this less often. Increasing the SP_OPO_READ_RELEASE_INTERVAL from the initial value of 100 to a value of 1000-10000 should increase the posting rate. This parameter only takes effect after stopping/starting the post process.
sp_ctrl> set param SP_OPO_READRELEASE_INTERVAL 1000
sp_ctrl> activate param
sp_ctrl> stop post
sp_ctrl> start post
As of shareplex 2.1.3.9.20 it is possible to run two cops on the same host with the same port number. The caveat is that ,these must be bound to different ethernet devices. This will only work if your machine has multiple nic's, since each cop will need to be bound to a different ethernet device.
On the target tar up the vardir and untar in different location.
Set the two environmental variables SP_SYS_HOST_NAME and SP_SYS_VARDIR to the correct settings and start each cop. Run ora_setup for each vardir (oracle users will need to be different).
A as of the current shareplex release, the post process is single threaded. Multiple cpu's don't provide increased performance. If it is possible to logically separate data that does not have referential integrity with other data, say an HR schema and an AP schema, running multiple vardir/cop/SP_SYS_HOST_NAME combinations will allow two or more independent posters to run. When using this scheme locally, ordering can't be assured.
-------------------------------------------------------------
Since the start of SharePlex 6, the Post is only multi-threaded.
