Since 126.96.36.199 there's a new parameter, "_datafile_write_errors_crash_instance" to prevent the intance to crash when a write error on a datafile occurs. But.. should I use this or not.
I was asked to deliver a backup-script for a windows-database. However I'm not a o.s.-scripting guru at all and certainly not on Windows, I came to the following script. It looks a lot like the one I use on Linux, just translated it into a .cmd-file. The challenge was to get it in one-command file.
Database: 10.2.0.2, Apex 3.2.1. Application works fine, until there's a bit of load of users logging in. They get the following message (derived from error-logging of Apache): [Wed Mar 10 09:21:58 2010] [error] [client 127.0.0.1] [ecid: 1268209318:188.8.131.52:1543:0:26453,0] mod_plsql: /pls/apex_app/wwv_flow.accept HTTP-404 ORA-06550: line 22, column 3:PLS-00306: wrong number or types of arguments in call to 'ACCEPT' ORA-06550: line 22, column 3:PLS-00306: wrong number or types of arguments in call to 'ACCEPT' ORA-06550: line 22, column 3:PL/SQL: Statement ignored
Got errors (ora-03114 / ora-03113) while running any dbms_java script on a 10.2.0.2 database. Took a while, but then I found out it only happens when I'm connected through sql*net. Directly on the server gave no problem at all. And... it only occurs on my Test-environment, not in development, and not in production.
After "alter table DWHINCIDENT.TEST_TABLE drop unused columns checkpoint 100000" And after a while: ERROR at line 1: ORA-00600: internal error code, arguments: , [0x12CB1C820], , , , Table in usable state. New bug !
Installed 11g release 2 , and wanted it to start and stop when booting and stopping the system. Taking into consideration that most of the standard stop-scripts are causing the database to 'crash' without knowing it.