Pl/sql logging!!

hello,
In order to log the pl/sql user messages we are trying to use log4plsql. Now, the problem is where to keep that log
- In log table within the database
- in File (here we are facing problem, related to some junk (hexa) characters in log file when the log4plsql java process write the logs to the file)
We are in a discussion, that where to keep this log.
Your suggestion would be appreciated.
Regards,
Amit

user11977262 wrote:
In order to log the pl/sql user messages we are trying to use log4plsql. Now, the problem is where to keep that log
- In log table within the database
- in File (here we are facing problem, related to some junk (hexa) characters in log file when the log4plsql java process write the logs to the file)Easy. Table.
Keeping logs in a file dates back to 80's style Cobol processing. It is primitive. It is unstructured. It is clunky. And for these exact same reasons, this is why the 80's style of file (ISAM/VSAM/etc) style processing gave way to databases. As database provide a data processing platform for dealing with structured data.
It would be, IMO, very silly to use the file system for storing structured data (as that is what log data is), and not a database.
Simple questions to ask. Find from a log file all errors that occurred between 09:00:20 and 09:00:55 yesterday? How many errors did application Foo generated and list the errors per hour and by catagory? Etc.
Try and do this with log files... now that would be, bluntly put, rather stupid.
Try and do this with a database table carrying log data - this is exactly why databases exist...

Similar Messages

NoClassDefFoundError: com/sap/sql/log/OpenSQLException

I have developed a Java project. It consists of 2 SQLJ files and then a Java class. When I try to execute the Java program, I get a Java error:
java.lang.NoClassDefFoundError: com/sap/sql/log/OpenSQLException
at com.mbb.crrs.business.report.dao.ReportDAO.<init>(ReportDAO.sqlj:23)
at com.mbb.crrs.business.report.dao.Test.main(Test.java:24)
Exception in thread "main"
I notice a similar problem on message: Re: Which jar to include com.sap.sql.log.OpenSQLException
Is that something that I need to maintain for it to work? Thank you.

Hi,
the problem one year ago was that the SQLException class was not available through remote access. I don't know if that might have been changed meanwhile in the latest release.
I implemented a simple work around: I caught every SQL-exception in the method where it was thrown, wrapped the exception message and any nested exception in a self written exception and threw this new exception. That worked fine.
Regards, Astrid

Com.sap.sql.log.OpenSQLException during EntityManager Call

Hi!
I deployed an EJB3 session bean on the NW 7.1.
The aim is to use JPA with this bean.
I configured the "persistence.XML" for the bean project and packed it into the jar File and a "data-source-aliases.xml" which is included in the ear file. The packaging of the ear-file is done with the developerStudio and deployed on the NW 7.1
Then I created a dataSource project which contains the "data-sources.xml" and deployed this too.
Here is my data-sources.xml:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE data-sources SYSTEM 'data-sources.dtd'>
<data-sources>
    <data-source>
        <data-source-name>JPA_SDN_EXAMPLE_DS_555</data-source-name>
        <driver-name>ora10</driver-name>
        <sql-engine>native_sql</sql-engine>
        <jdbc-1.x>
            <driver-class-name>oracle.jdbc.driver.OracleDriver</driver-class-name>

            <url>jdbc:oracle:thin:@10.XXX.7.27:1521:orcl</url>
            <user-name>bdeadm</user-name>
            <password>dmin</password>

        </jdbc-1.x>
    </data-source>
</data-sources>
My deployed session bean looks like this:
@Stateless(name="WorkerBean")
public class WorkerBean implements WorkerRemote {
     @PersistenceContext(unitName="JPAModel")
    private EntityManager em;
     public String sayHello() {
The last step was the deploment of the oracle driver on the NW7.1 under the "Application Resources Overview". The driver I named "ora10".
Now if I call my Bean shown above with its Entity Manager Call for the injection I got the following exception:
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing porting layer for ORACLE database via getSessionId().
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:148)
     at com.sap.sql.jdbc.direct.DirectConnectionFactory.createPooledConnection(DirectConnectionFactory.java:532)
     at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:157)
     at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:117)
     at com.sap.sql.connect.factory.PooledConnectionFactory.createPooledConnection(PooledConnectionFactory.java:119)
     at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:38)
I have no idea, whats wrong. Perhaps my driver is wrong or not set properly ?
Can anybody help me please ?
Thanks in advance,
Hendrik
Edited by: henne123 on May 18, 2009 6:19 PM

I have tried that.
[EXCEPTION]
*com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM EPD.SAPEPDDB.UME_EP_SLD" contains the syntax error[s]: - Open SQL syntax error: table names must not specify a catalog name (delete "EPD". before "SAPEPDDB"."UME_EP_SLD")*
Database name must be Ok, because i can access to other tables which are in the same DB...
Thanks for your help

