"Do not generate SQL" VB macro

is it possible to get the property "Do not generate SQL" in VB macro?
thanks

Hi Cyril,
I know you were looking for that, but it's not available as attribut in the current object model as Suresh said.
Then again why would you insist on doing this via the macro iso in the dp itself?
Are you adding a new dp via vba?
Or are you using the macro for more than one document?
Just curious about the why...
Sorry I can't be of more help,
Marianne

Similar Messages

TopLink does not generate SQL statements for inserting new objects

TopLink does not generate SQL statements for inserting new objects. Why?
Thanks in advance...

Please see the response in
Why does not unitofwork.commit write data to the database?
Regards,
Chris

Do Not Generate SQL before running

Post Author: beginner~~
CA Forum: WebIntelligence Reporting
Dear all,
Does anyone know where I could find the corresponding option in Web Intelligence for "Do Not Generate SQL before running" (in Desktop Intelligence)? Thanks.
Best Regards,

Post Author: James MacDonald
CA Forum: WebIntelligence Reporting
Go to the 'Edit Query' panel and press the 'SQL' button. There is a 'Use Custom SQL' check box that allows you to change the SQL manaully and if you 'Save' the results will work the same as 'Do Not Generate SQL ...'

Ejb3 entity bean not generating valid sql for postgres 8.1

Hello,
I originally posted this on the jboss seam board as I ran across this error on a seam test example, but it seems it's more generally applicable to ejb3 entity beans not generating sql that postgres can understand. I'll post my message below, all replies are appreciated.
I'm going through the hello world example from the seam book, and I'm getting an error I cannot resolve, that with an auto generated sql statement, that's not valid for postgres 8.1, the database I'm on. Here's my error:
17:40:31,370 INFO [STDOUT] Hibernate: select next value for person_id_seq from dual_person_id_seq
17:40:31,394 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 42601
17:40:31,394 ERROR [JDBCExceptionReporter] ERROR: syntax error at or near "value"
17:40:31,396 FATAL [application] javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not get next sequence value
javax.faces.el.EvaluationException: javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not get next sequence value
Here's the table definition
- create table Person (id bigint not null, name varchar(255), primary key (id))
- create table dual_person_id_seq (zero integer)
- create sequence person_id_seq start with 1 increment by 1
and here's the entity bean:
@Entity
@Name("person")
@Table(name="person")
@SequenceGenerator(name="person_sequence", sequenceName="person_id_seq")
public class Person implements Serializable {
private long id;
private String name;
@Id
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator="person_sequence")
public long getId() { return id;}
public void setId(long id) { this.id = id; }
public String getName() { return name; }
public void setName(String name) { this.name = name; }
How do I get it to generate a valid sql statement for postgres?

I think you should try putting the sequence generator annotation over the primary key field. Try it and be sure it works.
regards,
Michael

Not able to View generated SQL statement

Hi,
In order to view the generated SQL statement in Receiver JDBC Adapter,
i have done logSQLStatement as true in CC still not able to view in RWB,
also mesg protocol i m using in CC is "xml sql format", is it bcos of this i am not able to ?
If yes, then how can i see that sql string?
Regards,
Pratibha

Pratibha,
In our JDBC scenario the message protocol is also set to XML SQL Format
The Integration Process has a mapping step of type XSL that uses an Imported Archive to create the SQL select statement. Then there is a synchronous Send step for the JDBC component
Both this SQL statement and the returned SQL result are available in the XML message monitor SXMB_MONI
Regards,
Mike

SQL 2012 - SSIS Error -The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.

Hi guys
Trying to run this package on SQL 2012 agent and getting below error . No more details I could find so far.
The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
About Package - Its connecting to different version (2000,2005,2008,2008R2,2012) servers and putting Jobs information into one Database table.
Any workaround or fix ?
Thanks
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

New package or one that used to work? Connecting how? How does it poll?
On the surface it is an error from a memory space of the binary/non-managed code, so nothing can be really concluded based on what you decided to share with us.
Arthur My Blog
So Same package is working fine from my local machine which has SQL 2008 R2 and SQL 2012 installed. I am trying to push the package on server which has sql server 2012 Installed .
I don't see any error .
I ran package manually from server using SQL Data tools and ran successfully...
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

