Calling a service package's CRUD-style method (like `Some_Handling_SVC.CRUD_Delete`) directly from SQL Developer for a one-off cleanup task fails with a cryptic Oracle datatype error, even though the same call works fine when triggered normally through the application.

Q: Calling a service package's CRUD-style method (like `Some_Handling_SVC.CRUD_Delete`) directly from SQL Developer for a one-off cleanup task fails with a cryptic Oracle datatype error, even though the same call works fine when triggered normally through the application.

Check whether the block is missing an explicit COMMIT at the end — a service-package CRUD call invoked directly outside its normal client-driven transaction flow may need an explicit commit added after the call for the change to actually persist and for the call to complete cleanly, since it isn't automatically wrapped in a commit the way the calling client's own transaction handling would normally provide.

Answer

Check whether the block is missing an explicit COMMIT at the end — a service-package CRUD call invoked directly outside its normal client-driven transaction flow may need an explicit commit added after the call for the change to actually persist and for the call to complete cleanly, since it isn't automatically wrapped in a commit the way the calling client's own transaction handling would normally provide.

← Browse Developer Studio, deployment, and upgrades questions