First, make sure you are modifying the correct init.ora when trying to bring up the database with at least one of your controlfiles.
If all of your controlfiles are realy corupted then I'm affraid you can't use ALTER DATABASE BACKUP CONTROLFILE TO TRACE, because it must be performed with database in MOUNT or OPEN state, which you can't do without a valid controlfile (catch22....).
So I belive your options are:
1. If you have backup of your controlfile in ASCII file (the output of the above command, should be part of any proper backup plan) you just have to run the CREATE CONTROLFILE command from this file, copy the created controlfile to previous locations and start the database.
2. If you are roning in archivelog mode you can restor controlfiles and datafile sfrom your backup, recover the database and open it with the RESETLOGS option.
3. The last option is to create new controlfile manualy. But you must know the names and location of each and any datafile and redolog file of your database. Run the CREATE CONTROLFILE command in NOMOUNT state, copy the generated controlfile to original locations with original names (or change the init_file parameter CONTROL_FILES) and open the database. To get you started more easily with the CREATE CONTROLFILE command I'm attaching the sample - you have to replace all the file names from your database, probably the characterset, archivelog mode, size of redolog files and any other stuff that is different in your database.
CREATE CONTROLFILE REUSE DATABASE "O815" NORESETLOGS NOARCHIVELOG
GROUP 1 'C:\ORACLE\ORADATA\O815\REDO01.LOG' SIZE 1M,
GROUP 2 'C:\ORACLE\ORADATA\O815\REDO02.LOG' SIZE 1M
CHARACTER SET EE8MSWIN1250;
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?