Hello all,
I upgraded our Oracle db software this weekend to 11.2.0.3. In doing so I created a new gdb on our production server. Prior to this, I copied all of our datasets to a backup db. Once the new production db was ready, I copied the datasets into the new db. I haven't had any problem registering the datasets except for 2 of them. Not sure what the problem is. I am able to see the data just fine, but when I try to register them as versioned, it just hangs up. The last time I tried it, it ran for 2 hours before I decided to kill it. Any thoughts or ideas? The 2 datasets are assessor information with large feature classes. One of these is a parcel fabric. When I copied them to the backup db, I had no problem registering them as versioned. So I am not sure if the problem lies within the data or within the db. Any help would be greatly appreciated. I am running Oracle 11g R2 and ArcGIS 10.2 on a Windows 2008 Server.
Thanks,
Kevin
I upgraded our Oracle db software this weekend to 11.2.0.3. In doing so I created a new gdb on our production server. Prior to this, I copied all of our datasets to a backup db. Once the new production db was ready, I copied the datasets into the new db. I haven't had any problem registering the datasets except for 2 of them. Not sure what the problem is. I am able to see the data just fine, but when I try to register them as versioned, it just hangs up. The last time I tried it, it ran for 2 hours before I decided to kill it. Any thoughts or ideas? The 2 datasets are assessor information with large feature classes. One of these is a parcel fabric. When I copied them to the backup db, I had no problem registering them as versioned. So I am not sure if the problem lies within the data or within the db. Any help would be greatly appreciated. I am running Oracle 11g R2 and ArcGIS 10.2 on a Windows 2008 Server.
Thanks,
Kevin
I have experienced very similar behavior to what you're describing, where a small handful of our datasets took forever to register as versioned compared to the rest. One of those datasets contained a geometric network, and the other had a lot of data compared to all of the others. Our method involved copying and pasting from a 9.3.1 SP2 geodatabase to a 10.2.1 geodatabase, both on Oracle 11g R2. However, our 9.3.1 SP2 geodatabase used SDELOB and our 10.2.1 geodatabase used ST_Geometry. We discovered that the register as versioned process was much faster if we stuck with SDELOB at 10.2.1 instead of accepting the default keywords for ST_Geometry when copying and pasting. I can't tell yet if this is what might be affecting you, but I wanted to share my experiences thus far.