Home » SQL & PL/SQL » SQL & PL/SQL » Urgent: DBMS_SQL.PARSE - Raising ORA-01009: missing mandatory parameter (Oracle 11g (11.1.0.6.0))
Urgent: DBMS_SQL.PARSE - Raising ORA-01009: missing mandatory parameter [message #301064] Tue, 19 February 2008 02:04 Go to next message
shasikkumar
Messages: 8
Registered: February 2008
Location: India
Junior Member
Hi all,

In my PLSQL program unit while executing the DBMS_SQL.PARSE - I am getting the following error while running the PLSQL program (No Compilation Errors)
ORA-01009: missing mandatory parameter

The following is the exact statement in my PLSQL program unit,

DBMS_SQL.PARSE(CURSOR_NAME ,G_RULE_SOURCE ,G_RULE_START,G_RULE_END ,FALSE,DBMS_SQL.V7);

I have opened the cursor prior to this statement using CURSOR_NAME := DBMS_SQL.OPEN_CURSOR;

G_RULE_SOURCE has the value of 1
G_RULE_START has the value of 1
G_RULE_END has the value of 1

Please let me know - If this problem is specific in 11g - Experts please advice !!

Thanks,
Shasi




Re: Urgent: DBMS_SQL.PARSE - Raising ORA-01009: missing mandatory parameter [message #301068 is a reply to message #301064] Tue, 19 February 2008 02:14 Go to previous messageGo to next message
Michel Cadot
Messages: 64140
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Where is the statement you want to parse?

Regards
Michel
Re: Urgent: DBMS_SQL.PARSE - Raising ORA-01009: missing mandatory parameter [message #301206 is a reply to message #301064] Tue, 19 February 2008 10:03 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8636
Registered: November 2002
Location: California, USA
Senior Member
1 is not a legitimate value for g_rule_source. G_rule_source should be the sql statement that you want to parse.
Re: Urgent: DBMS_SQL.PARSE - Raising ORA-01009: missing mandatory parameter [message #301212 is a reply to message #301206] Tue, 19 February 2008 10:27 Go to previous message
shasikkumar
Messages: 8
Registered: February 2008
Location: India
Junior Member
Hi,

Sorry in the debug, I had taken a count of VARCHAR array by mistake and posted in the forum.

Actually, we frame the SQL statement processing through a loop. But unfortunately in my case, the loop is iterated only once due to some failure rendering the variable array to hold the sql statement as null.

Hence the error.

I checked the condition based on which iteration is happening and rectified it. Now it works fine.

Thanks,
Shasi
Previous Topic: A query related to Collapsing nulls /pivoing of data
Next Topic: Invalid number error when trying to retrieve numeric data from varchar2 columns.
Goto Forum:
  


Current Time: Fri Dec 09 03:43:32 CST 2016

Total time taken to generate the page: 0.18181 seconds