That means currently there is no way to get dbms_output to standard output when invoking stored procedure using pl-sql gem. Ok :( ..
Thanks Rai for your valuable comments.

Thanks,
Vikas Rana

I have a stored procedure named as “display”. In this stored procedure I have dbms_out.put_line statment. I am not able to get the statement specified in the dbms_output in the standard output of my terminal.
In my stored procedure I have a statement “dbms_output.enable” before the put_line statement. Eventhough I am not able to get the standard output to my terminal.

Please guide me on this.

Thanks,
Vikas Rana

One workaround is to use named parameters when calling it from Ruby:
plsql.prepare_phone(:country_id => 82, :work_phone_no => ‘+49 (89) 1234,123′)
In this case no additional parameters would be passed.

Other option would be always to replace NULL values in parameters with default values at PL/SQL side :)

my prepare_phone definition looks like this

FUNCTION prepare_phone (country_id in number, work_phone_no in varchar, leading_zero in number default 1) RETURN varchar

I just discovered in ruby_plsql the function returns expected result when the third parameter is provided:
p plsql.chrispack.prepare_phone(82,”+49 (89) 1234,123″,1);
“0891234″
p plsql.chrispack.prepare_phone(82,”+49 (89) 1234,123″); — should deliver same result but does not
“891234″

is it because of the default value in third parameter not being respected by ruby_plsql?

thanks,
chris

I noticed a little different ruby_plsql behaviour to what sqlplus does in the following example:

I have a plssql function in package chrispack called prepare_phone

in sqlplus
SQL> select chrispack.prepare_phone(82,’+49 (89) 1234,123′) from dual;
CHRISPACK.PREPARE_PHONE(82,’+49(89)1234,123′)
——————————————————————————–
0891234

when I run the same with in ruby:

p plsql.chrispack.prepare_phone(82,”+49 (89) 1234,123″);

it returns:
“8912345″ (without leading 0)

Is it ruby_plsql behaviour or some ruby issue?

thanks,
chris

I tried your suggested method.
result = plsql.proc_cuid_insert_cuid_detail(‘BBC338′,”,’P5954804′,’TESTING, JA ZOOO’,'LIS’,'QMH’,nil,nil)

Same error occor.
puts result[:raiserror_text].strip
=> “Error in cuid_detail table insertion!ORA-01461: can bind a LONG value only for insert into a LONG column”

I got no problem to execute the same store procedure with same parameters via SQLPLUS.

I think there is a part in somewhere to change the datatype to LONG…but actually my table schema do not have LONG column.. I tried to test with oracle jdbc adapter and your oracle_enhanced adapter. The result is the same…

I have really no idea, and your expertise advice is valuable to me.

Many thanks
Valentino

plsql.proc_cuid_insert_cuid_detail(‘BBC338′, ”, ‘P5954804′, ‘TESTING, TEST ZOOO’,
‘LIS’, ‘QMH’, nil, nil)

This is the main idea of ruby-plsql gem that it provides nice Ruby syntax for PL/SQL procedure calls and you don’t need to do this huge parameter binding. Alternative syntax is to use named parameter hash which would be preferred way if you have so many parameters.

If you get the same error then it would be necessary to identify in which exact place in your procedure this exception is raised – based on error message it complains that bind variable type is not matching table column type.

I got a problem in executing the specific store procedure in oracle via JDBC. But it is no problem to exec other store procedure, and all store procedures are working fine if I use SQLPLUS to connect to the database..

Please check the below link for detail.
http://www.ruby-forum.com/topic/192304

I am using JRuby 1.3.1, ruby-plsql-0.3.1

Please give me some advices

Many thanks
Valentino