creating DB on 9.2 on Win2003. Unable to startup nomount
I used the DBCA to try and create a database on my new Windows 2003 server.
I chose to generate scripts and then used the 'Create database' option to create the DB. (I wanted to keep the scripts for reference).
The creation lasted just a few minutes and then failed with an ORA-03113: end-of-file on communication channel, closely followed by ORA-01034: ORACLE not available.
The creation failure also generated an OraDim.Log file that showed a series of error messages:
ORA-12638: Credential retrieval failed.
I raised a TAR and was advised to check my sqlnet.ora file for an entry 'SQLNET.AUTHENTICATION_SERVICES=(NTS)' If found replace the (NTS) with (NONE). As the default for this is (NONE) can anyone help and explain why it was set to (NTS)? I'm sure its something to do with the way the Windows admin accounts are set up on this server.
Anyway - I changed the entry and chose to re-try by running the scripts line by line.
I successfully created the Service and Password file using Oradim and Orapwd, then I connected to an idle instance as the SYS user, but when I tried to 'startup nomount' using my pfile I again encountered :
03113: end-of-file on communication channel
Again the Oradim.log file shows ORA-12638: Credential retrieval failed.
Anyone help me?
What version of the d/b?
I haven't used DBCA. Offhand - Am guessing that you are not getting authenticated (os or otherwise). What's ur remote_login_passwordfile, remote_os_authentication set to?
remote_login_passwordfile = EXCLUSIVE (Which is fine as I want to authenticate sysdba users by username and password only).
I don't have any remote_os_authentication parameter set.
I'm using 220.127.116.11 on Windows 2003 Standard Edition.
I'm running this directly on the box - no client connection.
I can connect to the default starter database installed with the software without problem (as sysdba or whatever).
I just can't 'startup nomount' with a pfile, to try and create a new database. The SQLNet.ora file now has no parameters at all.
What is your setting for the parameter
The default is OPS$. Using your windows authentication you should delete this value,so that you are not authenticated by "OPS$your_network_name\os_user_name",but only by "your_network_name\os_user_name"
Able was I ere I saw Elba
Red Herring time.
I've managed to get past this block. The problem was the DB_BLOCK_SIZE parameter in the init.ora file, which was hugely inappropriate (wrongly cut and pasted - it was set to the value of the DB_CACHE_SIZE!!!). Why this manifested itself with an error about credentials is beyond me.
damn init.propriate.ora file!!!
Able was I ere I saw Elba
Click Here to Expand Forum to Full Width