Best Of
Re: too many parse errors
Some handy statements you may already know/tried
select SQL_ID,SQL_FULLTEXT from v$sql where sql_id='&&sql_id'; sELECT s.sid, s.sql_id, t.sql_text FROM v$session s JOIN v$sql t ON s.sql_id = t.sql_id WHERE s.sql_id = '&&sql_id'; SELECT sql_id, sql_text FROM v$sqltext WHERE sql_id = '&&sql_id'; SELECT sql_id, sql_text FROM dba_hist_sqltext WHERE sql_id = '&&sql_id'; select kglnaobj from x$kglob where kglobt03='&&sql_id';
Re: Issue viewing credit case folders
Hey John, just wanted to get back with you on our findings. We did run the diagnostics and discovered and issue with time zones. Looks like my profile for Client Timezone was set but no one else's. Once we changed them everything works fine. thanks again you have been a great help on our issues
Re: any approximate date for Weblogic 15.1.1?
Following up on this post. Has there been any update since we are now entering Sept 2025 .
We use the App Server throughout OCI and would like an update on this release date please.
Re: too many parse errors
That sounds a little extreme - setting COMPATIBLE is not a reversible change. Since it's a rather dramatic suggestion could you supply the argument for doing it? viz: what you think is going wrong, why this will fix it, and any reference you have that supports the approach.
The SQL_ID reported by the error is for a call to dbms_lock.sleep(60). Is it possible that dbms_lock in that RU of Oracle has removed the sleep() function from dbms_lock (it doesn't seem likely), or not given the execute privilege on dbms_lock to dbsnmp and the other affected user(s)?
The sleep() function was copied to the dbms_session package a few versions back, so it's possible that internal code that calls it has been adjusted to use the less powerful package.
Regards
Jonathan Lewis
Re: How to generate move order for material in work order
This set up is must for the process to work please.
Re: Three hours of red alert in OCOM. Have you ever seen something like this?
Hello,
These red and yellow bands are considered to be a software bug. I got following instructions on how to get rid of them from Support:
We analyzed the logs and could see the frames are getting dropped.
Jul 29 02:08:16 OCOM vsi[1693323]: ERROR (pktsub.c:825 handle_seqno) connection 'tcp://127.0.0.1:18010' lost 7244 frames
Jul 30 00:40:04 OCOM vsi[1740960]: ERROR (pktsub.c:825 handle_seqno) connection 'tcp://127.0.0.1:18010' lost 1 frames
Jul 30 00:40:04 OCOM vsi[1740960]: ERROR (pktsub.c:825 handle_seqno) connection 'tcp://127.0.0.1:18010' lost 7664 frames
Jul 30 00:44:51 OCOM vsi[1740960]: ERROR (pktsub.c:825 handle_seqno) connection 'tcp://127.0.0.1:18010' lost 76 frames
Jul 30 00:44:51 OCOM vsi[1740960]: ERROR (pktsub.c:825 handle_seqno) connection 'tcp://127.0.0.1:18010' lost 6183 frames
To address this we recommend you to please create new files namely apid.local.conf and vsi.local.conf with the below recommended values:
=> apid.local.conf
[publisher/sip]
hwm=100000
=> vsi.local.conf
[broker]
connsock_hwm=100000
these files should be under /opt/oracle/ocsm/etc/iptego/
Restart all processes in order to apply the change as below. Note that this will create a short service interruption and you will see a sudden drop in graphs. Perform this action within a maintenance window.
# systemctl restart pld-apid.service
# systemctl restart pld-vsi.service
Regards,
Daureen
Re: Hostname must be <= 30 characters in length
Hi.. I have rarely seen systems with more than 30 character names. In future it might be a limitation. Please post an idea in community and if other customers also feel it's required in future releases... They will vote for it and it will be considered for enhancement.
Regards,
Balaji P.
