Tuesday, October 4, 2011

11g Quick Steps to Package and Send Critical Error Diagnostic Information to Support for further information.

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Problem: 11g Quick Steps to Package and Send Critical Error Diagnostic Information to Support for further information.

Symptoms:

Staring with Oracle 11g there is significant change in trace file and alert.log generation. The locations of alert.log and trace files are also changed. This note explains how to find out a tracefile when there is a critical error in the database.


Solution:



From 11g , Whenever any critical error occurs, two files will be created .
1. Trace files .
2. Dump files
Trace files : Trace files have periodic, line-by-line information written by a process as it goes along doing its normal operation.
Dump files : Dumps are typically large blocks of information written in response to an error or other exceptional condition.
For each incident reported , there will be a trace file and incident dumps.
Process trace files are kept in ADR HOME/trace directory and will have name _ora_.trc.
When there is a critical error occur in the database an incident and a corresponding incident directory will be created.
The incident dump file will appear in the incident directory.
Alert log will show the trace file and incident dump for the error reported.
Thu Apr 17 17:11:56 2008
Errors in file e:\app\oracle\diag\rdbms\dmrds11\dmrds11\trace\dmrds11_fbda_2152.trc (incident=119612):
ORA-00600: internal error code, arguments: [ktfacht1-0], [], [], [], [], [], [], []
Incident details in: e:\app\oracle\diag\rdbms\dmrds11\dmrds11\incident\incdir_119612\dmrds11_fbda_2152_i119612.trc
Thu Apr 17 17:11:57 2008
dmrds11_fbda_2152.trc is the trace file .
dmrds11_fbda_2152_i119612.trc is the incident dump.
Most of the cases , incident dump will have the errorstack and will have more information for the error reported .
To identify the trace file from ADRCI :


The steps in identifying a trace file are.

1) Find out the incident number.
2) Find out the trace file.


1) Find out incident number.
adrci> show incident

ADR Home = /ade/prgeorge_v706/oracle/log/diag/rdbms/v706/v706:
*************************************************************************
INCIDENT_ID PROBLEM_KEY CREATE_TIME
-------------------- ----------------------------------------------------------- ----------------------------------------
986 ORA 600 [qksdie - feature:QKSFM_CVM] 2007-07-09 21:55:11.566607 -07:00
985 ORA 600 [qksdie - feature:QKSFM_CVM] 2007-07-09 21:10:56.573263 -07:00

2) Now if we want to get the trace file for incindent_id 986
Adrci> show trace -i 986.

This will open the incident dump file. The incident dump file will contain a pointer to the process trace file too.
An example:
/ade/prgeorge_v706/oracle/log/diag/rdbms/v706/v706/incident/incdir_986/v706_ora_6231_i986.trc
----------------------------------------------------------
LEVEL PAYLOAD
----- -----------------------------------------------------------------------------------
Dump file /ade/prgeorge_v706/oracle/log/diag/rdbms/v706/v706/incident/incdir_986/v706_ora_6231_i986.trc
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, Data Mining and Real Application Testing options
..........
..............
*** ACTION NAME:() 2007-07-09 21:55:11.568

Dump continued from file: /ade/prgeorge_v706/oracle/log/diag/rdbms/v706/v706/trace/v706_ora_6231.trc
1> ***** Error Stack *****
ORA-00600: internal error code, arguments: [qksdie - feature:QKSFM_CVM], [], [], [], [], [], [], []

In this example the process trace file is /ade/prgeorge_v706/oracle/log/diag/rdbms/v706/v706/trace/v706_ora_6231.trc

References:


NOTE:422893.1 - 11g Understanding Automatic Diagnostic Repository.
Get Oracle Certifications for all Exams
Free Online Exams.com

Forms FRD Trace with New variable FORMS60_TRACE_PATH

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Problem: Forms FRD Trace with New variable FORMS60_TRACE_PATH


Solution:



There has been new added security functionality depending on your Tech Stack Level. This is mainly seen
on the 11.5.10 Tech Stacks. With the Latest Patch Levels or 11.5.10 you are no longer allowed to
enter directly into the Applications Forms via the /dev60cgi/f60cgi URL.

