2

Can't got the problem,that reproduced on my environment.

Result of running PL/SQL procedure on my PC on Eclipse SQL Explorer:

ORA-06502: PL/SQL: numeric or value error: character string buffer too small

If this procedure compiled on other PC on Eclipse SQL Explorer also,that all is OK.

note: If you ask,why Eclipse SQl Explorer - its' historical issue,because procedure isn't compiled under Oracle Sql Developer.

What is problem in my environment?

Thank you.

10
  • is the input data the same in both cases? This error normally means your code is attempting to assign a string to a variable that is too small for it.. Commented Jun 1, 2011 at 10:58
  • @StevieG absolutely identical procedures and their input params for run. The only difference,that if proc. compiled from other PC,that there is no such error.Perhaps,some SQL Explorer settings? Commented Jun 1, 2011 at 11:03
  • Are you getting the error when compiling, or running the proc? Would be useful if you could post the code.. Commented Jun 1, 2011 at 11:05
  • getting error when running only,compilation is OK,procedure size is more than 1K lines Commented Jun 1, 2011 at 11:07
  • I'm stumped, then.. The procedure is running on the database, so it shouldn't matter what your SQL explorer settings are. Is the database hosted locally on your machines? Commented Jun 1, 2011 at 11:18

3 Answers 3

2

You need to look for a significant difference in the client environments. For instance, do they have different settings for NLS_LANG? This could matter if you're using a multi-byte character or Unicode character set in your database.

Sign up to request clarification or add additional context in comments.

1 Comment

thank you, for now I'm out of this task,anyway keep it in mind
1

There's an optimization level for PL/SQL procedures. Could be one of your environments is compiling in 'normal' mode and the other in 'debug' mode.

Check the settings for that object in ALL_PLSQL_OBJECT_SETTINGS

Comments

1

Does your code use the DBMS_OUTPUT package? Maybe you have a small limit on DBMS_OUTPUT. Try and increase the size to the maximum allowed (32767).

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.