Error when connecting linux oracle dataabse for replication thru oms

Question

I have installed oracle 8.1.7 ee on Redhat linux 7.1 and 6.2 both and also on windows2000.
When i try to access database of any oracle installed on linux machines from any of management server it gives following errors:
ora-01034 oracle not available
ora-27101 shared memory realm does not exist
linux error:2: file or dir does not exist.
if i try to access dataabse without login to any management server ( i.e thru dba studio) then it connects to it.
i want to setup master replication with two linux machine database.
if any person has solution for this then please help me.
Thx in advance
if possible mail me at [email protected]
thx in advance
pranav shah
null

Answer 1

1010056 wrote:
When iam connecting getting the following error
[rmancln@orawave ~]$ sqlplus '/as sysdba'
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jun 5 21:16:53 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> select status from v$instance;
STATUS
MOUNTED
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-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/rmancln/oradata/CLN/system01.dbf'provide details on what events lead up to this situation.
[oracle@localhost ~]$ oerr ora 1152
01152, 00000, "file %s was not restored from a sufficiently old backup "
// *Cause:  An incomplete recovery session was started, but an insufficient
//         number of logs were applied to make the database consistent. This
//         file is still in the future of the last log applied. The most
//         likely cause of this error is forgetting to restore the file
//         from a backup before doing incomplete recovery.
// *Action: Either apply more logs until the database is consistent or
//         restore the database file from an older backup and repeat recovery.