QUESTION POSED ON: 03 November 2006
We have got new EMC storage and want to migrate our Oracle database 300+ to the new storage box. We have two servers (say A and B), SUN E6500 Server with Solaris 8 and Oracle 8.0.5 (A=production server and B=standby server). We have connected the new CX-500 storage to Box B and created all the file systems same as Box A. Our aim is to migrate all the Oracle data by taking a cold backup from Box A and restoring to Box B and after successful migration declare Box B as the production server.
For test purpose we have done the following:
- Taken Oracle cold backup and orahome (Oracle -binaries) from production server (Box A) and restored all into Box B.
- After the restore host was changed in listener.ora and tnsnames.ora from A to B.
Oracle was started successfully and Unix user "oracle" is able to connect to database using SQL*Plus <username>/passwd and when the listener is started other clients are able to connect also.
$whoami
oracle
$sqlplus username/passwd
Connected
SQL>
But the problem started when we tried to connect the database with Unix user. Other than Oracle having the primary group same as Oracle (i.e., DBA) using SQL*Plus username/passwd and we are getting the following messages:
$whoami
xyz
$sqlplus username/password
Error:
ORA-01034 : Oracle not available
....
However , using listener xyz is able to connect to DB as follows.
$whoami
xyz
$sqlplus username@dbname
pawword:
Connected.
SQL>
My questions:
- When /orahome is restored from Box A to Box B, why are non-Oracle Unix users not able to connect to DB without listener?
- Shall we avoid restoring orahome file system to Box B and restore only Oracle cold backup into Box B? Because when we restore ONLY cold backup and orahome of Box B was not touched then we didn't had the problem mentioned in (1).
- What would be the best way to migrate data 300+ GB from Box A to Box B other than what we have planned for?
Regards.
|
