Hi,
We have a geoserver 2.8.5 version where the above works fine.
When we upgrade to geoserver 2.12 and try to create new feature via WFS in a featuretype that is based on Oracle view with instead of trigger we get to following error:
ORA-22816: unsupported feature with RETURNING clause
I have read the discussion when 2.9 was lauched that someone also had same problem, but did not see any resolution. Do you have a workaround for this?
Thank you,
Laszlo
Hi,
Just to have it in the archive I have found a workaround for this error.
The current version of gt-jdbc-oracle uses a “new” Oracle JDBC feature to get the DB generated ID of new record inserted by using Oracle RETURNING clause feature under the hook. By reverting back to gt-jdbc-oracle-14.5.jar (simple download it from the archive and replace gt-jdbc-oracle-X-Y.jar in WEB-INF/lib and restarting geoserver resolves the ERROR.
I guess that the newer version has couple of optimizations that are lost by this fallback to old version, so the prefect solution would be to include a config option where to use this feature or not (may be by featuretype).
Regards,
Laszlo
On 2018. Apr 19., at 11:21, Laszlo Nemeth <nemeth.laszlo@anonymised.com> wrote:
Hi,
We have a geoserver 2.8.5 version where the above works fine.
When we upgrade to geoserver 2.12 and try to create new feature via WFS in a featuretype that is based on Oracle view with instead of trigger we get to following error:
ORA-22816: unsupported feature with RETURNING clause
I have read the discussion when 2.9 was lauched that someone also had same problem, but did not see any resolution. Do you have a workaround for this?
Thank you,
Laszlo
Hi,
Just to have it in the archive I have found a workaround for this error.
The current version of gt-jdbc-oracle uses a “new” Oracle JDBC feature to get the DB generated ID of new record inserted by using Oracle RETURNING clause feature under the hook. By reverting back to gt-jdbc-oracle-14.5.jar (simple download it from the archive and replace gt-jdbc-oracle-X-Y.jar in WEB-INF/lib and restarting geoserver resolves the ERROR.
I guess that the newer version has couple of optimizations that are lost by this fallback to old version, so the prefect solution would be to include a config option where to use this feature or not (may be by featuretype).
Regards,
Laszlo
On 2018. Apr 19., at 11:21, Laszlo Nemeth <nemeth.laszlo@anonymised.com> wrote:
Hi,
We have a geoserver 2.8.5 version where the above works fine.
When we upgrade to geoserver 2.12 and try to create new feature via WFS in a featuretype that is based on Oracle view with instead of trigger we get to following error:
ORA-22816: unsupported feature with RETURNING clause
I have read the discussion when 2.9 was lauched that someone also had same problem, but did not see any resolution. Do you have a workaround for this?
Thank you,
Laszlo
Don’t randomly change the jars in a GeoServer install, many bad things can happen and there is no guarantee that it will continue to work in the future even if you get away with it now.
Instead please raise an issue (http://docs.geoserver.org/latest/en/user/introduction/gettinginvolved.html#bug-tracking) and make sure that it gets fixed in later versions of GeoServer. Since you can afford Oracle you can find some time or cash to fix this issue too, right?
Ian
···
On 19 April 2018 at 16:41, Laszlo Nemeth <nemeth.laszlo@anonymised.com> wrote:
Hi,
Just to have it in the archive I have found a workaround for this error.
The current version of gt-jdbc-oracle uses a “new” Oracle JDBC feature to get the DB generated ID of new record inserted by using Oracle RETURNING clause feature under the hook. By reverting back to gt-jdbc-oracle-14.5.jar (simple download it from the archive and replace gt-jdbc-oracle-X-Y.jar in WEB-INF/lib and restarting geoserver resolves the ERROR.
I guess that the newer version has couple of optimizations that are lost by this fallback to old version, so the prefect solution would be to include a config option where to use this feature or not (may be by featuretype).
Regards,
Laszlo
On 2018. Apr 19., at 11:21, Laszlo Nemeth <nemeth.laszlo@anonymised.com> wrote:
Hi,
We have a geoserver 2.8.5 version where the above works fine.
When we upgrade to geoserver 2.12 and try to create new feature via WFS in a featuretype that is based on Oracle view with instead of trigger we get to following error:
ORA-22816: unsupported feature with RETURNING clause
I have read the discussion when 2.9 was lauched that someone also had same problem, but did not see any resolution. Do you have a workaround for this?
Thank you,
Laszlo
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
Ian Turton
Correct. I raised the issue and also check commercial support.
Regards,
Laszlo
···
On 19 April 2018 at 16:41, Laszlo Nemeth <nemeth.laszlo@anonymised.com> wrote:
Hi,
Just to have it in the archive I have found a workaround for this error.
The current version of gt-jdbc-oracle uses a “new” Oracle JDBC feature to get the DB generated ID of new record inserted by using Oracle RETURNING clause feature under the hook. By reverting back to gt-jdbc-oracle-14.5.jar (simple download it from the archive and replace gt-jdbc-oracle-X-Y.jar in WEB-INF/lib and restarting geoserver resolves the ERROR.
I guess that the newer version has couple of optimizations that are lost by this fallback to old version, so the prefect solution would be to include a config option where to use this feature or not (may be by featuretype).
Regards,
Laszlo
On 2018. Apr 19., at 11:21, Laszlo Nemeth <nemeth.laszlo@anonymised.com> wrote:
Hi,
We have a geoserver 2.8.5 version where the above works fine.
When we upgrade to geoserver 2.12 and try to create new feature via WFS in a featuretype that is based on Oracle view with instead of trigger we get to following error:
ORA-22816: unsupported feature with RETURNING clause
I have read the discussion when 2.9 was lauched that someone also had same problem, but did not see any resolution. Do you have a workaround for this?
Thank you,
Laszlo
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
Ian Turton
Correct. I raised the issue and also check commercial support.
Regards,
Laszlo
···
On 19 April 2018 at 16:41, Laszlo Nemeth <nemeth.laszlo@anonymised.com83…> wrote:
Hi,
Just to have it in the archive I have found a workaround for this error.
The current version of gt-jdbc-oracle uses a “new” Oracle JDBC feature to get the DB generated ID of new record inserted by using Oracle RETURNING clause feature under the hook. By reverting back to gt-jdbc-oracle-14.5.jar (simple download it from the archive and replace gt-jdbc-oracle-X-Y.jar in WEB-INF/lib and restarting geoserver resolves the ERROR.
I guess that the newer version has couple of optimizations that are lost by this fallback to old version, so the prefect solution would be to include a config option where to use this feature or not (may be by featuretype).
Regards,
Laszlo
On 2018. Apr 19., at 11:21, Laszlo Nemeth <nemeth.laszlo@anonymised.com> wrote:
Hi,
We have a geoserver 2.8.5 version where the above works fine.
When we upgrade to geoserver 2.12 and try to create new feature via WFS in a featuretype that is based on Oracle view with instead of trigger we get to following error:
ORA-22816: unsupported feature with RETURNING clause
I have read the discussion when 2.9 was lauched that someone also had same problem, but did not see any resolution. Do you have a workaround for this?
Thank you,
Laszlo
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
Ian Turton