Manage Your Implementation
Managing your implementation to ensure an optimal experience includes troubleshooting issues and following recommended best practices.
Troubleshoot Issues
After migration, you might need to troubleshoot certain issues you could encounter. Here are some common issues and proven solutions:
Logging in by using database credentials fails in Siebel Management Console.
| Problem | After the VM is migrated and the necessary
etc/hosts file changes are done, accessing SMC with
the database credentials can fail.
|
| Possible Cause | The database hostname has changed, and the Gateway is still trying to connect to the database using the old hostname. |
| Solution | Remove and recreate the Siebel Gateway Security Profile. Refer to MOS Doc ID 2371577.1 (see Explore More for the appropriate link). This is also mentioned as a step under the Siebel VM Post Migration Tasks. |
You are unable to edit the etc\hosts file
| Problem | While editing the hosts file, you receive a permission error. |
| Possible Cause | You lack privileges to save the file in that location. |
| Solution | Copy the file to a location, for example a desktop where
the user has permission to save and edit files. Edit and save the file. Copy
and paste the file in etc folder, replacing the
existing hosts file.
|
Siebel Server is not getting removed from SMC
| Problem | As part of undeploying the profiles, the Siebel server also needs to be removed, but sometimes the process takes some time and doesn’t actually removing it. |
| Possible Cause | The backend task fails and doesn’t remove the Siebel server from the zookeeper configuration. |
| Solution | Follow MOS Note ID 2590232.1 (see Explore More for the appropriate link) and remove the Siebel server directly from the zookeeper. |
Instance not booting up with the custom image.
| Problem | The instance created from the custom image doesn’t boot up. |
| Possible Causes | A source image requirement might have been missed or
incorrectly set up.
Ensure your custom image meets all the source image requirements, as per the official documentation. |
| Solution | Troubleshoot instances by using Instance Console Connections. |
Follow Best Practices
For an optimal migration experience, you should follow these best practices when implementing this procedure.
- Before commencing the migration, gather all the details about the on-premises deployment like the user credentials, Siebel binaries’ path, custom components, parameters, etc.
- Identify all areas that require new hostname changes, like Symbolic URL Administration, Webservice endpoints, List of Values, Email Response Groups, Communication Drivers and Profiles, and so on.
- Avoid file write issues by launching the Siebel update wizard with administrator privileges.
- Although you disable User Access Control when you begin this process, re-enable it when you finish.
- Recreate ODBC data sources by using the new Oracle database client that you previously created by using the old version.
- Avoid removing the Siebel Services, Siebel Gateway, and Tomcat services by using the system command line. This technique doesn’t remove the corresponding entries from the properties files. Instead, log in to SMC and gracefully remove all deployed profiles one by one.
- Ensure to review the PostInstallDBSetup logs to ensure that the repository and database level changes were applied correctly and without any errors.
- While migrating a multi-server environment, ensure that all the servers can communicate with each other via the relevant ports. Create Network Security Groups (NSG) or enable the ports at the subnet level.
- Use Oracle Cloud Infrastructure File Storage Service for Siebel File System.
- You only need to undeploy and redeploy the profiles in SMC when the hostnames changes.