How to make sure that schema name is not included with generated sqls

How to make sure that schema name is not included with generated sqls with tableadapter wizard.
What should I use? Oledb, ODT.NET, where can set that I want "pure" sqls, not schemas, not ", or anything like this
I want
"Select a,b from t1" ,not "select "a","b" from schema.t1"
Also schema name is put in all parameters, all over the place... What if schema name changes. (b1test to b1prod)
. I now manually edit XML files of dataset. It works but....
thanks

The full hardware :
Processor Intel core due 3.00 MHz
RAM:1.5GB
psu:650 Watt (but i baught i cheap one so it may be actually about 400 watt)
HD Disk:160 GB
But about the power supply if it not able to run the VGA card ,Is it will not show any screen or it will not able to run the computer??

Java.sql.SQLException: Could not generate the DTD because..

I am trying to reverse an XML file and running into the following exception:
java.sql.SQLException: Could not generate the DTD because the file could not be created. Verify that you have write permission in the directory.
I have permission to the directory, so I suspect something else is causing this. I saw in another thread that file name length sometimes caused this. I tried that approach and it did not help.
I am trying to get data from an oracle table and put it in an XML file using an interface.
I have my interface set to use an oracle source table and an XML target. My LKM is SQL to SQL and my IKM is SQL Control Append. I have staging area different from target set.
My model (for the XML file) has technology set to XML, uses the SnpsXML jdbc driver and I use the following parameters in my file path: f, d, s, dp. This tests successfully.
I am trying reverse the xml file using standard reverse.
I am running this on a remote agent.
I am using ODI 10.1.3.5.5
Thank you for any help you can provide me.
Edited by: user13279807 on Oct 19, 2010 11:44 AM

The exact error message I recieved was the following:
The Technology or the Driver used does not support Reverse Engineering.
java.sql.SQLException: Could not generate the DTD because the file could not be created. Verify that you have write permission in the directory.
Details:
java.sql.SQLException: Could not generate the DTD because the file could not be created. Verify that you have write permission in the directory.
     at com.sunopsis.jdbc.driver.xml.bw.a(bw.java:810)
     at com.sunopsis.jdbc.driver.xml.bw.<init>(bw.java:450)
     at com.sunopsis.jdbc.driver.xml.bx.b(bx.java:292)
     at com.sunopsis.jdbc.driver.xml.bx.a(bx.java:270)
     at com.sunopsis.jdbc.driver.xml.SnpsXmlDriver.connect(SnpsXmlDriver.java:110)
     at com.sunopsis.sql.SnpsConnection.v(SnpsConnection.java)
     at com.sunopsis.sql.SnpsConnection.a(SnpsConnection.java)
     at com.sunopsis.sql.SnpsConnection.testConnection(SnpsConnection.java)
     at com.sunopsis.dwg.reverse.Reverse.a(Reverse.java)
     at com.sunopsis.dwg.reverse.Reverse.a(Reverse.java)
     at com.sunopsis.dwg.reverse.Reverse.a(Reverse.java)
     at com.sunopsis.dwg.reverse.Reverse.getMetaData(Reverse.java)
     at com.sunopsis.graphical.frame.a.ip.a(ip.java)
     at com.sunopsis.graphical.frame.a.ip.a(ip.java)
     at com.sunopsis.graphical.frame.a.hq.b(hq.java)
     at com.sunopsis.graphical.tools.utils.swingworker.v.call(v.java)
     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
     at com.sunopsis.graphical.tools.utils.swingworker.l.run(l.java)
     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
     at java.lang.Thread.run(Thread.java:619)

Generated SQL does not have fully qualified columnnames

