Skip to Main Content
Forums

Java Programming

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

JDBC Connection strings to connect to Oracle DB

OTG-467455Nov 8 2017 — edited Nov 9 2017

What are the various acceptable JDBC connection strings that can be used to connect to an Oracle database?

Which connection string is commonly used?

Please explain what the purpose of each different connection string is.

The reason for my asking this is I have seen some connection string incarnations I did not think could work.
This post has been answered by mNem on Nov 8 2017
Jump to Answer

Comments

781486
TRIM support was added to build snv_146 and it's available. However, there is no indication that ZFS has been updated to make use of it yet.

We've been using SSDs with ZFS on hundreds of systems and it works fine in terms of durability. I believe you shouldn't worry about it for your home system.
1 person found this helpful
ajazam
Hello,

Thanks for your reply. I think I'll skip on the SSD's until TRIM support is available for the ZIL and L2ARC. I'll be spending my own money so would like to get the most value for money.
Carsten T.-Oracle
Hello,

do you know whether 'SSD trim' is supported and used on the final Solaris 11/ZFS build?

Thanks

/ct
M10Torrey
Hi Community,
I opened an SR to ask Oracle about this. The answer: CR 6913905 covers this request and is integrated into Solaris 11 SRU 5, planned for the end of March 2012.

Hope that helps

-T
cradlinski
Does ZFS in Solaris 11.1 support TRIM?
Cindys-Oracle
The equivalent of TRIM is supported as SCSI unmap in Solaris 11.1 and ZFS will recognize that blocks are reclaimed.
We have some challenges due to 15804599, which means SSD performance is severely impacted by SCSI unmap.
The SCSI unmap is currently disabled due to this problem starting in S11.1 SRU 3.4.

Thanks, Cindy
cradlinski
Cindy,

Thanks for the quick reply. If I'm understanding correctly, the SCSI unmap command was implemented in last November's Solaris 11.1 release but has since been disabled due to performance problems. I'm running the original November release with no updates so can I assume that SCSI unmap is enabled on my system? If so, do I run any risk of data corruption by staying with my current version? I'm currently running Solaris 11.1 from a SATA SSD.
Cindys-Oracle
Hi--

No risk of corruption (from having this feature enabled).

Your SSD performance might be noticeably slower if the device supports SCSI unmap. If not, then no worries.

You can disable it manually by adding this syntax to the /etc/system file:

set zfs:zfs_unmap_ignore_size=0

Thanks, Cindy
cradlinski
Thanks again for the reply. One more question: I'm using a SATA drive, not SCSI. Does that mean I have no TRIM support under Solaris 11.1?
Cindys-Oracle
I guess it depends on the transport type, but SCSI commands can be transported over different bus types so yes, your SATA SSD might have this support.

Thanks, Cindy
cradlinski
Thank you, Cindy. You've been a big help.
unknown-791521
+... thread from December 2010 is now locked before it gets resurrected and hijacked in another couple of years.+
1 - 12

Post Details

Added on Nov 8 2017
#java-puzzle-ball
1 comment
2,801 views