As demonstrated in the first post in this series, the default size for Table Partitions is to start with an I nitial8MB Extent. The fourth post demonstrated how to resize a Partition that has already been created and populated.
Developing a solid business case for going to a conference is not always easy. Most of the time the company culture dictates the succes-rate of your attempt. The necessity for your own development is of great importance to you but is most of the time not the prevailing factor for the company. So how to convince your manager that it is of vital importance for the company that you will attend the conference ? One of the drives for writing this blog is of course the AMIS-conference on June 2-3 in 2016, but reasons for going to a conference is of all times.
href="https://www.pythian.com/apache-cassandra/">Cassandra team worked on one customer’s request to copy data of several Cassandra tables between two Cassandra clusters (not Cassandra data centers). The original approach we used to copy data is through Cassandra COPY TO/FROM commands because the size of the data to be copied is not large (several hundred mega-bytes per table).
“REDO_TRANSPORT_USER” was an Oracle Database Parameter that was introduced in Oracle release 11.1 to help transporting redo from a primary to a standby by using a user designated for log transport , The default configuration assumes the user “SYS” is performing the transport. This distinction is very important since the user “SYS” is available on every Oracle database and as such most data guard environment when created with default settings are created with “SYS” being the used for Log Transport services.
Before opting to procure Exadata machines, the first thing you need to check is the readiness of your data center to hold these machines. Exadata's dimensions are similar to other normal racks i.e a 42U rack. The complete details for X5-2 physical site requirements can be found HERE. This is very important step as, for some data…
This isn’t directly Oracle related but it did come to light within an Oracle context
We had a problem with a password file in a RAC cluster and whilst they appeared to be the same on both nodes of a cluster there were issues. I knew we needed to check the size of the files and ensure they were the same but I could not remember the (l)Unix command.
I knew it was to do with checking the bytes in a file and for some reason I was thinking it was to do with md5. Our sysadmin told me of the apropos command.
It’s time to announce the 3rd episode of Gluent New World webinar series! This time Gwen Shapira will talk about Kafka as a key data infrastructure component of a modern enterprise. And I will ask questions from a old database guy’s viewpoint :)