Bulk Insert

Buffer Size (KB)

Used for limiting the number of bytes each time data is inserted in a database table.

Bulk Insert

Transaction Boundary

Controls the batch size for an insert in a database table.

Temporary table

Database Name

Database where the temporary table will be created. This property applies only to IBM OS/390 because IBM OS/390 requires database name qualifier to be part of the CREATE TABLE statement. If left blank, OS/390 will default the target database to a system database for which the users may not have Create Table privileges.

Temporary table

Owner

Table owner name used to qualify a temporary table name in a SQL statement, for example to create the table owner.tablename. If left blank, the user name specified in the writeable connection pool is used to qualify the table name and the Shared Logon field on the General tab should also be set.

Temporary table

Prefix

When the Oracle BI Server creates a temporary table, these are the first two characters in the temporary table name. The default value is TT.

Temporary table

Tablespace Name

Tablespace where the temporary table will be created. This property applies to OS/390 only as OS/390 requires tablespace name qualifier to be part of the CREATE TABLE statement. If left blank, OS/390 will default the target database to a system database for which the users may not have Create Table privileges.

Unicode Database Type

Select this check box when working with columns of an explicit Unicode data type, such as NCHAR, in an Unicode database. This makes sure that the binding is correct and data will be inserted correctly. Different database vendors provide different character data types and different levels of Unicode support. Use the following general guidelines to determine when to set this check box:

• On a database where CHAR data type supports Unicode and there is no separate NCHAR data type, do not select this check box.
• On a database where NCHAR data type is available, it is recommended to select this check box.
• On a database where CHAR and NCHAR data type are configured to support Unicode, selecting this check box is optional.

NOTE:  Unicode and non-Unicode datatypes cannot coexist in a single non-Unicode database. For example, mixing the CHAR and NCHAR data types in a single non-Unicode database environment is not supported.