How many optional allowed in the query?

Question

Hi,
Data base is getting disconnected while running the below sparql query (Query with 9 optional conditions).
I tested the query with 5 optional its working fine but, its not working for more than 5 optional.
How many optional allowed in the query?
Please advice me to solve this problem.
Error Detail: ORA-03113: end-of-file on communication channel
SELECT bi, OWNER,name,usage,notes,icto,app,ssd,ssdname,ssdid,sdname,sdarchitect,schedule
FROM TABLE (sem_match('{
?bi rdf:type di:Bulk_Interface .
?bi di:hasBulkInterfaceItOwner ?OWNER .
?bi di:hasBulkInterfaceName ?name .
?bi di:hasBulkInterfaceRecipientApplicationArea ?usage .
?bi di:hasBulkInterfaceRecipientFeederType ?notes .
?bi di:hasBulkInterfaceSupplierApplicationId ?icto .
?app ds:hasConceptualSourceApplicationIctoId ?icto .
?ssd ds:hasConceptualSourceApplication ?app .
?ssd ds:hasConceptualSourceSubdomainName ?ssdname .
?ssd ds:hasConceptualSourceSubdomainIctoId ?ssdid .
?sd ds:hasConceptualSourceSubdomain ?ssd .
?sd ds:hasConceptualSourceDomainName ?sdname .
?sd ds:hasConceptualSourceDomainArchitect ?sdarchitect .
?bi di:hasBulkInterfaceDeliverySchedule ?schedule
optional {?bi di:hasBulkInterfaceRecSet1AverageStorageRequirements ?avgsize}
optional {?bi di:hasBulkInterfaceWorstStorageRequirements ?maxsize}
optional {?bi di:hasBulkInterfaceRecSet1AverageNumberOfRecords ?avgrec}
optional {?bi di:hasBulkInterfaceAverageNumberOfRecords ?avgrec}
optional {?bi di:hasBulkInterfaceRecSet1WorstNumberOfRecords ?maxrec}
optional {?bi di:hasBulkInterfaceWorstNumberOfRecords ?maxrec}
optional {?bi di:hasBulkInterfaceTransferMethodJob ?job}
optional {?bi di:hasBulkInterfaceDataFileAvailability ?post}
optional {?bi di:hasBulkInterfaceBusinessDescription ?descr}
sem_models ('IFM_CURR', 'SRC_CURR'),
SEM_Rulebases('OWLPRIME'),
sem_aliases(SEM_ALIAS('di','http://www.cse.com/sbip/dwh/mdm/data_interface#'),
SEM_ALIAS('ds','http://www.cse.com/sbip/dwh/mdm/data_sources#'))
, NULL));
Let me know if you need any other details.
Regards,
Kavitha.
Edited by: 789259 on Aug 3, 2011 2:01 AM

Answer 1

If possible, I would suggest that you upgrade to the latest release: 11.2.0.2.0. It has many bugfixes and enhancements.
There is no limit on the number of optionals per query. I suspect that the use of the same new variables (?avgrec and ?maxrec) in the parallel optional clauses is the reason you are seeing the error in this particular case. If you use different variable names does the error go away? If needed, you can use a coalesce in the outer SQL SELECT to get the same behavior as before (e.g. COALESCE(avgrec1, avgrec2) as avgrec).
Thanks,
Matt