Generate report for Server Job
Moderators: chulett, rschirm, roy
Generate report for Server Job
I have generated a report for a server job.
It is three stages - Source is hash file - transformer - target is Oracle OCI stage.
My action code in Oracle OCI is
Update exisitng rows or insert new rows/
When I view the report, I see the following statements under Oracle OCI stage
1. User defind SQL
update....
insert ....
2. User Defined Create table
Create table....
3. User Defined Drop table.
Drop table ...
My question is that when I view the Oracle OCI stage, I don to see any Create table/Drop table SQL. I only see the User defined SQL (update..../Insert statements)
Any ideas to find why drop and create statements are generated.
ketfos
It is three stages - Source is hash file - transformer - target is Oracle OCI stage.
My action code in Oracle OCI is
Update exisitng rows or insert new rows/
When I view the report, I see the following statements under Oracle OCI stage
1. User defind SQL
update....
insert ....
2. User Defined Create table
Create table....
3. User Defined Drop table.
Drop table ...
My question is that when I view the Oracle OCI stage, I don to see any Create table/Drop table SQL. I only see the User defined SQL (update..../Insert statements)
Any ideas to find why drop and create statements are generated.
ketfos
ketfos
Oracle OCI : Oracle_OCI_20
Table Name: EXPOSURE
Enable case sensitive table name and column name:
Generate SQL: Yes
User-defined SQL: UPDATE EXPOSURE ..............
Pre 4.2 User-defined SQL Behavior: Yes
Array Size: 2000
Rows per transaction: 0
Create target table: No
Generate CREATE TABLE: Yes
User-defined CREATE TABLE: CREATE TABLE EXPOSURE ..........
Drop target table: No
Generate DROP TABLE: Yes
User-defined DROP TABLE: DROP TABLE EXPOSURE
Clear table: No
Update action: Update existing rows or insert new ones
Treat warning as fatal:
Transaction isolation level: Read Committed
Table Name: EXPOSURE
Enable case sensitive table name and column name:
Generate SQL: Yes
User-defined SQL: UPDATE EXPOSURE ..............
Pre 4.2 User-defined SQL Behavior: Yes
Array Size: 2000
Rows per transaction: 0
Create target table: No
Generate CREATE TABLE: Yes
User-defined CREATE TABLE: CREATE TABLE EXPOSURE ..........
Drop target table: No
Generate DROP TABLE: Yes
User-defined DROP TABLE: DROP TABLE EXPOSURE
Clear table: No
Update action: Update existing rows or insert new ones
Treat warning as fatal:
Transaction isolation level: Read Committed
ketfos
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The DML statements are present in case you ever decide to enable the "create table" property possibly with the "drop table" sub-property. There's nothing there to be concerned about.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Exactly, standard stage stuff. That option doesn't get a lot of play in my experience as you can't use it to simply create the target table once like you could with say a hashed file. It will happily create it but then fail on every subsequent run as the object 'already exists'. Use it if you have a table you need to drop and recreate on every run.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers