메타 데이터의 끝으로 건너뛰기
메타 데이터의 시작으로 이동

Content of this page is not relevant to MagicINFO Cloud


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 DB wasn't update properly or you want to update db seperately, 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.
     OR 

For SQL Server (MSSQL):

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


Trouble Shooting 

Below are some points to check if upgrade fails:


 1. 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.

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. 


2. Web Author component failure

org.apache.catalina.core.ContainerBase.startInternal A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MagicInfoWebAuthorClient]]



=> 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.

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


MIS Update DB Query (2021 Nov).zip


< Postgresql >

 Current Version

Sql files to update to Server 9

V4004.8

PSQL_4004.8_4005.7.sql

PSQL_4005.7_additional.sql

PSQL_4005.7_4100.0.sql

PSQL_4100.0_4101.8.sql

PSQL_3106.1_additional.sql

PSQL_4101.8_6000.0.sql

PSQL_6000.0_6001.0.sql

PSQL_6001.0_6002.0.sql

PSQL_6002.0_7000.0.sql

PSQL_7100.0_7990.0.sql

PSQL_7990.0_20.1000.0.sql

PSQL_20.1000.0_20.1010.0.sql

PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

V4005.7

PSQL_4005.7_4100.0.sql

PSQL_4100.0_4101.8.sql

PSQL_3106.1_additional.sql

PSQL_4101.8_6000.0.sql

PSQL_6000.0_6001.0.sql

PSQL_6001.0_6002.0.sql

PSQL_6002.0_7000.0.sql

PSQL_7100.0_7990.0.sql

PSQL_7990.0_20.1000.0.sql

PSQL_20.1000.0_20.1010.0.sql

PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

V4101.8

PSQL_4101.8_6000.0.sql

PSQL_6000.0_6001.0.sql

PSQL_6001.0_6002.0.sql

PSQL_6002.0_7000.0.sql

PSQL_7100.0_7990.0.sql

PSQL_7990.0_20.1000.0.sql

PSQL_20.1000.0_20.1010.0.sql

PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

 v6000

PSQL_6000.0_6001.0.sql

PSQL_6001.0_6002.0.sql

PSQL_6002.0_7000.0.sql

PSQL_7100.0_7990.0.sql

PSQL_7990.0_20.1000.0.sql

PSQL_20.1000.0_20.1010.0.sql

PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

 v6001

PSQL_6001.0_6002.0.sql

PSQL_6002.0_7000.0.sql

PSQL_7100.0_7990.0.sql

PSQL_7990.0_20.1000.0.sql

PSQL_20.1000.0_20.1010.0.sql

PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

 v6002

PSQL_6002.0_7000.0.sql

PSQL_7100.0_7990.0.sql

PSQL_7990.0_20.1000.0.sql

PSQL_20.1000.0_20.1010.0.sql

PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

 v7100.2

PSQL_7100.0_7990.0.sql

PSQL_7990.0_20.1000.0.sql

PSQL_20.1000.0_20.1010.0.sql

PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

 V8 First Release(20.1000.14)

PSQL_20.1000.0_20.1010.0.sql

PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

V8 Update Release(20.1010.7,

20.1010.10)


PSQL_20.1010.0_21.1000.0.sql

PSQL_21.1000.0_21.1010.0.sql

V9 Release(21.1000.3)

PSQL_21.1000.0_21.1010.0.sql


< MSSQL > 

 Current Version

Sql files to update to Server 9

V4004.8

MSSQL_4004.8_4005.7.sql

MSSQL_4005.7_additional.sql

MSSQL_4005.7_4100.0.sql

MSSQL_4100.0_4101.8.sql

MSSQL_3106.1_additional.sql

MSSQL_4101.8_6000.0.sql

MSSQL_6000.0_6001.0.sql

MSSQL_6001.0_6002.0.sql

MSSQL_6002.0_7000.0.sql

MSSQL_7100.0_7990.0.sql

MSSQL_7990.0_20.1000.0.sql

MSSQL_20.1000.0_20.1010.0.sql

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

V4005.7

MSSQL_4005.7_4100.0.sql

MSSQL_4100.0_4101.8.sql

MSSQL_3106.1_additional.sql

MSSQL_4101.8_6000.0.sql

MSSQL_6000.0_6001.0.sql

MSSQL_6001.0_6002.0.sql

MSSQL_6002.0_7000.0.sql

MSSQL_7100.0_7990.0.sql

MSSQL_7990.0_20.1000.0.sql

MSSQL_20.1000.0_20.1010.0.sql

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

V4101.8

MSSQL_4101.8_6000.0.sql

MSSQL_6000.0_6001.0.sql

MSSQL_6001.0_6002.0.sql

MSSQL_6002.0_7000.0.sql

MSSQL_7100.0_7990.0.sql

MSSQL_7990.0_20.1000.0.sql

MSSQL_20.1000.0_20.1010.0.sql

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

 v6000

MSSQL_6000.0_6001.0.sql

MSSQL_6001.0_6002.0.sql

MSSQL_6002.0_7000.0.sql

MSSQL_7100.0_7990.0.sql

MSSQL_7990.0_20.1000.0.sql

MSSQL_20.1000.0_20.1010.0.sql

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

 v6001

MSSQL_6001.0_6002.0.sql

MSSQL_6002.0_7000.0.sql

MSSQL_7100.0_7990.0.sql

MSSQL_7990.0_20.1000.0.sql

MSSQL_20.1000.0_20.1010.0.sql

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

 v6002

MSSQL_6002.0_7000.0.sql

MSSQL_7100.0_7990.0.sql

MSSQL_7990.0_20.1000.0.sql

MSSQL_20.1000.0_20.1010.0.sql

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

 v7100

MSSQL_7100.0_7990.0.sql

MSSQL_7990.0_20.1000.0.sql

MSSQL_20.1000.0_20.1010.0.sql

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

 V8 First Release(20.1000.14)

 MSSQL_20.1000.0_20.1010.0.sql

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

V8 Update Release(20.1010.7,

20.1010.10)

MSSQL_20.1010.0_21.1000.0.sql

MSSQL_21.1000.0_21.1010.0.sql

V9 Release(20.1000.3)

MSSQL_21.1000.0_21.1010.0.sql