Hi,
I'm trying to run a JDO query which results in:
[code=-5001, state=42703]
java.sql.SQLException: [SQL5001] Column qualifier or table CUSTOMER
undefined.
The model is basically like this:
Class Order has a 1-1 relation with Class CustomerRole which in turn has a
n-1 relation with Class Customer
Class Order and CustomerRole are both mapped to table SCHEMA1.ORDER (the
ORDER table contains the FK to the CUSTOMER table)
Class Customer is mapped to table SCHEMA2.CUSTOMER
I perform a query using an Extend of class Order.
I add the following filter to the query:
"this.CustomerRole.Customer != null"
(CustomerRole is the name of the relation between Order and CustomerRole,
while Customer is the name of the relation between CustomerRole and
Customer)
When I execute this query, I get the following message:
kodo.util.DataStoreException: [SQL5001] Column qualifier or table CUSTOMER
undefined. {SELECT t0.ID, t2.CUSTID, t3.ADDRESS, t4.COUNTRY,
t4.COUNTRYNAME, t2.NAME FROM SCHEMA1.ORDER t0 INNER JOIN SCHEMA1.ORDER t1
ON t0.ID = t1.ID LEFT OUTER JOIN SCHEMA2.CUSTOMER t2 ON t1.CUSTID =
t2.CUSTID LEFT OUTER JOIN SCHEMA2.CUSTOMER t3 ON t2.CUSTID = t3.CUSTID
LEFT OUTER JOIN SCHEMA1.COUNTRY t4 ON t3.COUNTRY = t4.COUNTRY WHERE (0 <
(SELECT COUNT(*) FROM SCHEMA2.CUSTOMER WHERE CUSTOMER.CUSTID =
t1.CUSTID))} [code=-5001, state=42703]
NestedThrowables:
com.solarmetric.jdbc.ReportingSQLException: [SQL5001] Column qualifier or
table CUSTOMER undefined. {SELECT t0.ID, t2.CUSTID, t3.ADDRESS,
t4.COUNTRY, t4.COUNTRYNAME, t2.NAME FROM SCHEMA1.ORDER t0 INNER JOIN
SCHEMA1.ORDER t1 ON t0.ID = t1.ID LEFT OUTER JOIN SCHEMA2.CUSTOMER t2 ON
t1.CUSTID = t2.CUSTID LEFT OUTER JOIN SCHEMA2.CUSTOMER t3 ON t2.CUSTID =
t3.CUSTID LEFT OUTER JOIN SCHEMA1.COUNTRY t4 ON t3.COUNTRY = t4.COUNTRY
WHERE (0 < (SELECT COUNT(*) FROM SCHEMA2.CUSTOMER WHERE CUSTOMER.CUSTID =
t1.CUSTID))} [code=-5001, state=42703]
java.sql.SQLException: [SQL5001] Column qualifier or table CUSTOMER
undefined.
     at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63)
     at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:51)
     at
kodo.jdbc.runtime.AbstractSelectResultObjectProvider.handleCheckedException(AbstractSelectResultObjectProvider.java:150)
     at com.solarmetric.rop.WindowResultList.<init>(WindowResultList.java:57)
     at
kodo.jdbc.runtime.JDBCFetchConfigurationImpl.newResultList(JDBCFetchConfigurationImpl.java:135)
     at
kodo.runtime.CopyOnWriteFetchConfiguration.newResultList(CopyOnWriteFetchConfiguration.java:159)
     at kodo.query.AbstractQuery.executeWithMap(AbstractQuery.java:750)
     at kodo.query.AbstractQuery.execute(AbstractQuery.java:633)
     at TestApp.<init>(TestApp.java:67)
     at TestApp.main(TestApp.java:135)
The problem is the last part of the query where it selects from
SCHEMA2.CUSTOMER while the Where part refers to just CUSTOMER (without
schema qualifier).
Are there any ideas to solve this? Is there a way to force columnnames
always being fully qualified in generated SQL statements?
Thanks,
Regards,
Alexander

Unfortunately, this is a bug that has to be fixed on our end. We'll
make sure a fix is in the next 3.1 release. Thanks for the report!

Weird behavior: PLSQL-generated SQL Report Region

