I’ve been lucky enough to present at various conferences, seminars and user group events over the years in some 20 odd countries. But somewhere I’ve never quite managed to present at before is the place of my birth, the UK. Well this year, I’ve decided end my drought and submitted a number of papers for the UKOUG Tech14 Conference and […]
Normally, when I create physical standby database, the configuration has the same directory structures and name values as production with the exception of db_unique_name.
But this time was not the case as shown below.
I have recently used perfmon (performance monitor) at a customer site. I created a Data Collector Set to monitor CPU, Memory, Disk, and Network during one day. Then, I ran the monitor and I received a "beautiful" error message…
I use fio for all my I/O testing. Why not Orion from Oracle since almost all of my I/O testing and benchmarking has been geared toward Oracle? Several reasons
Last month, more than 4,000 bloggers joined us for Writing 101: Building a Blogging Habit, where they challenged themselves to carve out time to write regularly, and to experiment with new forms and styles. The result? Thousands of posts, comments, and follows, and countless new friendships.
Recently I worked on a issue where a third-party application was failing during the installation. Below was the error returned by the Application.
Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222)
The application was failing while it was trying to create a database. The application seemed to have a default timeout setting which was about 60 seconds after which it was failing, as the command had not yet returned any results.
As a DBA, it is common to get a request to run scripts against production databases. However, there can be environments where there are multiple databases on same instance, where the script needs to be run against. I have seen a environment where there were 50+ databases which have same schema with different data, and each database serving different customers.
A common criticism of PLSQL is that the "original" array datatype, now called associative arrays are perfect for passing stuff back and forth to 3GL environments (for example .Net), but canno be used within SQL natively, for example: