In the previous part (you can find it here) I discussed the character sets Oracle supports and the length limits. In this part I’ll show how it is actually stored and discuss some more topics that are relevant to using different languages with Oracle.
Remember my post about Oracle 12.2 release date? I’ve heard rumors that Oracle changed the date to March 1st, and it was right!
Oracle 12.2 is available for download for Linux x86-64, and Solaris (both SPARC and x86-64). I don’t know the release dates for other platforms. This is the download page: http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
I’m downloading it as I write, and hopefully will have time to play with it a little bit soon. I wrote so much about new features that I have to try some of them at least. Stay tuned!
A few days ago I was browsing the documentation and suddenly realized that I haven’t gone over the 12.2 books. One of the things I like to do is reading the “New Features” guide, so I did. After writing about the major features, here are some smaller ones, but still important enough to know.
Lately I had a weird problem with one of my customers regarding timezone in the database. They copied a database server from US (eastern time zone) to Europe (GMT) and changed all the OS setting to the new timezone. The application uses “sysdate” to insert data to the database, and they saw that the sysdate returns the wrong time. When I checked that, it seemed that when we used sqlplus locally on the server everything worked perfectly, sysdate, current_timestamp and systimestamp all returned the correct times with GMT. In SQL developer, however, even when running from the same timezone (GMT) the result of sysdate and systimestamp were still eastern time and not the GMT (current_timestamp returned the correct time).
lately I wrote a couple of posts about bash scripting for DBAs (part 1 and part 2). I promised to post an example script as well, and I will. But before that I thought it’s important to give several examples of how scripts can be destructive. The examples in this post are real, and involved me (either on the side that caused the problem, or the side who fixed it).
Lately I wrote a post about 12.2 new features. In the post I didn’t list sharding (probably one of the biggest features in this version), as I wanted to dedicate an entire post for it. In this post I will cover this option , but please note, as 12.2 is only released for the cloud and no one can install it and play with it, all the information is based on presentations I’ve seen at OOW and a chat I had with one of the developers in the demo ground. There might be some inaccuracies or mistakes in the post.