How does the Migration Workbench implement the migration of global variables?
The Migration Workbench creates equivalent functions in the destination Oracle database for global variables that are specific to stored procedures, for example the @@ROWCOUNT variable. The equivalent function is then called by the stored procedure. Currently, the Migration Workbench includes the @@IDENTITY and @@TRANCOUNT variables into the omwb_emulation package. However, you can add additional global variables after migration. For variables such as @@TRANCOUNT and @@IDENTITY, the Migration Workbench does the following: The Migration Workbench creates a new user called omwb_emulation with the password oracle in the destination Oracle database. Inserts an invoker-rights package into the database within the new user schema. Note: Unlike definer-rights routines, invoker-rights routines are not bound to a particular schema. A variety of users can run them. For more information, see the PL/SQL User’s Guide and Reference. Executes the database privilege Grant execute to public on the invok
