We can use the log viewer utility nQLogViewer to view the query log.Each entry in the query log is tagged with the user ID, session ID and request ID.The User ID will have the details of the user who issued the query, the session ID will have the details of the session in which the query was initiated, and the request ID will have the individual query.
Note : You must run first the bi-init initialization file.
BI-INIT INITIALIZATION FILE: Before running any of the Oracle BI Server command-line utilities, you must now run bi-init.cmd (or bi-init.sh on UNIX) to launch a command prompt or shell window that is initialized to your Oracle instance.
Location of this bi-init initialization file utility:
In 11g : ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup
In 10g : Oracle_BI/server/bin/nqlogviewer
Syntax :
To run the nQlogViewer utility, open a Command window and type nQlogViewer with any combination of its arguments.
The syntax is as follows:
nqlogviewer [-u<user_ID>] [-f<log_input_filename>]
[-o<output_result_filename>]
[-s<session_ID>] [-r<request_ID>]
user_ID :
The name of a user in the Oracle BI repository.By using this the user specified in the syntax only can use the query logging. If it is not specified ,all the users for whom query logging is enabled will be shown.
log_input_filename :
The name of an existing log file. This parameter is required.
output_result_filename :
The name of a file in which the output of the log viewer to be stored. If the file exists, results are appended to the file. If the file does not exist, a new file is created. If not specified, output is sent to the monitor screen.
session_ID :
The session ID of the user session.The Oracle BI Server assigns each session a unique ID when the session is initiated. This limits the scope of the log entries to the specified session ID. If not specified, all session IDs are shown.
request_ID :
The request ID of an individual query. The Oracle BI Server assigns each query a unique ID when the query is initiated. This limits the scope of the log entries to the specified request ID. If not specified, all request IDs are show
Location of nQLogViewer:
In 11g : Oracle_BI_HOME/bifoundation/server/bin/nqlogviewer.Note : You must run first the bi-init initialization file.
BI-INIT INITIALIZATION FILE: Before running any of the Oracle BI Server command-line utilities, you must now run bi-init.cmd (or bi-init.sh on UNIX) to launch a command prompt or shell window that is initialized to your Oracle instance.
In 11g : ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup
In 10g : Oracle_BI/server/bin/nqlogviewer
To run the nQlogViewer utility, open a Command window and type nQlogViewer with any combination of its arguments.
The syntax is as follows:
nqlogviewer [-u<user_ID>] [-f<log_input_filename>]
[-o<output_result_filename>]
[-s<session_ID>] [-r<request_ID>]
Here :
The name of a user in the Oracle BI repository.By using this the user specified in the syntax only can use the query logging. If it is not specified ,all the users for whom query logging is enabled will be shown.
log_input_filename :
The name of an existing log file. This parameter is required.
output_result_filename :
The name of a file in which the output of the log viewer to be stored. If the file exists, results are appended to the file. If the file does not exist, a new file is created. If not specified, output is sent to the monitor screen.
session_ID :
The session ID of the user session.The Oracle BI Server assigns each session a unique ID when the session is initiated. This limits the scope of the log entries to the specified session ID. If not specified, all session IDs are shown.
request_ID :
The request ID of an individual query. The Oracle BI Server assigns each query a unique ID when the query is initiated. This limits the scope of the log entries to the specified request ID. If not specified, all request IDs are show
Nice Post ... !!!!!!!!!!
ReplyDelete