There is a way to directly enter the Applications Forms via /dev60cgi/f60cgi if so desired for Trace purposes.
Note 293609.1 APP-FND-01542 when logging directly into forms via the f60cgi in 11.5.10

Please understand it is UNSUPPORTED to log directly to the Forms via /dev60cgi/f60cgi, but we do allow
it for FRD Traces only.


Starting FRD in Oracle Applications for a user:
Set a profile option "ICX: Forms Launcher" at user level to
http://:/dev60cgi/f60cgi/?&record=collect&log=
e.g. http://hostname.domainname.com:port/dev60cgi/f60cgi/?&record=collect&log=/mgd01/vis510ora/8.0.6/forms60/log
Log in to the Personal Home Page and select a responsibility to start the forms.

Suggestion: Create a user "TRACE" and set above profile for it. When a FRD
is needed ask user to use this username.

This log file will show each keystroke so it will build very fast,
I recommend on intermittent errors that the log file be periodically deleted,
so that the file does not become so massive that it hinders investigation of
the cause of the error.

There is a New twist for where the location of the FRD Trace files.
Found that Forms Patchset 16 introduced a new variable $FORMS60_TRACE_PATH
and it defaults to $ORACLE_HOME/forms60/log.

Forms Server enforces the following conditions after Forms Patchset 16:-

1) Ensures that all files from 'record=xyz', 'record=filename', 'play=xyz',
'log=' etc., are created in either FORMS60_TRACE_PATH or O_H/forms60/log,
and nowhere else.
2) Ensures that any filenames specified in 'log= '/'record= ' params are
stripped of any path information, using only the remaining 'terminal name',
thus making it impossible for users to overwrite any files outside
FORMS60_TRACE_PATH or O_H/forms60/log.
3) Ignores any values specified for FORMS60_TRACE_PATH on the URL or in static
HTML files, making it impossible for users to supply their own value.

Set your $FORMS60_TRACE_PATH variable to a Location from where you would like
your frd trace files to be coppied to or leave as the default.


This was changed for Security reason, so that the Sysadmin's can maintain Security
on the Servers.

References:
Forms FRD Trace with New variable FORMS60_TRACE_PATH [ID 290210.1]


Get Oracle Certifications for all Exams
Free Online Exams.com

Basic checks for user integration when using Oracle E-Business Suite 11i with Oracle AS 10g

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Problem:
Basic checks for user integration when using Oracle E-Business Suite 11i with Oracle AS 10g




Symptoms:

When integrating eBiz with SSO, the user record is stored in both OID and eBiz. Issues with user login problems can be due to either the user record not being provisioned/created in either OID or eBiz, or the linking of the user account between these two data sources
This document describes some basic checks you can perform to confirm the nature and extent of a user login problem, so you may find useful if you have issues with user provisioning or a user cannot login to eBusiness suite and/or SSO



Solution:



