
Archive for the ‘TEChNoLoGY’ Category
12c AdminServer 12.1.3 not starting and ending with error Critical WebLogicServer BEA-000386 Server subsystem failed. Reason: A MultiException has 6 exceptions
December 18th, 2018, posted in OracleSymptom:
A MultiException has 6 exceptions. They are:
1. java.lang.AssertionError: Cannot export non clusterable object with jndiName:weblogic.jndi.internal.RootNamingNode@69f01d6c:
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.jndi.internal.RemoteNamingService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.management.mbeanservers.runtime.internal.RuntimeServerService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.mbeanservers.runtime.internal.RuntimeServerService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.cacheprovider.CacheProviderServerService errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.cacheprovider.CacheProviderServerService
Cause:
This issue is caused by entry of the following JAVA_OPTIONS parameter ‘-Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory’ when deploying into WebLolgic 12c. In WebLogic 12c, the built-in WebLogic Server XML Input factory implementation class is com.ctc.wstx.stax.WstxInputFactory, and the XML Factory Input should be set to this value. Due to a documentation bug, the manual deployment guide for P6 is still referencing the 11g implementation class, causing the reported issue to occur.
Fix:
Edit setDomainEnv.sh
Locate the line:
JAVA_OPTIONS at the end (added by the installer)
Change it to:
export JAVA_OPTIONS=”-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Doracle.jdbc.V8Compatible=true ${JAVA_OPTIONS}”
Reference Doc:
MOS Document ID: WebLogic 12c Managed Server Fails To Start When Passing The “-Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory” Java Argument (Doc ID 2003152.1)
How To Cancel or Restart the Cost Manager
December 18th, 2018, posted in Concurrent Request, Oracle EBS Application, Oracle QueriesBehavior of Cost Manager:
Cost manager is not a typical concurrent manager that it finishes after is costing some transactions.
Cost manager it is rescheduling itself based on the the process interval specified in interface managers form.
Cost Manager should stay in this status : “Pending Scheduled” and will restart itself based on the process interval specified in interface managers form. It calculates the re-launch time as start time + process interval.
2 – Run the cmclean.sql script available from MOS Note 134007.1
3 – Restart the Cost Manager
Inventory> Setup : Transactions> Interface Managers
Select ‘Cost Manager’ – choose Tools > Launch Manager
Also review << Note 304313.1>>
- Restart the concurrent processes.
- Run the below select and update scripts to update the uncosted and/or erred records in the tables indicated.
- Relaunch the Cost Manager. Select and Update scripts for paragraph 5. above:
SQL> select count(*) from MTL_MATERIAL_TRANSACTIONS where COSTED_FLAG = ‘E’;
SQL> select count(*) from MTL_MATERIAL_TRANSACTIONS where COSTED_FLAG = ‘N’;
SQL > Update MTL_MATERIAL_TRANSACTIONS set COSTED_FLAG = ‘N’, TRANSACTION_GROUP_ID = NULL where COSTED_FLAG = ‘E’ or COSTED_FLAG = ‘N’;
If there are unprocessed records in MTL_MATERIAL_TRANSACTIONS_TEMP, then, also run the following:
- To see if there are records in mtl_material_transactions_temp, run:
SQL> select * from mtl_material_transactions_temp;
- If rows are returned from the SQL in a. above, then run:
SQL> Update MTL_MATERIAL_TRANSACTIONS_TEMP Set PROCESS_FLAG = ‘Y’, LOCK_FLAG = ‘N’, TRANSACTION_MODE = 3, ERROR_CODE = NULL Where TRANSACTION_HEADER_ID = ;
(OR)
Resubmit all transactions using this procedure:
- Shut down the cost manager
- Make a backup of the table mtl_material_transactions
- Perform the following update
SQL > update mtl_material_transactions
set costed_flag = ‘N’,
transaction_group_id = NULL,
transaction_set_id = NULL
where costed_flag = ‘E’ or costed_flag = ‘N’ ;
Commit ;
Update MTL_MATERIAL_TRANSACTIONS set COSTED_FLAG = ‘N’, TRANSACTION_GROUP_ID = NULL where COSTED_FLAG = ‘E’ or COSTED_FLAG = ‘N’;
Uncosted/failed transactions can be resubmitted through the application itself.
Costs -> View Transactions -> Material Transactions.
From the menu, Tools Select All: Tools Submit All
Else, use the following script to submit the records in MMT table:
update mtl_material_transactions MMT set MMT.costed_flag = 'N', MMT.error_code = NULL, MMT.error_explanation = NULL, MMT.transaction_group_id = NULL, MMT.transaction_set_id = NULL where MMT.organization_id = &organization_id and MMT.costed_flag in ('N','E') and NOT EXISTS ( SELECT 1 FROM MTL_TRANSACTION_ACCOUNTS MTA WHERE MMT.TRANSACTION_ID = MTA.TRANSACTION_ID);
commit;
- Re-start the cost manager.
Restart the cost manager via Inventory > Setup > Transactions >
Interface Managers > Tools > Launch Manager. Set up a periodic scheduling interval of every five
minutes.
Note — Cost Manager should not be scheduled through request form to run Periodically.
Cost Manger should be scheduled through Interface managers only.
Re-Enter Toad License Info
December 9th, 2018, posted in Oracle
Enter your license information once again. Toad will then save a file named “QSAuth11.key” into your default application data folder, which should be:
C:\Documents and Settings\Application Data\Quest Software\Toad for Oracle\10.0 (for WinXP and earlier) C:\Users\AppData\Roaming\QuestSoftware\Toad for Oracle\10.0 (for Vista and higher)