Com.sap.sql.log.OpenSQLException: table or view not exists

Hi!.
I'm developing a Portal Component over NW EP 2004s (7.0) which access to SQL Server database. I have created three tables on the system db (EPD). Connection is Ok, over datasource object, but i can't make a SELECT operation to my new tables.
Hovewer, making a SELECT operation over older system tables is OK.
I have adjusted permissions on my new tables, similar to the older tables. The table's owner is the same too.
The exception i get is:
**Exception of type com.sap.sql.log.OpenSQLException caught: The SQL statement "SELECT * FROM "SAPEPDDB"."UME_EP_UNLOCKUSERS"" contains the semantics error[s]: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist**
[EXCEPTION]
*com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM "SAPEPDDB"."UME_EP_UNLOCKUSERS"" contains the semantics error[s]: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist*
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:38)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.CommonStatementImpl.executeQuery(CommonStatementImpl.java:114)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeQuery(StatementWrapper.java:172)
at com.uralita.database.DbManager.executeQuery(DbManager.java:105)
at com.uralita.ListaSistemas$ListaSistemasDynPage.getSystemsR3(ListaSistemas.java:184)
at com.uralita.ListaSistemas$ListaSistemasDynPage.doInitialization(ListaSistemas.java:93)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:105)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.sql.sqlparser.CommonSQLParserException: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:171)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
... 19 more
caused by
com.sap.sql.sqlparser.CommonSQLParserException: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:171)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.CommonStatementImpl.executeQuery(CommonStatementImpl.java:114)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeQuery(StatementWrapper.java:172)
at com.uralita.database.DbManager.executeQuery(DbManager.java:105)
at com.uralita.ListaSistemas$ListaSistemasDynPage.getSystemsR3(ListaSistemas.java:184)
at com.uralita.ListaSistemas$ListaSistemasDynPage.doInitialization(ListaSistemas.java:93)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:105)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Someone has been getting this problem? Any idea?
Thanks!

I have tried that.
[EXCEPTION]
*com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM EPD.SAPEPDDB.UME_EP_SLD" contains the syntax error[s]: - Open SQL syntax error: table names must not specify a catalog name (delete "EPD". before "SAPEPDDB"."UME_EP_SLD")*
Database name must be Ok, because i can access to other tables which are in the same DB...
Thanks for your help

PL/SQL log in java concurrent program is missing

Hi,
I'm experiencing something strange with EBS R12 concurrent program logs.
Our concurrent program is just a normal program that runs fine in most cases. It is written in java, which calls PL/SQL procedures. Usually the log is concatenation of logs from both like following
(log from mid-tier java codes ...)
Start of log messages from FND_FILE
(log from database tier PL/SQL codes ...)
End of log messages from FND_FILE
But on one customer's environment the PL/SQL log is missing. This makes us unable to see the important messages.
I tried to directly look at the files but had no luck.
select 'cat '||c.value||'/'||p.plsql_log
from fnd_concurrent_processes p, fnd_concurrent_requests r, fnd_env_context c
where r.controlling_manager=p.concurrent_process_id
and p.concurrent_process_id=c.concurrent_process_id
and c.variable_name='APPLPTMP' and r.request_id=...
(file not exist in file system)
req=...; nedit ${APPLCSF}/log/l${req}.req&
(pl/sql part is missing)
We verified database tier log directory is writable and has free space.
Also verified that other concurrent programs written in PL/SQL has correct logs.
How can we get PL/SQL logs? Please help.
Thanks

Hi Srini, here are the env details I got from customer:
1) $ uname -a
Linux srvoracle06.gpodeacero.corp 2.6.18-194.el5 #1 SMP Mon Mar 29 22:10:29 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
2) select banner from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
PL/SQL Release 11.1.0.7.0 - Production
CORE 11.1.0.7.0 Production
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 – Production
3) The EBS version result is:
Oracle Applications : 12.1.2
Hi Hussein, about enabling trace for concurrent program, how to do that? I guess you are not refering to database SQL trace right?

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

PL/SQL log messages are not printing from Java concurrent program

Hi,
I have a strange issue while submitting the Java concurrent program through PL/SQL.
I have a PL/SQL concurrent program which will invoke the Java concurrent program inside the package by use of "FND_GLOBAL.SUBMIT_REQUEST". It worked and submitted successfully. From that Java concurrent program we are calling some other PL/SQL packages and printing some log messages over there. But problem here is the request is only printing the Java log messages in view log but not the PL/SQL log messages. But if I submit the Java concurrent program directly from SRS form at that it is printing both Java and PL/SQL log messages.
I am just wondering how the log messages has not printed. Please provide your inputs to solve this problem.
Thanks
Suriya

