Hi folks,
I was installing Oracle9i Application Server when suddenly got a problem. The pre-installation task were okay the setting of environment variable. I got at least 1GB of swap configured before I run the installer, I have a fully qualified domain name(FQDN) specified for the installation and I got no problem with that . But while I am installing the infrastructure, there are several errors occurred and some of them were said to be an expected behavior and fixed that already. The only thing that I haven't configured yet is the error saying:
Oracle Database configuration Assistant: ERROR
               ORA-01503: CREATE CONTROLFILE failed
If you have experienced this kind of error and have fixed this, your advice,opinions and suggestions are very much welcome.
Thanks!
Answered By
ZenRod
0 points
N/A
#125586
Oracle database configuration assistant: error
Â
Hi Stephen,
Try this solution. Maybe because your control script has been changed that is why the syntax appeared. Create a new controlfile in the database and use the word SET in the NEW CONTROLFILE COMMAND. Follow the script below after doing it.
Scripting:
STARTUP NOMOUNT PFILE='F:/PFILE.ORA'
CREATE CONTROLFILE REFUSE SET DATABASE "arjucl" RESETLOGS
ARCHIVELOG
MAXLOGFILES16
MAXLOGMEMBERS3
MAXDATAFILES100
MAXINSTANCES8
MAXLOGHISTORY292
LOGFILE
GROUP1 'F:ORACLEARJUCLREDO01.LOG' 50M,
GROUP2 'F:ORACLEARJUCLREDO02.LOG' 50M,
GROUP3 'F:ORACLEARJUCLREDO03.LOG' 50M
DATAFILE
'F:ORACLEARJUCLSYSTEM01.DBF',
'F:ORACLEARJUCLUNDOTBS01.DBF',
'F:ORACLEARJUCLSYSAUX01.DBF',
 'F:ORACLEARJUCLUSERS01.DBF',
'F:ORACLEARJUCLEXAMPLE01.DBF',
'F:ORACLEARJUCLTEST_TBS01.DBF',
CHARACTER SET WE8MSWIN1252;
That's it! Now run the SQL>@ f:controlfile.cl. To test if this will work out. Hope this will help you to solve the problems!
By: Zen
Answered By
Amelia1
0 points
N/A
#125587
Oracle database configuration assistant: error
Hi Stephen Messer,
The solution given above is ZenRod is quite good.Here is the script:
Please try this scrip as well to resetlogs with sysDBA user privilege. Â First shutdown your database using command SHUTDOWN IMMEDIATE, then startup your database in nomount state using this command STARTUP NOMOUNT after that write down the following scrip to reset logs as mostly archiving is enabled.
SQL> CREATE CONTROLFILE SET DATABASE "ORCL" RESETLOGS ARCHIVELOG
      MAXLOGFILES 200
      MAXLOGMEMBERS 2
          MAXDATAFILES 100
          MAXINSTANCES 10
          MAXLOGHISTORY 22000;
-
 These values could vary according to your DB requirements.
-
 After these steps, startup your database first to mount and then to open state. It will resolve your problem.
Regards
Amelia
