In an Oracle AWS RDS instance we do not have direct access to the server and hence we could not use our regular CRON scripts. I was testing an Oracle Stored procedure to replace this functionality and needed to simulate an error in the alert log. I found the below web site
(nice site with a good explanation)
and used these commands:
alter session set events '942 incident(SIMULATED_ERROR)'; drop table tablethatdoesnotexist; alter session set events '942 trace name context off';
The alert log contained:
ORA-00700: soft internal error, arguments: [EVENT_CREATED_INCIDENT], [942], [SIMULATED_ERROR], [], [], [], [], [], [], [], [], [] ORA-00942: table or view does not exist
This was exactly what I needed for my testing.