SAP BW HANA
Hi,
Is HANA part of BW 7.3 by default, or should it be purchased as extra?
Priya
Hi Priya,
SAP HANA is not part of BW 7.3. Hana needs additional License.
Similar Messages
-
Replicate in Two Locations? SAP B1 HANA High Availability
Hello Experts! Hope this message finds you well.
Can we replicate SAP B1 HANA to a standby server that is in another location?
Example Active Server\Central Server at my New York Data Center and Standby Server in Ohio
What would be needed in terms of high speed pipe between locations and NTP to synch time to a common time server.
Thank you for your advice.
EdHi Ed,
Currently the two locations have to be within ~100 KM of each other. You find this in section 14 of the HANA admin guide for SP6. You can open a support ticket asking what to consider if you want a distance greater than 100KM.
Best regards,
Duncan -
OVerseas SAP BI/HANA jobs and Visa possibilities.
HI All,
can anyone please tell me job market for SAP BI/HANA in overseas and what is employer expectations.
is it posisble to get a job for other countries and suggest me how to apporach.
Regards,
Sakthivel SJob opportunities are available in the overseas market. Get a certification in BI/HANA as you mentioned, then you can try for the applying the job.
if you have experience, possibility of getting job is easier.
apply jobs through job portals
Thanks
Sudhir Krishna Kumar Singh -
SAP B1 HANA - Query conversion
hello
how would I change this to work in SAP b1 HANA Sbo trns notification stored procedure?
IF @OBJECT_TYPE='17' AND @TRANSACTION_TYPE in ('U','A')
BEGIN
IF exists
(select count(*) from rdr1 T0 inner join oitm T1 on T0.ItemCode = T1.ItemCode inner join OITW t2 on t2.ItemCode = t1.ItemCode and t0.WhsCode = t2.WhsCode
where T1.U_ALLOWNEG = 'No'
AND T0.DocEntry = @list_of_cols_val_tab_del
having SUM(t2.OnHand + t2.OnOrder - t2.IsCommited ) < 0 )
select TOP 1 @ERROR = 1 ,@ERROR_MESSAGE = 'This Item Cannot be Ordered - Causing Negative Stock' ENDHi,
Please check this document http://scn.sap.com/docs/DOC-47664
Thanks & Regards,
Nagarajan -
SAP B1 HANA Installation Problem
Hi,
Please help, we are trying to install SAP B1 HANA PL04.
Here's the scenario;
1. Installation of SLE Server - Done
2. Installation of SAP HANA Server - Done (was able to access HANA Studio, install DB client)
3. Installation of SAP B1 HANA - Failed
It seems that Tomcat causes the problem.
Please help on how to resolve this.
TIA,
NormanHi Duncan,
after manually cleaning up previous installation of Server Components we proceed with the full install of PL11 and this time it worked! The new installer is much better than PL04 since it also includes the B1 Analytics and is eventually able to rollback failed components.
In our case we had a problem with XApp Framework but hopefully we will figure it out.... support suggested to upgrade the AFL first however we were already using the latest AFL from rev.69.
Do you have any idea why the XApp failed and rolled back?
All other systems and services installed and run flawlessly now!
Thanks.
Best regards,
Fabrizio -
SAP HANA, developer edition 1.0 SPS 09 created from SAP CAL running on AWS.
I am receiving the following errors when executing a query in HANA via jdbc.
The first execution runs for 6 minutes then produces this error:
Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [2]: general error: Allocation failed $REASON$
Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [2048]: column store error: [9] Memory allocation failed
I re execute the query it runs for 25 minutes then produces the same error.
Then the instance is unresponsive.
If I look in HANA studio general overview there is plenty of memory and cpu available to the HANA instance.
There is also a crush dump listed in the log files.
I see the following errors in the indexserver_alert_vhcalhdbdb.trc on the HANA server:
[3742]{-1}[-1/-1] 2015-03-18 18:41:42.430797 e Licensing
LicenseMeasurementPersistence.cpp(00161) : Error storing license measurement for application id '000670', value 26 at ' 2015-03-18 18:41:39.3910000', internal error
[3742]{-1}[-1/-1] 2015-03-18 18:41:42.430999 e Licensing
LicensePluginRegistry.cpp(00394) : Error storing license measurement: internal error
[3732]{300601}[27/-1] 2015-03-18 18:30:16.406867 e Executor
PlanExecutor.cpp(00825) : pop1245 (rc 9, Memory allocation failed)
pop = RowPlanOperator() # pop1245
pop.setDetails('')
[3732]{300601}[27/-1] 2015-03-18 18:30:16.406890 e Executor
PlanExecutor.cpp(00825) : pop1243 (rc 9, Memory allocation failed)
[4437]{300601}[27/-1] 2015-03-18 18:28:13.921145 e Memory
ReportMemoryProblems.cpp(00799) : 8: 0x00007f0b1ba7a8c5 in ptime::TrexPlanOp::executePtimeOp(ltt_adp::vector<Executor::PlanData*, ltt::integral_constant<bool, true> > const&, ltt_adp::vector<Executor::PlanData*, ltt::integral_constant<bool, true> > const&, TRexCommonObjects::TRexApiError&, Executor::ExecutionInfo const&)+0x41 at trex_plan.cc:340 (libhdbcswrapper.so)
The memory errors are repeated many times.
What is the recommendation to investigate this issue?
Thank you.The file indexserver_alert_vhcalhdbdb.trc contains the following errors:
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 1: 0x00007f049f94df0a in _ZN5ptime3pcc16MonitorAllocBase14throwExceptionEv.isra.53+0x22 at pcc_MonitorAlloc.h:61 (libhdbrskernel.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 2: 0x00007f049f9403f5 in ptime::Transaction::Transaction(ptime::Connection*, bool, bool, bool, bool)+0x18f1 at pcc_MonitorAlloc.h:114 (libhdbrskernel.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 3: 0x00007f049ca15949 in ptime::TrexTempIndex::clearIndex() const+0x25 at trex_itab.cc:3020 (libhdbcswrapper.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 4: 0x00007f049eb7bd74 in ptime::TrexObjectFactory::destroyTrexTempIndexObject(char const*, char const*, char const*)+0x40 at trex_object_factory.cc:1386 (libhdbrskernel.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 5: 0x00007f049ca4e706 in ptime::TrexPlanData::~TrexPlanData()+0x1d2 at trex_plan_data.cc:49 (libhdbcswrapper.so)
6: 0x00007f049ca4e849 in ptime::TrexPlanData::~TrexPlanData()+0x5 at trex_plan_data.cc:53 (libhdbcswrapper.so)
7: 0x00007f04c44739ed in Executor::X2ConnectorValue::deleteItsValue()+0x29 at X2.cpp:323 (libhdbexecutor.so)
8: 0x00007f04c4488101 in Executor::X2::failPop(int)+0xb0 at X2.h:176 (libhdbexecutor.so)
9: 0x00007f04c44879b4 in Executor::X2::finishValue(Executor::X2ConnectorValue&, int&, bool)+0x110 at X2.cpp:920 (libhdbexecutor.so)
10: 0x00007f04c4488163 in Executor::X2::failPop(int)+0x110 at X2.cpp:3571 (libhdbexecutor.so)
11: 0x00007f04c44879b4 in Executor::X2::finishValue(Executor::X2ConnectorValue&, int&, bool)+0x110 at X2.cpp:920 (libhdbexecutor.so)
12: 0x00007f04c4488163 in Executor::X2::failPop(int)+0x110 at X2.cpp:3571 (libhdbexecutor.so)
13: 0x00007f04c44938d0 in Executor::X2::runPopTask(Executor::X2::PopTaskInfo&, int&, ltt::allocator&, ltt::allocator&)+0x1290 at X2.cpp:3548 (libhdbexecutor.so)
14: 0x00007f04c4494e32 in Executor::X2::runPopJob(Executor::X2Job*)+0x80 at X2.cpp:2956 (libhdbexecutor.so)
15: 0x00007f04c44956b8 in Executor::X2Job::run(Execution::JobObject&)+0x224 at X2.cpp:5294 (libhdbexecutor.so)
16: 0x00007f04ab3ec1fe in Execution::JobObjectImpl::run(Execution::JobWorker*)+0x72a at JobExecutorImpl.cpp:822 (libhdbbasis.so)
17: 0x00007f04ab3fadd2 in Execution::JobWorker::runJob(ltt::smartptr_handle<Execution::JobObjectForHandle>&)+0x2e0 at JobExecutorThreads.cpp:205 (libhdbbasis.so)
18: 0x00007f04ab3fbd24 in Execution::JobWorker::run(void*&)+0x1a0 at JobExecutorThreads.cpp:370 (libhdbbasis.so)
19: 0x00007f04ab433759 in Execution::Thread::staticMainImp(void**)+0x875 at Thread.cpp:492 (libhdbbasis.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 20: 0x00007f04ab4343bd in Execution::Thread::staticMain(void*)+0x39 at ThreadMain.cpp:26 (libhdbbasis.so)
[4190]{300560}[23/-1] 2015-03-19 10:57:26.576080 e Memory
ReportMemoryProblems.cpp(00799) : OUT OF MEMORY occurred.
Host: sid-hdb
Executable: hdbindexserver
PID: 3599
Failed to allocate 131088 byte.
Current callstack:
1: 0x00007f04ab5a07fd in MemoryManager::PoolAllocator::allocateNoThrowImpl(unsigned long, void const*)+0x2a9 at PoolAllocator.cpp:1139 (libhdbbasis.so)
2: 0x00007f049dcfca79 in ptime::pcc::SingletonAlloc<ptime::pcc::MonitorAlloc<ptime::pcc::HeapAlloc>, ptime::pcc::GlobalScope>::allocate(unsigned long)+0x15 at pcc_MonitorAlloc.h:97 (libhdbrskernel.so)
3: 0x00007f049e095b50 in ptime::fastvector<void*, 16ul>::__allocate(unsigned long)+0x50 at fastvector.h:325 (libhdbrskernel.so) -
Hi friends,
Is there any additional functionality in SD or any new learning required with the introduction of SAP HANA for SAP SD consultants?
HANA seems to be a latest technology now.
Appreciate your response.
Regards,
AnjiI personally think HANA will bring the BIG DATA concepts into BW, BOBJ reporting. It should be easier that we don't have to think in advance what reports will be developed. Instead, we throw every bit of data to BW/HANA without building InfoCubes. Any report can be then developed as we have all the data.
Let's see what others think. -
SAP CAL HANA - Connectivity issues
I deployed SAP HANA on AWS through SAP CAL.
I can connect to the HTTP interface and the HDB through the command line.
hdbsql=> \c -i 00 -u system
Password:
Connected to HDB@vhcalhdbdb:30015
hdbsql HDB=>
But if I try to connect to port 30015 remotely I just timeout. I have the 30015 open to the world in the AWS security group.
Is there a daemon that runs on the server that accepts remote connections or do I have a AWS network issue I need to investigate?Hi Joseph,
Most probably you are behind a corporate firewall that does not allow you to connect to port 30015. Could you try to connect from another network?
Best regards,
Stanimir -
Refresh/Copy of SAP BPC/HANA Environment
Hi experts,
We are running SAP BPC on HANA with BW as our EDW. We would like to refresh our Regression environment with Production. However, i understand that with HANA technology the refresh may not be as simple as just a copy exercise.
Could you please advise on what are the steps or procedures that we need to take note of when undertaking such an exercise?
Thank you.
Kind regards,
TLHi TL,
What kind of refresh you are talking about: is it BPC Backup & Restore or system backup and restore?
If it's BPC tool then you shouldn't see any difference from similar procedure on another DB.
If it's HANA backup and restore then it's a completely different thing depending if your HANA box is co-habituated or not.
Please clarify.
Regards,
Gersh -
SAP BW HANA NLS with SAP IQ - ODBC driver / DLL error in configuration
We have a SAP BW 7.4 system running on HANA and we had configured SAP IQ 16 as NLS on this system for performing a PoC. The configuration was successful and working but after few weeks this was giving error. We tried creating new database connection but with no success.
When we test the database connection by SE38 -> ADBC_TEST_CONNECTION, we get the below error -
The screenshot of the trace file showing the detail error is below -
Refer below the screenshot showing errors from RSDANLCON -
We have tested the ODBC connection on the IQ database server and there seems no issue there. If anyone has come across this error earlier and have resolution, then please advise.We had also configured NLS on our SAP BW 7.31 system (non-HANA) using the same IQ server (v 16), and this configuration was also successful and working but since last 2 weeks or so even that this is giving similar error. We tried creating new database connection and test but there is no success. Sharing the screenshot from SAP BW 7.31 system below -
SE38 -> ADBC_TEST_CONNECTION shows error as below -
The screenshot of the trace file showing the detail error is below -
Here the error is somewhat different and mentions the Sybase IQ 16 version is not supported. But this same connection was working when configured earlier.
Refer below the screenshot showing errors from RSDANLCON -
This could also be because of some mismatch in library files but I had checked with our Basis team and there was no upgrade to BW 7.31 system after the NLS was configured successfully earlier (which was just 4 weeks back). So any help for this scenario is also appreciated. -
SAP HANA Lifecycle Manager Couldn't deploy using credentials
Hello,
After HLM 1.0.7.7 upgrade from 1.0.6 on IBM appliance we could not apply support packages in normal mode. When we launch the Upgrade process from Hana Studio or Command line we recive the following message:
Error Message: Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.
Detailed Message: null or empty argument
Help: http://help.sap.com/hana
We tried to downdgrade and reinstall HLM again with no luck. Users, Parsswords and Certificates was also renewed. We could read this log from HLM.
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Submit for subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_GetUpdateTypeTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Submit for subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_GetUpdateTypeTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Starting execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Starting execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor
Starting process [Deploys SAP Host Agent configurations using sidadm credentials, com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmTask] ({})...
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor
Starting process [Deploys SAP Host Agent configurations using sidadm credentials, com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmTask] ({})...
INFO 2014-05-08 16:05:15 com.sap.lm.util.status.StatusTracker
Status tracker initialized using storage file /usr/sap/hlm_bootstraps/HNB/HLM/param/configdeploystatus.properties.
INFO 2014-05-08 16:05:15 com.sap.lm.util.status.StatusTracker
Status tracker initialized using storage file /usr/sap/hlm_bootstraps/HNB/HLM/param/configdeploystatus.properties.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Progress [ 0%]
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Progress [ 0%]
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor
Deploying SAP Host Agent configurations on host with sidadm credentials.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor
Deploying SAP Host Agent configurations on host with sidadm credentials.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Process message: Deploying SAP Host Agent configurations on host
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Process message: Deploying SAP Host Agent configurations on host
INFO 2014-05-08 16:05:16 com.sap.lm.services.hostcontrol.SAPHostControlService
Deployed Host Agent configurations [/usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-client-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/gen-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-studio-repository-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-nzdm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-hdbeuspack.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/chmod-file.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v2.conf] with signature /usr/sap/hlm_bootstraps/HNB/HLM/SIGNATURE.SMF on host .
INFO 2014-05-08 16:05:16 com.sap.lm.services.hostcontrol.SAPHostControlService
Deployed Host Agent configurations [/usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-client-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/gen-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-studio-repository-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-nzdm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-hdbeuspack.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/chmod-file.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v2.conf] with signature /usr/sap/hlm_bootstraps/HNB/HLM/SIGNATURE.SMF on host .
ERROR 2014-05-08 16:05:16 com.sap.lm.hana.hlm.update.slpp.task.AbstractUpdateProcessExecutor
Process executor failed
java.lang.IllegalArgumentException: null or empty argument
at com.sap.lm.hlm.common.runtime.HlmRuntime.assertNotNullOrEmptyArgumens(HlmRuntime.java:342)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:74)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:69)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor.deployconfigurations(AbstractDeployConfigProcessExecutor.java:114)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmProcessExecutor.executeInternal(DeployConfigWithSidAdmProcessExecutor.java:42)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor.startInterruptibleExecution(AbstractProcessExecutor.java:128)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor$1.run(AbstractProcessExecutor.java:108)
ERROR 2014-05-08 16:05:16 com.sap.lm.hana.hlm.update.slpp.task.AbstractUpdateProcessExecutor
Process executor failed
java.lang.IllegalArgumentException: null or empty argument
at com.sap.lm.hlm.common.runtime.HlmRuntime.assertNotNullOrEmptyArgumens(HlmRuntime.java:342)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:74)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:69)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor.deployconfigurations(AbstractDeployConfigProcessExecutor.java:114)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmProcessExecutor.executeInternal(DeployConfigWithSidAdmProcessExecutor.java:42)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor.startInterruptibleExecution(AbstractProcessExecutor.java:128)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor$1.run(AbstractProcessExecutor.java:108)
ERROR 2014-05-08 16:05:16 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask, Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.] has failed: {}
ERROR 2014-05-08 16:05:16 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask, Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.] has failed: {}
Could you please help us with this issue?
Kind Regards,
Message was edited by: Tom FlanaganHi Alston,
I'm sorry for the late reply. Are you still experiencing this error?
I've seen this issue before with another customer and the final resolution was to make sure the /etc/hosts file does not have the ipv6 BEFORE ipv4. Here is an example:
>> cat /etc/hosts
# special IPv6 addresses
::1 localhost ipv6-localhost
ipv6-loopback
ff02::3 ipv6-allhosts
192.168.180.31 abceccd01.sap.com abceccd01
192.168.180.34 abceccs01.sap.com abceccs01
192.168.180.35 abccrms01.sap.com abccrms01
192.168.180.30 abceccs01.sap.com abceccs01
10.36.10.5 abceccs01-nfs.sap.com abceccs01-nfs
The resolution would be to change the ordering. So the IPv6 section appears below the IPv4 section.
After that is done, perform the following to "reset" HLM.
1. Stop all browsers that have HLM pages open
2. Stop the Studio
3. Execute /usr/sap/hlm_bootstraps/<SID>/HLM/stop-hlm.sh –f
4. Check that there are no any left HLM processes
5. Go to /usr/sap/hlm_bootstraps/<SID>/HLM/param/
and rename all files except logging.properties
6. go to directory: /usr/sap/hlm_bootstraps/<SID>/HLM
and rename directory persistence
7 restart SAP Host Agent - as root: /usr/sap/hostctrl/exe/saphostexec
-restart
8. open HLM ui via browser:
https://<hostname>:1129/lmsl/HLM/<SID>/ui/
I hope this helps.
Best Regards,
Jimmy -
How do I get access to Mobile documents admin console login with SAP HANA Cloud cockpit?
Hi All,
I am trying to launch SAP Mobile Documents from my trail version of SAP HANA Cloud.
The Help link which I had followed via link:
https://help.hana.ondemand.com/help/frameset.htm?dc618538d97610148155d97dcd123c24.html#concept_0B49F10346C94249845EC16364FFF66D_76
In SAP Cloud HANA Cockpit Using the link available in Authorization>Authorization Management
I had created an user assigned to a Group, and Group has been assigned to a Role ODP-OPERATOR,
Next step, when I am trying to assign a token, I could not able find a token. How to get a token from here?
My intention of creating user, group, role and token is for getting access to Mobile documents admin console.
However I have also tried to access the mobile documents admin console via link
https://smd-p1886950994trial.hana.ondemand.com/mcm/admin
When I browse the above link, It shows HTTP 503 the requested service is not currently available.
I am not sure, How to get access Mobile documents Admin page from here
Could someone clarify on this please?
Regards,
Saravanan.RHi,
I have managed find an answer from this link SAP Mobile Documents on SAP HANA Cloud saying, SAP Mobile documents trial is not available in SAP HANA Cloud cockpit.
Regards,
Saravanan.R -
DBLINK truncation with SAP HANA db
Hi - I have Oracle 11g installed in my Windows laptop and dblink connected to SAP's HANA database via ODBC using the HANA odbc driver. My NVARCHAR data in HANA is being truncated in half. I am working thru sqlplus. Same result in SQL developer client tool. The VARCHAR data is ok. I created three Oracle instances with the only difference being the NLS_CHARACTERSET & NLS_NCHAR_CHARACTERSET values. I have three SIDS: orcl, orulu, and orclutf8. All with the same result. My gateway settings for each are all the same. I started testing with SID orcl and once I found that out I decided to create orclu and orclutf8. In our Unix boxes, we have orcl and orclu settings and those are behaving the same (we use unixodbc.org as the mgr).
I provided orclutf8 gateway .ora file and the orclut8 system info below.
Symptoms/Info:
The character set of HANA db is AL32UTF8.
The HANA db table contains NVARCHAR and have Unicode values (eg: em dash, even Chinese char). NVARCHAR columns gets cut in half as shown in sqlplus (same in sql developer).
For the half that do show up, the actual Unicode character shows up in sqlplus as either unprintable character or upside down question mark or a \u character. This is ok coz no abends therefore data gets process and let my customers deal with the non-converted data – it is ok with them.
Since all SIDs are behaving the same way, I provided you information for orclutf8: initdwutf.ora, the system info, and the trace file. Of all things that SHOULD work, it is the one with the exact character set to HANA.
I have two tables in HANA with the same number of columns and rows. Only difference is NVARCHAR versus VARCHAR.There are three columns with 3, 20, and 150 length.
I took a Oracle trace when selecting from each table and compared them both. I pasted a picture at the bottom. The left side is the VARCHAR and right side NVARCHAR. You can see the HANA odbc driver report a truncation issue on line 209 but I do not see this error in sqlplus. I have a SAP incident open on this.
Is there something in the Oracle side that can be tried? For example, in the trace compare picture, the VARCHAR trace shows that is doubled the data size for each column from 3, 20, and 150 to 6, 40, and 300. In the NVARCHAR it did not.
SID: orcl
SELECT value$ FROM sys.props$ WHERE name = 'NLS_CHARACTERSET’;
WE8MSWIN1252
SELECT value$ FROM sys.props$ WHERE name = 'NLS_NCHAR_CHARACTERSET’;
AL16UTF16
SID: orclu
SELECT value$ FROM sys.props$ WHERE name = 'NLS_CHARACTERSET’;
AL32UTF8
SELECT value$ FROM sys.props$ WHERE name = 'NLS_NCHAR_CHARACTERSET’;
AL16UTF16
SID: orclutf8
SELECT value$ FROM sys.props$ WHERE name = 'NLS_CHARACTERSET’;
AL32UTF8
SELECT value$ FROM sys.props$ WHERE name = 'NLS_NCHAR_CHARACTERSET’;
UTF8
initdw7utf.ora:
# This is a sample agent init file that contains the HS parameters that are
# needed for the Database Gateway for ODBC
# HS init parameters
#HS_FDS_CONNECT_INFO = <odbc data_source_name>
HS_FDS_CONNECT_INFO = HANADW7
HS_FDS_TRACE_LEVEL=DEBUG
#HS_LANGUAGE=AL32UTF8
HS_LANGUAGE=AMERICAN_AMERICA.AL32UTF8
HS_FDS_REMOTE_DB_CHARSET=AL32UTF8
# Environment variables required for the non-Oracle system
#set <envvar>=<value>
SELECT * FROM sys.props$:
DICT.BASE 2
DEFAULT_TEMP_TABLESPACE TEMP
DEFAULT_PERMANENT_TABLESPACE USERS
DEFAULT_EDITION ORA$BASE
Flashback Timestamp TimeZone GMT
TDE_MASTER_KEY_ID
DST_UPGRADE_STATE NONE
DST_PRIMARY_TT_VERSION 11
DST_SECONDARY_TT_VERSION 0
DEFAULT_TBS_TYPE SMALLFILE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET AL32UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET UTF8
NLS_RDBMS_VERSION 11.2.0.1.0
GLOBAL_DB_NAME ORCLUTF8
EXPORT_VIEWS_VERSION 8
WORKLOAD_CAPTURE_MODE
WORKLOAD_REPLAY_MODE
NO_USERID_VERIFIER_SALT 57505D68AFECC3BCECE484A1C42CC8CE
DBTIMEZONE 00:001) When I tried HS_KEEP_REMOTE_COLUMN_SIZE=LOCAL the nvarchar select statement still truncated and displayed them in sqlplus.
For the varchar select statement, it just error'ed out in sqlplus.
ERROR:
ORA-28562: Heterogeneous Services data truncation error
ORA-02063: preceding line from DEVUTF8
no rows selected
I commented out the HS_KEEP_REMOTE_COLUMN_SIZE=LOCAL for now.
2) For the nvarchar select statement, I do not get an error messages via sqlplus. I get the records displayed truncated in half they should be. A native odbc error do show up in the Oracle Trace file. I think that comes from the HANA odbc driver. It is line 209 of the picture in my original thread.
3) DESCRIBE commands output below:
SQL> desc ESBA_DB.ZTESTSAP@DEVUTF8 - THIS IS THE NVARCHAR TABLE. The sizes match what is in HANA db.
Name Null? Type
MANDT NOT NULL NVARCHAR2(3)
NAME NOT NULL NVARCHAR2(20)
NAME_150 NOT NULL NVARCHAR2(150)
SQL> desc PTAN.ZTESTSAP_VC@DEVUTF8 - THIS IS THE VARCHAR TABLE.The sizes do not match what is in HANA db.
Name Null? Type
MANDT VARCHAR2(1)
NAME VARCHAR2(6)
NAME150 VARCHAR2(50)
4) Below is the gateway trace. I included from the first occurence of hgodscr and all the way to the end of it. You can see the HANA odbc driver truncation.
Entered hgodscr, cursor id 1 at 2014/10/02-11:15:41
Allocate hoada @ 03705518
Entered hgopcda at 2014/10/02-11:15:41
Column:1(M): dtype:-9 (WVARCHAR), prc/scl:3/0, nullbl:1, octet:3, sign:1, radix:0
Exiting hgopcda, rc=0 at 2014/10/02-11:15:41
Entered hgopcda at 2014/10/02-11:15:41
Column:2(N): dtype:-9 (WVARCHAR), prc/scl:20/0, nullbl:1, octet:20, sign:1, radix:0
Exiting hgopcda, rc=0 at 2014/10/02-11:15:41
Entered hgopcda at 2014/10/02-11:15:41
Column:3(N): dtype:-9 (WVARCHAR), prc/scl:150/0, nullbl:1, octet:150, sign:1, radix:0
Exiting hgopcda, rc=0 at 2014/10/02-11:15:41
hgodscr, line 910: Printing hoada @ 03705518
MAX:3, ACTUAL:3, BRC:100, WHT=5 (SELECT_LIST)
hoadaMOD bit-values found (0x40:TREAT_AS_NCHAR)
DTY NULL-OK LEN MAXBUFLEN PR/SC CST IND MOD NAME
12 VARCHAR Y 3 3 128/ 3 1000 0 40 MANDT
12 VARCHAR Y 20 20 128/ 20 1000 0 40 NAME
12 VARCHAR Y 150 150 128/150 1000 0 40 NAME_150
Exiting hgodscr, rc=0 at 2014/10/02-11:15:41
Entered hgoftch, cursor id 1 at 2014/10/02-11:15:41
hgoftch, line 130: Printing hoada @ 03705518
MAX:3, ACTUAL:3, BRC:100, WHT=5 (SELECT_LIST)
hoadaMOD bit-values found (0x40:TREAT_AS_NCHAR)
DTY NULL-OK LEN MAXBUFLEN PR/SC CST IND MOD NAME
12 VARCHAR Y 3 3 128/ 3 1000 0 40 MANDT
12 VARCHAR Y 20 20 128/ 20 1000 0 40 NAME
12 VARCHAR Y 150 150 128/150 1000 0 40 NAME_150
Performing delayed open.
SQLBindCol: column 1, cdatatype: -8, bflsz: 6
SQLBindCol: column 2, cdatatype: -8, bflsz: 22
SQLBindCol: column 3, cdatatype: -8, bflsz: 152
Entered hgopoer at 2014/10/02-11:15:41
hgopoer, line 233: got native error 0 and sqlstate 01004; message follows...
[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}
Exiting hgopoer, rc=0 at 2014/10/02-11:15:41
hgoftch, line 740: calling SQLFetch got sqlstate 01004
SQLFetch: row: 1, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 1, column 1, bflsz: 6, bflar: 6, (bfl: 3, mbl: 3)
SQLFetch: row: 1, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 1, column 2, bflsz: 22, bflar: 6, (bfl: 20, mbl: 20)
SQLFetch: row: 1, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 1, column 3, bflsz: 152, bflar: 0, (bfl: 150, mbl: 150)
SQLFetch: row: 2, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 2, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 2, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 2, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 2, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 2, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 3, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 3, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 3, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 3, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 3, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 3, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 4, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 4, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 4, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 4, column 2, bflsz: 22, bflar: 6, (bfl: 0, mbl: 20)
SQLFetch: row: 4, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 4, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 5, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 5, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 5, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 5, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 5, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 5, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 6, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 6, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 6, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 6, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 6, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 6, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 7, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 7, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 7, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 7, column 2, bflsz: 22, bflar: 6, (bfl: 0, mbl: 20)
SQLFetch: row: 7, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 7, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 8, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 8, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 8, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 8, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 8, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 8, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 9, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 9, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 9, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 9, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 9, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 9, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 10, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 10, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 10, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 10, column 2, bflsz: 22, bflar: 6, (bfl: 0, mbl: 20)
SQLFetch: row: 10, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 10, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 11, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 11, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 11, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 11, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 11, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 11, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 12, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 12, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 12, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 12, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 12, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 12, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 13, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 13, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 13, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 13, column 2, bflsz: 22, bflar: 6, (bfl: 0, mbl: 20)
SQLFetch: row: 13, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 13, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 14, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 14, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 14, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 14, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 14, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 14, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 15, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 15, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 15, column 2, bflsz: 22, bflar: 40
SQLFetch: row: 15, column 2, bflsz: 22, bflar: 40, (bfl: 0, mbl: 20)
SQLFetch: row: 15, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 15, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 16, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 16, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 16, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 16, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 16, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 16, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 17, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 17, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 17, column 2, bflsz: 22, bflar: 32
SQLFetch: row: 17, column 2, bflsz: 22, bflar: 32, (bfl: 0, mbl: 20)
SQLFetch: row: 17, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 17, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 18, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 18, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 18, column 2, bflsz: 22, bflar: 40
SQLFetch: row: 18, column 2, bflsz: 22, bflar: 40, (bfl: 0, mbl: 20)
SQLFetch: row: 18, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 18, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 19, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 19, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 19, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 19, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 19, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 19, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 20, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 20, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 20, column 2, bflsz: 22, bflar: 2
SQLFetch: row: 20, column 2, bflsz: 22, bflar: 2, (bfl: 0, mbl: 20)
SQLFetch: row: 20, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 20, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 21, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 21, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 21, column 2, bflsz: 22, bflar: 2
SQLFetch: row: 21, column 2, bflsz: 22, bflar: 2, (bfl: 0, mbl: 20)
SQLFetch: row: 21, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 21, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 22, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 22, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 22, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 22, column 2, bflsz: 22, bflar: 6, (bfl: 0, mbl: 20)
SQLFetch: row: 22, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 22, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 23, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 23, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 23, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 23, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 23, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 23, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 24, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 24, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 24, column 2, bflsz: 22, bflar: 40
SQLFetch: row: 24, column 2, bflsz: 22, bflar: 40, (bfl: 0, mbl: 20)
SQLFetch: row: 24, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 24, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 25, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 25, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 25, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 25, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 25, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 25, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 26, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 26, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 26, column 2, bflsz: 22, bflar: 32
SQLFetch: row: 26, column 2, bflsz: 22, bflar: 32, (bfl: 0, mbl: 20)
SQLFetch: row: 26, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 26, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 27, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 27, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 27, column 2, bflsz: 22, bflar: 40
SQLFetch: row: 27, column 2, bflsz: 22, bflar: 40, (bfl: 0, mbl: 20)
SQLFetch: row: 27, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 27, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 28, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 28, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 28, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 28, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 28, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 28, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 29, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 29, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 29, column 2, bflsz: 22, bflar: 2
SQLFetch: row: 29, column 2, bflsz: 22, bflar: 2, (bfl: 0, mbl: 20)
SQLFetch: row: 29, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 29, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 30, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 30, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 30, column 2, bflsz: 22, bflar: 2
SQLFetch: row: 30, column 2, bflsz: 22, bflar: 2, (bfl: 0, mbl: 20)
SQLFetch: row: 30, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 30, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 31, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 31, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 31, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 31, column 2, bflsz: 22, bflar: 6, (bfl: 0, mbl: 20)
SQLFetch: row: 31, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 31, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 32, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 32, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 32, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 32, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 32, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 32, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 33, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 33, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 33, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 33, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 33, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 33, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 34, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 34, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 34, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 34, column 2, bflsz: 22, bflar: 6, (bfl: 0, mbl: 20)
SQLFetch: row: 34, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 34, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 35, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 35, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 35, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 35, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 35, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 35, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 36, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 36, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 36, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 36, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 36, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 36, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 37, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 37, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 37, column 2, bflsz: 22, bflar: 6
SQLFetch: row: 37, column 2, bflsz: 22, bflar: 6, (bfl: 0, mbl: 20)
SQLFetch: row: 37, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 37, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 38, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 38, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 38, column 2, bflsz: 22, bflar: 12
SQLFetch: row: 38, column 2, bflsz: 22, bflar: 12, (bfl: 0, mbl: 20)
SQLFetch: row: 38, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 38, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 39, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 39, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 39, column 2, bflsz: 22, bflar: 8
SQLFetch: row: 39, column 2, bflsz: 22, bflar: 8, (bfl: 0, mbl: 20)
SQLFetch: row: 39, column 3, bflsz: 152, bflar: 0
SQLFetch: row: 39, column 3, bflsz: 152, bflar: 0, (bfl: 0, mbl: 150)
SQLFetch: row: 40, column 1, bflsz: 6, bflar: 6
SQLFetch: row: 40, column 1, bflsz: 6, bflar: 6, (bfl: 0, mbl: 3)
SQLFetch: row: 40, column 2, bflsz: 22, bflar: 38
SQLFetch: row: 40, column 2, bflsz: 22, bflar: 38, (bfl: 0, mbl: 20)
SQLFetch: row: 40, column 3, bflsz: 152, bflar: 298
SQLFetch: row: 40, column 3, bflsz: 152, bflar: 298, (bfl: 0, mbl: 150)
40 rows fetched
Exiting hgoftch, rc=0 at 2014/10/02-11:15:42 with error ptr FILE:hgoftch.c LINE:740 ID:Fetch resultset data
Entered hgoftch, cursor id 1 at 2014/10/02-11:15:42
hgoftch, line 130: Printing hoada @ 03705518
MAX:3, ACTUAL:3, BRC:40, WHT=5 (SELECT_LIST)
hoadaMOD bit-values found (0x40:TREAT_AS_NCHAR)
DTY NULL-OK LEN MAXBUFLEN PR/SC CST IND MOD NAME
12 VARCHAR Y 4 3 128/ 3 1000 0 40 MANDT
12 VARCHAR Y 6 20 128/ 20 1000 0 40 NAME
12 VARCHAR Y 0 150 128/150 1000 0 40 NAME_150
0 rows fetched
Exiting hgoftch, rc=1403 at 2014/10/02-11:15:42
Entered hgoclse, cursor id 1 at 2014/10/02-11:15:46
Exiting hgoclse, rc=0 at 2014/10/02-11:15:46
Entered hgodafr, cursor id 1 at 2014/10/02-11:15:46
Free hoada @ 03705518
Exiting hgodafr, rc=0 at 2014/10/02-11:15:46
Entered hgocomm at 2014/10/02-11:15:46
keepinfo:0, tflag:1
00: 4F52434C 55544638 2E376265 35343664 [ORCLUTF8.7be546d]
10: 392E312E 32362E36 3630 [9.1.26.660]
tbid (len 23) is ...
00: 4F52434C 55544638 5B312E32 362E3636 [ORCLUTF8[1.26.66]
10: 305D5B31 2E345D [0][1.4]]
cmt(0):
Entered hgocpctx at 2014/10/02-11:15:46
Exiting hgocpctx, rc=0 at 2014/10/02-11:15:46
Exiting hgocomm, rc=0 at 2014/10/02-11:15:46
Entered hgolgof at 2014/10/02-11:15:46
tflag:1
Exiting hgolgof, rc=0 at 2014/10/02-11:15:46
Entered hgoexit at 2014/10/02-11:15:46
Exiting hgoexit, rc=0 -
What is SAP HANA DXC ???
Hi SAP HANA Experts,
Can anyone you tell me what is SAP HANA DXC ???
Is it a Add-On Or inbuilt software component available with SAP HANA DB Package Itself
Do we need to download the SAP HANA DXC individually ???
What is the path of the DXC Software component in SMP to view itHello guy,
The SAP HANA Direct Extractor Connection (DXC) is a means for providing out-of-the-box foundational data models to SAP HANA, which are based on SAP Business Suite entities. (No add-on need to be installed). DXC is also a data acquisition method for SAP HANA. With DXC, SAP Business Content DataSource Extractors are available to deliver data directly to SAP HANA
Refer to:
http://help.sap.com/hana/sap_hana_direct_extractor_connection_implementation_guide_en.pdf
1665602 - Setup & Config: SAP HANA Direct Extractor Connection (DXC)
Regards,
Ning Tong -
Update SAP Hana Database - Guides/Information
Hello,
Can you tell me how can I do an update/upgrade to our SAP Hana Database from revision 66 to the latest version?
I didn´t found any document which cover this type of activity. Can you tell me if there are some SAP documents/guides with that instruction how to update a SAP Hana DB!?
Thank you,
samid raifHi Samid,
You can have a look at http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf section 5 Updating the SAP HANA System.
Best regards,
Wenjun
Maybe you are looking for
-
Events in ABAP runtime.
Can Any one explain me the events in ABAP runtime with proper example please.
-
How do i print the current view on a pdf file
How do i print a current view on a pdf file i am looking at, i dont want to print the current page i want to zoom in and print that zoom.
-
Unable to locate and run the adobe flash player
Hi all, I am able to down load adobe flash player. i reboot also . I have windows xp. But I am unable to see any adobe flash button in start menu. I am unabel to see and short cut on the desktop. How should I start adobe flash player? Thanks & Regard
-
FM for getting Customer Material
Hi all, I need a FM which returns customer material when i give customer number, sales organization, distribution channel, material number as input. Thanks and regards Chandu.
-
PDF created is ENORMOUS! Why?
Hi, here goes, my first post here.... I created 2 * jpgs of a form, I then set them to A4 size, then I went to Acrobat Pro, and merged files into a single PDF. Great!, then I opened the document, yikes! it fills the screen at 31%, actual size it's g