Forums

by news.jadeworld.com >> Thu, 2 Nov 2006 9:20:44 GMT

Hi All :
I have a problem in too big volumn of a map file
in map file name bizMast.biz
we group ARMast, APMast, SRMast three classes in the file.

the map file BizMast grow huge volumn for many instances of the classes

Is it possilbe to break down bizMast.dat file into
armast.dat only for ARMast class
apmast.dat only for APMast class
srmast.dat for SRMast class

Regards
Didier
2006.10.26

by BeeJay >> Fri, 3 Nov 2006 1:52:47 GMT

This has been covered before in the following two newsgroup postings:

1. In a posting titled 'Can we split a Populated Class out of a FIle' in the jade_tech_design_architecture newsgroup. (Posted: 1st June 2006)

2. In a posting titled 'changing map file of a class' further down in this Newsgroup (Posted: 5th February 2005).

One of those postings makes a mention of FAQ 25483 covering this topic, but that FAQ appears to be no longer available from the FAQ search on the Jade Web Site.

Cheers,
BeeJay

by BeeJay >> Fri, 3 Nov 2006 1:56:11 GMT

Sorry, that first posting reference should have had 1st June 2005 not 1st June 2006 as its posted date.

Cheers,
BeeJay.

by news.jadeworld.com >> Mon, 6 Nov 2006 0:56:39 GMT

Hi
I'v tested
1> in Window XP
Both Jade5.2 and Jade 6.1 are OK

2> In Linux AS3 , Jade 6024
the exception as follow =================================================================================================================== [root@rehat236 bin]# ./loadMapFile.sh
Begin Map File Processing...
Opening database in /home/user/jade/system_fila236...
Database opened
Executing RootSchema::Schema::_moveObjects()
MessageBox: Error

*** Unhandled Exception ***
Unhandled FileException on 2006/11/05 13:31:42
Computer= rehat236, Application= JadeLoader, Schema= RootSchema
FileException: 5003 (not continuable, resumable)
* Requested file not found
Error item: open
Error object: 295.1 (transient)
Caused By:
Receiver: File/295.1 (transient)
Method: File::openInput(133) -- source position: 133
Reported By:
Receiver: File/295.1 (transient)
Method: File::open -- 'fileOpen' in 'jomsupp'

MessageBox: Error

*** Unhandled Exception ***
Unhandled SystemException on 2006/11/05 13:31:42
Computer= rehat236, Application= JadeLoader, Schema= RootSchema
SystemException: 1090 (not continuable, resumable)
* Attempted access via null object reference
Caused By:
Receiver: Schema/1280.1
Method: Schema::_moveObjects(4777) -- source position: 4777

Closing database...
Database closed
Load failed with error 1090
[root@rehat236 bin]# =================================================================================================================== Appriciated for any help

Regards
Didier
2006.11.5

by allistar >> Mon, 6 Nov 2006 8:51:44 GMT

Can you post the contents of loadMapFile.sh?

Ta,
Allistar.

by news.jadeworld.com >> Fri, 10 Nov 2006 0:32:22 GMT

Hi:
The following is the content of loadMapFile.sh, also can refer to the attached file.

.../jadloadb.sh path="/home/user/jade/system_fila236" executeSchema=RootSchema executeClass=Schema executeMethod=_moveObjects noaudit=false ini="/home/user/jade/jade.ini"

loadMapFile.sh is in the bin directory.

Regards

Didier
2006.11.10

by allistar >> Fri, 10 Nov 2006 2:05:50 GMT

Is the _params.txt file in the system directory? A jommsg.log file should say which file it is trying to open when the exception happens - that may provide you with more information.

Regards,
Allistar.

by news.jadeworld.com >> Sat, 11 Nov 2006 9:38:22 GMT

Hi:
Yes, the _params.txt file is in the system directory.



I suppose the issue reslut in the error file path ( the following line is in the jommsg.log ):

2006/11/11 17:15:06 00658-b75db2a0 JomLog: [File open] error - No such file or directory (2), file: /home/user/jade/system_fila236\_params.txt

Is it possibile to specify the file explicitly, such as ini file.

