Today, a 32-bit Linux is installed on a server with a blade failure, a 32-bit Oracle is installed on it, and the physical replica uard of a 64-bit Oracle is successfully configured. Same bit
Today, a 32-bit Linux is installed on a server with a blade failure, and a 32-bit Oracle is installed on it, the physical data guard of a 64-bit Oracle instance is successfully configured. Same bit
Today, a 32-bit Linux is installed on a server with a blade failure, and a 32-bit Oracle is installed on it, the physical data guard of a 64-bit Oracle instance is successfully configured. The same-digit data guard configurations of the same version can be found on the Internet in countless textbooks, but the dg configurations between Oracle with different digits have hardly been discussed, however, our new servers are all 64-bit systems, and the eliminated servers are all 32-bit. If this test succeeds, these servers can still be used. The configuration installation process is actually the same as the original one, but when the switch is over, you need to perform several checks according to the metalink prompt. If you are free, sort and release it.
In addition, many backup tools have better support for Windows, while Linux is much worse. I have tried several tools, including the backup for the entire Linux system, restoring to vmware fails. There are still several old systems with RedHat 7.2 installed. The services configured above are relatively old and there is no documentation. It is troublesome to reinstall the system. If you can migrate the backup, in the future, the management workload will be lower. I found a document on the internet today and provided another manual backup method. I can try it if I have time.