EBS 問題診斷方法課件_第1頁
EBS 問題診斷方法課件_第2頁
EBS 問題診斷方法課件_第3頁
EBS 問題診斷方法課件_第4頁
EBS 問題診斷方法課件_第5頁
已閱讀5頁,還剩43頁未讀 繼續(xù)免費閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進行舉報或認領(lǐng)

文檔簡介

EBS問題診斷方法EBS問題診斷常用方法--OracleSSC--AndrewDuEBS問題診斷方法TopicsHowToGetLevel12TraceHowToGetTraceConcurrentPrograms?HowtogetFormsLevelTraceandFRD?HowToGetFNDDebug?HowToRunSelectedGeneralLedgerProgramsInDebugModeinR11.5?HowToStoreFADebugMessagesInAFile?HowtoGetaDebuginReceivablesin11.5.10?HowtorunaPayablesConcurrentPrograminDebugMode?HowtogenerateadebugOM?HowtoGenerateandReturnthePODocumentApprovalManagerTraceDebugDataHowtoGenerateReceivingTransactionDebugStatementsin11.5.10andR12?HowToDebugWIP?HowtogetDebugInformationforInventoryMaterialTransaction?EBS問題診斷方法HowToGetLevel12Trace?

為什么需要Trace?

提取執(zhí)行與錯誤信息獲取執(zhí)行程序/SQL獲取執(zhí)行計劃與成本信息獲取綁定變量值獲取等待事件等EBS問題診斷方法HowToGetLevel12Trace?

Gathering10046trace

SQL_TRACE是Oracle數(shù)據(jù)庫提供的用于進行SQL跟蹤的手段,在某種意義上講,可以說是Oracle最強有力的輔助診斷工具。10046事件是Oracle提供的內(nèi)部事件,是對SQL_TRACE的增強(包含綁定值與等待事務(wù)事件)10046事件可以設(shè)置以下四個級別:1-啟用標準的SQL_TRACE功能,等價于sql_trace4-Level1加上綁定值(bindvalues)8-Level1+等待事件跟蹤12-Level1+Level4+Level8EBS問題診斷方法HowToGetLevel12Trace?

在EBS中啟用10046trace切換到<系統(tǒng)管理員>職責Navigate:SystemAdministrator>Profile=>System在用戶層查詢pro'InitializationSQLStatement-Custom'.User:UsersubmittingtheprocessProfile:InitializationSQLStatement-Custom編輯User字段,輸入下列值并保存beginfnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTERSESSIONSETEVENTS='||''''||'10046TRACENAMECONTEXTFOREVER,LEVEL12'||'''');end;EBS問題診斷方法HowToGetLevel12Trace?

SessionTracingaltersessionsettrace'10046';altersessionsettimed_statistics=true;altersessionsetstatistics_level=all;altersessionsetmax_dump_=unlimited;altersessionsetevents'10046tracenamecontextforever,level12';altersessionsetevents'10046tracenamecontextoff';EBS問題診斷方法HowToGetLevel12Trace?

TraceotherSession

