Getting error while running OLEDB - get collection action

[JayaprakashRed1]

Hi Team,

We are able to connect to Oracle database from BP and tested with simple query.
But while running main query (which is tested at sqlplus editor) getting the below error.

Internal : Exception: A stack imbalance has occurred. Check your process for errors.

When i am running the other query like getting results from object 'Data - OLEDB' - get collection action.
select sysdate from dual;

Please let us know if any suggestions.

Thanks,
Jayaprakash

------------------------------
Jayaprakash Reddy Anikekalva
Technical Lead
TCS
Europe/London
------------------------------

[MateuszBartczak]

Hi Jayaprakash ,

A stack imbalance error in BP appearing in case process is already in recovery mode and is keeping an error in memory. Please go through resume stage first and then see what is the actual error. If you are not in recovery mode, maybe let's try to add Try Catch syntax to the code stage and try to read inner exception. Please provide also connection string that you are using.

Cheers

------------------------------
Mateusz Bartczak
------------------------------

[AnuraagPandey]

Hello Jayaprakash,

I could think of another reason why you are getting this error. This happens when you are asking your object to do too many things.

When you call the object (as an action) in your process studio, what BP does is, it calls the entire object and all its different actions in the temporary memory. The solution to this could be to split the object into multiple simpler blocks and then call them one by one as needed. 

Save the new object structure(multiple objects instead of one), reset the process, close everything and restart your  BP studio and execute again.
Let us know how it goes.

------------------------------
Anuraag Pandey
Germany
------------------------------

[krishna.kodimurali9]

Hi Jayaprakash, 

Are you running the process on debug mode?

------------------------------
MuraliKrishna
RPA Consultant
------------------------------

[EVIPUTI]

There are possible 2 reasons to this :
1-  You step over debug mode too fast .
2- the  process\object is in exception mode and new exception occurred. 
Simply reset or run a resume state to solve this .

------------------------------
------------------------------
Vipul Tiwari
Senior Process Simplification Developer
Amazon
------------------------------
------------------------------