1. Preparing the base for migration

- Make a cold backup (with stopped services) of the root folder of Protheus (Ex.: C:\TOTVS 12) and Database

2. Checking the duplicity in the base

- If your Data Base is Relational (use DBACCESS), you must run the verification process of duplicated 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:

http://tdn.totvs.com/pages/viewpage.action?pageId=271415266

Create in Protheus_Data folder, the MIGRATION folder, then unzip the full data dictionary of the release you want to migrate. In the verification of duplicity, the SX2.UNQ is requested, use this as reference for verification.

- See Instructions for the verification of duplicities in the link:

http://tdn.totvs.com/pages/viewpage.action?pageId=242386686

3. Updating files

Updating data dictionary files (Full and Differential) of the release version you want to update, and also the RPO (Repository of Objects) of the same version.

- To update dictionary, follow the procedure below:

http://tdn.totvs.com/pages/viewpage.action?pageId=271415266

- To update the RPO, follow the procedure below:

- Access the Support site:

https://suporte.totvs.com/download

.

Protheus line . MICROSIGA PROTHEUS VERSÃO 12.1.XX (where XX is the version of the new release) .

PROTHEUS 12 TOPCONNECT PORTUGUES .

Category: Repository of objects.

Download the repository for Brazil (BRA-EUA-PAR-URU-TTTP120) UPDATE:

Stop Protheus service.

In APO folder, rename the previous repository, or move to other folder.

Copy the new file for the APO directory of the system .

Rename file keeping only the last 7 characters (Example: tttp120.rpo)

Note: after switching the RPO, update the LIB, downloading and applying the most recent one of the Portal.

Link with updating procedures:

http://tdn.totvs.com/pages/viewpage.action?pageId=271651871

Information:
If you use the Appserver in Linux, transfer zipped file for Linux, and only unzip it in Linux. Unzip file in Windows, then transfer .txt for Linux may cause errors.

Note:
When preparing environment for migration, it is not recommendable to open Protheus after updating the files, but run the compatibility program (UPDDISTR)

4. Cleaning Folders

Delete files *.DBF e *.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

5. Executing the compatibility program of release migration

- Open the Smartclient, and in the Initial Program, enter: UPDDISTR

* Further details on the functionality of UPDDISTR may be found in this link: Dictionary and database updater - UPDDISTR

Image Modified

Select the company(ies) to migrate the Release, then click OK.

Image Modified
After selecting company(ies), a screen with recommendations of backup and free space. Click Next.

Image Modified
Then, the screens of the Acceptance Term which is necessary to proceed with the process. Read carefully, select the acceptances, and go ahead.

Image Modified
Image Modified
Image Modified
Image Modified
Image Modified
On the following screen, enter the Admin password, then click Next.

Image Modified

Then, the standard option for the Data Directory and the folder \DATA. Click Next.

Image Modified

On the Configuration screen, it is recommendable to select only the options required and the option Correct errors automatically. Click Next then Next again.

Image Modified

-The migration starts.

- If the updating has errors, a window displays the errors log, which must be corrected in the base before continuing. Below see the link with the corrections of the most common migrations:

http://tdn.totvs.com/pages/viewpage.action?pageId=271414000

- If error is not listed, open a ticket for the Framework Support through the Customer Portal.

- At the end of the migration, a window with the this information "The updating process was successfully finalized." is displayed.

Image Modified

To confirm, access the Configuration, press Shift+F6, then check the "RPO Release"

Image Modified