Enable access to the Tableau Server repository (Postgres) and update repository access job has failed

Users can connect to tableau server repository suing tableau desktop using 2 built-in user’s i.e tableau, readonly. For reading database tableau and in-depth analysis it is recommended to use readonly user.

Before you use readonly user you need to enable the access . In older versions you will be using “tabadmin” command and in newer versions you will be using “tsm”.

Users will be connecting to tableau repository using port 8060.

Run below command to enable repository access

tabadmin dbpass --username readonly <password>

or

tsm data-access repository-access enable --repository-username readonly --repository-password <password >

When enabling the "readonly" user access i have received error using TSM.

61% - The services failed to stop. 66% - Disabling database services.
72% - Waiting for database services to disable.
The update repository access job has failed.
or
66% - An error occurred while waiting for services to reconfigure.
73% - Disabling database services.
80% - Waiting for database services to disable.
The update repository access job has failed. 

I tried different ways but didn’t help. Finally I have stopped the services and ran the above TSM command and it executed successfully.

Steps:

stop tableau services using TSM

run the command - tsm data-access repository-access enable --repository-username readonly --repository-password <password > 

start tableau services using TSM

This operation will perform a server restart. Are you sure you wish to continue?
(y/n): y
Starting update repository access asynchronous job.
Job id is '8', timeout is 25 minutes.
5% - Enabling the maintenance app.
11% - Waiting for the maintenance app to start.
16% - Reading configuration.
22% - Putting the repository into local trust mode.
27% - Enabling the database services.
33% - Waiting for the database services to enable.
38% - Updating the roles in the repository.
44% - Taking the repository out of local trust mode.
50% - Updated pending configuration.
55% - Disabling all services.
61% - Waiting for the services to stop.
66% - Updating the configuration version on nodes.
72% - Waiting for services to reconfigure.
77% - Enabling all services.
83% - Waiting for the services to start.
88% - Reloading postgres configuration.
94% - Disabling database services.
100% - Waiting for database services to disable.
Successfully updated repository access.

Regards

Satishbabu Gunukula, Oracle ACE

http://www.oracleracexpert.com

Best practices for running Tableau on a VM (Virtual Machine)

Tableau Server is resource-intensive and latency-sensitive, that’s why if you are running Tableau on a VM then dedicated resources required.

1.       Dedicated vCPU

100% dedicated vCPU allocation – should not be pooled or shared.

Core count is based on "physical" cores. Physical cores can represent actual server hardware or cores on a virtual machine (VM). Hyper-threading is ignored.

2.       Dedicated RAM

Fully (100%) pre-allocated, no pooling or sharing, no dynamic RAM.

Contiguous on the host server.

Suggested 128GB RAM per 8 core for Enterprise Deployments.

3.       Disk

Write speed is often the bottle neck, faster the better!

150MB/s or less = BAD

250MB/s+ WRITE = GOOD

400MB/s to 1GB/s+ = GREAT

250MB/s Write & 1GB/s Read = Good performance

Tiered SAN: Tableau should be on higher tier with better IO than typical storage level tier.

No underlying network attached storage (NAS) for disk.

Always note that Poorly tuned VM’s results “Poor performance” and Wasted $$ on core purchases

VM Tuning Tips Directly From VMWare

  

•       Performance Best Practices for vSphere 5.5

                 (http://www.vmware.com/pdf/Perf_Best_Practices_vSphere5.5.pdf)

–        See page 17 for recommended BIOS setting

•       Deploying Extremely Latency-Sensitive Applications in vSphere 5.5 (http://www.vmware.com/files/pdf/techpaper/latency-sensitive-perf-vsphere55.pdf)

–        See page 15 for best practices for latency-sensitive applications

•       Upgrade network adapter driver in VM cluster

Other things needs to consider

•       Virus Scan can impact performance

–        Improve Performance by using antivirus exclusions

•       Network latency between worker machines should be less than 10ms.

•       Single network hop between servers (contiguous network access).

Regards
Satishbabu Gunukula, Oracle ACE
http://oracleracexpert.com

Unable to Connect to Published Data Sources When Opening a Downloaded Workbook from Tableau Server

I recently upgraded Tableau server from 9.1.2 to 9.1.3 to fix an issue with Data Server Data source. After upgrade we found below issue during the testing.

While opening a downloaded workbook from tableau server we received “Tableau Server Sign In” but URL greyed out and also URL is not correct as it is replaced by host name.

Normally you should receive a prompt to log in to the Tableau server, instead the server name field default to http://localhost and is unavailable for edit.

When we try to connect we got following error and not able to connect to published data source.

Cannot connect to Tableau Server. Please check the server name and port and try again. Internet communication error: SSL peer certificate or SSH remote key was not OK (analysis-server1)

It looks like the tableau server is not configured to recognize all the alias host names used to connect to the server. I have followed below steps to update the URL and port and able to resolve the issue.


1. Open command prompt as an administrator and go to the Tableau Server bin folder.
cd C:\Program Files\Tableau\Tableau Server\9.1\bin

2. Run the following command:
tabadmin set gateway.public.host "name"

where name is the URL used to connect to Tableau Server. For example:
tabadmin set gateway.public.host "analysis.oracleracexpert.com" 

3. If Tableau Server is configured for SSL, you must also run the following command:
tabadmin set gateway.public.port 443

4. Apply the configuration changes, and restart Tableau Server using following commands
tabadmin config
tabadmin restart

If a load balancer or proxy is in front of Tableau Server, the headers are not set.  Please refer to the following Knowledge Base article for information on the required headers

Reverse Proxy Server URL Reverts to Internal URL

http://kb.tableau.com/articles/issue/reverse-proxy-server-url-reverts-to-internal-url

Regards,

Satishbabu Gunukula, Oracle ACE

http://www.oracleracexpert.com