:

RSSDatabase Config

ORA-16014 No Available Destinations

ORA-16014 No Available Destinations

I arrived at work today to find a few emails in my inbox saying that one of the development environments appeared to be down. My first check was to try logging on as one of the application users, which failed with the error: ORA-00257: archiver error. Connect internal only, until freed I’ve written about this […]

Continue Reading

ORA-01019: unable to allocate memory in the user side

ORA-01019: unable to allocate memory in the user side

The Problem One of the in-house developed tools which connects to the database to allow a user to perform configuration updates was throwing an error: ORA-01019: unable to allocate memory in the user side Most of the docs that I could find online told me the same thing, namely: Cause: The user side memory allocator […]

Continue Reading

ORA-12154: TNS:could not resolve the connect identifier specified

I came across a little Oracle issue this morning which can be quite confusing at times. It’s to do with compilation of a package which has references across a database link. Here is what we were seeing from our database warehouse: USER1@DW> EXEC CONFIG_PKG.UPDATESOURCEROW ERROR at line 1: ORA-12154: TNS:could not resolve the connect identifier […]

Continue Reading

NID-00107: File I/O error on datafile

I was using the NID utility the other day to change the name of a database that I had just restored. The restore had been carried out using data pump and the transportable tablespaces feature. When using NID I got the following error: NID-00107: File I/O error on datafile “R:\CONTROL01.CTL” during block 1 offset operation  (27047/kunidb1c) This […]

Continue Reading

Rename Oracle Database – NID Command Explained

You can use the NID command to change an Oracle database’s name and/or ID. This is useful, for example, when making a clone of a production database and wanting to use it in development. You may find that when using it you come across the NID-00107: File I/O error on datafile or perhaps the NID-00137: […]

Continue Reading

SP2-0734: unknown command beginning “purge dba_” – rest of line ignored

The SP2-0734 error certainly made me scratch my head for a while. First off, I thought I had got the command wrong because I don’t execute it that much because we have all of our DEV environments configured with the recyclebin off. So I went to the Oracle documentation and realised that I had entered it correctly. Then […]

Continue Reading

ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST

The Problem You are receiving the error message: ORA-00257: archiver error. Connect internal only, until freed. You log into the database and try to archive the redo log files and get another error: sys@TEST> archive log all; ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST The Solution alter system set log_archive_dest_state_1=’ENABLE’ scope=both; sys@TEST> archive log […]

Continue Reading

The Job Coordinator and Job_queue_processes

If you are running jobs within the database by using the DBMS_JOB package to submit your jobs to the job queue, you will no doubt know that the job_queue_processes parameter is responsible for determining how many jobs can run at the same time. Each job which runs within the database will be viewable from the v$session dynamic view. […]

Continue Reading

ORA-32004 Obsolete and/or Deprecated Parameter(s) Specified

After modifying one or more database parameters you stop and start the database and get the error message: ORA-32004: Obsolete and/or Deprecated Parameter(s) Specified This could be when changing from a lower version database to a higher one, and some of the parameters that you had set are now deprecated. You can query the V$OBSOLETE_PARAMETER view […]

Continue Reading

ORA-01153 an Incompatible Media Recovery is Active

The Problem When running the command ALTER DATABASE OPEN RESETLOGS from an RMAN prompt, I got the error:                  ORA-01153: an incompatible media recovery is active I then tried from SQL Plus but got the same message. The Solution The solution was to close the RMAN session that I had open and then run the […]

Continue Reading