In addition to the issues I mentioned, I must say those good things that I
found in MGE 2008:
1. the MGE server 2008 stability has been significantly improved, at least
on the Server B I mentioned. There are much less unnecessary error prompts
from the client side. More meaningful server errors recorded in the server
error log file.
2. the overall performance of MGE 2008 has also been greatly improved,
especially for Autodesk FDO Providers for Oracle, Raster and ODBC. Though
the performance in some aspects (e.g. initial map loading if layers of
Oracle connection are involved) is still not comparable to that of MapGuide
6.5., it is very close, and in some cases even better than MG 6.5., such as
a layer display at a large scale. Don't forget many unique advantages of MGE
over MG 6.5.
3. The major FDO providers for Oracle, Raster and ODBC by Autodesk have been
greatly improved too. I have tested the FDO provider for Oracle, FDO
Provider for ODBC accessing tables with lat/lon from MS ACCESS, SQL Server
and Oracle, FDO Provider for Raster using our ECW and TIFF files, and they
all worked quite good, though the performance of the ECW and Tiff
orthophotos layers with MGE 2008 is still not equivalent to that of MG 6.5,
basically about 1.5x to 2x slower than 6.5.
I would like to hear more from other people experience.
Meng
"Meng Li" wrote in message
news:5696456@discussion.autodesk.com...
Based on our experience and postings here in using MGE 2008 for accessing an
Oracle (10g r2 ) database, I found these 3 major issues that I would like to
summarize:
1. MGE Server crashes and instability in connecting to an Oracle database
via Autodesk FDO Provider for Oracle.
I have a Server A with Windows Server 2003 SP2 previously installed with MGE
2007, and after the MGE 2007 removal, MGE 2008 is installed on Server A.
However, my testing showed that Oracle connection and layer building on
Server A often ended up with MGE 2008 server crashes and I had to frequently
restart the MGE server. The server error log file showed this type of
errors:
Error: Failed to stylize layer: LayerDefinition0
An exception occurred in FDO component.
'FdoPtr::operator->': Cannot execute function due to invalid
value for the input parameter(s) 'p'.
StackTrace:
- MgStylizationUtil.StylizeLayers line 923 file
c:\build_bond_area\bond_nightly\build_41.3\ent\os\server\src\services\mapping\StylizationUtil.cpp
Failed to stylize layer: LayerDefinition0
An exception occurred in FDO component.
'FdoPtr::operator->': Cannot execute function due to invalid value
for the input parameter(s) 'p'.
<2007-08-15T09:21:24> Administrator
Error: Failed to stylize layer: LayerDefinition0
An unclassified exception occurred.
However, I used another Windows Server 2003 SP2 Server B which has not
previouly installed any MGE, and set up MGE 2008 on it. Then my testing on
this server seems quite stable in connecting to the same Oracle database and
I only got 1-3 times server crashes in a week. So. I suspect that either the
old MGE 2007 has not been completed un-installed, or MGE 2008 has not been
properly configured on Server A?
I read another posting on July 17 "MapGuide 2008 Connect to Oracle" which
talked about a similar Oracle connection problem, but no obvious solution
yet. In my case the MGE 2008 installed on C drive of both Server A and B,
while a full Oracle client 10g r2 has been installed on D drive.
2. not good performance on initial Oracle connection and map loading.
I responded to a previous posting on July 20 "Performance issues on intial
map load with Oracle connection" with this:
I would also confirm on what Kayne said about MGE 2008 performance for
Oracle connection.
In my case, I have two Oracle (10g r2) database instances: GISDEV with
Oracle native schema of about 220 tables/views and GISTEST with a FDO schema
of the same tables/views.
The initial connection and loading for feature classes and layers from
GISDEV takes about 2-5 minutes, while it takes about 30 seconds from GISTEST
which is a FDO-enabled data store. Once the initial loading is done for the
connection at a time, the subsequent layer display of the same database
connection is quick enough, normally in 4-10 seconds, regardless of being
from GISDEV or GISTEST. Note that even the map has only SDF-based layers
initially displayed at startup, as long as there are Oracle layers in the
map, the map seems always looking up the database connection and metadata,
which takes a long time. The MGE server cache doesn't seem to work
adequately in this case.
The performance with a FDO-enabled Oracle database connection seems better
than an Oracle native db connection, in our case, it is 30 seconds versus
2-5 minutes for initial connection and map loading. But still 30 seconds is
not that good.
So the challenge here is to make the initial Oracle database connection and
map loading quickly done within an acceptable time, e.g. under 10 seconds?
Any tips or workarounds in addition to those already posted here?
3. Oracle connection and its feature source refresh problem. A feature
source of Oracle connection is not able to reflect any change/addition made
on tables/views of Oracle, unless the feature source is refreshed by
re-entering the password and re-saved. But this has to be done
manually in Studio, or any way using Studio API or Server API could make the
refresh automatically done? so that I don't have to re-save the feature
source manually?
There are two postings about the issue on July 18 "Can an Oracle data
connection by refreshed?" and on Aug 20 "Oracle connection in MGE 2008 can
not see nely created objects unless..."
Thanks
Meng
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")