|
Oracle FAQ
|
Your Portal to the Oracle Knowledge Grid
|
Home ->
Community ->
Mailing Lists ->
Oracle-L ->
Re: Oracle Apps conccurrency Manager
Re: Oracle Apps conccurrency Manager
- Original Message ----
From: Ken Naim <kennaim@gmail.com>
Sent: Friday, May 4, 2007 12:11:16 AM
Dear RAC/ Oracle App experts,
Let me preface this question with I have very limited exposure to both RAC and Oracle apps but I have been asked to help with this issue. Unfortunately I donąt even know the right questions to ask so the details will likely be sparse. If you have experience in this area, Iąd be most appreciative if you could point me in the direction of where/what to look for.
The issue we are experiencing is moving the Oracle Apps (11.5.10.2) concurrency manager from one of four 10.2.0.2 RAC nodes to its own tier. When we do this we are having an issue with utl_file not seeing the files even though the utl_file is defined in both the database and the Apps. We are running on 32 bit Redhat linux. I am not yet sure which kernel.
Ken
UTL_FILE writes to the filesystem from the point of view of the Oracle instance (mapping from an Oracle Directory definition to a specific path on the filesystem). Of course it can only write to a path that the database instance can actually see.
Apps concurrent manager is a client C program (well, it was when I used it - 12-15 years ago - so I'm guessing it still is). Up until now you have run it (if I understand you correctly) on the same server as the Oracle instances. Now, you've moved it to a middle tier. So the C program sees your mid-tier file system through normal library calls (fopen, fprintf etc), while any PL/SQL bits see the database tier file system through calls to utl_file.fopen etc.
If the concurrent programs (or the concurrent manager itself) are trying to write files with UTL_FILE and read with the C libraries, or vice versa, then you have an impasse. You may think you are reading and writing to the same path ($APPL_TOP/somepath, say) but it's the same path on different filesystems.With RAC instances, you also need to make sure that this path is shared across all instances, otherwise program 1 may write to a path private to node A's file system, while program 2 writes to node B's.
Possible solutions:
put your CM and concurrent programs back onto the database tier (after all, they are database programs so there's a pretty good chance that most of their work is happening in the DB rather than in the client. Mid-tiers can be surprisingly idle!)
and/or mount an NFS filesystem for the files you use to communicate between programs, and make sure that all the database instances and all the mid tiers can see that shared directory
As I said, my exposure to CM is very limited and dates back to the early 90s - I may have missed the odd design change since then, and I'm sure its all a lot more complicated than it used to be. I imagine you are not the first person to have tried this, so you could try asking on more Apps related forums, or using Google. I quickly found this (Oracle) blog entry referring to a couple of Metalink notes (eg "Configuring Oracle Applications Release 12 with 10g R2 RAC"): http://blogs.oracle.com/skrajend/2007/02/15.
HTH
Regards Nigel
--
http://www.freelists.org/webpage/oracle-l
Received on Fri May 04 2007 - 02:37:33 CDT
Original text of this message
