Jdbc statement in case of an unknown database operation

hi,
in an application in java, which makes connection to the database using JDBC,
if for eg, i am not sure if the statement is going to be a select or update or insert, which method of Statement i should be using. ?
Thanx.

try execute() method of java.sql.Statement object.
hi,
in an application in java, which makes connection to the database using JDBC,
if for eg, i am not sure if the statement is going to be a select or update or insert, which method of Statement i should be using. ?
Thanx.

Similar Messages

Pushing case statement applied in answers formula to Database

Hi All,
There are three prompts, for which there is a kind of header report with narrative view, now when user selects value in prompt element1 and do not select anything in prompt element 2 and 3, in the header only element1 should be displayed and emlement2,3 and few other elements should be nullified, to do this, i used presentation variables for element2,3 directly in narrative view. but for other non-prompt elements not to show up, i used case statement like:
case when length(@{presntation_var}) > 0 then "display.column" else NULL end
Now OBIEE is executing in such a way that, it is retrieving all the columns from the database and then applying logical case statement at BI server level, I need to push this case statement to DB level, can anyone help me how this could be accomplished.
Thanks,
Sreekanth Jala

Hi
why cant u use the condition in RPD.
In rpd use the case condition and make that as a one logical column. Test=" Fact"."Service Revenue" / "Fact"."Hours Budget". make it as a logical sum.
Then bring this column in to answerside, and use the case condition
case when
"Fact"."Location" <> 'X'
then
(" Fact""Test")
else
"Fact"."Hourly Rate"
end
Regards,
VG

How to insert an image file as blob using JDBC Statement

Hi,
I'm new on java.
I want the code to insert an image file in Oracle database whose data type is blob.
i want to use JDBC statement not the prepared statement.
Please help me out.

user8739226 wrote:
thanks for the solution.
I want to ask one thing
let say i've created a method in a bean in which i'm passing three parameters.
One is tablename as String, Second is Name of tablefields as Object, Third is Values as Object
Like:
public synchronized int insert(String table,Object[] fields, Object[] values)Ah now we're getting somewhere. I was trying to come up with a situation where using a regular Statement over PreparedStatement would be viable and came up with practically nothing.
In the method body i'm accessing the table fields and values and combining them into the insert sql query.
how can i do this using preparedstatment.
how do i come to know here in this bean that this value is int or string or date at runtime to use setInt, setString, setdate or setBlob respectively.That's your problem. Bad design. You want to make some sort of universal insert method that can insert anything anywhere. But it doesn't really make sense, because whenever you're trying to insert something, you know exactly what you want to insert and where. You could use a PreparedStatement at that point (although encapsulate it in its own method). Now you're trying to create your own poorly designed framework over JDBC that doesn't solve problems, only increases them.
Above was the only reason i saw, i was using statement instead of preparedstatment as statement was looking easy in this situation.
please, give me the solution of above using preparedstatment.No, rather you should reconsider your design. What advantage does your insert() method give you over, let's say using a regular PreparedStatement. Granted, you can put your connection opening and other boilerplate code in the method. But if that's your only problem, then your insert method isn't gonna be much use. You could always switch to JPA for example and work with that.

Why we use Tables statement in case of using SELECT-OPTIONS:

hi all,
Why we use Tables statement in case of using the following coding in an ABAP program ...
tables: vbak.
SELECT-OPTIONS: s1 for vbak-vbeln.
here if we dont provide the tables statement why it does not work ????
pls answwer ....???

