ORACLE error 6502 in FDPSTP

3482623 wrote:

 

Hello All,

 

we are getting

ORACLE error 6502 in FDPSTP

Cause: FDPSTP failed due to ORA-06502: PL/SQL: numeric or value error: character string buffer too small

ORA-06512: at line 1

 

Procedure:

CREATE OR REPLACE PROCEDURE p_test1 (p_in_report_name IN VARCHAR2,

p_in_responsibility IN VARCHAR2,

p_in_email IN OUT CLOB)

IS

l_exc_custom_exception EXCEPTION;

l_chr_attachment_name VARCHAR2 (100);

l_chr_email_body VARCHAR2 (2000);

l_in_email CLOB;

BEGIN

l_in_email := 'abc@google.com' || ',' || 'def@google.com';

p_in_email := p_in_email || l_in_email;

 

 

IF p_in_report_name = 'Report1'

THEN

l_chr_email_body := 'Details of the report';

 

 

l_chr_attachment_name := 'Report1';

END IF;

EXCEPTION

WHEN l_exc_custom_exception

THEN

DBMS_OUTPUT.put_line ('User Defined Exception => ' || SQLERRM);

WHEN OTHERS

THEN

DBMS_OUTPUT.put_line (

'Error while submitting request for Error While running email program. Error=> '

|| SQLERRM);

END p_test1;

 

Error:

ORACLE error 6502 in FDPSTP

Cause: FDPSTP failed due to ORA-06502: PL/SQL: numeric or value error: character string buffer too small

ORA-06512: at line 1

 

please suggest.

 

Thanks

how can we reproduce what you report?

I don't see how code you posted can throw the error you reported.

Please click on URL below & respond accordingly

Re: 2. How do I ask a question on the forums?

Code Analysis

It looks like you are "barking up the wrong tree".

• None of your EXCEPTIONS are calling RAISE/RAISE_APPLICATION_ERROR
• One EXCEPTION is the all-inclusive WHEN OTHERS (ie all errors will always hit one of the EXCEPTION blocks)
• Applications will never receive an error from this code.
• The DBMS_OUTPUT lines within the EXCEPTIONS do not match the error shown.

conclusion:

You have a bug in FDPSTP.  (the code you DIDN'T post)

MK

If you GOOGLE what I did (aka What is FDPSTP in Oracle) you'll get TONS of links:

(this is an Oracle EBS application's issue)

1. OraFAQ Forum: Forms » ORACLE error 6550 in FDPSTP
2. https://stackoverflow.com/questions/11802076/cause-fdpstp-failed-due-to-ora-06550-line-1-column-7pls-00221-is-not-a-proc
3. Solved: ORACLE error 6550 in FDPSTP - OracleMine.com
4. Manoj Reddy Oracle Applications Blog: Solution for ORACLE error 6550 in FDPSTP
   

As per the Developers Guide (https://docs.oracle.com/cd/E18727_01/doc.121/e12897/T302934T458252.htm#4163756), all stored procedure concurrent programs require the mandatory errbuf and retcode parameters.

Stored Procedure Concurrent Programs

You can implement your concurrent program as a stored procedure. Beginning with Release 11, file I/O operations are supported for stored procedures.

A benefit of developing your concurrent program as a stored procedure is that it runs as part of the concurrent manager's database connection and does not cause an additional process to be spawned, as do other concurrent processing execution methods. Therefore, the “Stored Procedure" execution method is appropriate for frequently-executed concurrent programs (including those you develop to replace immediate concurrent programs from prior releases of Oracle E-Business Suite).

Stored procedure concurrent programs accept input parameters only, and are submitted with the FND_REQUEST package. Following is an example specification of a PL/SQL procedure you could create to run as a concurrent program:

REM /* Beginning of SQL Script */ REM CREATE PROCEDURE FND60.SAMPLE_PROC (ERRBUF    OUT VARCHAR2, RETCODE   OUT VARCHAR2, ARGUMENT1 IN VARCHAR2, ARGUMENT2 IN VARCHAR2, ARGUMENT3 IN VARCHAR2, . . . . ARGUMENT100 IN VARCHAR2, ) 

Your stored procedure concurrent program is restricted to 100 parameters in addition to the first two parameters, which are required and must be specified exactly as indicated in the example above. (You must take these two parameters into account when you create your stored procedure.) Use errbuf to return any error messages, and retcode to return completion status. The parameter retcode returns 0 for success, 1 for success with warnings, and 2 for error. After your concurrent program runs, the concurrent manager writes the contents of both errbuf and retcode to the log file associated with your concurrent request.

Important: You should restart your concurrent managers whenever you create or reinstall a stored procedure concurrent program.

3482623 wrote:

 

thanks all.. got it resolved. thanks for valuable inputs.

Then mark whomever gave you the correct reply as the right answer by marking it ANSWERED

How did you resolve this issue? I am having the same issue with one of my Concurrent program

Please post the code for your custom program.

Sorry, the comment was directed at the user user9948901 who also had the issue.