Oracle error in PB10

Hi Experts,

We have migrated our PB 8 application to PB10. In our application, we are calling oracle stored procedure, which is part of the package, to get some value. The procedure has around 15 in parameter and 15 out parameters. After migrating to PB 10, while executing the procedure call from front-end we are getting the  following error. But the same procedure works fine in PB 8.

ora 01036: illegal variable name/number

Need experts suggetions/solution on this.

Thanks in advance
Bala


balakarthikeyanAsked:
Who is Participating?
 
sajuksConnect With a Mentor Commented:
Try setting StaticBind and Disable bind "on" in the dbparm page.You should be able to set this in the Database profile setup > transaction tab page.
0
 
sajuksCommented:
Also try setting a dbtrace on to get the actual SQL statement being used.

0
 
Vikas_DixitCommented:
Bala,
Please turn on the DB trace and check what actual statement is fired..

Regards
vikas
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
balakarthikeyanAuthor Commented:
Dear sajuks and vikas
The setting of staticbind and disablebind also did not work.

i set the trace on(Am doing it for the first time)I gave a trace file name in c:\temp\trace1.pbp. a trace has been generated. But how to view it. When it opens in Profiler it says error on settracefilename. Errorcode is FileinvalidFormaterror!

regards
bala
0
 
Vikas_DixitConnect With a Mentor Commented:
To Trun on the DB trace, put TRACE before the DBMS ( you may need to change the config file from where you r taking db connection parameters):

sqlca.DBMS = "TRACE o84" // Normally it will be just o84
sqlca.logid = 'XXX'
sqlca.

CONNECT USING SQLCA

There will be a file pbtrace.log saved in windows directory .. you can see all the sql statements fired from your application logged there.

Check for the call to this sp.

Trun off the profiling as you have mentioned above.

Also I will suggest you go to the sybase site and get the latest patches for PB10.


Regards,
Vikas

0
 
sajuksCommented:
A split would be the proper response. The user was made aware of the different ways he could solve the problem
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.