Logging in query

Hi,
Is there any query to find out ,how many users were logged into the frontend since some particular date..
Thanks,
kr

Please refer to the following threads:
USERS CONNECTED
Re: USERS CONNECTED
Number of users logged in last two months
Re: Number of users logged in last two months

Similar Messages

Change logs for query...........

Hi,
How to check the logs for query changes. Means which user has done what change.In properties we get the last user only.
Is there any way to check the full history of changes?
Can we change that in some transport request?
Bye,
Jeetu

Hi,
There is no such facilities available to find, which user has done what changes in the query. you can only get the last changed 's user name of query. in transport request also you cannot change the query.
To add, check out this:
Tcode SQ01>select 'Environement' from the menu>Directories>All Queries
in the popup window, select a query and click on 'Display' button. you would get some useful information about that query
Bye

How to see the user log of query

Hi all ,
Can any body help me about the log of user access to a Bex 3.5 query ? We want to learn which users access to query designer and make changes on queries. The query designer only give us the last user who access to query. Is there a transaction or something that we can see this information.

Hi Selen,
Check RSZCHANGES and note down the compid
and check it in RSZCOMPDIR
Check these tables in SE11
check these threads even..
[Change logs for query...........;
[Id of logged in user;
[http://help.sap.com/saphelp_nw04s/helpdata/en/43/5fa1dc3c046e47e10000000a422035/frameset.htm]
Regards,
NR
Assign points if helpful...

Log the query of the "Execute Query Task"

Hi,
I want to log/watch the query executed by the "Execute query Task". It's a query with different variables, the different variables i can see in one of the debug windows and these looks OK, but the query doesn't do what's expected. So i want to see the whole query, is that possible?
Query logging on the database server isn't an option. The server is an oracle server and the dba doesn't want to change this setting.
Thanks,
Dennis

You could use a single variable to store your entire query, and use that in your Execute SQL task. Basically, you need to set the variable to evaluate as an expression, then build your query string in the variable. You can use this to combine your
other variables into the query, and see it as one value at runtime.
I am using SSIS 2008. I know I can do it with a variable. But I was wondering why SSIS does not allow you to log the query easily. Just for this, I will have to create a variable and a script task :(

Log parser query

Hi, I need assistance in writing a log parser query which can read input from a txt file which contains smtp addresses. The query should search for each of the smtp addresses in the input file against a log file. The query results need to be exported to
a csv file.
Thanks,
Feroz
Feroz

Hi,
You need to ask about Log Parser in the Log Parser forum rather than here.
http://forums.iis.net/default.aspx/51
Bill

How to log a query or ticket to SAP on SAP support Portal - need process

Dear All,
I got SAP support portal user id and password. Can anybody guide me how to log a ticket or query on some issue to SAP.
Pls let me knwo how to search help notes to. Explain me in steps pls.
Need urgent help.
Thanks
Sunnzy

Hello exper,
Can you tell me that incase i have to log a request for a client server then how i will do that.
I am simply facing a problem in PPOME transaction where a tab for IT 1005 planned compensation has been added but it is not showing any input fields there. However we tried the same configuation in Sandpit server and it is working fine.
Incase i have to log this is to SAP for help, do i have to follow the same path to do it.
thanks
Sunny

SQL 2012 SP1 - How to determine a query that causes Error 8623 in SQL Log: The query processor ran out of internal resources and could not produce a query plan. This is a rare event...

We are getting multiple 8623 Errors in SQL Log while running Vendor's software.
How can you catch which Query causes the error?
I tried to catch it using SQL Profiler Trace but it doesn't show which Query/Sp is the one causing an error.
I also tried to use Extended Event session to catch it, but it doesn't create any output either.
Error:
The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that
reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.
Extended Event Session that I used;
CREATE EVENT SESSION
overly_complex_queries
ON SERVER
ADD EVENT sqlserver.error_reported
ACTION (sqlserver.sql_text, sqlserver.tsql_stack, sqlserver.database_id, sqlserver.username)
WHERE ([severity] = 16
AND [error_number] = 8623)
ADD TARGET package0.asynchronous_file_target
(SET filename = 'E:\SQLServer2012\MSSQL11.MSSQLSERVER\MSSQL\Log\XE\overly_complex_queries.xel' ,
metadatafile = 'E:\SQLServer2012\MSSQL11.MSSQLSERVER\MSSQL\Log\XE\overly_complex_queries.xem',
max_file_size = 10,
max_rollover_files = 5)
WITH (MAX_DISPATCH_LATENCY = 5SECONDS)
GO
-- Start the session
ALTER EVENT SESSION overly_complex_queries
ON SERVER STATE = START
GO
It creates only .xel file, but not .xem
Any help/advice is greatly appreciated

Hi VK_DBA,
According to your error message, about which query statement may fail with error message 8623, as other post, you can use trace flag 4102 & 4118 for overcoming this error. Another way is looking for queries with very long IN lists, a large number of
UNIONs, or a large number of nested sub-queries. These are the most common causes of this particular error message.
The error 8623 occurs when attempting to select records through a query with a large number of entries in the "IN" clause (> 10,000). For avoiding this error, I suggest that you could apply the latest Cumulative Updates media for SQL Server 2012 Service
Pack 1, then simplify the query. You may try divide and conquer approach to get part of the query working (as temp table) and then add extra joins / conditions. Or You could try to run the query using the hint option (force order), option (hash join), option
(merge join) with a plan guide.
For more information about error 8623, you can review the following article.
http://blogs.technet.com/b/mdegre/archive/2012/03/13/8623-the-query-processor-ran-out-of-internal-resources-and-could-not-produce-a-query-plan.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Terminate:Activity failed; there is no back end error log. - Query Designer

Hello all,
Has anyone encountered this erro before while using query Designer. I am trying to drag an infoobject in the rows section and I get this STOP error in message section at the bottom.
Terminate: Activity failed; there is no back-end error log [A006(R9E)]
Diagnosis
An error occurred in the back end.
System Response
An error occurred in the back end for which there is no error message. You cannot continue to work.
Procedure
Exit the Query Designer and correct the error on the back end.
Then start the query designer again.
Procedure for System Administration
I dont get what is going wrong here,
Thanks,

hi,
There may be some problems with the connectivity in the box which you have logged in or in the excel properties itself. Try to login again and see if the problem is resolved else contact the BASIS or admin.
Thanks,
vrrp.

Log application query not showing correct results

Hi,
We are running Dataguard (DG) in our production environment. EBS 11.5.10.2 and DB 10.2.0.4.
Every morning we run the following query on both primary and standby to confirm that the logs are being transported and applied to the standby:
select sequence#,applied,to_char(first_time,'mm/dd/yy hh24:mi:ss') first from v$archived_log order by first_time;
Once the logs are transported and applied, a response of 'Yes' is returned for each log generated. We have noticed within the last week that when we run the query on primary, 'No' is being returned, but on standby, 'Yes' is returned. I have confirmed that standby is reflecting the correct results. I've tried restarting the DG service (alter database recover managed standby....) in an attempt to have primary 'refresh' itself but that didn't work.
Does anyone have any idea why primary keeps returning 'No' to the query, and how we can get it to reflect to correct results?
Thanks,
Lia.

Hi Werner,
Thanks for your response. Given what you're saying I find that a little strange since prior to this, the query would return a value of 'YES' on the primary. Actually, to be exact, on the primary, each log would should up twice. One would show 'NO' and the other 'YES'- the second indicating transporting and shipping was successful.
This is how the results were before:
SEQUENCE APP FIRST
+154623 NO 04/07/09 08:03:22+
+154623 YES 04/07/09 08:03:22+
+154624 NO 04/07/09 08:05:27+
+154624 YES 04/07/09 08:05:27+
This is how the results are now:
SEQUENCE APP FIRST
+154754 NO 04/22/09 07:22:22+
+154754 NO 04/22/09 07:22:22+
+154755 NO 04/22/09 07:25:27+
+154755 NO 04/22/09 07:25:27+
I'm not doubting that what you're saying is correct, it just adds an element of confusion for me...
Lia.

Logs for query deletion

I can not seem to find a log file for deletion of queries.
I want to be able to track who and when a query is deleted. Any ideas? Does anybody know if this is logged?
Cheers,
Kevin.

An unfortunate circumstance to be sure. Out of curiosity is there any particular reason you can't use ClamXAV rather than NAV?
I suppose that if NAV has a log and nothing relevant is in the log, then you're at a loss to even know if NAV is responsible for the folder's mysterious disappearance. Maybe you have technically savvy cockroaches in the building that come out at night to play? An informational age version of Archie and Mehitabel?
This experience may be an impetus to install software that keeps track of what's installed or removed from a computer. Doesn't help much now but it would be useful in the future.
Oh, one thing comes to mind - file recovery software:
Data Rescue II
File Salvage
TechTool Pro
Message was edited by: Kappy

Is there any change log for query change in BIW?

Hi Buddies,
Could you please tell me if there is a change log in BIW to record all changes made to query and workbook? Since yesterday, I found a very important query had been deleted from our BI system, but I did not who had done this.
Thanks in advanced.
best regards
Patrick

Unfortunately there isn't. Check if you have the query in another system (test, development) and transport it again. You could also check if there is still an entry in RSRREPDIR but I don't think so.
Best regards
Dirk

How to get logging sql query error

Hi,
I want to create some constraints and indexes on tables on a particular schema and I have the script to build the indexes and constraints.
But I want to get the errors that should be logged on some file during indexes and constraints creation.
Pls help me...
Thanks in advance..

If you are running the script via SQLPlus then just add a "spool filename" to the beginning of the script and a "spool off" at the end so that query results are written to the file. Also you probably want to "set echo on" at the beginning so that the SQL statements are written to the file also.
See the SQLPLus Users Guide for the set command and spool.
HTH -- Mark D Powell --

Error While Logging in Query Designer`

Hi all
We recently upgraded our system to BI7.0, I am trying to open Query designer, I am getting this error "terminate: the BW server has deactivated this version of Query Designer".......can anyone suggest valuable pts why I am getting this??

The error is happening because the bex version is restricted to 3.x in server.
You can check it in t-code RSZVERSION. Here you will be able to maintain minimum and maximum version which we can use for designer and analyzer.
This is done because the 3.x queries if opened and saved in 7.0 version, cannot be reverted back.
check the OSS note 582944 which may help you.
workaroud for this is dont click OK on the pop up of error message. you will be able to work on the query.
the designner will close only if you click ok on the popup.
Hope this helps,
Sri....

Error on log when query record

SEVERE 114 0 oracle.dbtools.worksheet.sqlhistory.db.HistoryDB sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:52)

Please read the forum announcements before posting.
K.

Impact of Query Logging on Performance of Queries in OBIEE

I see from [An Oracle BI Blog post|http://obieeblog.wordpress.com/2009/01/19/obiee-performance-tuning-tip-%e2%80%93-turn-off-query-logging/] that Query Logging has a performance impact in OBIEE.
What is the experience with Query Logging at different levels in a Production environment with, say, 50 or 100 or 500 concurrent users ?
I am completely new to OBIEE, I know the Database. So, please bear with me.
Hemant K Chitale

Kumar's blog that you reference says it all really.
I don't know if anyone's going to be able to give you the kind of information you're looking for, because it's a no-brainer not to enable this level of logging :)
Is there are reason you're even considering it?
Imagine in the database running a low-level trace or debug log for every user session... you just wouldn't do it

Logging in query

Similar Messages

Maybe you are looking for