on 07-16-2013 7:29 AM
Hi,
I receive this message when trying to start an SFC via POD:
Exception occurred while executing Start (Activity ID PR500) (Message 11400)
Does anyone know what exception that could be?
Thanks
Ulrike
In fact, this message is just a wrapper but the root cause error should be checked in defaultTrace log. So, please look into the logs.
Regards,
Sergiy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sergiy,
I checked the log trace, I know what happened, but don't know why it happened. here is the log trace:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
#2.0 #2013 07 17 12:36:40:595#+0200#Info#com.sap.me.trace#
##sap.com/me~ear#C000AC1110360D150000006F000009E0#7732550000000004#sap.com/me~ear#com.sap.me.trace.VM#SITE_ADMIN#127#JTA Transaction : 266474#E177B5BDEECB11E2B71C00000075FD46#fa87d91aeecb11e28da800000075fd46#fa87d91aeecb11e28da800000075fd46#0#Thread[HTTP Worker [@1687977858],5,Dedicated_Application_Thread]#Plain##
[SQL][BaseDataSource].....The following fatal SQL exception has occurred:
select top 100 SFC_STEP.HANDLE ,SFC_ROUTER_BO,USE_AS_REWORK,OPERATION_BO ,STEP_ID,QTY_IN_QUEUE,QTY_IN_WORK,QTY_COMPLETED,QTY_COMPLETE_PENDING,QTY_REJECTED,TIMES_PROCESSED,LOCAL_REWORK ,MAX_LOOP,LAST_WORK_CENTER_BO ,DATE_QUEUED, STEP_SEQUENCE, RESOURCE_OR_CENTER_GBO ,STATE,PREVIOUS_RESOURCE_BO,SFC_STEP.REPORTING_STEP,SFC_STEP.REPORTING_CENTER_BO ,SFC_STEP.SPECIAL_INSTRUCTION,SFC_STEP.PREVIOUSLY_STARTED from SFC_STEP where SFC_ROUTER_BO='SFCRouterBO:SFCRoutingBO:SFCBO:0074,007417,RouterBO:0074,R_TESTING,U,01,1' and SFC_STEP.QTY_IN_QUEUE>'0'
java.sql.SQLSyntaxErrorException: ORA-00923: FROM keyword not found where expected
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I copied the SQL into PL/SQL developer, and it returned the same error message. Then I switched to another ME 6.0 which has completely same build version, but different NetWeaver instance, I tried the same behavior and it succeeded, and the log trace is as following:
##sap.com/me~ear#C000AC111033573B0000006F00000F9C#5938050000000004#sap.com/me~ear#com.sap.me.trace.VM#SITE_ADMIN#1025#JTA Transaction : 1133179#928ADC00EEE111E2CCC90000005A9B82#8ca9ba5feee111e2c4b80000005a9b82#8ca9ba5feee111e2c4b80000005a9b82#0#Thread[HTTP Worker [@467012458],5,Dedicated_Application_Thread]#Plain##
[1]{1} select SFC_STEP.HANDLE ,SFC_ROUTER_BO,USE_AS_REWORK,OPERATION_BO ,STEP_ID,QTY_IN_QUEUE,QTY_IN_WORK,QTY_COMPLETED,QTY_COMPLETE_PENDING,QTY_REJECTED,TIMES_PROCESSED,LOCAL_REWORK ,MAX_LOOP,LAST_WORK_CENTER_BO ,DATE_QUEUED, STEP_SEQUENCE, RESOURCE_OR_CENTER_GBO ,STATE,PREVIOUS_RESOURCE_BO,SFC_STEP.REPORTING_STEP,SFC_STEP.REPORTING_CENTER_BO ,SFC_STEP.SPECIAL_INSTRUCTION,SFC_STEP.PREVIOUSLY_STARTED from SFC_STEP where SFC_ROUTER_BO='SFCRouterBO:SFCRoutingBO:SFCBO:0074,007417,RouterBO:0074,R_TESTING,U,01,1' and SFC_STEP.QTY_IN_QUEUE>'0' and rownum < 100#
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Obvousely, the expection is using the select top 100 statment which is not supported by our Oracle, and the correct one is using rownum < 100 to filter out those 100 records.
I don't understand why same behavior is generating two different SQL statement, can you please advice?
Thanks & regards,
Leon
Hi Ulrike,
There was a relevant fix as per SAP Note 1872632. Please, make sure you have SAP ME 6.0 SP04 patch 8 or 6.1 SP1 patch 5 or 6.1 SP02 Patch 1.
Br, Alex.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.