![]() The following was run on both test instances: If you are not already using ER, you will also need to create two new dbspaces that it needs on both source and target servers, and update configuration parameters accordingly. You will most likely want full control over sizes and names of chunks, particularly when using raw devices rather than file system chunks (“cooked” files). ![]() We have already assumed that in this article, and prerequisite 1 above is therefore not relevant. In a real scenario, dbspaces on the target server – which must have the same names as in the original instance – are likely to be more precisely tailored to your preferences and infrastructure if created manually. Source server must be 11.70xC1 or higher version.Trusted host configuration must be already established between source and target servers.SQLHOSTS files at both source and target server must be already configured with ER group information. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |