Re: Ebs shutdown error

Posted by ErmanArslansOracleBlog on Nov 22, 2021; 5:46am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Ebs-shutdown-error-tp10432p10433.html

Interesting to see ORA-31011 during adstpall.sh run..
Seems like it is related with the context file..

a reference for an adop case -> http://ermanarslan.blogspot.com/2014/08/ebs-122-appsadzdadop-line-543-adadmin.html

an sql trace will probably show that adstpall in turn runs a code and it then goes to the database using database's xml features to get some value from an xml , which is probably stored in fnd_oam_context_files table.
In that table we have context files.. That is, context Files are in fnd_oam_context_files tables, they are stored in the TEXT column as clobs..

Well... Context Files are stored in the database.. The table that store the context files( historically) is "FND_OAM_CONTEXT_FILES"
Context files in this table is stored in a huge clob column named TEXT..
In TEXT column the context file is stored as is, that is in xml format ..

So basically our query wants to read a CLOB and make some xml processing on it, but it finds the relevant clob empty.

You need to identify the problematic context file(stored in the database).. Problematic context file = the one having a wrong/or null value in one of its xml tags..

An example / Note ->  to gather the web port information of the E-Busines Suite system, following query can be used; SELECT extractvalue(xmltype(text),'//web_port') FROM fnd_oam_context_files where status='S';


So, if you can find the problem, as I did in the given blog post above, you can take a to-the-point action.. But if you can't, you may try  to the following ->

Get some downtime;

backup fnd_oam_context_files
truncate it.
run autoconfig on db tier
run autoconfig on apps tier

Reference for the above action plan -> R12: Adop Failed With ORA-31011: XML Parsing Failed (Doc ID 1684167.1) --> Again for adop, but that's okay..