Sorry, You are right I should had say "Hi this seems to be related to bug xxx".
I'm no fully sure, I'm going to apply the patch 10.2.0.2
and I'll confirm fully.
But this is something that approximates more to that problem,and hope this can help him, there is not too muchinformationon the subject. I get the same message on
oradim.log and sqlnet.ora. I have similar symptoms.
And this is not another oracle home (installe over new 2003 installation).
My logic is simple, the problem is very similar, and there is a high probability this fix that too.
I had been all the morning creating and recreating the service on 2003 (only 10.2g, no other oracle home), I evengenerated a script from oracle database wizard to check if I was missing some code of line or parameter.
I move the init and spfiles to database directory so it could find the pfile anyway, and start with a simple startup without specifying parfile
When doing the oradim -edit, the regedit ORA_PERP_PFILE disappeared and I recreated manually, I couldn't make it work(maybe I did some mistake in one test), but definetively this is not normal
I had created several dozens of services and never had a similar problem.
Finally checking oradim and sqlnet I found some messages, went to metalink and found there was a bug.
It says it works from sqlplus using startup, and it is the same for me.
I found another comment in oracleforum saying the problem was because the spfile was wrongly created, so I recreated too. But that wasn't.
Niall Litchfield <firstname.lastname@example.org> wrote:
I'm intrigued how you determined that this bug was relevant. The bug
you point to is intermittent - which Nigel didn't mention - and
suggests that using oradim to start the service doesn't work at all
when in fact it appears that oradim manually will start the instance
though the pfile had to be specified.
On 6/27/06, Juan Carlos Reyes Pacheco <email@example.com
> Hi this is a bug
> Windows: Starting the instance service fails to start the database in Server
> rel. 10g
> Doc ID: Note:359428.1
> Bug 4598734
> Checking your oradim. log you'll find
> Tue Jun 27 11:19:18 2006
> C:\oracle\product\10.2.0\db_1\bin\oradim.exe -shutdown -sid
> perp -usrpwd * -shutmode immediate -log oradim.log
> Tue Jun 27 11:19:19 2006
> ORA-01012: not logged on
> and sqlnet.ora
> Fatal NI connect error 12560, connecting to:
Oracle Certified Profesional 9i 10g
Orace Certified Professional Developer 6i
10 years of experience from Oracle 7 to Oracle10g and developer 6i