1. PREPARING THE CURRENT VERSION FOR MIGRATION

Prepare a test base, making a cold backup (all services stopped) and consistent (of appropriate folders and database) of production base.

If your Data Base is Relational (use DBACCESS), you must run the verification process of doubled records for all companies. Wizard executed from CHECKDUPL routine via Configurator, which has the updating of the standard data dictionary in the SYSTEMLOAD as a requirement. To download the dictionary, follow the procedures of this link:

Update Protheus 12 Data Dictionary

Create in the Protheus_Data folder, the MIGRATION folder, and unzip the Full data dictionary of version 12. In the verification of duplicity the SX2.UNQ, use version 12 as reference for verification.

See Instructions for the verification of duplicity in the link: CHECKDUPL

Uninstall as Stored Procedures through the Configurator by the current version. Remember that such procedure must be executed along with DBA responsible for the database, as it has customizations in the Stored Procedures, and if it is the case, the DBA can make the backup to reapply such customizations after the migration for version 12. If you have questions on the uninstalling/installing of Stored Procedures, open a new ticket with the Framework team.

2. INSTALLATION OF PROTHEUS 12

Link for the Installation Form of Protheus 12:

Protheus 12 Installation Form

- Install Protheus 12

- Configure files appserver.ini (Server) and smartclient.ini (Client);

- Update the binary of the system (APPSERVER, SMARTCLIENT and SMARTCLIENTACTIVEX);

- Unzip content of folder ace_8.00 (only the ACE_8.00) in the folder bin\appserver_x32 of the base;

3. UPDATING THE SYSTEM AND DATA DICTIONARY

Update Binary, RPO, LIB, Dbaccess and Accrual Package of Protheus 12

Procedure of updating in the link:

Basic updating of Protheus 12

Update files of the Data Dictionary (sxsbra.txt) and Field Help in the Systemload

Procedure of updating in the link:

Data Dictionary:

Update Protheus 12 Data Dictionary

Fields Help:

Update the Field Help

4. UPDATING DATABASE

Copy content of folders SYSTEM, DATA and PROFILE of Protheus system (Current version) to their respective folders of the Protheus 12 system;

Copy folder of the existing Knowledge Base in Protheus installation (Current version) to inside protheus_data of Protheus 12 system; Note: As default, the name of the folder dirdoc is saved in Protheus_data, if you use parameter MV_DIRDOC to save in other directory, query its content and copy folder of the path indicated.

Check whether space available in the server hosting the database of Protheus 12 system is, at least, 3 times greater than the size of the database of Protheus system (Current version).

5. CLEANING FOLDERS

Delete files *.DBF

and *.DTC of SYSTEMLOAD folder

Delete files *.IDX of folder SYSTEMLOAD

Delete files *.LOG of folder SYSTEM - Delete files TOTVSP.** of folder SYSTEM

Delete files *.TSK and .LOG of folder APPSERVER_X32

6. EXECUTING COMPATIBILITY PROGRAM OF MIGRATION

• In Smartclient of version 12, execute in Initial Program: MP710TO120

Image Modified

• Click Next. Add password of Admin, the press TAB

Image Modified

• A window is displayed, questioning to which version the migration to version 12 is made. Select version, then click OK
  
  
  Image Modified
  
  
• It is recommendable to keep option Overwrite initializer selected Note: if you manually created a standard initializer, in a field without standard initializer, and now this field has a standard initializer, what was manually created is overwritten
• Click Next

• On the screen Data Dictionary, click Next

Image Modified

• In Update Execution Setup, we recommend that you keep only the Critical Error Log and the Fix Errors automatically options enabled, keeping in mind that the option to fix the errors automatically will apply the base changes by the system itself.

• NO select the Keep the existing log file option

Image Modified

• Click Next / Next
• Wait process of compatibility program. If during the process, critical errors that cannot be automatically adjusted arise, they must be MANUALLY adjusted, using as base the Critical Errors link (below), or inquiring the Support if the error is not listed
  
  7. UPDATING THE MENUS OF MODULES
  To download files, access:

• 
  Customer Portal:

• http://suporte.totvs.com

• 
  
  Menu Downloads and Updating

• 
  
  Protheus Line

• 
  
  Microsiga Protheus Version 12.112.1.XX (where XX is the Release version)

• 
  
  All - Category: Module menu

• 
  Download file MENUS - BRASIL 12.1.XX
  
  Note: if versions are not being displayed, in "Filters of packages", select "All packages available", then select the category again.
  
  To update it:
  - Stop Protheus (Appserver) server
  - Backup files .xnu of \Protheus_Data\system folder
  - Remove all menu files of folder system (.xnu).
  - Copy .xnu files downloaded from the portal for this folder.
  - Restart Protheus (Appserver) server
  
  Remember the customized menus need to be redone, as there are routines of version 11 that do not exist in the RPO of the version 12.
  
  CRITICAL ERRORS
  In case of critical error, the customer must execute the proper adjustments, then run routine MP710TO120 again. Link with adjustment of the most common critical errors:
  Most common critical errors in migrations[