Ebs shutdown error

[satish]

Hi erman,


While stoping or starting Ebs,getting below errors.

applprod@erpprodapp01 ~]$ adstpall.sh -mode=allnodes

You are running adstpall.sh version 120.22.12020000.7


Enter the APPS username: apps

Enter the APPS password:
Enter the WebLogic Server password:
java.sql.SQLException: ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00229: input source is empty
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at line 1

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:202)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:942)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1283)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1441)
at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:2251)
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:2192)
at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:347)
at oracle.apps.ad.util.ACUtil.getAllContextFiles(ACUtil.java:381)
at oracle.apps.ad.autoconfig.ServiceControl.<init>(ServiceControl.java:433)
at oracle.apps.ad.autoconfig.ServiceControl.main(ServiceControl.java:2152)
All enabled services on this node are stopped.

adstpall.sh:Exiting with status 0

adstpall.sh: check the logfile /u02/PRODINST/fs2/inst/apps/PRODDB_erpprodapp01/logs/appl/admin/log/adstpall.log for more information ...

Sent from my iPhone

[ErmanArslansOracleBlog]

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..