In Shareplex documentation you will find reference to the terms "9i DDL" or "9i Supported DDL". These terms are used interchangeably and are one in the same thing. What exactly are these DDLs and do they only work for Oracle 9i?
Prior to Shareplex 5.1, only the DDLs on replicating tables were replicated subject to setting of SP_OCT_REPLICATE_DDL to a value of 1, 2 or 3. With the advent of Shareplex 5.1, a new feature came into existence whereby it is possible to replicate DDL on all objects whereby it is possible to replicate DDL on all objects which are not replicating objects. This is subject to restrictions that the source and target database be identical in structure. Also, this feature only works for Oracle 9i and up (hence the use of the terms "9i DDL" or "9i Supported DDL"). Since the feature is not restricted to Oracle 9i, it is a bit of a misnomer. Another thing to note is that not all DDLs on all objects may be replicated and there is a list of supported DDL in the Release Notes. See section " Supported operations and objects for DDL replication”. Also, one needs to set the Capture parameter SP_OCT_REPLICATE_ALL_DDL to 1 to enable the 9i DDL replication. The parameter is off (value 0) by default for obvious reasons. Not many sites use this feature. If one is replicating all DDLs, the source and target need to have identical structures in terms of objects, storage characteristics, users etc. Not having these can result in DDLs failing on target and causing Post to be shutdown, whereby requiring intervention from customer or Support to get rid of the offending DDL. As an example, if the source database has a user A and the target did not had it to begin with, then the DDL "ALTER USER A IDENTIFIED BY XXX" will succeed on source database but the statement will fail to execute on target requiring manual intervention. There is a parameter SP_OPO_STOP_ON_DDL_ERR that can be set to 0 as a workaround to let Shareplex on target ignore DDL errors but this will result in all subsequent DDL errors ignored which is something one may not want. In certain situations the 9i DDL may be useful. For instance, if one has identical primary and secondary databases and would like to failover to the secondary with the least amount of steps, then the feature may be useful in maintaining an identical copy of primary at secondary site to enable this switch. This may be subject to certain restrictions. For instance not all available DDL fall under the category of 9i DDL, so differences can still crop up from the time the two were identical and the replication was set up with 9i DDL enabled.
The “9i DDL” or “9i Supported DDL” are now termed as “expanded DDL support” to reflect the fact that they were never tied to an Oracle version but rather, SharePlex started supporting such DDL on non-replicating objects starting with SharePlex versions compatible with Oracle 9i and up.
Please also see SOL281 for more information.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center