ITPub博客

XXSUP和XXDEV从同一个产品环境克隆过来。Form XXUTS_BULK_RECEIVE.fmb上传到XXSUP中编译通过，而上传到XXDEV中编译时出现错误。编译命令：$cd $XXUTS_TOP/forms/US$frmcmp_batch module=XX_BULK_RECEIVE.fmb userid=apps/****** output_file=XXUTS_BULK_RECEIVE.fmx错误：............Compiling package body APP_CUSTOM...No compilation errors.Compiling package body XXUTS_BUTTON_ACTION...Compilation error on package body XXUTS_BUTTON_ACTION:PL/SQL ERROR 49 at line 441, column 9bad bind variable 'parameter.G_query_find'

最近经常碰到这个等待事件，贴个metalink上的有用文档上来。Doc ID: 163424.1[@more@]Goal How to identify blocks which cause latch contention on the 'cache buffers chains' latch. How to identify a hot block within the database buffer cache. Solution Possible hot blocks in the buffer cache normally can be identified by a high or rapid increasing wait count on the CACHE BUFFERS CHAINS latch. This latch is acquired when searching for data blocks cached in the buffer cache. Since the Buffer cach

用户登录EBS系统后点击“Launch Discoverer Plus”， 结果出现空白页，无任何其他提示。[@more@]经核实:-1. 其他用户启动Discoverer Plus时正常2. 该用户在其他PC上启动时也正常基本确定问题出在客户的PC上。参照 Metalink文档 332748.1，做如下操作:-1. 删除所有IE的cookie和临时文件2. 在IE publishers中删除所有oracle相关项 (IE options -> Content Tab -> Under Publishers)3. 启动控制面板 -> 添加/删除程序，删除所有JRE (Java Runtime Environment)重启PC,解决。

EBS界面提示的错误信息:- Fatal error: Please have your system administrator view the bne.log file. oracle.apps.bne.exception.BneFatalException: A system error has occurred. Have your system administrator view the bne.log file. Please contact your support representative.[@more@]View the detail of Bne.log ( Found in location defined by profile option 'BNE Server Log Path' )

ORACLE EBS中打补丁是一个比较简单的过程，用“adpatch options=hotpatch”可以在线打，但还是有些需要注意的地方。 1. 如果你的系统出了支持英语外，还支持其他语言，比如中文，那你在下载补丁的时候除了下载Generic Platform版本外，还要确认有没有其他语言的版本,比如ZHS版本。如果有的话也要下载。 2. EBS的补丁不像数据库的补丁那样可以回滚，一旦失败就很麻烦。所以打补丁前一定要细看readme文件，确认补丁所需的前提条件都满足。 3. 要记录和对比打补丁前后APPS Schema下的无效对象。如果因为补丁引起新的无效对象，则视为补丁失败

也可以参照http://zhyuh.itpub.net/post/334/485841两种方法都是Oracle supporter在解答TAR中提供的[@more@] 1. Enable trace for a specific user:- Login as System Administrator responsibility- Move to Profile/System- Check off the USER box - and enter your username that you are using when getting the error- Search on the following profile option - 'Initialization SQL Statement - Custom'2. Please set this at the user level with the following string:BEGIN FND_CTL.FND_SESS_CTL('','', '', 'TRUE','','ALTER

ORACLE EBS R12中引入了XML Publisher，Oracle Application Framework等新东西，利用网页/JSP技术增强Form/Report等的功能和表现力。当运行网页出现错误时，ORACLE经常会出现如下抽象的提示:-You have encountered an unexpected error. Please contact the System Administrator for assistance.[@more@]用下面的步骤可以让系统显示详细的错误信息1. Set below profiles: FND: Diagnostics = Yes FND: Message Level Threshold = "Debug High" 2. Re-produce the error. The error message would be:You have encou

由于某些权限的限制，有时候哪怕System Administrator职责也只能看到某个Request信息，但是不能查看它的Output File（在“Requests Summary”窗口中“View Output”键显示灰色）。[@more@]select fnd_webfile.get_url(4,20378779,'APPLSYSPUB/PUB','FCWW',10) from dual第一个参数4表示request的output,第二个参数是request_id第四个参数是two_task,第五个参数是url有效的分钟数. 然后就是把这个url复制到ie就可以了.

用户访问ORACLE DISCOVERER时出现如下错误:-The server is running low on virtual memory. This can happen due to insufficient disk space or heap space on the server. Please contact your Discoverer Administrator for assistance.[@more@]解决办法如下==加大所有DISCOVERER用户的内存参数try to increase the MaxVirtualDiskMem and MaxVirtualHeapMem sizes in $ORACLE_HOME/discoverer/util/pref.txt.==加大某个用户的内存参数==dis51pr -user TEMP01@INSTANCE -setpref "Application" "MaxVirtualHeapMem&quot

ORACLE EBS系统中有时会出现如下错误:-Request 2726233 in INSTANCE1 failed with ORA-00903. The log file suggests to 'consult the OPP service log for details'。这时需要查看OPP Service Log找到详细的错误信息。[@more@]1. Concurrent -> Manager -> Administer2. Search for 'Output Post Processor'3. Select the processor that was active when the request ran and click the 'Manager Log' button参照 http://johanlouwers.blogspot.com/2007/10/oracle-finding-opp-service-log.html

Trace文件在数据库服务器的udump目录下。另外跟踪完用户的操作后记得及时关闭该功能。[@more@]1. Navigate Responsibility: System Administrator > Profile > System >QueryUser: XXXXProfile: FND:%Debug%2. Set the following Profile values at the user levelFND: Debug Log Enabled => YesFND: Debug Log Filename for Middel-Tier => <empty>FND: Debug Log Level => STATEMENTFND: Debug Log Mode => Asynchronous with Cross-Tier SequencingFND: Debug Log Module => %

把报表sales by contract挂到XXSC PLG GL Inquiry职责下[@more@]1. Login as "System Administrator"2. Security -> Resonsibility -> Define3. Find the Request Group 'GL Concurrent Program Group' mapping to 'XXSC PLG GL Inquiry' responsibility4. Open Request Groups window, add 'Sales By Contract Report' program to 'GL Concurrent Program Group' request group

编译EBS的form 和 .pll文件[@more@]编译FORM$frmcmp_batch module=$AU_TOP/forms/ZHS/ZXTRXSIM.fmb userid=apps/****** output_file=$ZX_TOP/forms/ZHS/ZXTRXSIM.fmx module_type=form batch=no compile_all=special编译.pll文件$cd $AU_TOP/resource$frmcmp_batch module=JAINSTFM.pll userid=apps/****** output_file=JAINSTFM.plx module_type=library batch=no compile_all=special

ORACLE EBS的Request和后台数据库Session通过apps.fnd_concurrent_requests.oracle_process_id字段和v$process.spid字段关联。[@more@]下面的SQL可以根据Request ID找到对应的Session信息:-select *from v$sessionwhere paddr in (select addr from v$process where spid = (select b.oracle_process_id from apps.fnd_concurrent_requests b where b.request_id = &req_number))或者进一步找到正在运行的SQL:-select sql_textfrom v$sqltext_with_newlineswhere hash_value in (select SQL_HASH_VALUE from v$session

给用户A赋了XXX职责，用户A用XXX职责登录时却出现如下错误信息：XXX is not a valid responsibility for the current user. Please contact your System Administrator.[@more@]这一般是由Application Server或用户IE的过期cache引起的，建议用户清除IE cache，然后用如下步骤清除application server的cache：-1. Login as "Functional Administrator" responsibility. 2. Select "Core Services".3. Select "Caching Framework".4. Click "Clear All Cache".5. Read the message, then click &q

激活某个职责，一般来说操作比较简单。[@more@]1. 用System Administrator职责登录EBS系统。2. Security => Responsibility => Define => 查找职责，比如 "Workflow Administrator" --> 将"Effective Dates To"列置为空3. 如果用户反映该职责没有激活，则提交一个"Workflow Background Process" request，将参数"Process Deferred", "Process Timeout" 和 "Process Stuck" 都设为 Yes。4. 如果用户反映还没有激活，则清理Application Server的Cache，同时建议用

众所周知，ORACLE EBS系统经常需要打各种补丁，由此也经常需要核对各种文件的版本信息。查看版本信息用如下步骤。[@more@]以查看文件APXINWKB.fmb的版本信息为例。1. 用application manager的系统帐号登录application server。2. $ cd $AU_TOP3. $ strings -a ./forms/US/APXINWKB.fmb|grep '$Header' FDRCSID('$Header: APXINWKB.fmb 120.496.12000000.123 2008/03/12 00:20 sbonala ship $'); $Header: APXINWKB.fmb 120.496.12000000.123 2008/03/12 00:20 sbonala ship $如果还有其他语言版本的文件，也要查看

HANGANALYZE事件在分析系统挂住的时候很有用，尤其是会话(session)因为锁的原因挂住的时候。 用法： SQL>alter session set events 'immediate trace name HANGANALYZE level 4';[@more@]http://zhyuh.itpub.net/resource/334/29544

oradebug setospid 11774 oradebug event 10046 trace name context forever, level 12 oradebug event 10046 trace name context off[@more@]

今天终于把session的sid, db server操作系统进程，application server操作系统进程，以及相关用户信息全部联系起来。[@more@]select /*+ ORDERED */chr(39)||s.sid||','||s.serial#||chr(39) sid_serial, to_char(s.logon_time,'yyyymmdd HH24:MI:SS') logon, floor(last_call_et/3600)||':'||floor(mod(last_call_et,3600)/60)||':'||mod(mod(last_call_et,3600),60) IDLE, s.username o_user, s.osuser os_user, s.status status, u.user_name apps_user--, n.TERMINAL_ID terminal, s.process midTier_process, p.spid dbTier_process,