Support

Loading JSON (and XML) data is possible in WhereScape RED, but does involve a number of steps, and may differ depending on the database platform (some platforms have native JSON &/or XML support while others do not...

Wherescape RED can be easily used in conjunction with Amazon’s cloud service, Amazon Relational Database Services (RDS). This document explains the few extra steps needed to upload a file source into an AWS SQL Server database. Description You can create a metadata reposit...

This provides an example of sending an email summary of a job once it completes.  This utilizes the Success & Failure Commands available on a job, and Microsoft SQL Server Database Mail. Pre-Requisites Microsoft SQL Server Database Mail has been configured and tested Installation...

Incremental Load by Date Note: Combine this with your Incremental Load by ID. Example of use within load table: 1. Create 3 parameters     Current_dt     Full_load_flag     Last_run_dt 2. Create two custom stored procedures (Code for procedur...

This process can work for both Microsoft SQL Server & Oracle.  There are separate attachments for each of these. Steps to Implement Incremental Load by ID 1. Create a custom procedure (code attached)     update_last_seq_id_parameter 2. In load table job descript...

It is possible to have RED Host Scripts that call external programs or processes and if these scripts are run by the RED scheduler service it can require the service to be able to interact with the Windows desktop. This is normally achieved either by running the service as a user account or by r...

There may be times when an error similar to the following occurs: A file that is required cannot be installed because the cabinet file c:\Users\<user>\AppData\Roaming\WhereScape Software Limited\WhereScape RED 6.8.4.00\install\disk1.cab has an invalid digital signature.  This may i...

Requirements and Assumptions A user account will be provisioned to Linux to run the scripts provided by WhereScape. This user is a trusted account and requires no other permissions that are described in this document. The trusted user and the scheduler employs CRON services. Th...

"Runtime Libraries Error "Missing api-ms-win-crt-runtime-l1-1.0.dll" Our Testing Team has discovered that, in some situations, a system error mentioning missing runtime libraries may occur. These Runtime Libraries are normally installed with the regular Windows Updates but can ea...

Registering Your License Key WhereScape RED requires a valid licensee and license key. This information and key are normally supplied in a separate email. In WhereScape's Setup Administrator, click on the Computer Setup tab in the left pane; Then click on th...

The recommended method of creating a Fact table is to create a Stage table and use this as the source for the fact table. If you try to create a Fact table directly from a Data Store or Normalised table you may see a procedure compile error and the resulting code contains a line like: ...

RED metadata can be backed up and restored to another database (which must already have a RED metadata repository installed using Setup Administrator). One of the two options available to do this is using the Backup > Export Metadata and Backup > Restore Metadata options. If these options ...

 If you experience application crash issues when using an Oracle repository database, the most likely cause is that the ODBC DSN for the RED repository database (the "Data Warehouse" connection) is using the Oracle ODBC driver (i.e. the ODBC driver installed with the Oracle Client). ...

Scenario Logging in to a RED repository created with Oracle on Linux you see an error "ORA 12154:TNS: Could not resolve the connect identifier specified." The same error is reported when using any other application that connects to Oracle using an ODBC DSN created with...

A common warning seen in the Scheduler audit log when using Integration Services loads is:   Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the s...

Scenario When running an Integration Services load in a SQL Server repository either interactively or via the Scheduler, an error with message "WhereScape SSIS Integrator stopped working" sometimes. Additionally, the below error message may also pop up in this case: Cause ...

Scenario Integration Services loads on a newly configured computer (PC or server) do not work. You may see an error similar to "Execution of Image WslSDL.exe failed". Cause RED Integration Services loads require components that are installed with SQL Server client tools, specifically...

Scenario RED can automatically generate Integration Services packages for Load tables, however in some situations it is a requirement to run an arbitrary Integration Services package that contains some specialised functionality or has been migrated from a legacy environment. Sol...

Scenario: Deploying an OLAP Cube from RED to a SQL Server 2012 RTM instance of Analysis Services results in an error message that includes the line: Deserialization failed: Requested value 'EnterpriseCore64' was not found. Cause: Analysis Services 2012 u...

Scenario There is an OLAP Cube that contains one or more partitioned measure groups. The "# Historic Partitions Updated" property on the measure group is set to some number e.g. 2 When the cube is updated, either interactively or via the Scheduler, all dimensions are processed ...

Connections are the access mechanisms to the different information stores throughout the organization.  They define the information necessary to get to each set of data whether as a source or even as your main target.  RED is context sensitive in that once the connection is defined, what y...

WhereScape RED - Azure SQL Support RED does support Azure SQL family for the WS RED Metadata Repository and DWH Target but there are limitations with some of the Azure SQL offerings: Azure SQL DB (limited RED functionality) Azure SQL MI (untested but is supposedly 100% compliant with SQL Server...

 By default WhereScape 3D installs it's own 32-bit Java runtime and starts as a 32-bit application - this is for compatibility with WhereScape RED. However, you can run 3D as a 64-bit application if you wish. To do this you will need to first have a 64-bit version of the Java run...

The setup for 3D prompts for a "storage location" which by default is a non-user-specific location like "C:\WhereScape\3D\". This configuration is intended for a single user PC and in this configuration you will not be able to start a second concurrent session of 3D on th...

WhereScape have identified an issue in WhereScape 3D 2.7.0.0 when using the Export/Import function for Model Conversion Rules. THE PROBLEM When a rule contains a Description and you create XML export including this rule, the created XML will not import. You instead receive the fo...

Registering Your License Key WhereScape 3D requires a valid licensee and license key. This information and key are normally supplied in a separate email. In WhereScape3D, click on the Help from the top menu; Then click on the Change license menu item. This menu ...

Step 1: Create a Postgres ODBC DSN called '3DRepo' pointing to your 3D repository. Save the credentials in the ODBC DSN. Step 2: Create a Host Script in RED / PowerShell 64 type and add the code below: (This script is used to remove all locks from the repository. A back-up is only...