Recently, I worked on an Oracle database migration for a customer and I faced a strange behavior when accessing a file stored on the file system of the Oracle database. The database has been migrated on a new server, and consolidated with existing databases. Several jobs are running into the database and need to access the file system to read or write some files. A particular file is received daily from a remote job over FTP. This file is owned by the "dc_ftp" user in /home/dc_ftp.
First, this is the directory where the file is located:
Every Oracle database has a data dictionary, which is owned by the SYS user and stored in the SYSTEM tablespace. This consists of read-only tables, which record information about the database e.g. table definitions, details of integrity constraints, usernames and the roles and privileges granted to them etc. You can read about this in detail in Oracle's own documentation.
One of the people attending my seminar in Munich last week has emailed me some details about a nasty little surprise you may get if you’re thinking about TSPITR (tablespace point in time recovery), and happen to have a few materialized views in your database.
I went to Hotsos Symposium 2014, in Irving, Texas, last week. If you’re an Oracle technologist and you’re not going to the Symposium each year, you’re really missing out. Not only is it a chance to see some excellent presentations, it’s also a chance to interact with the presenters on an ongoing basis for a few days, as the conference is small enough to allow for that.
It’s also a chance to enjoy camaraderie from Oracle professionals from around the world. Yep, this conference is so good that people fly in from overseas to attend.
This Saturday was International Women's Day! To keep the celebration going, here are a few of the outstanding WordPress.com blogs by, for, and about women.
In the last article (I hope) of this series I want to look at what happens when I change the parallel distribution method on the query that I’ve been using in my previous demonstrations.
In case you missed it, a quick recap of the past week on WordPress.com.
Due to the fact that multiple organizations are shifting to different platforms, database administration support companies are being contacted by private enterprises and public agencies to conduct extensive reviews of their data hosting systems. Whether on-premise or in the cloud, amassing large amounts of data through PCs, interfaces, mobile devices and other machines has become the norm.
I am slightly disappointed to report that the new extended data types cannot be used in the clustered tables. CLOB columns have never been allowed, and are still not allowed in 12c, but I expected the new data types to pass seamlessly. That is not the case:
SQL> create cluster testclu(intkey number(30,0));
SQL> create index testclu_ind on cluster testclu;
Now, let’s create a normal table with the extended character type: