Ibatis Spring Stored Procedure with Multiple OUT - spring

Is it possible to implement a stored procedure call in oracle, which has more than 3 output (OUT)
using Ibatis 2.3.4 integrated with Spring version 2.7,
If possible please provide link for reference,
Thanks in Advance

I implemented oracle store procedure called using iBatis on Spring, and can't find the limitation about 3 OUT parameter as you described above. In my opinion, it's possible to create store procedure for your purpose, use this link as reference:
Ibatis and Oracle Procedure
If you got any problem, please let me know.
HTH.

Related

Calling Oracle Stored Procedure from R2DBC

I am trying to call an Oracle stored procedure from Spring Data R2DBC. I have currently set up querying either by annotation or R2DBC entity template and those work fine. However, I have not been able to call a proc with input/output parameters.
I saw some documentation mentioning support for procedure calls in R2DBC but have not found any concrete examples on how it is done. Any help or link to documentation or examples would be greatly appreciated.
The documentation for how to do procedural-calls can be found in the readme on github for the oracle-r2dbc driver:
procedural calls

How to configure Kafka JDBC Source Connector with stored procedure?

I am very new to Kafka, I'm doing a PoC (my first Kafka app) and was curious to know if anyone has come across or worked on a custom JDBC Source Connector that uses a stored procedure to export data from Oracle into Kafka?
I know this could be considered an open-ended question by the SO community but thanks for your patience and I'd appreciate any feedback.
Thank you!
Some background:
I already have stored procedures in Oracle which are used by an existing Spring app to extract and load data in a new DB (for a new version of an existing enterprise application).
The table structure in the new database is different than that of the old.
The Spring app (which uses Spring JDBC and works with Stored Procedures, Row Mappers etc.) was developed as a PoC to check connectivity, integration and to load data in the new DB.
Now that it works, we're trying to introduce Kafka that would actually store the data and then load it into the new DB. The JDBC Sink Connector would be developed later.
I am looking for an example (using Java, Maven, Spring) that would help me in getting started towards building a custom connector. Most of the example/docs show curl examples which doesn't fit my existing app. I maybe missing something here.
There is way that we can call SP though source connector property - query: call sp here by creating temp table and insert data

Make BIRT report using data from Gemfire cache

I am relatively new to both, BIRT and gemfire but I know the basics. Thought I wasn't able to find how BIRT can fetch data from gemfire cache.
Can someone please help me on the procedure or whether it is possible or not?
It looks like BIRT uses JDBC (amongst other means) to talk to a backend datasource. Unfortunately GemFire does not provide a JDBC driver. You would need to develop a custom ODA Data Source as described here: https://wiki.eclipse.org/Use_Case_-_Create_a_Custom_ODA_Data_Source

Spring JDBC Stored Procedure call timing out

I am using Spring SimpleJBDCTemplate for a DB2 stored procedure call, the stored procedure returns around 200k records and it's kind of timing out from my java code.
I tried setMaxRecords option, it helps to an extent.
Is there something like a batch read or a page read that are part of Spring?
Spring has a library that is called Spring Batch. You should definitley see documentation and try to adapt it to your problem.
Please refer to this: Spring-Batch

Edit a record from a DB table using EJB3?

im quite new to EJB3 and was wondering if it is possible to edit a specific record from a table using EJB3?
If so, are there any tutorials and examples on how to do this?
Thanks in advance
Since entity beans were deprecated in the EJB3 standatd, you'd do this using either plain JDBC or JPA, but neither of these requires EJBs to be used.

Resources