Author Archives: Bobby

I keep forgetting that I need to bounce both the listener and the database after changing the oracle user’s group membership, so I am writing a quick note to myself here. This is the second time I have been tripped … Continue reading →

Last night, the plan change monitor script we have setup on one of our production databases alerted us about query with a SQL Analyze hint. It looked weird. The query has sql_id 48tfz5d37xk28 and starts like this: The weird thing … Continue reading →

I forget that Oracle’s AWR only records the top 30 SQL statements in each snapshot by default. I am not sure how long this link will last but here is a 19c manual page describing the default: 19c manual – … Continue reading →

Quick note. During my 11.2.0.4 to 19c upgrade that I have been writing about we found a difference in behavior of DBMS_UTILITY.FORMAT_CALL_STACK. I tested it on several versions, and it switched in 12.2. Now it puts the procedure name within … Continue reading →

I wanted to install the latest Python on Linux in a low powered user’s home directory and not have the install interfere with the Python that comes with Linux. I wanted my own local copy of Python that I could … Continue reading →

Quick note. The next AZORA meetup will be next Thursday, 2/13/2020. Be sure to RSVP on Viscosity’s web site: https://tips.viscosityna.com/modernize2020-phoenix/ (DOES NOT EXIST) I don’t know about you but we are busy moving to or implementing on 19c so these … Continue reading →

This week I investigated an issue with a query that was suddenly a lot slower in one test environment than another. It runs about 2 seconds in the good case as well as in production. But it was now running … Continue reading →

I have not yet had time to build a test case and prove this out, but I wanted to document one last bug that we found so far in our 11.2.0.4 to 19c upgrade. We tried copying a bunch of … Continue reading →

Last 19c upgrade issue. Working on our new 19c database, several things died off with errors like this: Our tablespaces had small uniform extents and our 19c database had defaulted the parameter db_securefile to PREFERRED. We bumped our uniform extent … Continue reading →

Quick post before I leave on vacation. We used Datapump to import a schema from an 11.2 HP-UX database to a 19c Linux database and got errors on a few tables like these: Workaround was to create the table first … Continue reading →