xxxxx is disabled and will not be called. Reason: timeout SNAPSHOT_ID

In HANA Studio I see many following internal alerts

 Internal statistics server problem --- xxx is disabled and will not be called. Reason: timeout SNAPSHOT_ID: <timestamp>

I found below error message in Indexserver trace.

These issues fixed in SAP HANA SPS08 database maintenance version 85.05, Please check the release SAP note 2188592.

If you are in higher version still receiving these alerts then raised a ticket with SAP.

Regards

Satishbabu Gunukula, Oracle ACE

http://www.oracleracexpert.com

The description for Event ID 4096 from source Tableau Server (vizportal) cannot be found

I have noticed below Tableau Error messages in event Viewer. You might see similar error for other processes too.

The description for Event ID 4096 from source Tableau Server (vizportal) cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

The description for Event ID 4096 from source Tableau Server (Backgroundr) cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
As per Tableau when you receive these errors, check the status by following below steps.

Step1 : tabadmin status –v
Step2: Check Tableau Server Administrative Views to verify that Tableau server is behaving as expected.

If all the processes are running as expected, then the error messages can be ignored.

Please refer below KB article from tableau
http://kb.tableau.com/articles/issue/error-event-id-4096-in-windows-event-viewer-logs?lang=en-us

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

Oracle In-Memory vs SAP HANA, What is your choice?

This is one of the very important discussions between DBA’s and BASIS Admins. Let’s see what benchmark results say….!

• Oracle Database In-Memory brings breakthrough analytical performance to enable businesses to make real-time decisions rapidly and easily. It is compatible with all existing applications and there is no need to rewrite your application to take advantage of it. In contrast, with SAP HANA the application need to be rewritten

• Oracle Database In-Memory implements state-of-the-art technology to accelerate analytics by orders of magnitude to allow users to get immediate answers to business questions that previously took hours. This same Oracle in-memory technology is proven to speed up SAP applications 2x faster than SAP HANA on SAP's own benchmarks. Read the Benchmark white paper*
   
• Oracle Database In-Memory does not mandate that all data fit in memory. Frequently accessed data can be kept In-Memory while less active data is kept on much lower-cost flash and disk, providing even more cost savings. In contrast, SAP HANA can only handle database sizes that fit in memory
   
• Building on decades of innovation, Oracle Database offers a proven platform with integrated high availability and data protection to deliver a reliable, secure, "always-on" business operation you can count on. Does SAP HANA offer the same high availability capabilities? Read more.
   
• Oracle has been an active leader in publishing benchmarks on transaction processing performance as measured by SAP's own standard application benchmarks (SAP Standard Application Benchmarks). Oracle Database In-Memory now enables real-time analytics on live transactional data. With Oracle, performance optimizations are built in for both transactions and analytics, unlike HANA, which optimizes your database for analytics at the cost of slowing down transactions. Where is the benchmark demonstrating HANA transaction processing performance running the SAP standard application benchmarks on HANA?

 Source: https://www.oracle.com/corporate/features/oracle-powers-sap.html

• Oracle is compatible with Compatible with cloud computing, big data and data warehousing. SAP HANA Database cloud consolidation is also not feasible 

• No new APIs and minimal new DBA commands are required, making Oracle Database In-Memory trivial to implement and maintain. Because HANA is a new “platform” with unique operational procedures and programming practices, a new team or retraining is required.

• Oracle Database In-Memory’s unique dual format enables transparent scale-up and scale-out for analytics and OLTP workloads running together. HANA uses a column format for high-performance analytics, which has severe architectural limitations for OLTP performance and scalability. Scaleup and scale-out are very immature

Source: http://www.oracle.com/technetwork/database/options/dbim-vs-sap-hana-2215625.pdf

Now it’s your time to read the benchmarks white paper and understands the facts and take the decision.

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

SAP DBTech JDBC: [403]: internal error: Cannot get remote source objects: Unable to load driver manager

When trying to create “Remote source” to Microsoft SQL Server under Smart Data Access (SDA) using HANA received following error

SAP DBTech JDBC: [403]: internal error: Cannot get remote source objects: Unable to load driver manager 

By looking the error it looks like the driver does not exists or not installed properly.  To find out the driver install or not run below command, if you receive an error then its not installed.

#isql --help
SAP DBTech JDBC: [403]: internal error: Cannot get remote source objects: [unixODBC][Microsoft][ODBC Driver 11 for SQL Server][SQL Server]Login failed for user 'hanasdauser'. 

I have followed below steps to install the Drivers

1. Set the environment
# cd /hana/ms-odbc-driver/unixODBC-2.3.0
# export CPPFLAGS=”-DSIZEOF_LONG_INT=8”
# echo $CPPFLAGS
-DSIZEOF_LONG_INT=8

2. Configure
#./configure --prefix=/usr --libdir=/usr/lib64 --sysconfdir=/etc --enable-gui=no --enable-drivers=no --enable-iconv --with-iconv-char-enc=UTF8 --with-iconv-ucode-enc=UTF16LE

3. Run make utility
# make

4. Run make install
# make install

5. Test the driver is installed or not
# isql –help
unixODBC 2.3.0

After installing the driver I was able to create Remote Source in HANA under SDA.

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

Failed to get connections for connection [http://hostname:8000] using session locale [English]

Failed to get connections for connection [http://hostname:8000] using session locale [English].

I was trying to create a OLAP connection from CMC to HANA in BOXI4.1 SP6 for Analysis Office 2.x SSO setup and receive below error. All the server details verified and everything seems to be correct.

After doing some investigation I found that the issue is due to limitation in BI platform4.1 sp06 or lower.

It cannot able to connect to HANA in CMC because there is no data provider available.

Errors in MDAS log file
Creating a BICS application with alias [session-2:http://hostname:8000:dev:en_US:HTTP:CREDENTIALS:null]
JCoDestinationDataProvider adding destination session-2:http://hostname:8000:dev:en_US:HTTP:CREDENTIALS:null.
JCoDestinationDataProvider setting jco.destination.pool_capacity property to 0 because it was not specified. <exception> com.sap.ip.bi.base.service.connection.impl.ConnectionException: No connection factory found for type session-2:http://hostname:8000:dev:en_US:HTTP:CREDENTIALS:null/HTTP.
Possible Solution: Upgrade to BI 4.1 SP07 or higher then you should be able to connect using HTTP provider.

Refer below SAP Note for more info
2182585 - Cannot connect to the Hana via SAP Hana Http OLAP connection in CMC

Regards

Satishbabu Gunukula, Oracle ACE

http://www.oracleracexpert.com