Pretty sure you won't be able to do that. The Oracle JDBC examples require you to register the parameter as oracle.jdbc.OracleTypes.CURSOR, which is not available in Ignition. (Only generic JDBC types are supported in Ignition--the actual drivers are in isolated classloaders in order to make connection pooling transparent.)
You'll probably have to wrap that procedure with another that explicitly SELECTs from that cursor. (Looks complicated--wrapping in a TABLE() function somehow. I've not used Oracle in years....)