well after running control.sql file got created but as error was there
then i tried to open the db it asked me for recovery then i did reocvery by
recover database using backup controlfile until cancel;
then it asked for some archive file hence i provided the same and database open now!!
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\FNQ\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 186608596 generated at 01/16/2014 15:05:06 needed for thread
1
ORA-00289: suggestion : D:\ORACLE\FNQ\ORAARCH\FNQARCHARC11188_0779565053.001
ORA-00280: change 186608596 for thread 1 is in sequence #11188
SQL> Alter database open resetlogs;
Database altered.
SQL> select status from v$instance;
STATUS
------------
OPEN
but sapints give error as
n error occurred while processing option SAP ERP 6.0 EHP4 Ready - Support Release 1 > Software Life-Cycle Options > System Copy > Oracle > Target System Installation > Central System > Based on AS ABAP > Central System( Last error reported by the step :SQL statement or script failed. DIAGNOSIS: Error message: ORA-27091: unable to queue I/O ORA-27070: async read/write failed OSD-04006: ReadFile() failure, unable to read from file O/S-Error: (OS 38) Reached the end of the file. ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist ORA-27091: unable to queue I/O ORA-27070: async read/write failed OSD-04006: ReadFile() failure, unable to read from file O/S-Error: (OS 38) Reached the end of the file. ALTER DATABASE ARCHIVELOG * ERROR at line 1: ORA-01034: ORACLE not available ALTER DATABASE OPEN * ERROR at line 1: ORA-01034: ORACLE not available ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Disconnected . SOLUTION: For more information, see ora_sql_results.log and the Oracle documentation.). You can now: