MSCA Debug Log
1. 找到mwa.cfg配置文件
In 11i: $MWA_TOP/secure/
In R12: $INST_TOP/admin/install/
2. 设置mwa.cfg
trace level: mwa.LogLevel=TRACE
'mwa.logdir' 为日志输出路径,R12下，mobile日志会写到$INST_TOP/logs下
注：mwa.LogLevel可以设置为: Fatal, Error, Warning, Debug, and Trace.
Fatal只有在出现错误的情况才会记录日志. Trace会打出所有日志。因为性能原因，一般情况下不要设置logLevel到TRACE
3. 重启mobile Server
4. 业务处理, 在日志目录下就能看到[port].INV.log，[port].system.log
MSCA SQL Trace
1. Go to $MWA_TOP/secure directory.
2. In the file mwa.cfg , set mwa.LogLevel=performance.
3. Restart the mobile server.
4. Perform the related navigation steps to cause the issue.
5. You can search in the trace directories for files created. Or you can try to locate the particular file using SQL like the following to help. Query to identify the trace file name with the corresponding number from the username.
select prs.spid
from v$session ses , v$process prs
where ses.program = 'JDBC Thin Client'
and ses.client_info is not null
and ses.osuser = '&OS_USER_NAME'
and ses.paddr = prs.addr
order by ses.logon_time desc ;
6. Use the column "prs.spid" which maps to the filename in udump location. For example, if the column has the value 18027, then the file name could be "ora_18027.trc".
7. Create a TKPROF file and upload both the raw trace (.trc) and TKPROF.
8. After generating the trace file, ensure that you disable SQL*Trace by stopping the mobile server, resetting the parameter in mwa.cfg, and restarting the mobile server.Reference:
| SQL*Trace with WMS-MWA: Mobile Applications (Tracing SQL Via Database Trace To Allow For TKPROF Of Results Of User Actions) (Doc ID 277655.1) |