Out of memory using Windows Server 2003 and Oracle 9.2.0.3

Question

Hi,
I just installed both Windows Server 2003 and Oracle 9.2.0.3. The server I am using has 4 gigabytes of memory installed, and windows shows that to be the actual physical memory on the server. The paging file is 8 gigabytes for a total of 12 gigabytes of virtual memory.
Using the Oracle Database Configuration Assistant, I create a new database using default values. After verifying the installation worked OK (database started, queries ran), I attempted to change some of the memory parameters and was able to start the database using about 1.4 gigabytes of total SGA, with the O/S using about .3 gigabytes for a total of 1.7 gigabytes. I then attempted to change the buffer cache + 1 gigabyte for a total of 2 gigabytes. Now the database will not start and I get an out of memory error ora-27102 with an additional O/S memory error of "O/S Error: (OS 8) Not enough storage is available to process this command".
So, I have two problems:
1) With 4 gigabytes installed, and the O/S using only about 300 megabytes, why isn't Oracle able to take advantage of the memory on this machine past the 1.7 gigabytes (as reported by Windows task manager).
2) How do I change the spfile memory parameters so the database will start using spfile? I can start the database pointing to a pfile with lesser memory parameters, but I don't know how to effect change on the spfile, since I cannot start with the spfile.
Both these technologies (9.2.0.3 and Server 2003) are new to me, so any insight would be appreciated!
HERE ARE THE SPFILE PARAMETERS THAT WORKED:
SGA (M)
Shared Pool=104
Buffer Cache=960 ***
Large Pool=0
Java Pool=64
Total SGA=1128
SGA Max Size=1321
Aggregate PGA Target=1500
Current PGA Allocated=22868KB
WINDOWS MEMORY INFO FROM TASK MANAGER SHOW:
PF Usage=1.66GB
Physical Memory (K)
Total=4062704
Available=3203460
System Cache=2499096
Commit Charge (K)
Total=1748184
Limit=12288628
Peak=1925276
*** When I change this to 2048 the database did not start.
Thank you.

Answer 1

CREATE SPFILE
Purpose
Use the CREATE SPFILE statement to create a server parameter file from a client-side initialization parameter file. Server parameter files are binary files that exist only on the server and are called from client locations to start up the database.
Server parameter files let you make persistent changes to individual parameters. When you use a server parameter file, you can specify in an ALTER SYSTEM SET parameter statement that the new parameter value should be persistent. This means that the new value applies not only in the current instance, but also to any instances that are started up subsequently. Traditional client-side parameter files do not let you make persistent changes to parameter values. Because they are located on the server, these files allow for automatic database tuning by Oracle and for backup by Recovery Manager (RMAN).
To use a server parameter file when starting up the database, you must create it from a traditional text initialization parameter file using the CREATE SPFILE statement.
All instances in an Real Application Clusters environment must use the same server parameter file. However, when otherwise permitted, individual instances can have different settings of the same parameter within this one file. Instance-specific parameter definitions are specified as SID.parameter = value, where SID is the instance identifier.
The method of starting up the database with a server parameter file depends on whether you create a default or nondefault server parameter file. Please refer to "Creating a Server Parameter File: Examples" for examples of how to use server parameter files.
See Also:
CREATE PFILE for information on creating a regular text parameter file from a binary server parameter file
Oracle9i Database Administrator's Guide for information on pre-Oracle9i initialization parameter files and Oracle9i server parameter files
Oracle9i Real Application Clusters Administration for information on using server parameter files in a Real Application Clusters environment
Prerequisites
You must have the SYSDBA or the SYSOPER system privilege to execute this statement. You can execute this statement before or after instance startup. However, if you have already started an instance using spfile_name, you cannot specify the same spfile_name in this statement.
Syntax
create_spfile::=
Text description of create_spfile
Semantics
spfile_name
This clause lets you specify a name for the server parameter file you are creating.
If you do not specify spfile_name, Oracle uses the platform-specific default server parameter filename. If spfile_name already exists on the server, this statement will overwrite it. When using a default server parameter file, you start up the database without referring to the file by name.
If you do specify spfile_name, you are creating a nondefault server parameter file. In this case, to start up the database, you must first create a single-line traditional parameter file that points to the server parameter file, and then name the single-line file in your STARTUP command.
See Also:
"Creating a Server Parameter File: Examples" for information on starting up the database with default and nondefault server parameter files
Oracle9i Database Administrator's Guide for Windows (or other appropriate operating system specific documentation) for default parameter file names
pfile_name
Specify the traditional initialization parameter file from which you want to create a server parameter file.
If you specify pfile_name, the parameter file must reside on the server. If it does not reside in the default directory for parameter files on your operating system, you must specify the full path.
If you do not specify pfile_name, Oracle looks in the default directory for parameter files on your operating system for the default parameter filename, and uses that file. If that file does not exist in the expected directory, Oracle returns an error.
Note:
In a Real Application Clusters environment, you must first combine all instance parameter files into one file before specifying it in this statement to create a server parameter file. For information on accomplishing this step, see Oracle9i Real Application Clusters Setup and Configuration.
Examples
Creating a Server Parameter File: Examples
The following example creates a default server parameter file from a client initialization parameter file named t_init1.ora:
CREATE SPFILE
FROM PFILE = '$ORACLE_HOME/work/t_init1.ora';
Note:
Typically you will need to specify the full path and filename for parameter files on your operating system. Please refer to your Oracle operating system documentation for path information.
When you create a default server parameter file, you subsequently start up the database using that server parameter file by using the SQL*Plus command STARTUP without the PFILE parameter, as follows:
STARTUP
The following example creates a nondefault server parameter file s_params.ora from a client initialization file named t_init1.ora:
CREATE SPFILE = 's_params.ora'
FROM PFILE = '$ORACLE_HOME/work/t_init1.ora';
When you create a nondefault server parameter file, you subsequently start up the database by first creating a traditional parameter file containing the following single line:
spfile = 's_params.ora'
The name of this parameter file must comply with the naming conventions of your operating system. You then use the single-line parameter file in the STARTUP command. The following example shows how to start up the database, assuming that the single-line parameter file is named new_param.ora:
STARTUP PFILE=new_param.ora
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_616a.htm#SQLRF01315
Joel P�rez