Troubleshooting Usage | Log Name | Log Location | Location Example | Increase Log Level | Log configuration file |
Install\De-install\Patch | |||||
Examples: deinstall2010-08-15_09-01-33PM.out deinstall2010-08-15_09-01-33PM.log installProfile2010-08-15_09-01-33PM.log oraInstall2010-08-15_09-01-33PM.out oraInstall2010-08-19_01-21-49AM.err OPatch2010-08-19_02-15-05-AM.log 2010-08-19_01-21-49AM.log installProfile2010-08-19_01-21-49AM.log | ■ Linux and UNIX: USER_HOME/oraInventory/logs/ ■ Windows: C:\Program Files\Oracle\Inventory\logs\ | C:\Program Files\Oracle\Inventory\logs | Q: Is this possible ? | ? | |
Startup\Shutdown\Execution | |||||
WLS Admin Server | AdminServer.log bifoundation_domain.log AdminServer-diagnostic.log(BI JEE log (Action Services and Security Services), - review in FMC) access.log logs\bipublisher \bipublisher.log ????? | <Middleware_HOME>\user_projects\domains\bifoundation_domain\servers\AdminServer\logs | C:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\AdminServer\logs | In WLS Console > biFoundation_domain > servers > AdminServer Logging Tab has a General and an HTTP sub-tab General (general settings for logs for this server) By default all messages are published By default all messages go to the log file. | ? |
WLS Managed Server | bi_server1.log bi_server1.out bi_server1.out00001 etc bi_server1-diagnostic.log (BI JEE log (Action Services and Security Services), - review in FMC) access.log logs\bipublisher \bipublisher.log ????? | <Middleware_HOME>\user_projects\domains\bifoundation_domain\servers\bi_server1\logs | C:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\bi_server1\logs | biFoundation_domain > servers > bi_server1 Logging Tab has a General and an HTTP sub-tab General sub-tab (general settings for logs for this server) By default all messages are published By default all messages go to the log file. | ? |
BI System Components (BI instance) | |||||
OracleBIServerComponent | nqserver.log Nqquery.log Administrator_NQSAdminTool.log Administrator_nQUDMLExec.log (For detailed info : See System Administrator's Guide for Oracle Business Intelligence Enterprise Edition, 8.2 Understanding Diagnostic Log and Log Configuration Files) | <ORACLE_INSTANCE>\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1\ | C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1\ | Use FMC Diagnostics tab > Log Configuration to set a higher “Log Level” Log Levels ■ Incident Error option ■ Error option ■ Warning option ■ Notification option ■ Trace option such as set Trace to “FINEST” (performance impact!) For nqquery.log, set level 0 thru 5 in BI Admin Tool > Manage Security for each user | ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBIServerComponent\coreapplication_obis1\logconfig.xml |
OracleBIPresentationServicesComponent | sawlog0.log webcatupgrade0.log \catalogcrawler\ sawcatalogcrawlerlogsys0.log | <ORACLE_INSTANCE>\diagnostics\logs\ OracleBIPresentationServicesComponent \coreapplication_obips1\ | C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1\ | As above | ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBIPresentationServicesComponent\coreapplication_ obips1\instanceconfig.xml |
OracleBISchedulerComponent | nqscheduler-<n>.log | <ORACLE_INSTANCE>\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1 | C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1 | ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBISchedulerComponent\coreapplication_obisch1\instanceconfig.xml | |
OracleBIJavaHostComponent | Jh.log Jh-n.log | <ORACLE_INSTANCE>\diagnostics\logs\ OracleBIJavaHostComponent\coreapplication_obijh1\ | C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBIJavaHostComponent\coreapplication_obijh1\ | As above | ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBIJavaHostComponent\coreapplication_obijh1\logging_config.xml |
OracleBIClusterControllerComponent | Nqcluster-<n>.log | <ORACLE_INSTANCE>\diagnostics\logs\ OracleBIClusterControllerComponent\coreapplication_obiccs1\ | C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBIClusterControllerComponent\coreapplication_obiccs1\ | As above | ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBIClusterControllerComponent\coreapplication_obiccs1\ccslogconfig.xml |
OPMN | Debug.log Opmn.log Service.log etc | C:\OBIEE11G\instances\instance2\diagnostics\logs\OPMN\opmn | As above | ORACLE_INSTANCE\config\component_type\bi_component_name\ \OPMN\opmn\opmn.xml | |
Troubleshooting Java Components | |||||
As above plus | |||||
EmbeddedLDAP (can be used in conjunction with the access.logs, as above | EmbeddedLDAP.log EmbeddedLDAPAccess.log | DOMAIN_HOME/servers/server_name/data/ldap/log/EmbeddedLDAP.log DOMAIN_HOME/servers/server_name/data/ldap/log/ | C:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\bi_server1\data\ldap\log\EmbeddedLDAP*.log | ? | ? |
Miscellaneous | |||||
Repository log | <Repository Name> .rpd.log | <ORACLE_INSTANCE>\OracleBIServerComponent\coreapplication_obis1\repository\ | C:\OBIEE11G\instances\instance2\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository\SampleAppLite.rpd.Log | ? | ? |
Upgrade | ua<timestamp>.log | BI_ORACLE_HOME\upgrade\logs | ? | ? | |
Usage Tracking (Only if redirected to logs) | NQAcct.yyyymmdd.hhmmss.log | STORAGE_DIRECTORY parameter in the Usage Tracking section of the NQSConfig.INI file determines the location of usage tracking log files | ? | ? | |
BI Agent Log | Agent-JobID-InstanceID.xxx | The default location for log files is the Log directory in the Oracle Business Intelligence installation directory on the computer where the Oracle BI Scheduler is installed. | ? | ? |
Configuration Files
Source: Oracle® Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition > Where are Configuration Files Located?
Oracle BI Server
NQSConfig.INI
logconfig.xml
ORACLE_INSTANCE\config\OracleBIServerComponent\coreapplication_obisn
For example:
\instances\instance1\config\OracleBIServerComponent\coreapplication_obis1
Note: Although DBFeatures.ini is also located in this directory, do not edit this file directly. See Oracle Fusion Middleware
Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for information about how to edit features for a
database.
Oracle BI Presentation Services
instanceconfig.xml ORACLE_INSTANCE\config\OracleBIPresentationServicesComponent\coreapplication_obipsn
For example:
\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1
Note: Do not add elements to the instanceconfig.xml file unless you are overriding the stated default values. Override only those
settings that are necessary for configuring the system to meet the needs of your organization.
Cluster Controller
NQClusterConfig.INI
ccslogging.xml
ORACLE_INSTANCE\config\OracleBIApplication\coreapplication
For example:
\instances\instance1\config\OracleBIApplication\coreapplication
Oracle BI Scheduler
instanceconfig.xml
ccslogging.xml
(for Cluster Controller)
ORACLE_INSTANCE\config\OracleBISchedulerComponent\coreapplicati on_obischn
For example:
\instances\instance1\config\OracleBISchedulerComponent\coreapplication_obisch1
JavaHost
config.xml
logging_config.xml
ORACLE_INSTANCE\config\OracleBIJavaHostComponent\coreapplication_obijhn
For example:
\instances\instance1\config\OracleBIJavaHostComponent\coreapplication_obijh1
Oracle BI Presentation Services Plug-in
bridgeconfig.properties
MW_HOME\user_projects\domains\domain_name\config\fmwconfig\biinstances\coreapplication
For example:
mw_home\user_projects\domains\bifoundation_domain\config\fmwconfig\biinstances\coreapplication
No comments:
Post a Comment