ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []

I got this error while shutting down the db on 10.2.0.2.


ORA-00081: address range [0x60000000000A7DE0, 0x60000000000A7DE4) is not readable
ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options

Metalink Note 435926.1 says to ignore this error.

OAM Dashboard shows source and target machine node

I found metalink note 260887.1 to clean up non-existent nodes from FND_NODES

1. SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN; COMMIT; EXIT;

2. Run autoconfig on DB tier followed by on Apps Tier.

UTL_MAIL package gives ORA-29261: bad argument

One of the developers sent this error while using UTL_MAIL package.

ORA-29261: bad argument
ORA-06512: at "SYS.UTL_TCP", line 28
ORA-06512: at "SYS.UTL_TCP", line 257
ORA-06512: at "SYS.UTL_SMTP", line 116
ORA-06512: at "SYS.UTL_SMTP", line 139
ORA-06512: at "SYS.UTL_MAIL", line 395
ORA-06512: at "SYS.UTL_MAIL", line 602
ORA-06512: at line 3

I found metalink note 339445.1 which says this can be due to two reasons.

1. SMTP_OUT_SERVER is not set as a database parameter.
2. This error can also occur if the SUBJECT parameter in the UTL_MAIL call is omitted.

In our case it was the first "SMTP_OUT_SERVER".

Added the parameter to the initialization parameter file and bounced the database.

SYSTEM OR APPS PASSWORD DISPLAYED ON THE SCREEN WHEN RUNNING ADPATCH

If you are on AD.I.2 you may have noticed the the system and/or apps password is visible on screen. To fix this move to 11i.AD.I.delta.4 (patch number 4605654) or better still to 11i.AD.I.4 (patch number 4712852).

Unable to login to Self Service after applying patch 5478710 and 5225940

On 11.5.9 CU2 after applying the latest Autoconfig and RapidClone patches I was unable to login to the self -service. After searching metalink, I found note 342580.1. As per the note, APPS_JDBC_URL needs to be commented out.