For security reasons, some database administrators do not allow every user the right to create or drop tables. If the database user account that is used to initialize SAS^® Customer Experience Targeting and to run the extract, transform, and load (ETL) jobs does not have these permissions, jobs that create and drop tables fail with the following error:

70                Libname CXAWH ORACLE PATH = CXAP DBMAX_TEXT = 3000
ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=NO DBSERVER_MAX_BYTES=1
70       ! DBCLIENT_MAX_BYTES=1 UPDATE_LOCK_TYPE=RO schema= APPCXA
AuthDomain='Oracle_CXA'
                                ________________
                                23
ERROR: Libname CXAWH is not assigned.
ERROR: Error in the LIBNAME statement.
ERROR 23-7: Invalid value for the UPDATE_LOCK_TYPE option.

There is no solution or workaround for this problem.

To obtain a fix for this issue, contact SAS Technical Support.

This fix includes the following changes:

• Changes to the priming job: The priming job assumes an empty database (no tables) because it runs the DDL to create tables. The fix adds an option that passes the DDL to a database administrator, enabling the administrator to create the tables up front. Then, the step in the priming job that creates tables is skipped.


• Changes to ETL jobs: Some load jobs use temporary tables in the database to improve performance. These tables are created dynamically, and the tables are dropped when they are no longer needed. The fix includes an option that passes the DDL to a database administrator, enabling the administrator to create the tables once. Then, during the ETL process, the administrator can insert data into the tables and delete records from them as necessary (rather than creating and dropping entire tables). Administrators should be aware that using this option has had a negative impact on performance because deleting and inserting into a table is slower than dropping and re-creating the table.

Operating System and Release Information