Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in August and this forum will be retired.

SA16 crashes when I try to import certain ESRI shapefiles.

It works for some .shp files and not for others.

The message is "Sybase Central Internal Error" (I've reported the ID(s) 984945 984946).

I'm running SQL Anywhere 16, Version

Has anyone else had this problem?

Terry Wilkinson

asked 19 Sep '14, 14:14

Terry%20Wilkinson's gravatar image

Terry Wilkinson
accept rate: 25%

FWIW, I found a work-around for this problem. I used the opensource program MapWindow GIS to read the problematic shapefile and then resave it. That seems to have fixed whatever was tripping up SA16, and I can now do the import. Terry

(20 Sep '14, 08:45) Terry Wilkinson

It sounds like there is something...unique...about your shapefile. In order to correct the issue, I'm sure it would be immensely helpful if you could provide one of the problematic shapefiles. Assuming, of course, that it does not violate any privacy or proprietary information policies.

permanent link

answered 20 Sep '14, 09:01

Phil%20Mitchell's gravatar image

Phil Mitchell
accept rate: 27%

It turns out that we are not licensed to share the problematic shapefile, so I guess we'll have to hope that the reported error ID's are enough for SPA to diagnose the problem. Too bad.. Terry

(22 Sep '14, 13:00) Terry Wilkinson

You can ask for help via support tickets.

(24 Sep '14, 03:41) Vlad

We can tell that there is something going on with the date data but it would be helpful to understand what it is inside the shape file that is leading to this.

Is there a way we can identify the shape files (from what source) or if you have identified the nature of the dates (that MapView GIS converted)?

(25 Sep '14, 15:23) Nick Elson S...

Thanks for identifying this issue.

A fix to prevent this crash will be available in a future EBF/SP of 16 and 12.0.1. Change Reference#: 771429

(26 Sep '14, 16:49) Nick Elson S...

Thanks guys. I had a drive failure and have been offline for a couple of days. It sounds like you identified the problem, but FWIW, I did notice that the dates in the 'good' .dbf files were YYYYMMDD, while the dates in the 'bad' files were YYYY-MM-DD (with the hyphens).

(29 Sep '14, 11:32) Terry Wilkinson
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 19 Sep '14, 14:14

question was seen: 2,196 times

last updated: 29 Sep '14, 11:32