R12 RUP4 Issue (6435000) with ce6157444.sql / ce5928260.sql

Posted on May 28, 2008. Filed under: R12 |

Last week, when i was applying RUP4 (6435000), i faced couple of issues:

1) Apps account was getting locked for no reason. After running for 2 to 3 hrs, patch would start failing with message “apps account is locked”. This was quite wierd and we didnt face this issue applying RUP4 in other environments. Simple solution is to login as sysdba and issue “alter user apps unlock account” and restarting patch from where it left.

2) Patch may fail with the following error in the worker log file.


sqlplus -s APPS/***** @/swafc/applmgr/afcuat/apps/apps_st/appl/ce/12.0.0/patch/115/sql/ce5928260.sql
ERROR at line 1:
ORA-29282: invalid file ID
ORA-06512: at “SYS.UTL_FILE”, line 774
ORA-06512: at line 106
ORA-29283: invalid file operation
ORA-06512: at “SYS.UTL_FILE”, line 475
ORA-29283: invalid file operation

This issue was seen in 2 environments (dev1 and dev2) where we applied RUP4. Both the environments were on the same server and the “utl_file_dir” on both environments had “/usr/tmp” as its first entry. What happens is, when the script runs for the first time, it creates a log file under /usr/tmp with <filename>.log and when we run the script again on the same server we get the above issue.

Solution is to (re)move the log file from /usr/tmp and rerun the script again either manually or restart via patch.

Hope this tip would be useful.


Oracle PitStop

Make a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

2 Responses to “R12 RUP4 Issue (6435000) with ce6157444.sql / ce5928260.sql”

RSS Feed for OraclePitStop – Lets share some knowledge Comments RSS Feed

Yes, this was useful to me today. I hit this
issue on my 3rd test upgrade. rm /usr/tmp/ce*.log
and use adctrl to restart the worker.

Hi, I also faced the same issue, i did
chmod -R 777 /usr/tmp & the worker started sucessfully. instead of renaming the log we can change the permission…??

Where's The Comment Form?

Liked it here?
Why not try sites on the blogroll...

%d bloggers like this: