FN19497 - Revision history

Lucas Trottier: moved FN:19497 to FN19497: Remove colon

2016-07-06T15:36:18Z

moved FN:19497 to FN19497: Remove colon

2016-07-06T15:30:46Z

2016-07-06T15:29:07Z

2016-07-05T22:13:01Z

2016-07-05T22:10:15Z

2016-07-05T22:09:01Z

2016-07-05T22:07:41Z

2016-06-15T18:26:19Z

2016-06-15T18:25:23Z

2016-06-15T18:24:35Z

@@ Line 81: / Line 81: @@
 For example, lets say your database was recovered from a 2.9 system on a 2.7 system and you upgraded to the software release 2.8. After you activated the package 2.8, the system would report a failure and fall back on 2.7 (if running 2.7.148 onward). Here is the steps you should follow:
 . Recover from a valid 2.7 database backup or a previous release backup. Skip to steps 4a or 4b.
@@ Line 86: / Line 87: @@
 If for some reason you can't recover a valid database, erase the databases to force the system to create new ones:
 . ssh to your TMG host
 . Drop the 2.7 database (toolpack_0) and the 2.8 database (toolpack_2_8):
@@ Line 94: / Line 97: @@
    # mysql -u tbdb -ptbdbpw -e "drop database toolpack_0;"
    # mysql -u tbdb -ptbdbpw -e "drop database toolpack_2_8;"
 a. If you '''upgrade from a release previous to 2.7.148''', you must follow the instruction below:
@@ Line 109: / Line 113: @@
 Restart toolpack
    # tbtoolpack start
 b. If you upgrade from a release supporting major release upgrade from the web ('''2.7.148 and above'''), you must follow the instruction below:

@@ Line 11: / Line 11: @@
 * Validate/Recover the database backup (validation and recover would be performed)
-==How to validate your system database==
+==System database backup recover ==
 Each time a database backup is recovered, the system proceed to the following actions:
 * perform an automatic backup of the actual database (under Backups->Automatic database backups)
@@ Line 17: / Line 17: @@
 * proceed to the database data upgrade to match the actual system's version
 {| class="wikitable"
 |-

← Older revision		Revision as of 22:10, 5 July 2016
Line 1:		Line 1:
−	{{DISPLAYTITLE:FN19497 - Major upgrade failure ~~on system running~~ with a database data updated from a newer release}}	+	{{DISPLAYTITLE:FN19497 - Major upgrade failure with a database having data updated from a newer release}}

	= Affected Products =		= Affected Products =

← Older revision		Revision as of 22:09, 5 July 2016
Line 1:		Line 1:
−	{{DISPLAYTITLE:FN19497 - Major ~~Upgrade~~ failure on system running with a database from newer ~~Version~~}}	+	{{DISPLAYTITLE:FN19497 - Major upgrade failure on system running with a database data updated from a newer release}}

	= Affected Products =		= Affected Products =

@@ Line 34: / Line 34: @@
    mysql> drop database toolpack_0;
-   mysql> drop database toolpack_2_9;
+   mysql> drop database toolpack_2_x;
 - Check the config files to make sure it is pointing to the new release.

@@ Line 41: / Line 41: @@
    Make sure it the applicaiton path is:
    application= /mnt/.0/tb/toolpack/setup/12358/2.9/apps/tboamapp/tboamapp_wd_cfg.ini
    vi /mnt/.0/tb/toolpack/setup/12358/2.9/apps/tboamapp/tboamapp_wd_cfg.ini
    Make sure package path is 2.9.41
@@ Line 47: / Line 46: @@
 - Manually start toolpack on the newer release
-[root@TB007036 ~]# tbtoolpack start
+  [root@TB007036 ~]# tbtoolpack start
 :tbtoolpack_12358
    Starting tbtoolpack_12358:                                 [  OK  ]
    Toolpack current state: Ready
    Ok