I am trying to tune my PLSQL-generated SQL Report Region. I put in some code to write the resulting query to a table. I turn it on, run the page, and then turn it off and look at the SQL. Instead of getting one query for each time I load the page, I get five. Trying to find out a bit more about why, I concatenate :APP_USER and to_char(sysdate, 'hh:mi:ss') to the resulting SQL. What I find is that four of the entries in the table have my ApEx dev username, and all of these writes are 3 seconds before the SQL generated under the app username is written!
It probably goes without saying, but in all of the writes under my dev username, there are no session values and so any PLSQL if statements that depend on a session value act as if the session values are null. Also, any place I have :APP_ID show up as 4000 in those writes instead of the app number that shows up under my app username.
Do you follow this?
Well, on a hunch I copied the whole region back on to the page and disabled the original. This time, no writes with the dev username, only one select statement as originally expected.
Is that wierd or what?
Bill

Scott, Your last comment - that was it. I should've paid more attention to the time. The minutes must have been off. I made sure to log out of the dev environment before I ran the page, but the writes under my dev login were occurring when I saved the region. I still don't see why that process causes four identical writes, but it's not that important.
Thanks! Now I can to working on the real problem - improving my SQL.
Bill

OBIEE generated SQL differs if it's a Physical Table or Select Table...

Hi!
I have some tables defined in the Physical Layer, which some are Physical Tables and others are OBIEE "views" (tables created with a Select clause).
My problem is that the difference in the generated SQL for the same table, differs (as expected) whether it is a Physical Table or a "Select Table". And this difference originates problems in the returned data. When it a Physical Table, the final report returns the correct data, but when it is a Select Table it returns incorrect/incomplete data. The report joins this table with another table from a different Database (it is a join between Sybase IQ and SQL Server).
This is the generated SQL in the log:
-- Physical Table generated SQL
select T182880."sbl_cust_acct_row_id" as c1,
T182880."sbl_cust_acct_ext_key" as c2,
T182880."sbl_cust_source_sys" as c3
from
"SGC_X_KEY_ACCOUNT" T182880
order by c2, c3
-- "Select Table" generated SQL
select
     sbl_cust_acct_ext_key,
     ltrim(rtrim(sbl_cust_source_sys)) as sbl_cust_source_sys,
     sbl_cust_acct_row_id,
     sbl_cust_acct_camp_contact_row_id,
     ods_date,
     ods_batch_no,
     ods_timestamp
from dbo.SGC_X_KEY_ACCOUNT
As you may notice, the main difference is the use of Aliases (which I think that it has no influence in the report result) and the use of "Order By" (which I start to think that it its the main cause to return the correct data).
Don't forget that OBIEE server is joining the data from this table, with data from another table from a differente database. Therefore, the join is made in memory (OBIEE Engine). Maybe in the OBIEE Engine the Order by is essential to guarantee a correct join...but then again, I have some other tables in the Physical Layer that are defined as "Select" and the generated SQL uses the aliases and the Order by clause...
In order to solve my problem, I had to transform the "Select Table" into a "Physical Table". The reason it was defined as a "Select Table" was because it had a restriction in the Where Clause (which I eliminated already, althouth the performance wil be worse).
I'm confused. Help!
Thanks.
FPG

Hi FPG,
Not sure if this is a potential issue for you at all, but I know it caused me all kinds of headaches before I figured it out. Had to do with "Features" tab Values in the database object's settings in the Physical Layer:
Different SQL generated for physical table query vs. view object query?
Mine had to do with SQL from View objects not being submitted as I would expect, sounds like yours has more to do with "Order By"? I believe I remembered seeing some Order By and Group By settings in the "Features" list. You might make a copy of your RPD and experiement around with setting some of those if they aren't already selected and retesting your queries with the new DB settings.
Jeremy

Parameter issue - report not generating any pdf files

Hi All,
I'm trying to run a report which generates pdf files. Is there any limitation on the parameter string size? For one of the parameter values - '11F EA Accept nonhonor ASnSOMnSON_20091201090150846' the report is not generating any pdf files. I assumed the reason is of the keyword 'AS' in it and created another parameter value - '11F EA Accept nonhonor AnS-SOM-SON_20091202074331997', but it is also not generating any pdf files. I get this message from Adobe Reader " There was an error opening this document. This file cannot be opened because it has no pages. " The report is working normally when i hardcode the same parameter values into the logic. Any suggestions on this?
Thanks.
Edited by: user1049091 on Dec 2, 2009 9:17 AM
Edited by: user1049091 on Dec 2, 2009 12:37 PM

