Two SAP Instances (DEV & QAS) on singe windows host.

Question

Dear Gurus,
I am planning to install the two seprate R/3 4.7 Enterprise Ext.200 SR1 (central) instances on one host ( windows 2003 Standard R2 server.)
**Server Configuration :-**
**CPU :- Intel  Xeon 3.0 Ghz.**
**RAM:- 4 GB**
**HDD :- 380 GB**
**OS :- Windows 2003 Standard Edition R2 SP1**
**Database :- Oracle 9.4.0.1**
**SAP :- R/3 4.7E X 200 SR1(NON UNICODE)**
I have query related to
1)On above system configuration the two sap instances will run or not?
2) Oracle that I have to install oracle two times or Can I create two databases using the single oracle executable directory ?
3) If  I have to install oracle two times then what configuration I have to do to connect to the database?
4)What about the Host names ? I have to define two host names ? How ?
5) What activities I have to perform post installation ?
Please help me on this.
Thanks & Regards,
Sachin Sable

Answer 1

Hi Nilesh/Kaushal
Thanks for your support, I really appriciate it.
I had install the QAS instance successfully on one sever.
Now both QAS & DEV instances are up & running.
But I am facing problem while executing transactions related to database i.e st04,st03,db12,db02.
After executing this transactions I received followng dumps.
1) Runtime Errors         DBIF_DSQL2_SQL_ERROR 
Exception              CX_SY_NATIVE_SQL_ERROR
Database error text........: "ORA-00904: "KEY": invalid identifier"
Triggering SQL statement...: "FETCH NEXT "                        
Internal call code.........: "[DBDS/NEW DSQL]"                    
2) Runtime Errors         RAISE_EXCEPTION
Exception condition "DB_RELEASE_UNKNOWN" raised
Error analysis                                                 
A RAISE statement in the program "SAPLSORA" raised the exception
condition "DB_RELEASE_UNKNOWN".                                
Since the exception was not intercepted by a superior program  
in the hierarchy, processing was terminated.                   
3)Runtime Errors         BCD_ZERODIVIDE 
Exception              CX_SY_ZERODIVIDE
An exception occurred. This exception is dealt with in more detail below      
. The exception, which is assigned to the class 'CX_SY_ZERODIVIDE', was neither
caught nor passed along using a RAISING clause, in the procedure              
"SKOM_CT_PERF_BUF_REDO" "(FUNCTION)"                                         
Since the caller of the procedure could not have expected this exception      
to occur, the running program was terminated.                                
The reason for the exception is:                                              
In the current program "SAPLSKOM", an arithmetic operation ('DIVIDE',         
'/', 'DIV', or 'MOD') with a type P operand attempted to divide               
by 0.                                                                         
4) Runtime Errors         COMPUTE_BCD_OVERFLOW    
Exception              CX_SY_ARITHMETIC_OVERFLOW
Error analysis                                                                               
An exception occurred. This exception is dealt with in more detail below    
. The exception, which is assigned to the class 'CX_SY_ARITHMETIC_OVERFLOW',
was neither                                                                
caught nor passed along using a RAISING clause, in the procedure            
"SKOM_CT_PERF_BUF_LIB" "(FUNCTION)"                                        
Since the caller of the procedure could not have expected this exception    
to occur, the running program was terminated.                              
The reason for the exception is:                                            
An overflow has been determined in the current arithmetical operation       
containing operands of type P. Possible causes include:                     
1.  The results field of type P is to small and the result does not fit     
    into it.                                                                
    places.                                                                 
2.  The result or partial result has more than 31 decimal places.                                                                               
Thanks,
Sachin