Always confused with time-outs in a web-forms environment, so I wrote it in very short terms down to be memorized. Note 549735.1 on Metalink is the best source by the way where it is explained what time-outs you can use best, in this kind of environments Three parameters of vital importance: * FORMS_TIMEOUT to be
Noticed that the following error was popping up in the emagent.trc of a 10.2.04 – Grid Control-agent on a specific node, every 5 seconds. Annoying, unnecessary: 2007-09-18 12:15:14 Thread-134875 ERROR vpxoci: Error on dequeue from SYS.ALERT_QUE: ORA-00604: error occurred at recursive SQL level 1 ORA-06502: PL/SQL: numeric or value error ORA-06512: at line 30 ORA-25228:
Most of the time I don't even think about how I connect to a database: set the environment - variables, connect /as sysdba, and voila.. Then I ran into a node in which this was not as simple as I thought. Only connections through the listener were accepted. After serious investigation in discovering some typo's,
On an application-server we have got FORMS with WEBUTIL and Headstart. It turned out that the key-enter didn’t work.
Almost not worthy to write it down, but I’m blogging, so go for it.. Grid Control agent gave some troubles, patched this with Opatch. But it didn’t help, got worse. Decided to rollback the Opatch. Gave me “OPatch failed with error code 73” , actions or inventory does not exist.
© Copyright 2012 - 2023 | Jobacle by Job | All Rights Reserved | Powered by WordPress
