Hi! Whats the trick to using the Enable Drill Down option when creating a profile? No matter what I have tried, I get [FATAL] Unable to start drill-through. Here are some sample tries:
[ITSM] dbo.
dbo.
dbo
[empty -- no literally, left blank]
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
-
Hello,
I assume you are trying to create a Profile using the "New Profile" dialog, you check "Enable drill-through" and when you click Finish, you get the [FATAL] error in the Console View, is that right?
In order for us to find the source of the error, please give us more details so we can try to replicate and fix it:
- is there any further information about the error in the Console View? This would help determine the cause.
- are you profiling a text file or a database table?
- what database engine are you using as the "Data source" for Drill-through and what driver are you using to connect to it?
- do you have sufficient privileges in the database to create and write into tables ?
Any additional relevant information will help us locate and remove the problem as soon as possible. -
-
The history is that we had a whole thread on connecting to the data with Martin and had to download a new .dll. Here are the steps:
Create a Profile [wizard]
Database table
Expand down the database structure
Select a table
Browse to a folder to save the profile
Configure Profile with the following:
All Columns
Standard Analysis
Domain Analysis
Mask Analysis [characters]
Enable Drill-through (Only option is the top of the Hierarchy)
Profile
Finish
Runs in milliseconds.
Today, I am unable to replicate the problem. However, 2 other people saw the error when it was happening. Just no screen shot from Friday, 10/16/2009.
As a secondary question, I note the console has a new error message that makes me ask, 'How often do the transaction logs need to be compacted/deleted/archived, due to the profiling tool?
We are currently running maintenance on ALL of the transaction logs to start from a zero baseline to see if we can determine the answer from our side. When that is complete, I will again try to reproduce the [FATAL] error.
This is what the Console says today, Monday 10/19/2009:
19.10.2009 11:39:53 [INFO] Using following licences:
19.10.2009 11:39:53 [INFO] C:\Program Files\DQ Analyzer 6\runtime\lib\..\license_keys\license.plf
19.10.2009 11:39:53 [INFO] Using Ataccama DQ Analyzer 6 configuration file C:\Documents and Settings\klockett\My Documents\CDI\Data Quality\Profiling\Ataccama\SFB\Account\.Account.plan
19.10.2009 11:39:53 [INFO] Using runtime configuration file C:\Documents and Settings\klockett\Local Settings\Temp\runtimeCfg1158623999713524018.tmp
19.10.2009 11:39:54 [INFO] Ataccama DQ Analyzer 6 engine initialized.
19.10.2009 11:39:54 [INFO] Creating runtime...
19.10.2009 11:39:55 [INFO] Starting runtime...
19.10.2009 11:39:55 [INFO] Running runtime...
19.10.2009 11:40:03 [WARNING] [Account] Unable to create drill-through table
java.sql.BatchUpdateException: The transaction log for database 'ContentManagement' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeBatch(SQLServerStatement.java:1693)
at cz.adastra.cif.model.internal.modelimpl.ConnectionPool$_E.executeBatch(ConnectionPool.java:702)
at cz.adastra.cif.io.jdbc.C.A(Connector.java:188)
at cz.adastra.cif.io.jdbc.C.B(Connector.java:109)
at cz.adastra.cif.io.jdbc.C.B(Connector.java:85)
at cz.adastra.cif.tasks.profiling.B.S.A(DrillDownManager.java:108)
at cz.adastra.cif.tasks.profiling.C.I.A(RollUpWrap.java:424)
at cz.adastra.cif.tasks.profiling.ProfilingAlgorithmInstance$_B.B(ProfilingAlgorithmInstance.java:358)
at cz.adastra.cif.tasks.profiling.ProfilingAlgorithmInstance$_B.access$400(ProfilingAlgorithmInstance.java:282)
at cz.adastra.cif.tasks.profiling.ProfilingAlgorithmInstance.run(ProfilingAlgorithmInstance.java:213)
at cz.adastra.cif.processor.internal.runner.B.E(ComplexStepNode.java:62)
at cz.adastra.cif.processor.internal.runner.F.run(Node.java:115)
at java.lang.Thread.run(Unknown Source)
19.10.2009 11:40:03 [INFO] Stopping runtime...
19.10.2009 11:40:04 [INFO] Finished!
19.10.2009 11:40:04 [WARNING] Task completed with warnings. Elapsed time: 00:00:09
K.J.-
I think the most important part is this:
ava.sql.BatchUpdateException: The transaction log for database 'ContentManagement' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
I understand it that the database you are using for drill-through was not able to create a new table as the log was full.
In MS SQL there are options for database to grow. If this option states the space for database or log is limited or the space on the disk is full, we may expect such situations. -
-
Regarding the second question: "How often to manage db logs?" In DQ Analyzer we have the option to delete orphaned tables (from deleted profiles). We do not take care about db logs. It really depends on db engine used for drill-through functionality as well as the size of profiled data.
Marek -
-
-
-
-
GOT IT! This is happening as a warning when I export to HTML and XML (both). Today, I am not able to make it happen [FATAL] on the original profile . . . yet. Still working on it.
19.10.2009 11:39:53 [INFO] Using following licences:
19.10.2009 11:39:53 [INFO] C:\Program Files\DQ Analyzer 6\runtime\lib\..\license_keys\license.plf
19.10.2009 11:39:53 [INFO] Using Ataccama DQ Analyzer 6 configuration file C:\Documents and Settings\klockett\My Documents\CDI\Data Quality\Profiling\Ataccama\SFB\Account\.Account.plan
19.10.2009 11:39:53 [INFO] Using runtime configuration file C:\Documents and Settings\klockett\Local Settings\Temp\runtimeCfg1158623999713524018.tmp
19.10.2009 11:39:54 [INFO] Ataccama DQ Analyzer 6 engine initialized.
19.10.2009 11:39:54 [INFO] Creating runtime...
19.10.2009 11:39:55 [INFO] Starting runtime...
19.10.2009 11:39:55 [INFO] Running runtime...
19.10.2009 11:40:03 [WARNING] [Account] Unable to create drill-through table
K.J. -
-
Looking back at the long message, I see the same
[WARNING] [Account] Unable to create drill-through table
is on the original profile.-
Is there anything else in the console? Usually the next sentence is taken from jdbc driver specifying the reason why.
Thanks
Marek -
-
-
-
-
No. I took the complete console message and cut/pasted it into the reply window(s).
Is there a log file I can check somewhere?-
OK, I meant the console. Thanks. Marek
-
-
-
-
-
Does the fact that I have no detailed error message have to do with this response from Martin for a connection issue?
We have reproduced the problem with no tables when connected using ODBC driver. We'll try and solve it for the next release (I am afraid it won't be for the Early Access 4 though).
I was able to connect using JDBC driver with Windows Authentication, but I needed special dll library to do so. The dll is "sqljdbc_auth.dll" which is included in MS SQL JDBC driver archive (http://www.microsoft.com/downloads/de... press Download, download Eula, then finally download the jdbc driver archive and look for dll inside), but we'll try and include it in the next release (probably in Early Access 4). This library should be in C:\Windows\system32 or any directory listed in PATH variable.
I used the "jdbc:sqlserver://localhost;integratedSecurity=true" format without any specification of instanceName (should be fine, unless you have to specify the instanceName).
This is just a hot fix of the problem. I think we'll be able to provide better solution soon. -
-
I am getting exactly same output "[WARNING] [test] Unable to create drill-through table" when I am try to write drill-through to database without permission to create a table. It might be caused by problem with permissions (creating a table, writing to our PROF_META table, wrong schema used...).
-
-
I have permission to create tables on our test environment. What is the default permissions on the PROF_Meta table?
-
Loading Profile...




EMPLOYEE
EMPLOYEE