Software Requirements/Prerequisites
This note is for customers who have implemented E-Business integration with AS10g SSO as described in note 233436.1 Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
Configuring the Script
No special steps required
Running the Script
1. Confirm if the user can login to OIDDAS
This will check the basic SSO username/password is functioning
Use the following URL to login as the specific user that is having difficulties
http://OID_host.domain:port/oiddas
2. Confirm if the user can login to eBiz locally
NOTE - this will only work if the user has been configured to login locally
Use the following URL to login as the specific user that is having difficulties
http://eBiz_host.domain:port/OA_HTML/AppsLocalLogin.jsp
3. Run the following SQL against the eBiz database
This script will list the most relevant information about the user from the eBiz user repository (FND_USER)
REM
REM START OF SQL
REM
set echo on
set timing on
set feedback on
set pagesize 132
set linesize 100
col user_id form 9999999999
col user_name form a30
col start_date form a12
col end_date form a12
col user_guid form a90
col encrypted_foundation_password form a12
col encrypted_user_password form a12
select
user_id,
user_name,
to_char(start_date, 'DD-MON-RRRR') start_date,
decode(end_date,NULL,'*** NULL ***',to_char(end_date, 'DD-MON-RRRR') ) end_date,
decode(encrypted_foundation_password, 'EXTERNAL', 'EXTERNAL', 'LOCAL_LOGIN') encrypted_foundation_password,
decode(encrypted_user_password,'EXTERNAL', 'EXTERNAL', 'LOCAL_LOGIN') encrypted_user_password,
decode(user_guid,NULL, '*** NULL ***',user_guid) user_guid
from fnd_user
where user_name like upper('%&enter_username%')
order by user_name
/
REM
REM END OF SQL
REM
Interpretation of the output
• start_date should be todays date or earlier
• end_date should be NULL or later than todays date
• if the user password is set to EXTERNAL, this user can only login to eBiz via SSO
4. Run the following script from the Infrastructure node
#####################################################################
### START OF SCRIPT : ldapsearch_appsuser.sh ###
#####################################################################
##
(
echo "****************************************************"
date
echo "****************************************************"
if [ "$OIDManagerName" == "" ]; then
echo -n "Please enter the OID Manager username (default=orcladmin) : "
read OIDManagerName
fi
if [ "$OIDManagerName" == "" ]; then
OIDManagerName="orcladmin"
fi
echo "you entered " $OIDManagerName
if [ "$OIDManagerPasswd" == "" ]; then
echo -n "Please enter the OID Manager password : "
read OIDManagerPasswd
fi
if [ "$Host" == "" ]; then
echo -n "Please enter the OID Server hostname (default=`eval hostname` ) : "
read Host
fi
if [ "$Host" == "" ]; then
Host=`eval hostname`
fi
echo "you entered " $Host
if [ "$Port" == "" ]; then
echo -n "Please enter the OID Server Port (default=389) : "
read Port
fi
if [ "$Port" == "" ]; then
Port="389"
fi
echo "you entered " $Port
if [ "$AppsUser" == "" ]; then
echo -n "Please enter the Applications username (default=all) : "
read AppsUser
echo "you entered " ${AppsUser}
fi
if [ "$AppsUser" == "" ]; then
echo "you entered all users"
fi
### The following lines are the read work of the script
ldapsearch -v -h "${Host}" -p ${Port} -D "cn=${OIDManagerName}" -w "${OIDManagerPasswd}" -b "" -s sub "uid=${AppsUser}*" uid orclguid orclactivestartdate orclactiveenddate orclisenabled
###
echo "***********************************************"
###
ldapsearch -v -h "${Host}" -p ${Port} -D "cn=${OIDManagerName}" -w "${OIDManagerPasswd}" -b "cn=Provisioning Profiles, cn=Changelog Subscriber, cn=Oracle Internet Directory" -s sub "objectclass=*"
###
) 2>&1 | tee -a mzLdapAppsUser.out
##
#####################################################################
### END OF SCRIPT ###
#####################################################################

