When you, or more accurately an application program, attempts to establish a connection to an Oracle database, it must look up the connection data for the database service that you are trying to connect to. Where it looks for this connection data depends on how your client is configured; there are several ways you can configure
A client of mine suffered a power failure the other day and when the power was eventually restored they hit a problem when they tried to restart one of their databases. The opening of the database failed with the following error: ORA-600: internal error code, arguments: [kcratr_nab_less_than_odr], , , , , , , , ,
One error that shows its head a lot and always seems to confuse a lot of people is the “ORA-28001 The Password Has Expired” error. Starting with Oracle database 10g, if you do a default database installation then all passwords will default to expiring within 180 days. So what a lot of people find is
ORA-00600 [kdsgrp1] One of my clients has a database job that runs weekly in the early hours of the morning. I have a cron job configured on their server to check the database alert log for errors on a regular basis and email me with any that it finds. This morning when I checked my emails
I was recently working for a client who has just done a new install of the Oracle 12c database. While attempting to import data into their new database using datapump, they got a segmentation error as follows: oracle:/u01/app/oracle/product/12.1.0/dbhome_1/bin: impdp Import: Release 188.8.131.52.0 – Production on Fri May 15 10:17:32 2015 Copyright (c) 1982, 2014, Oracle
I got a support call late last Friday afternoon (why do most call seem to come on a Friday afternoon just before you finish for the weekend?) about bad performance on one of our applications we host for a customer.
When I logged into the server and took a look at what it was doing, the CPU was getting hammered by the Oracle SMON process.