ORA-07445 [kkecdn()+9776] After apply Pacth Set 10.2.0.5

Recently, to solve a production problem identified as a bug (solventable with Path Set 10.2.0.4) has been necessary to update BD Oracle version 10.2.0.1 to 10.2.0.5 (that matter we are going to last Patch Set).

After installing the Path Set 10.2.0.5 for Linux 64 bits, which went smoothly and update catalogs databases, everything seemed to go perfectly.

At the moment the COMPATIBLE parameter remained with the original version 10.2.0.1.

Problems occurred about a day later when a report stopped working, the alert displays:

Continue reading

Oracle search string in database

In some cases, fortunately not too many, I had to search for a string (usually something related to configuration) in a schema of the database.

Gets complicated when there is a huge amount of tables and also no way to contact the developer, is as hell.

Well good for these cases I want to share a PL / SQL script homegrown (as almost everyone who put in the blog), which facilitates the issue fairly:

Continue reading

Oracle listener automatic registration of services

Starting with Oracle Database version 8i, need not be recorded BD services in the listener.ora file, the DB can automatically register.

This functionality works perfectly if we have the listener on port 1521 (default), if we make a change there’s no port to connect to the database. This is because the value of the parameter which defaults LOCAL_LISTENER:

Continue reading

Oracle ora-00600 librarycachenotemptyonclose, the famed in Oracle 10g

This error is caused by a bug recognized by Oracle that can be easily found in Metalink [ID 4483084.8], the error indicates that you have tried to stop the database without the Library Cache was empty.

The proposed solution is officially migrate to 11.1.0.6 and further indicates that it does not produce any kind of corruption in the datafiles, suggesting that we can get used to seeing on the alert without worrying.

What they do not say is that this error may generate a typical shutdown immediate, may fail and be the BD in nomount state, this has happened to me in HP-UX systems. If it happens during a cold weekend back, the database will not start because it is, but of course in nomunt state.

Continue reading