Hi
This statement is not allowed in classes and declares a data object table_wa as a table work area whose data type is adopted from the identically named structured data type table_wa from the ABAP Dictionary. table_wa must be defined as a flat structure in the ABAP Dictionary. You can specify database tables or Views for table_wa.
Work table areas declared with TABLES are interface work areas and should only be declared in the global declaration section of a program for the following purpose:
reward if usefull
The statement TABLES is required for exchanging data between screen fields that were defined in a program screen when transferring from the ABAP Dictionary and the ABAP program. For the screen event PBO, the content of the table work area is transferred to identically named screen fields; for PAI, the system adopts the data from identically named screen fields.
In executable programs, flat table work areas can be used for adopting data that were provided for the event GET table_wa from a linked logical database. TABLES is synonymous with the statement NODES for this purpose.
Work table areas declared with TABLES behave like the data declared with the addition COMMON PART, meaning the data are used by the programs of a program group.
Table work areas declared with TABLES can be declared in subroutines and
function modules. However, this is not recommended. A table work area declared in a procedure is not local but belongs to the context of a framework program. The table work area can be viewed starting from the declaration in the framework program and lives as long as the framework program. In contrast to normal program-global data, the content of the table work areas declared in subroutines and function modules is stored temporarily when these subroutines and function modules are called. Value assignments that were made during runtime of the procedure are preserved until the procedure is completed. When exiting the procedure, the table work areas are filled with the contents that they contained when the procedure was called. Table work areas declared in procedures behave like global data to which the statement LOCAL is applied in the procedure.
The form TABLES * is obsolete.

Unable to retrieve Object.Error in File: Unknown Database Connector Error

Hi,
I have deployed two report on BO XI server. Both the reports are designed in Crystal Report designer XI.
I got all database credentilas, saved in CMC by my administrator so that these reports should not prompt me for any database login parameters when I am trying to run them from BOXI test server.
When I am running one of my report, the report is working fine. But this is not the case with other report.
This second report is working well with some inputs.
Case 1 - It is having to input date parameter(Date1 and Date2), when I am entering one input date parameter (Date1) and other (Date2) is set to NULL, it is displaying correct result. But when I am giving any date for Date2 it is throwing me an error -
"Error in File Manager_Agent_Report.rpt: Unknown Database Connector Error
Unable to retrieve Object.
Error in File Manager_Agent_Report.rpt: Unknown Database Connector Error "
Case 2 - Similiarly it is having an other input field which I am using in filetering the records in Report.
If I am setting it to NULL or If I am not giving this field, while entering the input. I am getting an output.
But incase I am giving this particular field then again it is promptig me the above mentioned error.
The report are working fine if I am executing them from crystal report designer.
Please help me to find a solution for the same.
Thanks
Deepak

Deepak, firstly are you trying to connect to one database or two in these reports? I would check the ODBC connections both in server and client machine (testing server or whatever you testing it on). Make sure both connection settings are exactly the same.
Secondly I will check the parameters values under Objects under the CMC and see if there is anything changed there.
Report back if you have checked both and it still giving errors
Regards
Jehanzeb

Unknown Database Connector Error Details: "Failed to retrieve SQL Error"

Hi
Getting "Failed to retrieve SQL Error" while trying to refresh the Crystal report.
Unable to create a new report also
This is my ERROR MESSAGE
"Unknown Database Connector Error Details: "Failed to retrieve SQL Error"
Previous Error: Query generated multiple SQL statements.However multiple SQL is not supported in crystal reports query panel"
Any Suggestion.

Hi,
Please note that any query that generates multiple SQL statements is not supported in the Query Panel in Crystal Reports.
I guess this Universe is generating multiple SQLs and hence the error.
I found this option while I was searching for something else: Could you try turning off the "Multiple SQL statement for each measure" in the Universe parameters and see if it works?
Also, here's the Universe Support Guide, although old, it is still applicable:
http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20984c2b-17f1-2b10-1091-d18977f7cd8f?QuickLink=index&overridelayout=true
-Abhilash

Unknown Database Connector Error in CR XI R2 sp6

