| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Importing a runtime FDL -FmcAssertionException |
« View previous topic :: View next topic » |
| Author |
Message
|
| satboppana |
 Posted: Wed Dec 10, 2003 6:35 pm Post subject: Importing a runtime FDL -FmcAssertionException |
 |
|
Acolyte
Joined: 20 Dec 2001
Posts: 64
|
I was importing an FDL exported from Environment A to B
And i got the FmcAssertionException.
Any ideas?
I split the file into different processes and it worked.
_________________
Sb |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu Dec 11, 2003 5:40 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
There is a size limitation on FDL imports... Not sure where its documented, check the Readme files, and possibly the Install guide.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Prahasith |
| Posted: Thu Dec 11, 2003 12:54 pm Post subject: |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
Problem importing large FDL files into Buildtime
When importing large FDL files into Buildtime, Buildtime appears to
interrupt the operation before the process finishes.
Reasons for the interruption can be:
1. DB2: The tablespace fills up, which causes DB2 to interrupt.
This problem has been addressed with APAR IX76273 for DB2 UDB,
which has been fixed in DB2 UDB V.5.2.
The problem occurs both with database-managed tablespaces
and with system-managed tablespaces. The Buildtime database
uses system-managed tablespaces.
2. Microsoft Jet engine:
The Jet engine creates temporary files on the C drive
(for example, jet1855.tmp). If there is not enough space
available on the C drive (temp directory), the system
runs out of space.
150 MB free space is recommended.
You can solve the problem as follows:
- If the process does not show any change in CPU time,
end the fmcbmain.exe using the task manager.
- Split the FDL file into smaller files and import them individually.
Following is an example of an FDL file with a size of 2 MB:
- 850 persons
- 30 roles
- 25 organizations
- 100 programs
- 30 data structures
- 80 processes with
- 700 activities
- 8000 activity container default values
- 1800 data mappings
plus everything else that belongs to the processes
For this scenario, the temporary jet engine file can grow up to a
size of 50 MB. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