jommsg.log sample ======================================================================================== 2006/11/11 17:15:02 00658-b75db2a0 rehat236: (jadloadb) Version 6.0.21 - ANSI, OS Version: Linux 2.4.21-37.EL
2006/11/11 17:15:02 00658-b75db2a0 rehat236: Invocation: jadloadb ini=/home/user/jade/jade.ini path=/home/user/jade/deploy path=/home/user/jade/system_fila236 executeSchema=RootSchema executeClass=Schema executeMethod=_moveObjects noaudit=false ini=/home/user/jade/jade.ini
2006/11/11 17:15:02 00658-b75db2a0 PDB: Delta logging disabled
2006/11/11 17:15:02 00658-b75db2a0 PDB: Database initialising with jomdb version: 6.0.21.2, ini=/home/user/jade/jade.ini
2006/11/11 17:15:02 00658-b75db2a0 PDB: System file directory: /home/user/jade/system_fila236/
2006/11/11 17:15:02 00658-823bb0 PDB: BOT <Buffer Overlay>
2006/11/11 17:15:02 00658-965bb0 PDB: BOT <Bg Flush>
2006/11/11 17:15:02 00658-71b4bb0 PDB: BOT <Database Worker>
2006/11/11 17:15:02 00658-b75db2a0 PDB: Total active database size restricted to 4GB
2006/11/11 17:15:02 00658-40a3bb0 PDB: ************************************************************************************************ 2006/11/11 17:15:02 00658-40a3bb0 PDB: <<WARNING>> Transaction journal directory /home/user/jade/system_fila236/journals/current/ is located on the same volume as your Database
2006/11/11 17:15:02 00658-40a3bb0 PDB: Database performance compromised; audit I/O will compete with database I/O
2006/11/11 17:15:02 00658-40a3bb0 PDB: ************************************************************************************************ 2006/11/11 17:15:02 00658-40a3bb0 PDB: Current journal: /home/user/jade/system_fila236/journals/current/db0000002928.log 2006/11/11 17:15:02 00658-40a3bb0 PDB: <<WARNING>> Archival Recovery not enabled - database availability compromised
2006/11/11 17:15:02 00658-40a3bb0 PDB: Database: [a289d291-80d2-d911-8781-06004cd50200] successfully opened for update 2006/11/11 17:15:05 00658-40a3bb0 Jom: Initializing: scm=RootSchema, oid=[1.1], lvl=1
2006/11/11 17:15:05 00658-40a3bb0 Jom: Initializing: scm=CardSchema, oid=[1280.1], lvl=2
2006/11/11 17:15:05 00658-40a3bb0 Jom: Initializing: scm=CommonSchema, oid=[1280.2], lvl=3
2006/11/11 17:15:05 00658-40a3bb0 Jom: Initializing: scm=BizAcct, oid=[1280.3], lvl=4
2006/11/11 17:15:05 00658-40a3bb0 Jom: Initializing: scm=DatabaseQueryTool, oid=[1280.4], lvl=5
2006/11/11 17:15:05 00658-40a3bb0 Jom: Initializing: scm=JTTTools, oid=[1280.5], lvl=4
2006/11/11 17:15:05 00658-40a3bb0 Jom: Initializing: scm=DatabaseOnlineBackup, oid=[1280.6], lvl=4
2006/11/11 17:15:05 00658-40a3bb0 Jom: Initializing: Jade is present 2006/11/11 17:15:05 00658-40a3bb0 Jom: Node created: oid=[186.1], cacheCoherency=false
2006/11/11 17:15:05 00658-40a3bb0 Jom: Node initialized 0x8afe078: name=rehat2361, computer=, db=RootSchemaDb, oid=[186.1], nodeType=5 2006/11/11 17:15:05 00658-40a3bb0 Jom: Background process initialized 0x8bef1a0, oid=[187.1]
2006/11/11 17:15:05 00658-b75db2a0 Jom: Local process sign-on 0x8afb510: no=2, id=3076371104, oid=[187.2], type=6, scm=RootSchema, app=JadeLoader, 6.0.21.2
2006/11/11 17:15:06 00658-b75db2a0 JomLog: Executing RootSchema::Schema::_moveObjects()
2006/11/11 17:15:06 00658-b75db2a0 JomLog: [File open] error - No such file or directory (2), file: /home/user/jade/system_fila236\_params.txt 2006/11/11 17:15:06 00658-b75db2a0 JomLog: Unhandled FileException: Requested file not found, see JadeLoader.log for details
2006/11/11 17:15:06 00658-b75db2a0 JomLog: Unhandled SystemException: Attempted access via null object reference, see JadeLoader.log for details 2006/11/11 17:15:06 00658-40a3bb0 Jom: Local process delete 0x8afb510: no=2, id=3076371104, type=6, scm=RootSchema, app=JadeLoader
2006/11/11 17:15:06 00658-b75db2a0 Jom: Local process delete 0x8bef1a0: no=1, id=67779504, type=0, scm=RootSchema, app=RootSchemaApp
2006/11/11 17:15:06 00658-71b4bb0 PDB: EOT <Database Worker>
2006/11/11 17:15:06 00658-965bb0 PDB: EOT <Bg Flush>
2006/11/11 17:15:06 00658-823bb0 PDB: EOT <Buffer Overlay>
2006/11/11 17:15:07 00658-b75db2a0 PDB: Database closed successfully 2006/11/11 17:15:07 00658-b75db2a0 JomLog: Loader exiting - error 1090 2006/11/11 17:15:07 00658-b75db2a0 rehat236: (jadloadb) Finished: exit code 1090 remapped to 105 ========================================================================================

Regards

Didier
2006.11.11

by Patwos >> Sun, 12 Nov 2006 22:15:02 GMT

Unfortunately I don't believe you can control how this utility "generates" the name of the file to open - they appear to be taking the system directory and appending \_params.txt to generate the file name. It looks like it won't work on Linux until Jade adjusts this code to use a host-aware directory separator when "generating" the file name.

If you have a valid support contract I suggest you open a fault in Parsys.

Hope that helps,
Pat.

by allistar >> Tue, 14 Nov 2006 11:26:43 GMT

As Didier suggested, renaming the file to "system_fila236\_params.txt" will do the trick. Luckily "\" is a valid file name character in Linux.

Allistar.