Interpretation of the output
• orclisenabled should be ENABLED
• orclactivestartdate should be todays date or earlier
• orclactiveenddate should have no value
• orclguid should be same as FND_USER user_guid from step (3) above
5. Run the following SQL against the eBiz database to check the relevant profile options
REM
REM START OF SQL
REM
set echo on
set feedback on
set pagesize 132
set linesize 120
column SHORT_NAME format A30
column NAME format A40
column LEVEL_SET format a15
column CONTEXT format a30
column VALUE format A60 wrap
--
select p.profile_option_name SHORT_NAME,
n.user_profile_option_name NAME,
decode(v.level_id,
10001, 'Site',
10002, 'Application',
10003, 'Responsibility',
10004, 'User',
10005, 'Server',
'UnDef') LEVEL_SET,
decode(to_char(v.level_id),
'10001', '',
'10002', app.application_short_name,
'10003', rsp.responsibility_key,
'10005', svr.node_name,
'10006', org.name, '10004', usr.user_name,
'UnDef') "CONTEXT",
v.profile_option_value VALUE
from fnd_profile_options p,
fnd_profile_option_values v,
fnd_profile_options_tl n,
fnd_user usr,
fnd_application app,
fnd_responsibility rsp,
fnd_nodes svr,
hr_operating_units org
where p.profile_option_id = v.profile_option_id (+)
and p.profile_option_name = n.profile_option_name
and n.language = 'US'
and upper(p.profile_option_name) in (
'APPS_SSO',
'APPLICATIONS_HOME_PAGE',
'APPS_LOCAL_LOGIN_URL',
'APPS_PORTAL',
'APPS_PORTAL_LOGOUT',
'APPS_SSO_AUTO_LINK_USER',
'APPS_SSO_LINK_SAME_NAMES',
'APPS_SSO_ALLOW_MULTIPLE_ACCOUNTS',
'APPS_SSO_LOCAL_LOGIN',
'APPS_LOCAL_CHANGE_PWD_URL',
'APPS_SSO_CHANGE_PWD_URL',
'APPS_SSO_LDAP_SYNC',
'APPS_SSO_OID_IDENTITY',
'APPS_SSO_FORGOT_PWD_URL',
'APPS_SSO_LISTENER_TOKEN',
'APPS_DATABASE_ID',
'PASSWORD_CASE_OPTION',
'SIGNON_PASSWORD_CASE',
'SIGNON_PASSWORD_LENGTH',
'APPS_PORTAL_MODPLSQL_URL',
'APPS_SSO_MODPLSQL_URL',
'APPS_SSO_POSTLOGOUT_HOME_URL',
'APPS_AUTH_AGENT',
'APPS_AUTH_FORGOT_PASSWORD_LINK')
and usr.user_id (+) = v.level_value
and rsp.application_id (+) = v.level_value_application_id
and rsp.responsibility_id (+) = v.level_value
and app.application_id (+) = v.level_value
and svr.node_id (+) = v.level_value
and org.organization_id (+) = v.level_value
order by user_profile_option_name, level_set;
REM
REM END OF SQL
REM
Interpretation of the output
• APPS_SSO should be either SSWA_SSO or SSO_SDK
• APPS_LOCAL_LOGIN_URL should only be set at SITE level
• APPS_PORTAL should only be set at SITE level
• APPS_SSO_LOCAL_LOGIN normally set to SSO or BOTH for a user
• APPS_SSO_LDAP_SYNC should be set to "Y" at SITE level



References:


Basic checks for user integration when using Oracle E-Business Suite 11i with Oracle AS 10g [ID 444573.1]


NOTE:233436.1 - Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
NOTE:261914.1 - Integrating Oracle E-Business Suite Release 11i with Oracle Internet Directory and Oracle Single Sign-On
NOTE:295606.1 - Oracle Application Server 10g with Oracle E-Business Suite Release 11i Troubleshooting

Get Oracle Certifications for all Exams
Free Online Exams.com

How to Enable trace for a specific transaction in Sieble

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Problem: How to Enable trace for a specific transaction in Sieble

Solution:




Method1: through form
-----------------------
Enable SQL*Trace by choosing Help > Diagnostics > Trace > Trace with binds
Disable SQL*Trace by choosing Help > Diagnostics > Trace > Trace off

Method2: through concurrent program
-----------------------
Please enable trace on the concurrent program using the following steps:
Goto Sysadmin > Concurrent > Program > Define
Query the concurrent program
Check the trace box to enable trace

Method3: through bde script for concurrent programs with binds
-----------------------
*** This method will enable trace with binds for all new sessions and connections
Download and review the script, bde_system_event_10046.sql, from Note.179848.1.
Run the script and press enter when prompted
Return to the application
Execute the concurrent program
Monitor the program until it begins to run
Return to SQL*Plus and press enter to cancel tracing new programs

Method4: Level 12 Event Trace
-----------------------
INSTRUCTIONS FOR FND SESSION SQL
a. Please deliver a complete trace file created in the following manner:

First enable trace for a specific user:
- Bring up the Core application - 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'

