This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 102677 - Oracle SID seems to be hardcoded in Runtime config (with DataDirect driver)
Summary: Oracle SID seems to be hardcoded in Runtime config (with DataDirect driver)
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ hong_lin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-26 23:23 UTC by rpoon
Modified: 2008-10-18 02:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
User Entered SID under Additional Properties screen (138.78 KB, image/jpeg)
2007-04-26 23:24 UTC, rpoon 		Details
Wrong SID used (149.30 KB, image/jpeg)
2007-04-26 23:24 UTC, rpoon 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rpoon 2007-04-26 23:23:19 UTC 
Build:

Hula System Build
   http://bits.nbextras.org/netbeans/6.0/nightly/200704230000/installers/
     netbeans-6.0-nightly-200704230000-full-windows.exe

===================================================================

When using DataDirect driver to connect to Oracle 10g database, in runtime 
config for Connection Pool from App Server (under: Resource -> JDBC -> 
Conncection Pool), the SID that is used is different from the value that user 
enter (under 'Addition Properties').

It seems like the value 'orcl' is always used (hardcoded?) for SID.

User won't see this problem if the Database Name (SID) is named 'orcl'.  
However, if the Oracle database SID is anything else other 'orcl', the 
connection will fail with connection error (see attached jpeg file).
Comment 1 rpoon 2007-04-26 23:24:18 UTC 
Created attachment 41770 [details]
User Entered SID under Additional Properties screen
Comment 2 rpoon 2007-04-26 23:24:50 UTC 
Created attachment 41771 [details]
Wrong SID used
Comment 3 Venkat Srinivasan 2007-04-27 02:08:35 UTC 
Please look into this.
Comment 4 Narayana Pedapudi 2007-04-27 05:24:57 UTC 
This is not a jdbc binding component bug, however I have observed this behaviour.
As a work around can you configure SID also as a property apart from specifiying
in the url. Please assign this to the appropriate team. I am not sure which team
has to look at it, looks like application server team.
Comment 5 Sergey Lunegov 2008-01-18 11:03:06 UTC 
reassinging to more appropriate component
Comment 6 Jayashri Visvanathan 2008-01-19 01:40:43 UTC 
Hong,
   Can you please help reproduce the problem and assign it to the right category ? I don't see why this is being
assigned to j2ee/persistance ?
thanks
Comment 7 Andrei Badea 2008-01-21 14:32:26 UTC 
slunegov: please do not assign to j2ee/persistence issues that are not related to the Java Persistence API support. Use
ide/golden when you don't know the right component.
Comment 8 Nitya Doraisamy 2008-01-21 19:19:03 UTC 
Are you creating the connection pool via NetBeans or via adminconsole. From the description it appears that the
connection pool was created by user in the adminconsole and error comes from the adminconsole too.
Please clarify. If so, it appears that it is a glassfish issue and IO will file this issue against the server.
Comment 9 Vince Kraemer 2008-04-26 00:03:51 UTC 
this looks like it never really "resolved". resetting the TM
Comment 10 Vince Kraemer 2008-10-18 02:45:57 UTC 
This has been incomplete for over a year. Closing.

Reopen if you can confirm the issue still exists AND provide the additional information.