OpenTraceexecsys.dbms_system.set_ev(<sid>,<serial#>,10046,12,'');CloseTraceexecsys.dbms_system.set_ev(<sid>,<serial#>,10046,0,'');EBS問題診斷方法HowToGetLevel12Trace?SQLTracepathshowparameteruser_dump_destselect*fromv$parameterwherenamelike'user_dump_dest'EBS問題診斷方法HowToGetLevel12Trace?

Whattolookforinthetrace?

RollbackErrorSelectreturningnorows(forORA-01403errors)CalltostoredproceduresExecstatements(lastexeccompletedpriortorollback)ForhandledexceptionslookforcallstocodethatthrowserrormessageEBS問題診斷方法HowToGetLevel12Trace?

HowtoreadaRawTrace(note39817.1)CaseStudy:ORA-01403NoDataFoundPARSE#198:c=0,e=60,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=4,tim=10842EXEC#198:c=0,e=423,p=0,cr=0,cu=20,mis=0,r=0,dep=1,og=4,tim=11382RPCEXEC:c=530000,e=1892352RPCCALL:PROCEDUREAPPS.ARP_STANDARD.DEBUG(LINEINVARCHAR2);RPCBINDS:bind0:dty=1bfp=0ae65b50flg=08avl=54mxl=54val="01:42:27-arxtwmai_form_main.arxtwmai_main(ON-ERROR)+"PARSINGINCURSOR#92len=16dep=0uid=173oct=45lid=173tim=16729hv=2670021379ad='60292bf0'ROLLBACKTOFM_1ENDOFSTMTLastStatemExecutedEntBeforeRollbackFindRollbackEBS問題診斷方法HowToGetLevel12Trace?

Howtoreadarawtrace(cont.)PARSINGINCURSOR#198len=2959dep=1uid=173oct=3lid=173tim=14177hv=3671187712ad='63528a1c'SELECTcm.customer_trx_line_id,cm.previous_customer_trx_line_id,….WHEREcm.previous_customer_trx_line_id=:b0BINDS#198:bind0:dty=11mxl=16(16)mal=00scl=00pre=00oacflg=18oacfl2=1size=16offset=0bfp=40cd29e8bln=16avl=16flg=05value=254825ExecstatementsFindBindvaluesSearchfor“BINDS”

statementEBS問題診斷方法HowToGetLevel12Trace?

RawTrace+Understanding=RootCauseInthepriorexample:TheformthrewanORA-01403nodatafoundCursor#198wasthelaststatementexecutedpriortorollbackandreturnednorows(causeofORA-1403error)SQLbelongingto#198identifiedtheselectstatementIDbelongingtotransactionthatfailedwaslistedasabindNextsteps:DrilldowntothecodeleveltoinvestigatetheissueTARrelated,uploadtheRAWandTKProftracefilesEBS問題診斷方法TracetoolTkprofcommandtkproftrace[explain=user/password][options...]TkprofOptionsprint=integerListonlythefirst'integer'SQLstatements.insert=ListSQLstatementsanddatainsideINSERTstatements.sys=noTKPROFdoesnotlistSQLstatementsrunasuserSYS.record=Recordstatementsfoundinthetracefile.sort=optionSetofzeroormoresortoptionsEBS問題診斷方法Trace

(TKProfInterpretation)TKProfoutputstructureSQLStatementParse/Execute/FetchstatisticsandtimingsLibraryCacheinformationRowsourceplanEventswaitedforbythestatementEBS問題診斷方法Trace

(TKProfInterpretation)EBS問題診斷方法HowToGetTraceConcurrentPrograms?在并發(fā)程序定義中啟用<EnableTrace>選項

SystemAdministrator->Concurrent->Program->DefineEBS問題診斷方法HowToGetTraceConcurrentPrograms?SetProfile<Concurrent:AllowDebugging>enabledhighleveltraceEBS問題診斷方法TopicsHowToGetLevel12TraceHowToGetTraceConcurrentPrograms?HowtogetFormsLevelTraceandFRD?HowToGetFNDDebug?HowToRunSelectedGeneralLedgerProgramsInDebugModeinR11.5?HowToStoreFADebugMessagesInAFile?HowtoGetaDebuginReceivablesin11.5.10?HowtorunaPayablesConcurrentPrograminDebugMode?HowtogenerateadebugOM?HowtoGenerateandReturnthePODocumentApprovalManagerTraceDebugDataHowtoGenerateReceivingTransactionDebugStatementsin11.5.10andR12?HowToDebugWIP?HowtogetDebugInformationforInventoryMaterialTransaction?EBS問題診斷方法HowtogetFormsLevelTraceandFRD?

WhatisFRD?

FRDisFormsRuntimeDiagnosticsTheFormsRuntimeDiagnostics(FRD)loggingmechanismwasintroducedinForms4.5.10,andisakeytoolforinvestigatinganddebuggingFormsproblems.Whenenabled,itlogseveryuseraction,everytriggerthatfires,everyformsbuilt-incalled,andvaluechanges(deltas)ofFormsitems

EBS問題診斷方法HowtogetFormsLevelTraceandFRD?1.在用戶層設(shè)置pro

'ICX:FormsLauncher'e.g.updatethevalueof

ICX:FormsLauncherfortheusertobe

?play=&record=collect&log=/tmp/GW0097_frd.log2.用戶重新登錄系統(tǒng),并獲得啟用FormRuntimeDiagnostics的提示信息.

3.完成測試后,在應(yīng)用服務(wù)器的下列路徑$FORMS60_TRACE_PATH找到debug文件Note:thedefaultdirectoryfor

$FORMS60_TRACE_PATHis$ORACLE_HOME/forms60/log.$FORMS_TRACE_DIREBS問題診斷方法HowtogetFormsLevelTraceandFRD?EBS問題診斷方法HowtogetFormsLevelTraceandFRD?FRDlogoutputEBS問題診斷方法HowtogetFormsLevelTraceandFRD?在Form中啟用TraceFormsleveltraceisSQLtracegeneratedbeforethetransactionissavedonaform.ItisenabledfromtheformandcapturesSQLcoderelatedtotheexecutionoftheform.

ThisshouldbeusedwhentheerroroccursontheformBEFOREclickingonthesave.

TypicallytheseareFRMorAPPerrorsbuttherecouldbeothervaryingerrormessages.

啟用步驟:Navigatetothepointintheapplicationrightbeforeyouareexperiencingtheproblem.

Turntraceonby:Help>Diagnostics>Trace>TracewithBinds(Mayrequirepassword)Apop-upmessagewithtraceandnamewillbedisplayed.Notetheandpath.Duplicatetheerrorandthenstopimmediatelyafterwards.

Help>Diagnostics>Trace>NoTrace

生成的Tracefile存在在數(shù)據(jù)庫服務(wù)器user_dump_dest對應(yīng)的目錄中,可使用下列SQL找到具體路徑selectvaluefromV$PARAMETERwherenamelike'user_dump%';

使用tkprof命令解析Trace信息:

tkprof<>.trc<>.outexplain=<foundusername/password>

example:tkprofexplain=<apps/apps>EBS問題診斷方法HowtogetFormsLevelTraceandFRD?EBS問題診斷方法HowToGetFNDDebug?切換到系統(tǒng)管理員職責:Navigate:SystemAdministrator>Profile=>System在用戶層查找FNDproforUserwhoissubmittingtheprocesstodebug.User:UsersubmittingtheprocessProfile:FND:%Debug%在用戶層設(shè)置下列Pro并保存FND:DebugLogEnabled:YesFND:DebugLogLevel:STATEMENTFND:DebugLogModule:%

EBS問題診斷方法HowToGetFNDDebug?EBS問題診斷方法HowToGetFNDDebug?1.在執(zhí)行前臺功能操作執(zhí)行操作前,執(zhí)行下列SQL,SELECTMAX(log_sequence)fromfnd_log_message;完成操作后,執(zhí)行下列SQL查看Debug輸出:selectlog.message_text,log.module

fromfnd_log_messageslog

whereuser_id=&user_id

andlog_sequence>&max_logsequenceorder

bylog.log_sequence;2.執(zhí)行并發(fā)請求,在日志中檢查輸出信息;EBS問題診斷方法HowToGetFNDDebug?EBS問題診斷方法HowToRunSelectedGeneralLedgerProgramsInDebugModeinR11.5

在用戶層設(shè)置pro“GL:DebugMode”為Yes.下列程序?qū)a(chǎn)生debug信息

