1 / 22

Planning a Migration

Planning a Migration. Overview. Migration Methods Migration Roadmap Migrating Siebel Data Post Migration Issues Migration Tools. Lesson: Migration Methods. Single Step Migration (Not Supported) Two Step Migration/ Upgrade. Single Step Migration (Not Supported). Siebel 7.x Build 3701

pricks
Download Presentation

Planning a Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Planning a Migration

  2. Overview • Migration Methods • Migration Roadmap • Migrating Siebel Data • Post Migration Issues • Migration Tools

  3. Lesson: Migration Methods • Single Step Migration (Not Supported) • Two Step Migration/ Upgrade

  4. Single Step Migration (Not Supported) Siebel 7.x Build 3701 Oracle 10 Siebel 8.x Build 16177 SQL Server 2008 • Large Effort to Perform Manual Mapping for Schema Changes • Tables added, merged, split, in-activated, renamed • Columns added, renamed, deleted, moved to other tables • Likelihood of Making Mapping Errors Very High

  5. Two Step Migration/ Upgrade Siebel 7.x Build 3701 Oracle 10 Siebel 8.x Build 16177 Oracle 11 Siebel 7.x Build 3701 SQL Server 2005 Siebel 8.x Build 16177 SQL Server 2008

  6. Lesson: Migration Roadmap

  7. Lesson: Migrating Siebel Data • Migrating Repository Data • Migrating all Non-Repository Data • Process of Migrating all Non-Repository Data • Migrating User Names / Passwords (Manual Process) • Indexes

  8. Migrating Repository Data • Database Configuration Utility in Siebel 7.7 • Versions prior to Siebel 7.7 utilized utilities: • Exprep, imprep • Migrate only when repository changes are frozen

  9. Migrating all Non-Repository Data • Migrate Seed and Customer Data as one • Insure Siebel Logging, Audit Trail, Triggers are disabled • Migration Tools • Dataexp / Dataimp (Slow but can run concurrent streams) [31 hours for 120 GB in serial migration] • Insert / Select SQL [13 hours for 80 GB in serial migration] • EIM (Does not retain Siebel row IDs) • Consider Vendor Tools on very large tables • BCP • Bulk Loader

  10. Process of Migrating all Non-Repository Data • Build the SQL Server environment, configure SQL Server parameters, create the Siebel database (INSTALL.KSH), but don’t install the default Repository • Import customized Repository to SQL Server database and apply any schema extensions (DEV2PROD) • Export data using 1+ DATAEXP process(es) from existing Siebel database for all non-Repository Tables, including EIM, LOVs, Users, etc. • Truncate all non-Repository Tables in SQL Server Siebel database (remove the default seed data) • Import data from DATAEXP process(es) to SQL Server Siebel database using DATAIMP • Audit row counts between DATAEXP and DATAIMP • Collect statistics on SQL Server Siebel Tables • Reconfigure Siebel Server and Client .CFG files to use SQL Server Siebel database • Test • Celebrate!

  11. Migrating Usernames and Passwords (Manual Process) • Siebel Logins in S_EMPLOYEE (v6.x) or S_USER (v7.x) are migrated with the process, but not Passwords • Passwords are never stored in the Siebel Tables • Typically use a Database UserID, Windows Active Directory, or some other LDAP solution • Requires additional work if moving from Oracle UserID to any other authentication solution • Likely requires changing Password for each UserID if moving from Oracle UserID to any other authentication solution

  12. Indexes • Unique indexes should be in place to enforce uniqueness • No demonstrated advantage to building non-unique indexes after the loads • Review low-cardinality Indexes after loading all data (Information on Index scripts can be found on Technote 6 and 16 on the Student CD)

  13. Lesson: Post Migration Issues • General Guidelines • Testing • Tuning

  14. General Guidelines • Keep catalog statistics current so Optimizer can do it’s job

  15. Testing • Execute multiple dry runs to debug the process • Regression testing to ensure functionality has not changed • Perform load and stress testing based on real live environments • Test performance under load by using tools such as Load Runner

  16. Tuning • Tuning will be needed • How much tuning was done for current implementation? • Oracle uses rule based optimizer • SQL Server uses cost based optimizer • Perform stress testing with full sized database and expected full workload • Avoid having test data fully cached when stress testing – Mimic real production - Do a full tablespace scan on a key table every minute to flush bufferpools

  17. Lesson: Migration Tools • Services for UNIX (SFU) • SQL Server Migration Assistant (SSMA)

  18. Microsoft's Solution - Services for UNIX • Services for UNIX v. 3.5 provides the tools and environment that IT professionals and developers need to: • Integrate Windows and UNIX/Linux environments • Migrate UNIX applications to Windows • Services for UNIX is one of the most comprehensive interoperability solutions: • Directory, File System and UNIX Subsystem • Tested and supported by Microsoft • Services for UNIX uniquely enables IT pros to easily extend the value of their knowledge and training

  19. UNIXFiles Windows Files UNIXFolders SQL ServerDatabase UNIXDatabase UNIXServer Windows Server PC Laptop Windows Services for UNIX UNIXApplication WindowsApplication Windows Folders UNIXWorkstation UNIXWorkstation

  20. SSMA

  21. SSMA PL/SQL to T-SQL

  22. Review • Migration Methods • Migration Roadmap • Migrating Siebel Data • Post Migration Issues • Migration Tools

More Related