Changing the Configuration of Stopping the Oracle Cluster

Modify configuration items using scripts when Agent configuration stops the Oracle database, you can determine whether to stop the Oracle cluster.

sh checkcfg.sh write {0|1}

0: Not to stop the Oracle cluster in Agent Configuration.

1: Stop the Oracle cluster in Agent Configuration.

Use PuTTY to log in as user root to the application server where the eReplication Agent is installed.
Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.

After you run the preceding command, the system continues to run even when no operation is performed, resulting in security risks. For security purposes, you are advised to run the exit command to exit the system after completing your operations.
Run the su - rdadmin command to switch to user root.
Run the cd /home/rdadmin/Agent/sbin command to go to the script save path.
Run the following command to stop or not to stop the Oracle cluster when the Oracle database is stopped in Agent Configuration:

When modifying configuration items, you need to perform this operation on all nodes in the Oracle cluster to ensure that the configurations on all nodes are the same.
- Run the sh checkcfg.sh write 1 command to stop the Oracle cluster in Agent Configuration. The following information is displayed:
```
Writing the value of the configuration item of RAC to 1 is successful.
```
- Run the sh checkcfg.sh write 0 command not to stop the Oracle cluster in Agent Configuration. The following information is displayed:
```
Writing the value of the configuration item of RAC to 0 is successful.
```

linux87:/home/rdadmin/Agent/sbin/sh checkcfg.sh write 1 
Writing the value of the configuration item of RAC to 1 is successful.