I'm adding log messages in the package body , but these messages are not printing after completion of concurrent prog.
Any suggestions.
FND_FILE.PUT_LINE(FND_FILE.LOG,'Data Test :');Do you have COMMIT in your code?
https://forums.oracle.com/forums/search.jspa?threadID=&q=%27FND_FILE.PUT_LINE%27+AND+commit&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

The process could not execute 'sp_repldone/sp_replcounters' error for Log Reader Agent and SQL Server Assertion 17066 & 3624 errors in SQL Logs

One of our SQL Server started creating SQLDUMP file and and on investigation I found the error longs are filled with Errors 3624 & 17066. There is transnational replication configured on one of the databases is the LogReader Agent is failing error "The
process could not execute 'sp_repldone/sp_replcounters' on XXXXX".
Not sure if both these Assertion & Logreader Agent errors are related. Before I remove and put the replication, I wanted to check if anyone has experienced the same issues or aware of what the cause.
***********Error messages from SQL Logs******
**Dump thread - spid = 0, EC = 0x0000000111534460
Message
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <logscan.cpp>, line=2123 Failed Assertion = 'UtilDbccIsInsideDbcc () || (m_ProxyLogMgr->GetPru ()->GetStartupState () < RecoveryUnit::Recovered)'. This error may be timing-related. If the error persists after rerunning
the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Error: 17066, Severity: 16, State: 1.
External dump process return code 0x20000001.
External dump process returned no errors.
Thank you in advance.

You need to determine if this error is a transient one or a show stopper one.
It sounds like your log reader agent has crashed and can't continue.
If so your best bet is to call Microsoft CSS and open a support incident.
It also sounds like DBCC CHECKDB was running while the log reader agent crashed.
If you need to get up and running again run sp_replrestart, but then you might find that replicated commands are not picked up. You will need to run a validation to determine if you need to reinitialize the entire publication or a single article.
I have run into errors like this, but they tend to be transient, ie the log reader agent crashes, and on restart it works fine.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

How to turn on/enable sql logging

Our environment is Java EE 5, JPA, Weblogic 10, KODO 4.1.2, and our DB is Oracle 10gr2. We are trying to figure out what to do/what has to be set up in order to see the actual SQL going to the database. I have the following in the persistence.xml:
<properties>
<property name="kodo.Log" value="DefaultLevel=WARN, Runtime=INFO, Tool=INFO, SQL=TRACE"/>
</properties>
which I found posted somewhere while trying to resolve this, but it does nothing. There is no sql syntax whatsoever in any weblogic log or on the weblogic console. For what it's worth, we have tried both XA and the thin drivers, but that has no effect either. We have tweaked the logging options in the WL console as well, but nothing seems to have any impact on SQL logging. Any help would be greatly appreciated.

Russ Burkert wrote:
That did not work. There is nothing on the console or any of the logs that is new concerning sql logging. What didn't work?
Added the specified properties to the driver using the console and modified the
commEnv script so wlspy.jar is included in the WEBLOGIC_CLASSPATH. WebLogic was restarted.
However, spy.log is created and at least I can now see some database errors
(ORA-xxxx) coming back from Oracle (which is very helpful). But, no actual SQL in that log, either.
Upon further scrutiny of spy.log, I can see this kind of stuff:
PreparedStatement[35].setString(int parameterIndex, String x)
parameterIndex = 39
x = RN22
OK
All of our database transactions right now are inserts. I see how this maps to the JPA
objects, but it is quite grueling to have to figure out the index/offset of each piece
of data in the object and then cross-reference that to its DB table/column equivalent.
Is there any way to just see a simple INSERT statement somewhere?There has to be INSERT statements in the spy log. They may well be done by PreparedStatements,
which show their SQL once at the prepare, early in the log, and then re-executed indefinitely.
Find the SQL for a given prepared statement so you can know what failed when the XXXth execute()
returns a SQLException.
Joe

Weird errors in sql logs

I started seeing this kind of errors in sql logs after i moved databases to this server
The activated proc '[SQLDependency].[SqlQueryNotificationStoredProcedure-9c377656-a13c-4732-a5a2-177bbc45c565]' running on queue 'EmailValidator.SQLDependency.SqlQueryNotificationService-9c377656-a13c-4732-a5a2-177bbc45c565' output the following: 'Cannot
drop the service 'SqlQueryNotificationService-9c377656-a13c-4732-a5a2-177bbc45c565', because it does not exist or you do not have permission.'
Any help !!
Thanks in Advance