Please set this at the user level with the following string:
BEGIN FND_CTL.FND_SESS_CTL(,, , 'TRUE',,'ALTER SESSION
SET TRACEFILE_IDENTIFIER='||'||'TAR' ||'||' EVENTS
='||'||' 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12 '||');
END;
(Cut and paste the above sql statement against the initialization sql -
Custom Profile at the User Level )
This must be one complete line of text - so may be best to copy the string
into notepad prior to putting it into the profile.

b. Once the profile is set, please change responsibilities and directly go
and reproduce the problem.
To locate the trace file, use the following sql in sqlplus:
select name, value from v$parameter where name like 'user_dump_dest';
- The value is the location of the trace file on the database server
- Please move to this directory and search for the file having TAR in the
filename
- This is the trace file created - please tkprof and upload BOTH the raw
and tkprof trace file to metalink.

c. Ensure that the profile option is unset before exiting the Application.
This is a very important step. If this is not unset, unnecessary trace
files will be generated.

Method5: finding concurrent program trace files:
-----------------------
column traceid format a8
column tracename format a80
column user_concurrent_program_name format a40
column execname format a15
column enable_trace format a12
set lines 80
set pages 22
set head off

SELECT 'Request id: '||request_id ,
'Trace id: '||oracle_Process_id,
'Trace Flag: '||req.enable_trace,
'Trace Name:
'||dest.value||'/'||lower(dbnm.value)||ora||oracle_process_id||'.trc',
'Prog. Name: '||prog.user_concurrent_program_name,
'File Name: '||execname.execution_file_name|| execname.subroutine_name ,
'Status : '||decode(phase_code,'R','Running')
||'-'||decode(status_code,'R','Normal'),
'SID Serial: '||ses.sid||','|| ses.serial#,
'Module : '||ses.module
from fnd_concurrent_requests req, v$session ses, v$process proc,
v$parameter dest, v$parameter dbnm, fnd_concurrent_programs_vl prog,
fnd_executables execname
where req.request_id = &request
and req.oracle_process_id=proc.spid(+)
and proc.addr = ses.paddr(+)
and dest.name='user_dump_dest'
and dbnm.name='db_name'
and req.concurrent_program_id = prog.concurrent_program_id
and req.program_application_id = prog.application_id
and prog.application_id = execname.application_id
and prog.executable_id=execname.executable_id

where "&request" is the concurrent request id for the inventory
transaction
worker. also get the outputs of the following:

Method6: Creating a TKPROF file
-----------------------
A trace file is a raw set of data produced by the Oracle Database.
TKPROF reformats the raw data so that it is easier to review.

1. Retrieve the trace file.
2. Issue a command like the following to create a TKPROF version of the
trace file:
tkprof sys=no
explain=apps/

Method7: Creating a TraceAnalyzer File
-----------------------
Note#224270.1: Trace Analyzer

A trace file is a raw set of data produced by the Oracle Database.
TraceAnalyzer reformats the raw data so that it is easier to review.
It is a more powerful tool than TKPROF.
It translates things like bind variables and make them easy to find.

1. Download TraceAnalyzer from Note.224270.1
2. Install trace analyzer in SQL: @TRCACREA.sql;
3. Retrieve the trace file.
4. In SQL*Plus, issue a command like the following to create a TraceAnalyzer
version of the trace file:
@TRCANLZR.sql UDUMP vis015_ora_22854.trc




Get Oracle Certifications for all Exams
Free Online Exams.com

Migrate GL report in R12 from 11.5.10

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Problem: Migrate GL report in R12 from 11.5.10

Symptoms:
We are considering Migration to R12 from 11.5.10
What are the mandatory changes in the reports if no setup changed in R12 after migrating in the context of GL reports.

Solution:


In Release 12, a few 'Account Analysis' reports that were providing subledger information are not available.
They are now obsoleted reports.

he available reports may not be under the same responsibility that they were once and the format may have changed a little. However the new reports are xml reprots and often you are able to add columns to xml report that were not there in 11i.
Specifically:
In Release 12, a few 'Account Analysis' reports that were providing subledger information are not available.
They are now obsoleted reports.
These were available in prior releases:

Account Analysis - Payables Detail(132 Char)
Account Analysis - Payables Detail(180 Char)
Account Analysis - Subledger Detail (132 char)
Account Analysis - Subledger Detail (180 char)
Cause
This is due to SLA (Subledger accounting) features in R12.
Solution
Subledger Accounting provides accounting reports in Release 12 using Oracle XML Publisher. Those reports include Account Analysis, Open Account Balances, Journal Entries and many other reports.

Check the 'Subledger Accounting Implementation Guide' for details of each report.
Run the reports that are available to determine if any of them can be used as the alternative to the reports in 11i in order to meet all your needs.

Note 396829.1 'Oracle Subledger Accounting Documentation Resources, Release 12' provides all the mentioned documentation

The changes and improvements in R12 are significant and provide great benefits to most businesses some require a some change in process to get the full benefit. I am not aware of any reports being obsoleted that are not replaced by alternative reports in SLA.

Please ask on the My Oracle cistomer forum and see what experiences other customers have had. With good testing processes you should not find difficulties adapting to the benefits of using report manager with its report repository and security by responsibility.

References:
464233.1 R12: Are Account Analysis Subledger Detail Reports Available In R12? Are there obsoleted reports?




Get Oracle Certifications for all Exams
Free Online Exams.com

How Can User Actions Be Traced in the Object Manager?

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Problem: How Can User Actions Be Traced in the Object Manager?


Solution:



Tracing users' actions is a helpful tool for troubleshooting issues such as a crash or an unexpected behavior of Siebel applications. Siebel application versions 7.0.4.304 and later and Siebel versions 7.5.x and later, offer the possibility to trace navigational and data-related type actions of application users.
In Siebel version 7.0.4.304 and later, this feature is enabled by increasing the log level for the Object Manager's ObjMgrSessionInfo event type. In Siebel version 7.5.x and later, this feature is enabled by increasing the log level for the Object Manager's EventContext event type. Below is information on how to set these component events:
Enabling the Component Event
Siebel Version 7.0.4.304 and Later
Using the Client UI
1. In the Siebel client, navigate to Site Map > Server Administration > Components > Component Event Configuration.
2. Highlight the component that you want to trace the user's actions, for example the Call Center Object Manager component (SCCObjMgr).
3. In the lower applet set the log level for the Object Manager Session Information event type to a value of 4.
Using the Srvrmgr Command Line
change evtloglvl EventContext=4 for comp SCCObjMgr_enu
Siebel Version 7.5.x and Later
Using the Client UI
1. In the Siebel client, navigate to Site Map > Server Administration > Components > Component Event Configuration. NOTE: In Siebel version 7.7, you want to navigate to Site Map > Administration - Server Configuration > Servers > Components > Component Event Configuration.
2. Highlight the component that you want to trace the user's actions, for example the Call Center Object Manager (ENU) component (SCCObjMrg_enu).
3. In the lower applet set the log level for the Event Context event type to a value of 4.
Using the Srvrmgr Command Line
change evtloglvl EventContext=4 for comp SCCObjMgr_enu
Output Produced and Interpreting the Results
Output
In the appropriate Siebel Object Manager's log file, open the SCCObjMgr_enu_.log located in the SIEBEL_HOME\siebsrvr\log directory, you should search for the keyword EventContext as shown below:

EventContext EvtCtxView 3 2003-04-16 12:58:14 Home Page View (WCC)
EventContext EvtCtxScreen 3 2003-04-16 13:06:02 Accounts Screen

EventContext EvtCtxView 3 2003-04-16 13:06:02 Account List View

EventContext EvtCtxApplet 4 2003-04-16 13:06:08 Account List Applet (Drilldown)

EventContext EvtCtxView 3 2003-04-16 13:06:08 Account Detail - Contacts View
EventContext EvtCtxApplet 4 2003-04-16 13:06:14 Account Entry Applet (GetQuickPickInfo)

EventContext EvtCtxApplet 4 2003-04-16 13:06:19 Account Entry Applet (PostChanges)

EventContext EvtCtxApplet 4 2003-04-16 13:06:20 Account Entry Applet (WriteRecord)
NOTE: In Siebel version 7.0.4.304 and later, you should search for the keyword ObjMgrSessionInfo in the Object Manager's log file.
Interpretion
1. The user logs into the Siebel application and is presented with the Home Page screen:(Home Page View (WCC)).
2. Then they navigate to the Accounts Screen and they drill down on one of the records on the Accounts List applet: (Account List Applet (Drilldown)).
3. This takes the user to the Account Detail - Contacts View: Account Detail - Contacts View.
4. In the applet, a field with a pick list is invoked: (Account Entry Applet (GetQuickPickInfo)).
5. The user updates a record: (Account Entry Applet (PostChanges)).
6. The user saves the record to the database: (Account Entry Applet (WriteRecord)).



References:

How Can User Actions Be Traced in the Object Manager? [ID 477162.1]

Additional References
Below are some additional references that you may want to review:
1. For more information about the Event Context event type, refer to Siebel Bookshelf version 7.7 > Siebel Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging > Common Event Types for Application Object Manager Diagnostics.
2. Also refer to FAQ 2116 that discusses how to turn on tracing for the Siebel Object Manager.
3. There are three Troubleshooting Steps documents that discuss how to troubleshoot crash behaviors:
o Troubleshooting Steps 30 - covers how to troubleshoot Siebel server component crashes in the UNIX platform.
o Troubleshooting Steps 31 - covers how to troubleshoot Siebel server component crashes in the Microsoft Windows platform.
o Troubleshooting Steps 32 - covers how to troubleshoot Internet Explorer crashes.

Get Oracle Certifications for all Exams
Free Online Exams.com

How Can Tracing Be Increased for the Siebel Object Manager?

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Problem: How Can Tracing Be Increased for the Siebel Object Manager?


Solution:



The information and steps outlined in this document describe on how to generate a more detailed log file to assist in troubleshooting any Siebel Object Manager (OM) related behaviors. Increasing the event logging will provide information about the individual processes and steps that are part of that task. This information is especially useful when debugging performance, hang, memory leak, or crash behaviors.

NOTE: When you increase the Object Manager event logging levels, the log files will grow larger and require more disk space. Additionally, performance will be impacted as more detailed tracing is written to the log files. Therefore, you should monitor the disk space available under the Siebel Server's log directory and only increase the log levels while you are debugging a specific behavior or as instructed by Siebel Technical Support. You should reset the log levels to their default values when running in a production environment.

By default in Siebel 7.x and 8.0, the Siebel component only writes header information and errors to the component log file. Log files are created in the log directory on the Siebel server and are named using the following format:

_%Task_Id%.log

For example:

SCCObjMgr_enu_7204.log

There are a number of event types available to increase the amount of information logged. This FAQ does not attempt to detail all of them but details the most useful ones and those that have specific relevance to the Siebel Object Manager component. The table below lists the most commonly used ones and their recommended values:

Event Type Alias Siebel Version Log Level Event Description
v7.0.4 v7.0.5 v7.5.2 v7.5.3 V8.0
MessageFlow X X X X X 4 Messages exchanged between the OM and Siebel Web Server Extension (SWSE)
ObjMgrSessionInfo X X X X N/A 4 View/Applet (pre-Siebel version 7.5) and User Session login, logout and timeout information

NOTE: For additional information about this event type, refer to FAQ 1964.
EventContext N/A N/A X X X 4 View/Applet Information and User Actions, in other words, NewQuery, ExecuteQuery, Drilldown

NOTE: For additional information about this event type, refer to FAQ 1964.
ObjMgrDataObjLog X X X X X 5 Data Manager object tracking, in other words, creation, use, and deletion of Database Connections, SearchSpecs, SortSpecs, Cursors
ObjMgrLog X X X X X 5 General OM events: Load license, open SRF, errors, etc.
ObjMgrBusCompLog X X X X X 4 Business Component related events: create and delete
ObjMgrBusServiceLog X X X X X 4 Business Service events: create, delete, methods invoked, etc.

NOTE: For additional information about this event type and how it was used, refer to Alert 941.
MainThread X X X X X 4 Task counter, Task creates and exits (in main Multi Threaded Server log)
TaskEvents X X X X X 4 Task creation, context, session timeout and close info
SQLParseAndExecute X X X X X 4 SQL Prepare, Execute, Bind variables, etc.
ObjMgrSqlLog X X X X X 4/5 4 SQL statements, bind variables, timing information.

5 Search and Sort spec values, Join definitions.

NOTE: To avoid potential adverse behaviors from setting this event type, refer to Alert 945.
SQLProfiling X X X X X 4 SQL Profiling information. Helps aid in the diagnosis of a poorly performing component.
SQLSummary X X X X X 4/5 SQL Prepare, Fetch and Execute times. Provides detail information regarding the execution of a SQL statement.
SQLSlowQuery X X X X X 4 SQL Performance – lists 10 slowest performing queries

NOTE: This document covers only the important events related to the Siebel Object Manager components.

Bug 10507918 has been logged to address the issue that no log generated for SQLSummary event when evtloglvl is set to 4.

There are other events that can be turned on for other Siebel components like Siebel Workflow, Siebel EAI, etc. For more information about these events, refer to Siebel Bookshelf version 7.5.3 > Siebel Server Administration Guide > Event Logging Administration > Events and Event Logging.

From Siebel versions 7.0.5 and 7.5.3 onwards, it is possible to see the SQL generated by the Siebel Object Manager to be sent to the Fulcrum Search Engine by setting the Generic Log event parameter. This can be set either using the srvrmgr command line or the Server Administration screens. Refer to the following section, Steps to Enable the Component Event, for details on viewing the SQL sent to the Fulcrum Search Engine.

Steps To Enable the Component Event

Using the Siebel Client (UI)

To change the event log level for a component, do the following:

1. In Siebel 7.x release, navigate to Site Map > Server Administration > Components > Component Event Configuration. In Siebel 8.x release, navigate to Site Map > Administration - Server Configuration > Servers > Events.
2. Highlight the component for which you wish to turn the tracing on.
3. In the lower applet, select the event type alias and set the log level. For example, to view the SQL sent from the Siebel Search Center to the Fulcrum Search Engine, set the Generic Log event parameter =4.

NOTE: There is no need to stop and restart the Siebel Object Manager for the logging to take effect. You only need to start a new session connecting to the Object Manager.

Using the Srvrmgr Command Line Utility

To change the event log level for a component, type the following:

change evtloglvl for component

For example, to view the SQL sent from the Siebel Search Center to the Fulcrum Search Engine, type the following:

change evtloglvl genericlog=4 for comp

If you are using Siebel Call Center in English, the would be SSCObjMgr_enu. For a list of Object Manager components and their aliases, refer to Siebel Bookshelf version 7.7 > Siebel System Administration Guide > Siebel Server Components and Parameters > Siebel Server Components.

The log file where this SQL will be generated to is the object manager log file in the Siebel server log directory.

An example of the SQL generated in the object manager log file:

GenericLog GenericDetail 4 2003-12-12 12:36:49 Siebel Search: Executing search.

The select statement is

SELECT
ROW_ID, SUMMARY, FILE_NAME, FT_DNAME, REVNUM,VIS_ID,
TEXT_READER, FT_TEXT_STATUS,TABLENAME(), Relevance(),
FT_ORIGINAL_SIZE, FULLNAME(),VIS_INFO, DESCRIPTION,
PRIVATE_FLG, TITLE, VERSION
FROM "FUL_LIT"
WHERE
(FUL_LIT.VIS_ID IN ('0-3P1KT') AND
(FUL_LIT.SALES_TOOL_TYPE <> 'Component') AND
(FUL_LIT.SUMMARY CONTAINS ~ 'null' OR
FUL_LIT.EXTERNAL_TEXT CONTAINS ~ 'null' ))
ORDER BY 10 DESC


References:


How Can Tracing Be Increased for the Siebel Object Manager? [ID 477897.1]
For more information about the srvrmgr command line utility, refer to Siebel Bookshelf version 7.5.3 > Siebel Server Administration Guide > Using the Siebel Server Command-Line Interface.

For more information about the event logging commands, refer to Siebel Bookshelf version 7.5.3 > Siebel Server Administration Guide > Using the Siebel Server Command-Line Interface > Siebel Server Manager Commands > Event Logging Commands.

For more information about the srvrmgr command line utility, refer to Siebel Bookshelf version 8.0 > Siebel System Administration Guide > Using the Siebel Server Manager Command-Line Interface.

For more information about the event logging commands, refer to refer to Siebel Bookshelf version 8.0 > Siebel System Administration Guide > Using the Siebel Server Manager Command-Line Interface > Siebel Server Manager Commands > Event Logging Commands.
Get Oracle Certifications for all Exams
Free Online Exams.com