Tim,
That report is working normally for all the parameter values, except this one. It is not working only if i pass the value - ''11F EA Accept nonhonor ASnSOMnSON_20091201090150846' as a parameter. It is generating the pdf files when i hardcode the same value into sql query logic in the data template, instead of passing it as a parameter. Please advise.
Thanks.

Thread: Could not generate the XML in single thread mode

Hi all,
I have created a report using PLSQL Procedure method after submitting the request I am getting the following Error.Couldn't sort out why I am getting the error while running the report.
Error in "Multi threaded or single threaded execution block" of XXRX_REPORT_OUTPUT_PKG.insert_into_nested_table procedure
ERROR :ORA-20005: Could not generate the XML in single thread mode
XXRXERROR: XXRX_REPORT_OUTPUT_PKG.run_report SQLERROR: ORA-20005: ORA-20005: Could not generate the XML in single thread mode
Can someone help me out finding the issue
Thanks in Advance

Hi,
Please read SQL and PL/SQL FAQ
We cannot guess what is the error if you don't post any part of your code.
Additionally when you put some code or output please enclose it between two lines starting with {noformat}{noformat}
i.e.:
{noformat}{noformat}
SELECT ...
{noformat}{noformat}
Regards.
Al

OBIEE 11g "WITH SAWITH0 AS" subquery factoring clause in the generated sql

I've observed that the OBIEE 11g generates in the query log physical query using the WITH (sub-query factoring) clause to make the generated sql elegantly readable. This is great! Thanks for the developers. However I have some questions about this.
__Background__
Oracle Database' default behaviour is that if you have only one sub-query in the WITH section, it executes it as an in-line view and does not materialize it before the main sql is executed. If you have more than one, by default the database engine materializes all of them in the order of the definition. In some cases this can completely blow up the SGA and make the query never ending. To divert this behaviour you can apply two hints that work both in inline views and in sub-queries as well: /*+ MATERIALIZE */ and /*+ INLINE*/, however Analytics 11g does not seem to have hint capabilities at the logical table level, only at physical table level.
If we go with the current defaults, developers not aware of this feature can bump into serious performance issues for the sake of some syntax candy at the generated sql level, I'm afraid.
__Questions__
* Is it possible to turn the Analytics server not to use WITH but use inline views instead?
* Is there any way to sneak in some hints that would put the /*+ INLINE */ hint to the appropriate place in the generated sub-queries if needed
* Does the Oracle Database have any initialization parameter that can influence this sub-query factoring behavior and divert from the default?

The WITH statement is not added to make the query more elegant, it's added for performance reasons. If your queries take long to run then you may have a design issue. In a typical DWH DB SGA needs to be seriously increased since the queries ran are much larger and complex than on an OLTP DB. In any case you can disable the WITH statement in the Admin Tool by double clicking on your database object on the physical layer and going to the Features tab. The feature is called WITH_CLAUSE_SUPPORTED.

Why the snap_id is not generated sequentially in statspack?

I submitted some snaps manually, and thru dbms_job, the snap_ids are not sequential:
SQL> select SNAP_ID,to_char(SNAP_TIME,'DD-MON-YY HH24:MI') timestamp from stats$snapshot order by 1;
SNAP_ID TIMESTAMP
1 22-AUG-06 08:19
2 22-AUG-06 08:19
3 22-AUG-06 08:26
4 22-AUG-06 08:26
11 22-AUG-06 10:32
22 22-AUG-06 12:26
31 23-AUG-06 07:53
32 23-AUG-06 08:29
41 23-AUG-06 19:00
42 23-AUG-06 23:00
51 24-AUG-06 03:00
52 24-AUG-06 07:00
Could someone explain? Thanks.
- Zack

It probably generates the snap_id using a sequence with a cache value of 10. When the shared pool is flushed or the db is shutdown the cached values will be lost.

"Do not generate SQL" VB macro

Similar Messages

Maybe you are looking for