GLCRVL-RevaluationGLPPOS-PostingGLTTRN-TranslationGLCCON-ConsolidationTransferGLAMAS-RunMassAllocationsEBS問題診斷方法HowToStoreFADebugMessagesInAFile?1.執(zhí)行下列SQL,查詢debugfile存放目錄value(eg:/volume/d1/tmp_hpoc):selectvaluefromv$parameterwhereupper(name)='UTL_';在用戶設(shè)置下列pro

FA:PrintDebugtoYesFA:Debug,pleasepastethepathreturnedfromtheabovequeryEBS問題診斷方法HowtorunaPayablesConcurrentPrograminDebugMode?

1.LogintoSystemAdministratorresponsibility.2.NavigatetoConcurrent-Program-Define.3.QueryfortheConcurrentProgramName-PayablesAccountingProcess.4.ClickontheParametersbutton.5.ClickinthelinewiththeparameterDebug.6.ChecktheEnablebox.7.ChecktheDisplaybox.8.Save.9.ChooseYesfortheParameterDebugwhenrunPayablesAccountingProcess.TheLogtheDebugInformation.EBS問題診斷方法HowtorunaPayablesConcurrentPrograminDebugMode?EBS問題診斷方法HowtoGetaDebuginReceivablesin11.5.10?在用戶層設(shè)置下列Pro:FND:DebugLogEnabled=YESFND:DebugLog=NULLFND:DebugLogLevel=STATEMENT(mostdetailedlog)FND:DebugLogModule=%orar%AR:EnableDebugMessageOutput=YESCheckDebug1.在執(zhí)行前后功能操作前在SQLPlus中執(zhí)行下列SQL,SELECTMAX(log_sequence)fromfnd_log_messages;2.完成操作后,執(zhí)行下列SQL查看Debug輸出:SELECTLOG.MESSAGE_TEXT,LOG.MODULEFROMFND_LOG_MESSAGESLOGWhereuser_id=&user_idandlog_sequence>&max_logsequenceORDERBYLOG.LOG_SEQUENCE;EBS問題診斷方法HowtoGetaDebuginReceivablesin11.5.10?AR模塊的下列forms可啟用特殊的Debug.Transactionsworkbench(ARXTWMAI)Receiptsworkbench(ARXRWMAI)Collections(ARXCWMAI)

