Forums

by Didier >> Sat, 24 Mar 2007 6:30:27 GMT

Hi,
When we updated user's live system from Jade6.0.21( rhel3 ) to Jade6.1.09( rhel3 )
We got the following message :

WARNING: Found existing deployment system at '/home/jade/deploy'
WARNING: The installation and upgrade scripts no longer support installing WARNING: or upgrading of deployment systems. You are free to continue WARNING: using this configuration, but you will need to upgrade the deployment system listed above manually. Please refer to the file 'ReadmeInstallSteps.txt' in the document

Is the warning serious ? what area will be effected ?
Where can i download the file ReadmeInstallSteps.txt ?
What should we do next ?

Didier
2007.3.24

by Martyn Leadley >> Sun, 25 Mar 2007 22:01:51 GMT

Hi,

In Jade 6.0 there where two databases that could be installed. The "system" one that contained a full development environment, so that you could develop systems. The other was the "deploy" database that only allowed running of the developed system.

Jade version 6.0 on Linux (rhel3 and sles9) allowed both of these databases to be installed at the same time. With in the 6.0 release
both databases would be upgraded as necessary if you moved from 6.0.20
to 6.0.21 etc. Now with Jade 6.1 only the "system" database is shipped.

This warning indicates that the upgrade from 6.0 to 6.1 only upgraded
the system database, and that it has also discovered the existence of
the deploy database.

If you can connect to your live database and run the Jade development environment (or the path= parameter points at the system directory) then you are almost certain to be running with the system database.

If your site is using the deploy database, then you must upgrade this database manually. However if you are certain that you are not using
the deploy database then it is not needed and may be removed (first
doing a backup is always recommended).

The ReadmeInstallSteps.txt is released on the Windows CD, and the steps are Windows specific. If you are using the deploy database please get
in touch with Jade support.


Martyn

by Didier >> Tue, 27 Mar 2007 6:14:21 GMT

Hi,
We copy the live system to my pc to test upgrade.
we can upgrade the system in my pc.

but we can not upgrade the same system in user's server .
I wonder if it's becoz their server is a 64bit one... would it affect?

note:the bin Upgraded in User's server can be used in my PC.

Appreciated for any help.
YGZ
2007.3.27