I'm getting an "Unknown Database Connector Error" when I try to Set Data Source Location. This is effecting all of my reports and is happening on multiple copies of CR XI. I'm trying to connect to MS SQL using an ODBC (RDO) connection. The reports were initially working fine connecting to the datasource and then something changed. The current connection is blank and when I try to create a new connection I get the above error.
I tried updating CR to the latest version (what a pain! kept running into the Missing CrystalReport.msi problem). Finally figured out how to fix that but the updates did not solve my connection problem.
I ran the SQL Connectivity Test app and here are the results:
SQLDriverConnect Successful
[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'I3_IC'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
ODBC Version is : 03
SQL Driver Name is : SQLSRV32
SQL Driver Version is : 03.86.3959
SQL Driver Supported ODBC Version is : 03
SQL DBMS Name is : Microsoft SQL Server
SQL DBMS Version is : 10.00.2531
I am running Crystal on a Windows Server 2003 Enterprise Edition system. It's a developement and testing server. I also tried running CR on a Windows XP workstation connection to the same SQL server with the same results.
Any help would be greatly appreciated. I am totally stumped.

Hello,
mmmmmm.. From the driver name it's SQL Server 2000 you are using?
Have a look at your PATH statement to see if MS SQL is in there. It should look something like this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>path
PATH=C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;.....
It may be that your ODBCINI in the registry is corrupted so removing all and adding them back in may help. Use the ODBC Administrator to remove your DSN's, don't modify the registry.
Also create your DSN's using the System tab so all users and processes have access to them.
Thank you
Don

ERROR Util: unknown database type (name=MySQL)???

running WLS V8.2 on Solaris...
Recently migrated a developed EAR application from a Windows machine (v8.1) to a Solaris test environment (v8.2). Getting a weird error with JDBC connections to a MySQL database:
[ExecuteThread: '14' for queue
: 'weblogic.kernel.Default'][]:
unknown database type found. datbase name = MySQL, database driver name = MySQL-AB JDBC Driver]
No idea why. Do JDBC drivers have to be registered to WLS? Seems odd. Should be fine just including the MySQL JDBC drivers in with the startup classpath. And I don't understand why the problem doesn't occur on Windows?
mvh - Matthew Young

IMO that's because MySQL is not MS SQL
Slava
"Maggie Verdier" <[email protected]> wrote in message news:4231082.1103754343585.JavaMail.root@jserv5...
Actually it does happen on windows. I am running on windows 2000 and Weblogic 8.1.4 using a MS SQL database and I get the sameerror when I try to start the db connections with a jnetdirect driver. I did not get this error on sp3. Did you get a solution to
this?

CASE STATEMENTS AND CASE EXPRESSIONS IN ORACLE9I PL/SQL

