페이지 이력

This is how to guide for updating MagicInfo Server to V8 ( 20.1010.7) which is the latest at the moment (2020 Nov)

** If your current version is V4 or V6, you don't need to hop on V7 in order to end up V8. Just update straight to V8 from your version. 

** For lower version than V4004.8, please contact with your regional contact point. We recommend fresh installation of V8. 

DB Migration

책갈피
dbmigration dbmigration

WAS and DB is on separate machine

WAS will be updated using MagicINFO Server install package.

For DB update, you need to run the query or queries manually according to the MIS version.

This is how to guide for updating MagicInfo Server to V8 ( 20.1010.7) which is the latest at the moment (2020 Nov)

** If your current version is V4 or V6, you don't need to hop on V7 in order to end up V8. Just update straight to V8 from your version. 

** For lower version than V4004.8, please contact with your regional contact point. We recommend fresh installation of V8. 

DB Migration

책갈피
dbmigration dbmigration

WAS and DB is on separate machine

WAS will be updated using MagicINFO Server install package.

For DB update, you need to run the query or queries manually according to the MIS version.

See DB Manual Update section for more details.

WAS and DB is on Same machine

WAS and DB will be updated automatically by MagicINFO Server install package. Follow the below guide to update.

Step-by-step guide

1.Select the language of installation.

Image Added

2. Press the “Yes” button to continue the update.

Image Added

3.Press the “Yes” button. This process will check whether the MagicInfo Server and Server PC are ready to be updated or not.

Image Added

4. When everything is OK. Test result will be PASS.

Image Added

5. If status checking process Pass. It is good to continue updating.

Image Added

6. a) When there is a problem, Total Result is FAIL.

Image Added

6. b) Status Checking Process will show the Fail item and guide you to fix the issue.

Image Added

In case you face issue, mostly it will be related to DB only, so please check DB migration section.

*For other issues check trouble shooting section.

책갈피
#flywaytool #flywaytool

Running Flyway tool Manually

Flyway is an automatic DB migration tool.

This will run automatically when you install WAS and DB on the same machine,

but when you have error during DB upgrade this is how to check the log and re-run the migrate. 

**The version of official released MIS is first coming in SQL file's name, and if there is additional changes then the number comes after the next "." (ex. 4005.7.1) 

** If the original DB had problem on table so that the DB update failed during Flyway update, then we need to fix the problem on DB first and then re-execute updating using "migrate" command. ( The reason/problem line will be shown on flywaylog.txt)

** If upgraded to V8, only then you can see the Flyway folder at following path

[Install Directory]\MagicInfo Premium\flyway

Screenshot below shows SQL files for postgres when upgraded to V8

Image Added

To check whether DB upgrade is successful or not, Run the bat file using following command, it will show whether all scripts are executed properly or not:

(Below is the sample snapshot after running following command for upgrading v7 to v8)

mis.bat info 

Image Added

If update had failed, then that *.sql file's update state will be shown "Pending" and the excuted query before that line on that sql file will be REVERTED.

Meaning we need re-excute sql from which hadn't been applied. Updae state is also written in DB table (flyway_schema_history)

Run the following command to re-run the flyway:

mis.bat migrate

You can find the log & status on log file ([Install Directory]\MagicInfo Premium\flywaylog.txt) and db table (flyway_schema_history), check below snapshot. 

Image Added

if there is still an issue in flyaway execution then you need to update DB manually, see dbmanualupdate section. However after flyaway if you are doing manual updating then ,"flyway_schema_history" table has to be deleted totally (drop table) so that next version update won't have problem or stuck during updating

책갈피
#dbmanualupdate #dbmanualupdate

DB Manual Update

For updating DB manually, you need to run the query or queries manually according to the current MIS version to Upgraded version.

For queries check dbqueries Section and select the files according to the version and DB type (POSTGRES and MSSQL) 

There could be following scenarios.

Scenario 1: When WAS and DB is on separate machine, then you need to upgrade DB manually

Run the query files mentioned in dbqueries section one by one. Still if any issue check scenario 2.

Scenario 2: When WAS and DB is on same machine and DB did not update properly (DB tables/columns error) after upgrade MIS. (verify using WSRM.log files).

In this scenario customer need to run queries one by one from all related files as it seems some query are executed nd some are not, so running full file would not be helpful.

** while running queries one by one, you need to mind the insert queries as if they executed again they can create issue. Therefore before running the insert queries check the values in DB first.

Query Verification

For verification check the table in DB which you altered or updated to make sure query is executed properly.

For Postgres:

1. Open pgAdmin
2. Open MagicINFO DB > Schema > tables
3. If you have add some column A in table X then you can either use query tool and run query like (select A from table X) or check the same from pgAdmin UI.
   Image Added OR Image Added
   
   

For SQL Server (MSSQL):

1. Open SQL server Management studio
2. Open MagicINFO DB > Tables
3. Run Query or verify through UI.
    Image Added OR Image Added

책갈피
#troubleshooting #troubleshooting

Trouble Shooting 

Below are some points to check if upgrade fails:

1. Automatic update fails, check following log files (Path: [Install Directory]/MagicInfo Premium/)

• • MyInstallLog_20.1010.7.txt : update result file
     => [ERROR][MagicInfoServiceStop] stop MagicInfoPremium Service
    Meaning the mis service didn't stop. You have to stop the server, then update the server and "start" the service.
    
    
  • MISInformation.txt
    
    
  • verification.txt : result of "status checking process" before the actual update. 

 2. Maybe WAS/ DB were installed separately first, then DB has restored to same machine

Check the registry (Path will be Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Samsung\MagicInfo-i\Server\Premium) . See below snapshot for reference.

if bComplete ==1, means DB and WAS installed on same machine.

if bDBPostgresSQL ==1, means DB only installation

if bWAS ==1, means WAS only installation.

Image Added

if bWAS is set 1 , do the manual db update. And change to bComplete = 1 for next version update or remember to do manual db update next time. 

3. Web Author component failure

=> if this log appears on wsrm log, then do replace the web author client by following way:

1. Delete the folder "[Install Directory]\MagicInfo Premium\tomcat\webapps\MagicInfoWebAuthorClient"
2. Restart the MIS service.
3. If still issue exists then replace the [Install Directory]\MagicInfo Premium\webauthorMagicInfoWebAuthorClient.war with latest one according to MIS version, then repeat first 2 steps.

DB Queries.

책갈피
dbqueries dbqueries

These queries should be executed one - by - one in order

MIS Update DB Query (2020 Dec).zip

< Postgresql >

< MSSQL >