topic Re: Multi-versioned Views Not seeing data in the A & D tables in Data Management Questions

Multi-versioned Views Not seeing data in the A & D tables

KevinFox — Wed, 22 Feb 2012 18:25:42 GMT

We've created multi-versioned views as indicted in ArcSDE help using

"sdetable -o create_mv_view -T viewname -t table name -i sde: oracle11g -u user -p password"

The view creates fine however none of the data in the delta tables is seen in the view.

Using Oracle 11g
ArcGIS/ ArcSDE 10.0.2

Anyone know what could cause this?

We have recently loaded the data into 11g database and upgrade ArcSDE from 9.3.1 database. The views worked fine in 9.3.1. We've dropped and recreated the views using SDETABLE commands.

Re: Multi-versioned Views Not seeing data in the A & D tables

JakeSkinner — Thu, 23 Feb 2012 11:05:10 GMT

Hi Kevin,

Multiversioned views access the SDE.Default version by default. In order to query edits from other versions you will need to execute the ArcSDE version_util.set_current_version stored procedure. Here is more information on how to do this.

You can also perform a reconcile/post to the SDE.Default version and then the edits from the child version will be available in the multiversioned view.

Re: Multi-versioned Views Not seeing data in the A & D tables

DanaBaker — Tue, 28 Feb 2012 19:22:08 GMT

We are experiencing the same problem since upgrading our SDE instance to Oracle 11g and ArcSDE 10.0.2. We have correctly executed the sde.version_util.set_current_version procedure and queries to the multi-versioned views are not returning records in the A & D tables. These same views and procedures worked correctly before upgrading to ArcSDE 10.0.2.

We have tested dropping and recreating the views. Unversioning & re-versioning the data. Creating new data and views and nothing seems to fix the problem. We have also tested on different servers. This problem occurs on two of the Windows 2008 Servers, but the problem does not occur on our AIX server.

Any suggestions would be appreciated.

Thanks,
Dana

Re: Multi-versioned Views Not seeing data in the A & D tables

MandarPurohit — Tue, 28 Feb 2012 23:18:49 GMT

We have correctly executed the sde.version_util.set_current_version procedure and queries to the multi-versioned views are not returning records in the A & D tables.

Does this problem show up witout using 'EXEC sde.version_util.set_current_version'? It could be NIM070728.

As JSkinn3 mentioned, "Multiversioned views access the SDE.Default version by default". Accessing the default version without using 'sde.version_util.set_current_version' should read A & D tables.

Re: Multi-versioned Views Not seeing data in the A & D tables

DanaBaker — Wed, 29 Feb 2012 15:48:11 GMT

Thank you mvpurohit for the tip about NIM070728. This does appear to be the bug that is causing our problems.

Re: Multi-versioned Views Not seeing data in the A & D tables

MatthewTownsend — Mon, 02 Jul 2012 16:03:05 GMT

I think I have a similar issue.

If I open a SQLPlus (Oracle client app) connection and do a select on our multiversion view I get current DEFAULT data.

But if I open a SQLPlus connection and first call "sde.version_util.set_current_version('SDE.DEFAULT')" then run the same select it is missing recently added data that IS in DEFAULT.

Unfortunately, I can't see the bug in the link (NIM070728) to verify. Is there any way I can get access to view the bug information?

Is there any work around, other than NOT calling "sde.version_util.set_current_version('SDE.DEFAULT')"?

We are using ArcGIS 10 SP4 with Oracle 11g (11.2.0.1).

Thanks.

Re: Multi-versioned Views Not seeing data in the A & D tables

MatthewTownsend — Fri, 24 Aug 2012 18:23:19 GMT

ESRI confirmed that calling set_current_version against SDE.DEFAULT is behaving badly as described above.

After some investigation we found the following "fixes":
1) Don't call "sde.version_util.set_current_version('SDE.DEFAULT')" as it defaults to SDE.DEFAULT when you perform a select on a multi-version view.

2) Modify sde.version_util.set_current_version to perform a select on a multi-version view at the beginning of the procedure, thus ensuring that default is in a good state prior to running the rest of the method

3) use sde.version_util.set_default instead (added in version 10 SP4?).