on 07-10-2014 12:27 PM
Hi NWDI experts,
I just installed a completely new NWDI 7.4 SR1 (SP05) on Windows 2012 R2 and Oracle 11.2.0.4.
When I try to access DTR I receive error "500 Internal Server Error". In defaultTrace the system reports problems with initialization of DTR. Multiple entries exists in the various log-files and traces, which concerns the problem. I've therefore attached logs and traces to this discussion. After downloading the file rename it to .zip instead of .txt.
The error seems to be caused by a NullPointerException in oracle.jdbc.driver.OracleStatement.m_batchItems.
I've searched extensively on SCN, Notes and Google, but have not been able to find any answers to what the problem is. Also I've looked at note 774339 - Internal Server Error in DTR, but have not been able to find a useful solution.
Has anyone experienced the same error and how where you able to solve it?
Best regards,
Jacob
have you done all the configuration?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ervin,
Yes. the trace file contains that type of exception. The exact line is this:
Caused by: java.lang.NullPointerException: while trying to invoke the method java.util.Vector.removeAllElements() of a null object loaded from field oracle.jdbc.driver.OracleStatement.m_batchItems of an object loaded from local variable 'this'
Best regards,
Jacob
Good morning Ervin,
Thank you very much for your answer. I had a suspicion that the error was deeper in the belly of the system and not caused by DTR.
In the note you mention, it says that a new version of Oracle Client software will be delivered, which should fix the error, but do you have an idea on when it will be available for SAP customers to download?
Just as a temporary workaround I've replaced the ojdbc6.jar for 11.2.0.4 with the one from 11.2.0.3 and I'm now able to access and browse the DTR.
Best regards,
Jacob
Hi Jacob,
sorry, I am not aware when a final fix is available as this is rather the scope of the db support team, I only received this info from the db support that this is due to the oracle driver. Perhaps you can get some more information on this from a db related forum.
Anyway, I am glad that the temporary workaround helped you.
Best Regards,
Ervin
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.