Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 893006

Summary: JDBC Binary CS - using slash in cache name (problem with Oracle11gR2)
Product: [JBoss] JBoss Data Grid 6 Reporter: Tomas Sykora <tsykora>
Component: unspecifiedAssignee: Tristan Tarrant <ttarrant>
Status: CLOSED DUPLICATE QA Contact: Martin Gencur <mgencur>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: jdg-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-09 08:59:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Trace log - slash in cache name (using oracle11gR2 DB) none

Description Tomas Sykora 2013-01-08 12:48:41 UTC 
Created attachment 674781 [details]
Trace log - slash in cache name (using oracle11gR2 DB)

This can be related (duplication of?) to:
https://bugzilla.redhat.com/show_bug.cgi?id=841896 and https://issues.jboss.org/browse/ISPN-2155, but for other types of DBs it causes no problems. (Only for Oracle11gR2)

When I change cache name from default/xx to default_xx, everything seems to be ok.

The problem is: 
13:26:58,701 TRACE [org.infinispan.loaders.jdbc.TableManipulation] (MSC service thread 1-2) SQLException occurs while checking the table JDG_BINARY_default/xx: java.sql.SQLDataException: ORA-01424: missing or illegal character following the escape character (please, see full trace log for details)

I only guess: 
How about add another replace for cache name: cacheName.replace("/", "_") in TableManipulation.java?
https://github.com/infinispan/infinispan/pull/1223/files

Thank you for your investigation!
Comment 1 Martin Gencur 2013-01-09 08:59:18 UTC 

*** This bug has been marked as a duplicate of bug 888764 ***