cancel
Showing results for 
Search instead for 
Did you mean: 

Problem by switching to SAPJVM - Native JDBC drive in use

Former Member
0 Kudos

Hi all,

we are trying to Switch our PI System to the SAPJVM (Netweaver 7.0 - Kernel 7.20 64bit Unicode).

We started the SAPJVMSWITCHINGTOOL on the ISeries and started the GUI on the windows host. After detecting the Profiles, providing the SAPJVM.SAR and providing the JCE Policy we got a error message which said that we are using the Native JDBC driver.

This is the error message:

An error occurred while proccessing option Switch JDK to SAP JVM > Switch JDK (Last error reported by the step: Native JDBC detected for system <SID>. The native JDBC is not supported in combination with SAP JVM. For more information about JDBC an how to proceed see SAP Note 826449.

But this is wrong.

Nevertheless we make a switch to the Toolboxdriver again with CONFIGJVM, but nothing was changed. SAP told us to patch the ILE (because of note 1739772) to the newest version. After patching ILE to version 324 (the newest) the problem which is described in note 1739772 was solved. But the switch to SAPJVM is still throwing the error message above.

The error message on the windows host is giving also the sap note 826449.

I've proofed also a lot of property files e.g. "bootstrap.properties" but everywhere the right path is given. (rdbms.driverLocation=/usr/sap/<SID>/SYS/jdbc/tbx/jt400.jar)

Does anyone know how the sapinst is detecting the jdbc driver? Where does the sapinst search for the jdbc driver? Maybe the CONFIGJVM doesn't switch the whole enviroment?

I would be happy about any suggestion oder answer.

Thank you...

Tobias

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi all,

using the new version (Version 10) of SAPJVMSWITCHTOOL solved the problem.

I assume that adding sapinst group to user profile of SIDADM had also solved the problem.

Regards

Tobias

Former Member
0 Kudos

Thanks, this is very useful. We have some ECC 6.0 EHP6 systems on development that use the old JT400.jar we got from IBM. I think I would rather leave them in peace if possible and use the SAPJVM6 version when we install PI 7.31.

Is there any issue with leaving the older systems still using JT400.jar?

Former Member
0 Kudos

Hi all,

we solved the problem above.

In the logfile sapinst_dev.log we detected that the sapinst assumes a Native JDBC drive because the directory "/sapmnt/<sid>/jdbc/ntv" is still there.

So we changed the name of "ntv" to "ntv_old". Now you can see in the same logfile that now toolbox driver is detected.

But now we have the following error message:

An error occurred while processing option Switch JDK to SAP JVM > Switch JDK( Last error reported by the step: Execution of the command "/tmp/sapinst_instdir/NW70/SWITCH_JDK/sapjvm_4/sapjvm_4/bin/java -classpath /usr/sap/<SID>/SYS/global/sltools/sharedlib/launcher.jar com.sap.engine.offline.OfflineToolStart com.sap.inst.jswitch.JRead /usr/sap/<SID>/SYS/global/security/lib/tools/iaik_jce.jar:/usr/sap/<SID>/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/sap/<SID>/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/<SID>/SYS/global/security/lib/tools/iaik_ssl.jar:/usr/sap/<SID>/SYS/global/security/lib/tools/w3c_http.jar:/usr/sap/<SID>/SYS/global/sltools/sharedlib:/usr/sap/<SID>/SYS/jdbc/tbx/jt400.jar:/tmp/jswitch.jar -arch sap_64bit -instanceID ID3178666 -systemName <SID> -ssPropFile /usr/sap/<SID>/SYS/global/security/data/SecStore.properties -ssKeyFile /usr/sap/<SID>/SYS/global/security/data/SecStore.key -trace all -javaPath /QOpenSys/QIBM/ProdData/JavaVM/jdk14/64bit -outputFile /tmp/ID3178666_javaParameters.properties" finished with status TST_ERROR.). You can now:

The outputfile ID3178666_javaParameters.properties was not created.

Any ideas?

Former Member
0 Kudos

Hi Tobias,

I am almost sure you are running into a permission problem that has been fixed in the latest version of the JVM Switch tool. You should be able to fix this issue either by using this new version (patch level 10) or by adding sapinst group as a supplemental group for user sidadm.

Regards,

Luis

Former Member
0 Kudos

Hello Luis,

yes we assume this too.

And SAP Support suggests also to adding the sapinst group to SIDADM.

We have to try this on the next downtime.

But in our test system we made the switch successfull with an old sapjvmswitchingtool and a SIDADM user without SAPINST group.

I don't understand why the switch worked in the testsystem.

Thanks for your reply and help.

Regards

Tobias