I already got my reply from MapInfo tech support with 2 solutions. 1 - Upgrade to v7.5! lol, i was expecting this one. hehe
2 - In the init[database server].ora file, add the parameter: event="10499 trace name context forever, level 4" Shutdown the database startup the database We did #2 and MapInfo Pro v7.0 and Oracle are now functioning correctly again. But I guess we're still considering upgrading to 7.5. Maybe we'll see how this works and then move up to v8.0 when it comes out, as long as this work-around continues to work without problems. Apparently Oracle made a change so that it sees most number field types as just a generic Number type and a certain flag wasn't added to account for fields of type float. So Oracle was no longer communicating the float fields correctly to MapInfo. This was then corrected in MapInfo Pro v7.5. So much for a flawless business relationship. Heh. Then again, maybe this is was a conspiracy to make all v7.0 users upgrade to v.7.5! ;) -Evan -----Original Message----- From: Evan MacDougall Sent: Wednesday, December 10, 2003 11:16 AM To: MapInfo-L (E-mail) Subject: MI-L Oracle 9.2.0.4 v MapInfo 7.0 conflict I am having a problem and I want to know if anyone else has encountered this problem, contacted MapInfo about, and/or determined a work-around or solution for it. We have tables containing approx 1.5 million records contain in Oracle databases. Previously we were using Oracle version 9.0.1 and we recently upgraded to version 9.2.0.4. We have been using MapInfo version 7.0 for the whole time. A unique ID field is created called "MI_PRINX" when a table is loaded/imported into Oracle. This field has always been type FLOAT in MapInfo. When extracting data from the Oracle 9.0.1 database thru MapInfo 7.0's "oracle spatial" capabilities it shows up as float. However, when fetching data from Oracle 9.2.0.4 using the same MapInfo 7.0's "oracle spatial" capability, the MI_PRINX field AND ALL OTHER type FLOAT fields are being designated by MapInfo 7.0 as type Decimal (2,0) which causes any number in that field of 100 or greater to be converted to the number 99. We have checked using Oracle software to determine that the data in tables in the Oracle Database are still correct and showing the correct values. It is only when fetching data from the tables using MapInfo 7.0 that the data becomes "corrupted" because MapInfo insists on viewing these fields as Decimal (2,0) instead of FLOAT. This happens both on tables loaded thru MapInfo's EasyLoader AND thru tables exported from our Oracle 9.0.1 database and then imported into the 9.2.0.4 database. (Yes, we still have a copy of our older 9.0.1 database and the process continues to work correctly there). Anything helpful would be appreciated. (I am also sending this to MapInfo tech support, btw). Also wondering if this problem still occurs in MI-7.5 -Evan MacDougall GIS Supervisor - DPSI [EMAIL PROTECTED] (800)736-3109/(310)342-3600 - ext. 3681 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 9518