啟用步驟1.SetPro(同上一頁)2.Onthemenu,clickhelp/diagnostic/examine(11.5)3.Changeblockfield,thenchoosefromthelistofvalues:PARAMETER4.Forthefield,thenTYPEin:AR_DEBUG_FLAGThereisnoLOVforthisfield.ExplicitlytypeinAR_DEBUG_FLAG.5.Forthevalue,thenTYPEin:FS<path><file>(example:FS/volume/d1/tmp_hpoc2010debug.log)Path設(shè)置可使用下列SQL的輸出值:selectvaluefromv$parameterwhereupper(name)='UTL_';6.Debugfile生成數(shù)據(jù)庫服務(wù)器EBS問題診斷方法HowtoGetaDebuginReceivablesin11.5.10?EBS問題診斷方法HowtogenerateadebugOM?A.在SalesOrdersform中生成Debug信息:1.在用戶層設(shè)置下列Pro:OM:DebugLevel–設(shè)置為5OM:DebugLogDirectory–(e.g:/volume/d1/tmp_hpoc),執(zhí)行下列SQL查找數(shù)據(jù)庫服務(wù)器路徑

selectvaluefromv$parameterwherename=‘UTL_'2.打開Order工作臺FromgotoTools->Debugandgetnotemessage(e.g.ThelogXXX).EBS問題診斷方法HowtogenerateadebugOM?B.在并發(fā)請求中獲得debug信息:在用戶層設(shè)置proOM:DebugLevelto5.Debug信息將生成并發(fā)請求的log文件.

在并發(fā)請求的log文件中查看debug信息NavigatetoView>Requests>ReleventRequest_id(button).ClickViewOutput>Save"".EBS問題診斷方法HowtoGenerateandReturnthePODocumentApprovalManagerTraceDebugData1.在OraclePurchasing的應(yīng)用層設(shè)置下列pro:Name:InitializationSQL-CustomValue:beginfnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTERSESSIONSETEVENTS='||''''||'10046TRACENAMECONTEXTFOREVER,LEVEL12'||'''');end;

Name:PO:SetDebugWorkflowONValue:YesName:PO:SetDebugConcurrentONValue:Yes2.設(shè)置并發(fā)管理器DocumentManagerprocesses為13.清理tracefile文件目錄

和表po_wf_debugNote:Makesurethemaximumtraceissettounlimited4.啟動并發(fā)管理器DocumentManagerprocess.EBS問題診斷方法HowtoGenerateandReturnthePODocumentApprovalManagerTraceDebugData推薦的附加診斷數(shù)據(jù):wfstat.sqlandwfstatus.sqloutputsoftheapprovalpo_wf_debugtablecontent檢查Debug信息selectitemtype,itemkey,execution_sequence,debug_messagefrompo_wf_debugwhereitemtype='&ItemType'anditemkey='&ItemKey'orderbyexecution_sequence;檢查并發(fā)管理器日志信息Sysadmin=>Concurrent=>Managers=>Administration=>PODocumentManager=>Processes=>Active=>ManagerlogEBS問題診斷方法HowtoGenerateReceivingTransactionDebugStatementsin11.5.10andR12Profile設(shè)置1.Alltransactions:a.RCV:DebugMode=Yesb.FND:DebugLogEnabled=Yesc.FND:DebugLogLevel=Statementd.FND:DebugLogModule=%

注:可參考FNDDebug設(shè)置和debug信息讀取2.LinetobetransactedreferencesanItem:a.TP:INVTransactionprocessingmode=On-lineb.INV:DebugTrace=Yesc.INV:DebugLevel=11d.INV:Debugfile(Includingthecompletepath)=<validdirectorypathplus>

注:可參考InventoryMaterialTransactionsDebug設(shè)置EBS問題診斷方法HowtoGenerateReceivingTransactionDebugStatementsin11.5.10andR123.RMA,DropShipPurchaseOrderorInternalSalesOrder/Requisition:a.OM:DebugLevel=5b.OM:DebugLogDirectory=<validdirectorypath>注:可參考OMdebug設(shè)置

4.RCV:ProcessingMode=ImmediateorBatch:PO:EnableSqlTraceforReceivingProcessor=Yes

說明:此設(shè)置將為并發(fā)請求<ReceivingTransactionProcessor>生成TraceFileEBS問題診斷方法HowToDebugWIP用戶層Pro設(shè)置及debug信息讀取1.FND:DebugLogEnabled=Yes2.FND:DebugLogLevel=Statement3.FND:DebugLogModule=WIP%selectmessage_textfromfnd_log_messageswhereaudsid=(selectoracle_session_idfromfnd_concurrent_requestswhererequest_id=&MOVE_TRNX_WORKER_REQUEST_ID)orderbylog_sequence;EBS問題診斷方法HowtogetDebugInformationforInventoryMa

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負責。
  • 6. 下載文件中如有侵權(quán)或不適當內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準確性、安全性和完整性, 同時也不承擔用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

最新文檔

評論

0/150

提交評論