You can access a Yellowbrick database by using SAS/ACCESS^® Interface to PostgreSQL. With this hot fix, you can use the Yellowbrick utilties for bulk load and bulk unload.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Usage and Restrictions

Here are the new options to use the Yellowbrick bulk utilities:

Syntax: YBUNLOAD = YES/NO
Description: Turns Yellowbrick bulk unload on or off.
Default: NO
Example:

Syntax: YBLOAD = YES/NO
Description: Turns Yellowbrick bulk load on or off.
Default: NO
Example:

Syntax: BL_YB_PATH =
Description: Specifies the path and file name of the bulk load and bulk unload utilities if they are not in the default path. This option can also be used to specify the batch file instead. 
Default: none
Alias: BL_PSQL_PATH=
Example:

Syntax: YB_JAVA_HOME =
Description: Specifies the path to an alternative Java 1.8 Java Runtime Environment (JRE)/Java Development Kit (JDK).
Default: none
Example:

Restrictions

• PRESERVE_NAMES=YES is required with YBUNLOAD=YES if the table has mixed-case column names or special characters.
• Values for a Boolean data type are returned as TRUE or FALSE.
• The PostgreSQL BL_LOAD_METHOD= option is not supported with Yellowbrick.
• The dollar special character ($) is not supported in column or table names.

Known Issues

• You cannot use the $ and " characters in a WHERE statement when YBUNLOAD=YES is set. You can use them if these characters are escaped. 
• The PostgreSQL BL_ESCAPE= option accepts only the values ON and OFF.
• PRESERVE_COL_NAME=YES is not being honored when using YBUNLOAD=YES. Use PRESERVE_NAMES=YES as workaround.

Error Files

Any errors that occur with loading rows are written to a log file. That log file has the path/file name specified by the BL_LOGFILE option. If you do not specify the BL_LOGFILE option, the default log file is generated in the BL_<table name>_<#>.log.

Example

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to PostgreSQL 9.4_M6 is available at:

A fix for this issue for SAS/ACCESS Interface to PostgreSQL 9.4_M5 is available at: