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

Note 1732157 - Collecting support information for SAP HANA.

If you open any ticket with HANA, first they will ask you to collect the dump.

Collecting the dump is very simple in HANA and follows the steps.

1. Open HANA Studio -->  go to ‘Diagnosis files’ --> In ‘Diagnosis Information’ click  'List '
2. Select the dates where you had the issue or you want to collect diagnosis information --> Click “OK”
3. Collecting the diagnosis information will take time and once it finish “Download the Collection”

The dump will be created under below path
/usr/sap/SID/SYS/global/sapcontrol/snapshots

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

Webinar: Convert Single Instance to RAC

This Webinar helps Oracle community to understand the "RAC Benefits" and how to "Convert your single instance to RAC”.

Date and time: Friday, March 18th, 2016 8:00 am-9:00am
Pacific Daylight Time (San Francisco, GMT-07:00)

This Webinar covers following Topics.

• Oracle RAC and its Benefits
• Overview of different RAC conversion methods
• Overview of different Storage options
• Convert Single instance to Oracle RAC Using RMAN
• Overview
• Prerequisites
• Demonstration
• Check the logs
• Post Conversion Steps
• References
• Contact Info
• Q&A

To register for this Webinar, please send an email to SatishbabuGunukula@gmail.com and reserve your spot. Note that registrations are limited and accepted on first come and first serve basis.

You will receive an email confirmation with meeting session link. For presentation link Click here .

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

How to enable and disable HANA Client Trace

Use hdbodbc_cons for tracing applications based on ODBC and hdbsqldbc_cons for tracing applications based on SQLDBC.

Use blow syntax

hdbodbc_cons.exe trace <level> <on/off>

Where levels are:
             api: tracing of ODBC api calls
             debug: detailed tracing of whole call stack
             sql: tracing of sql commands as well as output and parameter handling

Before you trun on trace, first configure the trace file name.

C:\Program Files\sap\hdbclient>hdbodbc_cons.exe config trace filename C:\temp\hdbodbc_trace.log

To turn on/off trace use below examples

Tracing of sql commands as well as output and parameter handling
          C:\Program Files\sap\hdbclient>hdbodbc_cons.exe trace sql on
          C:\Program Files\sap\hdbclient>hdbodbc_cons.exe trace sql off

Detailed tracing of whole call stack
          C:\Program Files\sap\hdbclient>hdbodbc_cons.exe trace debug on
          C:\Program Files\sap\hdbclient>hdbodbc_cons.exe trace debug off

Tracing of ODBC api calls
           C:\Program Files\sap\hdbclient>hdbodbc_cons.exe trace api on
           C:\Program Files\sap\hdbclient>hdbodbc_cons.exe trace api off

Reference:-
SAP Note: 1993254 - Collecting ODBC Trace
SAP Note: 1993251 - Collecting SQLDBC Trace

Regards,

Satishbabu Gunukula, Oracle ACE

http://www.oracleracexpert.com

SAP DBTech JDBC: [2048]: column store error: search table error

We have received following error when selection data from an reporting application.

[SAP AG][LIBODBCHDB DLL][HDBODBC] General error;2048 column store error: search table error: [1000002] exception 1000002: ltt/impl/memory.cpp:86 Allocation failed ; $size$=1573119; $name$=ihm; $type$=pool; $inuse_count$=80; $allocated_size$=109062096 exception 1000002: ltt/impl/memory.cpp:86 Allocation failed ; $size$=209664; $name$=temp_aggregates; $type$=pool; $inuse_count$=946; $allocated_size$=58136000 Unable to create extract

Sometimes you will not get complete error message in the application log. It’s always good idea to run the query in HANA studio to get the complete error.

I have ran the same query manually using HANA studio and got the below error

SAP DBTech JDBC: [2048]: column store error: search table error: [9] Memory allocation failed
If you look at the error carefully you should be able to identify that “memory allocation failed”. Normally you will see this error when there is a statement memory limit set for the application user or end user running the query.

I have increased the memory for the user using below command and the issue has been resolved.
ALTER USER <username> SET PARAMETER STATEMENT MEMORY LIMIT = <gb>

You need to identify the optimal value for you environment to avoid these errors.

To reset a statement limit use the SQL statement:
ALTER USER <username> CLEAR PARAMETER STATEMENT MEMORY LIMIT

Note that in order to enable statement memory limit you must enable STATEMENT MEMORY TRACKING IN THE GLOBAL.INI FILE.

The below parameters must be ON.
enable_tracking = on
memory_tracking = on

You should be able to view the memory consumption of a statement in M_EXPENSIVE_STATEMENTS.MEMORY_SIZE.

Regards,
Satishbabu Gunukula, Oracle ACE