Hello,
That is coming from a service broker activated stored procedure in the database which looks like it is there because of notification services. Since you've just moved the database to another server, chances are the broker IDs aren't correct:
http://technet.microsoft.com/en-us/library/ms166057(v=SQL.105).aspx
Sean Gallardy | Blog
MCM 2008
MCSM:Data Platform Charter Member

Crystal Reports Server - Sub Reports requesting SQL Log In

I have a Sales report which has four subreports. The main report has parameters for year and four product groups. The year parameter and one of the product group parameters are passed to each subreport. When I run the report in Crystal Reports only one SQL log in is requested. When the report is run from Crystal Reports Server the SQL log in for he main report is handled automatically by CR Server but the report then prompts for 4 SQL logins, one for each subreport. I am not using integrated securirty. How can I prevent the four SQL log ins?

Hi Tony,
From the question that you have posted, we would like to know the following things: -
1. Are the main report and the subreports using the same database connection?
2. Which type of viewer are you using in Infoview to view the reports?
3. How many connections do you see in the Database Source under Process Tab in the properties of the report in CMC?
Usually this issue can be resolved by using ActiveX or Java Viewer in the Enterprise.
Please try chaning the viewer and let us know if it helps.
Cheers!

SQL log file

Hi guys. I know this is not adapted for this forum, but could anybody show me a way to read SQL server log(.ldf) files. have already tried SQL log Rescue, Apex SQL. I am trying to read a log file that got muh bigger in a couple of days. These 2 softwares do not seem to work

No. Go ask your question on an SQL forum.

SQL LOG FILE SIZE INCREASING

Hi DBA's
SQL Log file size occupies more disk space on the server, the overall database size is 8GB
How to decrease the SQL LDF file size on the server, please explain the suitable steps to perform
Thanks
DBA

use master
go
dump transaction <YourDBName>
with no_log
go
use <YourDBName>
go
DBCC SHRINKFILE (<YourDBNameLogFileName>,
100) -- where 100 is the size you may want to shrink it to in MB, change it to your needs
go
-- then you can call to check that all went fine
dbcc checkdb(<YourDBName>)
Andy ,
what point in asking user to use No_log and you did not even motioned about what this eveil command will do. Actually its
seriously not required reason being initial size of log file set to 8 G.
Plus what is point in running checkdb ?
I don't agree to any part you pointed
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Sql.log what is this all about

hi
i wanted to know why is this sql.log created on any drive on each jar opperation
contents being
vin(T)_ fff8382f:ffc73d0f     ENTER SQLAllocEnv
          HENV * 0x0b41f724
vin(T)_ fff8382f:ffc73d0f     EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
          HENV * 0x0b41f724 ( 0x0b70ff24)
vin(T)_ fff8382f:ffc73d0f     ENTER SQLAllocConnect
          HENV 0x0b70ff24
          HDBC * 0x0b41f688
vin(T)_ fff8382f:ffc73d0f     EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
          HENV 0x0b70ff24
          HDBC * 0x0b41f688 ( 0x0b610194)

i didnt get the debuggind stuff a little confused on
who initiates
that , as i have not.Let me try a slightly different take on what I said before.
Use "Start" and go to "Settings", then "Control Panel"
In there find either something that refers to "ODBC" or "Data Sources". You might have to poke around however this will be there. (Let me repeat it is there - it might be in a sub folder in the control panel but it is always there.)
Open it.
Look for a tab that says "Tracing", click on that.
I can't say for sure what you will find there, but on my system there is a big button that says "Start Tracing Now" and then says "Stop Tracing Now" when I click on it. Obviously when it says "Stop Tracing Now" it is no longer tracing. Yours will have something similar. Yours is turned on.
You will also notice that the file that it uses for tracing is called "sql.log". But once you turn the tracing off that no longer matters.

Where to find the SQL log by crystal reports

i want to watch the sql log by crystal report loading,but i don't know how to find it , somebody knows it? thanks advanced!

Hi Wang,
If you mean to look at the SQL query CR generates, then open the report in the CR Designer > Go to the Database option on the top > Click Show SQL.
-Abhilash

SQL LOG Backup failed in one Cluster Node

I have 02 node SQL fail over cluster, NOD01 and NODE 02. and configure SQL log backup job via SQL Logshipping
When the sql service is mounted to node 02 job backup will work without any issues, Once its connected to node 01 this will provide below issue
Executed as user: <domain>\administrator. The process could not be created for step 1 of job 0xAC90A0F3623AE44285089E9EF53B12C7 (reason: The system cannot find the file specified). The step failed.
could anyone have on fix for this
Thanx

SQL Server Agent on both nodes run under same domain account?
Are you sure that path location is correct?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Pl/sql logging!!

Similar Messages

Maybe you are looking for