Here attached fragment of jommsg.log file
when we startup jade server ============================================================================================================= ........
2007/03/27 00:05:23.498 058e4-40fb2bb0 Jom: Local process delete 0x815a818: no=1, id=1093905328, type=0 (non-prodn), scm=RootSchema, app=RootSchemaApp, elapsed time=00:15:15.236
2007/03/27 00:05:23.498 058e4-411f6bb0 PDB: EOT <Database Worker> 2007/03/27 00:05:23.689 058e4-410d4bb0 PDB: EOT <Buffer Overlay> 2007/03/27 00:05:23.689 058e4-410f5bb0 PDB: EOT <Bg Flush>
2007/03/27 00:05:24.683 058e4-40fb2bb0 PDB: Database closed successfully 2007/03/27 00:05:24.900 058e4-40fb2bb0 JomLog: Persistent NoteMgr : sys hits=0, sys misses=0, sys skips=5
2007/03/27 00:05:24.922 058e4-40fb2bb0 JomLog: Persistent NoteMgr : usr hits=0, usr misses=0, usr skips=0
2007/03/27 00:05:24.946 058e4-40fb2bb0 JomLog: Transient NoteMgr : sys hits=0, sys misses=0, sys skips=0
2007/03/27 00:05:24.974 058e4-40fb2bb0 JomLog: Transient NoteMgr : usr hits=0, usr misses=0, usr skips=0
2007/03/27 00:05:24.998 058e4-40fb2bb0 JomLog: Transient NoteMgr : sys hits=0, sys misses=0, sys skips=0
2007/03/27 00:05:25.022 058e4-40fb2bb0 JomLog: Transient NoteMgr : usr hits=0, usr misses=0, usr skips=0
2007/03/27 00:05:25.540 058e4-40bb9c80 E8-BRM: (jaded) Finished: exit code 0 2007/03/27 00:06:37.129 05fbb-40fb2bb0 E8-BRM: (jaded) Version 6.1.9 - ANSI, OS Version: Linux 2.4.21-40.EL
2007/03/27 00:06:37.129 05fbb-40fb2bb0 E8-BRM: Invocation: jaded ini=/home/jade/jade.ini path=/home/jade/deploy path=/home/test/system ini=/home/test/jade.ini
2007/03/27 00:06:37.128 05fbb-40fb2bb0 PDB: Database initialising with jomdb version: 6.1.9.5, ini=/home/test/jade.ini
2007/03/27 00:06:37.130 05fbb-40fb2bb0 PDB: System file directory: /home/jade/runtime/
2007/03/27 00:06:37.131 05fbb-410d4bb0 PDB: BOT <Buffer Overlay> 2007/03/27 00:06:37.131 05fbb-410f5bb0 PDB: BOT <Bg Flush>
2007/03/27 00:06:37.131 05fbb-411f6bb0 PDB: BOT <Database Worker> 2007/03/27 00:06:37.132 05fbb-40fb2bb0 PDB: <<INFO>> Retrying out of resource errors is enabled
2007/03/27 00:06:37.132 05fbb-40fb2bb0 PDB: <<INFO>> Retry delay = 1000ms, retry limit = 0
2007/03/27 00:06:37.167 05fbb-4133abb0 PDB: ************************************************************************************************ 2007/03/27 00:06:37.167 05fbb-4133abb0 PDB: <<WARNING>> Transaction journal directory /home/test/system/journals/current/ is located on the same volume as your Database
2007/03/27 00:06:37.167 05fbb-4133abb0 PDB: Database performance compromised; audit I/O will compete with database I/O
2007/03/27 00:06:37.167 05fbb-4133abb0 PDB: ************************************************************************************************ 2007/03/27 00:06:37.211 05fbb-4133abb0 PDB: Delta logging enabled 2007/03/27 00:06:37.219 05fbb-4133abb0 PDB: Current journal: /home/test/system/journals/current/db0000009044.log
2007/03/27 00:06:37.337 05fbb-4133abb0 PDB: <<WARNING>> Archival Recovery not enabled - database availability compromised
2007/03/27 00:06:37.367 05fbb-4133abb0 PDB: Database: {a289d291-80d2-d911-8781-06004cd50200} successfully opened for update, last update jomdb version: 6.1.9.5
2007/03/27 00:06:39.984 05fbb-4133abb0 Jom: Initializing: scm=RootSchema, oid=[1.1], scmNo=1, lvl=1
2007/03/27 00:06:39.985 05fbb-4133abb0 Jom: Initializing: scm=CardSchema, scmOid=[1280.1], scmNo=100, superScmOid=[1.1], superScmNo=1 , lvl=2 2007/03/27 00:06:39.985 05fbb-4133abb0 Jom: Initializing: scm=CommonSchema, scmOid=[1280.2], scmNo=101, superScmOid=[1280.1], superScmNo=100 , lvl=3 2007/03/27 00:06:39.985 05fbb-4133abb0 Jom: Initializing: scm=BizAcct, scmOid=[1280.3], scmNo=102, superScmOid=[1280.2], superScmNo=101 , lvl=4 2007/03/27 00:06:39.985 05fbb-4133abb0 Jom: Initializing: scm=DatabaseQueryTool, scmOid=[1280.4], scmNo=103, superScmOid=[1280.3], superScmNo=102 , lvl=5
2007/03/27 00:06:39.985 05fbb-4133abb0 Jom: Initializing: scm=JTTTools, scmOid=[1280.5], scmNo=105, superScmOid=[1280.2], superScmNo=101 , lvl=4 2007/03/27 00:06:39.985 05fbb-4133abb0 Jom: Initializing: scm=DatabaseOnlineBackup, scmOid=[1280.6], scmNo=104, superScmOid=[1280.2], superScmNo=101 , lvl=4
2007/03/27 00:06:39.985 05fbb-4133abb0 Jom: Initializing: Jade is present 2007/03/27 00:06:39.986 05fbb-4133abb0 Jom: Node created: oid=[186.1], cacheCoherency=true
2007/03/27 00:06:40.055 05fbb-4133abb0 TDB: <<INFO>> Retrying out of resource errors is enabled
2007/03/27 00:06:40.055 05fbb-4133abb0 TDB: <<INFO>> Retry delay = 1000ms, retry limit = 0
2007/03/27 00:06:40.056 05fbb-4133abb0 Jom: Node initialized 0x8068008: name=E8-BRM1, computer=, db=schema, oid=[186.1], nodeType=1
2007/03/27 00:06:40.092 05fbb-4133abb0 Jom: Background process initialized 0x815d010, oid=[187.1]
2007/03/27 00:06:40.112 05fbb-420b6bb0 JomLog: BOT <CacheCoherency> 2007/03/27 00:06:40.116 05fbb-40fb2bb0 SvcMgr: System initialize ini=/home/test/jade.ini path=/home/test/system
2007/03/27 00:08:05.275 05fd1-40cdf200 E8-BRM: (jadappb) Version 6.1.9 - ANSI, OS Version: Linux 2.4.21-40.EL
2007/03/27 00:08:05.276 05fd1-40cdf200 E8-BRM: Invocation: jadappb path=/home/test/system ini=/home/test/jade.ini appServerPort=60181 server=multiUser
2007/03/27 00:08:05.274 05fd1-40cdf200 JomLog: Load library libjadprnt.so failed - libcups.so.2: cannot open shared object file: No such file or directory (8)
2007/03/27 00:08:05.305 05fd1-40cdf200 JadApp: libjadprnt.so file not available - thin client automatic downloading disabled.
2007/03/27 00:08:05.333 05fd1-40cdf200 SvcMgr: Jade Runtime Error - Error 14161
Error : Jade Dll version mismatch:

Jadapp.exe 6.1.9

libjadprnt.so 0.0.0
2007/03/27 00:08:05.592 05fd1-40cdf200 E8-BRM: (jadappb) Finished: exit code 0
2007/03/27 00:10:10.378 05fbb-40fb2bb0 Jom: Local process delete 0x815d010: no=1, id=1093905328, type=0 (non-prodn), scm=RootSchema, app=RootSchemaApp, elapsed time=00:03:33.212
2007/03/27 00:10:10.379 05fbb-411f6bb0 PDB: EOT <Database Worker> 2007/03/27 00:10:10.578 05fbb-410d4bb0 PDB: EOT <Buffer Overlay> 2007/03/27 00:10:10.578 05fbb-410f5bb0 PDB: EOT <Bg Flush>
2007/03/27 00:10:11.738 05fbb-40fb2bb0 PDB: Database closed successfully 2007/03/27 00:10:11.958 05fbb-420b6bb0 JomLog: EOT <CacheCoherency> 2007/03/27 00:10:11.959 05fbb-40fb2bb0 JomLog: Persistent NoteMgr : sys hits=0, sys misses=0, sys skips=5
2007/03/27 00:10:11.981 05fbb-40fb2bb0 JomLog: Persistent NoteMgr : usr hits=0, usr misses=0, usr skips=0
2007/03/27 00:10:12.005 05fbb-40fb2bb0 JomLog: Transient NoteMgr : sys hits=0, sys misses=0, sys skips=0
2007/03/27 00:10:12.029 05fbb-40fb2bb0 JomLog: Transient NoteMgr : usr hits=0, usr misses=0, usr skips=0
2007/03/27 00:10:12.053 05fbb-40fb2bb0 JomLog: Transient NoteMgr : sys hits=0, sys misses=0, sys skips=0
2007/03/27 00:10:12.077 05fbb-40fb2bb0 JomLog: Transient NoteMgr : usr hits=0, usr misses=0, usr skips=0
2007/03/27 00:10:12.740 05fbb-40bb9c80 E8-BRM: (jaded) Finished: exit code 0 =================================================================================================================