Siebel Migration Application: Changes Not Reflecting Without Server Restart (Doc ID 2359601.1)

Last updated on APRIL 01, 2024

Applies to:

Goal

Qn1:1. We have tried Siebel Migration Application(SMA) for Deployment into Production Test Environment, Post completion we have changed the repository name from 'Migrated Repository' to 'Siebel Repository' and logged in with a new session in Application but changes were not reflected. We did full server restart then the changes were reflecting.

In IP17 guide no were it is mentioned for server restart, but the changes were not reflecting without server bounce. Do we need to do server restart for every migration or do we need to follow any other steps to avoid restarting the server everytime ?

Options Selected under SMA Plan for Migration :
Workspace Version
Schema Service
Runtime Repository Data Service
Application Workspace Data Service


2. For Incremental Runtime Repository Data Service and Incremental Application Workspace Data Service plan on SMA it will not ask for any workspace version to select, Clarity is required on what basis SMA will migrate the changes from Source to target? based on which version it will migrate, do we need to do server restart for this as well ?


3.We donot want to migrate certain tables like S_LST_OF_VAL for each migration plan, is there a way to exclude particular table's during migration ?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.