At times one intends to change the physical structure of the database, namely control files, online redo log files, archived redo log files and data files. The question arises as to whether Shareplex is impacted by such change.
Out of the files comprising the physical structure of Oracle, Shareplex is only affected by the change in location of online redo log files, archived redo log files. The Capture process of Shareplex needs to mine the data from online/archived redo logs. By default Shareplex will look for online/archive logs in directory as defined by the parameter LOG_ARCHIVE_DEST. If for any reason they are located in some other directory, then in the worst case scenario Capture will complain about log wrap and wait. At that point you can intervene and make the logs available for Capture, or, if you want Capture to read them from some other location, you can set the parameter SP_OCT_ARCH_LOC to point it to that location. (see solution # SOL4679 for further details). If such a situation occurs, you can always implement it on the fly. Other than this, Shareplex does not care about the physical structure of the database. So to implement the change, you can do the following:
1. Shutdown Shareplex.
2. Make the changes to the physical structure of the database
3. Restart Shareplex.
Assumption: It is assumed that there is no change to the location of ORACLE_HOME. If the change to the physical structure is also accompanied by the change to the ORACLE_HOME, then you need to implement the steps as outlined in the Admin Guide chapter 9 titled "Changing Oracle Characteristics of Replicated Objects" section "Moving the location of ORACLE_HOME on Unix systems".