제품 : PL/SQL
작성날짜 : 2001-11-13
CASE STATEMENTS AND CASE EXPRESSIONS IN ORACLE9I PL/SQL
=======================================================
PURPOSE
아래의 자료는 Case 문에서 oracle 8.1.7과 Oracle 9i의 New Feature로 8.1.7에서는
sqlplus 에서만 가능했고, 9i 부터는 pl/sql 까지 가능하다.
Explanation
1. Oracle 8.1.7 Feature
Oracle 8.1.7 에서 Case 문은 Decode 문과 유사하지만, 기존의 decode 문을 쓰는 것보다
더 많은 확장성과 Logical Power와 좋은 성능을 제공한다. 주로 나이와 같이 category 별로
나눌때 주로 사용하고 Syntex는 아래와 같다.
CASE WHEN <cond1> THEN <v1> WHEN <cond2> THEN <v2> ... [ELSE <vn+1> ] END
각각의 WHEN...THEN 절의 argument 는 255 까지 가능하고 이 Limit를 해결하려면
Oracle 8i Reference를 참조하면 된다.
The maximum number of arguments in a CASE expression is 255, and each
WHEN ... THEN pair counts as two arguments. To avoid exceeding the limit of 128 choices,
you can nest CASE expressions. That is expr1 can itself be a CASE expression.
Case Example : 한 회사의 모든 종업원의 평균 봉급을 계산하는데 봉급이 $2000보다 작은경우
2000으로 계산을 하는 방법이 pl/sql을 대신하여 case function을 사용할 수 있다.
SELECT AVG(CASE when e.sal > 2000 THEN e.sal ELSE 2000 end) FROM emp e;
Case Example : 나이를 column으로 가지고 있는 customer table을 예로 들어보자.
SQL> SELECT
2 SUM(CASE WHEN age BETWEEN 70 AND 79 THEN 1 ELSE 0 END) as "70-79",
3 SUM(CASE WHEN age BETWEEN 80 AND 89 THEN 1 ELSE 0 END) as "80-89",
4 SUM(CASE WHEN age BETWEEN 90 AND 99 THEN 1 ELSE 0 END) as "90-99",
5 SUM(CASE WHEN age > 99 THEN 1 ELSE 0 END) as "100+"
6 FROM customer;
70-79 80-89 90-99 100+
4 2 3 1
1 SELECT
2 (CASE WHEN age BETWEEN 70 AND 79 THEN '70-79'
3 WHEN age BETWEEN 80 and 89 THEN '80-89'
4 WHEN age BETWEEN 90 and 99 THEN '90-99'
5 WHEN age > 99 THEN '100+' END) as age_group,
6 COUNT(*) as age_count
7 FROM customer
8 GROUP BY
9 (CASE WHEN age BETWEEN 70 AND 79 THEN '70-79'
10 WHEN age BETWEEN 80 and 89 THEN '80-89'
11 WHEN age BETWEEN 90 and 99 THEN '90-99'
12* WHEN age > 99 THEN '100+' END)
SQL> /
AGE_G AGE_COUNT
100+ 1
70-79 4
80-89 2
90-99 3
Example
2. Oracle 9i Feature
Oracle 9i부터는 pl/sql에서도 case문을 사용할 수 있으면 이것은
복잡한 if-else 구문을 없애고, C언어의 switch문과 같은 기능을 한다.
아래의 9i pl/sql Sample 및 제약 사항을 보면 아래와 같다.
Sample 1:
A simple example demonstrating the proper syntax for a case
statement
using a character variable as the selector. See the section entitled
'Restrictions' at the end of this article for details on which PLSQL
datatypes may appear as a selector in a case statement or
expression.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
achar char(1) := '&achar';
begin
case achar
when 'A' then dbms_output.put_line('The description was Excellent');
when 'B' then dbms_output.put_line('The description was Very Good');
when 'C' then dbms_output.put_line('The description was Good');
when 'D' then dbms_output.put_line('The description was Fair');
when 'F' then dbms_output.put_line('The description was Poor');
else dbms_output.put_line('The description was No such Grade');
end case;
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 2:
A simple example demonstrating the proper syntax for a case
expression
using a character variable as the selector. See the section entitled
'Restrictions' at the end of this article for details on which PLSQL
datatypes may appear as a selector in a case statement or
expression.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
achar char(1) := '&achar';
description varchar2(20);
begin
description :=
case achar
when 'A' then 'Excellent'
when 'B' then 'Very Good'
when 'C' then 'Good'
when 'D' then 'Fair'
when 'F' then 'Poor'
else 'No such grade'
end;
dbms_output.put_line('The description was ' || description);
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
NOTE: The above simple samples demonstrate two subtle differences in the
syntax
required for case statements and expressions.
1) A case STATEMENT is terminated using the 'end case' keywords; a
case
EXPRESSION is terminated using only the 'end' keyword.
2) Each item in a case STATEMENT consists of one or more
statements, each
terminated by a semicolon. Each item in a case expression
consists of
exactly one expression, not terminated by a semicolon.
Sample 3:
Sample 1 demonstrates a simple case statement in which the selector
is
compared for equality with each item in the case statement body.
PL/SQL
also provides a 'searched' case statement as an alternative; rather
than
providing a selector and a list of values, each item in the body of
the
case statement provides its own predicate. This predicate can be any
valid boolean expression, but only one case will be selected.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
achar char(1) := '&achar';
begin
case
when achar = 'A' then dbms_output.put_line('The description was
Excellent');
when achar = 'B' then dbms_output.put_line('The description was Very
Good');
when achar = 'C' then dbms_output.put_line('The description was
Good');
when achar = 'D' then dbms_output.put_line('The description was
Fair');
when achar = 'F' then dbms_output.put_line('The description was
Poor');
else dbms_output.put_line('The description was No such Grade');
end case;
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 4:
This sample demonstrates the proper syntax for a case expression of
the
type discussed in Sample 3 above.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
achar char(1) := '&achar';
description varchar2(20);
begin
description :=
case
when achar = 'A' then 'Excellent'
when achar = 'B' then 'Very Good'
when achar = 'C' then 'Good'
when achar = 'D' then 'Fair'
when achar = 'F' then 'Poor'
else 'No such grade'
end;
dbms_output.put_line('The description was ' || description);
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 5:
This sample demonstrates the use of nested case statements. It is
also
permissable to nest case expressions within a case statement (though
it
is not demonstrated here), but nesting of case statements within a
case
expression is not possible since statements do not return any value.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
anum1 number := &anum1;
anum2 number := &anum2;
answer number;
begin
case anum1
when 1 then case anum2
when 1 then answer := 10;
when 2 then answer := 20;
when 3 then answer := 30;
else answer := 999;
end case;
when 2 then case anum2
when 1 then answer := 15;
when 2 then answer := 25;
when 3 then answer := 35;
else answer := 777;
end case;
else answer := 555;
end case;
dbms_output.put_line('The answer is ' || answer);
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 6:
This sample demonstrates nesting of case expressions within another
case
expression. Note again the absence of semicolons to terminate both
the
nested case expression and the individual cases of those
expressions.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
anum1 number := &anum1;
anum2 number := &anum2;
answer number;
begin
answer :=
case anum1
when 1 then case anum2
when 1 then 10
when 2 then 20
when 3 then 30
else 999
end
when 2 then case anum2
when 1 then 15
when 2 then 25
when 3 then 35
else 777
end
else 555
end;
dbms_output.put_line('The answer is ' || answer);
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Although PL/SQL anonymous blocks have been used in all of the examples
so far,
case statements and expressions can also be used in procedures,
functions, and
packages with no changes to the syntax.
The following samples are included for completeness and demonstrate the
use of
case statements and/or expressions in each of these scenarios.
Sample 7:
This sample demonstrates use of a case statement in a stored
procedure.
Note that this sample also demonstrates that it is possible for each
of
the items in the case body to consist of more than one statement.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
create or replace procedure testcasestmt ( anum IN number ) is
begin
case
when anum = 1 then dbms_output.put_line('The number was One');
dbms_output.put_line('In case 1');
when anum = 2 then dbms_output.put_line('The number was Two');
dbms_output.put_line('In case 2');
when anum = 3 then dbms_output.put_line('The number was Three');
dbms_output.put_line('In case 3');
when anum = 4 then dbms_output.put_line('The number was Four');
dbms_output.put_line('In case 4');
when anum = 5 then dbms_output.put_line('The number was Five');
dbms_output.put_line('In case 5');
else dbms_output.put_line('The description was Invalid input');
dbms_output.put_line('In the else case');
end case;
end;
exec testcasestmt(&anum);
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 8:
This sample demonstrates the use of a case statement in a stored
package.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
create or replace package testpkg2 is
procedure testcasestmt ( anum IN number );
function testcasestmt_f ( anum IN number ) return number;
end testpkg2;
create or replace package body testpkg2 is
procedure testcasestmt ( anum IN number ) is
begin
case
when anum = 1 then dbms_output.put_line('The number was One');
dbms_output.put_line('In case 1');
when anum = 2 then dbms_output.put_line('The number was Two');
dbms_output.put_line('In case 2');
when anum = 3 then dbms_output.put_line('The number was Three');
dbms_output.put_line('In case 3');
when anum = 4 then dbms_output.put_line('The number was Four');
dbms_output.put_line('In case 4');
when anum = 5 then dbms_output.put_line('The number was Five');
dbms_output.put_line('In case 5');
else dbms_output.put_line('The description was Invalid input');
dbms_output.put_line('In the else case');
end case;
end;
function testcasestmt_f ( anum IN number ) return number is
begin
case
when anum = 1 then dbms_output.put_line('The number was One');
dbms_output.put_line('In case 1');
when anum = 2 then dbms_output.put_line('The number was Two');
dbms_output.put_line('In case 2');
when anum = 3 then dbms_output.put_line('The number was Three');
dbms_output.put_line('In case 3');
when anum = 4 then dbms_output.put_line('The number was Four');
dbms_output.put_line('In case 4');
when anum = 5 then dbms_output.put_line('The number was Five');
dbms_output.put_line('In case 5');
else dbms_output.put_line('The description was Invalid input');
dbms_output.put_line('In the else case');
end case;
return anum;
end;
end testpkg2;
exec testpkg2.testcasestmt(&anum);
variable numout number
exec :numout := testpkg2.testcasestmt_f(&anum);
print numout
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 9:
This sample demonstrates the use of a case expression in a stored
package.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
create or replace package testpkg is
procedure testcase ( anum IN number );
function testcase_f ( anum IN number ) return number;
end testpkg;
create or replace package body testpkg is
procedure testcase ( anum IN number ) is
anumber number := anum;
anothernum number;
begin
anothernum :=
case
when anumber = 1 then anumber + 1
when anumber = 2 then anumber + 2
when anumber = 3 then anumber + 3
when anumber = 4 then anumber + 4
when anumber = 5 then anumber + 5
else 999
end;
dbms_output.put_line('The number was ' || anothernum);
end;
function testcase_f ( anum IN number ) return number is
anumber number := anum;
anothernum number;
begin
anothernum :=
case
when anumber = 1 then anumber + 1
when anumber = 2 then anumber + 2
when anumber = 3 then anumber + 3
when anumber = 4 then anumber + 4
when anumber = 5 then anumber + 5
else 999
end;
dbms_output.put_line('The number was ' || anothernum);
return anothernum;
end;
end testpkg;
variable numout number
exec testpkg.testcase(&anum);
exec :numout := testpkg.testcase_f(&anum);
print numout
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
제약 사항
다음의 databasetype은 case 문에서 지원되지 않는다.
BLOB
BFILE
VARRAY
Nested Table
PL/SQL Record
PL/SQL Version 2 tables (index by tables)
Object type (user-defined type)
All of these types except for object types face a similar restriction
even for if statements (i.e. they cannot be compared for equality directly) so this is unlikely to change for these types. Lack of support for object types is simply an implementation restriction which may be relaxed in future releases.
Reference Ducumment
Oracle 8.1.7 Manual
NOTE:131557.1

I have done the following code but doesn't
like the statement of - "case(butNext)". What do you mean "doesn't like" -- did you get an error message?
I'm guessing it won't compile because you're trying to switch on a Button.
I tried something
like "g.fillOval(100,50,70,90, BorderLayout.NORTH)"...no that doesn't make sense. You only use BorderLayout.NORTH when you're adding components to a BorderLayout layout manager. An oval is not a component and fillOval isn't adding a component and Graphics is not a Panel or layout manager.
Would appreciate it if someone could tell me how to position
shapes using the graohic method. I think the problem is that you're confusing shapes with components.

How to get the jdbc statement profile in 8.1

the wls 8.1 api does not have the methods in the wls 7 api for jdbc statement profiling...
in 7, the connection pool mbean has
setSqlStmtProfilingEnabled()
and the connection pool runtime mbean has
getStatementProfiles(int index, int count)
but in 8, i don't see these. i see the JDBCStatementProfile object in the api, but i don't see how to enable it or retrieve it.
is this feature removed? or moved?
thanks

Thanks for your response. But I need Process ID
not Product ID.
GetCurrentProcessID
Function should return you Process ID.
Gaurav Khanna | Microsoft .NET MVP | Microsoft Community Contributor

Golden Gate - DML statements are not replicated to target database

Hi,
Testing Environment
Source:
OS: RHEL 4.6, Database: 11gR2, Golden Gate 10.4, ASM
extract ext1
connection to database
userid ggate, password qwerty
hostname and port for trail
rmthost win2003, mgrport 7800
path and name for trial
rmttrail C:\app\admin\GOLDENGATE\dirdat\lt
EXTTRAIL /u01/oracle/goldengate/dirdat/lt
--TRANLOGOPTIONS ASMUSER SYS@ASM, ASMPASSWORD sys ALTARCHIVELOGDEST /u03/app/arch/ORCL/archivelog
--DDL support
ddl include mapped objname sender.*;
--DML
table sender.*;
Target:
OS: Windows 2003, Database: 11gR2, Golden Gate 10.4
--replicate group
replicat rep1
--source and target defintions
ASSUMETARGETDEFS
--target database login
userid ggate, password ggate
--file for discared transaction
discardfile C:\app\admin\GOLDENGATE\discard\rep1_disc.txt, append, megabytes 10
--ddl support
DDL
--specifying table mapping
map sender.* ,target receiver.* ;
I've Successfully setup Oracle Golden Gate test environment as above.
DDL statements are replicating successfully to target database.
while DML statements are not being replicated to target database.
Pl. try to solve the problem
Regards,
Edited by: Vihang Astik on Jul 2, 2010 2:33 PM

Almost ok but how you will handle the overlapping (transactions captured by expdp & captured by Extract too) of transactions for the new table ?
Metalink doc ID 1332674.1 has the complete steps. Follow the "without HANDLECOLLISIONS" approach.

BOE XI R2 Error on failed instance: Unknown Database Connector Error

I have a recurring job that runs against a high availability instance of our SAP production server. This job runs every 15 minutes to make sure that the HAS reporting instanace is available to my BOE environment for reporting. This morning, one of my recurring instances failed and the associated message was "Unknown Database Connection Error." The application and system event logs on my BOE server for the period immediately prior to the instance failure did not show any issues or unusual behavior. Basis reviewed AS400 logs for the SAP instance and didn't see anything there either.
Has anyone experienced a similar error nessage for a failed instance in this sort of a scenario? The next recurring instance, and so far all subsequent runs, have been successful.

David,
We have the same problem at times; the work around we found was to retry. Our standard is retry 3 time and wait 180 seconds. I believe the problem comes from network congestion. Our jobs usually complete on the first retry.
TB

JDBC Statement Profiling

Hi,
I have turned on JDBC Statement Profiling on my server. I can
get the statements being executed, but the Start & Stop times or
all Statements is the same. The relevant code and output follows.
Anybody see what I am doing wrong.
thanks,
Harish.
public static void printJDBCStatement(JDBCStatementProfile mb) {
System.out.println("\tStatement: " + mb.getStatementText());
System.out.println("\t\ttime = " + mb.getTimeTaken());
System.out.println("\t\tstarttime = " + mb.getStartTime());
System.out.println("\t\tendtime = " + mb.getStopTime());
System.out.println("\t\tthread = " + mb.getThreadId());
System.out.println("\t\tParams:");
int cnt = mb.getParameterCount();
for(int i=0; i<cnt;i++) {
System.out.println("\t\t\tParam " + (i+1) + mb.getParameter(i+1));
     Statements:
     Statement: INSERT INTO QUERY (ID, TYPE, OWNER, OBJVERSION) VALUES (?, ?, ?,
0)
          time = 0
          starttime = 1033591935157
          endtime = 1033591935157
          thread = Thread-15
          Params:
               Param 132397
               Param 212650
               Param 399999999
     Statement: SELECT OBJVERSION FROM QUERY WHERE ID = ? FOR UPDATE NOWAIT
          time = 0
          starttime = 1033591935167
          endtime = 1033591935167
          thread = Thread-15
          Params:
               Param 132397
     Statement: DELETE FROM SELECT_LIST WHERE QUERY_ID = ?
          time = 0
          starttime = 1033591935177
          endtime = 1033591935177
          thread = Thread-15
          Params:
               Param 132397
     Statement: SELECT 5, OBJVERSION, 0 FROM QUERY WHERE ID = ?
          time = 0
          starttime = 1033591935187
          endtime = 1033591935187
          thread = Thread-15
          Params:
               Param 132397

"Harish" <[email protected]> wrote in message
news:[email protected]..
>
I know for a fact that the statements take more than a 1ms.Could you try to run this code and tell what it prints?
public class test {
public static void main(String args[]) throws Throwable {
long previousTime = 0;
long currentTime = 0;
for (int i = 1; i < 1000000; i++) {
previousTime = System.currentTimeMillis();
// Thread.sleep(20);
currentTime = System.currentTimeMillis();
if (currentTime != previousTime) {
System.out.println("Difference: " + (currentTime - previousTime));
Regards,
SlavaImeshev
>
thanks,
Harish.
"Slava Imeshev" <[email protected]> wrote:
Hi Harish,
AFAIR this fact means that execution time is
less than 1ms. It's because java timer is not
very good at measuring precise periods of time.
So these digits are pretty good :)
Regards,
Slava Imeshev
"Harish" <[email protected]> wrote in message
news:3d9b6cfd$[email protected]..
Hi,
I have turned on JDBC Statement Profiling on my server. I can
get the statements being executed, but the Start & Stop times or
all Statements is the same. The relevant code and output follows.
Anybody see what I am doing wrong.
thanks,
Harish.
public static void printJDBCStatement(JDBCStatementProfile mb){>
Statements:
Statement: INSERT INTO QUERY (ID, TYPE, OWNER, OBJVERSION) VALUES
0)
time = 0
starttime = 1033591935157
endtime = 1033591935157
thread = Thread-15
Params:
Param 132397
Param 212650
Param 399999999
Statement: SELECT OBJVERSION FROM QUERY WHERE ID = ? FOR UPDATE NOWAIT
time = 0
starttime = 1033591935167
endtime = 1033591935167
thread = Thread-15
Params:
Param 132397
Statement: DELETE FROM SELECT_LIST WHERE QUERY_ID = ?
time = 0
starttime = 1033591935177
endtime = 1033591935177
thread = Thread-15
Params:
Param 132397
Statement: SELECT 5, OBJVERSION, 0 FROM QUERY WHERE ID = ?
time = 0
starttime = 1033591935187
endtime = 1033591935187
thread = Thread-15
Params:
Param 132397

Unknown Database Connector Error - when published

Post Author: dommurphy21
CA Forum: Deployment
Hi,
Im trying to get a Crystal Report to run when published to my BOXI Enterprise server. I get the following error when trying to run the report
CrystalReportViewer
Unable to retrieve Object.Error in File UseTable.rpt: Unknown Database Connector Error
The report runs on my PC using an oracle connection and I have also setup the orace driver and client on the Server and can connect to the database from the server. I'm using the same TNSNAMES entries on my client that are also on the server.
Could you please respond asap as once this simple issue is resolved I can get on with completing my Proof of Concept.
RegardsDominic

Post Author: colin mackenzie
CA Forum: Deployment
Hi Dominic. I had a similar problem in the past.When you go to publish your report try this.Select the Object.Select the Process Tab.Select the Database Tab.Select the radio button or option button "Use custom database logon information specified here"Inside the drop down list select Oracle.Enter your server name or tnsname "whatever.world"Enter your database name, this doesn't really matter you can enter anything will work here. (Whatever world - Production)Try that and let me know if that solves the problem.

Unknown Database connector Error - Crystal Reports 2008 and OLE DB

Hi,
I want to create a report based on OLE DB provider.
Once I Select it from the Database Expert list I get this Error: "Unknown Database Connector Error", and the list is empty.
I am using Crystal Reports 2008 on Win XP SP2.
SQL Server 2005 is installed on the local machine.
If I create a UDL File and double click, I can see all OLE DB Providers on the machine.
What am I missing ?
Thanks,
Yuval.

Hi Friends,
Thank you all for trying to help.
- The installed MDAC version is 2.8 (It comes with XP SP2). I have tried installing it again and it says that it is already installed.
- I am not using a bussiness view. Just the simplest blank report in CR2008. I am not able to start it using OLE DB, once I want to choose a provider - I get the error, before even entering connection details such as username and password.
- I am able to build an ODBC report, but when trying to view it using Crystal Reports Windows Form Viewer (from within a .Net application) I get an error: "Failed to Open The Connection". It happens also with reports built on other machines using OLE DB.
Same report works fine with the same application on different machines and I cannot figure out what is the difference.
I think Something on my machine is not right.
Any suggestions ?
Thanks,
Yuval.

Jdbc statement in case of an unknown database operation

Similar Messages

Maybe you are looking for