Oracle Protocol violation SQLException
I am getting Oracle Protocol Violation SQLException when I am calling connection.commit(). I have read other post which are saying that it might be due to password is about to expire. But in my case it is not. Also jdbc driver should be fine because for some other engine I do not have such a problem. What else can be problem do you have any idea ?
at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: Protocol violation
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4C7Ocommoncall.doOCOMMIT(T4C7Ocommoncall.java:75)
at oracle.jdbc.driver.T4CConnection.doCommit(T4CConnection.java:558)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3674)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3680)
at oracle.jdbc.OracleConnectionWrapper.commit(OracleConnectionWrapper.java:140)
sql oracle sqlexception
add a comment |
I am getting Oracle Protocol Violation SQLException when I am calling connection.commit(). I have read other post which are saying that it might be due to password is about to expire. But in my case it is not. Also jdbc driver should be fine because for some other engine I do not have such a problem. What else can be problem do you have any idea ?
at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: Protocol violation
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4C7Ocommoncall.doOCOMMIT(T4C7Ocommoncall.java:75)
at oracle.jdbc.driver.T4CConnection.doCommit(T4CConnection.java:558)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3674)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3680)
at oracle.jdbc.OracleConnectionWrapper.commit(OracleConnectionWrapper.java:140)
sql oracle sqlexception
add a comment |
I am getting Oracle Protocol Violation SQLException when I am calling connection.commit(). I have read other post which are saying that it might be due to password is about to expire. But in my case it is not. Also jdbc driver should be fine because for some other engine I do not have such a problem. What else can be problem do you have any idea ?
at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: Protocol violation
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4C7Ocommoncall.doOCOMMIT(T4C7Ocommoncall.java:75)
at oracle.jdbc.driver.T4CConnection.doCommit(T4CConnection.java:558)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3674)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3680)
at oracle.jdbc.OracleConnectionWrapper.commit(OracleConnectionWrapper.java:140)
sql oracle sqlexception
I am getting Oracle Protocol Violation SQLException when I am calling connection.commit(). I have read other post which are saying that it might be due to password is about to expire. But in my case it is not. Also jdbc driver should be fine because for some other engine I do not have such a problem. What else can be problem do you have any idea ?
at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: Protocol violation
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4C7Ocommoncall.doOCOMMIT(T4C7Ocommoncall.java:75)
at oracle.jdbc.driver.T4CConnection.doCommit(T4CConnection.java:558)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3674)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:3680)
at oracle.jdbc.OracleConnectionWrapper.commit(OracleConnectionWrapper.java:140)
sql oracle sqlexception
sql oracle sqlexception
asked Nov 23 '18 at 11:01
user1474111user1474111
2521323
2521323
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Generally the issue with the ojdbc7 jar. If the length of clob is 4193 characters, the driver fails to retrieve. Use new OJDBC7 patch jar
Happy Coding ..!!!
is same issue exist in older version of jdbc?
– user1474111
Nov 23 '18 at 11:54
add a comment |
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445446%2foracle-protocol-violation-sqlexception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Generally the issue with the ojdbc7 jar. If the length of clob is 4193 characters, the driver fails to retrieve. Use new OJDBC7 patch jar
Happy Coding ..!!!
is same issue exist in older version of jdbc?
– user1474111
Nov 23 '18 at 11:54
add a comment |
Generally the issue with the ojdbc7 jar. If the length of clob is 4193 characters, the driver fails to retrieve. Use new OJDBC7 patch jar
Happy Coding ..!!!
is same issue exist in older version of jdbc?
– user1474111
Nov 23 '18 at 11:54
add a comment |
Generally the issue with the ojdbc7 jar. If the length of clob is 4193 characters, the driver fails to retrieve. Use new OJDBC7 patch jar
Happy Coding ..!!!
Generally the issue with the ojdbc7 jar. If the length of clob is 4193 characters, the driver fails to retrieve. Use new OJDBC7 patch jar
Happy Coding ..!!!
answered Nov 23 '18 at 11:12
tshrtshr
76
76
is same issue exist in older version of jdbc?
– user1474111
Nov 23 '18 at 11:54
add a comment |
is same issue exist in older version of jdbc?
– user1474111
Nov 23 '18 at 11:54
is same issue exist in older version of jdbc?
– user1474111
Nov 23 '18 at 11:54
is same issue exist in older version of jdbc?
– user1474111
Nov 23 '18 at 11:54
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445446%2foracle-protocol-violation-sqlexception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown